Database Users

1 click eris unroot?

is there a 1 click eris unroot app like the 1 click rooting app? i looked for an easy way to unroot my eris but cant find it... and the thread i did fidn that walked through how to unroot said that the files where deleted?

Personally, I have not had to do anything "fancy" to get my phone back to stock. I just flash using the RUU and I'm good to go. I just plug in the phone, power it on and let it go through the boot sequence as the RUU detects the current version of the software on my phone. I agree to let it flash the update to my phone and I'm back to stock.

flash the RUU? can you suply a link an where to get this and how to do it? thanks!

do a forum search for unroot

Here you go: HowTo: Flash Any Ruu
http://forum.xda-developers.com/showthread.php?t=726885

is there a way to unroot without SDK? thats what i need to use in order to make it so i can run any RUU correct? cuz the link i found for an RUU gave me an error i think cuz the fesion on my phone is higher then that of the RUU? i only have acces to my work comp for a while and cant put SDK on it...

I never had to do anything fancy through the SDK to go back from root. I just ran the RUU and was "good to go". Your mileage may vary.
Again, from my post I just managed to get my device recognized and rebooted properly by running the RUU while my phone was booting. It was able to detect my phone once it was at the boot animation past the Androids on skateboards.

wamsille said:
I never had to do anything fancy through the SDK to go back from root. I just ran the RUU and was "good to go". Your mileage may vary.
Again, from my post I just managed to get my device recognized and rebooted properly by running the RUU while my phone was booting. It was able to detect my phone once it was at the boot animation past the Androids on skateboards.
Click to expand...
Click to collapse
using the the ruu from searching... i plug my phone in and run the .exe from my computer and it sees my phone and goes through the steps telling me what version im on and what im going to and then strats to update and then tell me that the update is not suported?
this is what im using...
http://www.pcdphones.com/our-devices/products/46-adr6200vw

This will work I promise..
If you have s=off your good if your not s=off and you are s=on pm me and I will give you the file to convert your bootloader to s=off... So considering you are s=off all you need to do is flash the PB00IMG.zip file leaked version 3. You can easily find it by searching google or by going to grdlocks android file manager webpage. What it does is flashes through your bootloader like the old root method and it completely downgrades your phone, your kernel, your radio, puts you back to s=on, everything. As soon as the phone boots log in to google as normal and as soon as the phone connects to the server and your are signed in where your contacts start to sync you will instantly get an "OTA" over the air update notification to update your phone. You used to not be able to successfully update with the ota because the leaked version 3 matched the ota perfectly. Since then there has been radio updates etc. so now it is possible to actually update the phone. Once completed with the over the air you will have all the most recent software/firmware out right now for the Droid Eris and that's pretty much it, your good to go!!!!! Let me know if you have any questions!!!!! Good luck bro...

[Q] MyTouch 4G: HTC Glacier - Perm root/with recovery?

I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks

geronimo711 said:
I am new to the rooting scene and I am very eager to root my HTC Glacier|MyTouch 4G.
I am however hesitant because I cannot risk bricking my phone.
Advice on how to recover from brick and an easy to follow guide to perm-root.
Thanks
Click to expand...
Click to collapse
What is the end result you are trying to get to?
If you are wanting S=off so you can flash custom ROMs.
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/; do that and it will lead you to perma root the easy way.
if you are wanting s=off so you can have complete control over your phone, which will enable the possibility of a brick. including SuperCID, ./gfree and some other goodies...... But this will give you the option to severally screw up your phone including up to a 500.00 paper weight.
http://forum.xda-developers.com/showthread.php?t=858996
If you haven't screwed up the HBoot and the bootloader you can use this to get back to a factory spec.
http://forum.xda-developers.com/showthread.php?t=863899&highlight=level
But if this is your first android, and your first time rooting i would HIGHLY suggest doing alot of reading before you jump in head first. There are alot of people who have tried to do and get stuck. This phone is confusing once rooted with 2.2 ROMs and 2.3 ROMs and different recovery images you need to read and make sure you understand everything before jumping in feet first.

