Hey All -
I made a post a couple of days ago about the best way to wipe my phone and all folders / files except what's needed to run it. I'm not selling it, just want to start all over from scratch again 100%.
My post was answered by a suggestion to install HTC's "HTC One Maintenance Release" / RUU. I was told doing this would bring it back to factory and I'd even have to re-root.
Today, I made a full backup of everything and ran it. Unfortunately, it failed with error 155. I tried all troubleshooting steps without luck, but am confident the reason it failed was due to the RUU being older than my ROM as you can see in the attached picture.
If this is the best method to wipe my device, any suggestions on how to get it working? If you have another method to suggest, I'm all ears. Below are the specs I'm running right now:
Phone Specs
- HTC One (AT&T)
- Rooted
- S-OFF
- ViperOne 4.3.0 / Android 4.4 / HTC Sense 5.5 / HTC Sense SDK 5.65
- Build Number 4.06.1540.3
- TWRP
- Kernel 3.4.10
After wipe, I plan to re-root (if needed), then install Viper 5.0.0 ROM.
Thanks!
Did you lock the bootloader ?
Your s-off you can flash any RUU you choose
sent from my recliner
You need to revert to Hboot 1.44
Most guides don't include this, idk why as I've never gotten it to work without reverting to Hboot 1.44
It will give the same error 155 unless you flash Hboot 1.44
Download here https://mega.co.nz/#!2U5DQAAY!Fbi7I3lqyKaIsoUkRV_xPQQHMKUiGE8gl9l-sAKd0Gk
I have hboot 155 and got it to work. I had to flash stock recovery first though.
Sent from my HTC One using Tapatalk
That may have been my problem then, I had custom recovery. Weird though downgrading hboot worked
Sent from my HTC One using xda app-developers app
bzowk said:
Hey All -
I made a post a couple of days ago about the best way to wipe my phone and all folders / files except what's needed to run it. I'm not selling it, just want to start all over from scratch again 100%.
My post was answered by a suggestion to install HTC's "HTC One Maintenance Release" / RUU. I was told doing this would bring it back to factory and I'd even have to re-root.
Today, I made a full backup of everything and ran it. Unfortunately, it failed with error 155. I tried all troubleshooting steps without luck, but am confident the reason it failed was due to the RUU being older than my ROM as you can see in the attached picture.
If this is the best method to wipe my device, any suggestions on how to get it working? If you have another method to suggest, I'm all ears. Below are the specs I'm running right now:
Phone Specs
- HTC One (AT&T)
- Rooted
- S-OFF
- ViperOne 4.3.0 / Android 4.4 / HTC Sense 5.5 / HTC Sense SDK 5.65
- Build Number 4.06.1540.3
- TWRP
- Kernel 3.4.10
After wipe, I plan to re-root (if needed), then install Viper 5.0.0 ROM.
Thanks!
Click to expand...
Click to collapse
I had the exact same problem on my AT&T HTC One (sim-unlocked). My device came with Android 4.3. I tried OTA update, but as I am currently outside USA and on different carrier, I didn't get any OTA update. I tried to flash the Android 4.4 RUU exe, but every time it returned the error you stated, although my device was 100% stock. However, I have found a solution, you can try that.
Related
I thought I saw this in one of the forums, but now I cant find it (yes, I used the search).
A few weeks ago, I did the firmware update (OTA_JEWEL_CL_ICS_40_S_SPRINT_WWE_2.13.651.1-1.22.651.3_release_277), downloaded, then restarted the phone, but the phone went into the TWRP recovery....nothing happened. So I tried to install through TWRP, but it "FAILS" every time. Can anyone let me know how the heck I can install the firmware update? And if I install the update, will that remove my "unlocking" (<~ word?)? Thanks for the help guys and gals.
A couple of notes:
I am not fully rooted, I just unlocked with HTC - so S-on
Hboot 1.15
Radio - 1.05.11.0606
TWRP-2.2.1
hardware - 0003
software 1.22.651.3.71ORD
android version - 4.0.3
HTC Sense - 4.0
bretweb24 said:
I thought I saw this in one of the forums, but now I cant find it (yes, I used the search).
A few weeks ago, I did the firmware update (OTA_JEWEL_CL_ICS_40_S_SPRINT_WWE_2.13.651.1-1.22.651.3_release_277), downloaded, then restarted the phone, but the phone went into the TWRP recovery....nothing happened. So I tried to install through TWRP, but it "FAILS" every time. Can anyone let me know how the heck I can install the firmware update? And if I install the update, will that remove my "unlocking" (<~ word?)? Thanks for the help guys and gals.
A couple of notes:
I am not fully rooted, I just unlocked with HTC - so S-on
Hboot 1.15
Radio - 1.05.11.0606
TWRP-2.2.1
hardware - 0003
software 1.22.651.3.71ORD
android version - 4.0.3
HTC Sense - 4.0
Click to expand...
Click to collapse
You can't install firmware with that hboot..you either need to relock and use the most recent ruu, or downgrade your hboot to 1.12 and lazy panda for s-off
Sent from my EVO using xda premium
Thank you for the response. Is the problem the s- on? And if so, can I wait for s-off for hboot 1.5 and then apply the update?
I know this had probably been answered in the past, so I do appreciate taking the time to catch me up.
Sent from my EVO using xda app-developers app
Just run the 1.22 stock recovery, that will wipe twrp. Your update should go right thru. Yes you would need to HTC unlock again. If you can't find 1.22 stock recovery let me know and I can pm you the PJ75IMG when I get home
That would be great if you could PM me that file. Also, could you let me know again what it would affect. Do I just unlock through HTC to get access to the root drive?
Does it also zap all my programs and settings? And if so, would I than install TWRP and flash my latest backup?
Sorry for all the questions, I have been away from the "scene" for too long.
Sent from my EVO using xda app-developers app
If you're not in a hurry, you could just reflash a rooted ROM for now and wait for dirty racun to get s-off (no eta atm) and then flash the latest firmware package.
http://forum.xda-developers.com/showthread.php?t=1964309
Otherwise you will need to relock, run the RUU, htc dev unlock again, flash TWRP, etc.
Sent from my EVO LTE
Also update your twrp to v2.3.1.0
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
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
brownsfan said:
Hi guys.
I was trying to do one of two things. Either get to stock ICS with the RUU or get to an older stock version so that my phone would update itself.
I ran the ICS RUU and ran into an issue. Im on Hboot 2.28 Radio 2.23.10.0123r/2.23.10.0124r
I am S-On and relocked to get run the RUU.
I got an error as it said the Hboot version is older. Now I am stuck on the Bootloader with TAMPERED, RELOCKED, and Security Warning.
I should have known that I potentially had a leaked Hboot version but it was so long ago I forgot.
What can I do? Iv been googling and searching threads without much luck. Do I have to S-off? Can I S-off from this position? The other issue I keep running into is dead file links.
Click to expand...
Click to collapse
So I think I found out what I did. 2.28 is the Global version. I must of rooted that version and flashed roms. I wanted to unroot and get back to stock software version.
Where should I go from here? Is there an RUU for the ICS Global? I can not seem to find one.
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Thingula said:
Have you tried unlocking the bootloader again?
Edit: I searched for a long time (a few days ago) but couldn't find any information on S-Off, not going back to stock for people on the latest OTA. I'm not the best person to give advice, but if you're on the current OTA, I don't think you can use the RUU.exe.
Also, you can't downgrade if you're S-On - only upgrade..
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Yes I can unlock again and that does get me unstock from the boot screen but still cant get where I want. Hmm.
I wonder if you can fastboot-flash the older kernels, using a computer, then flash the old stock ROM, lock the bootloader, then run an RUU.. Can anyone confirm this? Sounds too simple to work on an HTC phone.
Edit: No, of course that doesn't work. Sorry, I can't really offer any more help.. I'll have to just hope that someone more knowledgeable can take over.
Sent from my ADR6425LVW using xda app-developers app
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Very much so! Thank you. If I could hit the thanks button 10x I would.
Im sure im not the only only to have the Hboot 2.28 issue.
hey man you still around ? i need some help with a situation like this
dust906 said:
hey man you still around ? i need some help with a situation like this
Click to expand...
Click to collapse
I replied to you in your thread.
S-On Locked stock !
mikeyk101 said:
Be prepared, I get rather long winded.
If you were on the most current 4.05.605.14 with S-on which based on what you list as the radios and hboot is what it appears you were on, then you are in a difficult spot. The really bad news is the only RUU you would be able to use is the 4.05.605.14 and no one has admitted to being able to get ahold of. The most current one available is 3.14.605.12 but that is useless to you. You would have to S-off to go back to stock but would have to have a working rom to do it. It's not impossible but it aint easy. I just had to do it about a month ago when I was trying to S-off my replacement Rezound. It came with the most current stock ROM and I didn't bother reading up on the current ControlBear method. In the past, you had to have a rooted rom in order to S-off. So of course, I unlocked the bootloader, flashed AmonRa 3.15 and then used superuser to root it and then went about trying to S-off. I couldn't find my previous windows based versions of ControlBear so I went about making a live cd ubunto disk and trying to S-off. It wouldn't work. Then I read the unlimited.io site instructions and found that the current version needs the unrooted stock rom to succeed. I really never paid attention to unrooting before because if I had to do it, I could always just run the factory wipe and root would be gone but not this time. It kept showing that I was rooted. So I tried wiping data, cache, dalvik cache, and after that didn't work, I wiped the system. Very bad move on my part. Now I couldn't get past the bootloader. I thought I was done for because I knew with S-on, there was no going back and the global rom RUU was still not available.
After trying all kinds of things I ended up
1. downloading the 4.05.605.14 stock rooted rom listed HERE (Thanks MicroMod777) in the Rezound Development section.
2. Then downloaded the current firmware.zip from HERE (Thanks Flyhalf205) and then extracted the recovery.img along with the hboot .nb0 file from it.
3. I then created 2 separate custom ph98img.zip for each so I could always reinstall the stock hboot and the stock recovery.img.
4. I extracted the boot.img from the rooted rom and flashed that first. I don't remember if I did it via adb in fastboot usb or with another ph98img.zip and then
5. I made sure that my bootloader was unlocked and then installed AmonRa as the recovery
6. Then used AmonRa to flash the stock rooted zip file. I then wiped the cache 3 times and the dalkvik cache 3 times.
I let the phone reboot and I was back to a working phone.!!! Then I found out that it was rooted with SuperSu which gives you the option of doing a full permanent unroot which I did. I then put that ph98img that I had made that had the stock recovery.img on it and flashed that in the bootloader. After rebooting I now had a fully stock phone and proceeded to do the S-off. I left the bootloader unlocked as directed by the unlimited.io site. I had limited experience with ubunto but found THIS PAGE that helped walk me through it. I followed it exactly and ended up with an S-off phone. One thing that wasn't clear to me was how to open a terminal in ubunto but I figured that out after trial and error. IIRC, I clicked on the home tab on the left and then in the search box, typed terminal. The first icon that was shown was a terminal emulator and I used that for the commands.
Now I still wasn't finished. I ended up relocking the bootloader but didn't like the relocked and tampered flags that were showing. So I ended up running the most recent RUU (3.14.605.12 found HERE and I now had a ***LOCKED*** bootloader and then let the phone reboot. After it rebooted, I hit the home key and bypassed the setup. I then got into settings and then into software update and let it update. It did a small update and then had to repeat the reboot, bypass setup, and software update. This time it did the global update. I let it reboot but this time, I ran the setup. Once I was up and running, I again went into bootloader and reinstalled AmonRa and used the 3.16 version and made sure to do a nandroid before doing anything further. After that, I got ahold of SuperSu 1.51 and flashed that in the AmonRa recovery. I now had a ***LOCKED*** stock rooted Rezound and several nandroid backups of both fully stock and rooted. Which turned out to be a great idea because not even 3 weeks later after this, the phone started malfunctioning (power button) and a problem with the camera so it got replaced and I had to put it back fully stock. I was already setup for this. I unrooted, put the stock recovery back on, and made it S-on. When the replacement came, I immediately unlocked it, did the S-off (only took one try), relocked, ruu'd back to 3.14.605.12, updated to global rom, flashed AmonRa, and restored with my most recent rooted nandroid. and I am back up and running a whole lot sooner...
I hope this helps.
Click to expand...
Click to collapse
This guide was FREAKING AWESOME. It led me to finally after 2 years go S-Off (wire trick) to do RUU, etc. Have to return phone and have already got replacement. Crossed my fingers and everything looks stock stock stock !
Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
HitShane said:
Hi,
Can someone help me please. I am looking for a rom for my AT&T US, HTC One M8. I'm running 4.4.2, Hboot 3.16, Radio 1.16..., and 1.58.502.1 firmware.I have the 3.4 kernel. I am unlocked, TWRP latest custom recovery, and rooted with SuperSU. I am S-On. I can't S-Off and can't update my Firmware. I need it to work in the US, so what rom can I flash that will work. When I go to Dev sites every rom I see only has the 4.4.3/4.4.4 versions with the new Firmware, for my device. When I try to flash .zip's through TWRP, Aroma gives me a success, but it auto reboots and I get stuck in boot loop... I am able to recover the stock image, but can't get a custom rom to stick. I have watched hours of videos and read hundreds of pages of threads. HELP
Thank You,
-Shane
Click to expand...
Click to collapse
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
redpoint73 said:
If you've tried the flash various ROMs, and they all won't boot, then the problem is not what ROM, but something else.
adb erase cache
Then, flash recovery again. Possibly re-download recovery, to make sure the file is not corrupt.
Click to expand...
Click to collapse
^^ I did that when I rooted the phone. I used the HTCDev to unlock it. I used Fastboot and adb in cmd from my PC to install TWRP and the Recovery file and clear the cache. Should I reflash recovery again???
I have wiped and tried factory resets before installing a rom. The problem is that I can't find the download link for an old rom for my specific phone. I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF... When I find a rom that did make one that would work on my device, they have already updated the OP download link with their latest version to run with the updated AT&T 4.4.3/4.4.4 and 2.22.1540.3.
* I have the newest TWRP installed with the 24MB Recovery.img. I have SU installed with privileges. The phone passes rooted tests. Phone is S-ON... *
iRunLinux said:
There are 4.4.2 roms still available but your best bet is pay the $25 for sunshine s-off utility that way you can update your firmware and run whatever rom/kernel you want.
Click to expand...
Click to collapse
^^I have seen even sunshine fail with the latest devices from AT&T.
?----->Does anyone have a good link to a rom that will run on my; AT&T HTC One M8 running 4.4.2 & 1.58.502.1, (1.16.21331931.LA11G)? It was bought a month ago from an AT&T store...
Thank You,
-Shane
HitShane said:
Should I reflash recovery again???
Click to expand...
Click to collapse
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
HitShane said:
I need the 1.58.502.1 version (Don't I ?), so that I don't have to change my Firmware through S-OFF...
Click to expand...
Click to collapse
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
HitShane said:
^^I have seen even sunshine fail with the latest devices from AT&T.
Click to expand...
Click to collapse
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
918
redpoint73 said:
I just told you to adb wipe cache and flash recovery again. Why are you asking me this? A lot of issues with TWRP not flashing ROMs can be solved by wiping cache and flashing again (probably just a bad initial install).
Any ROM that is not 2.xx Sense based.
I haven't checked every single thread/link, but most (if not all) 1.54 and 1.58 based Sense ROMs on my Index thread seem to be working:
http://forum.xda-developers.com/showthread.php?t=2751432
This also includes the stock rooted 1.58 ROM, if you wish to go that route.
You sure? I haven't seen sunshine fail for anybody, much less AT&T, which hasn't had their software updated for sometime now. Regardless of how new the device is, its still the same 1.58 software, which is 3 months old at this point.
firewater, on the other hand is known to fail for more recent AT&T versions.
Click to expand...
Click to collapse
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
-Shane
HitShane said:
So for instance on your Index, I followed the link to ViperOneM8 1.6.0. This takes you to the Dev page for that rom. I follow the page to downloads that directs me another page. Along the way I find out that it looks like ViperOneM8 1.8 is the last update before 2.xx. The download page only has the most recent ViperOneM8_2.2.0.zip, or they offer the OTA increments of each previous version. Those aren't large enough to be the whole rom. How do I find the legacy full roms?
Click to expand...
Click to collapse
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
redpoint73 said:
I think you picked one of the few (maybe the only one) that doesn't link to an actual 1.xx ROM. Just pick any other one.
EDIT: Oh, wait InsertCoin also. Will update the Index to show those as 2.22 ROMs.
Devs usually don't keep their legacy versions posted. Most you can do is ask if another member has the zip.
Click to expand...
Click to collapse
Thank you for all of the information. I guess the roms develop faster than I can get a phone for them It baffles me that a version for each baseline of a current device isn't listed. I guess I should flash back to the most current stock rom and wait for the OTA from AT&T. I might try the S-Off for $25, but I have seen a lot of chatter about newly bought M8 ATT devices not working. Something about them having a patch from HTC...
-Shane
So the developer sense RUU released and i'm currently on GPE RUU i'm wondering do I just change my cid and mid and just run the RUU or do I need to do other steps?
http://www.htc.com/us/support/htc-one-m8/news/
Link to download Sense 5.0.1
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Conflicting report on converting back to Sense ROM GPE, whether you can just change CID/MID and flash the RUU; or other say you need to run the firmware zip first, then RUU.
Andrew149 said:
So the developer sense RUU released and i'm currently on GPE RUU i'm wondering do I just change my cid and mid and just run the RUU or do I need to do other steps?
http://www.htc.com/us/support/htc-one-m8/news/
Link to download Sense 5.0.1
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
I just converted my AT&T M8 back to developer edition from GPe RUU. I am aware of the conflicting info on converting back from GPe. So I tried to run the sense RUU but it said wrong file or something, even though I changed my cid to Dev edition cid already. Then I installed the developers edition firmware and ran the developers edition RUU and it ran fine. Hope this helps.
pavankvn said:
I just converted my AT&T M8 back to developer edition from GPe RUU. I am aware of the conflicting info on converting back from GPe. So I tried to run the sense RUU but it said wrong file or something, even though I changed my cid to Dev edition cid already. Then I installed the developers edition firmware and ran the developers edition RUU and it ran fine. Hope this helps.
Click to expand...
Click to collapse
how did you convert it to dev edition?
Good day friends, I am currently in lollipop 5.0.1 , just shrunk to GPE and I want to install Android Revolution HD 34.0, sense again , I cid GOOGL001 , I could indicate how do I reinstall ARHD , thank you very much .
Advice for restoring AT&T Sense with GPE hboot
Through ignorance, I've gotten myself into a bind and would appreciate some help.
I have an M8, CWS__001 configured with:
- Unlocked Bootloader
- HBoot 3.19.0.0000
- Partitioned for GPE
- S-on
- Most of Sense installed (ran out of room)
- TWRP 2.8.4
- Full ADB and Fastboot access as well as full TWRP functionality
My dilemma is that I can't install GPE because it fails the signature check, can't install Sense because there is not enough room on the partition, and haven't been able find an RUU.zip to install with an Hboot newer than 3.19.0.0000 to restore to stock.
I think my potential solutions are:
-1- a method to set S-off without a functional OS installed, then install GPE
-2- an up-to-date, signed RUU to flash the entire thing back to stock
-3- a sense appropriate firmware (502) that has a more up-to-date HBoot than I have now (1.58.502.1.zip from Android Revolution HD's Firmware collection)
-4- re-partition manually to make space for sense
At this point I have spent several days on the problem, learned a lot about what all the different numbers in the firmware/ROM filenames represent and, in my opinion, have done due diligence researching my options. I could really use some help either with one of my potential solutions or others I haven't considered. As always, links would be appreciated.
GW
Yeah! Just the act of writing my post put me on track to find the solution. I found another guy who did exactly the same thing (Other guy with same problem). His solution was to install Skydragon GPE through TWRP and it seems to be working! I just called my own house!!!! I'm going to try this ROM out for awhile and see how I like it before I try to screw it up again; three days without a phone sucked.
Green Wenonah said:
Yeah! Just the act of writing my post put me on track to find the solution. I found another guy who did exactly the same thing (Other guy with same problem). His solution was to install Skydragon GPE through TWRP and it seems to be working! I just called my own house!!!! I'm going to try this ROM out for awhile and see how I like it before I try to screw it up again; three days without a phone sucked.
Click to expand...
Click to collapse
Skydragon works because it's small enough to fit into the smaller partitions. If you want to set your phone back to stock you need to lock your bootloader and flash the signed encrypted firmware that matches what your phone last had. Then do a factory reset from either hboot or stock recovery. This will resize your partitions back to the 2.6gig needed for system. After doing this you can either unlock and flash TWRP and a stock sense rom -or- flash the current RUU that matches your system.
I help guys out on the VZW side of the house revert back from GPE partition sizing all the time so if anyone needs a hand I can usually help using team viewer.