ojrits.blogg.se

Make sure that AP Fastboot indicates "Unlocked, status code 3"Īlso, when you reboot, you will get a warning screen about an unlocked bootloader. Run through the entire process, until it tells you you have a bootloader unlock. Next, download Motopocalypse.zip by Dan Rosenberg from here: You need to be rooted, have the motorola drivers installed (link here - sorry, it's device manager, but they do have all the drivers in a nice package.) Don't update unless you know it won't disable the bootloader exploit

Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things. Be careful, don't flash stuff for other devices, etc etc.įuture OTAs may (will) disable this exploit. You can flash any firmware, recovery, etc that you want. This essentially makes the phone behave like an unlocked dev edition. So here's a how-to on unlocking and flashing a custom recovery.

So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked! you mean you tried it a while ago back on safestrap bootlocked, and the restore failed? As for restoring a safestrap backup on top of a fresh CM10 you have now, I am not entirely sure how safestrap works, haven't used it myself but as long as it is the same CM10 rom build you used before I don't see why you should have any problem with that. Not sure what you meant by restoring a backup before unlocking. Hmm not sure why it didn't work exactly (bad gapps flash file maybe), but go back into recovery and reflash gapps alone, and you should be ok on reboot. before you put on a custom rom) then you need to disable it by this method, get it? But to get into custom recovery after the initial flash while still on stock (i.e. Once the script is disabled by rebooting into TWRP, or after a custom rom is installed with said script removed, you no longer need to worry about it. When you flash TWRP or CWM, if you do not boot directly back into custom recovery, the shell script is not disabled and runs when the phone is booted, which overwrites it back to stock recovery. It is a shell script built into the stock rom that overwrites back to stock recovery unless disabled.

RikRong look up /system/etc/install-recovery.sh.