Phone is stuck on boot ( S-on - custom recovery - branded) - One (M8) Q&A, Help & Troubleshooting

Hello everyone,
My friend has tried to get into the rooting scene and without proper knowledge he managed to get himself stuck on the boot screen.
I offered him my help, since I thought that this would be an easy fix because the phone still has access to the TWRP recovery.
What I didn't know is that the phone was branded and S-on. The CID is: VODAPE17.
ADB works in recovery mod !
To sum it up:
CID: VODAPE17
The bootloader is unlocked
S-on
Acces to custom recovery
no backup
adb works
fastboot works
What I have tried:
I tried to get the device S-off with HTC dev. But it required me to boot up the phone, so that didn't work out.
I have found a nand backup that should work with this CID on this page: http://forum.xda-developers.com/showthread.php?t=2701376&page=5
This one: 3.29.161.9 - TWRP Thanks to Petert87 (what does that number: 3.29.1619 mean?)
I unpacked the file. Send it to the internal storage and renamed it to a backup that I had made myself (otherwise TWRP wouldn't recognize it?).
After wiping I restored the backup, but to my surprise the phone still was stuck on the HTC one logo when I tried to boot it!
I tried to get as much information from the phone as possible.
This is what I got:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-cpld: None
version-microp: None
version-main: 4.19.161.2
version-misc: PVT SHIP S-ON
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: VODAPE17
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 3aa067db
hbootpreupdate: 11
gencheckpt: 0
My question
Can anyone help me to get this phone running again? I don't really know what to do anymore.
Every bit of help is appreciated very much! :good:
Thank you in advance!
Sietse

After flashing countless amounts of customs roms I still don't make any progress.
I have even tried to flash the boot.img of a custom rom separately with fastboot but that didn't work either.
Something is preventing this phone from booting, but I don't know what
Does anyone have idea's? They will be greatly appreaciated!

Download and install latest TWRP from their website, not playstore. Do full wipe including system, then format data typing yes to confirm. Download compatible ROM to extSD, mount extSD in TWRP and install from extSD. That's what I would try. Your firmware looks up to date..

flyera343 said:
Download and install latest TWRP from their website,
Click to expand...
Click to collapse
Agree, this is very important. Some older versions of TWRP won't work with the current hboot. You can drive yourself crazy flashing a hundred ROMs, and it still won't work.

Same issue here. Latest firmware. S-ON. Every custom ROM causes a boot loop. Luckily I had a nandroid of stock ROM (5.0.1) so I can always go back to stock.

petrjanda said:
Same issue here. Latest firmware. S-ON. Every custom ROM causes a boot loop. Luckily I had a nandroid of stock ROM (5.0.1) so I can always go back to stock.
Click to expand...
Click to collapse
As already stated by myself and another, make sure TWRP is up to date (2.8.7). Outdated TWRP is the most common cause for many ROMs bootlooping.

Related

Problems during restoring phone

Hi everyone,
I'm stuck, I am trying to restore my HTC One X to stock as I am sending off for repair, however its not working. I've read many tutorials but I'm still not getting anywhere.
I've locked the phone, replaced the recovery.img and replaced the boot.img however the RUU won't install.
My phone is from Australia, Virgin and has the CID of: CID_023
My original Nandroid back-up is gone, so I can't use that.
Can anyone give me some advice on what I might be doing wrong and what information you require to help me?
S-ON
HBOOT-1.39.0000
FabMan_UK said:
Hi everyone,
I'm stuck, I am trying to restore my HTC One X to stock as I am sending off for repair, however its not working. I've read many tutorials but I'm still not getting anywhere.
I've locked the phone, replaced the recovery.img and replaced the boot.img however the RUU won't install.
My phone is from Australia, Virgin and has the CID of: CID_023
My original Nandroid back-up is gone, so I can't use that.
Can anyone give me some advice on what I might be doing wrong and what information you require to help me?
S-ON
HBOOT-1.39.0000
Click to expand...
Click to collapse
Post the result from command fastboot getvar all and delete your S/N and IMEI from the info
Thant said:
Post the result from command fastboot getvar all and delete your S/N and IMEI from the info
Click to expand...
Click to collapse
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.17.728.1
serialno:
imei:
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4611000
cidnum: HTC__023
battery-status: good
battery-voltage: 4157mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Thanks
FabMan_UK said:
version: 0.5a
version-bootloader: 1.39.0000
version-baseband: 5.1204.162.29
version-cpld: None
version-microp: None
version-main: 3.17.728.1
serialno:
imei:
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4611000
cidnum: HTC__023
battery-status: good
battery-voltage: 4157mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
Thanks
Click to expand...
Click to collapse
You must to restore nandroid backup no RRU for nwer base more then 3.14. NOW
1. Install this recovery with command fastboot flash recovery recovery.img
2. download this Nandroid Backup
3. go in recovery mount the sd card and unrar the nandroid backup to your computer after this paste on your SD card in folder Backup
4. flash the boot.img, erase cache, and restor nandroid from recovery.
5. You must to install stock recovery and you are full stock and you can receive OTA
Thant said:
You must to restore nandroid backup no RRU for nwer base more then 3.14. NOW
1. Install this recovery with command fastboot flash recovery recovery.img
2. download this Nandroid Backup
3. go in recovery mount the sd card and unrar the nandroid backup to your computer after this paste on your SD card in folder Backup
4. flash the boot.img, erase cache, and restor nandroid from recovery.
5. You must to install stock recovery and you are full stock and you can receive OTA
Click to expand...
Click to collapse
Thank you for your help, so the problem for me was the 3.14 update I had applied. I can't download the file at work, I'll try at home later.
Thant, I want to thank you for your assistance with this problem. Your solution worked, I was able to install the OTA update.
The guides I was following used the RUU as the solution to those without a working Nandroid back up of their own, I wasn't aware that 3.14 or newer could be a problem for that. It is a shame out of date guides are not removed or updated.
I had seen people upload nandroid backups, but I didn't trust those. I decided to take a chance with yours and it worked for me.
My info now states:
version: 0.5a
version-bootloader: 1.73.0000
version-baseband: 5.1204.167.31
version-cpld: None
version-microp: None
version-main: 4.19.728.3
serialno:
imei:
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4611000
cidnum: HTC__023
battery-status: good
battery-voltage: 4061mV
devpower: 97
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
SuperSU is still install, I am now assuming the firmware/h-boot is still a modified version. Looking into it.
Thant said:
You must to restore nandroid backup no RRU for nwer base more then 3.14. NOW
1. Install this recovery with command fastboot flash recovery recovery.img
2. download this Nandroid Backup
3. go in recovery mount the sd card and unrar the nandroid backup to your computer after this paste on your SD card in folder Backup
4. flash the boot.img, erase cache, and restor nandroid from recovery.
5. You must to install stock recovery and you are full stock and you can receive OTA
Click to expand...
Click to collapse
Okay I'm going crazy SuperSU is on my phone and I can't get rid of it. I couldn't uninstall it, so I re-rooted the phone, installed custom recovery, installed SuperSU binaries then tried to uninstall. But every reboot reinstalls the application. Argh!!!
Any help with this?
Okay fixed the SuperSU problem, unfortunately the Nadroid backup supplied was not a stock image, still worked though when I did a factory reset, restored nandroid backup, install SU binaries, uninstalled SuperSU from OS, restored recovery, locked OEM, downloaded OTA and installed it.
So it all looks good except the recovery option comes up with an image of a phone and a large red exclamation mark, I assume this means the recovery.img doesn't match. Is there a way to fix this as I'd like my phone repaired?
Thank you
-EDIT-
Okay, I've done some more reading and learnt a little more, which is great.
I believe I need recovery.img for 4.19.728.3, so that will match the software on my phone. I've tried stock recovery for 4.19.707.3 but that didn't work.
I wonder if I should downgrade everything. Say downgrade HBOOT to 1.39, then install stock software of 4.18 and removing SuperSU, then flash stock recovery, lock the phone and attempt a OTA update to update everything. I'm assuming an OTA update would update HBOOT to 1.73, the software to 4.19 and the recovery will also be updated to work. Is this a good solution perhaps?
FabMan_UK said:
Okay I'm going crazy SuperSU is on my phone and I can't get rid of it. I couldn't uninstall it, so I re-rooted the phone, installed custom recovery, installed SuperSU binaries then tried to uninstall. But every reboot reinstalls the application. Argh!!!
Any help with this?
Okay fixed the SuperSU problem, unfortunately the Nadroid backup supplied was not a stock image, still worked though when I did a factory reset, restored nandroid backup, install SU binaries, uninstalled SuperSU from OS, restored recovery, locked OEM, downloaded OTA and installed it.
So it all looks good except the recovery option comes up with an image of a phone and a large red exclamation mark, I assume this means the recovery.img doesn't match. Is there a way to fix this as I'd like my phone repaired?
Thank you
-EDIT-
Okay, I've done some more reading and learnt a little more, which is great.
I believe I need recovery.img for 4.19.728.3, so that will match the software on my phone. I've tried stock recovery for 4.19.707.3 but that didn't work.
I wonder if I should downgrade everything. Say downgrade HBOOT to 1.39, then install stock software of 4.18 and removing SuperSU, then flash stock recovery, lock the phone and attempt a OTA update to update everything. I'm assuming an OTA update would update HBOOT to 1.73, the software to 4.19 and the recovery will also be updated to work. Is this a good solution perhaps?
Click to expand...
Click to collapse
You can't downgrade are you upgrade the stock rom to 4.19?
if you are on 3.17.728.x you need stock rom not rooted and stock recovery 3.17.728.x maybe you can try with stock recovery 4.19.728.x
Thant said:
You can't downgrade are you upgrade the stock rom to 4.19?
Click to expand...
Click to collapse
Yes, I upgraded stock ROM to 4.19.
Thant said:
maybe you can try with stock recovery 4.19.728.x
Click to expand...
Click to collapse
That would be great, a Google search doesn't show anything and neither does a search on XDA forums, would you have any suggestions where I could find it?
Thanks

Cannot flash custom rom, but why ?

Hey there,
i have a strage problem, after rooting a lot of android devices the m8 behaves kind of strange.
I got a brand new M8 (Hbot 3.15xxxx and 4.4.2) for my girl friend and unlocked the device with htc dev. after this i flashed twrp 2.7.0.2, no big deal.
Now i made a backup (thank god....) and downloaded viper rom and arhd roms.
But if i install a rom (does not matter which one, with wipe and so on) the script tells me installtion is finished, but if i hit the next button the m8 vibrates and turns off, at least the screen goes dark.
the only way to wake up the m8 is to push power and volume up button, but the only thing i see is the htc logo with the red text at the buttom.
adb reboot boatloader does not work, but reboot recocery does. Wipen cache and so does not fix the problem, the stock backup can be restored.
do you have any idea what's going on, i really want to run viper or arhd on the m8.
thanks!
Havoc2k said:
Hey there,
i have a strage problem, after rooting a lot of android devices the m8 behaves kind of strange.
I got a brand new M8 (Hbot 3.15xxxx and 4.4.2) for my girl friend and unlocked the device with htc dev. after this i flashed twrp 2.7.0.2, no big deal.
Now i made a backup (thank god....) and downloaded viper rom and arhd roms.
But if i install a rom (does not matter which one, with wipe and so on) the script tells me installtion is finished, but if i hit the next button the m8 vibrates and turns off, at least the screen goes dark.
the only way to wake up the m8 is to push power and volume up button, but the only thing i see is the htc logo with the red text at the buttom.
adb reboot boatloader does not work, but reboot recocery does. Wipen cache and so does not fix the problem, the stock backup can be restored.
do you have any idea what's going on, i really want to run viper or arhd on the m8.
thanks!
Click to expand...
Click to collapse
Just a bug in TWRP, nothing to worry about. Disable from TWRP the screen timeout and you are good to go.
stathis95194 said:
Just a bug in TWRP, nothing to worry about. Disable from TWRP the screen timeout and you are good to go.
Click to expand...
Click to collapse
i don't think thats the problem. if the screen would timeout (like while doing backup or restore) i could wake it up.
but the device is not booting anymore then. Even if i do a adb reboot recovery and make a clean reboot. Just the htc logo with the warning.
could it be the firmware ? i dont see any information for hboot 3.15.....
thanks
Havoc2k said:
i don't think thats the problem. if the screen would timeout (like while doing backup or restore) i could wake it up.
but the device is not booting anymore then. Even if i do a adb reboot recovery and make a clean reboot. Just the htc logo with the warning.
could it be the firmware ? i dont see any information for hboot 3.15.....
thanks
Click to expand...
Click to collapse
Are you flashing a 4.4.3 ROM? which firmware are you on? Can you please do a :
fastboot getvar all
and post the outcome? Don't forget to hide your sensitive info (imei, etc)
stathis95194 said:
Are you flashing a 4.4.3 ROM? which firmware are you on? Can you please do a :
fastboot getvar all
and post the outcome? Don't forget to hide your sensitive info (imei, etc)
Click to expand...
Click to collapse
yes i will flash viper 2.0.0 or arhd 10.2 both are 4.4.3 roms.
device is running at 4.4.2 at the moment (rooted stock vodafone germany)
getvar all:
Code:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA03_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43FWM10422
imei: xxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: T-MOB101
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
m8_ul...... what device is it? internation one? should be, there are no at&t or sprint devices in germany, are they?
edit: i think i found the problem:
ckpv5 said:
Right ... your current hboot is 3.16 so it's 1.54.707.7
I suggest that you restore 1.54.707.7 stock Backup, flash back stock recovery and do the OTA (no need to relock bootloader or S-On .. OTA update work on unlocked bootloader and S-Off)
Click to expand...
Click to collapse
so the firmware should be the problem, i am right?
Havoc2k said:
yes i will flash viper 2.0.0 or arhd 10.2 both are 4.4.3 roms.
device is running at 4.4.2 at the moment (rooted stock vodafone germany)
getvar all:
Code:
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.15.2133156.UA03_2G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT43FWM10422
imei: xxxxxxxxx
imei2: Not Support
meid: 00000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: T-MOB101
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
m8_ul...... what device is it? internation one? should be, there are no at&t or sprint devices in germany, are they?
Click to expand...
Click to collapse
Well nothing strange here. You are on older firmware trying to flash a 4.4.3 ROM. First boot might take up to 15 minutes...But after that you will experience slow boots and/or wifi or bt issues.
You can either try to s-off and upgrade firmware or try a 4.4.2 rom like ARHD 8.1
First of all try the following. Flash the ROM and reboot and let it sit there for around 15 minutes to see if it boots. And we can see your choices from there.
If i want to update with OTA,
which stock recovery i need to flash ? my version.main is empty :/ so i am not sure how to flash the right recovery. there a lots of them: http://forum.xda-developers.com/showthread.php?t=2701376
Havoc2k said:
If i want to update with OTA,
which stock recovery i need to flash ? my version.main is empty :/ so i am not sure how to flash the right recovery. there a lots of them: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Try here:
http://www.handy-faq.de/forum/htc_o...resammlung_ruus_otas_backups.html#post2832637
it's either 1.12.111.18 or 1.57.111.2
it is 1.12.111.18
at the moment the OTA to 1.57.111.2 is running
some german forums wrote that any 1.12.xxx recovery will work for the ota. let's see if there is another ota after this one.
edit: 1.57 went well, now ota to 1.70

H3G__001 stock lollipop nandroid

Hi im trying to update to lollipop on my 3 UK branded m8 but im having serious issues upgrading to 4.4.4 eye experience version 3.32.771.3 was wondering if anyone has or could get a nandroid of the stock 4.20.771.2 ROM. I can see an OTA in http://forum.xda-developers.com/showthread.php?t=2701376 but I have no idea how to use those OTA files. Any help would be appreciated.
Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.
ckpv5 said:
Post your fastboot getvar all result (minus serial no. & imei no.)
then we know which backup that you really need.
No point to give you 4.20.771.2 backup for now.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.21331147A1.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.771.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dcdaa6e0
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
hmmm it says OS version 4.20.771.2 there but in about phone --> software info. it says 2.22.771.5 for software number. not sure what that means?!
Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
ckpv5 said:
Try restore my backup and see how it goes : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
Click to expand...
Click to collapse
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?
f_padia said:
cool thanks. I tried your nandroid backup and it starts up fine but I cant connect to my wifi network. It sees the network but it wont connect. It does allow me to connect to another open network I can see but not my own. This happened on one of the stock updates I did too. Any ideas why this might be? or how it might be fixed?
Click to expand...
Click to collapse
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice
ckpv5 said:
There are two options :
1. Restore 3.32.771.10 backup and its stock recovery image then do OTA to 4.20.771.2
You can have all the needed files here : http://forum.xda-developers.com/showpost.php?p=55322461&postcount=1897
Or
2. Reflashed the untouched 4.20.771.2 firmware that linked here : http://forum.xda-developers.com/showpost.php?p=58781201&postcount=4598
but you need to relock bootloader in order to do that.
a. put your device in bootloader/fastboot mode
b. relock bootloader - fastboot oem lock
c. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.20.771.2_firmware.zip
fastboot flash zip 4.20.771.2_firmware.zip .....( again for the 2nd time)
fastboot reboot
d. check your wifi
For me .. 1st option is a better choice
Click to expand...
Click to collapse
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?
f_padia said:
so I tried option 2 first and that didnt work Then I tried option 1. Flashing 3.32.... worked ok wifi working etc. I then did the OTA that popped up. That flashed and it boots up but system ui force closes and wifi doesnt turn on at all Is there anyway to flash your OTA update specifically and avoid downloading and flashing the one that pops up on screen?
Click to expand...
Click to collapse
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot
ckpv5 said:
You can't flash OTA manually because your device is S-On.
When you have system ui force close and wifi doesn't turn on at all ... that's a good sign.
What you need to do now is unlock bootloader again with unlock_code.bin that you received from HTC. Then install TWRP 2.8.5.0. Boot to TWRP recovery, select mount - advance - format data - yes
Reboot - check your wifi again - system ui should work and wifi should work too.
Then restore my 4.20.771.2 backup (reason is when re-unlock bootloader and format data .. all data files such as calculator & flashlight & etc are removed)
EDIT : before you do the above, please try boot to recovery where you see the red triangle .. press & hold volume up & press power once.
In stock recovery, select factory reset/wipe data ... reboot
Click to expand...
Click to collapse
before I saw your message I did a factory rest from stock recovery as you suggested in your edit and system ui force close was fixed and wifi does turn on... but im back to the problem of not being able to connect to my wifi network. I've managed to connect to 2 separate open (public) networks fine but cant connect to mine for some reason. I cant understand why this might be happening.
Thanks for all the help by the way really appreciate it!
That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.
ckpv5 said:
That's something I'm not familiar with as I never have that problem before. I read a few thread of this kind of wifi problem .. there are a few suggestions such as reset the router, try change wifi password and a few more like 2.4GHz & 5.0 GHz problem
Maybe someone else more familiar with this kind of problem will step in.
Click to expand...
Click to collapse
I had a look around and came across this http://www.pcadvisor.co.uk/how-to/g...llipop-solve-wi-fi-problems-on-nexus-devices/ where it suggests changing wifi router channel. I did and it works
Cant thank you enough dude. i've tried to thank all your posts to reflect how many thanks you deserve! At one point when one of the software updates went bad and the screen wouldnt turn on I was told HTC would charge around £200 to fix it! so yeah, thanks
Great :good::good:
Will keep that in mind in case someone else has same problem
-deleted-
Lost RUU backup
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
D:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.054s
lv426HuDz said:
Hi I to am trying to revert back to stock on my HTC one M8 (Three UK H3g__00)1 but I have lost my original backups do to an hdd fail the RUU files you posted on here I believe I could have used but the links no longer work
My phone is in a bad way at the moment it is softbricked with the latest version of CWRM on and no OS currently installed, is this why my version main appears blank?
My phone has ended up in this state after trying to install the latest android revolution rom (5.0.1). The rom seemed to install ok booted and setup fine but my Wifi wouldn't turn ON at all. After I rebooted the phone for the first time it got stuck in a boot loop.
I deally would like to get lollipop on the phone and doing some reading I believe with the situation I'm in I have to go back to stock and do the OTA updates to raise my hboot version to 3.18 or above, that way I could install cyanogen 12.1
Apologies for noob question still learning.
My bootloader (3.16) is tampered, unlocked and S-ON
Click to expand...
Click to collapse
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x
ckpv5 said:
First - remove the serial no. & imei no. on your above post.
Second - install TWRP 2.8.1.0, don't use CWM recovery.
Third - read this thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
for how-to and restore 1.54.771.9 backup & its matching recovery then do multiple OTAs up to the latest 4.xx.771.x
Click to expand...
Click to collapse
Hi ckpv5, thanks I will give this a try now, I did try to flash TWRP 2.8.7.0 recently but when I tried to enter the recovery it just hung and I never figured out why. I will give 2.8.1.0 a go now.
Last night, just to get my phone working I flashed on cm-11-20141112-SNAPSHOT-M12-m8 with open_gapps-arm-4.4-mini-20151203. It all seemed to be working fine and I liked the look and feel of the KitKat cyanogenmod but after I received my first phone call my phone speaker went crazy and gave some nasty distortion out, I rebooted the phone to stop it and now I have the noise on everything if I turn my volume up to mid/high, I'm worried my speakers are damaged. I followed a couple of threads to install the viperapp but with no success, any ideas on this one?
Cheers,
Thanks
CHeers ckpv5 Ifollowed the guide used the files and its all sorted now.
Looks like CM11 has damaged my bottom speaker though i have ordered a replacement.
I do have 1 last question, after all the updating i have now put cm12.1 on and it seems to be running ok however when im booted into the OS my SD card is not being detected. If i drop back into TWRP recovery it does recognise the SD card, any ideas? im searching for a solution now.
I can't comment anything on CM as I never use one .. no experience on CM .. sorry.

Cannot install TWRP Recovery

Hi,
My phone got the red triangle and exclamation mark after upgrading my firmware. I believe this was due to it wiping the custom recovery which was TWRP. I have tried to reinstall TWERP but I get stuck on the entering recovery screen.
I have tried to install twrp a couple of times with no joy but I have a copy of philz recovery and this installed 1st time.
Any ideas? I have tried clearing the cache in fastboot but am stuck.
I have no phone as the rom I install is on the ext sd card and Philz touch will not mount the ext sd card.
Thanks in advance
Ugg
uggitt said:
My phone got the red triangle and exclamation mark after upgrading my firmware. I believe this was due to it wiping the custom recovery which was TWRP. I have tried to reinstall TWERP but I get stuck on the entering recovery screen.
Click to expand...
Click to collapse
You reverted to stock recovery, which flashing firmware will always do, unless its a modded firmware which has the stock recovery removed.
Confirm that your bootloader is UNLOCKED (which is needs to be to flash recovery).
Also, if you update to Lollipop firmware (which is usually the reason for updating firmware) you need to use one of the more recent TWRP versions. I recommend TWRP 2.8.7.
Older TWRP versions do not work on LP, and fail to install properly is the mode of failure. Similarly, Philz does not work on LP.
EDIT: To clarify TWRP build.
I have checked and the bootloader is unlocked, s-off and super cid.
The problem is I cannot get twrp to load up. I install it with fasboot and all goes well but when I try to get into recovery it just stays on the entering recovery screen.
I have tried to reinstall the latest firmare using the'Firmware Flashing without the panic attacks' guide as I have always used and this seems to install ok and then tried to install twrp again ( I have tried the latest and the previous copy) but no joy. I can though install philz recovery and that boots up fine.
So still stuck trying to get twrp installed.
Also if I reboot the phone hangs while starting upon the htc screen with red text but the phone is actually working behind this, just cant see the normal desktop/startup screen. If i hold the power button so the screen goes off and the hold the power button to turn it on the screen comes to life.
For information, I am on Android HD 41.0 as this is the only rom I had on the internal sd
What numbers listed on hboot screen:
- hboot number
- radio baseband
- OS
And what version TWRP are you trying to install?
Hi,
Here is the info from getvar and thank you for your help:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA459WM******
(bootloader) imei: ********************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Twrp versions tried are 2.8.7.0 and 2.8.6.1 from https://twrp.me/devices/htconem8gsm.html
redpoint73 said:
Older TWRP versions do not work on LP, and fail to install properly is the mode of failure. Similarly, Philz does not work on LP.
Click to expand...
Click to collapse
I beg to differ, no problems running 2.8.5.0 or 2.8.6.0 on lollipop for me. Installed via fastboot or flashify.
uggitt said:
Here is the info from getvar and thank you for your help:
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-main: 1.54.401.10
Click to expand...
Click to collapse
Your firmware flash never properly "stuck".
Your getvar data indicates you are on the original version firmware (1.54) which is over a year old. The current firmware would have updated you to hboot 3.19, radio 1.2xxx, and main version 4.16.401.
This also explains why Philz works, and the current versions of TWRP do not work. The current TWRP versions only work on Lollipop firmware; and only older TWRP versions work with your 3.16 firmware.
Try running the 4.16.401 firmware twice, this is often necessary to get it to flash properly. Then once you've confirmed you are on hboot 4.16, radio 1.2xxx, main version 4.16.401, then try TWRP 2.8.7.
---------- Post added at 03:19 PM ---------- Previous post was at 03:14 PM ----------
ashyx said:
I beg to differ, no problems running 2.8.5.0 or 2.8.6.0 on lollipop for me. Installed via fastboot or flashify.
Click to expand...
Click to collapse
True, a few of the recent builds will work on LP. But older ones than that won't work, trust me. I forget the breakoff point exactly, which is why I recommended the most current version (2.8.7). And once the most current version is known to be stablen (which 2.8.7 is), its usually the best recommendation.
I didn't mean to state that 2.8.7 is the only version that works. But I see how it can be interpreted that way (and have edited the previous post for clarity). For some reason, I constantly see folks still trying to flash much older TWRP builds (2.7 or so) onto Lollipop (which won't work).
And it turns out the OP had the opposite issue (trying to flash newer version TWRP on really old firmware hboot 3.16).
Thank you, I will try and flash the firmware again. Have you a link for this. I have been getting it from the ARHD Firmware page but not sure if its corrupt.
uggitt said:
Thank you, I will try and flash the firmware again. Have you a link for this. I have been getting it from the ARHD Firmware page but not sure if its corrupt.
Click to expand...
Click to collapse
4.15.401 (Euro) firmware is probably the most commonly downloaded and installed firmware from that collection. So it should be fine.
You probably just flashed the firmware once; when twice is often needed.
I managed to get the updated firmware on my phone eventually. I had to download from another link and it flashed first time.
Twrp installed straightaway and I am back on S.Rom.
Thank you for all your help, much appreciated
ugg..

