Database Users

Have to admit I need some help with rooting

Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.

This means you are on the leaked version now and there is nothing that can be done as of right now.

K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?

ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.

sounds like you got a bad pb001.img file.

ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?

nevermind addressed my issue

As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5

ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.

af man...seriously!

out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"

HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA

ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!

Recovery mode issues

Hi guys!
I had root my htc hero a month ago then i tried few rom's to see how they are. My phone is locked for Orange UK. Everything was ok. Then i had updated the new ROM from htc website (via RUU file). The phone working fine, but now i can't go into recovery mode. If i reboot into recovery mode i have a white screen with a triangle and a phone sign. Pressing Home+Power again i have acces to 3 options:reboot system now, apply sdcard:update.zip, and wipe data/factory reset but only reboot working. Also i have an error on the same screen: E:Can't open /cache/recovery/command
Trying to downgrade using an older version of RUU i got an error: on phone-Checking customer ID. Upgrade failed; on the computer: Customer ID error.
Everything else working fine.
What can i do?
Thank you.

emilio33 said:
... Then i had updated the new ROM from htc website (via RUU file). The phone working fine, but now i can't go into recovery mode....
Click to expand...
Click to collapse
Which RUU exactly?.... Please do not say the new 2.1?!

As long as it isn't the 2.1 update from a few days ago,... Just follow BTDAGs guide in my signature. You will probably need to downgrade using the goldcard method. But start at the top and you should be fine.

No, is not 2.1update. I want to update to the new 2.1 but can't do because of that issue.
-------------------------------------
Sent via the XDA Tapatalk App

Thanks 'ddotpatel' . I will try to follow that guide. Hopefully will work.
-------------------------------------
Sent via the XDA Tapatalk App

The RUU file version installed is 2.73.61.66 for Orange. Could be a problem?
Thanks.

ddotpatel said:
As long as it isn't the 2.1 update from a few days ago,... Just follow BTDAGs guide in my signature. You will probably need to downgrade using the goldcard method. But start at the top and you should be fine.
Click to expand...
Click to collapse
Followed BTDAG guide with no succes.
On first method with flashrec i've got an error: Backup FAILED: Could not run command.
Second option can't use because i don't have full access to recovery mode
Last option (goldcard), i've got an error when use: cat /sys/class/mmc_host/mmc1/mmc1:*/cid
saying: cat/sys/class/mmc_host/mmc1/mmc1:*/cid not found.
What else i can do? Please guys...
Thank you.

Have you set up the SDK correctly? ... Do you see anything when doing:
cd c:\android\tools\
adb devices
???????

Help Please
I have the same problem.
Tried everything, can't flash new recovery img using apk flasher, can't try the goldcard method cause I get "adb access denied" even though "adb devices" shows my phone. Tried using Droid Explorer to flash the new img or update but that didn't work too. Formatted my sd card a few times using the phone & my OS (when it was mounted and acted as disk on key). I also reinstalled the RUU that caused it a few time to see maybe I did something wrong but nothing (I too had a rooted phone and installed the 2.73 Orange UK root).
What else can I do? I feel like it has something to do with my SD card but I don't know how else to format it. Even on Droid Explorer it doesn't show me any of the folders that are in there when I'm connected (like tmp,rosiescrl, footprints).
Help

Tried to reinstall corect drivers for HTC but in device manager show 'drivers are up to date', so no change yet. Any other ideea?

tried to reinstall RUU file 2.73.61.66. Was working fine, then i tried RUU 2.73.405.5 . No chance. It said 'customer ID error'. Recovery mode still not working.
Help guys.

Well, of course it won't be working. Updating with official rom completely replaces everything on your phone including custom boot. And, of course, you won't be able to install .405.5 since it's lower version than your firmware. You have to downgrade to .405.5 using goldcard and then repeat the root and custom recovery install procedure.

2.1 Unrevoked root/forever dif kernel, just got update message