Temp root with visionary is the easiest and safest way, but gfree is pretty simple as well. The hardest bit is getting the drivers and ADB to work, and thats not overly difficult. (remember to use the command "ADB devices" to know if the drives are working) It just matters what you plan on doing, stock root or custom ROM.
There is really only two points that risk a hard brick, flashing the radio or hboot.
The gfree method does not require either, but you can flash the engineering hboot as optional.
The biggest thing with recoveries and ROMs is know that gingerbread based ROMs (like CM7) use ext4 file system and froyo ROMs use ext3. So it is important to use the right version of Clockwork recovery. Use v2.5.1.2 for froyo ROMs and v3.0 for gingerbread ROMs. Soon clockwork mod will support both on the same version.
Just read the instructions well and have all files downloaded and ready to go.
If you want to use gfree and a custom ROM, there is no need to get perm root on the stock ROM first. After the steps that get s=off, just run visionary as temp root with system r/w access and install ROM manager from the market, then use ROM manager to flash a new recovery. Reboot into recovery backup your stock ROM then flash a new ROM.
If you never touch the hboot or radio firmware, then at worse you can bootloop or soft brick the device. That can be fixed with varying amounts of work, depending on the exact issue.
Read and learn how the different parts work, learn how to use ADB and you will be better prepared.

newbie here
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?

ibnird said:
This is my first post. I would really appreciate anybody helping me out here. I can't seem to get any straight answers, or answers I can understand, anyway, so here goes.
I have an HTC Mytouch 4g. I did a temporary root (using the method at theunlockr.com) and uninstalled the monopoly app. I was going to uninstall a bunch of other stuff but I got nervous and did a factory data reset (in the SD & phone storage area). All of my marketplace apps reinstalled, which I thought wasn't supposed to happen, but anyway.... I did the volume down/power on and see now that my phone is GLACIER PVT SHIP S-ON. So my question is how to interpret the state that my phone is now in. Is it factory? Is it rooted? Will the T-Mobile OTA updates work? Why is the monopoly app still gone? Is my warranty voided?
Click to expand...
Click to collapse
Temp root is just that, temporary. It creates a copy of the essential files in the system partition that it runs from rather than the actual system partition. If you allow it r/w access, (an option you can choose when using visionary) it can uninstall apps that normally can not be. (and more, but causing big changes would require more work on your part)
Because it is temporary, there is no need to get nervous. Unless you are doing some major changes, ones that need a root explorer app or terminal emulator, then you can't really hurt the phone. Download terminal emulator from market and run it, then type in the super user command "su" (no quotes) then hit enter, if the cursor changes to a # symbol then you have root. (you may get a popup asking for root permission, choose to allow) If it works after a fresh reboot, you either ran perm root in visionary, or you have the option checked to temp root every reboot.
S-ON means that the bootloader security is still in place. You need it off to install custom software. While you can root the stock software with S-ON you can not install any software that has potential to brick your phone, so no need to worry at all. If you are really that worried, keep a copy of the stock software on your SD card. Make sure it is named PD15IMG and at any time you get nervous, you can boot into hboot (the bootloader) and it will run automatically. It will wipe your phone and return it to complete stock. The irony is, that flashing this stock image file does things that can brick a phone if it goes wrong. It flashes more than just the OS, it also flashes hboot and recovery as well, and if the process is messed up in anyway like loosing power at the wrong time, it can brick the phone.
Really as long as you make sure you have the phone charged and you follow instructions you should be fine. The only times you can brick a phone to the point it can not be brought back is when flashing hboot and the radio firmware. Both of which you would rarely flash. Hboot only needs flashed to the engineering version once (OEM testing/DEV version) and only if you choose to, as it is not required. The radio will only need flashed if an update for it comes out, and that isn't often, and it is rarely mandatory.
The chance of truly bricking your phone is not very high, unless you just can't follow the directions. Now you can put it into a bootloop or soft brick it. (bootup stuck on mytouch screen) But if you can boot the phone into hboot (vol down + power on) then you can fix it. Even if you can not boot into recovery (an option in the hboot menu) you can even fix that with a good hboot.

