Related
Hi, I've been running into a problem the last few days. Any help will be really appreciated.
My phone was unrooted and updated to sense 5 via OTA and it also updated my HBOOT from (if I'm not mistaken) 1.35 to 1.72. Now I've been trying a few roms like slim bean and CM but I want to go back to stock. The problem is that the RUU file that I've been using now doesn't work to go back stock as it shows an error while restoring. Can someone please guide me with this?
Many thanks!
For custom Rom you Need unlock - for ruu you Need to relock your bootloader - try this.
Sent from my HTC One X+ using xda premium
morbvamp said:
Hi, I've been running into a problem the last few days. Any help will be really appreciated.
My phone was unrooted and updated to sense 5 via OTA and it also updated my HBOOT from (if I'm not mistaken) 1.35 to 1.72. Now I've been trying a few roms like slim bean and CM but I want to go back to stock. The problem is that the RUU file that I've been using now doesn't work to go back stock as it shows an error while restoring. Can someone please guide me with this?
Many thanks!
Click to expand...
Click to collapse
Because we have no possiblity to S-OFF our phones, you are not allowed to downgrade your HBOOT, so in order to go back to stock now, you would need latest RUU of the Sense5/Android4.2.2 update, which is not available (in fact there wasn't even a RUU for latest Sense 4+/Android 4.1.1 ...).
If you really want back to stock, you need to search the forum or internet for a stock TWRP or CWM backup matching your CID, then flash belonging boot.img in fastboot, restore this stock backup and as a last step reflash stock recovery in fastboot.
Easier (at least that's what i think) would be to install a stock like custom rom from One X+ Android Development forum. You won't get the OTA updates this way, but if there will be any more updates for our phones (which i doubt) the devs will most likely rebase their roms on these updates.
reaper90 said:
Because we have no possiblity to S-OFF our phones, you are not allowed to downgrade your HBOOT, so in order to go back to stock now, you would need latest RUU of the Sense5/Android4.2.2 update, which is not available (in fact there wasn't even a RUU for latest Sense 4+/Android 4.1.1 ...).
If you really want back to stock, you need to search the forum or internet for a stock TWRP or CWM backup matching your CID, then flash belonging boot.img in fastboot, restore this stock backup and as a last step reflash stock recovery in fastboot.
Easier (at least that's what i think) would be to install a stock like custom rom from One X+ Android Development forum. You won't get the OTA updates this way, but if there will be any more updates for our phones (which i doubt) the devs will most likely rebase their roms on these updates.
Click to expand...
Click to collapse
On a similar theme, I also have hboot 1.72 after OTA 4.2.2 / sense 5 update. (O2)
Currently unlocked, rooted and using ARHD8.
Over the last few weeks I've been reading on this forum about the possibility of returning to COMPLETELY stock in case of further updates which, like you, I doubt will happen.
Am I right in saying that if I.... relock bootloader, flash backed up original OS (backed up with TWRP), flash stock boot.img, I will be back to stock ?
Where, and how, does the 'stock recovery' come in to returning phone to stock ?
Thanks
10rdan said:
On a similar theme, I also have hboot 1.72 after OTA 4.2.2 / sense 5 update. (O2)
Currently unlocked, rooted and using ARHD8.
Over the last few weeks I've been reading on this forum about the possibility of returning to COMPLETELY stock in case of further updates which, like you, I doubt will happen.
Am I right in saying that if I.... relock bootloader, flash backed up original OS (backed up with TWRP), flash stock boot.img, I will be back to stock ?
Where, and how, does the 'stock recovery' come in to returning phone to stock ?
Thanks
Click to expand...
Click to collapse
Assuming you have everything you need, meaning stock backup (already placed on your phone) including boot.img/kernel & stock recovery from latest update, best order would be:
1. flash stock boot.img in fastboot
2. restore stock backup
3. flash stock recovery
3. relock bootloader
Now your phone should be completely back to stock except your bootloader saying "relocked" instead of "locked". You should be able to get future OTA updates from HTC (assuming we will get another update) again, the stock recovery is necessary to install these updates and if i remember right, the bootloader only has to be relocked in order to update HBOOT version. But what's the matter in keeping bootloader unlocked when having completely stock rom installed?
For me the only reason to go back to stock is installing latest OTA if there's a new HBOOT version included.
reaper90 said:
Assuming you have everything you need, meaning stock backup (already placed on your phone) including boot.img/kernel & stock recovery from latest update, best order would be:
1. flash stock boot.img in fastboot
2. restore stock backup
3. flash stock recovery
3. relock bootloader
Now your phone should be completely back to stock except your bootloader saying "relocked" instead of "locked". You should be able to get future OTA updates from HTC (assuming we will get another update) again, the stock recovery is necessary to install these updates and if i remember right, the bootloader only has to be relocked in order to update HBOOT version. But what's the matter in keeping bootloader unlocked when having completely stock rom installed?
For me the only reason to go back to stock is installing latest OTA if there's a new HBOOT version included.
Click to expand...
Click to collapse
I've got 'stock backup and boot.img' saved on laptop and USB stick. Where will I find 'stock recovey, is it within the backup I created or do I need to find it on this forum ?
I'm happy with ARHD8 etc but, me being me, I'm always curious about what can and can't be done. ie, return to 'stock'.
Cheers
10rdan said:
I've got 'stock backup and boot.img' saved on laptop and USB stick. Where will I find 'stock recovey, is it within the backup I created or do I need to find it on this forum ?
I'm happy with ARHD8 etc but, me being me, I'm always curious about what can and can't be done. ie, return to 'stock'.
Cheers
Click to expand...
Click to collapse
You can find it inside of this firmware package for O2 i extracted from latest OTA. But don't use the boot.img in there, if you do so, your mobile connections may not work after restore.
https://www.dropbox.com/s/ithmy88yf4dwnnw/firmware.zip
I've just been having a look at the various settings within TWRP and noticed that one of the options available when backing up is 'recovery'. By default there is no 'X' in the box which, I presume, means I didn't backup the 'stock recovery' when doing my initial back before flashing ARHD8 ?
If so, is it possible to get the stock recovery somewhere ?
Thanks
10rdan said:
I've just been having a look at the various settings within TWRP and noticed that one of the options available when backing up is 'recovery'. By default there is no 'X' in the box which, I presume, means I didn't backup the 'stock recovery' when doing my initial back before flashing ARHD8 ?
If so, is it possible to get the stock recovery somewhere ?
Thanks
Click to expand...
Click to collapse
Lol even if you had checked this in TWRP when you took a backup of stock rom, guess which recovery you would've backuped
10rdan said:
I've just been having a look at the various settings within TWRP and noticed that one of the options available when backing up is 'recovery'. By default there is no 'X' in the box which, I presume, means I didn't backup the 'stock recovery' when doing my initial back before flashing ARHD8 ?
If so, is it possible to get the stock recovery somewhere ?
Thanks
Click to expand...
Click to collapse
Sorry, just read your reply re. getting stock recovery. Was posting my thread at same time.
Am I right about not having backed up 'recovery' because there was no 'X' in box ?
Thanks
---------- Post added at 01:58 PM ---------- Previous post was at 01:56 PM ----------
reaper90 said:
Lol even if you had checked this in TWRP when you took a backup of stock rom, guess which recovery you would've backup
Click to expand...
Click to collapse
TWRP !
---------- Post added at 02:06 PM ---------- Previous post was at 01:58 PM ----------
reaper90 said:
You can find it inside of this firmware package for O2 i extracted from latest OTA. But don't use the boot.img in there, if you do so, your mobile connections may not work after restore.
https://www.dropbox.com/s/ithmy88yf4dwnnw/firmware.zip
Click to expand...
Click to collapse
I've downloaded the file but winzip won't open it, 'central directory not found', so I can't extract the 'recovery' ??
10rdan said:
I've downloaded the file but winzip won't open it, 'central directory not found', so I can't extract the 'recovery' ??
Click to expand...
Click to collapse
No problems here using WinRAR, just copy it out of the zip.
reaper90 said:
No problems here using WinRAR, just copy it out of the zip.
Click to expand...
Click to collapse
Just downloaded 7-zip and 'got it out'. Must have been my copy of winzip at fault.
Thanks again and sorry for 'being a pain'.
Hey folks, this is urgend!
Why? Well, I wanted to do my girlfriend a favour and root her device and did so successfully, but it seems I cannot boot into any real ROM. The only ROM that successfully booted was the unofficial port of CM9. I uninstalled it because I would like to flash a daily driver for her. And that was when I tried fulmix.ROM as well as mySENSEdx+ v3. Here is my setup:
* TWRP 2.5 (official release)
* Formatted with SuperWipe JB
* Unlocked bootloader
Issues; When having flashed the ROM and installed boot.img through fastboot, all I get is a blackish screen, the device reboots every 5 minutes. Strange: I seem to not be able to perform a factory reset through TWRP. It always tells me that either cache or another smaller partition is inaccessible. Did I miss something while rooting? Any recommendations as how to solve this freaking issue will be REWARDED!
You are using the wrong recovery for your hboot. Your hboot version seems to be 1.25, but you are using a recovery made for hboot 1.24 and below. So go in Android Development Section and download TWRP for JB, flash that via fastboot and ROM installing as well as factory reset should work again.
1. Your main problem is the recovery. Don't use the official release but use the one for JB hboot from this thread : http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
2. In order to make sure that recovery is correct for your device, make sure you do have a 1.25 hboot (boot to bootloader and recheck that)
ckpv5 said:
1. Your main problem is the recovery. Don't use the official release but use the one for JB hboot from this thread : http://forum.xda-developers.com/showpost.php?p=36714573&postcount=2
2. In order to make sure that recovery is correct for your device, make sure you do have a 1.25 hboot (boot to bootloader and recheck that)
Click to expand...
Click to collapse
Thank you so much! To anwer your questions:
1. Will flash it ASAP after work. Is SuperWipe JB correct if want to flash your ROM?
2. It definately is. Would you Please tell me why the official TWRP will not work? Just curious..
SecUpwN said:
Thank you so much! To anwer your questions:
1. Will flash it ASAP after work. Is SuperWipe JB correct if want to flash your ROM?
2. It definately is. Would you Please tell me why the official TWRP will not work? Just curious..
Click to expand...
Click to collapse
1. Superwipe is not necessary. Just select wipe and do swipe to factory reset in TWRP is enough.
2. The official one is based on old files before JB is released to DX (e.g official TWRP for One X for the latest JB 4.2.2 hboot 1.73, touch is not working because it is based on old files)
ckpv5 said:
1. Superwipe is not necessary. Just select wipe and do swipe to factory reset in TWRP is enough.
2. The official one is based on old files before JB is released to DX (e.g official TWRP for One X for the latest JB 4.2.2 hboot 1.73, touch is not working because it is based on old files)
Click to expand...
Click to collapse
Everything is working good now. Any chance of an updated TWRP or 4EXT?
SecUpwN said:
Everything is working good now. Any chance of an updated TWRP or 4EXT?
Click to expand...
Click to collapse
Latest we have is TWRP 2.6.3.0, and it will probably be the latest for a while
GtrCraft said:
Latest we have is TWRP 2.6.3.0, and it will probably be the latest for a while
Click to expand...
Click to collapse
Does it work with Desire X without any issues?
SecUpwN said:
Does it work with Desire X without any issues?
Click to expand...
Click to collapse
No problems at all
GtrCraft said:
No problems at all
Click to expand...
Click to collapse
Can you help me here, please?
SecUpwN said:
Can you help me here, please?
Click to expand...
Click to collapse
Why don't you just flash a recovery and install rom from there.
Because flashing a recovery results in a "signature error" - means no recovery is flashable. This phone is not even able to get S-OFF yet, guess this is since the ROM itself is "corrupt" due to the HBOOT downgrade. Or am I getting this wrong?
Maybe... If I recall it correctly, the revolutionary scripts first interaction with the phone requires adb which isn't possible through bootloader. Do you have the stock recovery installed and can you boot into it? If yes, maybe adb can access your phone from there. If this is possible, try to run revolutionary from within the recovery...
dansou901 said:
Maybe... If I recall it correctly, the revolutionary scripts first interaction with the phone requires adb which isn't possible through bootloader. Do you have the stock recovery installed and can you boot into it? If yes, maybe adb can access your phone from there. If this is possible, try to run revolutionary from within the recovery...
Click to expand...
Click to collapse
That's the point: This phone doesn't have a recovery and flashing one is not possible. That's why flashing a complete RUU is trivial here. Are you able to find the adequate 1.22 RUU as a ZIP zo be flashed through fastboot?
Do you have the download link for the appropriate RUU? I can then extract it for you and load it up again, but I don't know which file you need exactly, as there are many RUUs on AndroidRuu...
dansou901 said:
Do you have the download link for the appropriate RUU? I can then extract it for you and load it up again, but I don't know which file you need exactly, as there are many RUUs on AndroidRuu...
Click to expand...
Click to collapse
Thank you so much! You'll find it here.
SecUpwN said:
Can you help me here, please?
Click to expand...
Click to collapse
I've got you covered friend
Sent from my C525c using Xparent Skyblue Tapatalk 2
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
There is no real difference between AT&T Kitkat and Jellybean on the One. In fact there are a few bugs with Kitkat. Such as the camera and a few others that have been posted.
njaustin123 said:
Hi All,
I bought this refurbished AT&T unlocked HTC One from eBay. I am with T Mobile.
I already unlocked the bootloader and rooted the phone. Why I did this:
1) I wanted to remove all the AT&T stuff including their update check which doesn't work with T Mobile SIM. (But not able to do it even after uninstalling with Titanium, those just come back on restart)
2) I wanted KitKat (either like an unlocked or international HTC one or the Google Play KitKat)
But I am not sure how to proceed.
I already have downloaded a ROM from this link: htconeroot.com/htc-one-stock-roms/android-4-4-kitkat-sense-5-5-stock-rom-for-htc-one
But not sure about S-OFF/ON etc because I am a newbie, this is my second android phone and first rooting.
Can anyone give me step by step instructions to install either a google play kitkat or a pure sense 5.5 kitkat? I would prefer if I can do this just once now and get future updates automatically from google/htc.
Mine is Android 4.3 based Sense 5.0 with all the AT&T stuff. I am in the US.
Click to expand...
Click to collapse
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
I dont want AT&T again
mb_guy said:
You could just try this
http://forum.xda-developers.com/showthread.php?t=2659374
Click to expand...
Click to collapse
I dont want AT&T again.
njaustin123 said:
I dont want AT&T again.
Click to expand...
Click to collapse
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader here.
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it here.
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Thanks. Any more Info?
cschmitt said:
I'd say switch to the Developer Edition rom, it doesn't contain all of the AT&T bloat.
1. Unlock the bootloader
2. S-Off via rummrunner or firewater.
3. Change CID to BS_US001 'fastboot oem writecid BS_US001'
4. Install Developer Edition 4.3 RUU, get it
5. Take OTA to 4.4.2.
There are guides in the One General and Q&A sections that cover all of this. Do a lot of reading, and then ask questions as needed.
Click to expand...
Click to collapse
Thanks a lot Schmitt. I think that is exactly what I have to do.
My bootloader is already unlcoked, Also I think I can handle Step 2 and Step3. Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
njaustin123 said:
Could you please pour or point me to more info on Step 4 and 5. Links to discussions here or other links will do. Being a newbie I am totally confused about stock, kernel, RUU etc.
Click to expand...
Click to collapse
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
Go to http://www.htcdev.com/devcenter/downloads and select 'Brightstar US' as the carrier, then 'Find Files' and download the 'RUU 3.22.1540.1 Developer Edition'. It is an EXE, just run it with the phone connected to the USB port of the computer and it will walk you through the install. After it reboots you will have developer edition 4.3, then update to 4.4.2 by OTA, just check in the Software Update menu in settings on the phone. It will download a file to the phone that will update it.
rumrunner didn't work
cschmitt said:
The RUU is easy, it is a complete software package for the phone that will restore it to the original software of the Developer Edition phones.
For the RUU to work, the CID (carrier id) must be set to BS_US001. This why you'll need to s-off the phone, so that you can change the CID.
.
Click to expand...
Click to collapse
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
njaustin123 said:
rumrunner gave this error:
unfortunately this isn't going to work out with your configuration. you have 2
options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner
(preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix thi
s issue for you!!!.
Click to expand...
Click to collapse
Flash the ElementalX kernel from here http://forum.xda-developers.com/showthread.php?p=40682393 and try again.
It's unsecured and should make rumrunner successful.
Thanks. It's S-OFF Now
cschmitt said:
Flash the ElementalX kernel from here and try again.
It's unsecured and should make rumrunner successful.
Click to expand...
Click to collapse
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
njaustin123 said:
Thanks a lot. I did the kernel update and then S-OFF. Will try RUU tonight.
Click to expand...
Click to collapse
See, this stuff is easy. You'll like the Dev Edition ROM.
In Dev Edition
cschmitt said:
See, this stuff is easy. You'll like the Dev Edition ROM.
Click to expand...
Click to collapse
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
njaustin123 said:
Thank you again. I installed 4.3 RUU and OTAed to KitKat.
Very much satisfied and happy with it.
Some questions:
My root and custom kernel are gone. Even the TWRP recovery is lost.
Do I need to flash TWRP as recovery again? And install SU and 4.4 ElementalX again for root and getting the kernel? If yes and if I do these, will my future OTAs be blocked?
Click to expand...
Click to collapse
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
How do I flash stock recovery?
clsA said:
Yes
yes and Yes
you get future OTA by returning to stock first (flashing stock recovery will sometimes be all that's needed)
Click to expand...
Click to collapse
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
njaustin123 said:
How do I flash stock recovery? If that alone doesn't work, is a complete installation with RUU the only way?
Click to expand...
Click to collapse
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Could not find the recovery image
cschmitt said:
Flash it using fastboot just like you would flash TWRP. The stock recovery can be pulled out of a firmware.zip.
Click to expand...
Click to collapse
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
njaustin123 said:
I got the notification for 4.19.1540.9 update. I was about to go back to the stock recovery to update this.
But could not unzip the recovery image from the RUU zip
(PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip). It was not unzippable and even after repairing it with zip_repair tool I could not get the recovery image.
Also I downloaded recovery_1.29.1540.16_R.img from another xda post. That didn't work. After giving start update, it was stuck at a red triangle with a warning sign.
Click to expand...
Click to collapse
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Any idea where can I get it?
mb_guy said:
I think both of those recoveries are too old, you need the one for your currently installed kitkat version.
Click to expand...
Click to collapse
Any idea where can I get it?
njaustin123 said:
Any idea where can I get it?
Click to expand...
Click to collapse
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
No. That doesn't have it
mb_guy said:
I can't find the 4.19.1540.x version but I believe any 4.19.x.x version will work.
I think the stock recovery may be in this dark bootloader firmware download .
http://www.htc1guru.com/downloads/firmware-downloads/
Get the 4.19.401.8 download and see if the recovery.img is included.
Best I can come up with for now.
Click to expand...
Click to collapse
I just downloaded it and checked, it doesn't have the recovery.img
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
Q&A for [ROM][4.4.4_r2][OFFICIAL][GPL] LiquidSmooth v3.2 - vigor - 10|12|14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
bunchies said:
Final KitKat build coming soon, Lollipop was released this morning :thumbup:
Let's see if the Rezound can run android 5.0
Click to expand...
Click to collapse
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
catcher8587 said:
Let's hope so!
I'm thinking of trying this ROM out coming from Cyanogen mod and I am S-On. If I follow the instructions in the OP should I be ok? I see I will have to flash the boot.img separately.
Click to expand...
Click to collapse
Yeah, you will be fine
s-on users flash boot.img in fastboot
Last Build
I set the last build and at once found an error. If to come Settings - the Mobile network - Settings of the operator you give out an error: "In application of "com.android.phone" there was an error..." At all so? I quickly discharge the battery for some reason!
Crash video playing
added small problem... When I want to view video sometimes issues the error message. Video doesn't play...
re:chrome floating windows
Just uninstall and download an older version of chrome. Then, don't accept the update. You can't turn off the floating windows. Very annoying
HTC Rezound Liquidsmooth 3.2 ROM install failure
I used this link (theunlockr.com/2013/10/22/how-to-root-the-htc-rezound/) on my stock HTC Verizon Rezound to unlock the bootloader, installed TWRP, and SuperSU to gain access to root.
Then I downloaded LiquidSmooth 3.2 11/5/14 R2 -- Android 4.4.4 and Gapps 4.4.4 Build 8.1 (not Build 7 on this site) I used TWRP to flash both files in the same flash event to the phone. I had placed the files on the INTERNAL SD in the DOWNLOAD directory. Wiped before and after the flash. Phone came up to HTC screen, Blinked, and returned to HTC screen. Waited 10 minutes or so and had to pull battery . Tried another boot with same results. Restored. Repeated same results.
Downloaded the LS v3.2 file again. Downloaded an md5 checker program to my computer. Both files passed. Repeated using second v3.2 file with same results. Downloaded the 8/21/2014 version of the file, md5 checked it, and repeated with same results.
Then downloaded the final LS v2.9 JB4.2.2 file and the appropriate GAPPS file and md5ed it. Repeated with same results.
I am now back to my rooted but stock ROM. I would like to get this LS v3.2 KitKat ROM installed, but am at my wits end.
I also used this link (android.wonderhowto.com/how-to/ultimate-guide-using-twrp-only-custom-recovery-youll-ever-need-0156006/) to troubleshoot. That is why I did a wipe in advance of the first install attempt and I think most of the others as well, although I couldn't tell it helped. I tried the Fix Permissions hint several times but it failed each time.
The only think I have ever read about on HTC phones is S-On or S-Off, but I don't think this applies as neither link source I referred to mentioned S-ON.
Any help would be appreciated. Thanks in advance.
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Thanks a Million or perhaps 10 million!!!
acejavelin said:
When you are S-ON you have to manually flash the boot.img via Fastboot after flashing the ROM image in recovery... or boot recovery with fastboot not from the phone... in order to boot successfully. When an HTC device is S-ON, the boot partition is write protected from recovery if it is booted from the phone.
Click to expand...
Click to collapse
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
xdatsellers said:
I'll not bore you with the details, but I just now found you had replied to my question. I refreshed myself on fastboot (I used it in the unlock process a few days back), extracted the boot.img file, and flashed it.
Guess What? It worked.
Thanks a lot. I do think it would be great if people would include a brief statement on HTC ROM installation Instructions, "If you are not S-OFF you must use fastboot to flash the boot.img file (extract from ROM zip) after flashing the ROM. If you do not know what that means, Google it!"
BTW, if for some reason I every wanted to go back to my stock ROM, I assume that I would have to do the same thing (Flash ROM following by Fastboot Flash boot.img file) after restoring or would my Nandroid backup work? I doubt it would for the same reason. It will be hard to find that file (unless it is contained in the backup) since the ROM was by OTA programming.
Thanks again,
Terry
Click to expand...
Click to collapse
Most general tutorials on flashing ROMs on HTC devices includes this information, although most devs will say their ROMs are for S-OFF devices only, it is assumed with a little fastboot trickery most ROMs will work fine, but devs usually make the assumption you know what you are doing.
I would HIGHLY recommend you go S-OFF... if something catastrophic happens and you are S-ON there is often no method of recovery, since all current RUU (HTC's proprietary ROM restoration image) files are prior to current, so do downgrade and restore to stock you must be S-OFF. Rumrunner makes the S-OFF process pretty painless if you are on a custom ROM already.
The boot image, or more accurately the /boot partition, cannot be written to under normal recovery well S-ON, so that affects a nandroid restore as well, you would have to extract the boot image and flash it manually as well to restore a nandroid. BUT, if you boot the recovery image via fastboot it gets around the /boot write restriction even when S-ON... this is a key difference, essentially you are taking the recovery image and telling the phone "this is your new kernel, start it like a ROM" which gets around some of the S-ON restrictions.
Grey network bars
Hello bunchies
I really enjoyed using this rom except this problem my network bars are grey but i can make and receive calls and use the 3g on slow speed (the problem when i call the customer service centre i can't press numbers)
I've checked hboot radio and recovery they are updated
Sorry for my bad English and thanks in advance
Need help to install liquidsmooth
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Thank you
Sent from my SM-N900 using XDA Free mobile app
edwardnizz said:
Hi I have a verizion htc rezound s-on that is unlocked with amon ra recovery ics rooted super su . What do i need to do to install liquid smooth
Click to expand...
Click to collapse
Assuming you are on current Hboot & radios, upgrade to latest TWRP, flash ROM ZIP and Gapps, fastboot flash boot.img, then reboot and enjoy.
Hello i'm just asking if there wont be any problems with rom update such as recovery boot loop or Freeze or crashes .....etc kthnxbai
can't send SMS or ssd with liquidsmooth 3.2
Hi. As the title says , i cant sens SMS nor use ussd codes. Another issue is that i can't play music. Any help would be appreciated.