I recently bought a replacement Rezound, which has Hboot 2.25/Radios 1.22.10 0421r &0424r. I have unlocked the bootloader and installed TWERP 2.6.3.0 and Infection 2.9.1. I am sure I should have thought of this before installing Infection, but my battery life is worse than my original phone and it runs hot. No reboots or other problems.
I have searched for instructions and recommendations for upgrading Hboot, but haven't found anything clear enough to overcome my nervousness about this process. I have one bricked phone on the desk in front of me and I don't want another. I will be grateful to anyone who can recommend what Hboot to flash (I'm thinking 2.27 or 2.28?) and guide me through the process.
Thanks,
geronimo48 said:
I recently bought a replacement Rezound, which has Hboot 2.25/Radios 1.22.10 0421r &0424r. I have unlocked the bootloader and installed TWERP 2.6.3.0 and Infection 2.9.1. I am sure I should have thought of this before installing Infection, but my battery life is worse than my original phone and it runs hot. No reboots or other problems.
I have searched for instructions and recommendations for upgrading Hboot, but haven't found anything clear enough to overcome my nervousness about this process. I have one bricked phone on the desk in front of me and I don't want another. I will be grateful to anyone who can recommend what Hboot to flash (I'm thinking 2.27 or 2.28?) and guide me through the process.
Thanks,
Click to expand...
Click to collapse
look at my downgrade/upgrade guide here in the rezound q&a.....the 3 ph98img ota files are the updates you want
REV3NT3CH said:
look at my downgrade/upgrade guide here in the rezound q&a.....the 3 ph98img ota files are the updates you want
Click to expand...
Click to collapse
Your initial comment, "For this you MUST BE S-OFF FOR DOWNGRADING with a relocked bootloader and make sure you are not on a custom or hex edited hboot or you can brick your device." stopped me. My phone is S-on and Hboot is unlocked. Do I have to be S-off and unlocked to flash the three OTAs?
geronimo48 said:
Your initial comment, "For this you MUST BE S-OFF FOR DOWNGRADING with a relocked bootloader and make sure you are not on a custom or hex edited hboot or you can brick your device." stopped me. My phone is S-on and Hboot is unlocked. Do I have to be S-off and unlocked to flash the three OTAs?
Click to expand...
Click to collapse
yes thats for downgrading with the ruu.exe's not for updating...to update just follow the OTA part with the ph98img.zips
REV3NT3CH said:
yes thats for downgrading with the ruu.exe's not for updating...to update just follow the OTA part with the ph98img.zips
Click to expand...
Click to collapse
I downloaded all three files and checked md5 - all checked out. I then put the 1st file on the root directory of my ex sd card, renamed it PH98IMG.zip and rebooted into the unlocked bootloader. Bootloader recognized the zip, the progress bar appeared and the file transferred. Then the progress bar disappeared and nothing else happened. There was no instruction to press Volume up. I repeated everything and got the same result. I can still boot into TWERP and my phone still starts up with Infection 2.9.1.
Let me say at this point, THANK GOD NOTHING BAD HAPPENED!
Any suggestions?
geronimo48 said:
I downloaded all three files and checked md5 - all checked out. I then put the 1st file on the root directory of my ex sd card, renamed it PH98IMG.zip and rebooted into the unlocked bootloader. Bootloader recognized the zip, the progress bar appeared and the file transferred. Then the progress bar disappeared and nothing else happened. There was no instruction to press Volume up. I repeated everything and got the same result. I can still boot into TWERP and my phone still starts up with Infection 2.9.1.
Let me say at this point, THANK GOD NOTHING BAD HAPPENED!
Any suggestions?
Click to expand...
Click to collapse
hmmm for s and g's relock the bootloader....are you absolutely sure you are on 2.25...the first ph98img is hboot 2.27 with the firmware....also just rename it to just PH98IMG if you type the zip with it the phone will read it as PH98IMG.zip.zip and wont work
REV3NT3CH said:
hmmm for s and g's relock the bootloader....are you absolutely sure you are on 2.25...the first ph98img is hboot 2.27 with the firmware....also just rename it to just PH98IMG if you type the zip with it the phone will read it as PH98IMG.zip.zip and wont work
Click to expand...
Click to collapse
I am looking at my Hboot screen. It says:
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
I transferred the 1st file to my SD card and deleted "this 1st " from the name. I watched it reading in Hboot and saw "PH98IMG.ZIP".
I'll try relocking the bootloader.
Thanks.
EDIT - Looks like the bootloader needs to be locked. The first file is finished, starting on the second.
EDIT 2 - OK. I can't get the 2nd file to flash with the bootloader locked or unlocked.
BUT, I now have:
HBOOT-2.27.000
RADIO-2.22.20.0801r/2.22.10.0803r
geronimo48 said:
I am looking at my Hboot screen. It says:
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12 2012, 16:47:46
I transferred the 1st file to my SD card and deleted "this 1st " from the name. I watched it reading in Hboot and saw "PH98IMG.ZIP".
I'll try relocking the bootloader.
Thanks.
EDIT - Looks like the bootloader needs to be locked. The first file is finished, starting on the second.
Click to expand...
Click to collapse
ah thanks for the info bud much appreciated....glad relocking it worked for you
REV3NT3CH said:
ah thanks for the info bud much appreciated....glad relocking it worked for you
Click to expand...
Click to collapse
Please see EDIT 2. I can't flash the 2nd file with the bootloader locked or unlocked.
I can boot into Hboot, but when I try to open Recovery I first get the green arrows (circle and down), then I get the red triangle with exclamation mark. When I booted the phone I got the setup wizard and a notice that my phone was just activated. Of course it was already activated. I suppose this just means everything has been wiped and I'm starting fresh with the firmware from the 1st downloaded zip. I didn't go through setup.
Any ideas?
geronimo48 said:
Please see EDIT 2. I can't flash the 2nd file with the bootloader locked or unlocked.
I can boot into Hboot, but when I try to open Recovery I first get the green arrows (circle and down), then I get the red triangle with exclamation mark. When I booted the phone I got the setup wizard and a notice that my phone was just activated. Of course it was already activated. I suppose this just means everything has been wiped and I'm starting fresh with the firmware from the 1st downloaded zip. I didn't go through setup.
Any ideas?
Click to expand...
Click to collapse
yes....after 1st ota phone is suppose to activate through verizon
REV3NT3CH said:
yes....after 1st ota phone is suppose to activate through verizon
Click to expand...
Click to collapse
Any ideas on how to install the other two OTAs?
geronimo48 said:
Any ideas on how to install the other two OTAs?
Click to expand...
Click to collapse
all 3 install through bootloader....must have a relocked bootloader...the other 2 ph98img.zip's are not firmware or rom....just radios, hboot, and required system files for them
REV3NT3CH said:
all 3 install through bootloader....must have a relocked bootloader...the other 2 ph98img.zip's are not firmware or rom....just radios, hboot, and required system files for them
Click to expand...
Click to collapse
I noticed they were smaller. I installed the 1st OTA with the bootloader relocked. The 2nd OTA wouldn't complete installation locked or unlocked. I reflashed the first OTA just to make sure and the process worked flawlessly. The 2nd OTA acts like it is loading, but I don't get the notice to press Vol Up.
If you think of a way that might work to get the other OTAs installed, let me know.
Thanks again for all your help.
geronimo48 said:
I noticed they were smaller. I installed the 1st OTA with the bootloader relocked. The 2nd OTA wouldn't complete installation locked or unlocked. I reflashed the first OTA just to make sure and the process worked flawlessly. The 2nd OTA acts like it is loading, but I don't get the notice to press Vol Up.
If you think of a way that might work to get the other OTAs installed, let me know.
Thanks again for all your help.
Click to expand...
Click to collapse
Same issue here thanks for addressing it.
drhile said:
Same issue here thanks for addressing it.
Click to expand...
Click to collapse
hmm strange....works for some doesnt for others...i know flyhalf posted a method of this somewhere for s-on users...required extra step i think
geronimo48 said:
Any ideas on how to install the other two OTAs?
Click to expand...
Click to collapse
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
geronimo48 said:
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
Click to expand...
Click to collapse
If you're at hboot 2.27, that's not your problem, you have other issues, being you're s-on, how did you flash the kernel for Tachyon?
geronimo48 said:
I guess you haven't thought of anything.
I am thinking of having another go at installing all three OTAs. I have installed CWM and TACHYON. I don't have FCs or bootloops, but my battery life is poor, the camera doesn't work and the phone runs hot (>110). I have tried SetCPU with limited success.
You and others have stated that outdated HBOOT/radios can cause overheating, so I want to try.
Question: Do I need to do a factory reset and start over with the 1st OTA?
Thanks again for all of your help.
Click to expand...
Click to collapse
as stated there is a method with the last two foe s-on users...having to use fastboot i believe
REV3NT3CH said:
as stated there is a method with the last two foe s-on users...having to use fastboot i believe
Click to expand...
Click to collapse
Thanks. I'll post if I figure it out.
geronimo48 said:
Thanks. I'll post if I figure it out.
Click to expand...
Click to collapse
according to flyhalf as the this 3rd was uploaded by him you just need a relocked bootloader for s-on....im s-off though but can guarantee links work as i just used them...but in all seriouness if your not really using stock i highly suggest gaining s-off as it will make life easier....plus it has less of a chance on fully and permanently bricking your rez...with s-on there isnt really much you can do in a brick
Related
I achieved S-Off on my Evo 4g LTE by downgrading from HBOOT 1.19 to 1.12. After doing this I stupidly ran RUU to upgrade from 1.13 to 2.23. Now my bootloader is showing the following:
EVITA PVT SHIP S-OFF RL
CID-########
HBOOT-1.12.2222
RADIO-1.12.11.0809
OpenDSP-v29.1.0.45.0622
eMMC-boot
It also has an incorrect IMEI, but a correct SN, and don't know about the MB there. All of them have barcodes as well.
Evita HBOOT on a jewel? The phone now only sits on the HTC Splash with the Dev warning red text.
Am i screwed?
evilmm85 said:
I achieved S-Off on my Evo 4g LTE by downgrading from HBOOT 1.19 to 1.12. After doing this I stupidly ran RUU to upgrade from 1.13 to 2.23. Now my bootloader is showing the following:
EVITA PVT SHIP S-OFF RL
CID-########
HBOOT-1.12.2222
RADIO-1.12.11.0809
OpenDSP-v29.1.0.45.0622
eMMC-boot
It also has an incorrect IMEI, but a correct SN, and don't know about the MB there. All of them have barcodes as well.
Evita HBOOT on a jewel? The phone now only sits on the HTC Splash with the Dev warning red text.
Am i screwed?
Click to expand...
Click to collapse
if the phone still is on .. u should be good :good:
evo401 said:
if the phone still is on .. u should be good :good:
Click to expand...
Click to collapse
Any idea on steps? I ran a TWRP backup but I cant get into recovery, just fastboot. I have tried fastbooting recovery and it says okay but it doesnt work. I also tried the RUU again and it does not work.
Are you sure you have the correct ruu? There is no version 2.23, our latest version is 2.13.651.1. Just throwing ideas out there.
metalfan78 said:
Are you sure you have the correct ruu? There is no version 2.23, our latest version is 2.13.651.1. Just throwing ideas out there.
Click to expand...
Click to collapse
Sorry I meant 2.13, I was at work and didn't have it in front of me.
When I run the RUU it does go into RUU recovery and scrolls across and give me successful at the end. But still no good. When i plug it into my windows computer it shows up as "HTC Android Phone USB Device".
Have you tried to install the updated hboot on the lazy panda Site. If you out the pj75img.zip on your sdcard card and reboot into the bootloader it should install. Then install twrp 2.2.2 the same way and install the rom of your choosing.
Sent from my A500 using Tapatalk
cruise350 said:
Have you tried to install the updated hboot on the lazy panda Site. If you out the pj75img.zip on your sdcard card and reboot into the bootloader it should install. Then install twrp 2.2.2 the same way and install the rom of your choosing.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Since its the wrong model it looks for PJ83IMG.zip. When I do this it reverts the HBOOT to 1.12.2222. When I do the same for TWRP it flashes but still won't boot to it.
What ruu did you run after you got s-off?
RUU_JEWEL_CLICS_40_S_Sprint_WWE-2.13.651.1_Radio_1.12.11.0809_NV_SPCS-2.45_003_release_277028_signed
Nevermind. You could always try the downgrade. It seems like its the same process, especially if you ran the wrong ruu and it pushed a different hboot.
roids87 said:
Nevermind. You could always try the downgrade. It seems like its the same process, especially if you ran the wrong ruu and it pushed a different hboot.
Click to expand...
Click to collapse
I ran the 1.13 and it took, i got into adb but could not get root (not surprised) I installed SuperSU and still couldnt get root. It seems like it runs the system underneath the splash. Sometimes the volume keys even play sounds like its adjusting. I rebooted and havent got back into adb.
Could the HBOOT just be miscommunicating with the hardware?
evilmm85 said:
I ran the 1.13 and it took, i got into adb but could not get root (not surprised) I installed SuperSU and still couldnt get root. It seems like it runs the system underneath the splash. Sometimes the volume keys even play sounds like its adjusting. I rebooted and havent got back into adb.
Could the HBOOT just be miscommunicating with the hardware?
Click to expand...
Click to collapse
I was talking about the hboot downgrade in the Original Development section. It won't be much of a downgrade, since your on the same hboot, but the process seems like it would set you back on track with the jewel.
roids87 said:
I was talking about the hboot downgrade in the Original Development section. It won't be much of a downgrade, since your on the same hboot, but the process seems like it would set you back on track with the jewel.
Click to expand...
Click to collapse
I cant downgrade without getting into adb as root
evilmm85 said:
I cant downgrade without getting into adb as root
Click to expand...
Click to collapse
Touche, I really can't be much help, sorry bro.
roids87 said:
Touche, I really can't be much help, sorry bro.
Click to expand...
Click to collapse
Ok. I fastbooted flashed twrp into recovery. rebooted into recovery. now i can ADB, but i dont have root. I adb installed the SuperSU.apk and rebooted back into recovery but still cant root
evilmm85 said:
Ok. I fastbooted flashed twrp into recovery. rebooted into recovery. now i can ADB, but i dont have root. I adb installed the SuperSU.apk and rebooted back into recovery but still cant root
Click to expand...
Click to collapse
alright somehow when i was in recovery and noticed i had the # (root) in the adb shell so I rewrote my apparently broken block 4 with the backup i made after S-off.
SUCCESS!
Now im booting into my system and my recovery. although no network access right now although it might have to do with firmware bits, I'm gonna try to RUU with 2.13 again.
Somehow u kept the OneX downgrade files even after the RUU which seems odd. Have u tried asking the people working on the downgrade process?
I'm sure they would be more helpful to you.
evilmm85 said:
alright somehow when i was in recovery and noticed i had the # (root) in the adb shell so I rewrote my apparently broken block 4 with the backup i made after S-off.
SUCCESS!
Now im booting into my system and my recovery. although no network access right now although it might have to do with firmware bits, I'm gonna try to RUU with 2.13 again.
Click to expand...
Click to collapse
Good stuff!
roids87 said:
Good stuff!
Click to expand...
Click to collapse
No network because my MSL MEID, username, uicc id, imsi phone number are all wrecked...
And I dont have my MSL...ugh
evilmm85 said:
No network because my MSL MEID, username, uicc id, imsi phone number are all wrecked...
And I dont have my MSL...ugh
Click to expand...
Click to collapse
Do you have the bakp4 file you made when you did the downgrade? This has all of the correct information in it.
Does your bootloader still say Evita?
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
lxbeale said:
I have been trying for months to try and get back to stock in order to get S-OFF and rooted. I have tried many tut's and when I get to the RUU part, it stops me and prompts the error 140. Then I have gone to other websites and threads to find a solution to the problem but I haven't found a successful one.
As of right now this is what I have when I go into bootloader:
*** RELOCKED ***
SHOOTER XC SHIP S-ON RL
HBOOT-1. 58.0000
eMMC-boot
May 17 2012,15:06:44
Click to expand...
Click to collapse
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
fastboot getvar cid
fastboot getvar mainver
Click to expand...
Click to collapse
ramjet73
ramjet73 said:
What RUU are you trying to run? Since you are S-ON with hboot 1.58 the only version that should work is the Sprint ICS (2.89.651.2) version.
If you issue the following commands from fastboot you can verify that you have correct CID and man version (mainver) to flash that RUU:
ramjet73
Click to expand...
Click to collapse
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
lxbeale said:
Do you have a link to a RUU that would work? And I was trying RUU_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304_signed
Click to expand...
Click to collapse
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
ramjet73 said:
Yea, that's the latest GB version but won't flash over the Sprint ICS build.
Here's the one you want.
ramjet73
Click to expand...
Click to collapse
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
lxbeale said:
I downloaded it and ran it, It got about 3 minutes into it and then gave me ERROR[132]: Signature error
Click to expand...
Click to collapse
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? Here's a post with some more RUU.exe troubleshooting tips that might help.
ramjet73
ramjet73 said:
Did you ever run the fastboot commands posted above to display your CID and mainver? If so, what were the values they returned?
Also, did you check the MD5 for the RUU.exe file after you downloaded it? I know that RUU.exe is good because there have been almost 1400 downloads without any problems reported.
Is the phone in "fastboot USB" mode when you start the RUU.exe? with some more RUU.exe troubleshooting tips that might help.
ramjet73
Click to expand...
Click to collapse
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
lxbeale said:
I Got SPCS_001 and 2.89.651.2,
I did not check the MD5 because I have no clue what that is,
It was in fastboot usb mode when I started it.
Click to expand...
Click to collapse
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
I have tried different cables but not different PC's, I will give it another go with my laptop
ramjet73 said:
You have the correct CID and mainver for the Sprint ICS build, so that looks good.
Have you tried a different USB cable and/or another PC? Based on everything I've seen in this thread so far you are doing things right, but something may be corrupting the RUU as it's being flashed.
ramjet73
Click to expand...
Click to collapse
I have tried a different cable but not a different PC, I will have another go with my laptop
lxbeale said:
I have tried a different cable but not a different PC, I will have another go with my laptop
Click to expand...
Click to collapse
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
lxbeale said:
I just tried using my laptop and got Error 170, so I tried a different cord and that didn't work, I then thought that the file may have been corrupted and re downloaded it and still got the same problems. I then went to go and see if the other RUU (2.17) would connect to the phone and it did but still got me the error 140. Would I need to use another PC or what, cause I don't know where to go from here
Click to expand...
Click to collapse
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from this post, place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
ramjet73 said:
Let's take a different approach.
Try downloading the 2.89.651.2 RUU (the first one) from , place it in the root of your SD card and rename it to PG86IMG.zip, then start your bootloader and press the power button once. That should give you a prompt to authorize the installation so go ahead and do that.
This approach will eliminate both the cable and the PC as possible causes of the problem.
ramjet73
Click to expand...
Click to collapse
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
lxbeale said:
I performed this twice on two different computers using different cords each time and when I went into the bootloader, on the top right it went through a blue and then a brown loading bar and then went back to bootloader doing nothing
Click to expand...
Click to collapse
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
ramjet73 said:
Did you try flashing the zip version that I linked in my last post from the bootloader?
ramjet73
Click to expand...
Click to collapse
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
lxbeale said:
Yes I did, do you think if I would root my phone again and then relock it, this could be fixed?
Click to expand...
Click to collapse
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
ramjet73 said:
I really don't know what the problem is but you would definitely have a better chance of fixing it if you are S-OFF. You could unlock the bootloader, flash a custom recovery and then a stock rooted ROM and try the wire trick. If you can get that to work you should definitely be able to flash the RUU.
There is a stock rooted version of the Sprint ICS ROM in this post.
ramjet73
Click to expand...
Click to collapse
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
lxbeale said:
Okay so I unlocked my bootloader and put 4ext recovery on, but I am still having problems flashing firmware, it goes to a loading bar then it says it is parsing then returns back to the bootloader
Click to expand...
Click to collapse
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
ramjet73 said:
Unlocking your bootloader and installing a custom recovery is considered "rooting" and not the same as being S-OFF. If you want to flash PG86IMG.zip files from your bootloader you will have to perform the wire trick procedure to get radio S-OFF.
ramjet73
Click to expand...
Click to collapse
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
lxbeale said:
But in order to do the wire trick, you have to be on a stock RUU and at the moment I am not. I tried installing the stock rom but all its getting me is to the sprint loading screen when trying to boot. Will the wire trick still work?
Click to expand...
Click to collapse
According to the OP of this thread you have hboot 1.58 and should be able to boot a rooted stock Sprint ICS ROM. Did you do a wipe before you flashed it?
If you can't get the rooted stock ROM working you can try doing the wire trick with a "stockish" ROM like MeanROM 2.6. That's not supported by the JBear team but it's worked for some users.
You can't use a GB stock ROM because it won't boot with 1.58, so that's not an option.
ramjet73
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
So, I have a dilemma. I am currently S-ON running TACHYON 1.2 (Android 4.3)
HBOOT 2.28.0000
Radio 2.23.10.0123/4
I updated the hboot and radio while S-ON. Now, I've decided I'd like to go S-OFF. According to JuopunutBear I need to be on a stock RUU for their S-OFF to work. I tried running the newest ICS RUU a few weeks ago and found that it would just error out when it was checking the file because the radios and hboot on the phone were newer than the ones on the RUU. Can I step backwards in HBOOT versions whlie S-ON or have I kind of screwed myself? Or is there a better option I haven't thought about?
Thanks
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Uzephi said:
Just install a stock Rom to run s-off program. You are on a stock hboot, so no problem there.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
It's a stock hboot, yes. But the RUU won't run because it is an older version hboot.
You need s-off to downgrade. Just install a stock based Rom that is rooted and run s-off procedure. You will have no issues. After s-off if you want, you can ruu
Sent from my DNA using my mind.
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
jeff925 said:
Step 1 from Unlimited: Verify - You are on Stock RUU (not FreshROM, Stock Rooted, HarmonyROM - none of these will work!)
They say not to be rooted or anything. What difference does it make?
Also, what do you mean by "stock rom"? Is there a stock rom I can install that is not an RUU? (maybe that's a dumb question but I don't know lol)
Click to expand...
Click to collapse
A stock rooted RUU would work. I was in your predicament once. First, do a nandroid backup then use this guide it'll get you to s-off. If you want to downgrade, then use this guide to accomplish this.
Thanks guys for the help. Installed the rom listed in the guide and it worked great. S-OFF now!! (Took me long enough...I've had the phone for 2 years!)
It installed JuopunutBear's hboot but whatever. I'd probably rather stick with a stock hboot but I can do that later.
Restored my nandroid backup and I'm back up and running like I never left.
Just flash this ROM and boot image, and you should be able to S-OFF, I can't remember if stock recovery is needed but that can be flashed separately as well if needed, but I don't think it is.
http://forum.xda-developers.com/showthread.php?t=2260154
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
jeff925 said:
So, All was well until I decided to flash the stock hboot back to the phone. I put the file on the sd card and renamed it ph98img.zip and flashed it in fastboot. It said it was successful and that I was running hboot 2.28 and radio 2.23.10.0123/4. Then I rebooted and it hung up at the white screen with green htc logo. I pulled the battery and rebooted holding the power and volume buttons. It booted to fastboot so I tried a few things. I tried flashing a recovery but it said that remote was not allowed and failed. Then I tried opening the recovery I already had on the phone from fastboot and it gave me the software download icon. Nothing happened so I pulled the battery and tried to boot back to fastboot. This time it wouldn't even get to fastboot. The white screen with HTC logo comes up and then the screen goes blank. Then the software download icon comes up and then shortly there after a red triangle with an exclamation point takes its place.
That went downhill fast! Any suggestions?
EDIT: Pulling the SD card allows me to get back into fastboot! But I'm still not sure what to do. Is it because my bootloader is locked?
Click to expand...
Click to collapse
In fastboot does it say s-off? Try manually flashing the boot.img by extracting it. If you haven't setup enviroment variable for fastboot put the boot.img in the same directory as fastboot.exe and use command prompt by typing
Code:
cd C:\Android\platform-tools (or wherever it is for you)
Then type
Code:
fastboot flash boot boot.img
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
You can unlock when S-OFF, but there is no reason to, you can get a PH98img.zip of CWM here: http://forum.xda-developers.com/showthread.php?t=1914215 or TWRP here: http://forum.xda-developers.com/showthread.php?t=1902381 and just copy it to your sd card (remember to name it exactly PH98IMG.zip, beware the Windoze "double zip" issue) then pop it in the phone, boot into Hboot with the USB disconnected and it should recognize it and flash either CWM or TWRP. from there you can flash ANYTHING you want, being S-OFF with custom recovery allows you to flash anything, no fastboot commands required.
Also, since you are S-OFF, your Hboot is mostly irrelevant, but should be the matching version to your radios... an engineered hboot (like Juopunutbears) would allow fastboot commands well locked, but fastboot isn't generally needed once S-OFF has been obtained...
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
4218kris said:
Try this. no wire even, works great.
http://forum.xda-developers.com/showthread.php?p=48911002#post48911002
i am on hboot 2.25 though. im thinking of updating my hboot still researching how exactly.
Click to expand...
Click to collapse
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
jeff925 said:
I was able to put an RUU on another sd card and flash that. So now I'm on ICS 4.03.605.2 and running. But I still haven't solved my recovery problems.
According to this thread: androidforums.com/rezound-all-things-root/550408-s-off-guide-info-return-stock.html
I can either use juopunutbear's hboot (which I just flashed over the top of) to flash a new recovery or I can compile a recovery in a ph98img file (which I don't know how to do or want to do).
My question is: What happens if I unlock my bootloader while S-OFF? (Yes, it says s-off on the bootloader screen.) Will that solve my problem or do I have to go back to juopunutbear's hboot?
Click to expand...
Click to collapse
and what recovery problems are you having....flashing an hboot will not give you a recovery...and an ruu is an exe file not a ph98img file...those are OTA's.....if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
REV3NT3CH said:
i can help with that....its pretty easy if your already s-off
---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------
Click to expand...
Click to collapse
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
4218kris said:
i believe i can flash hboot with a ph98img yea? can you link me to the best/newest 2.28 i think.
Click to expand...
Click to collapse
that one or the this 2nd ph98img in my downgrade/upgrade guide work as well...that one is just radios and hboot....doesnt come with stock <3e> recovery
REV3NT3CH said:
if you need pure stock i can easily help you obtain it....i just need to know what exactly your trying to achieve
Click to expand...
Click to collapse
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
jrredho said:
Hey REV3NT3CH,
So, thanks to the help of so many in these parts, including you, I now think I'm S-Off and I'm very interested in bringing my phone up to the latest, completely stock OTA ROM. Can you help me with that?
Thanks!
cheers,
john
Click to expand...
Click to collapse
when you boot into your bootloader...does your hboot now say S-OFF....if so i can give you everything you need and what id suggest doing just prior to doing it
REV3NT3CH said:
when you boot into your bootloader...does your hboot now say S-OFF..
Click to expand...
Click to collapse
Yes it does.
REV3NT3CH said:
.if so i can give you everything you need and what id suggest doing just prior to doing it
Click to expand...
Click to collapse
That would be fantastic!
Thanks,
John
HTC has halted this firmware due to battery drain. I'm sure another firmware will be out in a week or two. I'm sure if you just flash a rom afterwards there will be no battery drain, its probably just something in the software. This firmware will let you flash all of the "newer 2.**" international roms such as Viper etc.. properly with new sound drivers.
Confirmed working first by "italyforever" - I could not test myself since I sold my M8, just wanted to help others out. Confirmed working by several other members too.
At&t 2.23.502.3 Ruu has just come out and I have had requests for bootable RUU. Here it is first from me! Place this file in the root of your ext sd card and boot to hboot and hit vol up to update. If you are soff you do not have to lock boot loader. If you are s-on you must lock boot loader first. Please follow my guide for the 1.58 bootable RUU for any questions. It explains everything. Do not try to modify file as it is singed and encrypted by HTC and will cause issues if you mess with it. If you try to unzip it, it will say corrupt because this is an encrypted file. Just verify md5 to make sure your file is good. The restore takes 14-17 minutes. Plugging in phone is a good idea so there is no chance of battery dying. It will do a bunch of different unzipping and installing. It will bypass certain things too, this is normal. Let the update finish. It will say update complete press button to reboot. Do not touch phone during this process! This is ONLY for the at&t M8, no other variant. CWS__001 or 11111111 cid required. This will erase your phone like new so backup anything needed. I am NOT responsible for anything that happens! Please click my thanks button if I helped you.
2.23.502.3 bootable RUU - https://www.androidfilehost.com/?fid=23622183712463537
Old guide - http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Has anyone tested this? I get my M8 hopefully by Saturday and hoping to run this RUU as soon as I get it.
italyforever said:
I needed to go back to stock this morning, i used this. worked perfectly, thanks:laugh:
Click to expand...
Click to collapse
Does this re-enable S-On or would you still have to do that manually?
K.AuthoR said:
Does this re-enable S-On or would you still have to do that manually?
Click to expand...
Click to collapse
No. This will not touch bootloader or security. Never go s-on.
This will give me stock recovery?
snoopy1e11 said:
This will give me stock recovery?
Click to expand...
Click to collapse
Yes it should
an0ther said:
HTC has halted this firmware due to battery drain. I'm sure another firmware will be out in a day or two.
Confirmed working by "italyforever" - I could not test myself since I sold my M8, just wanted to help others out.
At&t 2.23.502.3 Ruu has just come out and I have had requests for bootable RUU. Here it is first from me! Place this file in the root of your ext sd card and boot to hboot and hit vol up to update. If you are soff you do not have to lock boot loader. If you are s-on you must lock boot loader first. Please follow my guide for the 1.58 bootable RUU for any questions. It explains everything. Do not try to modify file as it is singed and encrypted by HTC and will cause issues if you mess with it. This is ONLY for the at&t M8, no other variant. CWS__001 or 11111111 cid required. This will erase your phone like new so backup anything needed. I am NOT responsible for anything that happens! Please click my thanks button if I helped you.
2.23.502.3 bootable RUU - https://www.androidfilehost.com/?fid=23622183712463537
Old guide - http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Click to expand...
Click to collapse
the file is broken i downloaded twice and both time got a corrupted file
JEANRIVERA said:
the file is broken i downloaded twice and both time got a corrupted file
Click to expand...
Click to collapse
Are you trying to unzip it? I have had multiple people tell me it works great. You cannot unzip an encrypted file, it will say corrupt. This is noted in OP.
an0ther said:
Are you trying to unzip it? I have had multiple people tell me it works great. You cannot unzip an encrypted file, it will say corrupt. This is noted in OP.
Click to expand...
Click to collapse
no one here has said that this work that's why i asked
JEANRIVERA said:
no one here has said that this work that's why i asked
Click to expand...
Click to collapse
Just finished restoring right now.
I came from Viper 2.2x, TWRP, and I re-locked bootloader before starting this RUU. I have never done S-OFF, so I was S-ON when I did this.
Reverted phone to 100% stock, no issues. re-unlocked bootloader and flashed viper again. Perfect.
Just used this to update from `1.58 since I couldn't OTA. Works perfectly! I was worried at one point when it kept unzipping and updating the system over and over, but after about the fifth time it finished. Thanks again!
Blaze9 said:
Just finished restoring right now.
I came from Viper 2.2x, TWRP, and I re-locked bootloader before starting this RUU. I have never done S-OFF, so I was S-ON when I did this.
Reverted phone to 100% stock, no issues. re-unlocked bootloader and flashed viper again. Perfect.
Click to expand...
Click to collapse
I am glad it worked for you. It is really nice when people like you read the instructions and you knew to lock your boot loader since you are s-on.
akitten007 said:
Just used this to update from `1.58 since I couldn't OTA. Works perfectly! I was worried at one point when it kept unzipping and updating the system over and over, but after about the fifth time it finished. Thanks again!
Click to expand...
Click to collapse
I am glad it worked for you. I added to the OP that it takes about 14-17 minutes and there is a bunch of unzipping, flashing, and bypasses so other people don't get worried and try to power off their phone. This is also a nice file to just leave on your ext sd card in case you need a restore on the go. If booting to recovery, you can just press vol down to decline the update whenever you go to hboot.
snoopy1e11 said:
This will give me stock recovery?
Click to expand...
Click to collapse
Yes, this will make your phone completely stock except it does not mess with boot loader or security "s-on / s-off"
Thanks. Worked
I need to update my base. Flashed and worked perfectly... I'm s-off and unlocked... So after flashing just fastboot recovery and flash new rom... = win! Thanks
Sent from my iPad using Tapatalk
an0ther said:
HTC has halted this firmware due to battery drain. I'm sure another firmware will be out in a week or two. I'm sure if you just flash a rom afterwards there will be no battery drain, its probably just something in the software. This firmware will let you flash all of the "newer 2.**" international roms such as Viper etc.. properly with new sound drivers.
Confirmed working first by "italyforever" - I could not test myself since I sold my M8, just wanted to help others out. Confirmed working by several other members too.
At&t 2.23.502.3 Ruu has just come out and I have had requests for bootable RUU. Here it is first from me! Place this file in the root of your ext sd card and boot to hboot and hit vol up to update. If you are soff you do not have to lock boot loader. If you are s-on you must lock boot loader first. Please follow my guide for the 1.58 bootable RUU for any questions. It explains everything. Do not try to modify file as it is singed and encrypted by HTC and will cause issues if you mess with it. If you try to unzip it, it will say corrupt because this is an encrypted file. Just verify md5 to make sure your file is good. The restore takes 14-17 minutes. Plugging in phone is a good idea so there is no chance of battery dying. It will do a bunch of different unzipping and installing. It will bypass certain things too, this is normal. Let the update finish. It will say update complete press button to reboot. Do not touch phone during this process! This is ONLY for the at&t M8, no other variant. CWS__001 or 11111111 cid required. This will erase your phone like new so backup anything needed. I am NOT responsible for anything that happens! Please click my thanks button if I helped you.
2.23.502.3 bootable RUU - https://www.androidfilehost.com/?fid=23622183712463537
Old guide - http://forum.xda-developers.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556
Click to expand...
Click to collapse
thank you so much! I've been trying to update my firmware for awhile. AT&T wouldn't let me update when they said I had an update and then it kept saying that I was up to date. Now I can enjoy viper Rom. You're the best!
.
Downloaded multiple times and keep getting a corrupted file
Don't unzip it
.
I'm not