3.26 (rooted) to 3.29 fails. Why? - EVO 4G Q&A, Help & Troubleshooting

Greetings all,
I am running 3.26 and rooted it using Unrevoked3. It is working great, including 4G here in St. Louis, etc. I searched for an answer to my question, but couldn't find an applicable answer. Here goes:
I have a good nandroid backup, and over the weekend, I tried to upgrade it using the 3.29 OTA update. The update failed, with the exclamation mark inside the triangle and the green guy to the lower right of it. Had to pull the battery, but it booted back up just fine.
Is the 3.29 updater failing because it sees root/s-off? What do I need to do in order to be able to get 3.29 on? Unroot and turn s-on somehow?
Thanks in advance, just trying to learn my way around.
-Rob

Well Rob when I did the update I was s-off so I know that does not make a difference. I rooted my phone the downgrade,unrevoked3, and unrevoked forever way. When the OTA came I put a stock ruu on my phone which probably unrooted it but kept the s-off. I then updated the phone then reinstalled the old bootloader and recovery soit was back to rooted. I don't know if that might help or not just thought I would tell you my way. Probably easier ways out there
Sent from my GiRLiE Evo

did you see this:
http://forum.xda-developers.com/showthread.php?t=790394

Related

Unrevoked Forever Questions

'Even if an “unrootable” OTA update is accepted, a device on which unrevoked forever has been run will still be able to reflash a custom recovery image.'
Ok, the statement above is straight from the Unrevoked Forever wiki. If this is true, I can update with the 3.70 OTA with no problems right?
At the very least, having to re-flash a recovery through Rom Manager?
Bump... come on guys...
I may be drunk but I think that weird ass sentence makes sense. If you run unrevoked forver the S-Off will stay off so even if you ota your s- will stay off and you only have to reflash your recoveries and roms.
Ok, I'm glad I'm not the only one who reads it that way.
In that case, what's the worst case scenario if I do the OTA. If the worst case is I'm unrooted, then that really doesn't matter now that Unrevoked 3.3 just came out for the 3.70 OTA, right?
Any chance of a brick?
I don't see why you want to do the OTA, there are lots of 3.70 custom roms already, you don't need any prerequisite to run them, just flash them and bam your on 3.70. so why OTA???
Well, I wanted to do the OTA because I was having problems with CWM 3.0.0.2. I have since flashed back to 2.5.0.1 and flashed a rooted 3.70 RUU. Everything went perfect.
On a side note, while still in CWM 3.0.0.2, I did try to apply the 3.70 OTA and it got stuck on the screen with an exclamation mark inside a triangle. I pulled the battery and rebooted and was back to normal. Still rooted and all. So, I guess Unrevoked really does what it says.
I'm sticking with CWM 2.5.0.1 until I hear anything different.

Non-rooted evo running 3.3 (how to restore recovery?)

