Related
Stop, listen. Follow my directions, if you fail to follow directions I will no longer help you. Don't PM me and ask. If you screw up ask in the thread.
Rooted Users (Non - Root Users scroll down below):
MR1 RUU
http://www.multiupload.com/KU7GSF2EY0
PG05IMG_MR1_no_hboot.zip - c64b4367086fff4f51ec3d5d766a0456
Bootloader (FLASH THIS LAST) FLASHING THIS WITHOUT SUCESSFULLY FLASHING THE ABOVE FILE WILL CAUSE A SECURITY WARNING
http://www.multiupload.com/26WG1UZCXR
abda920f3e159fb05c00d8c54a5b8768 - PG05IMG_hboot_1.4.0000.zip
Flash the above PG05IMG_MR1_no_hboot.zip to restore everything to stock + OTA BUT still will have the s-off bootloader.
Rename PG05IMG_MR1_no_hboot.zip as PG05IMG.zip, and flash through hboot (like in the root guide).
To restore the bootloader, rename PG05IMG_hboot_1.4.0000.zip as PG05IMG.zip and flash through the bootloader. DO NOT FLASH THIS unless you are absolutely sure PG05IMG_MR1_no_hboot.zip flashed to your device, without issue.
Now you are done, enjoy. If you screwed up, and got a security warning contact me, don't stress. Then again, don't screw up.
Non root users wanting to return to 1.12.605.6 (Stock, pre OTA) can continue below:
NOT FOR ROOT USERS
Taken from AndroidPolice: [Tutorial] How To "Un-Root" The HTC ThunderBolt And Return It To Stock. Please check the site out.
One of the most popular questions about rooting the ThunderBolt is how to undo the process and return to stock, which renews your eligibility for customer support. Well, here you go:
Instructions:
Please read the whole tutorial first, and pay attention to every detail. Note that your battery needs to be charged to at least 40% at the beginning of the process, and remember to check the MD5 sums of all downloaded files before diving in. As always, neither Android Police nor Team AndIRC are responsible for any damage this may cause to your phone, and, needless to say, returning to stock means you will no longer be able to use root apps like ShootMe and Titanium Backup.
First, download the following files:
Stock firmware (MD5 sum: 7141f5620f6128af77d50587e341f4b0)
exploits.zip (MD5 sum: 3b359efd76aac456ba7fb0d6972de3af)
Next, push exploits.zip and misc.img.
Code:
adb push misc.img /data/local/
adb push busybox /data/local/
adb shell chmod 777 /data/local/busybox
To gain root and flash misc.img:
Code:
adb shell
su
/data/local/busybox md5sum /data/local/misc.img
If the output is anything other than "c88dd947eb3b36eec90503a3525ae0de," stop and start over again.
Now let’s write misc.img:
Code:
dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
Rename "PG05IMG_Mecha_VERIZON_WWE_1.12.605.6_Radio_1.16.00.0223r_NV_8k_1.41_9k_1.64_
release_174685_signed.zip" to "PG05IMG.zip" before placing it on your SD card.
Finally, reboot into bootloader mode by entering the following command. Allow the stock firmware to flash.
Code:
adb reboot bootloader
You’re done – your phone should now be stock, S-ON.
Bookmarking this, just in case. Thanks, Jcase!
Looks like I'll be going back to Froyo for now. I believe the Sense in GB leak is older than the stock on the device.. plus.. camera doesn't work, weather in clock widget doesn't work.. quadrant score is pretty low.. As for now.. I don't see any solid reason to upgrade to GB.. (though I wish I did).. sigh!
http://forum.xda-developers.com/showthread.php?t=1082114
Follow that to return to stock from gingerbread
I am getting No Image or Wrong Image Error In Final Step. I downloaded Stock Firmware Twice but same issue!
Can anyone help me out? I am not able to return to stock. I have BAMF remix 1.6.3 installed and trying to get back to stock as i have to send this device back to Verizon for replacement. I tried everything..file name is correct....md5 sum is correct however in final step when i tried to load the stock FW the boot-loader says wrong image!!
i downloaded stock FW from every possible source but no different!
Please Help!
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
spjoneser said:
If I wanted to unroot and use pre ota software? Would I have to perform both procedures or is there a way to go straight to the pre ota with s-on?
Click to expand...
Click to collapse
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
jcase said:
Take the pre ota RUU, and make a custom ruu out of it without the hboot, and then proceed with the instructions in the first half.
Click to expand...
Click to collapse
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
spjoneser said:
First of all Jcase, thanks for the time, I know it's valuable to the community.
So just so I'm clear.... All I need to do is remove "hboot_7630_1.04.0000_110223.nb0" from the pre ota ruu or is there more to be altered than just that?
And if that's all I have to do is flash those seperate, could you tell me briefly why you could not just flash all at once? Would it not flash the rest of it if the stock hboot was installed first?
Click to expand...
Click to collapse
Yes, because some radios seem to cause the files to flash in different orders, doing it like this keeps me from having to make multiple versions.
Sent from my LG Revolution
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Androidfreakz said:
Question I have used the oneclick program to get ride of the NV recovery but I think im still rooted because I still see my superuser program on my stock 2.2. Can I just download Rom Manager and use clockwork Recovery to flash the Zips? I have to stock recover now which just formats the phone pretty much.
Click to expand...
Click to collapse
You need to consult the author of the program, because I don't know what it did, I can't support their application.
Sent from my LG Revolution
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
AnalyzeFaith said:
This flashes EVERYTHING back to stock? I have my boss tripping that his phone is bad after rooting it. I want to know if this reverts the baseband back to stock too?
Click to expand...
Click to collapse
Reverts everything back to stock + OTA
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Droid_ALM2ND said:
Can I still use these steps to revert to stock after flashing the leaked Gingerbread Radio?
Click to expand...
Click to collapse
yes
1234567890
droidrev71 said:
i am rooted and so i followed directions for first file and lost root.. so for the second file(its been forever since rooting) do i run adb commands( like step 6 for rooting) for install or can i use fastboot and bootloader? Does the second file bring root back?
Click to expand...
Click to collapse
Of course you lost root, this is for restoring to stock. It removes root.
jcase said:
Of course you lost root, this is for restoring to stock. It removes root.
Click to expand...
Click to collapse
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
droidrev71 said:
well the good news is it works..the bad news is i didn't realize it was back to factory stock (like out of the box) which is very useful.. my bad.. so how do i install the bootloader file?
Click to expand...
Click to collapse
if you are S-off, you can just flash the MR1 upgrade from the root guide, otherwise you have to do a complete re-root.
For those of you wondering why the S-OFF feature was worth your extra time to update, this is a prime example of why S-OFF kicks royal behind.
So here is the situation I was having. Friday morning, T-Mo showed me some love and sent me the Gingerbread update. I didn't have my morning coffee so I wasn't thinking strait and authorized the update. I forgot that it would probably interfere with good ol' ClockworkMod Recovery. Sure enough, it did. So, after the OTA failed due to the recovery, I haven't been able to get T-Mo to show me some OTA love again.
However, I had previously invoked the S-OFF feature when it was discovered how to.
After following the guide at http://forum.xda-developers.com/showthread.php?t=1202060 I found myself with a G2 using stock recovery and bone stock Gingerbread (S-OFF still invoked).
After some thought, I decided to do the following:
Flash ClockworkMod via the bootloader screen, and flash SU via the ClockworkMod screen.
Note: You can only do this if you have S-OFF! And since my guide writing skills are not so pristine, I'm assuming you have some sort of working adb/bootloader/recovery knowledge.
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Thanks!
It sounds like you started where I am: Clockwork Mod, S-OFF and stock Froyo 2.2.
Q. How did you follow the steps in the thread to get onto Gingerbread? Did you remove ClockworkMod? If yes, how did you revert to stock recovery? This is the step that I'm caught on, and can't find a thread regarding. Thanks!
Edit to add:
Did you unroot the phone using these steps?
If so, were you at all scared about the warning regarding PC10IMG.zip?
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Okay, so just to verify, you flashed CWM recovery while running the GB update? When you adb shell you open a # prompt? I've been gfree s-off'd since I got my phone so even with the leak or otherwise I've been able to just reflash the stock 1.19/1.22OTA and reroot it but I didn't think to try flashing cwm while it's stock gb'd....so tempted.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
So I sit down to write up a quick guide this morning and what do I find? Nicely done. Couple of points I wanted to add to why this works -
This method fixes the things that the OTA breaks for root: New stock hboot and stock recovery are flashed and on the rom side it wipes /system/xbin which breaks the su symlink.
Flashing the PC10IMG above fixes the recovery.
Flashing the superuser package reinstalls Superuser.apk, the su binary and fixes the symlink to xbin.
But, still not hboot-eng so your fastboot options are limited.
When I did this I had replaced the DZ engineering hboot.img in rmk's package with the G2 engineering hboot.img and edited android.txt for the new G2 build. This allows you to take care of both in once flash.
Hope this is useful to someone and thank you for saving me from writing a guide!
8/27/2011 Edit:
Realized ro.secure=0 so I repacked the stock boot.img from the 2.3.4 PC10IMG.zip with the below changes to default.prop. This allows use of the "adb remount" so files can be pushed to system folders without needing to go into terminal and mounting rw.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Modified installation instructions for full root:
Flash the PC10IMG.zip with the G2 engineering bootloader in this post
Flash the superuser update.zip in the OP
Extract the attached boot.img to the platform-tools directory
Remove the PC10IMG from your sdcard and reboot into bootloader
Select fastboot
Enter the following command in terminal or cmd:
Code:
fastboot flash boot boot.img
fastboot reboot
Kind Regards,
Kevin
zkid2010 said:
Okay, so just to verify, you flashed CWM recovery while running the GB update?
Click to expand...
Click to collapse
Yes. Just flash the PC10IMG and you have clockwork recovery again. However, you absolutely need SuperCID set while in froyo or this does not work.
Kind Regards,
Kevin
Confirm Here that it works...
Root and S-OFF
Gingerbread OTA 2.3.4
Thanks Guys for your help!
Flawless!
This worked flawlessly!!
I admire you so much for figuring this out!!
Thank you so much!
HELP!
sort of noobie here..
so i just updated my g2 to 2.3.4 following http://forum.xda-developers.com/showthread.php?t=1202060
and now i want to perm root my phone and overclock it but im having troubles.
1. how do i get clockworkmod installed? i know you can install this from rom manager but it requires root. right?
cause you said.. "Just flash the PC10IMG and you have clockwork recovery again"..
i tried flashing the PC10IMG.zip but got an error and says aborted.
any help please?
thanks in advance
If you are already on 2.3.4 and had not previously rooted then this thread will be of no use to you since your G2 does not have SuperCID (again, read the wiki.)
You will need to downgrade back to froyo (other threads on this and links in the wiki.) Once rooted, then install one of the rooted stock roms in this forum or follow this guide to reinstall the recovery and superuser (hboot optional.)
Hope that gets you going in the right direction.
Kind Regards,
Kevin
Sent from my T-Mobile G2 using Tapatalk
G2 Problems??
Hi, how can i get S-OFF on my g2 since it seems i can not generate a beta key from the revolutionary website cause g2 it's not in the drop down list, don't know what to pick and i want to be able to have my g2 rooted with android 2.3.. can somebody help me please?
Thanks.
Revolutionary is not available for the Desire Z/G2. Have you flashed the leaked 2.3.3 and trying to root? PM please.
Hey I notice most of the people in this thread are Americans - would this method work for the DZ or is it just for the G2?
Sorry if this is a noobish question.
Not a noob question, this one is new for me too. Fundementals are the same, process would be the same. I don't know if there is any issue using a PC10IMG with the info for a G2 (contained in the file called android-info) so may need rebuild one modified with DZ information.
Proceed with caution and do not do anything you are not 100% sure about.
Sent from my T-Mobile G2 using Tapatalk
I'll hold off on confirming the update in that case! I'm still on stock firmware, didn't apply the update from March either. When I've read enough to be confident on how to perma-root the current firmware I might risk following the method in this thread. Then I'll post back to let you know if it works on the DZ.
My DZ came with 1.34 firmware, I rooted it on this firmware. I accidentally upgraded it and am now on the OTA gingerbread ROM. Is this method suitable in this situation or do I require to flash a rooted stock ROM for this method to work.
Accidentally manually applied the OTA? Should work, you have a G2 now!
Sent from my HTC ThunderBolt using Tapatalk
Is there any newbie guide for how to do this? From getting Clockwork on there to getting this rooted 2.3.4 on. I have a rooted 2.2 with S-OFF right now, stock. Just don't really know what to do from this point on.
How to is in the OTA thread (which needs a helping of Iron Fist.) Come back here when ready to re-root.
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
**** Im at the step above finally lol this is my first root and I had to downgrade, man Ive been doing this for hours and hours. My brain is fried LMAO **** I currently have my G2 with S-OFF and a stock Gingerbread 2.3.4. I have the PC10IMG.zip and su.zip in the root or directly in my sdcard. In no folders im trying to say... I reboot into the bootloader. The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
Well when I do it it doesnt ask me to "flash the recovery" it says "Parsing....(SD ZIP)
(1) RECOVERY
Do you want to start the update?
<VOL UP> YES
<VOL DOWN> NO
I accept the update by pressing vol. up. It comes back and says Update comeplete... - OK
Press Power to Reboot
I reboot and get into clockworkmod it says click "install zip from sdcard" I click it and a little hat appears but it doesnt do anything from there. I let it set a couple of min but still nothing... I have to pull battery out to get it to reboot. help pls....
Sean...
This is not my work, and I can not vouch if it works or not as I am a US Cellular customer and don't have a working version of 4.4 on my device. This was posted on Reddit. Link and entire post to follow:
Video "proof":
http://www.youtube.com/watch?v=NP9WXLIzhTY&feature=youtu.be
http://www.reddit.com/r/MotoX/comments/1r3y30/root_achieved_for_44_kitkat_on_my_dev_edition/
------------------------------------------------------------------------------------------
[–]8bitremixguy 1 point 33 minutes ago*
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)-> http://forum.xda-developers.com/showthread.php?t=2534850
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues. After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (use the motorola fastboot binary)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
If you do this correctly you will regain root.
------------------------------------------------------------------------------------------
Again, don't kill the messenger! I figured I would pass this information along.
i.Design said:
This is not my work, and I can not vouch if it works or not as I am a US Cellular customer and don't have a working version of 4.4 on my device. This was posted on Reddit. Link and entire post to follow:
Video "proof":
http://www.youtube.com/watch?v=NP9WXLIzhTY&feature=youtu.be
http://www.reddit.com/r/MotoX/comments/1r3y30/root_achieved_for_44_kitkat_on_my_dev_edition/
------------------------------------------------------------------------------------------
[–]8bitremixguy 1 point 33 minutes ago*
I want to first say that I did not figure out this method on my own, I saw it on Google+ via Matthew Pierce and modified it to make it easier to follow
Second, do not try this on a device with a locked bootloader. You need the unlocked bootloader to do this.
You'll want to first download these 2 things
1) Superuser zip to be installed in recovery (from Chainfire) -> http://download.chainfire.eu/366/SuperSU/BETA-SuperSU-v1.72B.zip
2) New TWRP for 4.4 KitKat (from Hashcode)-> http://forum.xda-developers.com/showthread.php?t=2534850
Here's the method to get root:
1) let the system fully install the 4.4 Kitkat ota and reboot. Make sure you are on the first OTA before you try to install the KitKat OTA, otherwise your phone could have major issues. After it installs, do not do anything else, let it boot into android.
1b) Take the SuperSU installable zip and place it onto the internal storage
2) reboot phone to bootloader.
3) install Hashcode's TWRP using mfastboot flash recovery twrp-2.6.3.1-ghost-4.4.img. (use the motorola fastboot binary)
4) reboot device to recovery, do not boot into android before this step!
5) go to install and find then select BETA-SuperSU-v1.72B.zip
6) Boot back into android, and if needed, go to the Play Store and install SuperSU from Chainfire
7) enjoy root!
If you do this correctly you will regain root.
------------------------------------------------------------------------------------------
Again, don't kill the messenger! I figured I would pass this information along.
Click to expand...
Click to collapse
I tried yesterday and it works flawlesly, just to remenber that you need an unlocked BL , basically you will gain root on any unlocked boatloader as you can install TWRP or CWM
unlocked bootloader </thread>
jcase said:
unlocked bootloader </thread>
Click to expand...
Click to collapse
Ha. Classic.
I wasn't aware that this was the case with unlocked bootloaders. I just came from my S3 where an unlock method was readily available when I purchased the phone. In either case, I think this information is useful for noobs (such as myself) if unlocking the bootloader is an option (like myself).
Also, I hope you're having luck with the new root method for non-dev variants, jcase.
Fastboot
beelzebu said:
I tried yesterday and it works flawlesly, just to remenber that you need an unlocked BL , basically you will gain root on any unlocked boatloader as you can install TWRP or CWM
Click to expand...
Click to collapse
Where can I find info for installing Motorola fastboot files for KitKat?
downloading the tmo retail 4.4 from motorola has the necessary files.
Fastboot
beelzebu said:
downloading the tmo retail 4.4 from motorola has the necessary files.
Click to expand...
Click to collapse
I am looking for the fastboot command file to flash the TWRP image. Can you please provide me with the link.
Thanks.
rooting a phone with an unlocked bootloader is something a toddler could do
Fastboot
BaconDrips said:
rooting a phone with an unlocked bootloader is something a toddler could do
Click to expand...
Click to collapse
Agree.
Usually flash using the fastboot command in the SDK-platform-tools.
Comments suggest that that will not work and I need mfastboot, motorola binary. Unfamiliar with that one.
Appreciate a constructive comment. We all have to start somewhere.
Thanks.
This is merely a guide, I do not take credit for any methods or apps listed below. I am not a developer. The great people working on these apps and methods deserve all the credit and your donations, so please disparse accordingly.
BIG THANKS to @iKrYpToNiTe, @jcase, @geohot who worked on these apps. Also thanks to @mschumacher69 for some constructive discussions.
YOU AGREE BY PERFORMING ANY OF THE ACTIONS BELOW THAT I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE. EVERY DISCLAIMER STATED ON THE LINKS PROVIDED IS STILL 100% VALID.
A RECAP OF THOSE DISCLAIMERS IS THAT YOU WILL VOID YOUR PHONE'S WARRANTY AND NOONE ELSE BUT YOURSELF ARE RESPONSIBLE IF YOU DAMAGE YOUR PHONE!!!
I decided to compile a root guide for the Cricket variant of the Moto G falcon xt1032 running 4.4.2 (may work on other variants as well, not sure). I obtained full, permanent root with philz touch recovery (but it would work for any other recovery you may choose to use).
THIS METHOD DOES NOT REQUIRE A COMPUTER/PC/MAC/LINUX USB CONNECTION
1. Enable USB debugging
2. From the setting tab "security". Check the " unknown sources" box, so you can install apk outside of play store
3. In addition to all things below, you will need a file explorer. I find es file explorer to be the golden standard, but your preferred file manager will do
4. This Link below is for you to install towelpieroot.apk
http://forum.xda-developers.com/moto-x/themes-apps/root-towelpieroot-motorola-devices-t2825059.
The version 1.2 supports the xt1032 falcon. Big thanks to @iKrYpToNiTe for adding support for the Moto G! You will need this temporary or "tethered" root before you go to the next step, which is unlocking the bootloader with this app called Sunshine (link to thread given below). Towelpieroot is buggy at times, but if it doesn't work the first time, try a few more. It WILL work.
5. http://theroot.ninja/
Note that running Sunshine is not free, but the $25 is well spent! Just so you know, Sunshine will NOT charge you if the process fails.
6. After the bootloader is unlocked, UNINSTALL towelpieroot. This is important in order for you to proceed to the next step.
7. Once you unlock the bootloader, you need to run towelroot (link below)
https://towelroot.com/
This step will grant you full, permanent root. Tap on the "welcome to towel root V3" three times, then you should see a box where you can modify the modstring. By experimentation and trial, I found the modstring 1337 0 0 0 4 0 to be the one. Click "Make it ra1n" and you should have permanent, full root privileges!!!
8. Download your favorite root checker to verify root access!
9. Go to play store and install SuperSU, and do any necessary updates.
10. Go to play store and install busybox and do all necessary binary updates.
11. Go to play store and download a terminal emulator. This will aid you in flashing your recovery.
12. My personal preference is Philz Touch recovery, but I think it it fair to assume that any compatible recovery of your choice is appropriate to flash with this method (link below)
http://forum.xda-developers.com/showthread.php?t=2639583
Download the latest .IMG from the OP
13. Before you flash you may want to back up your stock recovery.
Open the terminal emulator.
(do not include quote marks, only what's inside them, including spaces)
Type "su" and hit the ENTER key
This will get you superuser access
Type "dd=if/dev/block/mmcblk0p32 of=/sdcard/stock-recovery-backup.img"
This will create a backup of your current STOCK recovery.
14. Now ,using your file manager, go to the philz touch recovery .img file you just downloaded and rename it into "recovery.img", then move it to the sdcard folder (storage root folder)
Note: there you should also see the backup recovery file "stock-recovery-backup.img" you just created
15. Open the terminal emulator
Type "su" to gain superuser access
Type "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p32
16. THAT'S IT!!!
Verify by powering off your phone, hold volume down and power button for 5 seconds, select recovery and you should have Philz touch recovery in your phone.
NEXT LOGICAL STEP WOULD BE TO BACKUP YOUR STOCK FIRMWARE IMMEDIATELY!
BE MINDFUL WHEN YOU HOP BETWEEN ROMS THIS PHONE HAS ONLY AN INTERNAL STORAGE, SO BE CAREFUL WHAT YOU FORMAT
Other than that, whoohoo!!!!
NOTE: ACCORDING TO SOME DEVS I HAVE COME ACROSS ARE TELLING ME STEP 7 IS NOT NECESSARY. YOU CAN TRY SKIPPING IT. UNFORTUNATELY MY BOOTLOADER AND ROOT ARE IN EFFECT, THEREFORE I CANNOT VERIFY THIS. YOU COULD TRY[emoji3]
Please, when you need app-specific support, you may get better answers in the respective forums, but don't be discouraged posting questions here. It took me great effort finding a way to root without a PC, and although i am not a developer, I have stumbled in enough obstacles to be of some assistance
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
mschumacher69 said:
Once you unlock ur bootloader, u don't need exploit apps such as towelroot to gain root, all you need is a custom recovery such as twrp. Once you flash it and reboot from it, it will tell you that you're not rooted, do u want to flash supersu to gain root access? Swipe to intall supersu and u're rooted...
Click to expand...
Click to collapse
Yes that is true if you wanna fastboot via USB, which means connecting the phone to a PC. I was under the impression that I could not flash a custom recovery from the stock one. I have been struggling to gain root because of non-access to a computer. It is a little more lengthy but I find this to be the only no PC guide around, since I've been looking for one for 4 months now. And most certainly I would not be able to flash a recovery from the terminal emulator if I did not have su.
Towelpieroot only gives a tethered, temp root with no r/w privileges to system. It would make it impossible to flash a recovery from the terminal without gaining full root. This is why you need to run the original towelroot with the modified modstring.
REMINDER: THIS METHOD DOES NOT REQUIRE A USB CONNECTION WITH A COMPUTET. ITS ALL DONE ON THE PHONE.
XT 1032 Falcon from Cricket GSM 4.4.2 stock
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
lmf said:
Thanks for the guide. I ran towelroot 1.2 and it crashes my phone ;( and v3 says it's not compatible
Click to expand...
Click to collapse
Towelpieroot is buggy (the dev states in his post). I had to try the process numerous times. What i think may work (or may have worked). Is you have to make sure that before running towelpieroot again youbhave to clear it from the recents. What i have done was clear it from recents, uninstall. Reboot phone. Install and run again. Once you get temp root you can continue the process.
On towelroot v3. It will say your device is not supported. Tap on "welcome to towelroot v3" twxt three times and a modstring modification box will appear showing numbers. Input the modstring posted above in the OP "1337 0 0 0 4 0" (with the spaces). Then it will give you root
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
BBobby said:
Note: According to some devs i have come across are telling me step 7 is not necessary. You can try skipping it. Unfortunately my bootloader and root are in effect, therefore i cannot verify this. You could try. [emoji3]
THIS NOTE ADDED TO THE OP AS WELL
Click to expand...
Click to collapse
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
mschumacher69 said:
It is definitely unnecessary. Once you unlock ur bootloader, all you need to do is flash custom recovery and it would flash supersu for u which would give u root...
Towelroot uses an exploit to root, exploits are only needed on a locked bootloader. Unlocked bootloaders don't need exploits to be rooted...
Click to expand...
Click to collapse
Would it be OK to download super su from play store directly?
BBobby said:
Would it be OK to download super su from play store directly?
Click to expand...
Click to collapse
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
mschumacher69 said:
You wouldn't be able to download it directly. Once you unlock the bootloader, you flash custom recovery such as twrp, then when u reboot from twrp (or any other custom recovery), it would tell you that you're not rooted, would you like to install supersu? Swipe to install it and you're rooted. Then you can update supersu from the play store.
Click to expand...
Click to collapse
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
2. Is it bad to just run towelroot V3 and gain permanent root in less than a minute, then just download super su and continue?
I just posted what has worked for me. I am thankful for your input and persistent suggestions. But like I said it has worked for me the way it is described in the OP. I just don't think it is necessary to fix what is not broken.
Click to expand...
Click to collapse
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
mschumacher69 said:
1. Yes you can flash a custom recovery via a terminal emulator, but you would need root to be able to do it without using a PC.
2. I wouldn't say bad, it's rather unnecessary especially that it uses an exploit to gain root. You wouldn't know what unnecessary changes it makes to your system in order to be able to gain root.
Click to expand...
Click to collapse
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
BBobby said:
The guide is about NOT using a PC. Its in the topic, in the OP, in my posts... Then yes, its necessary to gain some sort of root (permanent, in the towelroot case) to run the terminal emulator.
Two birds with one shot.
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Click to expand...
Click to collapse
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
mschumacher69 said:
Fair enough, but I don't see why you wouldn't want to use a PC. It's safer if u use a PC because u wouldn't be using any exploits...
Click to expand...
Click to collapse
Do you even read the posts? I have not had a PC or access to one (yes, people like me exist). I have looked for months on end and once I came across towelpieroot it all became possible. Then jcase released sunshine and that all put it together in a working method. This is the collection of hour of searching. If anyone like me does not have PC access it is still possible. But I wouldn't want others to have to go through that frustration
Moto G (XT 1032) from Cricket. Unlocked Bootloader, Rooted, Stock ROM (4.4.2) with Xposed tweaks
Thanks for the useful guide.
Once you do all of this what can be done . Does this mean the device is carrier free or just allows to install any variant of android on it.
Also even after doing all of these things how one can activate it on a different network than it is bought to be used on.
Sorry i am newbie to flashing software.
Thanks
Mars
This is a guide to root this device. That means you have access to the operating system files. By getting this access it allows you to modify the system in many ways. It also allows you to install custom ROMs. Gaining root has so many uses I cannot list here.
But no, this is not a carrier/SIM unlock.
How about the 4.4.4 cricket XT1046 seems to be impossible at this point?
When I get to the step on gaining temporary root it just keeps loading and loading and it never gives me root.. Like I went on and off multiple times and it still won't work
BBobby said:
But my questions continue to be:
1. How do I flash a custom recovery from the stock one?. Will the terminal commands still be effective? Or an .IMG file flasher app like rashr will be effective without initial root?
Click to expand...
Click to collapse
Rashr needs root to flash images and zips
Edit: I didn't saw that you already have been answered
Here is a dedicated thread for Q&A and general info on OTA's for the Motorola Nexus 6. Please feel free to discuss all things OTA related and ask any questions you may have.
*Bootloader lock status has no effect on OTA pass or fail.*
To summarize, an OTA (Over The Air) is a software update pushed to nexus devices directly from Google. You will receive a notification when one is available for your device. The files are generally large in size and downloading via WiFi is recommended.
With Android 5.0 and up, OTA updating has changed significantly from previous versions. In the past, you could be stock, rooted, with stock recovery and OTA's would flash successfully. This is no longer possible in lollipop. Absolutely no system or kernel modifications can be present in order for the OTA to flash. This means that if you have unencrypted the stock kernel, the OTA will fail. The phone must be in a "out of box" state.
As always, you are not required to take the OTA as there are other options available. If you are already rooted, unlocked and using a custom recovery, you can use an updated custom ROM provided by the amazing development community here at XDA. Factory images are released by Google prior to OTA's being pushed out so most, if not all, of the custom ROMs are updated before you'll even see an OTA notification. Also, there are stock, rooted ROMs available as well.
*Factory images*
You can always update or return to stock via factory images direct from Google. Link to this guide provided in post #2
*Sideloading*
Another feature available to use is the sideload option. With the use of a few simple ADB commands, you can apply the OTA via sideload. Sideloading will require connecting to your PC and a working ADB/fastboot connection. Directions for sideloading are in post #3.
*Updating while rooted, unlocked, and having a custom recovery via fastboot*
This is quite simple with basic knowledge of fastboot/ADB. Download the factory image, extract the system image and flash with fastboot. Then flash TWRP and SuperSU again. You can also flash the boot image if desired. However if you are unencrypted, this will encrypt the device.
Many, MANY thanks to the development community, themers, modders and other talented people here at XDA.
Thanks @El Daddy for guidance and advice.
Helpful links:
*Please hit the thanks button for the OP's of the XDA threads below if the threads were helpful in any way.*
Beginners guide:
Thanks @xBeerdroiDx
http://forum.xda-developers.com/showthread.php?t=2948481
Setting up and using ADB and fastboot:
Thanks @rootSU
http://forum.xda-developers.com/showthread.php?t=3006500
Factory images installation instructions:
(Including the fastboot flash method for flashing individual images):
Thanks @Mr hOaX
http://forum.xda-developers.com/showthread.php?t=2954008
OTA files:
Thanks @oldblue910
http://forum.xda-developers.com/showthread.php?t=2906493
*For rooted/unlocked users only*
OTA zip files and radio files (TWRP flashable):
Thanks @Q9Nap
http://forum.xda-developers.com/showthread.php?t=3066052
Radio thread (fastboot flashable):
Thanks @zephiK
http://forum.xda-developers.com/showthread.php?t=2969380
Directions for sideloading
*These directions are based on Android SDK, Windows OS and a 100% stock Nexus 6*
This is just a simple, well known, user guide to using sideload.
Make sure your SDK is updated!
Download the OTA file to your PC, rename it to update.zip and transfer into the platform-tools folder of your SDK.
Connect your Nexus to your PC with your OEM USB cable.
Hold shift and right click on platform-tools folder and select open command prompt here.
Type: adb devices
If your serial number comes up, you are good to go. If not, check out your drivers in device manager. You may need to manually point your PC to their location. Also, you may need to uninstall any other Android drivers that are not associated with your Nexus.
Type: adb reboot bootloader
Select recovery mode from your phone using the volume down key. Once you've highlighted recovery mode, press power to select it.
It looks like a restart but the the dead android appears with red exclamation point. When that happens, hold power button and press volume up once.
Once in recovery, use the volume down key to select apply update from adb and push power to select it.
When your phone says now send file,
type: adb sideload update.zip
If all goes well, you'll see things progress and your Nexus will restart when complete. If you encounter the device not found error after beginning, unplug your USB and reconnect. I had to do it twice, but it works.
How do we install ota zip
if you are running stock you should be able to use wug toolkit and have it flash this zip file
What about stock-ish? I'm assuming since I'm rooted with my device unencrypted, that I can't flash this, right?
Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.
knitler said:
Flashing now. Will post back when done.
EDIT: Flash went perfect ^.^ 5.1 is all set.
Click to expand...
Click to collapse
Were you completely stock?
Sent from my Nexus 6 using XDA Premium 4 mobile app
instructions for mac
http://www.androidcentral.com/how-manually-upgrade-your-nexus#slide5
I have a modded boot image and it failed to install. Guess ill have to nuke and start over to get this OTA in place.
http://www.androidpolice.com/2015/0...gs-android-5-1-ota-roundup-for-nexus-devices/ I just want to flash the radio but it looks line it's 20 MB bigger than the last
Is anyone creating a flashable zip that works with TWRP?
@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).
I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?
I think I'm on the same situation as edif30
Stock image
rooted
unlocked bootloader
TWRP recovery
How can i sideload w/o losing root?
edif30 said:
I probably already know the answer but here is my situation... I am on the stock image but unlocked boot loader, rooted, and twrp recovery. The only way I can remain stock and not lose my current state other than root and a few apps that rely on root is to... Unroot, relock boot loader and put back stock recovery... Then OTA or side load? Theres no other option right?
Click to expand...
Click to collapse
You could flash the 5.0.1 factory image except for the userdata.img and radio.img and side load the OTA. Or you can wait for the 5.1 factory image and remove the "-w" from the flash-all script.
You will lose root and TWRP. but your data will remain intact.
So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?
stevexyz0 said:
So I'm all stock, unrooted, with a still-locked bootloader. I can flash the OTA without unlocking and without losing my data, right?
Click to expand...
Click to collapse
Yep, just use ADB sideload.
So I had stock 5.0.1 with a custom kernel. I flashed the stock boot.img from the factory image using TWRP and I unrooted from in the SuperSU app, so I should be stock all around except for recovery. When I try to flash the OTA in TWRP it gives the following error message:
Package expects build fingerprint of google/shamu/shamu:5.0.1/LRX22C/1602158:user/release-keys or google/shamu/shamu:5.1/LMY47D/1743759:user/release-keys; this device has google/omni_shamu/shamu:5.0.2/LRX22G/dees_troy01130854:eng/test-keys.
Any idea why TWRP would think I was running 5.0.2?
cam30era said:
@oldblue910,
Thank you very much. ADB sideload went flawlessly (completely stock 5.0.1 of course).
Click to expand...
Click to collapse
Mine too but how long did it stay on the GOOGLE screen before booting?