i have been trying to take the lastest OTA (2.11.651.19) update. i get the following error when trying to install the OTA. i have RUU the device several times to the 2.11.651.11 then as soon as i get done with the sign in i go directly to the OTA update and the follow occures in recovery mode when flashing.
E: missing bitmap oem_unlock_bg
(code -1)
E:missing bitmap oem_unlock_bg_yes
(code -1)
E:missing bitmap oem_unlock_bg_no
(code -1)
E:find no match partition: for package path @/cache/recover/block.map
finding update package...
opening update package...
verifying package...
installing update...
L51QCT.01.103.027
verifying current system...
/dev/block/bootdevice/by-name/system has been remounted r/w
reflash device to reenable ota updates
E: error in @/cache/recovery/block.map
(status 7)
installation aborted.
OTA failed! please power off the device to keep it in this
tate and file a big report!
any ideas what is causing this?
My advice would be to wait until OMJ is finished making the zips/RUU to flash. If not Start at number 8 in 2nd post here http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
schmeggy929 said:
My advice would be to wait until OMJ is finished making the zips/RUU to flash. If not Start at number 8 in 2nd post here http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
Click to expand...
Click to collapse
unfortunately I'm having the same issue...not sure what the deal is...may have to wait for RUU to be posted.
OMJ said:
unfortunately I'm having the same issue...not sure what the deal is...may have to wait for RUU to be posted.
Click to expand...
Click to collapse
That's why I wait for you geniuses to come up with the right answers, LOL
I've only seen @formulabird say he was successful in updating, I'm wondering if there's others...maybe if this forum wasn't so dead...
I downloaded the update but haven't applied it yet as I too am waiting to see if the radio has been updated. Right now my radio is rock solid and I'd hate for this update to take a dump on it.
Sent from my 0PJA2 using Tapatalk
Why is this forum so dead. Been running up date since yesterday. I am completely stock. First time I haven't unlocked my phone only because there seems to be a lack of interest in it.
Sent from my 0PJA2 using XDA Free mobile app
formulabird said:
Why is this forum so dead. Been running up date since yesterday. I am completely stock. First time I haven't unlocked my phone only because there seems to be a lack of interest in it.
Sent from my 0PJA2 using XDA Free mobile app
Click to expand...
Click to collapse
Post a screen shot of software firmware screen, is there a new radio ?
Sent from my 0PJA2 using XDA Free mobile app
formulabird said:
Sent from my 0PJA2 using XDA Free mobile app
Click to expand...
Click to collapse
Looks like a new radio. Any thoughts on the radio so far?
Sent from my 0PJA2 using Tapatalk
formulabird said:
Sent from my 0PJA2 using XDA Free mobile app
Click to expand...
Click to collapse
@formulabird thx..but it would be helpful if u could post the info I requested via pm...no one else is showing to have the new ota installed...
*edit* looks like the ota is finally installing for me, so I'll be able to pull that info myself...
---------- Post added at 11:20 AM ---------- Previous post was at 10:33 AM ----------
finally... I had to RUU back to 1.32, then manually apply the 2.6 ota, then manually apply the 2.11 ota
it appears the 2.6 RUU checksum does not match the 2.11 ota causing it to fail...nice one HTC
OMJ said:
@formulabird thx..but it would be helpful if u could post the info I requested via pm...no one else is showing to have the new ota installed...
*edit* looks like the ota is finally installing for me, so I'll be able to pull that info myself...
---------- Post added at 11:20 AM ---------- Previous post was at 10:33 AM ----------
finally... I had to RUU back to 1.32, then manually apply the 2.6 ota, then manually apply the 2.11 ota
it appears the 2.6 RUU checksum does not match the 2.11 ota causing it to fail...nice one HTC
Click to expand...
Click to collapse
Good glad it worked out sorry. Would have been more then happy to try and pull it for you. Work sucks this time of year!!!
OMJ said:
@formulabird thx..but it would be helpful if u could post the info I requested via pm...no one else is showing to have the new ota installed...
*edit* looks like the ota is finally installing for me, so I'll be able to pull that info myself...
---------- Post added at 11:20 AM ---------- Previous post was at 10:33 AM ----------
finally... I had to RUU back to 1.32, then manually apply the 2.6 ota, then manually apply the 2.11 ota
it appears the 2.6 RUU checksum does not match the 2.11 ota causing it to fail...nice one HTC
Click to expand...
Click to collapse
Good catch. That's why you guys are the pros!
Sent from my 0PJA2 using Tapatalk
We have the OTA issue worked out look HERE
I am stock, never rooted, never unlocked, S-ON. I can't take the OTA because I installed the .11 updated with the RUU. I can't RUU back to the 1.32.xx releases (tried both .17 and .30). I get "Failed: -2, 19: failed to flash via downloadzip" every time.
Am I screwed until they release the updated RUU?
Does anyone have a stock system image for 2.6.651.11?
kwolf said:
I am stock, never rooted, never unlocked, S-ON. I can't take the OTA because I installed the .11 updated with the RUU. I can't RUU back to the 1.32.xx releases (tried both .17 and .30). I get "Failed: -2, 19: failed to flash via downloadzip" every time.
Am I screwed until they release the updated RUU?
Click to expand...
Click to collapse
yep...HTC failed big time w/ this OTA, those that ran the .11 RUU will not be able to update
being s-on, u cannot flash older RUU's...your options are to wait for new RUU or s-off, flash 1.32 RUU, then take the otas 1 at a time
personally I'd call HTC & complain, maybe they'll release the new RUU sooner
I gave that a shot but their support was useless. Told me to basically sit and wait and it might be released in a month.
Edit: I gave it a second shot and got it escalated, so hopefully it can be fixed.
kwolf said:
I gave that a shot but their support was useless. Told me to basically sit and wait and it might be released in a month.
Edit: I gave it a second shot and got it escalated, so hopefully it can be fixed.
Click to expand...
Click to collapse
@kwolf, RUU time...
http://forum.xda-developers.com/showpost.php?p=62801151&postcount=480
Just wanted to thank OMJ!
Thanks for the info here, and in the main thread here;
http://forum.xda-developers.com/sprint-one-m9/development/ruu-sprint-htc-one-m9-1-32-651-17-t3073355
I was able to use the info you posted to fix my phone after taking the OTA for 2.11.651.19, which caused me a few problems. I got my M9 on Sprint 2 weeks ago, and it worked great, and then the morning of the 2.11.651.19 update the phone wouldn't connect to my car stereo through Pioneer's bluetooth touchscreen integration, and the phone's screen wouldn't turn off without the power button.
I was able to unlock the bootloader, flash TWRP recovery, gain root, and then go S-OFF to be able to flash the previous 2.6.651.11 RUU from HTC's site.
The phone is working perfectly again! The screen turns off, and it connects to my car stereo immediately through bluetooth!
Even though I flashed the official RUU, my bootloader screen still shows "software modified", "Bootloader Unlocked", and "S-OFF", but I definitely do not have root anymore (of course). And I also won't be able to take the stagefright patch, since it is tied in with 2.11.651.19, which didn't work for me... Unless HTC and Pioneer want to fix their issues. I've emailed both, and no reply at all.
Related
So i was kinda scared but i knew this day would come, VZW is pushing a update to all rezounds with H-boot 2.11. Concitering we dont have S-off yet this usually wouldnt be a problem but H-boot 2.11 breaks temp root. I have been using it for a while and it fails to push SU.
Just a warning so no one gets stuck without root
What about the people who are fully unlocked with perm root ? What happens if we run the update
Update failed in recovery for me. I've deleted some bloat though.
Sent from my ADR6425LVW using XDA App
Easton999GS said:
What about the people who are fully unlocked with perm root ? What happens if we run the update
Click to expand...
Click to collapse
As far as I can tell, the update will not run. I let it download to my Rezound and then it auto-restarted after 3 minutes. Booted into recovery and said update failed. I rebooted from recovery and once booted up, I got a message saying "No new software update available" or something to that effect. Clicked "Finish" and since then, my phone has been working like before. From what I just experienced, there is no harm to your phone if you let it try to install, but nothing will happen either, so there is no benefit.
k_flan said:
Update failed in recovery for me. I've deleted some bloat though.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
were you unlocked?
i dont think it should effect anyone who is unlocked but dont hold me to that
You can only update radios when your device is locked or relocked. The ? Is can we unlock after we are on hboot 2.11
Mechadan said:
As far as I can tell, the update will not run. I let it download to my Rezound and then it auto-restarted after 3 minutes. Booted into recovery and said update failed. I rebooted from recovery and once booted up, I got a message saying "No new software update available" or something to that effect. Clicked "Finish" and since then, my phone has been working like before. From what I just experienced, there is no harm to your phone if you let it try to install, but nothing will happen either, so there is no benefit.
Click to expand...
Click to collapse
try putting stock recovery on the device.
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
Easton999GS said:
You can only update radios when your device is locked or relocked. The ? Is can we unlock after we are on hboot 2.11
Click to expand...
Click to collapse
This is what I'm waiting to know.
Easton999GS said:
You can only update radios when your device is locked or relocked. The ? Is can we unlock after we are on hboot 2.11
Click to expand...
Click to collapse
i would assume so because the unlock is directly from HTC to anser the second part of your Q
andybones said:
try putting stock recovery on the device.
---------- Post added at 06:14 PM ---------- Previous post was at 06:13 PM ----------
This is what I'm waiting to know.
Click to expand...
Click to collapse
I am rather new... I'm not entirely sure:
1) How to get stock recovery back, haha.
2) If I even want to get it back. If HBoot is updated by this OTA, I don't know that I want it running and screwing up my root. Is that possible if I am unlocked and perm-rooted?
To be clear, I am willing to experiment for your guys' benefit, but would just like to be sure what I am getting myself into.
werdna87 said:
were you unlocked?
i dont think it should effect anyone who is unlocked but dont hold me to that
Click to expand...
Click to collapse
Yeah, unlocked. I'd be surprised if unlocked breaks it though. Im guessing its that I'm running AR recovery or because I've messed with system apps.
Sent from my ADR6425LVW using XDA App
werdna87 said:
i would assume so because the unlock is directly from HTC to anser the second part of your Q
Click to expand...
Click to collapse
If that is the case then we could get root back and get back on cusom recovery, hopefully someone who has accepted the OTA will see if they can unlock it.
I'm trying to get back to stock and test to see if we can unlock but It takes forever to get back to stock.
Mechadan said:
I am rather new... I'm not entirely sure:
1) How to get stock recovery back, haha.
2) If I even want to get it back. If HBoot is updated by this OTA, I don't know that I want it running and screwing up my root. Is that possible if I am unlocked and perm-rooted?
To be clear, I am willing to experiment for your guys' benefit, but would just like to be sure what I am getting myself into.
Click to expand...
Click to collapse
I'm not entirely sure but if you are willing to experiement that would be huge.
it does update to 2.11 hboot, so the question is can you then do the unlock and root again.
i think you need to be on stock recovery to the update to take.
but dont hold me to any of this.
andybones said:
I'm not entirely sure but if you are willing to experiement that would be huge.
it does update to 2.11 hboot, so the question is can you then do the unlock and root again.
i think you need to be on stock recovery to the update to take.
but dont hold me to any of this.
Click to expand...
Click to collapse
OK, well I can't do anything here from work, so when I get settled at home later tonight, I will see what I can do. I don't mind losing root until someone can figure out a workaround for those stuck with 2.11 hboot, mainly because a custom ROM is the only benefit I use from root at the moment. I can't figure out tethering to my Transformer Prime for the time-being anyhow, so losing Nils' ROM is a hit I'm willing to take for a bit.
If someone else does not figure out what you need before later tonight, I will do what I can.
By the way, it would help if you set up some steps for me. Like, do you want me to restore stock recovery, then check to see if stock recovery and custom ROM lets me install the update, then if it doesn't work, go back to stock everything and see if it works, then if it doesn't work go to relocked and see if it works? Just lay out each operation you want me to do to test your theories. I know far too little to be making up my own procedures. Inevitably, I'll finish and people will say, "Well, what about... and what about..."
I just don't want to waste my time or yours.
just letting everyone know, if you were one of those ppl who ran the ruu leak and get a mainversion error, your ****ed. you cant update and you cant change the text cause then it fails the sig check
Easton999GS said:
just letting everyone know, if you were one of those ppl who ran the ruu leak and get a mainversion error, your ****ed. you cant update and you cant change the text cause then it fails the sig check
Click to expand...
Click to collapse
So this happened to you?
con247 said:
So this happened to you?
Click to expand...
Click to collapse
yep yep.... we can't RUU back to stock, or apply this new update... we need the actuall RUU file for this new update before we will be able to do anything.
con247 said:
So this happened to you?
Click to expand...
Click to collapse
no but i know it wont work. it will fail when it tries to update the kernel part. i also cant even restore an RUU because the RUU gets the mainver error, and yes i relocked the phone before i tried to restore.
Easton999GS said:
just letting everyone know, if you were one of those ppl who ran the ruu leak and get a mainversion error, your ****ed. you cant update and you cant change the text cause then it fails the sig check
Click to expand...
Click to collapse
thank you for this.
---------- Post added at 06:51 PM ---------- Previous post was at 06:49 PM ----------
jskolm said:
yep yep.... we can't RUU back to stock, or apply this new update... we need the actuall RUU file for this new update before we will be able to do anything.
Click to expand...
Click to collapse
u can RUU back to stock pulling the rom.zip from the stock ruu
Damn guys... sorry about that.
Hey All,
I am trying to install the OTA for ICS that was released by Rogers today for my EVO 3D.
I am rooted and unlocked but with the stock Rogers ROM and I also have S-OFF.
The problem I am running into is that I am able to download the upgrade but when I go into HBoot and try to apply it I get a signature verification failed.
Originally I thought it might have been a bad download so I downloaded it a 2nd time, same result.
So I thought, what the hell, I will turn off the signature check and try it again. This time I get an error that the 'assert failed: check_cid(getprop("ro.cid").' and the installation aborted.
Does anyone have any insight into why this would fail? I am hoping to apply this but not sure why its a no go.
Thanks for the help in advance.
Cheers, Crash
Have you ever changed your cid? run "fastboot getvar cid" and post what it says. If your cid is original for rogers, the ota may not be working because you are s-off.
Hey @patrick92260
I have not checked my CID, not really sure how actually.
In order for me to run that command I would have to be hooked up to ADB I assume? If so thats going to need to wait until I get home tonight to try that and give you the results, unless there is another way I can run that command?
Thx for the reply
Yeah it's done through ADB. If you don't really know what the cid is, you probably haven't changed it. If you have the stock recovery, then the reason the ota isn't working has to be because you are s-off. you will probably have to wait for an RUU to upgrade to ICS.
Makes sense then. Would setting S-ON make it so I can apply it? Or would that not be worth the effort?
Honestly I can wait a bit longer, we have been waiting this long for it
Thx for the help.
But you should be able to get back to S-ON by flashing Gingerbread RUU, no?
If you originally used revolutionary to get s-off, then you have radio s-off which is the highest level of s-off you can have and i would not recommend trying to set it back to s-on. i also have a rogers evo 3d and i am using the asian RUU ICS and it works fine while letting me keep s-off after flashing it so i would recommend using that RUU if you want ICS.
---------- Post added at 01:10 PM ---------- Previous post was at 01:07 PM ----------
SaHiLzZ said:
But you should be able to get back to S-ON by flashing Gingerbread RUU, no?
Click to expand...
Click to collapse
If he has radio s-off you can flash any RUU you want and it will not turn it back to s-on. Radio s-off is basically permanent since it removes the data in the S58 section of the phone. The fake s-off is the one you need to be careful with which is usually done by using a hacked hboot.
patrick92260 said:
If your cid is original for rogers, the ota may not be working because you are s-off.
Click to expand...
Click to collapse
Bull**** Bull**** Bull****.
For getting OTA you need NOT rooted and NOT deodexed Stock-rom+stock recovery.
Don't try to make S-ON, it is great chance to brick the phone.
And your CID you can get with cid getter from the market.
Patrik, stop it plz.
Is there any risk or advantage to used to Asia one? Not sure I want to have that one my phone over the NA ones.
Would there not be a RUU or this Rogers release? Maybe I should just say the hell with it and just ROM it?
Kemanorell said:
Bull**** Bull**** Bull****.
For getting OTA you need NOT rooted and NOT deodexed Stock-rom+stock recovery.
Don't try to make S-ON, it is great chance to brick the phone.
And your CID you can get with cid getter from the market.
Patrik, stop it plz.
Click to expand...
Click to collapse
lol good one, so why would my evo 3d not flash the ota with a completely stock rom and recovery then with no root? only thing it had was s-off.
---------- Post added at 01:28 PM ---------- Previous post was at 01:24 PM ----------
Crash1912 said:
Is there any risk or advantage to used to Asia one? Not sure I want to have that one my phone over the NA ones.
Would there not be a RUU or this Rogers release? Maybe I should just say the hell with it and just ROM it?
Click to expand...
Click to collapse
It's a toss up if the RUU for rogers or the europe ICS ever shows up here. I am using the asian one and don't really notice any difference over the rogers or europe update. If you have radio s-off you can always downgrade by flashing a gingerbread RUU if you don't like the asian ICS RUU.
I had to run the Rogers gb ruu 1.20.631.2. It then update to 631.3 when I checked for updates. I then booted checked for updates again and it updated to ics. Now I'm running official Rogers ics but as I said I had to roll all the way back 1.20.631.2 and update all the way up from there.
And it does update the hboot but you can downgrade it with ruu previously mentioned.
Sent from my HTC EVO 3D X515a using Tapatalk 2
healer82 said:
I had to run the Rogers gb ruu 1.20.631.2. It then update to 631.3 when I checked for updates. I then booted checked for updates again and it updated to ics. Now I'm running official Rogers ics but as I said I had to roll all the way back 1.20.631.2 and update all the way up from there.
And it does update the hboot but you can downgrade it with ruu previously mentioned.
Sent from my HTC EVO 3D X515a using Tapatalk 2
Click to expand...
Click to collapse
Please link how this is done. I quickly scammed google, and couldnt find how to roll back to this. Looking to do ICS update today sometime.
js593 said:
Please link how this is done. I quickly scammed google, and couldnt find how to roll back to this. Looking to do ICS update today sometime.
Click to expand...
Click to collapse
Somewhere in the development thread there is a thread with shipped ruus already covered to pg86img.zip. Just find the Rogers one and put it on the root of your sd card and boot into bootloader. It will detect it and install 1.20.631.2 then just manually check for updates under about phone. The first update should be 1.20.631.3 which is 9.35mb then xcheck again and it's the ics update around 306 mb. Sorry I can't link to it you'll have to search the development forum. I've had it since it was posted way back when on my phone.
Make sure it's renamed PG86IMG.zip
http://forum.xda-developers.com/showthread.php?p=16450859
Sent from my HTC EVO 3D X515a using Tapatalk 2
healer82 said:
Somewhere in the development thread there is a thread with shipped ruus already covered to pg86img.zip. Just find the Rogers one and put it on the root of your sd card and boot into bootloader. It will detect it and install 1.20.631.2 then just manually check for updates under about phone. The first update should be 1.20.631.3 which is 9.35mb then xcheck again and it's the ics update around 306 mb. Sorry I can't link to it you'll have to search the development forum. I've had it since it was posted way back when on my phone.
Make sure it's renamed PG86IMG.zip
http://forum.xda-developers.com/showthread.php?p=16450859
Sent from my HTC EVO 3D X515a using Tapatalk 2
Click to expand...
Click to collapse
Would this be it?
http://forum.xda-developers.com/showthread.php?p=22501510&highlight=rogers#post22501510
js593 said:
Would this be it?
http://forum.xda-developers.com/showthread.php?p=22501510&highlight=rogers#post22501510
Click to expand...
Click to collapse
That seems to be the one yes.
Sent from my HTC EVO 3D X515a using Tapatalk 2
Ive tried to do this, after downloading it and putting it in the root directory of my phone. Hboot sees the image, stalls there for a few seconds then continues. nothing has happened. Ive tried installing it from CWM, no difference. I think i may need a bit more help then this. After it was detected, i did go and see if it was downgraded in the ABOUT, but it sits at .3 still.
Any ideas?
Okay, so for those people out there that are looking to do this, here's the functional way it worked for me (no errors, nothing happened during the update)
Download the .exe file,
EXECUTE the exe file from windows while the phone is plugges in. This will revert back to .2
Put phone into a wireless network once back up and running.
Update the phone as neccessary.
After the update, i noticed my Hboot when to 1.53.007. Now we just need to wait for a root.
Also, when i went into Recovery from Hboot, i noticed that it didnt do anything, sat there with a pic of my 3D and it had a red exclamation point. should that happen?
no luck
hi i have tried every method here with no go. i have s-on and phone is rooted. can some one post a working rom or something for the love of android!
looks like it was the bootloader it needs to be relocked using rootevo3dnew.zip. which will allow you to downgrade using the ruu file in windows. followed by the 2 updates in about phone and i got the ICS yay! if you have trouble search youtube for the video on "relocking evo 3d bootloader" it was easy, good luck ppl.
So I was driving down the road today and noticed that I could do an OTA...being extremely green to HTC, android, and rooting...I accepted. Then I noticed that things weren't working like they were before the update. Doh!
Came home...hopped on here and noticed that was very stupid. No more root.
So I have S-Off and bootloader unlocked (did when I got home) but no root. Is there a way for me to get it back?
Thanks in advance!
Nevermind, was useless.
roids87 said:
http://forum.xda-developers.com/showthread.php?t=1671577
That thread will help you out.
Click to expand...
Click to collapse
That method no longer works on the ota update.
If you're S-Off with bootloader unlocked all you have to do is grab a custom recovery and flash a superuser package. Since you're green here are some links.
http://forum.xda-developers.com/showthread.php?t=1675738 - recovery
http://forum.xda-developers.com/showthread.php?t=1538053 - superuser
OTA and new to root
I too am new to rooting my device. I rooted with RegawMod and love it but I can't get the OTA update to even work. I tried to download the jewel update from this website
http://forum.xda-developers.com/showthread.php?t=1766628
I couldn't figure out what to open to make it work. I am new to the rooting so I could use some help.
thanks
triscuit1983 said:
If you're S-Off with bootloader unlocked all you have to do is grab a custom recovery and flash a superuser package. Since you're green here are some links.
http://forum.xda-developers.com/showthread.php?t=1675738 - recovery
http://forum.xda-developers.com/showthread.php?t=1538053 - superuser
Click to expand...
Click to collapse
Thanks! This is great! Going to check it out now.
Same here. I am rooted running MeanRom and today when the ota started, I cancelled it thinking it might mess something up with my root. I went to do the update this evening because I read users were getting better 3g speeds and what not, but when I go to install, it just reboots into recovery and so I followed with a reboot system in twrp and when it fully reboots, I get nothing.
Sent from my EVO 4G LTE using XDA-Developer App
Same here. On fresh rom. Just goes to recovery and doesn't finish the update. Any ideas?
EVOMIKE025 said:
Same here. I am rooted running MeanRom and today when the ota started, I cancelled it thinking it might mess something up with my root. I went to do the update this evening because I read users were getting better 3g speeds and what not, but when I go to install, it just reboots into recovery and so I followed with a reboot system in twrp and when it fully reboots, I get nothing.
Sent from my EVO 4G LTE using XDA-Developer App
Click to expand...
Click to collapse
Sent from my EVO using xda app-developers app
I would say to just wait until the devs update the roms we are using with the ota. It seems as though I'm reading its doing something with the bootloader and installing a stock rom?
Sent from my EVO 4G LTE using XDA-Developer App
I'm thinking if I lock and unroot, I should be able to get update? I tried just going ahead with update but it keeps booting to twrp. I can reunlock and root after right? Im too novice to use s-off method.
Sent from my EVO using xda app-developers app
I'm actually not on S-OFF and its doing the same. I would say unroot and then try updating. Once you unroot, it should go back to stock automatically
Sent from my EVO 4G LTE using XDA-Developer App
S-Off is something you guys will want eventually and updating the Hboot will more than likely keep you away from that. Just sit tight and wait on the Rom of your choice to be updated or download the rooted update within the development forum.
That's what I was trying to suggest doing. I'm not really interested in the update as of right now.... Sitting tight! Lol
Sent from my EVO 4G LTE using XDA-Developer App
Not Happy....post 1.22.651.3
Guess this is what I get for not understanding the update before I installed it. Used Voodoo OTA RootKeeper, thought I was good to go. I should have known something was amiss when the update was a HTC software update and not a Firmware update. Not only did it nix my root, I can't even get to recovery, it blocked it.
My current configuration is:
TAMPERED
LOCKED
Jewel PVT SHIP S-ON RL
So I am thinking I am pretty much toast. Not real interested if flashing ROMs at this point, just wanted Root.
This totally s__ks. And 3 days before they light up LTE in my area, ugh.
i unrooted and relocked phone by installing ruu in order to get ota update. i received update just fine. problem is ive tried to root again using regaw root and the other root method. regaw got me unlocked and recovery but when it got to installing root files said error cannot mount system as rw. hope this helps cause i am one who di try it by goin back stock. and thanks to all you devs. this is the GREATEST place to learn anything about any android phone. i just hopw you guys come up with a way foe me to root my phone soon. and oh yeah my phgone did accept the twrp recovery, i was wonderin if i could install some type of zip file thru twrp to regain root. no i do not have su, never got it when i tried to root
---------- Post added at 04:01 AM ---------- Previous post was at 03:49 AM ----------
my data connection is worse with new radios. went from ave. of 500 kbs to 220. ive done everything ican to try to improve that. all the ## stuff to reactivating. nothin is helping. im in ohio. voice stayed the same 2 signal bars
---------- Post added at 04:15 AM ---------- Previous post was at 04:01 AM ----------
treIII said:
i unrooted and relocked phone by installing ruu in order to get ota update. i received update just fine. problem is ive tried to root again using regaw root and the other root method. regaw got me unlocked and recovery but when it got to installing root files said error cannot mount system as rw. hope this helps cause i am one who di try it by goin back stock. and thanks to all you devs. this is the GREATEST place to learn anything about any android phone. i just hopw you guys come up with a way foe me to root my phone soon. and oh yeah my phgone did accept the twrp recovery, i was wonderin if i could install some type of zip file thru twrp to regain root. no i do not have su, never got it when i tried to root
---------- Post added at 04:01 AM ---------- Previous post was at 03:49 AM ----------
my data connection is worse with new radios. went from ave. of 500 kbs to 220. ive done everything ican to try to improve that. all the ## stuff to reactivating. nothin is helping. im in ohio. voice stayed the same 2 signal bars
Click to expand...
Click to collapse
im also s-on
root
hey guys,
very similar situation -
my phone never got 'auto updates' turned off, so on saturday it accepted the update and installed over my rooted evo lte. i have no custom recovery or unlocked bootloader. the phone now does not receive calls/texts (can send/call out fine) i cannot get it to flash back tothe stock RUU b/c i keep getting 171 usb errors. Is there a way to reroot it on the 1.22 software? i figure if i can root it, i can then unlock the bootloader and install a previous version on it to get it back to OEM settings. if it doesnt fix my communication errors, i can at least take it to sprint to get a new unit.
thanks
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
if you updated to the latest OTA update; that usually updates your radios and your Hboot which means the old RUU won't work because it has an OLDER HBoot and radios. Your gonna have to wait till the new OTA becomes available as an RUU to be able to go back to stock.
if you didn't take the OTA 2.13 and you are still on 1.22 then try putting your phone on Fastboot and try it that way.
Edit: Ok so it looks like the latest RUU has been uploaded. Look here http://www.filefactory.com/f/b6eb73c80cc97030/
Thanks, I will try fastboot.
However, as I said in the OP, I am on the same version (1.22.651.3) as the RUU I am using...
ronnienyc said:
I have a rooted and S-on Evo. The RUU keeps failing, even after I unrooted via the Superuser app.
Keep getting “ERROR [155]: UNKNOWN ERROR” and then it says it can not update the phone.
And then “Please get the correct ROM update utility and try again.”
I am definitely using the correct RUU version. 1.22.651.3.
Also I have tried two different computers and two different USB cables.
Does anyone know how to get this thing working?
Click to expand...
Click to collapse
I ran into the same error 155 issue.
I found the solution and it's quite simple. In the instructions to unroot, they forget to mention that you MUST relock your bootloader (instructions below). Once you relock it, then you can run the RUU for 1.22.651.3.....after that, take the stock OTA update.
http://www.theandroidsoul.com/how-to-re-lock-htc-one-x-bootloader/
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Is there another site with the new ruu?
Sent from my EVO using Tapatalk 2
running "fastboot oem lock" yields "waiting for device," and this stays on the screen forever. It doesn't work...
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Hypeo said:
It helps to have HTC Sync installed too
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct - this is an important step too. HTC Sync must be fully installed, drivers and all.
---------- Post added at 11:04 PM ---------- Previous post was at 11:01 PM ----------
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
Congrats!
That's my plan, except I'm keeping the stock ROM. If you find a way to Root, let me know - I tried RegawMOD, but I could not get it to work
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
ronnienyc said:
OK, finally got it to lock. Now, trying to see if I can get that RUU to work...it seems to be working. I think the issue was that I was not properly in fastboot mode.
So my plan is this:
RUU
OTA (to get the latest kernel and such)
Root/Unlock
MeanROM
Click to expand...
Click to collapse
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
I suggest no OTA as well!
Rxpert said:
I would highly suggest NOT taking the OTA...
The reason they now have a new h-boot is because there was a vulnerability in the old one.
Simply flash a new ROM based on the lastest OTA.
Click to expand...
Click to collapse
That's not always true, and almost all new major releases come with a new hboot. In fact I can't remember any updates on my 0g evo, evo 3d, and evo LTE, that didn't come with a new hboot. The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
The fact of the matter is, people that are s-on and hboot 1.15 won't be able to upgrade their radios and firmware unless they take the ota or run the ruu. This update makes the phone fly and is worth it.
On the other post, regaw mod does work with unlocking and installing twrp, you will have to install a rooted rom afterwards though because regaw mod fails at the rooting step.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
Sweet this is actually the point where I'm at. HTC Dev unlocked, s-on, hboot 1.15 and rocking twrp. I've been trying to parse through all of the numerous posts on a method to go ahead and install the ota updates. I actually believe I'm 2 down as I haven't updated ever and I got the phone @ launch. I recall reading somewhere that just going back to the stock recovery is a viable option if I want to go w/ the ota updates. I don't really have any interest in different ROMs (I scratch that itch w/ my evo 3d).
tl;dr Whats the least painful way to install the OTA updates post HTC Dev unlock, s-on, twrp recovery, and hboot 1.15?
Hey guys,
I was running the latest Viper rom. Every great once in a while the phone would just turn off. I could get it back fine and this happened about 5-6 times. Today the phone got stuck in a boot loop. I figured something went wrong.
I attempted to restore the phone to stock using the RUU thread found here: http://forum.xda-developers.com/showthread.php?t=2152993
I restored it once fine, said it was good. Phone only rebooted over and over. The HTC logo came up 3-4 times then screen went blank. So I flashed again. Same thing, nothing.
Now I had been playing around and think I updated my radio. Now the RUU from that thread above says it cannot upgrade my phone. I can get to fastbook and lock and unlock the bootloader. I did install latest TWRP but it never enters recovery. I had hoped to just install a basic rom from the 2.04 update and be done. But I cannot get into recovery.
I'm stuck and don't know what else to do. Is there and RUU file like the one above for the new 2.04?
I still think something else is wrong with this phone. Somehow doubt VZW will take it back and exchange.
S-ON
Phone displays HBOOT-1.33.0001
RADIO-1.01.01.0110
Any ideas what I can do next please?
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Tersanyus said:
I think the radio got updated when I tried to do S-OFF. Instead of an error at step 3 it flashed. Now I've gone back and tried it again and though I get the proper errors is still shows S-ON. Maybe this isn't even needed. I think my days of tinkering with Android should be over. I can follow guides and such
When I try to enter recovery for TWRP I get a lot of colored lines. Going to try reflashing that and see what gives. I feel that if I could get into TWRP and get a rom file on the phone since I cannot get into Android I might have a chance.
Click to expand...
Click to collapse
Did you take the verizon update as you mentioned 2.04? If you did you will have to wait a bit yet to root again. Your only option would be stock verizon. Their software update basically closed the previously open window. If not...You HAVE updated radio per the # you posted, not sure if that really matters with regard to recovery. It seems like you have compounded many issues. I would try relocking bootloader and flash stock RUU again. Try to get back to stock verizon. If that's a no go, would try reflashing old radio and try stock ruu. How are you getting to try bootloader/recovery, turning on phone holding down vol button? Last ditch if it's says s-on and locked, I think you would be ok to try for a new phone.
I did not take the OTA from Verizon. I never got any prompt for an update. I did the updates for Viper that turned I think just turned that off.
Getting to bootloader is fine. I can lock it and unlock it fine. I know the RUU only loads if locked. I know recovery can only be installed if unlocked I believe. And yes I do that from vol down plus power button.
If I use newest TWRP recovery just gives a whole bunch of colored lines. If I try 2.4.0.0 I can see TWRP come up briefly then the phone reboots again.
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Tersanyus said:
The RUU exe file just now gives error 158. Basically it thinks it is not the correct ROM
I found the 1.15 radio but it won't flash. http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
Just gives error of FAILED remote: 92 supercid
Click to expand...
Click to collapse
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
---------- Post added at 10:39 AM ---------- Previous post was at 09:48 AM ----------
rootntootn said:
Is there a boot.img for the ruu? Maybe the previous boot image is still directing the process, a thought at least. Also that error 92 cid MAY be the issue, Do you have the newest one on (cid)? I had a lot of issues getting s-off and had to run supercid again to run the process after several error 92 messages. I would look at the whole s-off thread in original dev section maybe some answers in there or a direction to head in.
Click to expand...
Click to collapse
Can you get to fastboot? adb can communicate with the phone? Says in red fastboot usb? Also how are you doing RUU, assuming your using executable from your pc? Forgot to ask..
Yes I can get to fastboot fine. I do a "fastboot devices" and it is read. adb doesn't seem to do anything though. The RUU is the .exe I found.
For the cid I did the old one so mine reads all 1's. I didn't think I could so the new cid as I cannot boot into Android at all.
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Tersanyus said:
Ok success!! Yes.
I did the S-OFF directions once. Nothing, no change.
Did it again this time it booted to factory rom.
I am S-OFF cid is all ones.
I got the prompt for the OTA update, took ot, phone rebooted to recovery, TWRP, then nothing.
Wifi not working, I know I read about that so looks like I have a little more work.
Click to expand...
Click to collapse
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
rootntootn said:
Not sure how you got there s-off should have all 2's....but it sounds like progress. If you are back to recovery and have a rom to flash in your phone that's great...but you'll need adb working to flash the image file that's associated with it, that will likely fix your wifi issue as well. Even with S-off most of the roms still need to have their respective image files flashed but I am unsure about stock RUU, someone with more experience may know that answer and can maybe steer you in the right direction...
Click to expand...
Click to collapse
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
BTW There was nothing wrong with your phone, it's just that when you restored, you needed to flash the boot.img from your rom that you restored. It was most likely a kernel issue that we could correct with viper.
It sounds like you just need to install the matching rom and boot.img. If you're s off, just fastboot flash the boot.img for whatever rom you currently have installed. For the OTA update, you can install the radios without an RUU if you're s off.
I ran for several hours and several reboots on the RUU .exe file. When I downloaded a custom rom from http://forum.xda-developers.com/showthread.php?t=2150262 - That fan fine for an hour or so. Then boot loop over and over again. Thankfully I made a backup in twrp. I restored that and all is well.
I can't stand this factory rom, the part that really annoys me, besides the VZW bloat, is the recent apps button. For over a year with other HTC's I am used to making that the menu button. Had that in the custom rom.
So it looks like that rebooting loop just means I need to fastboot the boot.img?
I go back to the rom I linked about and fastboot the boot.img. I really liked viper rom but am going to stick to stock that is rooted and debloated.
My cid is all 1's since I did that before all this OTA came out. I did that about 3 weeks ago the day I got the phone.
Thanks for the tips. I'll let you know what happens when I go back to the rom above.
Bigandrewgold said:
If you have a custom recovery then you can't install the ota. If you want the ota stuff you can install the Rom kernel and radio from it.
As far as wifi not working, just flash a kernel, right now it sounds like you have the modules from one kernel and the boot.img from another.
Sent from my HTC6435LVW using xda app-developers app
---------- Post added at 09:43 PM ---------- Previous post was at 09:40 PM ----------
You don't need all 2s to get s off, you can do it with all ones without a problem.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Sorry about the 2's info but read that the older cid apk would no longer work (from thread below) and myself put on the new one which yields the all 2's. Bottom line, glad you made progress, hopefully problem resolved
http://forum.xda-developers.com/showthread.php?t=2109862