Related
Hi all,
Bit of a noob query, apologies.
I had never rooted a device until last night when I took the plunge with WugFresh's (thankyou so much) program. Great program had an issue with the adb drivers (turned out I needed more power for the USB port) hence I plugged the USB into the rear port and it magically appeared and installed, thus if you have problems installing the driver make sure you are plugged into the rear.
But I am now on the 4.04 google factory flash.
Now my query is, now I am on this 4.04, I presume I am no longer rooted. Can I use WugFresh's program to root the phone again or do I have to wait for another update to the program?
I was rather twitchy during rooting, expecting power cuts across the UK, earth tremor to knock the lead out at the wrong time, aliens to come down and screw it up etc that I dare not try it (don't really understand what I did even though it has worked)...
There is a program on now called superuser, but does not seem to have root access, so I presume I am not rooted now??
Any help would be appreciated.
Thanks
Darren
I did refer to a guide but can't post the link to it.
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???
pittnuma said:
Yip, I can agree with the statement, I don't know what was happening.
However, I could follow some of it, I think the bootloader is unlocked (can boot into with vol and off switch), I have clockwork and su, the installer did flash with clockwork.
Wonder if I am indeed rooted then???
Click to expand...
Click to collapse
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.
zephiK said:
this is why you don't use toolkits... when you use them you dont know what's going on.
fastboot oem unlock (bootloader unlocked already?)
fastboot flash recovery <get clockwork recovery img>
get su.zip (find it on forum)
flash it in clockwork
you have root.
alternatively, you can flash a custom rom.
Click to expand...
Click to collapse
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
does the toolkit update itself to include the 4.0.4 root? no, so download the new toolkit..also u dont need to try 3 toolkits, u need the latest and select gsm 4.0.4
if u use the su.zip, u need the latest working with the 4.0.4
again what make u say "still no root"? with no details we can't help u
foreman31 said:
Actually no, not with 4.04
I flashed su.zip with CWM and no dice and I used 3 toolkits as well as that method and still no root.
Click to expand...
Click to collapse
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.
hEaTLoE said:
When you boot the phone is there an unlocked lock at the bottom of the Google screen? That means your bootloader is unlocked. You can always get into the bootloader using the volume buttons and power.
Once again...using toolkits suck. Now you're stuck in limbo. Try installing an app that needs root like Titanium Backup and see if it works.
Click to expand...
Click to collapse
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume
pittnuma said:
Thanks, yes there is, so the bootloader is unlocked.
I am flashed correctly so just the root I presume
Click to expand...
Click to collapse
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Hi guys, just curious but is there anyway to gain root temporarily in 4.0.4 without unlocking bootloader? Similar to the escalation of privileges hack that worked on 4.0.1/4.0.2.
I want to remove the /system/bin/su and /system/app/Superuser.apk files on the device to get rid of the "Unsupported Device" warning in Google Wallet.
Thanks in advance.
jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
Ahh right, I have the Superuser, however when I tried the app suggested earlierit stated device not rooted...
Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt
jonnyg1097 said:
If you see a superuser app in your app drawer then you have a proper root. If not then something went wrong.
Click to expand...
Click to collapse
This is not entirely true. You can have the Superuser app in your app drawer and still not have root. The permissions on su need to be set properly.
Diger36 said:
Download Superuser-3.0.7-d-signed.zip from here: Link
and flash that through CWM... It definately works on 4.0.4.
Click to expand...
Click to collapse
pittnuma said:
Got it...
Installed new SU.zip, I had a slightly older version and the recovery-clockwork-5.5.0.4
Thanks all.
Can't post links yet but this is the link for the su I used just add the www etc
box.com/s/jvcf196j7x8f8vrc9cyt
Click to expand...
Click to collapse
A look at the first page.... Ah well, glad you sorted it out...
Sent from my Galaxy Nexus using xda premium
1. Will Galaxy Nexus rooting wipe my phone's data?
2. Which method is recommended? I've found Toolkit 5.7, and that one:
http://forum.xda-developers.com/showthread.php?t=1454314
Maybe they all do exactly the same?
Unlocking wipes phone, rooting comes after..Copy anything from sd card you want to save to pc. Use mskip's toolkit and read all instructions and you will be fine. Google saves all your apps in market and contacts will sync when you sign into google.
Hope this helps.
Use my guide.
Stickied above...and linked in my sig.
But yes, it will wipe your data.
You could, however, use the backup method detailed in my guide.
DON'T use these damn toolkits...
If you someday soft brick your phone (and if you tinker...you will, I promise) you're going to want to know how to utilize the resources you needed to root it manually...and if you used a toolkit, you'll be far worse off as you won't even know if adb/fastboot are set up properly...and will cause a huge barrier of troubleshooting your problems.
I personally promise...
Do it the manual way...and you'll end up with a rooted phone in an hour.
It's not hard.
I also root my nexus without using those tool kits (seems don't have any when I got my nexus)
you may follow Jubakuba's guide, it's safe and not that hard, I root my nexus within 30mins (not following Jubakuba's guide, but almost the same)
Jubakuba said:
DON'T use these damn toolkits...
If you someday soft brick your phone (and if you tinker...you will, I promise) you're going to want to know how to utilize the resources you needed to root it manually...and if you used a toolkit, you'll be far worse off as you won't even know if adb/fastboot are set up properly...and will cause a huge barrier of troubleshooting your problems.
I personally promise...
Do it the manual way...and you'll end up with a rooted phone in an hour.
It's not hard.
Click to expand...
Click to collapse
X3. I used the toolkit for the drivers when I couldn't get mine properly installed. Otherwise, everything else was done in the command prompt with ADB and Fastboot. Very simple and you'll learn what these toolkits are doing behind the scenes so you can better troubleshoot later.
I also rooted my Nexus one without tool kits, it's very easy!
bullka said:
1. Will Galaxy Nexus rooting wipe my phone's data?
2. Which method is recommended? I've found Toolkit 5.7, and that one:
http://forum.xda-developers.com/showthread.php?t=1454314
Maybe they all do exactly the same?
Click to expand...
Click to collapse
If your bootloader is locked, and you are running 4.0.1 or 4.0.2, you can root using this method.
If you want, you can then install ROM Manager from the market and do a backup. Then copy that backup off your device, and proceed to unlock your bootloader (which will wipe) if you want, but then you can restore your backup, and you will have all your data and an unlocked bootloader.
Hi,
I have my bootloader unlocked at the moment after the upgrade to 4.0.4 using this guide: http://forum.xda-developers.com/showthread.php?t=1391881
So I understand that rooting won't erase my phone. Right?
To root I need (I'm skipping blablabla and leaving just the important):
1) fastboot reboot-bootloader
2) fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
3) select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the Superuser-3.0.7-efghi-signed.zip
4) find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option
I'm rooted permanently without loosing my data (as I already have bootloader unlocked), right?
bullka said:
Hi,
I have my bootloader unlocked at the moment after the upgrade to 4.0.4 using this guide: http://forum.xda-developers.com/showthread.php?t=1391881
So I understand that rooting won't erase my phone. Right?
To root I need (I'm skipping blablabla and leaving just the important):
1) fastboot reboot-bootloader
2) fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
3) select the "Recovery Mode" option again on your phone.
You should get a new recovery menu here. Select "install zip from sd card" and "choose zip from sd card."
Find the Superuser-3.0.7-efghi-signed.zip
4) find "Rom Manager" from the market. (The free version is fine.) Use the "Flash ClockworkMod Recovery" option
I'm rooted permanently without loosing my data (as I already have bootloader unlocked), right?
Click to expand...
Click to collapse
Correct.
Just remember that un-locking/locking DOES reset your SD.
But as you said, you're already unlocked. So you're good!
Edit:
PLEASE let me know if that superuser.zip works for you, btw.
I had to update the OP recently to fix 4.0.4 users not being able to root...but wanted the same file to also root us CDMA users and GSM users who aren't on 4.0.4.
If that zip doesn't work...you simply won't have root access. Nothing bad will happen.
Let me know if that happens though (I can't test a 4.0.4 gsm phone, obviously) and I'll get you a .zip that I KNOW works for 4.0.4 users.
Quick question: does the SuperUser app developer has his homepage? Who's the author of that?
Now I understand that there're tons of superuser.apk modifications in the internet. Right?
bullka said:
Quick question: does the SuperUser app developer has his homepage? Who's the author of that?
Now I understand that there're tons of superuser.apk modifications in the internet. Right?
Click to expand...
Click to collapse
http://androidsu.com/superuser/
There are binaries required in 4.0.4 that aren't officially updated, it seems.
Hence my new .zip that is compiled from official SU, but with new binaries.
Jubakuba said:
Correct.
Just remember that un-locking/locking DOES reset your SD.
But as you said, you're already unlocked. So you're good!
Edit:
PLEASE let me know if that superuser.zip works for you, btw.
I had to update the OP recently to fix 4.0.4 users not being able to root...but wanted the same file to also root us CDMA users and GSM users who aren't on 4.0.4.
If that zip doesn't work...you simply won't have root access. Nothing bad will happen.
Let me know if that happens though (I can't test a 4.0.4 gsm phone, obviously) and I'll get you a .zip that I KNOW works for 4.0.4 users.
Click to expand...
Click to collapse
Hi,
Thanks.
Just followed you guide and I have now superuser installed and working. Thanks.
Your guide has some errors. Link is to Maguro and your guide says to flash Toro. Fix the links.
When I flashed Clockwork Recovery with ROM Manager, superuser app asked to confirm the SU request by ROM Manager.
So I assume rooting works well.
bullka said:
Hi,
Thanks.
Just followed you guide and I have now superuser installed and working. Thanks.
Your guide has some errors. Link is to Maguro and your guide says to flash Toro. Fix the links.
When I flashed Clockwork Recovery with ROM Manager, superuser app asked to confirm the SU request by ROM Manager.
So I assume rooting works well.
Click to expand...
Click to collapse
I should probably implement that better.
Guide originally came from a CDMA only forum.
And a GSM only forum.
Merged the posts here...
But it does mention changing the code.
I'll fix it up so it's more obvious now.
And yes, if it asked for SU...
It's fine.
Great news. I hadn't had anyone test yet.
Thanks for being a guinea pig .
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
EDIT: Never mind, it seems the awesome developers have figured out ways to relock the bootloader.
https://play.google.com/store/apps/details?id=aperture.ezekeel.gladoscontrol
Potentially.
MAYBE.
Just Maybe you can re-lock with this.
I'm not sure if it requires SU or not.
And I haven't given anyone this advice yet, so you'll be the first.
But as the above poster said...
Mobile Odin first.
mt6272 said:
My USB connector is broken on my nexus. Amazon has sent me a replacement, which I have at hand. I would like to lock my boot loader on my nexus with the broken USB connector before sending it back to amazon.
Any thoughts as to how I may accomplish this?
If not, can you at the least convince me amazon won't care that my boot loader is unlocked?
Click to expand...
Click to collapse
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
EDIT: For those that are curious, to unlock your bootloader without wiping, replace the command above with this:
su
dd if=/sdcard/param.unlock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
Awesome efrant, thank you.
I'll reference to this later if need be.
efrant said:
Not sure if Amazon will even care if it is locked or not.
Thanks to AdamOutler and a few others, you can re-lock the bootloader without being plugging into a computer, but root (and busybox) is required.
Download the attachment from this post, and extract the files to the root of /sdcard. Then open a terminal emulator on your device and type the following commands:
su
dd if=/sdcard/param.lock of=dev/block/platform/omap/omap_hsmmc.0/by-name/param
That should re-lock your bootloader.
Now you need to make sure you are running a stock ROM and stock recovery.
Once that is done, you can then remove busybox, and finally, you can delete /system/app/Superuser.apk and su.
Click to expand...
Click to collapse
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Zepius said:
couldnt you take it a step further?
doesnt mobile odin work properly even if the bootloader is locked?
Click to expand...
Click to collapse
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
efrant said:
Yeah, he could use mobile odin to flash to stock (and thus, no need to remove custom recovery, root, etc.), but mobile odin will not re-lock his bootloader.
Click to expand...
Click to collapse
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Zepius said:
ah i figured you could still use mobile odin to restore to stock with the bootloader already locked when you first run it.
ive never used it so i guess i didnt understand completely what it did.
Click to expand...
Click to collapse
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
efrant said:
No, you're right. You CAN use mobile odin with a bootloader already locked. However, you need root to use it.
Click to expand...
Click to collapse
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Zepius said:
so you could then change the param file, which locks the bootloader, then use mobile odin to go back to 100% stock and still have a locked bootloader.
Click to expand...
Click to collapse
Yes. That's what I was trying to say in my earlier post, but I guess it wasn't clear. Mobile Odin will not change the lock state of the bootloader, but will work in either a locked state or an unlocked state, assuming you have root.
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
I don't know how you have broken USB, but my friend had it broken - it didn't want to charge longer than few seconds, connection to PC was extremely inconsistent...
Samsung told him that it happens on SGNs sometimes and that it is caused by oxidation of USB. It isn't covered by warranty.
But he solved it very simply - you can clean the USB by soft toothbrush and it works like a charm again. Hope this helps you.
mt6272 said:
More details on my phone: It is rooted, running aokp m5 & franco m3. It sounds like there is a solution to my problem contained within this thread - however, things are a bit hazy to me when it comes to what order to perform these operations and which apps to use when.
My thanks to the first person who compiles a step-by-step (albeit brief and concise) guide to unrooting, re-locking the bootloader, and restoring to stock WITHOUT being connected to the computer!
Click to expand...
Click to collapse
It is not that difficult, and I'm sure you do not need a step by step.
I haven't tried this on my device, as I don't really feel like wiping, but:
1) Lock your bootloader as per my post above. EDIT: I just looked at Mobile Odin, and it seems that Chainfire has implemented flashing the param partition as well in his app, so you can skip this step and go straight to step two.
2) Download the param file from the same post mentioned in step 1, and extract it to the root of your /sdcard.
3) Rename the param.lock file to param.img
4) Download version of the stock ROM for your device from here, e.g., if you have a GSM device, download the maguro factory image, if you have a Verizon device, download the toro factory image.
5) Extract the system, boot, userdata and recovery images from within and place them on the root of your /sdcard.
6) Buy Mobile Odin Pro from the Play Store. [You can use get the free version from the XDA thread here, but it needs setting up, and I'm not going to guide you through that.]
7) Run Mobile Odin Pro and follow the instructions here. It should be pretty obvious what you need to do.
I'm running AOKP 4.2, their latest release. I, too, have a failed USB connection. I downloaded the latest recovery from the link for my Verizon Toro. When I used the paid version of Mobile Odin, it says "partition could not be found in file". I tried the older, ICS image, but it just factory reset my AOKP install, not reflash to stock. So far, I've locked the boot loader, but I can't get rid of AOKP. I think it is because Mobile Odin doesn't reflash the bootloader, which I learned after my attempt, and I attempted to Odin back to factory ICS, which is a different bootloader. My other thought was to get into TWRP and flash an older AOKP ICS build, which flashes the older bootloader(right??), and try again, but I have no recovery, stock or otherwise after my Mobile Odin attempt. Any advice at this point? Should I just send it to Verizon as-is and let the chips fall where they may?
Quick update: I used Goomanager from the market to instantly flash TWRP. BAM! Recovery restored! I just finished flashing AOKP Jellybean Milestone 1, which is 4.1.2. I also figured out my JRO030 issue. It was a bad .tar file. When I browsed it with Winrar, it containted another file with the same name and no extension. I found another .tar file with the entire file structure inside. I'm currently booting into AOKP M1 as I type. I'll attempt to Mobile Odin with the JRO030 factory image (4.1.1) over 4.1.2 and then update this thread again. I hope I can save others some heartache.
The JRO030 update said something about "unable to extract update script". So I gave up on Jelly Bean and went futher back. I found an old AOKP ICS build, Milestone 6, flashed to that and used the monster 470 mb 4.0.2 update file that was linked to in a galaxynexusforums post with Mobile Odin. TADA! It worked like a charm. No root. Stock software. The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
scubamike said:
Snip
The only downside is that recovery is broken. It shows an Android guy with a red exclamation point over his belly. Whatever. I'm on 4.0.2 stock VZW software. That's all I care about. Let me know if anyone needs help with this.
Click to expand...
Click to collapse
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
efrant said:
That IS the stock recovery.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I thought it was too, but, just for the heck of it, I tried taking the OTA. It rebooted and stuck on the android guy with the red exclamation. I had to pull the battery.
It is the stock recovery and no, you did not have to pull the battery. The Android with the red triangle is the main screen of the stock recovery . To access the menu from the main screen, hold power and press volume up. This is covered in at least 2 of the stickies in the General section.
Sent from my Nexus 4 using Tapatalk 2
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
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...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://d-h.st/QGe
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Reboot directly into recovery, and allow TWRP to disable the re-flashing.
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
----IMPORTANT NOTE:----
IF you are on the latest OTA and have NOT unlocked, it is impossible at this time to unlock. It may be possible in the future if someone finds another exploit, but not likely. Basically, if you updated without researching (that's why you shouldn't do that) or got a new one after the OTA, you're SOL for right npw
sloosecannon said:
So if anybody's been reading the news, you may know that the bootloader for the Razr M has finally been unlocked!
So here's a how-to on unlocking and flashing a custom recovery.
A couple notes:
This essentially makes the phone behave like an unlocked dev edition. You can flash any firmware, recovery, etc that you want. Be careful, don't flash stuff for other devices, etc etc...
FOLLOW THE INSTRUCTIONS...
Future OTAs may (will) disable this exploit. Do it while it can be done! Also, beware OTAs! They could disable this, or do bad things... Don't update unless you know it won't disable the bootloader exploit
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...)
First, root if you haven't already...
Next, download Motopocalypse.zip by Dan Rosenberg from here: http://vulnfactory.org/blog/2013/04/08/motorola-bootloader-unlocking/
extract the zip and run
Run through the entire process, until it tells you you have a bootloader unlock.
Make sure that AP Fastboot indicates "Unlocked, status code 3"
Also, when you reboot, you will get a warning screen about an unlocked bootloader.
Next, choose your recovery. There are 2 options, TWRP (Touch Win Recovery Project) and CWM (ClockworkMod)
either works, and each has benefits and downsides, choose whichever one you want.
Follow the instructions for your flavor of recovery:
CWM:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/cwm-recovery--scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "cwm-recovery--scorpion_mini.img" unless you renamed it): fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
The first time you use CWM, it will ask you if you want to disable something that would cause CWM to stop working. You do want to, so say "yes". Othewise, you'll have to reflash CWM every time you want to use it
TWRP:
Download the .img file here: http://goo.im/devs/Hashcode/scorpion_mini/twrp2.4-recovery-scorpion_mini.img
Move it to the same place you extracted the .zip above.
Open a command prompt/terminal/command interpreter at that location (Windows short-cut: shift-right click, command window here)
type the following (filename is the name of the file you downloaded, probably "twrp2.4-recovery-scorpion_mini.img" unless you renamed it):
fastboot flash recovery filename
and press Enter. Let it flash, then reboot.
Now, you need to disable the automatic re-flashing of stock recovery.
Run adb shell from the same info and run the following commands (you can copy-paste and press enter):
su
mount -o remount,rw /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro /system
Now, you have TWRP running on your Razr M
Please consider donating to Dan Rosenberg here for all the work he's done for our phones!
Congrats! You now have a custom recovery on your Razr M
Reboot into recovery, and you're done!
Click to expand...
Click to collapse
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Awesome!!!! Hopefully this will spark up some dev activity. I know this is huge I just hope its not too little too late.
BoredKender said:
I followed the instructions, ran the .bat, but my Razr M is still being shown as locked 1. Am on 4.1.1 stock rom. Do I need to uninstall SafeStrap?
Edit- Found my answer, the phone needed to be unlocked so it could ask me for SU permissions. Hope this helps someone else so I don't feel like the only idiot.
Click to expand...
Click to collapse
Nope, don't need to uninstall safestrap, and yep, you do need SU.
sujaanj said:
As long as we do this first, future OTAs can't relock our bootloaders, can they?
Click to expand...
Click to collapse
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
sloosecannon said:
That's really not known... advise you steer clear of OTAs for the time being... until we can determine if it will actually relock or not...
Click to expand...
Click to collapse
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
trouble installing recovery
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
dnoren said:
Thanks! I successfully unlocked the bootloader following the awesome instructions AP Fastboot indicated "Unlocked, status code 3"
I then let the device reboot.
I'm trying to install CWM following the instructions and I get <waiting for device>
This makes me think i need to not have the phone booted into the OS
What am I doing wrong.
Please excuse my newbness
Regards,
Darryl
Click to expand...
Click to collapse
You need to be in fast boot mode for it to flash recovery.
Turn off your device, hold Power + Vol Up + Vol down then select fast boot and plug your phone into your computer.
Sent from my XT907 using xda premium
new roms
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
CaptainElwood said:
Thanks for the write up, worked flawlessly. So I did this with safestrap installed, can I just wipe the phone and install a rom made for safestrap like you normally would with CWM?
Click to expand...
Click to collapse
Yes, as long as you mount your /system first. Found that out the hard way too...
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Nope
ifrankie10 said:
Does this wipe our phone
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
No, everything is the same except I get a warning every boot that my phones bootloader is unlocked
Has anyone flashed a dev edition rom yet? If so what one, I wanted to try but the cm10 thread has broken links. Can I get that somewhere else?
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Sent from my XT907 using xda app-developers app
---------- Post added at 03:11 AM ---------- Previous post was at 03:07 AM ----------
and can we rsd back to stock if we can't get into the recovery but into fastboot
Sent from my XT907 using xda app-developers app
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
mindflayyer said:
I'm trying to help unlock my friends razr m, but his device was updated to 4.1.1 in the Verizon store by one of the sales associates. Does the root method (required for bootloader unlock) work on 4.1.1?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
If I recall correctly, 4.1.1 is fine, just use the JB root method. 4.1.2 is an issue, but that has not been pushed yet (on Verizon that is).
Floundering with recovery
I've tried both methods cwm and twrp it says writing recovery, okay, and finished but when i try to go into recovery I just get the Green robot
Any ideas on what I'm doing wrong?
Thanks
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Hmm..
Also say my screen cracks and I call Motorola and they say send it out and they see that it is unlocked does that mean they will not repair it
Click to expand...
Click to collapse
If they are able to discover that the phones system files have been tampered with in anyway, including unlocking, rooting, installing custom recoveries, roms, modems etc.. most likely they will not fix your phone. Quoted off the Motorola website "Unlocking your DEVELOPER EDITION's bootloader voids all warranties" (Naturally this goes for retail edition even more so). I have however hear of people getting unlocked phones repaired under warranty, just make sure that you RSD back to stock, unrooted before you send it.
pjf626 said:
Cant get this to work and I can't get safestrap off my phone
Sent from my cm_tenderloin using Tapatalk HD
Click to expand...
Click to collapse
Gonna need a tad more detail.. Are you sure that you're rooted? If not, that would cause both of your problems. You also need to uninstall safestrap through the safestap app, and then remove the app.
sujaanj said:
Well, from what I read from Dan's explanation on his website, we are essentially blowing a fuse that can not be reset. So I'm leaning towards rejecting OTAs from now on but according to my limited understanding, we will be safe.
Click to expand...
Click to collapse
Yes unlocking is blowing a fuse but that's beside the point, there is a separate piece of software that looks at that fuse and decides whether to allow the system to boot an unsigned system or not. If the OTA changes this piece of software to use another fuse instead (there might be many of them) then your device will be locked again and we will be back at square one, no fuse need to actually be reset for this to happen.
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
ahmadsraj said:
Hero guys
I just want to know, is there any way to root and keep getting OTA ?
And what is the best method to root?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete or change any files and apps that is build-in on system.
Even you want to delete apps made from telecom operators IS NOT PERMITTED!
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
missile0407 said:
You still can OTA, even your phone is rooted.
Only their is some tips you need to know:
1. Don't delete any files and apps that is build-in on system.
2. Recovery need flash back to original version.
For these two tips, you can do OTA even your phone is rooted.
But note that YOU NEED TO ROOT AGAIN every OTA.
Click to expand...
Click to collapse
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
craig0r said:
Speaking to point 2:
I recommend not flashing a custom recovery at all. You can boot to TWRP/CWM/Philz from fastboot without flashing, and this leaves your stock recovery intact.
To do this: download your preferred recovery image. Let's say it's called "openrecovery-2.7.0.3-m8.img"
Copy this file to the same folder your "fastboot" executable is in on your computer.
Boot your phone into fastboot and connect it to your computer via USB.
Type in the following on your computer:
Code:
fastboot boot openrecovery-2.7.0.3-m8.img
Now your phone will boot into TWRP without touching your partitions or anything else that might affect OTAs. Apply your root.zip update and reboot!
EDIT: Once you've booted into your custom recovery from fastboot, you can disconnect the USB, so you're not stuck at your PC.
Click to expand...
Click to collapse
Hello,
I have the same question as the OP. Everything seems to make sense when following this post. My question is even though I will just boot into recovery without ever flashing the recovery am I really able to disconnect my phone from the computer? It seems like the recovery files are actually on the computer so I would need to keep the phone connected while I install the supersu.zip
Thank you for the help
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
exad said:
I don't see why you would want to disconnect it but the image should be loaded into ram so I assume it would be safe to disconnect. I have never tried it though :/
Click to expand...
Click to collapse
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
SouthBayBruin said:
Ok I guess I should just leave it connected since I just need to install the supersu.zip file.
Every time an OTA update is applied will I just need to boot into TWRP recover and reinstall the supersu.zip file in order to regain root access?
Click to expand...
Click to collapse
There's no reason you *can't* leave it plugged in, but yeah, when you run the fastboot command it loads the custom recovery into RAM, and the connection to your computer is doing nothing for you. I give my personal guarantee that it's 100% safe to disconnect after recovery's loaded. But again, if leaving it plugged in makes you more comfortable, it won't hurt.
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
SouthBayBruin said:
Did you just install the regular supersu file?
I read this thread (http://forum.xda-developers.com/showthread.php?t=2755657) and it seems that if I install the regular supersu root file the OTA update will fail.
Just wondering if you just used the regular files in order to root your phone.
Click to expand...
Click to collapse
http://download.chainfire.eu/396/SuperSU
zimilaci said:
I can confirm it, that with root OTA is possible
I had a device with root, s-off, unlocked etc... but stock recovery, stock rom,..
today I got the ota, updated without any problems... I just needed to boot into custom recovery afterwards and install the root.zip
Click to expand...
Click to collapse
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
KaranNavani said:
Can you please guide me through the entire process on how to install the OTA update and not lose root, I don't have much knowledge when it comes to flashing into recovery, etc. I do have an HTC One M8 with S-Off. I would be eternally grateful if you could help me out.
Click to expand...
Click to collapse
Dude, do the research yourself. I don't know how many more times this has to be said. There's nothing special you have to do, just apply the OTA update when prompted