Related
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.
:crying:what do i do...
phone wouldn't start only can go into hboot or recovery and that's about it..
What did you do to get it into that state? Do you have a Nandroid? You could always flash a newer RUU as well
Sent from my ADR6425LVW using xda app-developers app
sian0120 said:
:crying:what do i do...
phone wouldn't start only can go into hboot or recovery and that's about it..
Click to expand...
Click to collapse
I ran into this when I re-locked the bootloader via fastboot oem lock, and if this is how you got there, you're OK. Just somehow get the OTA/RUU downloaded, renamed to PH98IMG.ZIP on your ext sd, flash HBOOT (twice, both flashes together maybe take 20 minutes) and then you should be totally stock and can re-unlock and root from there. My HBOOT does still say "TAMPERED", but everything works fine.
Yeah the tampered banner comes up when you install a custom recovery but but just follow the above post and you'll be back up and running.
Sent from my HTC Rezound using Tapatalk 2
yave same problem
when trying to flash RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed *sending* is more than 10 minets and nothing happens
what should i do?
yurchik92 said:
yave same problem
when trying to flash RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed *sending* is more than 10 minets and nothing happens
what should i do?
Click to expand...
Click to collapse
First of all, you verified the MD5? If you are s-on, did you relock the phone? (if s-off no need to)
Did you ever flash the global leak? If so, use that again.
http://www.androidpolice.com/2012/0...ull-ruu-build-4-03-605-2-for-the-htc-rezound/
If not, you can try that one if you don't mind going up to that leak. Are you s-off? If you are then it won't hurt a thing. If you are s-on and you go to the global leak you won't be able to take the most recent OTA that came out a few weeks ago.
I have a similar problem, if I may piggyback off of this thread. I tried running the latest RUU and first got a security error, so I relocked it and ran it again. The second time I ran it I got "hboot is older than..." something else. I tried flashing a later hboot 2.27 but it doesn't change in the hboot menu, nor can I run the RUU.
---------- Post added at 03:37 AM ---------- Previous post was at 03:25 AM ----------
Oops. I meant I tried flashing 2.27 (http://forum.xda-developers.com/showthread.php?t=1843030) but it never actually applies it, it just says "parsing" and then goes back to the fastboot menu.
project_86 said:
I have a similar problem, if I may piggyback off of this thread. I tried running the latest RUU and first got a security error, so I relocked it and ran it again. The second time I ran it I got "hboot is older than..." something else. I tried flashing a later hboot 2.27 but it doesn't change in the hboot menu, nor can I run the RUU.
---------- Post added at 03:37 AM ---------- Previous post was at 03:25 AM ----------
Oops. I meant I tried flashing 2.27 (http://forum.xda-developers.com/showthread.php?t=1843030) but it never actually applies it, it just says "parsing" and then goes back to the fastboot menu.
Click to expand...
Click to collapse
Are you s-on? Does the RUU have an hboot that's older than the one your phone has? Which RUU are you trying to use?
Feralicious, thank you! Your question led me to try an older RUU and it worked. From what I've gathered, I cannot update the HBOOT to 2.27 until I'm s-off. I never attempted that, but will some day.
I'm a noob n before using this jewel i used a shooter, it usually takes only several minutes to flash an RUU, but now I'm f;ashing the 3.15 RUU and its been half an hour n my phone still stuck on HTC logo, any help please?
Hboot 2.09 has 2 versions 3.15.651.16 and 3.16.651.3 which one do you have?
hboot 2.09.0000 and 3.15, it has been more than an hour and hasn't reboot yet
Check PM
why pm? why not post for others to see? having the same issues here with a friends evo. started ruu but sits on the htc logo indefinitely....
b.huss2 said:
why pm? why not post for others to see? having the same issues here with a friends evo. started ruu but sits on the htc logo indefinitely....
Click to expand...
Click to collapse
Issue the fastboot command again, make sure all of the files are in the same directory where you have adb... Try another usb port/cable... I never had that issue, what version of Windows?
Sent from my SPH-L900 using Tapatalk 4
jocarog said:
Issue the fastboot command again, make sure all of the files are in the same directory where you have adb... Try another usb port/cable... I never had that issue, what version of Windows?
Sent from my SPH-L900 using Tapatalk 4
Click to expand...
Click to collapse
It's an RUU, there are no other files. possible driver issue maybe? I'll try a different usb cable.
Windows 7 btw
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
some more info.....I see it has hboot 2.09.0000 and is flaged as tampered with and s-on. I think it was s-off at some point but re-locked. Keep in mind I'm not real familiar with this device, but have modded many. My friend just wanted me to help him get it back stock/unrooted. I thought it would be easy enough to flash an RUU but that's not getting me very far.
b.huss2 said:
It's an RUU, there are no other files. possible driver issue maybe? I'll try a different usb cable.
Windows 7 btw
---------- Post added at 12:36 PM ---------- Previous post was at 12:30 PM ----------
some more info.....I see it has hboot 2.09.0000 and is flaged as tampered with and s-on. I think it was s-off at some point but re-locked. Keep in mind I'm not real familiar with this device, but have modded many. My friend just wanted me to help him get it back stock/unrooted. I thought it would be easy enough to flash an RUU but that's not getting me very far.
Click to expand...
Click to collapse
An RUU won't put the device back S-on but it will relock the bootloader. If you want to put the phone back totally stock and S-on get S-off and use VipeRUU. The link is below:
http://forum.xda-developers.com/showthread.php?p=47720390
Sent from my HTC EVO 4G LTE
FinZ28 said:
An RUU won't put the device back S-on but it will relock the bootloader. If you want to put the phone back totally stock and S-on get S-off and use VipeRUU. The link is below:
http://forum.xda-developers.com/showthread.php?p=47720390
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
You may have misunderstood or I was unclear. It is currently s-on. I think it was s-off at one point and rooted but is now back to s-on In his attempt to return it back to stock.
b.huss2 said:
You may have misunderstood or I was unclear. It is currently s-on. I think it was s-off at one point and rooted but is now back to s-on In his attempt to return it back to stock.
Click to expand...
Click to collapse
Nah, I understood you. If you want to get rid of the tampered flag and get back totally stock VipeRUU can do that for you, unlike a regular RUU.
Sent from my HTC EVO 4G LTE
FinZ28 said:
Nah, I understood you. If you want to get rid of the tampered flag and get back totally stock VipeRUU can do that for you, unlike a regular RUU.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Ok cool, I will try that then. Thanks.
so i have a Htc rezound i have TWRP installed as the recovery and it is S-ON
i had done a twrp back before i had done any modding to the firmware, and it was and is an entire backup of the phone
i have gotten the backup to restore via TWRP but once it gets to the verizon 4G LTE splash screen it just hangs there everytime
i've downloaded a bunch of RUU's to try and get them to work with the phone but they either don't show up or it tells me the Hboot version im using is too new for the RUU im using.
i have the newest hboot version 2.28
i have used many threads but this was the most promising , i just can't get it to work
http://forum.xda-developers.com/showthread.php?t=2453701
can anyone help as i didn't do the S-off , so it is still S-on
i do have a entire backup of the phone via TWRP i just don't know how to get it to work..... couldn't find a boot.img to flash either , i figured to try that but couldn't find it
dust906 said:
so i have a Htc rezound i have TWRP installed as the recovery and it is S-ON
i had done a twrp back before i had done any modding to the firmware, and it was and is an entire backup of the phone
i have gotten the backup to restore via TWRP but once it gets to the verizon 4G LTE splash screen it just hangs there everytime
i've downloaded a bunch of RUU's to try and get them to work with the phone but they either don't show up or it tells me the Hboot version im using is too new for the RUU im using.
i have the newest hboot version 2.28
i have used many threads but this was the most promising , i just can't get it to work
http://forum.xda-developers.com/showthread.php?t=2453701
can anyone help as i didn't do the S-off , so it is still S-on
i do have a entire backup of the phone via TWRP i just don't know how to get it to work..... couldn't find a boot.img to flash either , i figured to try that but couldn't find it
Click to expand...
Click to collapse
I was in a similar predicament only worse because I had accidentally wiped the system and I didn't have any backup as it was a refurbished replacement phone. At the time, I was also S-on and Hboot 2.28. Even though I used AmonRa, I'm sure it would work with TWRP as well. Take a look at THIS POST on how I was able to get my phone back up and running. Maybe it will help.
The only way to go back to stock is s-off then downgrade to the stock ruu.exe and then go back to s-on and relock...let me find it but someone already posted a thread about this
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
http://forum.xda-developers.com/showthread.php?t=2453701
Instructions and links, step by step to s-off, get ruu stock.
Thanks flamewalker....this was exactly what I was referring to
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
REV3NT3CH said:
The only way to go back to stock is s-off then downgrade to the stock ruu.exe and then go back to s-on and relock...let me find it but someone already posted a thread about this
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
Click to expand...
Click to collapse
Not true. I was able to accomplish getting back to fully stock while still S-on with Hboot 2.28.0000 and can see how I did it if you click the link I posted. In order to use the most current ControlBear through the Ubuntu method, you have to be completely stock. Since I had accidentally wiped the entire system along with the cache and dalvik cache, and without a nandroid backup, my phone was soft bricked but I was able to get a working stock phone without having to S-off so it can be done. It was only then that I proceeded to S-off.
Not true read flamewalkers post...quite a few have gone s-off while on a custom ROM....and doing downgrading while s-on has a very high chance of bricking your device
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
REV3NT3CH said:
Not true read flamewalkers post...quite a few have gone s-off while on a custom ROM....and doing downgrading while s-on has a very high chance of bricking your device
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
Click to expand...
Click to collapse
I didn't downgrade, I went from a new replacement phone that unfortunately ended up completely wiped of any of the system files and folders and was able to reinstall the current 4.05.605 using that stock rooted rom and flashing that in a custom recovery. I also did the boot.img thing as well but I am almost certain that I had to flash that boot.img first before flashing the stock rooted rom zip. I never used any earlier versions, only that stock rooted rom file. It didn't require any downgrading or S-off. I had extracted the stock recovery from the firmware link I posted in the other thread and placed it in a custom ph98img.zip. I put that on the ext-sd card after my phone was up and running. Then I went back into the unlocked bootloader and let it install the stock recovery. For whatever reason I was unable to get earlier versions of ControlBear to work for me and that was why I chose to use the most current version. I don't know if it was a problem with my computer or what. And I actually have just about every ControlBear version that had been released. This most current version though, requires that the phone be completely bone stock but unlocked. I know that the earlier versions actually required a rooted rom but this one is different. Take a look at the unlimited.io site for confirmation.
But my point is that you can get a phone back to stock without S-off or having to downgrade either. I know because I suffered through it. The only reason I only downgraded later after doing S-off was to get rid of the relocked and tampered message in the bootloader and then I just let the OTA do it's updates.
In order to get fully untampered stock you have to downgrade
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
REV3NT3CH said:
In order to get fully untampered stock you have to downgrade
Sent from my P4R4N01D R3D D347H 4.3 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I know. I'm fully aware of that.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
But to get a stock phone, you do not need to downgrade, just use that stock rooted rom and then use remove root by using the option in SuperSu that gets installed with that rom. And if you want to take it further then reinstall the stock recovery and you now have a fully stocked phone.
Here's a potential facepalm moment...
Did the op try 'fastboot flash boot boot.img' (after extracting the boot.img from the mod zip using winzip or winrar)? Cause with S-ON you have to flash the boot.img after loading a custom rom.
mikeyk101 said:
Yeah, I know. I'm fully aware of that.
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
But to get a stock phone, you do not need to downgrade, just use that stock rooted rom and then use remove root by using the option in SuperSu that gets installed with that rom. And if you want to take it further then reinstall the stock recovery and you now have a fully stocked phone.
Click to expand...
Click to collapse
You do understand to be "stock" means no "tampered" or "relocked" or "unlocked" tags in hboot right? Stock phone will say "locked" S-On. Only way for our phone is to s-off for "locked" tag after unlocking and to remove "tampered" requires an official RUU, which is only downgrading as we do not have an official RUU for current OTA.
Sent fromy Liquid Smooth Rezound running 4.3
Uzephi said:
You do understand to be "stock" means no "tampered" or "relocked" or "unlocked" tags in hboot right? Stock phone will say "locked" S-On. Only way for our phone is to s-off for "locked" tag after unlocking and to remove "tampered" requires an official RUU, which is only downgrading as we do not have an official RUU for current OTA.
Sent fromy Liquid Smooth Rezound running 4.3
Click to expand...
Click to collapse
also i figured out why adb has been an issue for some people trying to fastboot and it slipped my mind...If your bootloader is locked it will not allow all fastboot commands including fastboot flashes...if anyone needs help unlocking their bootloader i can help and all you need to do is pm me
I think you guys are way overthinking this. I think we are splitting hairs over what the OP is talking about when he says he wants the phone returned to stock. The way I read it, the OP is just looking at getting his phone up and running and wants it to be "stock" as in not modded. He mentions that he has twrp recovery but makes no mention about wanting to have the stock recovery or locking his bootloader. Sure if you want a pure, able to return to Verizon for warranty phone with an unmolested truly stock ***Locked*** bootloader, then yes, the only way is to downgrade to S-off and use the full 3.14.605.12 RUU and then update OTA back to "fully stock" 4.05.605.14. But I don't think that is what the OP is asking for so to have a working "stock" phone that is fully functional, you do not have to downgrade.
I think we are all making assumptions. Maybe waiting for the OP to respond back would be helpful...
Hey guys,
Sorry for the slight threadjack but I didn't want to post a new thread while this one was out there.
I'm having trouble getting my Rezound back to stock as well. I was S-OFF and tried RUUing but it goes to ***RELOCKED*** instead of ***LOCKED***, so I can't get to completely stock. I've tried several different ways and I am having no success.
I need to send the phone back as a warranty replacement, so at this point I'm just looking to make the phone appear as ***LOCKED*** and S-ON. Despite a Verizon customer service lady telling me I had 150 days, just one month and they've charged me $450 for the device, so I need to get it sorted out.
I'm thinking I can RUU while S-OFF, then install custom HBOOT, then S-ON with that custom HBOOT and that might do the trick. However, the custom HBOOT needs to not be an engineering HBOOT because then S-ON will brick it.
Is there a custom HBOOT that will say ***LOCKED*** consistently that I can then S-ON without bricking the phone?
Thanks for any help you can give.
tigerxchaos said:
Hey guys,
Sorry for the slight threadjack but I didn't want to post a new thread while this one was out there.
I'm having trouble getting my Rezound back to stock as well. I was S-OFF and tried RUUing but it goes to ***RELOCKED*** instead of ***LOCKED***, so I can't get to completely stock. I've tried several different ways and I am having no success.
I need to send the phone back as a warranty replacement, so at this point I'm just looking to make the phone appear as ***LOCKED*** and S-ON. Despite a Verizon customer service lady telling me I had 150 days, just one month and they've charged me $450 for the device, so I need to get it sorted out.
I'm thinking I can RUU while S-OFF, then install custom HBOOT, then S-ON with that custom HBOOT and that might do the trick. However, the custom HBOOT needs to not be an engineering HBOOT because then S-ON will brick it.
Is there a custom HBOOT that will say ***LOCKED*** consistently that I can then S-ON without bricking the phone?
Thanks for any help you can give.
Click to expand...
Click to collapse
Just S-off again, it will make the locked tag.
Sent fromy Liquid Smooth Rezound running 4.3
Uzephi said:
Just S-off again, it will make the locked tag.
Sent fromy Liquid Smooth Rezound running 4.3
Click to expand...
Click to collapse
Yeah if you unlocked and relocked while s-off (which I did once /facepalm), then do the s-off procedure again, then run the ruu to return it completely to stock (if it isn't already on the ruu).
http://forum.xda-developers.com/showthread.php?t=2453701 <- Just start from wherever you are currently at. Be careful not to s-on unless you are fully 100% stock ruu.
flamewalker said:
Yeah if you unlocked and relocked while s-off (which I did once /facepalm), then do the s-off procedure again, then run the ruu to return it completely to stock (if it isn't already on the ruu).
http://forum.xda-developers.com/showthread.php?t=2453701 <- Just start from wherever you are currently at. Be careful not to s-on unless you are fully 100% stock ruu.
Click to expand...
Click to collapse
Thanks for the suggestions.
I had thought of trying this, but Juopunutbear doesn't allow S-OFF to be done again if the phone is already S-OFF. I could re-RUU and then S-ON, but my main worry is that I get an error when relocking the bootloader:
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
I was worried that it might have caused an issue that would brick the phone if I set it back to S-ON. Verizon is expecting to get a phone that at least boots up.
Running the RUU also installs a stock HBOOT, correct? So that would clear out any issues with the bootloader?
I just replied to your post in the other fourm with the same information as above.
When you ruu it will replace the bootloader with the one in the ruu. It should not matter if you are locked or unlocked. You have to be unlocked to s-off any way. I don't quite remember if it auto locks when you run the ruu. If it does just unlock.
Sent from my Infected Rezound using xda app-developers app
tigerxchaos said:
Thanks for the suggestions.
I had thought of trying this, but Juopunutbear doesn't allow S-OFF to be done again if the phone is already S-OFF. I could re-RUU and then S-ON, but my main worry is that I get an error when relocking the bootloader:
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
I was worried that it might have caused an issue that would brick the phone if I set it back to S-ON. Verizon is expecting to get a phone that at least boots up.
Running the RUU also installs a stock HBOOT, correct? So that would clear out any issues with the bootloader?
Click to expand...
Click to collapse
So my understanding is that you are currently S-Off? Are you on stock rom now or?
Yes. Hboot and recovery all get replaced with RUU. RUU will also relock. Then do the part to s-on after, ONLY after you are successfully booting a full RUU.
Good luck
---------- Post added at 08:58 AM ---------- Previous post was at 08:07 AM ----------
tigerxchaos said:
Thanks for the suggestions.
I had thought of trying this, but Juopunutbear doesn't allow S-OFF to be done again if the phone is already S-OFF. I could re-RUU and then S-ON, but my main worry is that I get an error when relocking the bootloader:
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
I was worried that it might have caused an issue that would brick the phone if I set it back to S-ON. Verizon is expecting to get a phone that at least boots up.
Running the RUU also installs a stock HBOOT, correct? So that would clear out any issues with the bootloader?
Click to expand...
Click to collapse
Just to reiterate... Per the s-on instructions, DO NOT S-ON ON ANYTHING OTHER THAN A FULL RUU! You will hard brick your device if you s-on on anything other than a full RUU.
I'm hoping the wisdom of the XDA crowd can show me the way. My EVO 4G LTE was unrooted, fully stock when I ran the new RUU from Sprint. It got stuck and never completed. It sat overnight, with the sliver HTC logo against a black background. The program stopped responding on my laptop. So, I disconnected. I am able to get into HBOOT screen. I can reach the phone through ADB when connected in Fastboot. I have also been able to load TWRP and CWM, but image files won't take. I cannot get the phone to load past the white screen with the green HTC letters.
I figure that I have no more OS. But, I cannot do anything else because while I have unlocked the bootloader, I still have S-ON. I have HBOOT 2.10 as well.
I cannot mount the storage from the laptop, but I do have an external SD card I can swap in and out.
I know there are ways I can get to a new ROM with HBOOT 2.10, but it seems they all require S-OFF. I can't figure out how to get S-OFF.
At this point I would just like a working phone. Where do I go from here?
robwalte said:
I'm hoping the wisdom of the XDA crowd can show me the way. My EVO 4G LTE was unrooted, fully stock when I ran the new RUU from Sprint. It got stuck and never completed. It sat overnight, with the sliver HTC logo against a black background. The program stopped responding on my laptop. So, I disconnected. I am able to get into HBOOT screen. I can reach the phone through ADB when connected in Fastboot. I have also been able to load TWRP and CWM, but image files won't take. I cannot get the phone to load past the white screen with the green HTC letters.
I figure that I have no more OS. But, I cannot do anything else because while I have unlocked the bootloader, I still have S-ON. I have HBOOT 2.10 as well.
I cannot mount the storage from the laptop, but I do have an external SD card I can swap in and out.
I know there are ways I can get to a new ROM with HBOOT 2.10, but it seems they all require S-OFF. I can't figure out how to get S-OFF.
At this point I would just like a working phone. Where do I go from here?
Click to expand...
Click to collapse
To gain s-OFF you'd need to be on 3.16 firmware if you don't want the hassle then redo the RUU a different way which is that link V
Sent from my EVO using Tapatalk
---------- Post added at 08:46 AM ---------- Previous post was at 08:43 AM ----------
Then use these instructions found here.
http://forum.xda-developers.com/showthread.php?p=50523371
Sent from my EVO using Tapatalk
---------- Post added at 08:54 AM ---------- Previous post was at 08:46 AM ----------
lreyes said:
To gain s-OFF you would have to be on 3.16 firmware. If your bootloader is unlocked...
Sent from my EVO using Tapatalk
---------- Post added at 08:46 AM ---------- Previous post was at 08:43 AM ----------
Then use these instructions found here.
http://forum.xda-developers.com/showthread.php?p=50523371
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
Sent from my EVO using Tapatalk
Thanks for the link. That kind of worked. The first rom_1.zip that I renamed didn't work...Gave me an error that said "Wrong zipped file!" I tried it with the other file, just to see, and that seemed to work. It was able to parse it and flash it. However, when I rebooted, I am still stuck on the white HTC screen.
Is there any way to downgrade the firmware to 3.16 from fastboot or recovery? I can still access CWM.
Not unless you're S-off, no.
Sent from my EVO LTE
Is there any way to gain S-OFF with HBOOT 2.10 without an OS?
No.
Have you tried running the RUU again from the bootloader, or have you tried flashing a ROM?
Sent from my EVO LTE
I was trying to figure out how to run the RUU from the bootloader, but couldn't figure it out. How can I do that?
Connect via Fastboot USB mode and start the RUU just like you did when you ran it previously.
Sent from my EVO LTE
Yes - I've done that. Putting it into Fastboot USB was the only way my laptop could recognize the phone. I could try to flash a rom, but I wasn't sure which one would work with the HBOOT/firmware version I have.
robwalte said:
Yes - I've done that. Putting it into Fastboot USB was the only way my laptop could recognize the phone. I could try to flash a rom, but I wasn't sure which one would work with the HBOOT/firmware version I have.
Click to expand...
Click to collapse
If your Hboot and firmware match the new layout you can try and flash one of the new Android 4.3 Sense 5 ROM's.
I'll keep looking for one that doesn't require S-OFF. All the ones I've found so far require it.
robwalte said:
I'll keep looking for one that doesn't require S-OFF. All the ones I've found so far require it.
Click to expand...
Click to collapse
Any luck? I know there are aosp roms that work on the new layout. Not sure if they require s-off
HTC Jewel
Hboot 2.10 S-off
Android 4.3 Sense 5.5 V3
gstanke said:
Any luck? I know there are aosp roms that work on the new layout. Not sure if they require s-off
HTC Jewel
Hboot 2.10 S-off
Android 4.3 Sense 5.5 V3
Click to expand...
Click to collapse
No luck on that front, but Captain_Throwback came to the rescue and gave me the solution after a plea from help over at the Android Central forums. I had to relock my bootloader, then load on the RUU as a PJ75IMG.img in the root of the SD card.
The file was provided by Captain_Throwback - link is in the post here: http://forums.androidcentral.com/ht...te-coming-htc-evo-4g-lte-132.html#post3475940
Everything is working great now. It does feel like a new phone, to a certain extent - very fast.