Softbricked my ATT M8 recovered now new issues - AT&T HTC One (M8)

Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please

Darthdiddy said:
Ok I unlocked my loader, then i think what happend was clockwerk installed its self to the boot partition so i was stuck in a loop. I used One_M8_All-In-One_Kit_v to flash a new recovery lower version at that and now i do have a bootable recovery. Problem is now i didn't backup like a dumb arse my working OS and flashed a bad one or maybe the radio or some crap needed to be done first since it was going from 4.4.2 to 5+. In short all i have is recovery and sideload and every rom i download fails to sideload on the phone side and says sucessful on the pc cmd window. Need help with this please
Click to expand...
Click to collapse
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.

CavyS said:
Wipe data, cache, dalvik, put the appropriate ROM for your carrier/build on SD card or root of internal storage and flash. All else fails run an RUU, bring you back to 100% stock then you can properly reinstall the custom recovery of your choice.
Click to expand...
Click to collapse
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.

Darthdiddy said:
I do the proper wipe before flashing my new rom, i'm under the AT&T HTC One M8 section i believe my phone was only @ 4.4.2 before this and here is the bootloader info is :
***Tampered***
***Unlocked***
M8_UL_CA_ PVT SHIP S-On
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 18 2014,16:06:33.22985
Tried cm-12-20150131-NIGHTLY-m8 it fails to flash and its on the sd and internal. SkyDragon M8 Sense Rom installs but doesn't boot (tried 2 versions of this rom 700mb and a 1.6gb), believe i tried a couple other roms in my phones section there's only like 9 of them there. I have the stock RUU but fails to detect the phone and fails i think it's meant to sense a turned on functional phone i don't see any kind of recovery method with the stock ruu. All i want is a rom to work with Straight talk the stock os even being unlocked and rooted with su still shoved the default APN down my throat(I even paid 2.99$ for the SQLlite and deleted all other APNs still won't let me check off a APN profile i created as default) making my signal on ST flakey and couldn't get mms to work just picture txting wasn't working. So i went full on like my old HTC One X but dived head first too fast didn't backup my old OS and didn't know firewater was gone till i was at that step of the procedure and it was too late Oh and using TWRP 2.7.1.0 it's the highest i can use before it won't boot.
Click to expand...
Click to collapse
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.

CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok TY i'll try that soon as it downloads, i did finally get RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2
To see the phone and no progress bar shows up on the phone and the program errors out, i even did a full system wipe before i tried it again still to no avail.

CavyS said:
Boot into fastboot, check device manager (if youre on windows) for any unknown drivers and install them if you can. Then run the RUU I posted here http://forum.xda-developers.com/att-htc-one-m8/help/100-stock-4-4-4-ruu-t3017594 which would update you to 4.4.4.
Click to expand...
Click to collapse
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help

Darthdiddy said:
Ok tried that stock ruu and it failed i did finally get the phone running on a badseed rom based on 4.4.2 all seems to be working now except i can't send pictures in texts but regular text, calls, and internet work seems to be a common problem with straight talk. So new problem probably a thread somewhere on here about it i'll take a look, thank you for the help
Click to expand...
Click to collapse
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.

CavyS said:
You'll have to setup your APN and mms message size settings for straight talk, that should fix the text messaging problems.
Click to expand...
Click to collapse
No matter what message app i try i can't send pictures or large txts my mms is borked and to make matters worse when i installed this rom i must of removed the stock HTC messaging app so i can't find any settings to set the mms size limits. I'd like to figure out how to put the stock messaging app back on the phone without redoing the whole OS
Using Handcent and hangouts and i see no size limit options within the apps or anywhere in the phone settings. Looked up my phone specifically and where the option/s is supposed to be the said section of options is not even there.

If you've got a stock rom downloaded to your computer or sd card you can unzip it and look in system app folder and find the htc messaging apks. Then just install them as system apps and fix permissions.
Sent from my HTC One_M8 using XDA Free mobile app

Before i try and fix my obvious other problems does anyone know how to fix a bad flash of TWRP? I'm used to just adb command line flashing it and never had a issue before on my HTC One X, but seems it a was bad idea and it landed on boot partition and is causing glitches. is there a stock boot i can flash or what do i need?

Darthdiddy said:
but seems it a was bad idea and it landed on boot partition and is causing glitches.?
Click to expand...
Click to collapse
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.

redpoint73 said:
Why do you think that partition, in particular? If you are talking about boot.img, that gets re-flashed any time your flash a ROM.
Try fastboot erase cache, and flash recovery by fastboot. If Clockwork doesn't work, try TWRP.
If you indeed have some corrupted partition(s), your best bet is to RUU. You are non-specific about what error codes, so its hard to help you troubleshoot why the RUU failed. Try a more updated RUU, such as 2.23.
Click to expand...
Click to collapse
Error 155 Unknown Error it says, do i need to relock the bootloader? I could never find a way to S-Off the device so idk if its that or corrupted partition like you said but all my services on my phone crash constantly. But that's better then aokp_task650_m8_kitkat_5.13.2014 that one won't even make it through setup the services crash so often the badseed rom is the only other rom i found that is actually usable. Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?

Darthdiddy said:
Error 155 Unknown Error it says, do i need to relock the bootloader?
Oh my RUU is 2.0.16 how can i find the newest one for my HTC One M8?
Click to expand...
Click to collapse
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Darthdiddy said:
I could never find a way to S-Off the device
Click to expand...
Click to collapse
Did you try sunshine? Its the only way to s-off at this time.

redpoint73 said:
You always need to relock the bootloader to run RUU with s-on. No exceptions.
Hopefully this will clear up your RUU problem, although the RUU number you just supplied above doesn't make any sense (doesn't correspond to any RUU for this device) Where did you find it, and its not what you referenced in Post #5 above.
CavyS already supplied a link for the "latest" AT&T RUU in Post #4 above. Although be aware, that if you are successful in running the latest RUU, it will render sunshine unable to achieve s-off. I suggest RUU to 1.58 or 2.23 (if you want s-off), as those should still be supported by sunshine.
Did you try sunshine? Its the only way to s-off at this time.
Click to expand...
Click to collapse
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4, idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?