need stock RUU for htc desire 816 dual sim india

hi all, my phone is stuck on boot mode for a couple of weeks and I am still not able to find correct stock rom. please help me find one so that I can flash it via fastboot. here are the getvar all details from fastboot:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.31.50.1103
version-cpld: None
version-microp: None
version-main: 1.61.720.1
version-misc: PVT SHIP S-ON
serialno: FA484MZ00452
product: a5_dwg
platform: hTCBmsm8226
modelid: 0P9C51000
cidnum: HTC__038
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: be7179e5
hbootpreupdate: 11
gencheckpt: 0
HTC desire 816 A5_dwg
Kit Kat RUU:
http://www.mediafire.com/?jimitej7orp4qcr
Lollipop RUU:
http://www.4shared.com/zip/9nQZohiEba/0P9CIMG_A5_DWG_L50_DESIRE_SENS.html
***RELOCKED***
A5_DWG PVT SHIP S-ON
HBOOT-3.19.0.0000
RADIO-1.31.50.1103
OpenDSP-v28.2.2.00546.0331
OS-1.61.720.1
eMMC-boot 1536MB
Nov 4 2014,20:04:44.23583
I already tried the kitkat one u r posting. it said something remote:12 signature failed
Download lollipop RUU, should work with your device.
Have you tried flashing with sd-card?
When did this bootloop first appear?
nukaru said:
Download lollipop RUU, should work with your device.
Have you tried flashing with sd-card?
When did this bootloop first appear?
Click to expand...
Click to collapse
sorry for late response, I tried the lollipop RUU too
1. with fastboot, it says :02 remote fie is too large
2. via sd card...finding package..opening package....unable to map file
And here is the story of bootloop. my phone was working fine till I received the official lollipop update, which failed repeatedly during installation. I checked the recovery log and found some error in system/bin/flash_camera and decided to flash just recovery image. I flashed recovery and boot image from the ota update I received...but got stuck. then I started trying all these RUU stuff but still no clue. thanks for listening
Ah, okay.
Can you select recovery in hboot and does it start up normally? Have you tried a Kit Kat nandroid backup with twrp?
Ps: you need to delete your imeis in the first post..
nukaru said:
Ah, okay.
Can you select recovery in hboot and does it start up normally? Have you tried a Kit Kat nandroid backup with twrp?
Ps: you need to delete your imeis in the first post..
Click to expand...
Click to collapse
yes once stuck on white screen with htc, I need to hold vol up+ power to turn it off and before it reboots automatically I open hboot by vol down+ power. from there I can continue in recovery mode and fastboot etc. no I haven't tried nandroid backup with twrp. I want to get stock rom so that I am able to get updates in future. plus I read twrp backup roms are havng problems like wifi and all.
That sounds like your bootsector is damaged, so usb debugging is disabled.
Did you back up your old recovery.img? The kit kat one before the update?
The easiest way, if you're able to flash a custom recovery, is a clean nandroid backup without root using twrp and once your device is booting again, start from scratch.
Enable usb debugging, unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
nukaru said:
That sounds like your bootsector is damaged, so usb debugging is disabled.
Did you back up your old recovery.img? The kit kat one before the update?
The easiest way, if you're able to flash a custom recovery, is a clean nandroid backup without root using twrp and once your device is booting again, start from scratch.
Enable usb debugging, unlock bootloader, flash stock recovery, relock bootloader and flash RUU.
Click to expand...
Click to collapse
no I havent backed up the KitKat factory image
I flashed the latest twrp recovery and booted to it. also I placed a twrp stock backup in sd card ( from one of the threads on this forum) . but when I proceed to backup from sd card, it doesn't appear there, however in the install option I can see the contents I placed..but again I m not getting an option to install it from there. guide me what to do next.
shubhamjswl said:
no I havent backed up the KitKat factory image
I flashed the latest twrp recovery and booted to it. also I placed a twrp stock backup in sd card ( from one of the threads on this forum) . but when I proceed to backup from sd card, it doesn't appear there, however in the install option I can see the contents I placed..but again I m not getting an option to install it from there. guide me what to do next.
Click to expand...
Click to collapse
guess wat!! my phone started and I am now getting ota also. thanks
That's great ? Remember to make your own backup and store it somewhere safe ?
Please provide me detailed steps on how to reinstall official stock rom on htc desire 816 dual sim indian version and also rom file
hi all, my phone is stuck on boot mode for weeks and i can't find a usable stock rom for my phone here are the details from fastboot
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.31.50.1215
version-cpld: None
version-microp: None
version-main:1.27.710.1
version-misc: PVT SHIP S-ON
serialno: FA47RMZ00345
imei: 352795062179097
imei2: 352795062179105
meid: A1000037D93FA6
product: a5_dwg
platform: hTCBmsm8226
modelid: 0P9C51000
cidnum: HTC__621
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: fba3c246
hbootpreupdate: 11
gencheckpt: 0

Categories

Resources