theres a video on youtube by mackster its awesome and it gives you all the links very easy to use.
it wont let me post the link but just search root mytouch 4g on youtube and it should be the first or second one.

Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?

ibnird said:
Thanks Marine and Tommy.
So with temporary root, as soon as I turned off and then back on the phone, it was back to its unrooted, original state, minus the T-Mobile application? Will I now get T-Mobile's Over the Air (OTA, right?) updates and not have a problem if I need warranty work?
Click to expand...
Click to collapse
Uninstalling an app will not hurt anything. OTA updates will still work fine. You can temp root and then perm root the stock ROM and revert easily. Heck, even perm rooting stock doesn't break OTA I believe.
Voiding the warranty is one of those grey areas. As long as you can revert to stock, then they will never know. Temp root does not void warranty at all, because you do not alter the system files. (unless you want to, and enable the ability to read/write system) Just uninstall terminal emulator and super user apps and there is no evidence.
The only time you might get caught, is if say the screen stops working, and you can not see to revert back. Though even then, just putting the stock OTA image on the sd card then booting up the phone in hboot will restore without needing to actually see anything. It does ask for confirmation to restore, just wait several minutes then hit the power button and it would do it on its own.
The set of circumstances needed to prevent you from restoring to stock, are rare. Basically a borked hboot or radio firmware, and you never need to touch those to get full root and custom ROMs. If you never touch them, the chance of issue is almost zero.

I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?

goldfish524 said:
I just got my mt4g and I am looking to root my phone for the following reasons:
apps2sd
remove bloatware (I want the app to be disabled and I don't want the icon in my app drawer)
use adfree
I don't want any custom roms and I'd like to keep sense ui.
Can anyone tell me if this is at all possible? I've read around and I know it's possible but I don't know about rom flashing and I'm confused as to whether or not I need to flash a custom rom? What's the point of a custom rom anyways?
Click to expand...
Click to collapse
You dont need apps2sd, as the mytouch 4g has Froyo installed, and you can move some apps to the SD card. Just go into settings-Applications-chose the applicaiton you want on your SD card, and look for "move to SD". If it's grayed out, then you cant move it.
Also download appfreezer from the market, and just "freeze" the bloatware. That's what I do, and it gets rid of those annoying looking apps they installed.

Question about clockworkmod
OK i just rooted my phone, flashed the rom, and installed all the goods... it works perfectly and looks great.
Ty for all the guides/ instructions.
My only question is about the clockworkmod. When I turn off my phone and plug it in to charge the recovery screen always appears when off and connected. Is this suppose to happen? Or is there a solution to this?
If there is a solution can some one post a link or provide instructions so it doesn't constantly boot to clockworkmod recovery.
Thanks.

I downgraded from the Official AT&T 2.2 update back to 2.1

I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb

I have done this and can confirm that this works
Thanks mate!

I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.

khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.

andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?

Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.

andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.

Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.

Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?

FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.

I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post

PM me if you want the process...

xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.

econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.

It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.

econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272

Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.

econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?

Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.

VZW Software Update inside

Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
It does "fix" the bootloader unlock exploit though
http://www.droid-life.com/2013/07/1...the-kernel-exploit-for-unlocking-bootloaders/

scoobaspeaz said:
Here is the Droid Razr HD software update. I have not tested it as I use CM 10.1 and have no interest in going back to stock. I found it on www.droidrzr.com in a forum post then shared it on my dropbox account.
I posted it on my Dropbox account so not sure how long it will last until the link is gone:
https://www.dropbox.com/s/d2x9vutel4vnqmm/Blur_Version.9.16.6.XT926.Verizon.en.US.zip
Click to expand...
Click to collapse
So, stock recovery to install this?

I would assume you would need to be 100% stock, including the recovery, to install this.

scoobaspeaz said:
I would assume you would need to be 100% stock, including the recovery, to install this.
Click to expand...
Click to collapse
hmm put it on my internal storage and its not found, I think stock recovery wants to see it on a sdcard.

If your boot loader is unlocked before the update, it should stay unlocked. You just will not be able to unlock with methods out there now.
Sent from my Razr HD using xda app-developers app

I received the OTA today on my Max HD. It was build 9.18.79.
Sent using xda premium

A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!

LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1

Thanks for the reply! A few more questions if you don't mind (would hate to do something wrong... like I did last time... luckily I was able to revert back to an original version and fix the install... sigh...):
4) With protecting root, I need the SuperSU Pro version, yes? To be able to use the survival mode, yes? Will Voodoo OTA Rootkeeper do the same thing? Is it possible to use both "to be sure"?
5) I have everything backed up with Titanium Backup. Should I bother getting the pro version and backing everything up using the cloud backup and hypershell? Or won't this matter since if root doesn't keep I won't be able to use Titanium Backup?
6) I also have performed the VZW Wireless Hotspot hack using SQLite. Am I going to have to undo the hack in order for the OTA update to work?
Thanks again for all your help!

