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

I Got Root But Now I Cant Get su To Work

Please close this post!

I would ask what you did now that you want this closed? After weeks of trying to get root I finally am able to get in. Followed the steps did update.zip etc. Reboot and it appears I have no SU access. I am hoping this is a simple fix because for the last 2 hours I have been unsuccessful getting into adb shell.
Thanks

trying to root the OTA 2.2 upgrade

so i accidentally installed the 2.2 OTA and it got rid of my root and everything and to my understanding you cant root the OTA 2.2...am i totally screwed or is there away to downgrade some how or something and get root back

Screwed for now anyway until they find a hole. You'll need patience for a bit. I'm assuming you didn't install unrevoked forever?

egobuster1 said:
so i accidentally installed the 2.2 OTA and it got rid of my root and everything and to my understanding you cant root the OTA 2.2...am i totally screwed or is there away to downgrade some how or something and get root back
Click to expand...
Click to collapse
No you are not. I did the same thing. You can downgrade your phone and then root and S-OFF it. Once this is done, you can upgrade to 2.2 and then root the phone. Check my post: http://forum.xda-developers.com/showthread.php?t=771178
This will give you the steps and links to follow. Enjoy.

I went to the link above, and tried condition five but I got stuck at step 18-19, When I re-enter adb shell I dont have root, I still have $ not #. Has anyone else had trouble or done this yet? Im running Ubuntu if that makes a difference

adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked

just followed all the steps i thought and everything went well got the # sign instead og hte $ sign and everything and when i restarded it for it to load the PB21img file once it did that it erroed and said the main version is older udate fail..not sure what to do

egobuster1 said:
just followed all the steps i thought and everything went well got the # sign instead og hte $ sign and everything and when i restarded it for it to load the PB21img file once it did that it erroed and said the main version is older udate fail..not sure what to do
Click to expand...
Click to collapse
What steps are you refering to?

dalepl said:
What steps are you refering to?
Click to expand...
Click to collapse
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img

egobuster1 said:
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img
Click to expand...
Click to collapse
Thanks, will update.

egobuster1 said:
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img
Click to expand...
Click to collapse
What error did you get? Did HBoot load the image?

egobuster1 said:
i followed condition #5 and everything seemed to go as plan until the reboot then it gave a error. im gonna download a older RUU off the the site and see if maybe thats the problem but i dont know what else to do if not
also in the instructions it says to push pc31img and i think its supposed to be pb31img
Click to expand...
Click to collapse
I used this RUU to extract the ROM.
RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494_NoDriver_0514
You can get it here: http://www.shipped-roms.com/shipped/Incredible/RUU_IncredibleC_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_release_161494_NoDriver_0514.exe

dalepl said:
What error did you get? Did HBoot load the image?
Click to expand...
Click to collapse
no it started to proccess through like it was going to and then said error the image is to old or something what ever it says if you just try and load the img with out having root access

i got the same error, main version is older! i tried rom.zip from all 4 RUU. i think we need to revert to an older hboot but i have no clue how to do that without root.

ya i think we need a older Hboot also but like you stated im lost as of how to do it

yep tried again with a different RUU and got the error main version is older.
not sure if there is a fix or what to do for this

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

Unlock Problem: Permission Denied??

I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.

If I root the phone, will that work?
Also, what are some good programs to copy the EFS folder?
Sorry for all the questions.

I'm fairly certain you have to be rooted

I am rooted as of 10 mins ago.
I tried to unlock it and I still got the same thing.
It says Permission Denied
Anyone have any ideas?

Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.

molson24 said:
Does anyone know how to get SU permission?
I am trying to pull that nv_data.bin
But it says I do not have permission.
Click to expand...
Click to collapse
in Terminal?
type:
su
(and hit enter)
before the command that needs superuser permission.

Also you probably would be better off just pulling the whole efs folder.

molson24 said:
I have my device bridged and it says its connected and recognized when I run ADB. When I try to run the Script it says the following:
Failed to copy /efs/nv_data.bin Permission: Denied
*Error Unable to find file <.\nv_data.bin>
Could not find C:\Documents and Settings\1\Desktop\Generate Unlock Windows\nv_data.bin
If anyone could help that would be greatly appreciated.
It is on JFD stock, which I rooted from JF16 using Odin.
I have installed all the drivers as well, and I have it on debug mode.
Click to expand...
Click to collapse
for permission denied try this:
open terminal emulator on your phone (download it from the market if you dont have it yet)
or you can type "adb shell" without quotations into the dos prompt and do it from there.
and type:
su
chmod 777 /efs/nv_data.bin
exit
exit
then in the dos prompt try:
adb pull /efs
or if you just want nv_data.bin:
adb pull /efs/nv_data.bin
if you need further help, this was written for the 19000 but it should help you anyways.
http://www.communityhosting.net/sgsunlock/i9000.html

You need to copy your nv_data.bin from your phone to your pc
You should see a folder made in the repair_nv_data folder like this Sauverarde_efs_apres_reparation
Move your nv_data.bin there along with nv_data.binvierge and repairation_nv_data.jar and Step2 and Step 4
Run Step 2 again and then Step 4 after its done creating the new nv_data.bin
I can't remember but I think you have to delete nv_data.md5 and a few others from your phone first

Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol

molson24 said:
Thanks for the help boys!
The phone is now unlocked, it took the whole night, but I finally got it.
Ended up using this method here
http ://www.communityhosting.net/sgsunlock/
Worked fine, but theres alot of steps you have to follow, so it just takes time.
The reason I was having problems with the SU permission, was because the phone screen always shuts off after a few seconds or w/e and I never saw the pop up asking to accept the SU Permission. lol
Click to expand...
Click to collapse
lol yeah I can see that happening
I've accidently denied su permission a few times myself even when I do notice the pop up
well congrats!

Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?

molson24 said:
Thanks Dude!!
The only weird thing that is happening is that when I am connected on wifi... My downloads dont seem to be working really... They worked for 20 mins... And then I tried at a few mins later and it says download starting and dosent do anything. I can browse the internet fine and I am connected so I am not really sure.
Also, If I am still in JFD stock, If I were to flash it again with JFK with Odin, would this lock the phone back up again? Or If I were to flash it back from J16 to JFD, would it still be unlocked?
I am not sure, but I am thinking I reload JFD again, and root it again, then maybe the downloads will work properly. Any thoughts?
Click to expand...
Click to collapse
Unlocking should not break your downloads (At least I've never heard of it happening) but you'll be fine flashing any rom you like, without having to unlock again.
are you still on t-mobile just unlocked?
orare you on a different carrier now that your unlocked?
the main things to be careful of when flashing roms is:
be careful going from froyo (2.2 JK2/JK6) back to eclair (2.1 JFD/JI6) its a little tricky, but not too bad.
and be careful with lag fixes, if you use one always disable it before flashing. (I never found them very useful myself anyways)
going from JFD to JI6 and back should be fine though.
if you want a completly clean slate then you can use Odin and it still wont re-lock your phone.
you might even find that you like some of the roms out there better than the stock one
I know I did.