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

Frak! Fat fingered permaroot - root is now an unknown user

Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.

vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.

Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!

just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on

vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.

mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.

Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...

Please post questions in Q&A section.

just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.

Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App

Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark

Can't boot into recovery

OK so my evos software is fully up to date, 3.70.651.1, I tried using the Z4root rooting method that basically works on anything running froyo but i've hit a snag. This app gives you the option to temporarily root of permanently root your phone. The permanent option doesn't work, just restarts the phkne. The temporary option does work though, I've run Cachecleaner and rom manager and have successfully flashed both clockworkmod and Ra recoveries. My issue is this, when I either manually try to reboot to recovery or use the option to within rom manager, all I get is the phone symbol and a red triangle with an exclamation point. Despite successful flashing of the recovery menu, I can't actually get to it. Any help would be appreciated.

joehunni said:
OK so my evos software is fully up to date, 3.70.651.1, I tried using the Z4root rooting method that basically works on anything running froyo but i've hit a snag. This app gives you the option to temporarily root of permanently root your phone. The permanent option doesn't work, just restarts the phkne. The temporary option does work though, I've run Cachecleaner and rom manager and have successfully flashed both clockworkmod and Ra recoveries. My issue is this, when I either manually try to reboot to recovery or use the option to within rom manager, all I get is the phone symbol and a red triangle with an exclamation point. Despite successful flashing of the recovery menu, I can't actually get to it. Any help would be appreciated.
Click to expand...
Click to collapse
I dunno about all of that, but based off your description of temporary and permanent roots, sounds like you did a temporary root without NAND unlock and correct me if i'm wrong, you can't flash a recovery without a nand unlock?

SilverStone641 said:
I dunno about all of that, but based off your description of temporary and permanent roots, sounds like you did a temporary root without NAND unlock and correct me if i'm wrong, you can't flash a recovery without a nand unlock?
Click to expand...
Click to collapse
correct, need nand unlocked to flash a rom, z4 doesn't unlock nand, unrevoked does, and the adb method does as well

I don't think there is a successful root yet for 3.7, is there? Not a simple one like urevokEd

mikeDCMDVA said:
I don't think there is a successful root yet for 3.7, is there? Not a simple one like urevokEd
Click to expand...
Click to collapse
I think theres a new unrevoked
edit there is but it says for the incredible ota, if it doesn't with then will need to follow the guide in the dev section for rooting

[Q] Rooting GT540

Hello all,
I'm kind of a newbie, but able to follow step-by-step instructions.
I've tried two different methods of rooting my phone, the password method (android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/310737/how-to-root-your-lg-gt540) and using Z4 Root. I assumed the first one had worked, but somehow not. When I tried with Z4, it installed Super User and gave me the option to "un-root", but testing it in adb and terminal emulator inevitably ended with a "failed to link su CANNOT LINK EXECUTABLE" message. Apps like Titanium Backup won't work either. I tried factory reset, and when I restarted it Super User was still there, but when I opened it, it gave a message saying that there was a new su update. I okayed it to install but it failed and said it was placed on the SD card. Super User instructed me to reboot in recovery mode and install it from there, but I wouldn't know what to do with it.
Anyone know where I went wrong, or have a foolproof method of actually getting my phone rooted? Thanks so much!

laurengirl said:
Hello all,
I'm kind of a newbie, but able to follow step-by-step instructions.
I've tried two different methods of rooting my phone, the password method (android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/310737/how-to-root-your-lg-gt540) and using Z4 Root. I assumed the first one had worked, but somehow not. When I tried with Z4, it installed Super User and gave me the option to "un-root", but testing it in adb and terminal emulator inevitably ended with a "failed to link su CANNOT LINK EXECUTABLE" message. Apps like Titanium Backup won't work either. I tried factory reset, and when I restarted it Super User was still there, but when I opened it, it gave a message saying that there was a new su update. I okayed it to install but it failed and said it was placed on the SD card. Super User instructed me to reboot in recovery mode and install it from there, but I wouldn't know what to do with it.
Anyone know where I went wrong, or have a foolproof method of actually getting my phone rooted? Thanks so much!
Click to expand...
Click to collapse
What version of android version u r running with?