I truly wasn't expecting to be part of the update group. I am rooted/S-OFF and running Hydra Kernel.
Tonight about 15min ago I got the update message. I went to "more info" and when I backed out the pop-up went away, but I captured the system update page. Would like to get the update off the phone, but not sure how too.
I tried to use the "If you receive the 2.1 update, do this first thing.
http://www.droid-life.com/2010/03/30/if-you-receive-the-2-1-update-do-this-first/
Selecting "install" my phone vibrated twice and went BLACK. Left it that way for a bit. I *guess* it was trying to download the update... I pulled the battery before it finished. No idea where it put the update. I pulled the SD and mounted it in my PC (no update.zip).
Booting into recover it attempted to install the update and failed. Rebooting got me back to my current ROM.
So, I'm not sure how to grab the update and/or if it's worth it.
Edit: during that process apparently my phone thinks its up-to-date again (shows 2.1 still of course) but under system updates it says no longer shows the update... ahh well I wasn't gonna install it anyway.

Dmtalon said:
I truly wasn't expecting to be part of the update group. I am rooted/S-OFF and running Hydra Kernel.
Click to expand...
Click to collapse
Are you running a custom ROM? If not, that is more than likely why. Stock 2.1

It failed because you more than likely have a custom recovery. need stock.

My goal was, of course to just get the update.zip file... Not actually apply it. It was an apparent fail... At least I didn't dork anything up too bad. I do see some files that got created on the phone (0 byte) which I believe was the attempt to install.
Ahh well, life goes on.
And, yes I have stock 2.1 + unrevoked + forever + Hydra kernel.

Getting your phone ready for the FroYo update.zip!

Okay, so it seems we ran into a few issues with the installation
DO NOT run the FroYo update.zip unless the software information on your phone reads as followed:
Baseband should say 1.00.03.04.06
Software/Build number should say 1.22.605.2...if it is 1.22.605.0 please read the following instructions:
May OTA attached at the bottom of the thread thanks to wryun(note: i havent tested it, so any feedback on the zip would be great.)
-Drop the file on the root of your SD card.
- Turn your phone off.
- Press and hold the Volume Down and Power at the same time to boot into HBOOT.
-
When the white HBOOT screen appears, use the volume button to move down to “RECOVERY.”
- Press the Power button to select “RECOVERY.”
- When the triangle and exclamation appears, hold the Volume Up and Power button at the same time.
- Using the volume button, scroll down to “apply sdcard:update.zip” and select it.
- Make sure that the software now says 1.22.605.2[/COLOR]
Now go back to the update.zip on your sd card and delete...now you can proceed with the Froyo update.zip here http://forum.xda-developers.com/showthread.php?t=770091

Dinc with Baseband 2.05.00.06.11
I'm not rooted but had applied the leaked update to my Droid that updated my phone and now have the baseband 2.05.00.06.11. I am not able to apply the froyo update.zip without getting the same error message as many others have. Any assistance would be much appreciated. I hope to get back to stock and then update.

whiteknight333 said:
I'm not rooted but had applied the leaked update to my Droid that updated my phone and now have the baseband 2.05.00.06.11. I am not able to apply the froyo update.zip without getting the same error message as many others have. Any assistance would be much appreciated. I hope to get back to stock and then update.
Click to expand...
Click to collapse
I will provide you with a link to get it back to stock shortly

whiteknight333 said:
I'm not rooted but had applied the leaked update to my Droid that updated my phone and now have the baseband 2.05.00.06.11. I am not able to apply the froyo update.zip without getting the same error message as many others have. Any assistance would be much appreciated. I hope to get back to stock and then update.
Click to expand...
Click to collapse
Here ya go...http://androidforums.com/incredible-all-things-root/99828-video-howto-unroot-incredible-downgrading.html

Thank you schwartzman93. Very much appreciated. I'll let you know how it works.

Is it CONFIRMED that the update will fail if we are running 1.22.605.2 with the 2.15 radio and STOCK recovery?

Do we have to downgrade if we are running on the 2.2 OTA from 8/1?
build 3.16.605.0/ radio 2.05.00.06.11

lamusician said:
Do we have to downgrade if we are running on the 2.2 OTA from 8/1?
build 3.16.605.0/ radio 2.05.00.06.11
Click to expand...
Click to collapse
Yes, you do.

tylerwagler said:
Is it CONFIRMED that the update will fail if we are running 1.22.605.2 with the 2.15 radio and STOCK recovery?
Click to expand...
Click to collapse
that's also with hboot .77
**Trying it right now
***it appeared to have worked, however when I booted it hung toward the end of the droid bootup animation... then after like 3 minutes it finally booted

