Hi there!
I have been having difficulty reloading/flashing my carriers RUU/stock rom, for my HTC Amaze 4G/Ruby from bootloader and also 4Ext.
My carrier is Mobilicity and I’m looking for the Sense 3.6, ICS 4.0 stock rom. I’ve posted in a different thread but believe I have narrowed it down.
After a massive amount of research, the only link I can find is this one http://forum.xda-developers.com/showthread.php?t=1617644
And I try to flash the zip file under Mobilicity. I’ve tried through bootloader (both unlocked and relocked modes) and 4 ext as well. When I try to flash it from 4Ext it gives an error and says STATUS 7. Bootloader says….
ph85diag.zip no image!
ph85diag.nbh no or wrong image!
PH85IMG.zip loads up, a blue progress bar eventually finishes, then it says
PH85IMG.zip ... checking <-----t with a yellow progress bar
…Then it takes me back to the bootloader screen.
For some reason or the other, I am able to reload/flash T-Mobile’s RUU ICS 4.0 rom, however, it doesn’t do me any good as it won’t recognize my mobilicity SIM card. My phone is set to S-ON which I think is the problem.
I would like to try an alternative correct RUU other than the one in the link above, if anyone has one? Or, I am open to suggestions, I’m not sure how to get it to S-OFF – someone provided me with instructions, however, the requirements is that I command it from linux, and I only have access to Win XP sp3.
Any help would be immensely appreciated. Such a beautiful phone to just through to the gallows.
Thank you kindly!
jonnybbadd said:
Hi there!
I have been having difficulty reloading/flashing my carriers RUU/stock rom, for my HTC Amaze 4G/Ruby from bootloader and also 4Ext.
My carrier is Mobilicity and I’m looking for the Sense 3.6, ICS 4.0 stock rom. I’ve posted in a different thread but believe I have narrowed it down.
After a massive amount of research, the only link I can find is this one http://forum.xda-developers.com/showthread.php?t=1617644
And I try to flash the zip file under Mobilicity. I’ve tried through bootloader (both unlocked and relocked modes) and 4 ext as well. When I try to flash it from 4Ext it gives an error and says STATUS 7. Bootloader says….
ph85diag.zip no image!
ph85diag.nbh no or wrong image!
PH85IMG.zip loads up, a blue progress bar eventually finishes, then it says
PH85IMG.zip ... checking <-----t with a yellow progress bar
…Then it takes me back to the bootloader screen.
For some reason or the other, I am able to reload/flash T-Mobile’s RUU ICS 4.0 rom, however, it doesn’t do me any good as it won’t recognize my mobilicity SIM card. My phone is set to S-ON which I think is the problem.
I would like to try an alternative correct RUU other than the one in the link above, if anyone has one? Or, I am open to suggestions, I’m not sure how to get it to S-OFF – someone provided me with instructions, however, the requirements is that I command it from linux, and I only have access to Win XP sp3.
Any help would be immensely appreciated. Such a beautiful phone to just through to the gallows.
Thank you kindly!
Click to expand...
Click to collapse
OR else a nandroid back up of a mobilicity rom :good:
Related
Hello Everyone,
I hope there is an obvious solution that I am just missing. I have the Amaze 4G on Wind Mobile, I rooted, then flashed the Energy rom. Then I wanted to return to stock. I have followed more tips, tricks, guides, suggestions, how-to's then I can count so here is where I am at.
I can still get into hboot/fastboot as well as whatever recovery I happen to flash with Hasoon2000's kit;
hboot version is 1.93.0002
I am still S-ON
I was running the official stock ICS; I rooted after that update; so I don't think that I need to return to GB then OTA update to ICS.
I have tried the three Wind mobile stock RUU's that are floating around; the first two fail because my hboot is a newer version.
I have downloaded the Wind ICS OTA file, extracted the stock boot and recovery .img files and flashed them over with the Hasoon2000 kit, renamed the un-extracted ICS OTA file to PH85IMG.zip (with only ONE .zip), copied to my external card, relocked the bootloader, removed the battery and rebooted. It finds the file, loads, checks, then sends me back to the hboot screen. I have tried then rebooting the phone and eventually it ends up at the white HTC boot screen and sits there. I have tried leaving it there for 30 + minutes and unless it might need days I don't think it is going anywhere.
I have managed to boot into the stock recovery which at times even gets a progress bar, reboots, and sits at the HTC screen; other times I get the red triangle.
I know other people have had issues similar to this as I have read an endless number of threads on the subject, none of the suggestions have worked thus far.
Any help is greatly appreciated. Thank you!
EDIT:
I can still install custom roms so not all is lost, but I would still like to get back to the stock rom and it still isn't working. I tried using the tool from this thread http://forum.xda-developers.com/showthread.php?t=1526316 to reset my version and then run the update wizard and it recognized that I was at version 1.00.0000 but still failed.
Also installing PH85IMG.zip from the sd card gets to the parsing stage and then goes back to hboot.
Any ideas?
Tried to delete this thread but couldn't figure out how so I'll just edit it again.
I finally found the following thread http://forum.xda-developers.com/showpost.php?p=27058110&postcount=44
It doesn't specifically state that this problem applies to Wind mobile users but given the issues I am having I assume it does.
So I need a nand backup file! I would have my own except the SD Card it was saved on has died. So if anyone out there is using the Amaze 4G on Wind Mobile and can send me their Nand backup I will be forever grateful!
Unless of course those reading this know of an alternative solution?
Thanks in advance!
I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
joebandli said:
I have an Evo3d through Sprint and about a month ago they started sending me notifications to upgrade to Ice cream sandwich. I did such and immediately my touchscreen started going crazy. If I used the keypad in either position it would just randomly add letters all over the place, the home row would just stop working, and the phone would occasionally appear to lock up. I took the phone into the Sprint repair center and they told me they would not do anything with it because there is a incredibly small dent along the bezel that happened when I dropped the phone over 1 year ago. It has worked for at least a year on Gingerbread with 0 issues. I was then left to my own devices and after looking at several guides finally decided on a guide video to use for flashing to a custom rom, which I was hoping would fix the problem.
I unlocked the phone, simple enough, and from what I could find came to the conclusion that the guide which was for HBOOT-1.50 S-ON was the same image and process for my phone which is HBOOT-1.58 S-ON. I then used the cwm-4.0.1.4-shooter image to load into a "revolution" menu which allowed me to select the ROM which I had previously loaded onto the phone in the sdcard root directory. I selected MeanROM-v45 as per the video's recommendation and it told me it installed. I then rebooted the phone and saw the fancy new loading animation, then I saw the phone background, then I saw the unlock ring, then the phone rebooted in a never ending cycle. After reading the countless threads on what could be wrong, I tired MeanRom-v4.1, and the stock rom which I was led to believe was "Kingdom_Sprint_WWE-0.81.651.0_Radio_1.05.00.0429_NV-SPCS_2.25_0429_PRL21078_test_188785" and it gave me an error when trying to install. I then did more reading and found a new boot image which is "recovery-clockwork-5.0.2.0-shooter" and another rom which claimed to be stock which was "Shooter_S_Sprint_WWE_2.17651.5_odex". This rom reset the boot animation to the stock Sprint one, but alas all my phone does is constantly reboot, except I did notice it says "Safe Mode" in the lower right hand corner of the background before it reboots. I then tried to use the "RUU_Shooter_ICS_35_S_Sprint_WWE_2.89...." application which I was linked to from one forum post or another, and it gives me an error 155, then gives me another error when it tries to recover. Does anyone know how to correct what I apparently messed up? Sometimes some of the instructions are filled with lingo that i don't quite understand, but i can follow directions if they are sufficiently given.
Click to expand...
Click to collapse
Well since you are S-on and unlocked you have to relock your bootloader to run ruu files. Fastboot oem lock is the command you run in fastboot. Also with older ruu files they only work with older roms and such. as for newer ones like the ics ruu, ics roms such as meanrom ics v2.6 works with only hboot 1.58 and newer firmware. I understand that sometimes these guides and tutorials are not clear enough. That's why you got to ask questions. We are here to help so you can get the best out of your experience with your evo 3d. I would not rely on sprint techs too much because sometimes they will just tell you to do a factory reset. Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy. If you want to flash a custom rom after you do the update just unlock your bootloader again. Flash 4ext recovery for your device and do some research on what roms and kernels are compatible with S-on unlocked bootloaders. Fyi 4ext recovery has this thing called the smart flash option that allows you to flash kernels through their recovery without having to do through fastboot. Or try Joeykrims Flash Gui Image. All in all, gaining s-off is the best route to solve most of your problems and makes it easier to flash roms and kernels. There is a method for gaining s-off with the ics ota and hboot 1.58. Just do your research. Best of luck to you.
Oh yeah don't forget to hit the thanks button if I helped you out at all.
Jsparta26 said:
Your phone should be fine. Just relock your bootloader and run the file from the bootloader screen and everything should be peachy.
Click to expand...
Click to collapse
Which file are you reffering to from the bootloader screen?
When I Vol Down + Power On this is what I see
***RELOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.58.0000
eMMC-boot
May 17 2012,15:06:44
HBOOT
Now that I have relocked the phone it tries to load PG86DIAG.zip (No Image!), PG86DIAG.nbh (No Image!), PG86DIAG.zip (No Image or wrong image!), PG86IMG.zip, and then it does "Checking..[PG86IMG.zip]" and returns Main Version is Older! Update Fail! Press <Power> to reboot.
I know several of the tutorials and even the "How to Fix" guides I was trying to use to restore the phone has me copy PG86IMG.zip to the sdcard root, so I am guessing I need a different image. Now the only problem is that I have to re unlock the phone so I can "fastboot boot cwm-4.0.1.4-shooter.img" so that I can mount the phone and transfer files to and from it (unless there is another method I can use other than adb, because it does not see it as an attached device)
So what I should do is:
1, Unlock the phone again
2, fastboot boot cwm-4.0.1.4-shooter.img
3, Mount the phone, and copy a file named "PG86IMG.zip" (Which I need to obtain the correct one)
4, Unmount the phone and then relock it?
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
joebandli said:
What would the next step be and do you know where I can get the correct file?
I appreciate the response, I am at my wits end and was about to go waste some cash buying a new phone.
Click to expand...
Click to collapse
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
ramjet73 said:
Forget about PG86IMG.zip files. Since you are S-ON they have to be signed by HTC and there are very few of those around.
You need the 2.89 RUU.exe from one of the links in this post. Flash that from Windows, then HTC unlock again and follow the guides to flash a custom recovery and then root the stock ROM or a rooted custom ROM.
ramjet73
Click to expand...
Click to collapse
Thank a ton, that worked to put my phone back to "working" icecream sandwich.
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
tigerxchaos said:
Hey all,
So I'm sending my Rezound back to Verizon as a warranty replacement, and today I tried to revert it to stock. It was rooted, S-OFF, with Infected ROM installed (based off CM10.1.2). However, the re-lock process didn't work correctly. I received the below error in the command prompt when I tried to relock it with fastboot oem lock:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
The steps I took are as follows:
1) Re-installed RUU using this file: Rezound_Global_ICS_4.03.605.2_Full_RUU_PH98IMG (renamed to PH98IMG and done through bootloader)
2) Attempted fastboot oem lock (and got the above error)
This process worked on a different Rezound that I also received as a warranty replacement which itself was also defective, but in that case I locked the phone first and THEN flashed the RUU. In my haste today I accidentally flipped the order to what you see above.
Now, the phone will not go back to ***LOCKED*** up at the top. Instead, it says ***RELOCKED*** which is not what I want here. I am afraid to set the S-OFF flag back to ON while the phone is displaying "relocked". The RUU did work, as the phone has stock firmware on it once again and boots up fine. I attempted to relock it again and RUU it again with the same results, still got the above error and still showing ***RELOCKED***.
I did some research but couldn't find anything specific to the Rezound; the nearest thing I was able to find was some info about how CleanROM can cause this on a different device, and something about mainver, which I'm not familiar with. I did use CleanROM for nearly a year before going S-OFF and moving to CM10. If anyone has an idea on how to fix it I would be eternally grateful.
Click to expand...
Click to collapse
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
mikeyk101 said:
You need to get ahold of either the ph98img.zip for 3.14.605.12 like HERE and put it on your sd card and run that at hboot after renaming it ph98img.zip or get a copy of the full RUU (RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed.exe) for 3.14.605.12 at ONE OF THESE LINKS and run this on your pc with the phone connected by the USB cable. Make sure on the exe version that you have USB debugging enabled. The RUU you used is a leak and not an "official" full RUU. You need to run a full official RUU to accomplish what you want and the full RUU for 4.05.605.14 has not been released yet. If you use either of the ones I provided links for, the hboot will show "locked" but an earlier version. Then if you want it to show the latest version, leave your SIM card in the phone, let it bootup, when the setup starts, just press the home key and it will bypass setup. The get into settings and into the software update and run that. It will update to the next version. Let it reboot and again bypassing the setup. Then run software update one more time and you will have 4.05.605.14 which is the latest version and your hboot will now show locked. Now you can go ahead and re S-on the phone.
However, I have heard over and over that Verizon never checks the software on the phones and you could just send it back the way it is now. But I'm sure that you are paranoid about this like I am and want it fully stock again so there are no red flags...
Click to expand...
Click to collapse
Thanks very much for the suggestion. I'll give this a try shortly.
It's just weird that this RUU successfully took another phone back to fully stock. The only difference between the two is that the other phone never had CleanROM installed on it.
EDIT: Just realized one other thing, at one point I manually updated the radios on the first phone (the one that is now giving me trouble) but didn't do this on the one that went back to stock properly. I'm going to give the PC method a try since it mentions the radios in the file name.
Sent from my SCH-I535 using xda app-developers app
Went ahead and ran the full RUU from my PC as suggested above. Unfortunately it didn't accomplish the goal. The RUU completed successfully, but HBOOT still says ***RELOCKED***. I tried unlocking and then relocking again, and got the same error:
(bootloader) Lock successfully...
(bootloader) TZ_HTC_SVC_DISABLE ret = -131073 (0xFFFDFFFF)
FAILED (status read failed (Too many links))
finished. total time: 0.958s
Not sure where to go from here.
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
mikeyk101 said:
With S-off, the radios shouldnt matter. Seems to me when I s-offed this latest phone, it was on 4.05.605.14 and I had to unlock the bootloader to do the s-off. After I achieved s-off, I dont remember relocking, I just ran that ph98img from android police. The bootloader then displayed that it was locked. Maybe try to run either of those RUUs after unlocking the bootloader.
Click to expand...
Click to collapse
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
tigerxchaos said:
I think the key is this error I'm getting via the command line. I didn't get it with the other phone and on that one, after I relocked, it said **TAMPERED** across the top; after the RUU, it just said **LOCKED**. This one is saying **RELOCKED** instead of **TAMPERED** and it's the one that won't go back to locked after a RUU. If we can figure out what's causing this error, might be the key to solving the issue. However, that's where I'm falling short in my research.
Click to expand...
Click to collapse
IIRC, when it says Tampered across the top of the bootloader, it just means that the bootloader is unlocked and that a other than factory recovery has been installed such as TWRP or AmonRa. Relocked means that the bootloader had originally been unlocked at some point and then locked again. If it were me, I would
1. Try to unlock the bootloader again,
2. Reinstall either AmonRa or TWRP if either is not there, then
3. Wipe everything such as cache, dalvik cache, wipe ALL data/factory reset, and possibly even wipe system.
(Normally you would not want to wipe system because pretty much everything is then gone but since you have the RUU.exe, you have the means to reinstall the original OS.)
4. After wiping everything above, reboot from recovery to bootloader and try running that RUU again.
You are right though and this is weird. Normally when you run a full factory RUU, it should reset EVERYTHING back to factory original condition.
BTW, I have just been trying to come up with a workable solution. I was kind of hoping that someone with more experience would pipe in. Unfortunately it looks like the Rezound and development is dying a slow but sure death and many have moved on...
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
mikeyk101 said:
Just trying to think of alternate solutions again, I know that it is possible to change just the hboots by using the proper ph98img.zip files. I remember using one awhile back when I was unlocked that changed the hboot from tampered to read locked. I cant find the thread but I think it came from Vinylfreak . I attached it in this post but it will read 2.27.0000 as the version. I have also included the factory 2.28.0000 in a separate ph98img file below. Maybe try one of these and it might take care of it. Put these on your sd card, change the name of the first one to ph98img.zip and get into the bootloader hboot and let it update. If that doesn't work, try the second one.
If needed, I could also probably make one for the 3.05.605.12 and upload that as well. I just need to check the hboot version it came with.
ETA, I think the first one came from THIS THREAD and it is just renamed by me so I could keep track of what it was...
Click to expand...
Click to collapse
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
tigerxchaos said:
Thanks again for all your suggestions, you've been REALLY helpful.
I'll try out the hboot method you listed above and see what I can come up with. My concern there is that I think vinylfreak's hboot was an engineering hboot, which will brick the phone if I try to go back to S-ON with it installed.
Rezound development is actually still alive and well, among several dedicated developers who are working on some great software for the phone. @Flyhalf205 has been releasing regular updates to his Rezound build of CyanogenMod 10.1 and as I understand it, is responsible for a ton of the recent progress made on bringing Jellybean to the Rezound. @IAmTheOneTheyCallNeo has a fantastic ROM based off of CM called Infection, and a variant of it based on PACMan called Tron. @iHateWebOS has a great kernel called HIRO, @Snuzzo has another one called Funky Kernel, and there are other devs that I'm less familiar with working on other projects. Check out their work, it breathed new life into my phone.
Click to expand...
Click to collapse
I didn't quite elaborate on what I was thinking. But you are absolutely correct about doing S-on with an engineered hboot and that it would brick it. However, since it is going back as a warranty replacement, maybe bricking it might not be such a bad idea. LOL. I should have added that by using the fake locked hboot, it may trick the phone into thinking it really was locked. And then flash the second one and the banner just might stay showing locked. I have actually gone back and forth between the two but have always been locked so I am not sure how yours would work out. BTW, that second one is the original factory hboot extracted off the full OTApkg.zip for 4.05.605.14 and packaged in a ph98img file. I extracted it in the event that I might have to S-on again sometime in the future. I also extracted the original factory recovery and packaged that in a ph98img file as well in case I ever had to revert back to stock for the same reason. I just have to unroot (I am using supersu), reinstall the factory recovery, reinstall the factory hboot, do a factory wipe in recovery and finally do the write secure flag command and I am golden. I know that there are still many very cool roms out there. I used to be a big fan of CleanROM but that is no longer supported by the developer. Since then I have gotten kind of used to using a rooted stock rom. I know I may be missing some bells and whistles but I mostly rooted and S-offed just because I could and have a few more choices available to me. I hope you are able to find a solution.
I had this happen a wile ago what worked for me was that I ran the ruu to back to stock, then go through the unlock process, once unlocked s-off. Once s-off run ruu, then follow directions in this link http://forum.xda-developers.com/showthread.php?t=1612937
Sent from my Infected Rezound using xda app-developers app
Ok, I will try to give as much info as I can, please let me know if there is anything else I should provide. I really appreciate any help and advice as I've been pulling my hair out for the last 3 days, spending 10+ hours trying to get my Amaze back working.
Problem started a few days ago, phone shut off, when it powered back on it was stuck on the White HTC logo. That same day the phone died completely and would not power on at all, not even the amber light. Eventually the amber light would blink the but phone wouldn't charge. I fixed this first issue by jump starting the battery with a 9V battery, something someone suggested on a thread. Worked great to get the phone charging again... but that's it. So basically I have access to the HBOOT/Fastboot and EXT4 Recovery menu's, and there is no OS on the phone, I know for sure now because I wiped the system.
When I try (but fail) to install the RUU 1.41 exe, and it checks the phone, i comes back saying my "current" version on the phone is 2.14.661.2 even though there isn't any OS on there...
Bit more background info. I purchased this phone last year off someone, it was running 4.1.2 and the bootloader was unlocked. It *is S-ON though.
Whatever else this guy did, I'm not sure as this is what I can tell, however the CID pulls up as Telus001? which the guy did tell me it was a Telus phone.
So I'm trying to load the Telus stock rom and I've been getting nowhere and pulling my hair out. I'm 10hrs in and no further then I was. So first I downloaded the Telus RUU 1.41 exe from the stock rom but it gives an Error 43. I tried this with both the bootloader locked again, and unlocked. I then downloaded the OTA 2.14.661 zip from the stock roms, and renamed it to PH85IMG, stuck that on the Ext SD card. Problem is when it boots into the HBOOT it actually see's the file, loads it, then checks it, but then returns me to the main menu. I don't get promted to update. Now I've tried this too with the bootloader unlocked, and locked. So a third go, I extracted the Rom from the 1.41 RUU and made that PH85IMG, tossed it onto the SD card and again this time it actually went further but gave another error.
I have tried to Sideload the above Roms through recovery but they give error's.
In that All In One program there is an option to fix the Mainver error, however when I run that all I get is "Device not found". The phone IS loaded under device manager as HTC Phone as I had installed the drivers. I've tried to google this fix but I can't get anywhere.
Everyone has said on forums that sticking a PH85IMG.zip file on an Ex SD and having it boot into the HBOOT menu will rebuild the phone, but I'm out of idea's how to get there because it loads the rom's, checks them, and then boots me back to the menu. There is only 2 Rom's I can find for Telus, and that's the 1.41 EXE or the OTA 2.14.661.2. My HBOOT version is 1.93.0002, RUBY PVT SHIP S-ON RL.
Thanks in advance for any help/suggestions, desperately just want my phone working again. I feel like I've been to the 4 corner's of google trying to solve this problem.
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
darkshadow1997 said:
Strange This should not happen.Also if your phone is running 4.1.2 which should be a custom then that means your phone was updated to ics so the ruu.exe will fail.if you have access to 4ext recovery then you can flash any custom rom to boot your phone.But if you want stock and both of the stock roms for your carrier is not working then the only thing you can do is s-off the phone then use supercid so you can flash any carrier's rom then flash t-mobile ics stock.Tell me if this worked for you.
Click to expand...
Click to collapse
Got it going!! Thanks for the suggestions. What did it in the end was this thread --> http://forum.xda-developers.com/showpost.php?p=27058110
I had EXT4 Recovery already, so I used his Zip and just flashed that. Phone came back up and is running great now... if only I had found his thread before the hr's and hr's I've been googling and trying things.
A few months ago I, posted a thread with a similar idea in mind however, the only answer I got was (I'm paraphrasing) "Why go back to stock,the custom ROMS are much better anyways". Well the time has come where I figure out the "why?". Yesterday I brought the phone into Wind for a check of why it's not sending MMS messages when the data is on (strangely enough it turns data on while sending the mms but, that's a story for another time). The people at Wind refused to look at my phone and told me to come back when it has stock firmware. (because, obviously I haven't returned to stock yet). Now from what I understand, from doing some research today on the forums, that the HTC Amaze (Wind Variant) has some weird software issues upon flashing a T-Mobile based ROM which I can link back to Speed Rom. So, I do the standard "Relock the bootloader and run the RUU.exe" and it just comes up with an error saying my hboot is the wrong version. The forums are pretty blank on ways to get around this (well besides going S-OFF which is a problem considering I need to bring my phone in to get the MMS issue checked. Also, I don't have that level of confidence in myself to insure I don't destroy my phone when going s-off). So, I was wondering if anyone has a fix for the issue. I'm confident that someone could possibly help me with my issue. (PS my current ROM is the latest Cyanogenmod 10 nightly, and I'm using 4ext recovery on the Amaze/Ruby).
Hope, I can get this issue resolved and thank you for helping me out with what ever problems I've had on my journey with this phone.
P.S: I didn't mean to double post the same question it's just I really needed this problem solved. I hope you can forgive me. (I fully understand if I can't return to stock under these circumstances.)
It's funny, I'm kind of in the same boat, except for 2 "minor" differences:
1) The "Smart Flash" on 4EXT never worked for me (and has consistently corrupted my internal SD card, but been able to fix it each time), so I have S-ON yet
2) I've rooted the phone itself and unlocked the bootloader, but the HBOOT is 1.93.0002, and from what I've seen, the latest firmware patch is .2222 although that really shouldn't matter
This is my 2nd HTC Amaze, and the first time I've gone through the rooting and that, took me at most an hour to complete, including time spent choosing a CMOD (I ended up with 7). This time around...I'm practically pulling my hair out because I cannot perform the S-OFF via Linux (LiveCD of course) nor starting from "square 1". I seem to be in limbo with 4EXT.
I installed Viper Amaze 1.7.2, but continually got stuck on the boot screen. Further investigation revealed that I needed to superCID the phone, which in turn would be to S-OFF first.
Additionally, I've downloaded and flashed the "stock ICS" ROM (since that was my stock ROM to begin with, naturally upgraded ICS), renamed to PH85IMG.zip yadda yadda. It recognizes and loads, but never "updates", more or less does anything after the loading bar on the bootloader.
So, just to try how much I've dug myself in with this, I've downloaded and tried 2 other ROMS, both saying "bad" (no status 7 error like the RUU flash).
I want to try out the Viper Amaze ROM since so much work and effort went into it, and it seriously looks awesome, but because my original tool that I used (HTC Super Tool) didn't require me all of these extra steps (and I didn't remember the program until now), I want to return back to stock so I can start over in a sense and complete those couple of steps that I inadvertently missed. I really feel like I'm missing something stupid.
Out of 7 Android phones that I've completed the custom ROM setup, it has to be this phone...
Anyways, tl;dr here's what I got:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
darkandshadow said:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
Click to expand...
Click to collapse
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Megapead said:
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Click to expand...
Click to collapse
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
darkandshadow said:
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
Click to expand...
Click to collapse
I tried, that EXE seems to only be for update from Gingerbread purposes or, was broke after I flashed a T-Mobile ROM on the device.