Database Users

Main Version Is Older! Update Fail! Message

Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate

Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.

I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.

jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?

xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?

try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.

jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!

xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.

g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?

xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.

I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.

It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0

Rooting OTB 2.1 Eris

I have now Rooted Two 2.1 Eris the last few days. I dont know if this has been covered, I did a search and honestly searching here is a little fetch.
This is a place holder.
POST here if you want to know how to root 2.1 or post here and let me know if its already been known how to root.
Here is the Phone Information and Specs of the one i just rooted.
Firmware Version
2.1
Baseband
2.42.00.04.12
Kernel Verison
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.36.605.1 CL165907 Release-keys
Software Number
2.36.605.1
Browser Version
WebKit 3.1
PRL Version
58005
ERI Version
5

Were the specs like this before or after the rooting?

After the root.
I should have got the specs before the root. I can tell you how to do it if you have a 2.1 its fast.
I just want someone on here to verify it.

Sure why not.

Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.

FireSokar said:
Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.
Click to expand...
Click to collapse
Yeah honestly I'm with this guy ^.

Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.

amoamare said:
Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.
Click to expand...
Click to collapse
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.

Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.

amoamare said:
Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.
Click to expand...
Click to collapse
I would like it if you spelled it out even more. I am not familiar with all the ADB shell commands, so could you list the exact command for each step? That would help me out greatly, thanks!

AcidRoot said:
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.
Click to expand...
Click to collapse
He is trying to tell you that he has the old root method working on 2.1.
I know that he has done this on two devices. One fresh out the box with 2.1 and one that was updated to 2.1.
I am looking for a 2.1 Eris myself to duplicate.
I personally remember having a problem loading the root file on a 2.1 Eris, but I only tried one of them. Then I left it alone.
I think I gave up too easy when I was told that it could not be done with that file.

Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
version 1.47 or 1.49?

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
What was the boot screen like? The Green Android people that wave at you or the HTC "quietly brilliant" screen

Holy **** It works!

I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
No when you took the phone out of the box and started it for the first time after the green androids on skate boards did little green android guys wave or did you get the htc quietly brillant

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
HBOOT version I believe.

PusherRobot said:
Holy **** It works!
Click to expand...
Click to collapse
Hey man, what are the commands you used? I pushed PB00IMG.zip to the sdcard, but when I do > adb reboot recovery , it simply restarts and shows that phone icon with the red triangle over it. When I manually pressed power and volume down, the same error as always occurs (version is older). What am I doing wrong?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
Well congratulations, you found a bass ackwards way to root a phone with a (more than likely) 1.47 bootloader. We've had it for months, welcome to the party. Although, You're a little late...

Stock FRF85B to root?

So I've got a stock FRF85B setup. I'd like to be able to run some rooted apps, mainly something like SetCPU. Do I have to run a custom ROM or can I just obtain root and then install what I want?

clickwir said:
So I've got a stock FRF85B setup. I'd like to be able to run some rooted apps, mainly something like SetCPU. Do I have to run a custom ROM or can I just obtain root and then install what I want?
Click to expand...
Click to collapse
if apps requiring root are all you want, yes.
if flashing custom ROM or kernel are what you are looking for, you need custom recovery as well.

I got a file called 'update-nexusone-FRF85-root-signed.zip'. Can I just rename that to update.zip and do like I was doing for the other updates 2.1->FRF50, FRF50->FRF72 etc?

clickwir said:
So I've got a stock FRF85B setup. I'd like to be able to run some rooted apps, mainly something like SetCPU. Do I have to run a custom ROM or can I just obtain root and then install what I want?
Click to expand...
Click to collapse
have you unlocked you bootloader?

clickwir said:
I got a file called 'update-nexusone-FRF85-root-signed.zip'. Can I just rename that to update.zip and do like I was doing for the other updates 2.1->FRF50, FRF50->FRF72 etc?
Click to expand...
Click to collapse
+1... thanks

clickwir said:
I got a file called 'update-nexusone-FRF85-root-signed.zip'. Can I just rename that to update.zip and do like I was doing for the other updates 2.1->FRF50, FRF50->FRF72 etc?
Click to expand...
Click to collapse
If that is the (about)530KB update then you can do it that way if you want to go the long route.
You can get the already rooted custom ROMS like kang-o-rama frf85b final and flash them through custom recovery. Then you will be on 85b.
Also, here is the full update from 2.1. It took me from t-mobile stock 2.1 (edr79) to frf85b, but it works from most ROMS. This one you change to update.zip and go through stock recovery...If you haven't received it yet OTA.
Post #291
http://forum.xda-developers.com/showthread.php?t=712902&page=30

fineiwill89 said:
have you unlocked you bootloader?
Click to expand...
Click to collapse
No I have not. It's stock except for I've applied the google provided updates as they came out.
@adambenjamin The file I have is 2.9MB. How is it the long route?
My current understanding is I just rename this to update.zip, reboot into stock recovery, apply and reboot. There's more to it maybe? I think this is the one provided by Lox...? maybe.

Yes just rename update.zip with astro and boot into recovery just like the manual update process.

Well I tried it. Apparently there's more to it.
I got an error saying it's not a signed update. So I posted in the thread in the DEV section about it and we'll see what everyone says. Some people seem to be saying they need a custom recovery to run this, but can't put a custom recovery on because they need root first. I don't know.
No root for me.