Thank you so much for all of the help on these threads. I have read extensively but I still have a question concerning the new 2.2 OTA update:
I rooted via unrevoked3, then ran unrevoked forever to set s-off. I then immediately reverted back to pure stock 2.1. I have not upgraded my radio and I never received an OTA of any kind, in May or now.
Baseband:1.00.03.04.06
Build Number: 1.22.605.0 CL161493
My question is this: will I receive the "official" OTA 2.2 from verizon with this build, and will I be able to install it if I receive it, or will I need to upgrade my build to 1.22.605.2 before I can receive and/or install it? Thanks!

THANKS
THANKS schwartzman. the "may OTA" got me to ...605.2 perfectly. I read through a bunch of other posts by you. You did a lot of good work today. THANKS

schwartzman93 said:
Yes, you do.
Click to expand...
Click to collapse
I've downgraded and my baseband is now 1.00.03.04.06 and sw is 1.22.605.2
My hboot is 0.79 though, not 0.77. Is this going to be a problem or can I proceed with the update?
Thanks in advance.

Thanks for posting the link to the downgrade. It took some work but I was able to get my phone back to stock and now...it is booting up with Froyo (crossing fingers).

help!
schwartzman93 said:
I will provide you with a link to get it back to stock shortly
Click to expand...
Click to collapse
I was following the video instruction to downgrade from 1.36.605.0 baseband 2.05.00.06.11. when i booted and it was supposed to error out reading the pb31img it wants to install. is this a problem? bootloader is .77

HELP!!!!
its telling me e: signature verification failed Installation aborted... how do i fix this?? i factory reset and wiped cache still nothing???

Thanks soo much dude. I just registered with this site so I could thank you. I rooted my phone right before the OTA and the update failed so I assumed it was my fault and unrooted back to stock. I wasn't even aware of a May update till now. Thanks a ton!

when i try to install the may ota update.zip i keep getting
E:Can't open /cache/recovery/command
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/inc/inc/inc:2.1-update1/ERE27/161494:user/release-keys" || file_getprop("system/build.prop", "ro.build.fingerprint") == "verizon_wwe/inc/inc/inc:2.2/FRF91/231334:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation Aborted.
anyone have any idea what im doing wrong or what i should do to fix it so i can install the may ota, and then install the 2.2 ota?
Here is what i have on it right now
INCREDIBLEC XC SHIP S-OFF
HBOOT-0.77.0000
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Firmware 2.1-update1
Build 1.22.605.0 CL161493 release-keys

Make sure you arent running Clockwork Recovery...that maybe the problem...thats what seems to be the problem with people getting their phones to Android 2.2

no i did the pb31img.zip to remove it and when i go into it says its the android recovery

same error
optikkore said:
no i did the pb31img.zip to remove it and when i go into it says its the android recovery
Click to expand...
Click to collapse
i am getting that same error when i try it as well

Update to HTC EVO 4G failed

All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!