Phone won't load recovery -
My phone currently has 2.3.3 and will not root because the firmware is too "new" according to Unrevoked.
How do I backtrack to 2.2?
Also, the phone is not rooted (s-on) and recovery once again will not load properly; i get the red exclamation.
Any help would be greatly appreciated, thank you.
There are a few threads addressing this issue already, and the short answer from what I have found in my research, because I too took the OTA update and have looked in to this myself, is that there is no option.
If you are S-ON and have the new Bootloader and newest OTA update, you just have to hang tight until the devs behind Unrevoked or other such methods figure out a workaround for the newest bootloader.
denxnis said:
Phone won't load recovery -
My phone currently has 2.3.3 and will not root because the firmware is too "new" according to Unrevoked.
How do I backtrack to 2.2?
Also, the phone is not rooted (s-on) and recovery once again will not load properly; i get the red exclamation.
Any help would be greatly appreciated, thank you.
Click to expand...
Click to collapse
Hey man, I am sorry to inform you that there is currently no root method for the software you're on. You can't downgrade to 2.2, the RUU won't let you do it. The new bootloader that you're on is not downgradeable, and it is still currently locked. Hopefully a new exploit is figured out soon, but for now you just need to wait it out. Or trade your Evo with someone who still has froyo!
Thanks for the info guys.
Not sure is any of this could render your phone without functionality and If you are willing to give it a shot, try the first part of my post. After I unrooted the defective EVO to accept the OTA (since it was going back in a day anyway and didn't care if the root was lost) adn it was along with my .76 Hboot. I was able to get root back by using the HBOOT in stock recovery and loading the RUU posted with of course loading the usb drivers. Now, to be honest, I never used unrevoked to begin with on that EVO, so never checked son/soff before.
If for some glorious reason you are able to load the ruu and it comes up...try the root option also posted from the link to xHausx.
Here's hoping....but reality will probably set in and a short wait is needed for a real method.
http://forum.xda-developers.com/showthread.php?p=14496385#post14496385
unfortunately no root for 2.3 but rumor has it that htc is working on unlocking the new bootloader with a update coming in the near future prob 2.3.4

S-OFF still showing after OTA?

My wife got her replacement Inc2 today after the one she got last week just died. She was on Froyo so I might of.. swapped her phones.. anyways, I rooted, went to the bathroom and the stupid ota ran I guess because when I came back the phone was on GB 2.3.3 however my boot screen shows S-OFF. Can anyone help me to verify that S-OFF is indeed still off. I can post any screen shots etc.. I am still a noob when it comes to the Inc2.
If your boot screen says S-Off, you are S-Off
Sent from my stock, bloated ADR6350 using XDA Premium App
Did you flash clockworkmod recovery when you rooted? I didn't think the OTA would take if you had a custom recovery. In any event, since you're still s-off, you're fine.
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
kujayhawks77 said:
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
Click to expand...
Click to collapse
Alpharev changed ur hboot to a higer version than the one in the OTA.. this is why it kept you S-OFF.. if I'm wrong someone correct me.
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
kujayhawks77 said:
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
Click to expand...
Click to collapse
No. stock hboot is .97. alpharev bumped you up to 1.something.. idk I used XTC clip.. since your hboot is newer than the OTA.. it keeps you S-OFF, pretty smart by alpha.
So does this open a gateway to first root in Froyo and then go gingerbread and retain the root?
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Now when I use the term "gateway" I say this loosely because it doesn't fix anything for anyone who is already on GB. If indeed this works, it would only work for a small percentage who get Froyo and don't flash clockwork before running the OTA.
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
tnez said:
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
Click to expand...
Click to collapse
2.1??? I think you are mistaken, sir
beenz said:
2.1??? I think you are mistaken, sir
Click to expand...
Click to collapse
He was mistaken cause it is sense 2.1 but android 2.2
Sent from my Incredible 2 using XDA Premium App
kujayhawks77 said:
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Click to expand...
Click to collapse
I've been wondering about this. I got my Dinc2 early July and I'm still on stock, unrooted Froyo. Somehow the OTA update to GB hasn't hit yet. Could I run ApharevX to get S-off and stop there for now? I am happy with bloated stock for the time being and want to be able to receive OTA updates, but would like to have the option down the road to add Clockworkmod and flash custom ROMs. From kujayhawks experience it seems that this should be possible.
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
P.S. First post, though I've been lurking around for a while. Great forum/community.
xenakis said:
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
Click to expand...
Click to collapse
It appears from reports that S-off stays after the OTA to 2.3, so yea, that would seem to be the case.
If you turn S-off with AlphaRev, you might want to just go ahead and install Clockwork recovery at the same time. Doing so won't root or install SuperUser or anything, but you would be able to then backup your phone and be ready to flash if you wanted.
If you install clockwork recovery you won't be able to receive OTAs though, just keep that in mind. You can flash back to the stock recovery, but unless you are familiar with ADB, it won't necessarily be an easy process.

[Q] Help, please. Need to Root 2.3.4 DINC

Ok, a few users here have offered advice/assistance, but I fear this problem has been forgotten.
I am stuck with an S-ON, 2.3.4 Droid Incredible, and am looking for a way to acquire root again.
This happened a few weeks ago, with the leak of the 2.3.4 OTA. Flashed S-ON via CWM (not aware I would permanently lose Root), then flashed the OTA as PB31IMG.zip in HBOOT.
Now, Unrevoked no longer roots the device. HBOOT will not allow downgrading to a 2.2 IMG, nor will it flash any downgraded Radio/HBOOT versions. I've tried them all from Dougpiston.com, even the signed ones.
I've attempted to contact the folks at Unrevoked about this issue on IRC, but I can't ever get a reliable dialogue going with anyone, and I believe they are busy working on Revolution, for Incredible 2/S & Newer devices.
Throwing my hands up, I even called Verizon, gave them an excuse to send me a replacement, just so I could start fresh with a 2.2 phone, but I am out of warranty.
I really want to enjoy Sense 3.0/MIUI, even Cyanogenmod, but the outlook is not so good.
Is there any solution I haven't tried yet? Please help.
Unless Unrevoked or someone else finds a new root method you're pretty much out of luck.
Sent from my Droid Incredible 3D using XDA App
Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4
resyek83 said:
Yep, same situation here, nothing will re-root if you did the GB OTA with S-ON bootloader. just have to wait and see if somebody comes up with something new or Unrevoked comes up with a new method.
EDIT: and I'm willing to bet if you get one from Verizon it might already be 2.3.4
Click to expand...
Click to collapse
That's most likely true. 2.3.4 is being pushed out to the Incredible now, so they would probably run the newest RUU on their Incredible devices.
I feel your pain deadsoulboy, and I've seen your posts lamenting your situation on other threads. Only solace I can offer you is that generally the source code and RUU are made available within 30 days of the OTA, at which point the developers are completely free to tear into them with reckless abandon and hopefully the folks at unrevoked figure things out.
It's also distinctly possible that HTC will unlock the bootloader the way it has with others of its handsets, in which case you'll be back in business.
Until then, my friend, I believe you are rootless.
i have the same problem. its been a couple months.... am i still hosed?
Have you tried this? http://forum.xda-developers.com/showthread.php?t=1306400
I used Scotty1223's instructions a few weeks ago and it worked like a charm.
So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.
alexyaz said:
So I burnt out my Cpu on my original rooted Dinc and got a replacement however after playing around on my replacement Dinc verizon pushed the update to 2.3.4 onto my phone. I would've stopped it but I figured I would just downgrade and root again however the new HBOOT 92 didn't let me downgrade i tried the unrevoked method anyway and i got a custom recovery so i restored MIUI on my current Dinc however i seem to still be unrooted? for example Titanium Backup can't delete system apps. i still have S-on and the new HBOOT 92 however i also have a mac so i am a little stuck and confused on how to regain full root access with s-off again any hep would be greatly appreciated.
Click to expand...
Click to collapse
Check this out. http://androidforums.com/incredible-all-things-root/427344-2-3-4-root-downgrade-s-off.html

updated dinc no root, no tether

Hi all,
Here is my problem, the other day when updates were being pushed out by VZW my Incredible updated, I woke the next morning and found that I had no root and no way to tether. I have tried unrevoked3 and followed all instructions and still no luck on the matter. I even re-downloaded everything and nothing. Can anyone help me with this.
dexcaliber said:
Hi all,
Here is my problem, the other day when updates were being pushed out by VZW my Incredible updated, I woke the next morning and found that I had no root and no way to tether. I have tried unrevoked3 and followed all instructions and still no luck on the matter. I even re-downloaded everything and nothing. Can anyone help me with this.
Click to expand...
Click to collapse
I'm presuming the gingerbread update reset your recovery to stock. First of all, unrevoked doesn't work on the gingerbread OTA that you received. However, if you're S-OFF you're still in luck. First check if you are. Go to HBOOT and at the top next to the HBOOT version it will either say S-OFF or S-ON. If you rooted with a recent version of unrevoked you should be S-OFF unless you manually flashed S-ON. Then read through the site below
http://pvillecomp.com
It willl instruct you how to boot into HBOOT and flash an image to get clockworkmod back. Then you should be able to flash a custom recovery again or superuser to get root back. I don't know offhand about the superuser flashing but if you flash wildstang's OTA ROM you will have root again.
Check out this thread if you're updated to GB 2.3.4:
http://forum.xda-developers.com/showthread.php?t=1306400
EDIT: Read the link I posted, but follow what Tiny is suggesting, he'll get you squared away!

Categories

Resources