Related
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...
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.
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.
I want to install an OTA, but I had rooted it using TWRP and then followed so many procedures in trying to restore to stock that I think my phone's wasted. (It's functioning normally, but I can't help the feeling I've done something untowardly to it).
I have been doing a lot of reading, but I apparently suck since nothing seems to make sense (or that everything seems so disconnected). It appears that what could be one long, detailed post about something is to be found in many different posts, but I understand that since there are so many phones and each one probably needs its own way of being handled. So without complaining any further, I'll just let you know what I've done so far, and hopefully someone is able to tell me what the hell is wrong with me. And my phone.
Here's what I have with me right now:
Device: HTC One SV (Boost mobile) - K2_CL, OS- 4.1.2 (the OTA is 4.2.2)
Tampered, relocked, s-on.
adb is installed
fastboot is installed
android SDK with 4.1.2 and 4.2.2 packages installed
htc toolkit utility is installed
recoverytest.img from androidruu files.
revone
All right, I installed adb, fastboot, an htc utility toolkit, downloaded 3 different img files (one says recoverytest.img, which is from androidruu.com/k2_cl, another one was put here on xda by one of the members, and that was simply recovery.img, and another one called HTC_One_Sv_K2_Ul_boot_signed.img <-- this is probably the wrong file since my bootloader screen says k2_Cl).
Prior to this, a few months ago, my phone was rooted. SuperSU was working fine, and one day somehow I lost the root access when SuperSU upgraded. Tried a few methods to upgrade manually but none worked. Not sure if this is of any importance.
So after installing all those above, I did a variety of commands like revone, fastboot flash recovery.img, fastboot oem lock, fastboot flash boot recovery.img, all based on what was mentioned one one thread or another on the forum and mostly all of them gave me some kind of an error.
So I'm stuck now. My phone does nothing. When I reboot from bootloader, it says in red "this is for development purposes only, blah, blah". When I download the update and try installing it, the phone simply restarts. When I try to do factory reset from the hboot, the phone simply goes back into fastboot menu. My phone apparently doesn't have an RUU, only a recoverytest.img.
Here's where I am and I want to do what next. I jsut installed android sdk, and installed 4.1.2 package (which is the current version on my phone), and I want to update to 4.2.2, which is the latest update for htc one sv on boostmobile (installed the package for that in sdk also).
(A lot of people were also asking for cid, mid and phone model, and I have no clue how to make sure that the .img file is the same as my phone's).
I know I am all over the place, and call me a knucklehead, but I genuinely do not understand a lot of the things that are mentioned on the forums. Every thread mentions a process, and within each process is contained a subprocess which I equally do not know.
Thanks for any help with this!
PS: While I go from fastboot usb to hboot, the screen flickers for a couple seconds an dmessages like "sd checking: no image or bad image" appear for a couple seconds and then I see the hboot menu.
Edit:
Here are some, but not all, of the forums/threads I was trying to follow:
http://forums.androidcentral.com/verizon-droid-dna/287135-revone-s-off-root-method-help.html
http://androidforums.com/one-sv-all...root-without-overwriting-recovery-kernel.html
http://forum.xda-developers.com/showpost.php?p=38018890&postcount=78
http://forum.xda-developers.com/showthread.php?t=2292432
http://forum.xda-developers.com/showthread.php?t=2405050
http://forum.xda-developers.com/showpost.php?p=42371333&postcount=1480
http://forums.androidcentral.com/htc-one-sv/279026-htc-one-sv-ruu.html
http://www.androidfiles.org/?developer=K2_CL
http://forum.xda-developers.com/showpost.php?p=43266179&postcount=6
The way I understand how to do this (in layman terms) is as follows:
1. Restore to stock {by first turning S-Off, then lock the bootloader, and then RUU. I cannot get S-off using revone (revone failed, error code 2 or error code -1); the bootloader is "relocked", and I cannot get to do anything with the RUU (iow I don't know what to do with it)}.
2. Restore to factory settings.
3. Download and install the OTA 4.2.2 update.
You don't need to go S-Off to return to stock, just relocked. Here is the RUU for your phone:
http://goo.gl/0cgV6d
Run as admin. Turn off anti-virus. Have more than 30% battery life. Follow instructions as the program loads and accept whatever.
OTA zip:
http://goo.gl/ckfYQj
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
ravisoni said:
The RUU worked, thank you so much!
Is this OTA.zip 4.2.2? Or is it a newer version?
Click to expand...
Click to collapse
You're welcome. It is the 4.2.2 update. My understanding is that there is nothing newer. There were reports of a 4.4 update for the Boost variant, but believe it was a mistake, or at least jumping the gun by quite a bit.
So yesterday I had my Aria in my pocket and I guess the power button got nudged and the screen turned on, lo and behold I pull my phone out of my pocket to find the lovely words written on the screen that too many pattern attempts have been attempted and that the device is locked. Only problem is I use this phone for everything but the phone function, I don't even have a sim in there. So with WiFi off, and no mobile network I was stuck for a bit. But then I finally sat down with it and luckily I had kept USB debugging on so I used adb to hack it. And that is where my urgent problem starts. After finally unlocking it I decided to might as well upgrade it, it was running 2.0.2 I believe Liberated ROM with CWM. So I started browsing around because I haven't really worked with this phone before all that much, I ended up reflashing to stock rom and then was going to use a nifty tool to get my hboot to 1.02, well it worked, the nifty tool flashed my hboot alright, along with my ROM and everything else there was. I am now stuck with a brick, the phone goes to the boot logo and then reboots... over and over and over until I pull the battery. I was charging the phone the whole time while working on it and after the tool was done flashing the hboot I unplugged the phone and a long list of errors ran down the screen of files that the OS was missing. I can get into fastboot, haven't had luck with any reflashs, adb is dud (while in recovery computer recognizes the adb connection but adb only lists the device as inactive. Ever since I lost my Inspire 4G this was my only working mobile device. If you have any tips tricks or clues as to how or if it is possible to come back from this destruction I am all ears.
Thank you in advance :fingers-crossed:
To clarify a bit further, the part that screwed me was the Upgrade HTC Gratia HBOOT for AlpharevX S-OFF tool. It was chugging along just fine up until the very end. The original sites listed for making a gold card are all dead but I managed to find a working one. Now I am trying to figure out what went wrong and why.
LIBERTY PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-031b
TOUCH PANEL-STN21_03
RADIO-7.13.35.13
Nov 4 2010,23:12:58
The time and date are frozen
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
dansou901 said:
First you should S-OFF your phone with revolutionary. Then you need to flash a working recovery image and reflash ROM from there. Should work. If this still doesn't work, flash a modified hboot from the Development forum and see if you have any luck with that...
Click to expand...
Click to collapse
I cannot get revolutionary to find the device, the system version is 2.37.709.11 and I cannot do anything, if I try flashing anything the sig verification always fails.
(EDIT: Well I got lucky, found an asian RUU with same version, reflashed phone, S-Off, flashed unofficial CWM recovery and unofficial cyanogen 11.)
The problem I was having with revolutionary not recognizing the device was because my hboot version was too old (0.57). I used this AT&T Update package to get back to stock 2.2 and revolutionary worked straight away.
HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe
http://www.mediafire.com/download/mch2657rdy8aqct/HTC_Aria_for_ATT_Android_2.2_ROM_Update.exe