If this helps at all I pulled some info from this guide to cobble something together. I already had my bootloader unlocked and I am unsure if the same method will apply to you as you are coming from stock. This also assumes you use a mac. Ignore the fluff about custom radios and images etc - this guide isn't specific to FRF85.
If you aren't urgent about this, I would hold off until you get better direction. If you don't mind tinkering around with your device then maybe this can get you in the right direction.
http://theonda.org/articles/2010/03...-performance-boost-and-some-serious-geek-cred

I wouldn't touch a mac with a 10 foot pole... unless I got a running start
I'm tempted to just wait for Cyanogen Mod 6 and go with that. There doesn't seem to be any easy way to get root. It seems complicated enough that I'd rather go with a full unlock, custom recovery and custom rom.

The method in the dev section works perfect on frf85b. I've got root with stock rom and stock recovery.
N1 w/ XDA App

new update can't root now.

i run unrevoked and nothing happens. this a new problem with the new update? this is my replacement phone anwaysy so.
anyone know anyways to root? i can't downgrade to old version. please help..

if you have s-off you just need to flash a custom recovery.
if you don't then i have no idea if the updated rom is rootable.
that would have been something to look for before upgrading
Good luck!

Having custom recovery is not the same as rooting (Superuser acess). Unfortunately, at the moment, Unrevoked won't work on the new OTA and if you install SU pack after the OTA it will just hang during boot up and you'll be in reboot hell. You can have Clockwork with the new OTA, just not root access.

downgrading to stock then s-off and upgrading work?
update. i tried downloading the super back to stock thread and the hboot says the file is older and i can't by pass it.. so hmm

I am in the same boat. Just got the phone and the f-ing salesman decided to install the OTA for me while he was setting it up. So do I return this thing in the hopes of getting one without the OTA or is it likely it will be rooted?

guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?

dadsterflip said:
guessing no ones able to do anything with the new update to reroot yet huh... any manual way to actually do root or downgrade to where the hboot doesn't recognize it as a older version?
Click to expand...
Click to collapse
Nope, can't downgrade...I'm out of ideas. Pretty pissed off actually to the point where I'm ready to take it back and get one that doesn't have the god damn OTA applied. I HATE owning devices that I don't really own.

i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box

I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary

caleris said:
I seem to have a problem. I was following the Bob Denny procedure to apply the OTA. Everything was going good until I got to the second step of booting into HBoot and reapplying the Clockwork recovery again. I cannot get into the Recover option in HBoot, it gets me stuck with the triangle over the phone image. I can boot normally and the phone is working but no root. In addition if I plug the usb cable into the phone, it charges but will not allow me to connect the phone as a disk drive, as well as the USB Debugging option is not there. I went to settings and tried the Connect To PC option but it FCs on me. The OTA part of this was successful (if you want to call it that). Any ideas on how to get this rooted again? Any help is appreciated.
Thanks,
Cary
Click to expand...
Click to collapse
press Volume Up + Power I think when you see the triangle

magneticzero said:
i rooted with unrevoked. it will stay waiting on root or something then you stop kill the program after phone is booted up.
imma be lazy and let you do the work but...
1. use unrevoked (not forever) http://downloads.unrevoked.com/recovery/3.21/reflash_package.exe
2. wait for it to say waiting for root and phone is restarted, then exit unrevoked.
3. place clockwork mod on sd card as pb31img.zip http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
4. go into recovery(volume down + power button) and let it detect pb31img and let it install
5. then use clockwork mod to install superuser apk manually http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
and yes this works, because i done it to 3 phones already
and yes this isnt hard...think outside of the box
Click to expand...
Click to collapse
But???????????? This will only work if you are already s-off, correct?

blackwolf77 said:
But???????????? This will only work if you are already s-off, correct?
Click to expand...
Click to collapse
if you have clockwork mod installed with S-On and updated the ota already, you can flash unrevoked forever through clockwork recovery... that will take S-Off to off. I was messing around earlier and did that..

I am not sure how you got clockwork installed. Everytime I try it recognizes the PB31IMG and then just skips over it. It never asks about installing it.

The file name has to be PB31IMG.ZIP right? Also the LCD works different right?
SLCD PB31IMG.ZIP
Sent from my ADR6300 using XDA App

Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.

Nitrogenus said:
Would the old downgrade and root process work? I upgraded my stock INC to 2.2 before Unrevoked worked on it. I went through a fairly painless, albeit time-consuming, process of downgrading to 2.1, rooting, and then installing 2.2.
I would think the process could be utilized here, the only difference being specific files used. One may even be able to follow the process as is. The end result would be S-OFF, which would allow you to do whatever you wanted (upgrade to 2.2 + recent OTA, install custom ROM, etc)
If anyone gets this to work, please let everyone know.
Click to expand...
Click to collapse
in for answer

tried it out, didn't work. the su trick with rageagainstthecage-arm5.bin does not work.

how to see page 3

Standing by!!!!! Will it work with s-on?

It shouldn't matter s-on or off. I have the SLCD screen don't know if it will make a difference. Just FYI
Sent from my ADR6300 using XDA App

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.