Update - I decided to attempt the update and hope for the best. System update 9.18.79.xx updating from 9.16.6.xx.
I purchased the SuperSU Pro from the Play Store, and used the survival mode in SuperSU. I also used the Voodoo OTA Rootkeeper and protected root. I figured if one didn't work the other might... Voodoo worked to protect and re-install root access (not sure about SuperSU as I tried Voodoo first to restore root after the install).
I am unsure if the bootloader is still unlocked, but from what people have said there doesn't seem to be a reason to believe it is re-locked. I haven't tested it out to know for sure though.
It appears that the entire update installed correctly. No errors, and the baseband version was updated to the new radio (xxx.15P).
I did not undo the VZW Wireless Hotspot hack prior to installing the update.
Hopefully this post helps others out there.
My final question... what does updating the radio/baseband do exactly?

i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options

rodmc123 said:
i need help! i tried installing the update but i forgot i had TWRP.. so the update did not got installed, i rebooted the phone, but the OS tried to install the update again and inmediatly reboot the phone in recovery again .. then from recovery i flashed liquid smooth rom but i got stuck in the boot animation... my big issue is that my power button is broken! now i cant reset the phone to enter in fastboot mode.. i cant do anything... now my battery is totally drained and i cant turn on the phone (my power button does not work).. i can plug the usb cable and the led turns green. but i dont see any more options
Click to expand...
Click to collapse
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny

KachowPow said:
There are 2 different versions, depends on what System version you have of 4.1.2 on the XT926 only. The 9.18.79 version would indicate that your Systems version is 9.16.6 if this is not correct DO NOT FLASH. I am Rooted/Unlocked, if you take the plunge you must OTA Rootkeeper/SuperSU backup SU, as the update breaks Root> IF there is no backup of SU with the latest binaries. If you lose Root, there are a couple of ways to Downgrade. A common problem for those of us Root/Unlocked the Update FAILs at the end. Most of the Update goes through, however the new Radio does not go through, as of right now if you Update and your Baseband is VANQUISH_BP_100730.081.64.09P then you have the OLD radio, the new Radio is VANQUISH_BP_100730.160.64.15P.
Between the 2 OTA's these should match-up as either 9.16.6 = 9.18.79 or 9.16.9 = 9.20.1
Click to expand...
Click to collapse
So any idea how one might fix this?