It's a 1.6 :/

The password one should work for 1.6
Sent from my GT540 using XDA App

Universal Androot?
laurengirl said:
Hello all,
I'm kind of a newbie, but able to follow step-by-step instructions.
I've tried two different methods of rooting my phone, the password method (android.modaco.com/content/lg-gt540-optimus-gt540-modaco-com/310737/how-to-root-your-lg-gt540) and using Z4 Root. I assumed the first one had worked, but somehow not. When I tried with Z4, it installed Super User and gave me the option to "un-root", but testing it in adb and terminal emulator inevitably ended with a "failed to link su CANNOT LINK EXECUTABLE" message. Apps like Titanium Backup won't work either. I tried factory reset, and when I restarted it Super User was still there, but when I opened it, it gave a message saying that there was a new su update. I okayed it to install but it failed and said it was placed on the SD card. Super User instructed me to reboot in recovery mode and install it from there, but I wouldn't know what to do with it.
Anyone know where I went wrong, or have a foolproof method of actually getting my phone rooted? Thanks so much!
Click to expand...
Click to collapse
You obviously know I don't have this phone =], but read something somewhere about Universal Androot from market. I don't know if you got this on my FB or whatnot. GL

Thanks, but same message:
link_image[1638]: 1841 could not load needed library 'libbinder.so' for 'su' (load_library[984]: Library 'libbinder.so' not found)CANNOT LINK EXECUTABLE
Titanium backup still cannot acquire privileges. I've tried universal androot now as well.

laurengirl said:
It's a 1.6 :/
Click to expand...
Click to collapse
why don't you upgrade to 2.1 or 2.2

Check whether u have file libbinder.so in ur system/lib folder.
If u don't have
Exatract it from .zip and change the name to libbinder.so then past this folder in system/lib
I am not sure whether it will work or not. it is kind of workaround

Thanks, I ended up unrooting it with z4, doing a factory reset and formatting the sd, and then rerooting with androot and now it works! No idea why it worked this time and not the three or four times before... I guess tenacity pays off. I appreciate the help!!

[Q] unrevoked wont flash

hi
im a complete noob at this game so plz bear with me.. i managed to s off my wildfire earlier with alpharev (cheers alpharev) and have followed instructions on other threads but i still cant get the latest unrevoked to work..it still asks if the firmware is new? ive also tried the older version which also fails to flash the recovery.
i used the latest superoneclick and it went through the motions and deemed that the phone was rooted but as i checked it, it wasnt
i have just used rom manager premium and it downloads clockwork to about 99% then freezes and force closes
can anyone point me it the right direction as im loosing my hair atm
thanks in advance.

tincaesox said:
hi
im a complete noob at this game so plz bear with me.. i managed to s off my wildfire earlier with alpharev (cheers alpharev) and have followed instructions on other threads but i still cant get the latest unrevoked to work..it still asks if the firmware is new? ive also tried the older version which also fails to flash the recovery.
i used the latest superoneclick and it went through the motions and deemed that the phone was rooted but as i checked it, it wasnt
i have just used rom manager premium and it downloads clockwork to about 99% then freezes and force closes
can anyone point me it the right direction as im loosing my hair atm
thanks in advance.
Click to expand...
Click to collapse
with superoneclick, hit shell root, wait. after , hit root, and you'll have it !

anonimo95 said:
with superoneclick, hit shell root, wait. after , hit root, and you'll have it !
Click to expand...
Click to collapse
thanks..tried this and still no joy

Try this way:
http://forum.xda-developers.com/showthread.php?t=1130044

nejc121 said:
Try this way:
http://forum.xda-developers.com/showthread.php?t=1130044
Click to expand...
Click to collapse
worked a treat
kudos to you man

no need of shell root first. Directly hitting the root also gives permaroot.
And go with PC49IMG process or fastboot flash recovery process for custom recovery. Donot use unrevoked.