I have the Wind Amaze 4G
I tried to get S-off today and being unsuccessful I ended up at the screen where it shows the 3 arrows (2 in a circle and 1 pointing at the phone). I am assuming my stock rom got corrupted.
I can still get into fastboot and recovery (have CWM installed). Bootloader is unlocked (I can still lock/unlock it). I can get into CWM with the bootloader unlocked.
What I want to do is to revert back to stock and found a Wind/Globalive rom, but it's in an exe file. I ran it, but got back an error saying bootloader version incorrect.
I can't find any stock Wind zips...according to juopunutbear's instructions I need the stock rom...
Any help would be appreciated.
Wind's RUU is on the first link:
http://forum.xda-developers.com/showthread.php?t=1570807
I have that, but when I used it (with bootloader relocked), it spits out an error saying Bootloader version error and exits
Then why don't you just keep trying to get s-off, some people said they had tried for hours before they succeeded. And btw, how far you get before s-off install fails?
At the wire trick when it restarted and said failed.
I tried to complete s-off and where it says to do the wire trick, no matter what I did it just kept repeating "Do the wire trick now!".
Right now I'm downloading a custom rom (Energy 3.10) and see if I can flash it on with CWM then try to revert back to stock using that Wind/Globalive exe file and go from there.
I guess while I am waiting on the download I'll keep going with the s-off.
If it works, then I'm flashing the ICS update onto the phone directly and be done with it.
What I don't understand is why I can't revert back to stock in the mean time.
Did you see this video?
Edit: May be something's wrong with the RUU. Actually, there was a flame war recently because someone had posted a broken RUU for T-Mobile, but no one mentioned anything about the Wind one, so I assume its working fine... Go to xboarder56's website an ask him, he was the one who was providing the RUUs for the community
First I'd like to thank you for helping. I really appreciate it.
Now I am attempting the s-off again, got a bit further except after the wire trick it says cannot find device.
As for xboarders site, I can't seem to find it...
No problem, I'll pm you x's site, dont think Im allowed to paste it here, its a long story...
so after several tries I managed to get s-off, I guess my timing was just off the first time and the time where it looked like it looped was me not making proper contact with the wire.
Few other unsuccessful attempts were poor timing, got it right finally after like 6 tries.
Got ICS loaded and s-off!!!!
Now to unlock and re-root then debloat this rom!
THANK YOU SO MUCH FOR YOUR SUPPORT!!!
Im glad it worked out, man, cheers
P.s. Also, you dont need to unlock the bootloader, the best way to install ICS is the one described here, thats how I did it, got ENG hboot, and worked like a charm...
Related
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Have you tried flashing a cwm recovery? I think I read someone had the same problem.seens your s-off you should still be able to flash a recovery, and after that's done then you can be able to wipe and flash anything you want, and you well even be able to downgrade your hboot.
Nope, it wont let me flash a recovery through fastboot...access denied (phone shows locked). I cant install it with "flash image gui" because i dont have root.
I know it should be an easy fix because I have the all important s-off...I just cant find how to do it.
taminrob said:
So I had some "help" from a well meaning visiting nephew who was playing with my phone and noticed that I had an update available and decided that I should really have the latest software on my phone...so now I am on 2.17 with hboot 1.5, locked bootloader and all with no custom recovery BUT I am still s-off. I have a NAND backup that is not to old that I did with CWM, but how do I get to that to install it?
I have been looking for several hours and cant seem to find a solution...maybe I'm just searching under the wrong keywords...nevertheless HELP!!!!!!!
I am in the process of downloading a 1.13 stock ruu. Will that work or is there a quicker way to get this done?
I would prefer to avoid HTC unlock if I can, and my understanding is that with s-off, I should be able to.
Thanks for helping bail my ass out guys and girls!
(I thought about it, but no, I didnt beat the kid...his intentions were good...at least they better have been...)
Click to expand...
Click to collapse
S-Off just means that the security is off, and you're able to write onto the boot partition of the phone when flashing a ROM, in one shot. If your Hboot = 1.50, you may have to unlock your bootloader via HTCDEV method, your phone gets wiped. Try HTC SuperTool, maybe it will work, since you're S-Off.
http://forum.xda-developers.com/showthread.php?p=21538250
Follow my post and the links in there should get you back to 1.4
Sent from my HTC Evo 3D using Tapatalk
Thank you, that got me back in where I needed to be! Was able to load CWM again and restored from my back up...now all I need to do is make since of all the conflicting instructions to do this update so the icon goes away...found some that are fairly clear, but the links are broken now that the upload sites are blacklisted.
Either way, just glad to have my hboot back where it belongs.
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.
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.
Hi everyone. It is currently 3:30am my time when Im writing this message. I was rooted, had TWRP and S-On and I installed a stock rooted rom. When it finally flashed (after a couple attempts) the phone told me that a password was required to decrypt the device. I never put one on there. So I went back to TWRP to restore my backup, but of course I am locked out of all the memory in the phone. I was than at a standstill. I thought that i would try and do RUU. Part of the procedure as most of you probably know is to re lock your boot loader and have s-off. Well I re-locked it but than found out that no one has figured out how to s-off hboot 1.57. So i thought that i would unlock the boot-loader again and try some other things with the recovery. Well I used WinDroids tool kit and it seemed like i unlocked the bootloader...at first. The pop up message giving me the warning about unlocked bootloaders poped up. Of course i selected agree. But i was still left with a Relocked bootloader. Keep in mind, it still deleted everything. Including the recovery. So now i have no way of putting a recovery on the device. I tried manual fastboot commands and they didn't work (but im not sure if im doing that right anyway). So now I am at a lost. Any help would be amazing. I just bought this phone and It would be very sad to have a paperweight on the first day. lol
I had the same (almost) issue with my HTC one.
I followed the instructions on WonderHowTo website. I am unable to post a link here, but you can get to it by googling "pushing twrp htc one". It should be the third link on the search page with the title, "How to Fix a Soft-Bricked HTC One by Flashing a New ROM". I completed step 4 and restarted and it worked. It might be different for you.
Also, I tried multiple roms and none of them seemed to work EXCEPT Android Revolution HD 31.6 by mike1986 . (This was the only rom that seemed to work. I tried multiple other ones but I just got stuck into bootloop. I am assuming it was because this one is Android 4.3 )
It seems to be working now but I am stucked with an older version of Android and I am not liking it
Good Luck and Try it at your own risk.