Eris Root Status - Droid Eris General

Root has been achieved for devices running 1.5. If you are on 2.1, we need to figure out how to downgrade back to 1.5. Goldcard seems to work for other devices, so it leads me to believe that goldcard is broken for our device. I'll be working on fixing it.

Done Very interested in seeing this rooted.

Any progress update? I have all sorts of friends who are anxious for this to happen. Is there another thread on another site where a progress is listed?

This seems to be the hot thread...they are close, but the 2.1 update may stall the efforts.
<edited>The original link is now closed, a new thread was started here.
forum.xda-developers.com/showthread.php?t=617203
(I can't post URL's due to moderation restrictions.)

so the desire got presented on the MWC in Barcelona this week. I t shure looks very neat. But what can I get with Android 2.1 on it? What is possible from application perspective?

EDIT::
-FAIL- =[
Disappointment.

Root Status Attained see Developers section for information

eris root
I am incredibly frustrated on trying to root my eris. I can place the img. File on the root folder, says I don't have access... ugh... someone help please.

Have you been here?▼
http://forum.xda-developers.com/showthread.php?t=647707

Trying to re-root my HTC Droid Eris
Nvm about my previous post. I just found out my rooting error "Main version is older" is due to the fact I have an Hboot 1.49. What I am failing to understand is that when I first got my HTC Droid Eris refurb (stock 2.1) I rooted it easily with the 1 click root for eris. Then had to downgrade to 1.5 firmware because I had no network connect for over twenty four hours even after a few hard resets that were well spaced out. I've read EVERYWHERE that you cannot root your phone if it has a 1.49 Hboot. So how did I? And yes I was rooted, I had full superuser permissions and the abd confirmed my root when I typed "$ su" it turned to a "#". I used the wireless tether soon after on a laptop not connected to the internet, worked no problems. So I was rooted. But now that I'm trying to re-root manually I'm getting the "Main version is older" error. Can anyone tell me why I was able to root the first time? Did reverting back to 1.5 change my Hboot to 1.49 when it could've been 1.46 or 1.47 previous to the downgrade? Thanks to anyone with any info.

evenmoreconfused said:
Nvm about my previous post. I just found out my rooting error "Main version is older" is due to the fact I have an Hboot 1.49. What I am failing to understand is that when I first got my HTC Droid Eris refurb (stock 2.1) I rooted it easily with the 1 click root for eris. Then had to downgrade to 1.5 firmware because I had no network connect for over twenty four hours even after a few hard resets that were well spaced out. I've read EVERYWHERE that you cannot root your phone if it has a 1.49 Hboot. So how did I? And yes I was rooted, I had full superuser permissions and the abd confirmed my root when I typed "$ su" it turned to a "#". I used the wireless tether soon after on a laptop not connected to the internet, worked no problems. So I was rooted. But now that I'm trying to re-root manually I'm getting the "Main version is older" error. Can anyone tell me why I was able to root the first time? Did reverting back to 1.5 change my Hboot to 1.49 when it could've been 1.46 or 1.47 previous to the downgrade? Thanks to anyone with any info.
Click to expand...
Click to collapse
Search the forums for "how to flash any ruu" and follow the instructions there. That should resolve your "main version is older error".
After that flash the official 2.1 ruu (search the forums) and reroot.
Sent from my Cyanogen Froyo using XDA App

Related

2.1 stock custom rom

Ok, so I bought an Eris about a month ago and got the OTA update like an hour after I bought it. After that installed, I was interested in rooting my phone only to find out that this could not be done because I have the stock 2.1 OTA. After playing with my phone I was able to install custom Roms' but I thought this could not be done if you had stock 2.1. I am still new to the whole "root" community and was just looking for clarification on how this happened. I am now running the Senseless Rom.
You only couldn't root if the hboot version was 1.49. Which some were and some weren't. You were a lucky one and got 1.47 s-off or something like that.
If your flashing custom roms then you have root. Your eris must have a 1.47 hboot instead of 1.49. The leaked versions of 2.1 have .49 which is currently unable to gain root through. Eris' that come with android 1.5 will have an hboot of 1.47 so eris' that recieve the OTA for 2.1 will still be rootable because the OTA dosent install a new HBOOT but is more or less a patch
-------------------------------------
Sent via the XDA Tapatalk Aspp
That clears it up. Thanks
Sheen160 said:
You only couldn't root if the hboot version was 1.49. Which some were and some weren't. You were a lucky one and got 1.47 s-off or something like that.
Click to expand...
Click to collapse
mine is 1.49 and i got my rooted
You only couldn't root if the hboot version was 1.49. Which some were and some weren't. You were a lucky one and got 1.47 s-off or something like that.
Click to expand...
Click to collapse
mine is 1.49 and i got my rooted
Click to expand...
Click to collapse
Really? Did you have a rooted
.47 first then some how retained it when "upgrading" to a pb00img.zip or rom or something? Cause I have leak v3 with a .49 and I haven't been able to root no matter what I try
-------------------------------------
Sent via the XDA Tapatalk App
ahjee said:
Really? Did you have a rooted
.47 first then some how retained it when "upgrading" to a pb00img.zip or rom or something? Cause I have leak v3 with a .49 and I haven't been able to root no matter what I try
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
There has never been a 1.47 S-OFF in the wild. Maybe at HTC, but not circulating publicly.
The first thing that the HBOOT flashing process (using a "PB00IMG.ZIP" file) does is replace the bootloader on the phone with the replacement version which is inside the PB00IMG.ZIP file. So, no - nobody ever "retained" their 1.46 S-ON, or 1.47 S-ON bootloaders during the root flashing process. After rooting - because you now have full control over the phone - it is indeed possible to put whatever bootloader you please back on the phone. It is rare that anyone does this, except maybe for testing purposes, but it is possible.
The bootloader which gets installed by the rooting process shows the following two lines at the top of the display:
[SIZE=+1]
PB00100 XC ENG S-OFF
HBOOT-1.49.2000 (PB0010000)[/SIZE]
I know this because I am staring at that screen right now. This is how you identify the bootloader from the ROOT ROM - it says "1.49.2000" and "S-OFF".
Now, the "locked" bootloader that is present in the Leak-V1, Leak-V2, and Leak-V3 PB00IMG.ZIP files says something slightly different - the version number it will report after it is installed is: 1.49.0000, and it will report S-ON in the top line.
You can see why people get confused when others say things like "1.49", when that could mean two radically different situations which are nearly polar opposites..
The bottom line is that if you have a bootloader which says 1.49-something-or-other, just check the top line in the display (the part that says either S-ON or S-OFF). That will discriminate between "rooted" and "might not ever be able to root".
bftb0
Aw come on.don't crush our hopes and dreams of rooted leaked phones lol.there's always hope
-------------------------------------
Sent from my HTC Droid Eris using Swype
i went from 2.1 ota to root also. Its the same steps as going from 1.5 to 2.1 root. just follow the steps at the unlockr website

[Q] No root after 2.11.605.9 HTC Thunderbolt

Been lurking for sometime learning things here and there, but now I've got an issue of my own I been pulling hair out over for the last 6 hrs.
I Upgraded to 2.11.605.9 Verizon OTA release today... attempted to use the revolutionary tool to re-root after the upgrade. Well that didn't work. I just get the message "Zerging Root... this might take a minute or so.. Failed to get Root! "
I have tried http://forum.xda-developers.com/showthread.php?t=1009423 the non root users section. With no luck.
Pretty new at this stuff, so if someone can let me if its possible to get s-off, i'd just like to downgrade to an earlier pg05img and NOT get the latest update So i can use revolutionary root.
Thanks in advance.
Nick
Try this..
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
CaptainStrange said:
This thread sounds like the same problem as what you are having. Read what the last two commenters did to correct the problem they are having.
http://forum.xda-developers.com/showthread.php?t=1308324
Also, the thread you originally posted is for returning back to stock, which is not the case. You want to refer to this thread at Thunderbolt Forums in order to acquire root...
http://www.thunderboltforums.com/fo...ry-5-minutes-less-root-without-data-loss.html
Confirm that you are following each and every step. In addition, make sure you are using the USB ports on the back of your PC opposed to the ones in the front. Good luck!
Click to expand...
Click to collapse
I've rooted multiple times using the method above, but since the update, I can't get past the Zerging Root step, even following the posts from the first link you sent
Flashed the Pg image using .androidpolice.com/2011/10/24/exclusive-gingerbread-build-2-11-605-5-for-the-htc-thunderbolt-fixes-several-issues-from-the-previous-leak/[/url] and it works, I was able to re-root using the rev.
Capt....
I am having the same problem as him. After I got this warranty replacement yesterday, no matter what I tried, I can't get past "zerging root". Cannot gain root access. I see you said to flash that image, but how do you do that if you cannot get s-off. I have also rooted thunderbolt several times using the "one click method" (which is also not working for this new 2.11. 605.9 build) and revolutionary. Any suggestions or instructions?
You dont need S-off to load that image... Simply download the file and rename it pg05img.zip and put it on the root of your SD card. Reboot the phone and hold down the vol down + power button to access the bootloader, push the volume button and it will search the sd card for the pg05img.zip file and load it. Just keep in mind it will reload it to factory settings, so back anything up that you have. It takes about 15 mins, but it does work. Once you have that image loaded from the link above you can use the revolutionary root. Let me know if you need help.
Rooting after 2.11.605.9 on TB solution
For those of you that have endured the frustration of updating to the latest software version (2.11.605.9) There is hope! Apparently with this software version, the bootloader is locked. And for some reason this version would not allow the "Revolutionary" rooting method to work. (I would imagine everyone with this problem had issues with not being able to get past Zerg Root. At least that was the problem I had)
Anyways, I got my phone rooted....heres how.
Per the instructions for using Revolutionary, install the driver as stated on their website. (Make sure HTC Sync is not installed on your computer)
Download Mecha_2.11.605.3.zip (I'm a newbie here so I cant post links, but I found it through Android Police but if u google it its easy to find, its hosted on multi upload) rename the zip file as PG05IMG and put on the root of your SD card (as you would in other rooting methods) and run the bootloader.
Once its booted and all that fun waiting is over and your TB powers back up, make sure to turn off all wireless connections to make sure OTA doesnt try to upgrade you. (I turned on airplane mode as soon as I could)
From there run Revolutionary as instructed from their website. Worked like a charm for me, and hope it does for all of you with this same problem.
I TAKE ABSOLUTELY NO CREDIT FOR THIS SOLUTION. Thank you for all you developers out there that make our phones able to be so much cooler and more enjoyable. I'm just glad I could help in this marginal way, and hope that someone will find it usefull. SPREAD THE WORD IF YOU KNOW OF ANYONE HAVING
So if I unroot and my phone takes the latest 2.11.605..9 update, all I have to do is flash the 2.11.605.5 RUU, put phone into airplane mode as soon as it boots, then I can root again?
I am not sure if I missed something but I followed those steps. When I went into boot, it said my version is "older- failed" and won't revert to the .5
I am miserable here with stock. I want to be rooted again.
Any thing else I can do?
Not sure why it wouldn't let you revert to an earlier RUU. Have you tried other earlier versions other than .5? The RUU I used was 2.11.605.3. Try that one. What version bootloader do you have? Also is there Pink letter at the top that says LOCKED?
I have not tried an earlier version... Yet. Will try and will update you. But the bootloader says "***locked***" s-on on the main screen. So I am not sure any older one will work. I read other people were able to accept a downgrade so I am hopeful.
Bootloader 1.5 and yes... It is ***locked*** sigh...
Try loading the 2.11.605.3 If it works just make sure you disable wireless connections when it boots, so OTA doesn't push the upgrade
Even if the OTA comes up before you disable any wireless connection it will download the OTA but then ask if you want to accept or defer. Just hit defer and proceed with the Revolutionary method to root and gain s-off.
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Ok guys hold on now, this is kind of misleaing... so did the OP have s-off for the downgrade ? Revolutionary has a password protected HBOOT that was designed to maintain s-off during an OTA or upgrade RUU, hence the reason a downgrade would be possible... Is the OP able to confirm they had S-OFF during the upgrade or S-ON. If i upgrade to 2.11.605.9 on a stock phone S-ON, am i going to be able to downgrade with ease ? I would say no.. not without tricking the bootloader into thinking its an older version which is what the commands are for:
adb push misc.img /data/local/
adb shell dd if=/data/local/misc.img of=/dev/block/mmcblk0p17
However you can't do this without a temporary root shell.
on build 2.11.605.9 there is no exploit for temporary root shell currently..
Please clarify.. ?
rberry88 said:
*Note: when you hit defer on the OTA, it asks you for a date to remind you, I just set the date to 12/29/2099. If anyone is still using this phone on that date, please tell them not to accept the OTA
Click to expand...
Click to collapse
No matter how far out you pick, the limit is 5 days. Picking anything longer, the phone will tell you that.
Like I was saying before the OTA came out, this OTA patches zergRush.
Bootloader has always been locked, this is not new.
I have a few vulns found, and erishasnobattery and I have a couple working exploits done.
However I am on vacation and wont be home until late tonight, once I am we will get something packaged and released for root.
Until then (this isn't the one we are going to release)
Awesome, i just bought my wife a t-bolt Friday and it did an OTA (that i just assumed was the same old gingerbread update that my buddy got but apparently it wasn't because i could not root. Thanks jcase for working on this for us.
I was able to get root with 2.11.605.9
I was already on 2.11.605.5 with root and S-OFF (revolutionary). Perhaps you can try one of the earlier releases such as MR2? This is what you do to get root with 2.11.605.9 if you can get your phone back to 2.11.605.5 or older:
1. Reinstall 2.11.605.5 stock (no root). I got the file from Android Police. I had to rename the file as PG05IMG.zip and run it from the bootloader.
2. Obtain S-OFF with Revolutionary after 2.11.605.5 has installed. Do not install clockworkmod or super user yet.
3. Allow the 2.11.605.9 OTA to be installed. Let the phone do it's thing, the update took my phone awhile.
4. Install Clockwork Recovery (again rename it as PG05IMG.zip and run it from the bootloader)
5. Boot into bootloader again and select Recovery. Install superuser.
6. Reboot and enjoy.
PS. I stumbled upon this on another thread here.
So I'm on a new phone that just did the .9 update about 10 minutes ago and then I find this thread after failing to root. So I'm s on stock everything. I can't revert can I? I'm screwed. I hate stock phones. Adds everywhere. No tether boring no options. I want my skyraider back.

[Q] Obtaining Root on Refurb?

Hey guys, recently sent my phone back and got a refurbished one running the 2.11.605.9 update. I have tired both the Revolutionary method and the old method to obtain root on my phone to no avail, any advice?
Currently there is no way to root 605.9. You'll have to downgrade to 605.5 then you'll be able to root with whatever method you choose. Had to do the same thing myself, not difficult but EZ to flub up, read up n take your time. A couple of threads on this and IIRC even a sticky.
Tapatalkn with my T-Bolt
I found an exe file that apparently will allow me to flash the ruu without having to mess with doing it from hboot, will post a something so they can include it as a revision to the guide to rooting sticky if I this whole process works
Whelp it worked, all they have to do is that you need to download and run this installer and it will take you back to .5 then run revolutionary.io (source)

[Q] sw 2.17 after hboot downgrade? revolutionary failed root.sw downgrade issues

Hi so I know there is tons of threads about software downgrades and revolutionary root fails etc. and I apoligize in advance for posting another.but Ive Been researching for hours a day for the past 2 weeks and Ive tried everything Ive come across to fix my issues with caution to no avail .Also everything Ive found is about just one of the problems Im dealing with and most are about downgrading sw in order to downgrade hboot. So I thought if I listed everything it would help overall in others process of downgrades and hopefully find a easy or atleast quicker way to fix these issues instead of going through each one at a time .so here it goes.....
I used unknownforce's method of downgrading my hboot from 1.50000 to 1.40000. and for some reason although my bootloader says hboot 1.40000 my software version is still 2.17. Now when I try and run revolutionary after i put the beta key in it says key accepted and starts with "zerging root...thhis might take a minute..."then says "failed to get root". I have run revolutionary several times now and redownloaded the file several times as well..hoping that it will catch as Ive read that sometimes it takes several attempts to work. Now Upon all my research Ive found that because my software is still 2.17 that its not truly hboot 1.4 until I downgrade my software to 1.3...Correct? and thats what is causing the revolutionary to fail getting root(or S_off) .And yes Ive unistalled HTC Sync(which i know needed to be unistalled for hboot downgrade process but not sure if i need it intalled to run RUU..Ive tried running RUUs both with and without HTCsync , Installed the 3.0.0.007 Drivers that comes in the unzipped rootingevo3d folder,my phone is in charge only mode when plugged into my pc , my debugging is on,fastboot unchecked,and Ive done severalfactory resets ,cleared caches and my cpu's antivirus is off ...
another note is the RUU that came in the downgrade zip didnt work so i had to find one that did.
Now Im trying to downgrade my software.. Ive run several of these versions of RUUs:
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.exe(which was the original version of the ruu that came in the downgrade hboot zip , Ive just tried different downloads)
and RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_signed.exe (which as far as i understand is the last software version for hboot 1.4)
and I get This Error
[Error[140]: BOOTLOADER VERSION ERROR
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again]
Ive also run several RUU zip files through my bootloader of the same software(which I renamed PG86IMG.zip) and It loads the file,then scans the file then it just goes straight back to the bootloader.It doesnt go through the whole list of files afterward and ask if i want to continue with update.
Ive also tried everything on a few different computers with the same results... another thing ive tried because durring the hboot downgrade process i gain temp root.i thought that was causing the issue running revolutionary. so ive run revolutionary after i took the temp root off and aslo with it back on as someone stated they fixed the revoltionary issue by gaining temp root then ran revolutionary and it worked . But i get the same root failed error.
Evo3d(cdma)
running:
Android version
2.3.4
Software #
2.17.651.5
hboot
1.40000
please help ..its much apreciated..
I hate to reply having to say that I "think" this will work but I'm just not positive. You need to run the 1.13 to get to the correct version. If you're already on 2.17 then you can't just run the 1.13, as you already know. I did my downgrade the same night it was discovered and at that point we had to change the mainvar so that the 1.13 would run. Unfortunately, the method has changed and those instructions are no longer there. However, if you look at the thread started by jlechner called simple guide to downgrade from the virgin mobile firmware (development sticky), you'll see instructions to set your mainvar to 0.0.0.0 and you should be able to run an older ruu or rom.zip.
Edit... Here's the link http://forum.xda-developers.com/showthread.php?t=1647505 just follow directions until you get to the part where it says leave this window open and dial ##msl, you don't need to do that.
Hope this helps.
ohkay so you gave me a good idea of how to fix it. now reading the threads comments there seems to be some major issues and after effects . such as data issues activation issues and the fact that it will be running virgin mobile although it seems compatible its causing issues after running for a while.also it states you need to be on a rooted rom but im trying to gain root in the first place haha. and also it states something about having s-on can cause problems in certain steps (in getting s-off is my initial goal i dont want to create more issues in trying to fix my first one . my phones working fine right now and i dont want to take 5 steps back to take one step forward...but I do thank you for the information it is very informative and hopefully can in the least help me
so my idea is to follow the first part if downgrading hboot as far as changing the mainver to 1.1 . the step right before you start running the ruu. i think its step 8. and then just run the 1.3 ruu then try revolutionary. I hope its that easy haha
now my question to you is do you know if the misc version/mainver is what causes the whole virgin mobile transfer? can i follow the steps i said as far as following the hboot downgrade method to a point and use that misc version/main ver that comes in the link you posted ?
It is very apreciated and I'm always open to sugestions . I will use the information you provided and try my idea and post my results if sucessfull thanks again
Aha! Success !! Thank You wikdNoob! Your input was what got me here! So I did what I said I was going to try based on your input and it worked flawlessly. Got the mainver down using the one I used to downgrade my hboot to 1.4 (which I followed the step by step from sorry to say but we all need outsources at some point evohacksdotcom)which Is just Unknownforces method in a step by step.I did up to step 8 then ran the 1.3 RUU and from there ran Revolutionary and without any hiccups I'm hboot 1.4 with s-off! I find its very rare to find a solution in the first response even if its just using something someone says in the first reply.haha so thank you again for the input.It is much appreciated and I hope others can use this thread to fix the several issues i was having.

Rooted GSM Evo 3D + OTA ICS

I honestly hate to post and will usually spend days reading existing posts as normaly the info I need has already been posted, but this time round I'm honestly spinning my wheels a bit.
Phone: Rogers HTC Evo 3D running original Rogers ROM.
Android: 2.3.4
HTC Sense: 3.0
Baseband: 10.53.9020.00U
Radio: 10.13.9020.08_2M
Hboot: 1.49.1107
Modifications
Revolutionary CWM 4.0.1.4
Superuser 3.0.7
Revolutionary S-Off
All I want to do is install the official Rogers OTA ICS update (which my phone is showing as available). I believe I need to disable S-OFF, unroot and restore the stock recovery loader before the OTA update will install.
I'm looking for the easiest way to go about this. There is so much info out there and majority being CDMA. A push in the right direction would be much appreciated.
In another thread, in the Q&A, i pointed towards a download. Let me try and find it....
Anyways.... I downloaded the EXE, they say to put it in a zip, and let it run from Hboot. I executed the EXE file directly from windows, and downgraded to .2, updated the phone to .3, and then to 4.0. I lost my root, but i still have my S-off and my Recovery does not work in Hboot (used to be CWM, i guess it got overwritten)
My next step is do get CWM back on and flash SuperUser to root my phone again. There's a few things in ICS, that i don't like. If you hear how to do this, or find a thread on it, let me know. Ive been searching for 2 days now and cant find anything.
EDIT: Here's the link
http://file.anzhuo.cn/data/attachme...00_10.13.9020.08_2M_release_203803_signed.exe
what about the kingcobra ICS? Why not stick with that then this?
I've used modded roms in the past. Honestly they were always more headache then they were worth for me. Features not working etc etc.

Categories

Resources