guidecca said:
All,
I got a notification of update this morning (June 29, 2011) on my HTC EVO 4G (rooted/with netarchy toast mod) but when I tried to apply the update I get:
assert failed: apply_patch_check ("/system/lib/modules/bcm4329.ko". "78fE:unknown command [c535f323ef3a5c8304b32f514c23ea458132b".]
E:unknown command [9"0]
E: Error in /cache/OTA-Supersonic_4.24.651.1-3.70.651.1_release404yzkft23eop520.zip (Status 7)
Installation aborted.
Android system recover is open and the prompts are:
- Reboot system now
- USB-MS toggle
- Backup/Restore
- Flash zip from sdcard
- Wipe
- Partition sdcard
- Mounts
- Other
- Power off
What do I do next? How do I get this update? Thanks!
Click to expand...
Click to collapse
Anyone, anyone? Don't everyone rush down. There's room for everyone.

Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?

Try unrooting and put a stock rom and then do an update. Hope that helps
Sent from my HTC EVO phone, shouldn't we all have one?

If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.

I Think I Did/Didn't
mattrb said:
Is your recovery old (ie not Clockworkmod 3)
Have you tried to backup your apps with titanium and just starting all over with a new updated full rom?
Have you edited the filesystem to cause the update to say this? If you edit any of the filesystem, the update fails.
You need to download a new rom and just start all over it seems.
How are we to figure things out if you dont give any background?
Click to expand...
Click to collapse
Not sure what clockworkmod I have. I could backup app with titanium and which "full rom" would you recommend? I have netarchy-toastmod-4.3.4-cfs-havs-less-nosbc-uni installed and in zip format. I rooted the phone and applied the toastmod so I modified the stock HTC EVO 4G file system. The next comment suggests unrooting the phone and starting over. Why so much work for a "smart" phone? Any specifics would be appreciated on how to proceed.

kf2m said:
If you want to keep root, then you never take the update. Otherwise you will most likely lose root, and will have to wait until a Dev finds an exploit to reroot. If you want to just update the radio(s) then there are flashable updates in the Dev section that you can flash.
Click to expand...
Click to collapse
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it. My wife's unrooted phone took the update easily.

guidecca said:
Seems to be a rule never to take an update of the original after modifying any gadget. Maybe my rooted phone is better off/more advanced without the update but I haven't found anyone that has said it yet. Since the update failed I think I have root but I will check it.
Click to expand...
Click to collapse
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.

If you would like to keep the stock rom but update to the newest release you can download Rom Manager from the market and flash the newest stock rom. Quite easy and only takes a few clicks. Next time you see an update from sprint, just wait until Rom Manager gets a rooted rom of that release and go nuts. If you don't feel like dealing with Rom Manager you can manually flash the roms you find in this forum. Hope this helps.

This has worked rather well for me for the past few updates, including the most recent one:
forum.androidcentral.com/htc-evo-4g-rooting-roms-hacks/90582-guide-updating-rooted-gingerbread-without-flashing-new-rom-wiping-your-phone.html
Also, the error you see is likely due to you changing the Broadcom file in that location to enable Wifi-N speeds on your EVO. Is that something you remember doing? When installing updates, it needs the original unchanged version of "\system" files to be there to verify against, including this one.
I just went through the process, and got the same error before I remembered to change bcm4329.ko back to the original. Also, don't forget to unfreeze any bloatware if it is frozen, or it won't proceed past the verification process (as it changes "\system" files. Additionally, clearing the Davlik cache is always a good idea when updating.

I forgot to mention- If I remember correctly, the instructions are elaborated on in post #44 of that page.

tgruendler said:
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
Click to expand...
Click to collapse
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?

guidecca said:
You say a rooted version was ready to be flashed within hours.
This is what I read on Android Forums:
There is no exploit yet to allow unrevoked to root the new hboot(2.16). They will find it but how long is unknown.
You can apply the update by flashing the rooted rom and the updated radios found here: [ROM][STOCK] 4.24.651.1 - Odexed & De-Odexed - xda-developers and here: [ Radios ][ 6-3 ] All EVO Radio, WiMAX, PRI, NV & HBoot versions - xda-developers
The only thing that would not happen by flashing those it that your hboot would not be upgraded which you don't want anyway so that you can retain root.
If Haux has an exploit would it work on netachy toastmod rooted EVO 4G?
Click to expand...
Click to collapse
To be technical because I am a jerk, Hehe, you don't root the hboot. You unlock it via making it s off. You root the Rom by applying super user privileges from within. Hboot s off means you can easily flash different recovety images, radios, and any ruu considering you have supported radios. Tomatoes tomahtoes.
Sent from my PC36100 using XDA Premium App

Thanks
That is why you should read, read, read a little more and when you feel comfortable with doing something to your phone, stop and keep reading. This is posted over and over and over again in this forum. Never, ever take the OTA update. As soon as the update was available, Haux had the rooted version ready to be flashed within hours.
I just thought that maybe there was an exploit for gingerbread 2.3 (OTA) that someone had found within hours of Google's release. I wanted to definitely make sure there was or wasn't a way to update my phone. Thanks for your clarification on hboot, etc. Mattlock over on Android Forums has a good guide for rooting and he is good at step-by-step 'how to do it' and some explanation why for us newbies. My rooted phone works fine but my wife's stock phone with the update seems to get a lot of network failures. She has a lot apps and a stock SD card - she refuses to let me root her phone - superstitious kind.