Darthdiddy said:
Relocked and flashed the ruu utility version said 2.0.16.2014 and is KK 4.4
Click to expand...
Click to collapse
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
Darthdiddy said:
idk about sunshine as to reading about people with my phone and it not working so for a 25$ leap of faith not sure what to do about that. My phone is running perfect now in a locked down carrier branded and bloatware way lol. Thanks guys, anyway i can tell if sunshine will work on my phone?
Click to expand...
Click to collapse
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.

redpoint73 said:
I think that is the version of the actual installer software (.exe) not the ROM version it will install on your phone. Kitkat for AT&T would be either 1.58 or 2.23. That number will be in the actual file name of the RUU, so just look there (actually a much longer string of numbers starting with 1.58 or 2.23, but I've abbreviated them for convenience).
You install the sunshine APK, run it, and sunshine will tell you whether it can s-off the phone or not. You won't be charged unless it can successfully s-off the phone. I haven't heard of any folks here that got charged, and sunshine couldn't s-off the device.
Click to expand...
Click to collapse
Wow thanks for the info! Before i try this can after S-OFF/rooting/SU can i install the unlocked/developer ruu from HTC and get HTC OTA and get away from this bloated carrier branded crap? So much in the forums and i can't find a answer to this question anywhere.

Related

[Q] WIFI Does not work after 2.95 update on Htc Evo 3d Sprint CDMA

Hi I just updated my htc evo 4g 3d from Sprint to 2.95 via ota and after that i cannot use wifi at all it just says error. please Help!!!!
b0235g10d said:
Hi I just updated my htc evo 4g 3d from Sprint to 2.95 via ota and after that i cannot use wifi at all it just says error. please Help!!!!
Click to expand...
Click to collapse
You probably took the update and tried to install it with a custom recovery installed. If so, it appears that will result in a partially installed update with the ROM updated and the kernel not being flashed, which causes WiFi errors.
If that's your situation the best thing to do is flash a stock rooted ROM if that is what you were using prior to taking the OTA.
ramjet73
ramjet73 said:
You probably took the update and tried to install it with a custom recovery installed. If so, it appears that will result in a partially installed update with the ROM updated and the kernel not being flashed, which causes WiFi errors.
If that's your situation the best thing to do is flash a stock rooted ROM if that is what you were using prior to taking the OTA.
ramjet73
Click to expand...
Click to collapse
Can you please give me the official ics 2.89 rom or find it please?
b0235g10d said:
Can you please give me the official ics 2.89 rom or find it please?
Click to expand...
Click to collapse
You can find a rooted version in this post.
ramjet73
ramjet73 said:
You can find a rooted version in this post.
ramjet73
Click to expand...
Click to collapse
I found this thread because I'm in a similar situation. I tried downloading from the quoted link and using 4eXT recovery to load the zip file from sd card and it says "installation aborted".
Any ideas on what to try next? My eventual goal is to get back to 100% showroom stock non-rooted, locked booloader, so that the phone will accept OTA updates fully. Modding/ROMing is a drug I experimented with, and am now ready to go back to the straight and narrow. I'd prefer the phone not have any scars whatsoever from my old habits.
Additional background:
Started with ICS OTA. Used HTC unlock to unlock bootloader. Coworker installed rom toolbox, superSU and 4eXT recovery (not sure what order) to get SOS rom up and running. Never did go for S-OFF.
Decided I wanted to return to 100% Sprint factory stock. Coworker promptly moved across country, leaving me to figure this out. Tried using several ROMs from XDA and elsewhere, and eventually ended up with a rooted almost stock ROM, but had to flash my own radios via 4eXT, as wifi and 4G weren't working from the rom. Flashing my own radios via 4eXT, got to 2.89 with then current radios.
While sitting in my hotel travelling abroad with no international data plan and super slow hotel wifi, I foolishly downloaded OTA this morning, promptly killing my phone's wifi. Phone is still rooted with 4eXT, superSU, installed on it if that helps.
ramjet73 said:
You can find a rooted version in this post.
ramjet73
Click to expand...
Click to collapse
I just did this yesterday (Thanks to ramjet for pointing it out). Backup first. It dose a factory reset. You also need to install the blue tooth fix from this post after flashing the ROM http://forum.xda-developers.com/showpost.php?p=29707708&postcount=303
fixed thanks
Hi to all
I just fixed my phone thanks to Mr ramjet and I used the last one because I completely formatted my phone and only had 4ext it takes while to load the first time but be patient and it will work
How about S-Off phones?
Hello... so my fiance' has a Virgin Mobile Evo 3D. I downloaded the update from them and tried to install it through the custom recovery. It did what Ramjet said by updating the ROM and not the Kernel. I now have no wifi,it says wifi error when trying to turn it on. Since then, I have made sure the stock ROM was rooted, and have also HTCDev unlocked the device as well as S-Off with the Junobear wire trick and Linux. Now that I'm S-Off, is it ok to use an RUU to downgrade everything? Just wondering before I go any further and brick the device or screw up something I shouldn't. I figure it's better to ask questions first before doing it lol! Any help is greatly appreciated from anybody! I have my specs listed here for you all:
HTC Evo 3D 4G Virgin Mobile
Mods: Rooted,HTCDev Unlocked, S-Off
JuopunutBear
Shooter XC SHIP S-OFF RL
HBOOT: 1.57.5757
Radio: 1.09.00.0706
Android Version 4.0.3
Sense Version 3.6
Software number 2.95.652.5 710RD
Kernel Version: 3.0.16-g4211684
[email protected] #1
SMP PREEMPT
Baseband Version:1.09.00.0706
Build Number: 2.95.652.5 CL560640 release-keys
EDIT: Problem has been fixed and I will post a new thread on how to fix the problem soon.
PS4AndroidHacker said:
EDIT: Problem has been fixed and I will post a new thread on how to fix the problem soon.
Click to expand...
Click to collapse
Was this new thread ever made because I am a Virgin Mobile user too just like the above user and ever since last update my wireless has stated error.
If ur phone's bootloader is unlocked, relock your phone by using the fastboot command "fastboot oem lock". Then just download the 2.89 RUU.exe. (i know ur on 2.95 but i have not seen the 2.95 ruu floating around hgere yet) Run it on a windows PC and follow the prompts and it should flash correctly on your phone (caution, it will erase everything on your phone). Once its flashed, the phone will reboot (sometimes more than once) just let it do its thing
Once the phone has flashed correctly, do a software update and it will update to 2.95
Worked for me when i had to go back to stock in order to return it for warranty when the digitizer went out
EDIT:
Here is the link to the 2.95 OTA http://d-h.st/vUe
Download to your PC, then unzip it, and run it after you have relocked your phone
Should you need them, here is the list of HBOOTS (thanks to ramjet73) http://forum.xda-developers.com/showthread.php?p=29844945#post29844945
sixty9fordkiller said:
If ur phone's bootloader is unlocked, relock your phone by using the fastboot command "fastboot oem lock". Then just download the 2.89 RUU.exe. (i know ur on 2.95 but i have not seen the 2.95 ruu floating around hgere yet) Run it on a windows PC and follow the prompts and it should flash correctly on your phone (caution, it will erase everything on your phone). Once its flashed, the phone will reboot (sometimes more than once) just let it do its thing
Once the phone has flashed correctly, do a software update and it will update to 2.95
Worked for me when i had to go back to stock in order to return it for warranty when the digitizer went out
EDIT:
Here is the link to the 2.95 OTA http://d-h.st/vUe
Download to your PC, then unzip it, and run it after you have relocked your phone
Should you need them, here is the list of HBOOTS (thanks to ramjet73) http://forum.xda-developers.com/showthread.php?p=29844945#post29844945
Click to expand...
Click to collapse
This sounds hopeful, I did try to install this before with no luck, it gave me a 131 custom id error. I did it relocked and I am currently 2.95.652.5, and S-ON.
any suggestions?
Thanks

[Q] Trying to RUU to update my firmware not working.

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

[Q] How do i convert an at&t One from Developer's Edition back to at&t stock

Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
infg3570 said:
Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
Click to expand...
Click to collapse
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
infg3570 said:
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
Click to expand...
Click to collapse
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
clsA said:
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
Click to expand...
Click to collapse
I tried as you have suggested your decrypted file. Unfortunately, I get an error when trying to run it via ADB in fastboot.
I've rooted when I first got the phone last summer using Revone method/tool. All worked fine and i had continued updating the OS a few times with stock rooted phones.
The last that i updated to was a stock rooted odex kitkat ROM found here http://forum.xda-developers.com/showthread.php?t=2676986
Only thing that seemed wrong was that I couldn't reinstall any of my apps requiring root. The error that would pop up is "Could not install to SD card".
Now, I have to say that I noticed that with some updates, it seems that new ROMS don't clean up the old files/framework even after fully wipes. It seems to back it up in some folders (sdcard0, sdcard00, sdcard000 etc). All though the sdcard folder seems clean and refreshed, the others mentioned had all my old files in there. Since I've updated to kitkat, I can no longer view these folders (I used to use Root Explorer, but now since the kitkat install - I can't). What caused me to notice was the fact that my storage, in the 'Other:' section, shows 20GB out of 32. So, I used ES File Mgr to see if I can create some space by deleting the so-called backup folders. I think that was a bad mistake because now, even after a full data wipe, I still can't:
* Install root-required apps
* flash the zip file you provided
* use the exe version of the zip you provided (still get an error with that as well)
* Clear the 20gb of data I don't need
* get back to the At&t carrier brand from the Developer's Edition that i switched it to back last summer.
Fortunately the phone works fine, but is this hopeless? Anything I can do to get this going again (really thing I messed things up)
Is there anything else I can try?
thank you,
infg3570

urgent help needed: Virgin Mobile HTC desire 601 bricked

I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
I'm assuming you don't have a backup... Try a factory reset from twrp, if that didn't help seek out a zara_cl backup
attrunner said:
I have a HTC desire 601 bought this Summer from Virgin Mobile USA, a CDMA based carrier using Sprint network. My son played with it yesterday and now it is bricked. A "HTC" log is shown up and frozen in the display, not able to shutdown the phone by pressing anything.
I asked my son what he did, but he didnt say anything as he is afraid of punishment
what I can do is try to remove the battery, then hold the volume down key and power key, then it brings up this screen:
***Tampered***
***Unlocked***
ZARA_C PVT SHIP S-ON RL
HBOOT-2.20.0000
RADIO-1.14.50.1003
OpenDSP-v16.2.0268.noBeats.0902
OS-1.10.652.9
eMMC-boot 1024MB
Oct 7 2013 18:39.56.0
HBOOT
<vol_up>to previewitem
<vol_down> to next item
<power> to select item
Fastboot
Recovery
Factory reset
CLEAR storage
SIMLOCK
Image CRC
Show barcode
after I press "recovery", it enter this page::
Team Win Recovery project v2.7.1.1(kk)
Install Wipe
Backup Restore
Mount Settings
Advanced Reboot
what I want to to go back to the stock Virgin Mobile ROM. what should I do? thanks.
Click to expand...
Click to collapse
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive[/URL].
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
attrunner said:
sir, can you show me where did you see it's Kitkat recovery on my device, and where did you see it's still Jelly bean? I am still leaning.
Click to expand...
Click to collapse
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
Team Win Recovery project v2.7.1.1(kk)
^^where it says "kk" at the end means that is a kitkat recovery.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
where it shows it's jelly bean? thank you very much.
attrunner said:
where it shows it's jelly bean? thank you very much.
Click to expand...
Click to collapse
The OS version in your post is Jelly Bean.
-Duir- said:
You're still on the old firmware so you can simply use the RUU which can be downloaded from my Drive.
Re-reading your post I see a problem - You installed the KitKat recovery on your device but your device is still Jelly Bean. As stated in the thread, you want the official version from TWRP's site if you're still on Jelly Bean
Click to expand...
Click to collapse
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
attrunner said:
sir, This is what I did:
1 I tried to use the RUU (file name RUU_ZARA_CL_JB422_SENSE50_Sprint_WWE_VM_1.10.652.9_Radio_1.14.50.1003_NV_SPCS_5.17_003_PRL55009_release_337148_signed_2.exe), but after the RUU erase data, and trying to send data, it has error message:
ERROR[155]: unknown error.
The ROM Update Utility can not update your Android phone.
Please get the correct ROM update utility and try again.
2 I tried different TWRP version as recovery, then use your RUU, all failed as step 1.
openrecovery-twrp-2.6.3.0-zaracl
openrecovery-twrp-2.7.0.0-zaracl
openrecovery-twrp-2.7.1.0-zaracl
3. I tried a stock ROM in Google dirve:
/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
I chose file JB_stock_system_dump.zip, tried to copy to external SD card and install from recovery, but failed.
So please help what should I try next. thank you very much
Click to expand...
Click to collapse
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
-Duir- said:
Lock the bootloader and then run it.
Also:
Custom recovery does not affect the RUU.
The system dump zip is literally that, a dump of the system partition. As such, it's not recovery flashable.
Click to expand...
Click to collapse
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
mrplowdan said:
Don't lock the boot loader, that's not why the ruu is failing.
You need to change the mid first
Click to expand...
Click to collapse
That's exactly why it's failing. You need to be relocked to run the RUU.
-Duir- said:
That's exactly why it's failing. You need to be relocked to run the RUU.
Click to expand...
Click to collapse
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
mrplowdan said:
Perhaps its different for the cl varient but for my ul, I'm 100% positive you don't need to be relocked. However, mid and cid must match the ruu.
*edit*
Also your hboot must be older or the same version as the ruu's hboot
Click to expand...
Click to collapse
Well, they have the Virgin Mobile zara_cl variant which the RUU is made for, so the mid and cid shouldn't be an issue since they're S-ON and can't change it. Also, as stated their using 4.2.2. They still have the old firmware and partition layout which is why the version of twrp they installed won't work so hboot version is also not an issue. Also, it throws a different error if your device has a newer hboot than the RUU.
While it's not entirely outside the realm of possibility that something else could be causing the error, it's definitely not hboot version or mid/cid.
Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
-Duir- said:
... Were you S-OFF when you ran RUU on unlocked bootloader? I'm not sure of all the benefits of being S-OFF, but maybe one is being able to RUU with an unlocked bootloader. It makes perfect sense for an unlocked bootloader to throw an error since it can void your warranty and RUUs are generally ran by service techs.
But in all my experience the bootloader needs to be locked/relocked for the RUU to run.
Click to expand...
Click to collapse
I haven't tried running the ruu while s-on. I'm pretty sure the distinction is if your s-off you can flash ruu zips (which don't have the mid/cid requirements) after running fastboot oem rebootRUU as well as the standard exe RUUs, and if your s-on you can only run exe RUUs.
Hey, guys. I've finally made an account here after clumsily stepping into the world of custom ROMs. I recently got a Zara_CL on Virgin mobile and somehow wound up in the same position as the OP here. I never updated to KitKat due to the update failing with a custom recovery image. After unlocking the bootloader, I installed TWRP 2.7.1.1 and tried to flash InstertCoin yesterday without making a backup (couldn't mount certain partitions and now I know why ^_^). It took many hours to figure out what I did wrong and to make many plans of action to fix those mistakes.
I have re-locked my bootloader and the RUU has allowed me to get the stock Jellybean ROM back on my phone. I tried before while still unlocked and the RUU made no progress at all.
From what I've experienced, S-OFF and Unlocked are sort of interchangeable on a device in this stage of being cracked. One can flash recoveries with S-OFF and a locked loader, or with S-ON and an unlocked loader. I'm still learning after a few months and a successful root, s-off, and rom flash on an ancient EVO 3D. The high of that success drove me to buy this phone and try some magic on it, but my conjuration skills are quite unpolished.
To OP: Relock your bootloader with fastboot command "oem lock" and then run the RUU you found here. This should resurrect your handset flawlessly as it did in my situation. Don't punish your son, but teach him to be more careful. We both learned the hard way, but I guess I learned more quickly.
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Hedied4me said:
I had to always lock bootloader before running ruu. Would always get same error otherwise. This was for s-on. I can't remember my one experience running ruu while s-off.
Sent from my cdma Virgin Mobile HTC Desire 601 zara_cl
Click to expand...
Click to collapse
How to lock bootloader? I only know how to unlock.
Get into boot loader and type "oem lock" into adb/command prompt.
attrunner said:
How to lock bootloader? I only know how to unlock.
Click to expand...
Click to collapse
You're phone needs to be in fastboot mode.
You need adb on your computer and to run a command prompt from your adb folder. Plug your phone into the computer and from the command prompt type "fastboot oem lock" and press enter. You're bootloader will now be locked. If you get a message about too many flags or something and a security warning afterwards, don't worry, it worked.

how do i unroot??

i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Jduncan312 said:
i bought the m8 on att froma guy on craigslist i cant figure out how to unroot it ive tried installing skydragon a maximus but i cant get pass the htc boot screen ive tried updating the twrp to the newest and no i dont have a recovery ive even tried downgrading to an older one any help?? edit!! i cant get pass the boot screen i had cwm and tried installing stock att firmware please help
Click to expand...
Click to collapse
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
redpoint73 said:
What does your heart really want? Do you want to run custom ROMs and have root or not? It mostly sounds like you may want to return to stock due to lack of understanding and knowledge. That's okay if you want to do that. But kinda against the spirit of XDA!
Relock the bootloader and RUU will return the phone to stock and unrooted.
But it just sounds like you have mismatched firmware (results in long boot times with no boot animation, which some folks mistake for it not being booted).
Also, the newest TWRP require updated hboot, so that is probably the problem there.
If you want the phone rooted, and running a custom ROM: either run a ROM that corresponds with your firmware, or s-off and update your firmware.
What hboot and radio numbers? S-on or S-off?
Click to expand...
Click to collapse
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Jduncan312 said:
my hboot is 3.16.0 not sure about the s on and off thing but yeah iw ould love to run roms on it I tried downloading the skydragon 5.0.1 on it but it was stuck at the boot screen im using clockwork mod but I cant get twrp back on because I cant boot into the phone and ive tried everything to install the drivers and ive tried to manually install them also but no luck if you can email me or something to help me out it would be great!! [email protected]
Click to expand...
Click to collapse
Holy run-on sentence! Seriously, please take the time to type a proper response with punctuation. Making it easier to read, makes it easier for me to help you. And that is what you want, isn't it???
I don't use my personal email for this type of support. That is what these forums are for.
Skydragon is probably not "stuck" but rather taking an extremely long time to boot (10+ minutes) with no boot animation, which often leads folks to believe its stuck altogether. If you leave it alone, it will probably boot eventually, but you may also find that WiFi is broken. Both are symptoms of the wrong firmware for the ROM you flashed.
Your hboot number also indicates that you don't have the right firmware installed, as firmware includes hboot as well as radio, WiFi, Bluetooth, and other modules.
On the AT&T variant, you will not have any "official" way to update the firmware to anything more up-to-date than 2.x firmware (hboot 3.17). You need 4.x firmware (hboot 3.19) to run the ROM you mentioned. Therefore you need s-off by sunshine (if not s-off already).
You can check s-on or s-off by booting into bootloader, and you will see it says one of the other near the top of the screen.
Alternately, if you don't s-off, you can flash a ROM that corresponds to your firmware. Try the following ROM, but putting the ROM zip on a removable SD card using a card reader connected to your computer (if you have those available). Then boot into recovery,navigate to the file and flash: http://forum.xda-developers.com/showthread.php?t=2705640
Aside from that, you should really get your USB connectivity issue sorted out. You can't do much without it. Verify no response when you type fastboot devices when the phone is in fastboot mode. If it doesn't respond (should return device ID) then try a different USB cable, and different USB port. If on Windows, try going to Device Manager, finding the phone, and pick the option to manually select the drivers, than pick the USB MTP drivers (not the HTC ones). This will often fix adb/fastboot connectivity issues.

Categories

Resources