LifeAsADroid said:
A few questions I haven't been able to find answers to (many threads have been started on this new update topic and I haven't found the answers I'm looking for yet):
1) I've heard that there are two versions of this update, 9.20.xx and 9.18.xx... Anyone know the differences yet? Is one version for phones that have been unlocked and the other for phones that are still locked? Is one version for XT925 and the other for XT926? I received the 9.18 version, I am rooted, unlocked, and have a XT926 phone.
2) Anyone with an already unlocked bootloader try and take the update? Do you remember which version of the update you took? Did it install correctly? Are you still unlocked?
3) Anyone that is rooted and unlocked try to take the update? Did it install correctly? Are you still rooted and unlocked after the update? Did you have to protect the root with either SuperSU or Voodoo OTA Root Keeper? If so, do you mind posting step-by-step instructions for protecting the root so the phone is still rooted after the update?
Thanks to all who can shed light on these questions!
Click to expand...
Click to collapse
I tried to take the 9.18.79 update I protected the root (I'm not unlocked) before I did so I also temporarily un-rooted (I've always been told to do this before and update) Now I an no longer rooted and it can't find any SU binary codes. Gonna have to flash back to 9.6.16 and try it again I guess or stay on 9.6.16 in order to maintain root for now. If you find a solution please share.

IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
I agree with Lenny. This same thing happened to me when I tried to take the liquid smooth ROM. Follow his instructions above. You'll lose all your pics, vids, files, etc. But at least you'll have a working phone again.

Went smoothly here
All my devices except this one are rooted and some are rom'd. I thought long and hard about whether to void this warranty but decided one day it would be out of updates from VZW and I would want to flash something. I have been denying the OTA for the last day so I figured now or never.
Here are the simple steps:
Download and install Moto device manager (for the USB drivers) here
Enable USB debugging in developer options on the phone
run motochopper here
run motoapocolypse here
install voodooOTA root keeper from Play and backup root
apply OTA
It went error free. The phone has the 15P radio update, unlocked BL and root.

larsdennert said:
It went error free. The phone has the 15P radio update, unlocked BL and root.
Click to expand...
Click to collapse
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?

bananapeapod said:
I want to confirm something, you unlocked the bootloader and then took the OTA and the bootloader remain unlocked (and stayed rooted due to root keeper)?
So the benefit to all this would be to get the new radio update?
Click to expand...
Click to collapse
Yes, the bootloader won't get locked again after it is unlocked. Moto would be shooting themselves having to reinstate warranties if they did that. Yes I wanted the option of flashing later becuase the ota will install sooner or later. I also want to stay on the upgrade path for now to have current radios.
I still have an Eris lying around that is long out of support but i have gb on it.

