Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Waterheeter said:
Hello all,
I am brand new to the android community, and have come accross a problem that I can't seem to get fixed. I previously rooted/rom'd my EVO lte with mean rom a while back. I started to have wireless issues so I decided to spend some time learning/fixing the problems that I'm sure my noobness created.
I relocked my phone and unrooted it back to factory 2.13.651.1. After doing that I updated my phone via Sprints OTA updater. I recieved an update that took me to 3.16.561.3. After that was completed I preceeded to unlock my bootloader again and installed TWRP 2.4.1.0. When I try to install any ROM it appears to go well in TWRP, but it reboots right after it says "updating kernel, this may take a while". When it reboots it sits at the HTC white startup screen, it doesnt even flash the red developer letters under the HTC logo like it normally does when continuing to boot into recovery or the old ROM.
I did some search and have found that others had issues with TWRP 2.4.1.0 (http://forum.xda-developers.com/showthread.php?t=2048229&page=573). They rolled back to 2.4.0.0. The problem is that with the OTA update the touch sence in TWRP is broken unless you run 2.4.1.0.
Anyone else run across ths issue?
The solution is probably staring me in the face but my noob aura is blocking it. :silly:
Click to expand...
Click to collapse
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
polar2792 said:
So u was on 3.16 and unlocked it? Did u use dirty racun? Did it work? Sorry I accepted ota and want s-off rooted if possible.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I didnt use dirty racun to unlock, I used the fastboot method. I'm not developed enough in my knowledge to be s-off atm.
cruise350 said:
TWRP 2.4.1.0 broke something with flashing so you might have to relock and ruu to get back to normal. The problem is there is no ruu out for 3.16 and running the ruu for 3.15 may mess up your phone. I would try to flash the kernel separately by flashing with fastboot or flashgui and see if that allows it to boot into the rom. You may be able to run dirty racun and gain s-off since the hboot didn't change with the latest update.
Click to expand...
Click to collapse
On your notes I did some searching to learn what you were saying. First I tried to use the fastboot update 'meanbean-rom.zip' file but it produced errors:
archive does not contain 'android-info.txt
archive does not contain 'android-product.txt
error: update package has no android-info.txt or android-product.txt
I tried fastboot flash boot boot.img after extracting the boot.img from the .zip. After rebooting the phone stays on the white HTC logo screen but now populates the red dev notice. Looks like I'm going in the right direction
Thanks for your help so far.
I believe I have it figured out. I searched for an unofficial version of CWM recovery (all the XDA links for the evo lte have been removed for now due to bugs). I'll deal with those bugs as I was stuck without a phone until I got it figured out
Installed CWM 5.8.3.5 and flashed Meanbean Rom. Problem fixed
I'll put TWRP back on when they release a patch.
*Edit* spoke too soon. The touch interface doesnt work with meanbean due to the driver update (I'm guessing). Atlease I can see any missed calls now. lol
*Edit* Thanks to the D3rps I was able to get my phone up and going again. They had posted the stock 3.16 rom here: http://forum.xda-developers.com/showthread.php?t=2127947, with *Removed* recovery I was able to flash that rom. Now I just have to keep an eye out for the Meanbean update that will make it work with 3.16 touch.
**Edit** I removed the reference to the recovery I was using due to problems my noob self was not aware of. Thanks to Bigdaddy619 for his guidance, I now realize why no one is using it on the evo lte.
SOLVED!! Thanks to everyone, especially bigdaddy and FinZ! I will post something about what I did and what I used to get S-Off since it is actually really easy once put into easy to understands terms
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
venkman21 said:
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
Click to expand...
Click to collapse
Flash meanbean or viper rom, both have s-on kernel installer and you should be able to get s-off using dirty racun or moonshine... Sharkie rom is a stock rom too with a s-on installer... Good Luck!
Sent from my EVO using xda app-developers app
venkman21 said:
Hey everyone,
Everything was going really as I was rooting my Evo 4G LTE this afternoon, until I realized I forgot to S-off. TWRP was installed and Superuser was flashed - Anyways, I got antsy and wiped the phone and flashed CM 10.1 and realized I forgot S-off - so of course, the phone wouldn't boot past the HTC screen.
I've been trying to flash stock roms to get into the superuser app, but none of them will load. They start to flash in TWRP, then the phone reboots to the HTC splash screen.
I am now unlocked, but still S-on. I can't flash any roms right now and was hoping someone might be able to help me out. I even tried the process all over again, but I get the same problem. So as of now, I can't get an OS on the phone.
Any ideas? Thanks.
Edit: I was running the latest OTA with HBOOT 2.09.
Click to expand...
Click to collapse
Question... How did you install your recovery? Goo manager, pj75img.zip, or fastboot? I have had this same problem and the only solution was to fastboot flash a recovery... Dunno it was very weird and has only happened on my lte but it's been months.
Flowed from my Jewel using Tapatalk 2
gunfromsako said:
Question... How did you install your recovery? Goo manager, pj75img.zip, or fastboot? I have had this same problem and the only solution was to fastboot flash a recovery... Dunno it was very weird and has only happened on my lte but it's been months.
Flowed from my Jewel using Tapatalk 2
Click to expand...
Click to collapse
I installed it using fastboot. I'm going to try one of the ROMs suggested above and see if that works. I'll let you all know as soon as I do it.
I keep reading that Moonshine won't work with HBOOT 2.09 - and I haven't had any luck getting it to work; it still gives me connection issues saying it can't connect to the phone. It's weird... I can use the adb devices command in recovery mode and my device ID shows up, but when I go into fastboot USB and do adb devices, I can't get it to show up. If I could somehow get that to show up during fastboot, it would mean smooth sailing.
Update: I successfully installed Meanbean. However, I still cannot gain S-Off. Moonshine won't work and I do not know enough to use DirtyRacun since it must be used with Ubuntu. I'll post my Moonshine issues in that thread
Thanks for the help with this! It looks like it just needed a S-On ROM to be installed which I though I was doing before!
I've tried every single HTC driver available and I can't get anything to recognize the Evo when it's in fastboot. It only recognizes the device when the ROM is loaded and USB storage is enabled. Unfortunately, I can't get s-off (as far as I know) without being in the bootloader and using fastboot.
Anyone know how I can achieve this or how I can get everything to communicate with one another like they're supposed to?
Have you deleted all the HTC stuff on your PC rebooted it the plug you phone back in and it should load the drivers again
then boot into bootloader and it should load more drivers
also try updating your android-sdk
Make sure you have the most current HTC driver. At least one person that I know of had issues until he updated to the most recent driver, which can be found in the link below. Use the HTC driver from post #2.
http://forum.xda-developers.com/showthread.php?t=2179776
Also, like Bigdaddy said, make sure you have things like HTC Sync removed. Make sure you're using a USB 2.0 port, too. I don't know where you read Moonshine doesn't work with Hboot 2.09, because it does (specifically for the latest OTA).
Sent you a PM
Sent from my EVO using xda premium
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
BrahManty said:
So I'm currently on Flyhalf's CM10.1 (S-ON), and I checked the recommended firmware/radios for the ROM and realized I'm outdated. It calls for Hboot 2.26 and radio 2.23.10.0123r, 2.23.10.0124r. but I'm on 2.25 and 1.22.10.0421r/1.22.10.0424r. I just updated to the latest version of the rom and I keep getting random bootlooping as well as the rom being way more unstable than the previous build I was on for about 4 months.
So, I'm trying to use Wildhorse's guide to updating firmware through RUU in hopes that it will solve my problems and it just plain isn't working. I've put the RUU in my external SD as PH98IMG, waited for my battery to charge to 90%, shut off the phone, pulled the battery, then gone into Hboot to flash it but I keep getting "No Image or Wrong Image" and it just goes back to the main Hboot screen every single time. Can anyone explain to me why this is happening even though I'm following everybody's directions exactly? I've been searching through the forums for about 2 hours now and I can't get an answer.
I'm still kind of new to HTC devices and how they work, so if anyone could help me figure this out I'd be very thankful.
Click to expand...
Click to collapse
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
acejavelin said:
You are on a leaked firmware, the currently available RUUs are all older than that, and you can't go back when you are S-ON. You need to S-OFF then you can RUU back to 3.14.605.12 and then OTA back up to the current 4.5.605.14
Click to expand...
Click to collapse
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
BrahManty said:
Okay, I was really hoping that wasn't the case. I hate to ask for more help, but I don't really understand how I'm supposed to get S-Off when I need to be on the stock RUU to do it, and I can't get on the stock RUU because I need to be S-Off to do so...
I hope I'm not stuck this way. Technically I'm on all the same software as I was yesterday, but now I'm getting random reboots all the time as well as bootloops that either go on for ten minutes or never end. I was on a build of CM10.1 from may with Amon Ra recovery, then tried to flash the newest TWRP that requires the new firmware (didn't realize I was on older firmware) and it bricked my phone. So I put on an older CWM recovery, tried to backup and it froze in the middle of every backup it tried to make. Put on an old TWRP, backups worked, so I flashed the newest version of CM10.1 (again not knowing I didn't have newest firmware) and that's when the bootlooping/rebooting started. I recovered to the old version of CM10.1 and the issue didn't go away, so now I'm just trying to figure out what I can do to get my phone in a usable state again.
Click to expand...
Click to collapse
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
acejavelin said:
Hey, wait a sec... :laugh:
My bad, I just double checked, and with that Hboot/radio combination you are on stock ICS firmware already! Just RUU version 3.14.605.12, that should work without issues if done correctly and you should be back to pure ICS and can then allow the OTA to upgrade you in a few steps to 4.5.605.14
Click to expand...
Click to collapse
Oh, thank god. Hahah. I didn't remember ever flashing any leaked firmware before, so I was kind of confused there. I figured I may have done it somewhere in the unlocking/rooting process and just couldnt remember. Okay, thanks again for the help. RUU's have always confused me with the way they work. I should be stable in no time hopefully.
And now I'm having more issues... I can't use the Rom Updater because somethings wrong with my usb connection. I can plug it in and transfer files and such, but trying to use any ADB commands results in "Device not found" and the Rom Updater says it can't connect to my device either. My HTC Drivers are up to date, so I'm not sure why this is happening. Is there any way I can just get the PH98IMG.zip for 3.14.605.12 instead of having to use the RUU?
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
acejavelin said:
Not really sure what you are trying to run, I didn't think there was a 3.14.605.12 executable RUU, but use this page and instructions and grab the file: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Remember you will need to RELOCK the bootloader if I am not mistaken it is possible to hard brick if you don't!
Then copy to external SD card, name the file PH98IMG.zip (beware of the Windows "double zip" issue), verify MD5 on the SDcard, then reboot into hboot and go. Do it twice!!! Let it boot up and sit for about 10 minutes to calm down, then remove the PH98IMG.zip file from the SD card. Everything should be smooth sailing from there...
You should then be S-ON, completely stock. You will need to unlock again to do anything more
Click to expand...
Click to collapse
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
BrahManty said:
Strange, re-locking the bootloader was all I needed to get the RUU to update in my bootloader. No one else said to do that in any of the instructions, but I did it and immediately it started updating with the PH98IMG that I was originally trying to flash (from here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331).
I'm back to stock now, but firmware is 4.03.605.2, not 4.03.605.14. Is that going to be an issue or can I go right ahead with re-unlocking the bootloader and flashing recovery/roms?
Click to expand...
Click to collapse
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
acejavelin said:
Well, I have some good news and bad news...
Bad news is you are now on a leaked firmware and will have to S-OFF to go up or down in versions unless a full RUU is released for the current OTA of 4.5.605.14...
Good news is you are the global leak, and you can use the JuopunutBear S-OFF exploit from http://unlimited.io/index.htm just as if you were on the original ICS release. Also, you can S-OFF and use most ROMs and recoveries as you are now on a global mode firmware.
Click to expand...
Click to collapse
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
BrahManty said:
Lol, all right, I would have tried to get the right firmware on there but my phone got so buggy that it wouldn't even boot into the rom anymore. So I couldn't get it on the SD card and I had to make do with what I had on there. At this point, I'm just glad the phone is usable again and I might leave it stock for a while. Thank you so much for all your help, I couldn't have figured this out without you!
Click to expand...
Click to collapse
Cool, glad you got it working.
That firmware is actually pretty decent and rock solid stable, you shouldn't have any more software related issues... Plus you can root/ROM like normal from that version, the radios may be slightler lower than most recommended versions, but they should work fine. If you do decide to go the ROM route again, I would suggest going S-OFF before starting, it will just make it easier in the long run.
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
*** TAMPERED ***
*** LOCKED ***
VIGOR PVT SHIP S-OFF RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Sep 20 2012, 17:40:22
Click to expand...
Click to collapse
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
JoeKamel said:
Hey, just wanted to ask some questions as a follow-up since this seems to be the most relevant (and active) thread to my issue:
Long story short, got a new (to me) Rezound. It was running CM10, from the forthnightly thread. New SIM card from Verizon and I was getting data, but the no mobile network found error. After reading the threads I could find on the error, went with the suggestion of a wipe and so I did. A few too many beers while reading thru the forums, and I did the wipe a bit too thoroughly. Now I have a no OS found, and instead of thinking I know what I'm doing I'd like to ask to make sure I understand this correctly.
Currently, the phone is S-OFF, with TWRP 2.5.0.0. It's saying I'm not rooted, but then again no OS to be rooted. The dump from my bootloader is as follows:
After checking this thread and this one here it looks like the following applies:
* I can just run the regular RUU (executable) to load a stock image without having to revert back to S-ON first.
* I will have to re-unlock the bootloader thru htcdev after RUUing
* I'll need to reinstall TWRP
Is this right? Am I missing anything?
Click to expand...
Click to collapse
You should be able to just boot into twrp and flash a rom
Sent from my ADR6425LVW using xda premium
izzaeroth said:
You should be able to just boot into twrp and flash a rom
Click to expand...
Click to collapse
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
JoeKamel said:
Okay, that's good to know. For now though, if I just wanted to get my phone working, make sure there's not a SIM issue and such I could go back to a stock image without worrying? I just would rather do a lot more reading and make sure I understand what I'm doing before I try to put a rom on and screw things up further.
Click to expand...
Click to collapse
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Sent from my ADR6425LVW using xda premium
izzaeroth said:
No doubt its good to be cautious when you are s-off. If you are just wanting plain jane stock then you could just flash a ruu from boot loader.
Click to expand...
Click to collapse
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
JoeKamel said:
Okay, so if I go with the image here: http://forum.xda-developers.com/showpost.php?p=38527788&postcount=745&nocache=1&z=1965375486761331
Would I still need to relock the bootloader since I'm S-OFF or can I just flash that from TWRP and go from there?
Click to expand...
Click to collapse
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Click to expand...
Click to collapse
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
JoeKamel said:
Recovery as in HBoot or TWRP? Because I still have TWRP. I can get the windows executable RUU for ICS if need be.
Click to expand...
Click to collapse
Recovery = twrp
Sent from my ADR6425LVW using xda premium
izzaeroth said:
Honestly I don't remember if you would have to relock to flash that in boot loader sine you are s-off, but I do know it won't flash from recovery
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
S-off is S-off... installing a RUU wont change that, it may set you back to 'Locked", but you are S-off so it doesn't matter, you can stay locked&s-off and its no different than unlocked/S-off.
If you are going back to stock and are S-off I would use the Global Mode Leak (4.3.605.2) available on AndroidPolice and flash in Hboot... rename file to PH98IMG.zip and place in root of SD card (how it gets there is a irrelevant) then reboot into Hboot, confirm and wait.
Sent from my HTC Aria (Liberty) running CM 7.2 using xda app-developers app
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
simonsgray said:
Oh how i loathe this POS phone
i have this as my work support phone. It wouldn't reliably stay powered up, any time I did turn it on it took 20+ minutes to acquire data/cell/3g signal. turning on maps crashed the phone. so i figured i'd install a new rom
I have lots of experience with sony ericsson, nexus 4, nexus 7 2012, 2013, acer 10.1 tab. i've done all this stuff before, but i cannot get cyanogen 10 or 11 to install properly, and now my phone sits with a spinning logo doing nothing
i:
unlocked the bootloader as per instructions at htc dev
setup ADB on the phone
first jsut copied the c11.zip to the sd card and tried to install that, same issue on with the HTC logo
used hansoon's kit to sideload c10. claims to have installd, now just spins the logo.
any help would be great.
Click to expand...
Click to collapse
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Thanks man. sig is a little out of date, i havent' needed xda as much since jumping to nexus. TWRP and i didn't do the s-off stuff. it says it needs a stock rom and i just havea spinning cyanogen mod. i will try install the 4ext and see if that changes the results.
Odysseus1962 said:
You give a lot of info in your sig, but nothing there or in your post if you're s-off or on and which recovery you're using. Since, you're Canadian you probably need s-off to flash the latest T-Mobile ruu for the radio. And ext4 seems to be the most trouble-free recovery for the amaze. If s-on you can probably still get CM working if you were already on ICS and flash with smart flash enabled in 4ext. If you're still having issues then try pushing the kernel with adb from hboot wth your pc.
I hope this helps.
Click to expand...
Click to collapse
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
simonsgray said:
Tried to install this RUU http://www.androidruu.com/getdownlo...1.41.661.3_release_258801lhwl8053lp8g5hcp.zip
but i get an error status 7 because the file_getprop assert fails.
was trying to install stock so i can do th s-off thing
Click to expand...
Click to collapse
If you want to flash back to the stock ICS image you need to first relock your bootloader. When you relock it will say relocked when in hboot. The procedure is to place the image in the root of your external SD card and select from hboot. It should recognize and flash back to stock, however everything other than your external SD gets wiped in the process. So you need to make sure you have a good recent backup. Also, you remember when you first HTC dev unlocked they sent you an image to push to unlock? Well, I hope you saved it, because you'll need it again to re-unlock the bootloader after flashing the firmware image, but before attaining s-off.
However, if you were already on your carrier's latest ICS firmware before you started flashing different ROMs, you probably already have their latest radio. If you install the latest 4ext and enable smart flash, you'll probably succeed in installing any of the source built ROMs (ASOP, CM, PACman, evervolv) without s-off, because ROMs built from the source don't have the CID flag in their binaries.
If you still decide to go back and attain s-off the procedure is as follows: 1) relock your bootloader 2) flash the latest stock firmware for the carrier that sold your device. 3) Unlock your bootloader again using the image and commands you previously did to HTC dev unlock the first time, 4) get s-off using the wire-trick 5) flash the hacked hboot (and another radio if you desire, but not required for most ROMs) 6) super CID to remove all carrier locked file / partition limitations and protections 7) Flash your preferred recovery. Because you're now s-off you can use TWRP, CWM, or 4ext since the protected partitions are no longer an issue. 8) Flash any ROM you want provided it's based on ICS or later (below won't work because the radio is incompatible).
Edit: One other thing to note before starting any of this make sure your battery is fully charged. Also, the first time you boot after installing CM or any ASOP based ROM it can take quite some time to go through the process before you get to the login screen. For me it usually takes a little under 10 mins. It may at first appear to be a little sluggish until the rom settles, usually about 10-15 mins.
I hope this helps