I wil
UPD: I finally found the root of the problem. I made one mistake, when refactored some classes and this became a problem due to which the payload was loaded to the device, but exploit was not started. Fixed in version 1.1.1.
l think about your problem. All used payloads located in Rekado folder in your devices memory root.Switch FW: 5.1.0
Auto RCM: No
SDCard: 128GB Samsung EVo Plus EXFAT formatted
Smartphone: OP3 Lineage 14.1 Rooted (No problems with NXLoader and this OS/version/cables/OTG adapter)
Hello @Menos,
Thanks a lot for Rekado.
Since it's regularly updated, I would like to use your app instead of NXLoader but, sadly, I have a problem using it with my OnePlus3.
My cables and OTG adapter are HighGrade cables and everything works fine with NXLoader or TegraRCMGui (oc, Only Cable used for TegraRCM).
Storage and USB rights are permanently set for Rekado.
When I tested Rekado for the first time, I deleted NXLoader app+data and rebooted the device!
After that, I even tested deleting Rekado app+data, going into recovery and deleting cache and Dalvik/ART cache before any test.
App react to the fact that it's a switch and ask me which Payload I want to send!
I tested various working Payloads including the embedded one but I only get a black screen after sending the payload.
The log is normal (Payload sent)(see below or attached) and I have to press the ON/OFF button for x seconds before going into RCM again (I check to be sure that I'm in RCM)
I also tried without SDCard since it's not needed to launch the SX payload ->> boot.dat missing screen ->> without success (black screen!)
Btw, even when I delete app+data, Rekado find a list of my previous payload so there is a remaining file/db somewhere in my phone.
Can you tell me where is located the db/file and I will try to delete it manually before restarting the whole process and check again?
Or maybe if you have any idea of what can be the problem?
Thanks a lot,
UPD: I finally found the root of the problem. I made one mistake, when refactored some classes and this became a problem due to which the payload was loaded to the device, but exploit was not started. Fixed in version 1.1.1.
Last edited by Menos,