IDroidThere4Iam said:
My suggestion, let your phone charge a bit.
Once charged up, turn it on and get it into Fastboot. From there you can use the DROID RAZR HD UTILITY 1.21 (http://forum.xda-developers.com/showthread.php?t=2307439). In that utility option 1 will bring you back to complete stock ROM, option 2 will bring you back to a stock recovery. This will completely erase your phone.
This should at least give you a fresh functioning phone. If you want to try to keep your data or personal files, I'm not sure what you could load via fastboot to get yourself a functioning phone again (maybe just a kernel?).
As a side note, I used TWRP to load the update and my phone updated except the radios it seems. It sounds like the same thing happens with the stock recovery.
Lenny
Click to expand...
Click to collapse
that's what i want to do, but i cant because my power button is broken! so i cant enter to fastboot mode without the power button.. i will have to open my phone and try to fix the power button myself.

Just to make a point and to clear up any confusion, this Update will not lock the Bootloader. If you have an Unlocked Bootloader then you will have an Unlocked Bootloader after the update, regardless if it fully works or not, and even if you lose Root, the Bootloader will still be Unlocked. If Root is lost with an Unlocked Bootloader, I suggest downgrading through an FXZ of either 9.16.6 or 9.16.9 and restore Root.

Updating while rooted clarification.

My phone is currently on version 1.19 and I have not had the time to update the phone. But before I do, I just wanted to clarify a couple of things.
First is that at this time turning s-on and applying the OTA update will cause me to lose the ability to go back to S-off unless I send my phone to Jcase again. (Just wanted to make sure this was still the case as it would be the easiest for me.)
Which brings me to my main question. All I have to do to update to the new version is renaming the RUU correctly, put it on my micro sd card making sure that it is formatted to fat32 and reboot the phone. At this point go into TWRP aaaand I’m not sure about the next part. If I was a betting man I would say install, select storage find the RUU and then hit the install image button. Am I correct in this assumption? And I am aware that flashing 2.41 will erase my data and force me out of root but will keep my S-off status.
I know how to fix software issues when things break on computers, but put a phone in my hands and I get extremely nervous that I might brick something. I know it is not having the experience with phones compared to computers and fixing OS issues on a phone is through recovery, but it still scares me a little. Any and all help is greatly appreciated!

WS-99 said:
My phone is currently on version 1.19 and I have not had the time to update the phone. But before I do, I just wanted to clarify a couple of things.
First is that at this time turning s-on and applying the OTA update will cause me to lose the ability to go back to S-off unless I send my phone to Jcase again. (Just wanted to make sure this was still the case as it would be the easiest for me.)
Which brings me to my main question. All I have to do to update to the new version is renaming the RUU correctly, put it on my micro sd card making sure that it is formatted to fat32 and reboot the phone. At this point go into TWRP aaaand I’m not sure about the next part. If I was a betting man I would say install, select storage find the RUU and then hit the install image button. Am I correct in this assumption? And I am aware that flashing 2.41 will erase my data and force me out of root but will keep my S-off status.
I know how to fix software issues when things break on computers, but put a phone in my hands and I get extremely nervous that I might brick something. I know it is not having the experience with phones compared to computers and fixing OS issues on a phone is through recovery, but it still scares me a little. Any and all help is greatly appreciated!
Click to expand...
Click to collapse
Having s-off doesn't prevent you from taking an OTA, so don't bother going back to s-on. Having a modified system (e.g being rooted) or having twrp are things that would block the OTA. And yes, if you're s-on and you update to Nougat, you're screwed.
To answer your question, you got the RUU steps sorta right, just that you don't flash the RUU from twrp, but rather from Download mode. With the correct and properly renamed ruu on the root of your sd card, boot into download mode (hold vol down and power during bootup), and you'll be promoted to begin the procedure.

Tarima said:
Having s-off doesn't prevent you from taking an OTA, so don't bother going back to s-on. Having a modified system (e.g being rooted) or having twrp are things that would block the OTA. And yes, if you're s-on and you update to Nougat, you're screwed.
To answer your question, you got the RUU steps sorta right, just that you don't flash the RUU from twrp, but rather from Download mode. With the correct and properly renamed ruu on the root of your sd card, boot into download mode (hold vol down and power during bootup), and you'll be promoted to begin the procedure.
Click to expand...
Click to collapse
Dang, so close! Thank you for your help! And once again, just so I understand correctly, the 'root' of the sd card is the top level directory, right? And to gain root access back will that require sunshine?

WS-99 said:
Dang, so close! Thank you for your help! And once again, just so I understand correctly, the 'root' of the sd card is the top level directory, right? And to gain root access back will that require sunshine?
Click to expand...
Click to collapse
Yes, root of sd card is top level.
Since you're already s-off (that's the case right? If you're currently not s-off don't update yet!), you won't need sunshine to root. After running the ruu, just flash TWRP, root and be on your merry way.
Also look into making an untouched system backup before you root, which you can restore next time there is an ota available so that you won't need to ruu.
Good luck.

Tarima said:
Yes, root of sd card is top level.
Since you're already s-off (that's the case right? If you're currently not s-off don't update yet!), you won't need sunshine to root. After running the ruu, just flash TWRP, root and be on your merry way.
Also look into making an untouched system backup before you root, which you can restore next time there is an ota available so that you won't need to ruu.
Good luck.
Click to expand...
Click to collapse
Correct, I am already S-off. You guys are the absolute best! Thank you so much for your help!

WS-99 said:
Correct, I am already S-off. You guys are the absolute best! Thank you so much for your help!
Click to expand...
Click to collapse
No worries bud.