Develop Bugs

help with get back stock rom from custom rom

hi, i have this htc one x.
this is fastboot info (fastboot getvar all)
Code:
(bootloader) version: 0.5a
(bootloader) [COLOR="Red"]version-bootloader: 1.39.000[/COLOR]0
(bootloader) version-baseband: 5.1204.164.30H
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) [COLOR="Red"]version-main: 3.14.771.34[/COLOR]
(bootloader) serialno: HT23TW126661
(bootloader) imei: 359188042590570
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) [COLOR="Red"]cidnum: H3G__G04[/COLOR]
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) devpower: 100
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.826s
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?

hyber_99 said:
hi, i have this htc one x.
actually it has running cyanogen rom, but i wanna get back to stock rom.
as info, i haven't nandroid backup or anything else.
i have downloaded latest ruu from Hutchison, but i don't find exactly rom. H3G__G04 (H3G_SWE)
i have downloaded rom from H3G from UK. and i tried flash this rom, but i get bootloader error.
i almost forget it. i was locked bootloader to run RUU, and i have read many threads from forum.
anybody can help me to get back to stock rom please?
Click to expand...
Click to collapse
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.

1.- i dont know what is better, if 4+ or 5.
2.- in fact the phone was updated by other person, i don't know what he did :/
3.- let me flash ruu again and post bootloader error.
if it's usefull, it has Team Win Recovery Project v2.4.1.0 installed.
thanks for reply

genocide_ru said:
What sense version do you want in result: 4+ or 5?
Did you update your phone via OTA earlier?
Post bootloader error here, please. Looks like your bootloader is updated and do not match requirements to flash RUU from Hutchison.
Click to expand...
Click to collapse
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.

hyber_99 said:
Error 140, error with bootloader version.
and if i try with Europe RUU i got Error with Carrier ID.
Click to expand...
Click to collapse
Well, looks like firmware\hboot was updated and latest RUU for your CID requires older firmware\hboot.
So, you can't use old RUU to go back to stock.
You need to flash stock ROM for 1.39 hboot from recovery
Try to find ROM like this one, but older: http://forum.xda-developers.com/showthread.php?t=1546970&highlight=*stock*
I guess you need to search 3.18 or 3.20 version, don't remember wwich one will work with 1.39

ok, i'll search it.
thank you sir, i'll let you know the results.

one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Nand for H3G__106 - thanks to Jackster88
Part 1
Part 2
Quote:
Instructions:
***For this nand to work you need HBOOT 1.39 and cwm***
1) go into fastboot and enter "fastboot oem lock" - the device will reboot
2) go into fastboot again and enter "fastboot oem rebootRUU" - there will be a black screen with a silverish HTC logo
3) enter "fastboot flash zip firmware.zip" (you need the firmware.zip from page 1 for this)
3a) enter the same again, the green bar under the logo should go to 100% (either after the first or second time)
4) enter "fastboot reboot-bootloader" to go back to your fastboot
5) unlock your device again with the unlock code ("fastboot flash unlocktoken Unlock_code.bin")
6) Restore your old boot.img (fastboot flash boot name_of_boot_file.img) and recovery (fastboot flash recovery name_of_recovery_file.img), make sure you copied them from the nandroid backup folder we created earlier into the folder that contains the fastboot.exe you're using.
7) Reboot and you should now have Hboot 1.39 with your old boot and recovery.
(8) If it won't work we still have the backup ready to restore the old system, Hboot isn't changeable right now on S-ON devices outside of the RUU routine - so even if you restore your nandroid you should still have Hboot 1.39 now)
Confirmed working with H3G__001, H3G__003, H3g__G04
Click to expand...
Click to collapse

hyber_99 said:
one more question, can i use this method posted here? http://forum.xda-developers.com/showthread.php?t=1927048
exactly this:
Click to expand...
Click to collapse
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39

genocide_ru said:
yes, you can try this method
except, I guess you need not flash firmware, because you are already on 1.39
Click to expand...
Click to collapse
thank you very much.
after all i solve my problem installing RENOVATE Final 4 Rom ------ http://forum.xda-developers.com/showthread.php?t=1705334&highlight=3+20
after installing rom, we need flash kernel manually i flashed stock kernel.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time

hyber_99 said:
thank you very much.
my problem was that with cyanogen 10.1 this phone cann't accept unlocking code,
but now with renovate rom, code was accepted and phone now is sim unlocked
thank you very much for your time
Click to expand...
Click to collapse
No problem, man!
Glad I helped you with this :good:

[Q] Bootloop after failed attempt to Flash new Firmware

Dear Community
As I wanted to update my ROM to Android 5, but with working WiFi, i tried to flash a new firmware. I'm on S-ON. My HBOOT is 3.16. After relocking and booting to RUU-Mode I attempted to flash the firmware.zip (version 4.19.161.2) which leaded to failure with error code 42. My CID is VODAP110 (Swisscom). After this not working i rebooted to fastboot, unlocked the bootloader again, reflashed recovery (philZ-touch, latest version). I tried to reboot and ended in a bootloop. So I went to recovery and reflashed the OS (SlimKat 4.4.4, build 8). After rebooting i was still in bootloop. I tried already to flush the cache, but this didn't help either.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Also, here is my getvar all Dump:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****
(bootloader) imei: *****
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP110
(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.339s
Click to expand...
Click to collapse
Greetings,
Michael

ppcinj said:
Dear Community
As I wanted to update my ROM to Android 5, but with working WiFi, i tried to flash a new firmware. I'm on S-ON. My HBOOT is 3.16. After relocking and booting to RUU-Mode I attempted to flash the firmware.zip (version 4.19.161.2) which leaded to failure with error code 42. My CID is VODAP110 (Swisscom). After this not working i rebooted to fastboot, unlocked the bootloader again, reflashed recovery (philZ-touch, latest version). I tried to reboot and ended in a bootloop. So I went to recovery and reflashed the OS (SlimKat 4.4.4, build 8). After rebooting i was still in bootloop. I tried already to flush the cache, but this didn't help either.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Also, here is my getvar all Dump:
Greetings,
Michael
Click to expand...
Click to collapse
Delete the Serial Number and the IMEI.

UniversalKID said:
Delete the Serial Number and the IMEI.
Click to expand...
Click to collapse
Could you please point me to an tutorial how to do so?

ppcinj said:
Could you please point me to an tutorial how to do so?
Click to expand...
Click to collapse
He means from your first post - it's not wise to show the IMEI and serial number of your device as someone could clone your phone

EddyOS said:
He means from your first post - it's not wise to show the IMEI and serial number of your device as someone could clone your phone
Click to expand...
Click to collapse
Oh, ok, thanks for the correction

ppcinj said:
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.
Greetings,
Michael
Click to expand...
Click to collapse
What you need is a 2.xx.166.x 1.xx.166.x backup, but I don't have any idea on the full no.
So to have a working phone so you can make a phone call, temporarily just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup from this thread : http://forum.xda-developers.com/showthread.php?t=2701376
That's only a temp solution until you can find a right backup and firmware for your hboot 3.16.0000
If you want a Android for 5.0, you need firmware 4.19.166.2 which is available but I'm not sure whether you can jump from hboot 3.16.0000 directly to 3.19.0000

Jump should be fine, so long as it goes through without an error but I've gone from 3.16.0000 to 3.19.0000 having converted back from GPe to latest Lollipop RUU

EddyOS said:
Jump should be fine, so long as it goes through without an error but I've gone from 3.16.0000 to 3.19.0000 having converted back from GPe to latest Lollipop RUU
Click to expand...
Click to collapse
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.

ckpv5 said:
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
Click to expand...
Click to collapse
Yeah, good point.
It shouldn't be a problem going UP a version but going down won't work without S-OFF...

ckpv5 said:
I know it's ok for S-Off device, just not sure about S-On. Let's see what OP intend to do now.
Click to expand...
Click to collapse
Ok, but what exactly do I need now? Could you help me out finding the right file? I found backups for 2.x.161.x, but not for 2.x.166.x... And also what are the most secure steps for me to do now for avoiding a brick? Flashing the new 4.x.x.x so i can haz Android 5 or reverting to 2.x.x.x and stick with Android 4?
And also if you need some more data, screenshots, etc. feel free to ask for them

ppcinj said:
Ok, but what exactly do I need now? Could you help me out finding the right file? I found backups for 2.x.161.x, but not for 2.x.166.x... And also what are the most secure steps for me to do now for avoiding a brick? Flashing the new 4.x.x.x so i can haz Android 5 or reverting to 2.x.x.x and stick with Android 4?
And also if you need some more data, screenshots, etc. feel free to ask for them
Click to expand...
Click to collapse
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup

ckpv5 said:
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
Click to expand...
Click to collapse
Maybe this doesn't mean anything, but my OS is Version 4.4.4. (At least, this is what they say on the official Page & in Settings)

ppcinj said:
Maybe this doesn't mean anything, but my OS is Version 4.4.4. (At least, this is what they say on the official Page & in Settings)
Click to expand...
Click to collapse
I don't know anything when it comes to AOSP ROM requirement.
What I talked about here is to get your device up and running on Sense ROM.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.​Your fastboot getvar all tells that your original Sense OS is 4.4.2

ckpv5 said:
I wrote "just restore any of the 2.xx.xxx.x 1.xx.xxx.x backup" means any 2.xx.xxx.x 1.xx.xxx.x including the EU WWE... this just to get your device working again. But you're stuck at 4.4.2 for awhile. This is what at least you need for now as mentioned on post #1
Restoring a nandroid backup won't brick a device.
You can't install 4.xx.xxxx.x because hboot is too low version.
Damn ... just notice I gave you wrong info. hboot 3.16.0000 you can restore only 1.xx.xxx.x backup
Click to expand...
Click to collapse
I've tried now to restore the zip file... I used this one: 1.54.401.5 - CWM Philz touch. After restoration process I rebooted the system and then the Slimkat logo appeared again, and it's still in bootloop.:crying:
Edit: This is one problem i noticed already some time ago: I couldn't flash any other rom than slimkat since i flashed it the first time...
Edit2: Also After I flashed philz once I couldn't go back to twrp... THen it stuck in "Entering recovery" screen.
Sorry, i was an idiot, i didn't realise, that i need to extract the zip first -.-. I will try it again now.

ckpv5 said:
I don't know anything when it comes to AOSP ROM requirement.
What I talked about here is to get your device up and running on Sense ROM.
Anybody had this experience or knows what to do, for bring my phone back to working? It mustnt be Android 5, but just working, so I can make phone calls again.​Your fastboot getvar all tells that your original Sense OS is 4.4.2
Click to expand...
Click to collapse
Ok, im trying to restore now one of the downloaded Backups, however i can't manage to do so... It's always checking for img files, however it doesnt find them, and therefore doesn't restore them... Do I need to do anything special with the downloaded files?

ppcinj said:
Ok, im trying to restore now one of the downloaded Backups, however i can't manage to do so... It's always checking for img files, however it doesnt find them, and therefore doesn't restore them... Do I need to do anything special with the downloaded files?
Click to expand...
Click to collapse
I expect you know how to use a nandroid backup zip.
I want to help you but I'm not familiar with Philz recovery, only TWRP
The basic thing is, the nandroid backup zip to be extracted on PC. Then transfer the extracted the last folder that you see with its contents to recovery backup folder.
Also make sure the backup is meant for the right recovery.
What I read : philz --> Clockworkmod\Backups\
What I know : TWRP --> TWRP\BACKUPS\serialno\BackupFolderHere
For TWRP, simply make a nandroid backup of your boot, so you'll see the correct path then paste the nandroid folder that you extracted to this folder

ckpv5 said:
I expect you know how to use a nandroid backup zip.
I want to help you but I'm not familiar with Philz recovery, only TWRP
The basic thing is, the nandroid backup zip to be extracted on PC. Then transfer the extracted the last folder that you see with its contents to recovery backup folder.
Also make sure the backup is meant for the right recovery.
What I read : philz --> Clockworkmod\Backups\
What I know : TWRP --> TWRP\BACKUPS\serialno\BackupFolderHere
For TWRP, simply make a nandroid backup of your boot, so you'll see the correct path then paste the nandroid folder that you extracted to this folder
Click to expand...
Click to collapse
Ok, this worked for now and my Mobile is back in running state. Because of a strange feeling in my stomach i think that it's not possible now to simply download an OTA and get the new Android 5? What options do I have to get android 5?

ppcinj said:
Ok, this worked for now and my Mobile is back in running state. Because of a strange feeling in my stomach i think that it's not possible now to simply download an OTA and get the new Android 5? What options do I have to get android 5?
Click to expand...
Click to collapse
Not possible unless:
1. Use SunShine (paid service) to S-Off then you can flash other region ROM
or
2. Search/google around for a backup for your region device 1.xx.166.x (I have no idea the exact no.)
or
3. A risky one - flash your region 5.0 firmware 4.19.166.2 then install any 5.0 ROM .. I cannot guarantee this will work on hboot 3.16 as its a big jump from 3.16 to 3.19 .. you may brick your device.

ckpv5 said:
Not possible unless:
1. Use SunShine (paid service) to S-Off then you can flash other region ROM
or
2. Search/google around for a backup for your region device 1.xx.166.x (I have no idea the exact no.)
or
3. A risky one - flash your region 5.0 firmware 4.19.166.2 then install any 5.0 ROM .. I cannot guarantee this will work on hboot 3.16 as its a big jump from 3.16 to 3.19 .. you may brick your device.
Click to expand...
Click to collapse
You have written a second time 1.xx.166.x. Are you sure about this, and that it's not the .161 region?

ppcinj said:
You have written a second time 1.xx.166.x. Are you sure about this, and that it's not the .161 region?
Click to expand...
Click to collapse
Your fastboot getvar tells that :
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAP110​x.xx.166.x
modelid: 0P6B10000
cidnum: VODAP110
cidnum: VODAP120
mainver: 4.19.166.2
There is no CID VODAP110 in
x.xx.161.x
modelid: 0P6B10000
cidnum: VODAP001
cidnum: VODAP102
cidnum: VODAP405
cidnum: VODAPE17
cidnum: VODAPD18
cidnum: VODAP304
mainver: 2.22.161.6
Good luck ... got to rest now

[Q] HTC M8 Wifi problems on several Roms -HELP!

I was hoping someone could help me with a problem I have.
My htc M8 was rooted and insertcoin was flashed onto it however the wifi button greyed out and wouldnt turn on in order to s-off it. I tried several different roms and they all have the same problem. I am currently running skydragon v5. I have been trying to sort this phone out for a week and I am getting absolutely nowhere so any help would be appreciated. It's on ORANG001 and is s-on.
Thanks

You have old firmware. You need to have 4.19.61.2 on ORANG001 in order to have wifi on these ROM.
And you post this in wrong section.

ckpv5 said:
You have old firmware. You need to have 4.19.61.2 on ORANG001 in order to have wifi on these ROM.
And you post this in wrong section.
Click to expand...
Click to collapse
Apologies, new to the forum it's been moved now!

Yeah .. requested it to be moved to correct section.
So .. you need to restore your stock ROM and do OTA up to 4.19.61.2
What's your current firmware version .. 3.33.61.9 or 2.26.61.1 ? Or even lower ?
Check what's written on bootloader - hboot 3.16 or 3.18 .. you need 3.19

ckpv5 said:
Yeah .. requested it to be moved to correct section.
So .. you need to restore your stock ROM and do OTA up to 4.19.61.2
What's your current firmware version .. 3.33.61.9 or 2.26.61.1 ? Or even lower ?
Check what's written on bootloader - hboot 3.16 or 3.18 .. you need 3.19
Click to expand...
Click to collapse
Hboot is 3.16.0.0000
The phone is currently in the bootloader and I can't get it to turn on to check the firmware version.
Ran getvar all does this help ? thanks for the help, I was stuck for over a week.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************
(bootloader) imei: ************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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.206s

That's a very low version ... you need to restore to stock backup 1.54.61.5
But I deleted my TWRP backup for most 1.xx.xxx.x only keep 2.x; 3x & 4x
There is someone else backup made with Philz recovery so you need to download Philz recovery - http://forum.xda-developers.com/showthread.php?t=2703223
then download the backup : https://mega.co.nz/#!WhwRmSoJ!QJxmI0gYj7t_0Hc4fMKx0XLYQ2n45S3OfrEcDRS3C-s
restore that backup with the stock recovery (included in that backup if I'm not wrong)
then do multiple OTA

ckpv5 said:
That's a very low version ... you need to restore to stock backup 1.54.61.5
But I deleted my TWRP backup for most 1.xx.xxx.x only keep 2.x; 3x & 4x
There is someone else backup made with Philz recovery so you need to download Philz recovery - http://forum.xda-developers.com/showthread.php?t=2703223
then download the backup : https://mega.co.nz/#!WhwRmSoJ!QJxmI0gYj7t_0Hc4fMKx0XLYQ2n45S3OfrEcDRS3C-s
restore that backup with the stock recovery (included in that backup if I'm not wrong)
then do multiple OTA
Click to expand...
Click to collapse
I have Philz Touch 6.26.6 clockwork mod v6.0.4.8
Will this be okay or do i need to install a different one ? sorry if these questions are stupid.

Should be ok ... good luck
I'll check your progress tomorrow or maybe someone will help you later.
Time to sleep ... good night

ckpv5 said:
Should be ok ... good luck
I'll check your progress tomorrow or maybe someone will help you later.
Time to sleep ... good night
Click to expand...
Click to collapse
Okay cheers for your help!

I was trying to adb push the firmware to my phone to then install it on Recovery but when im typing "adb devices" it says list of devices attached then it is blank. I have been trying to search for solutions but I cant seem to fix it. If you have any advice it would be much appreciated. Thanks

Has anyone got an idea?

paulmcclafferty said:
I was trying to adb push the firmware to my phone to then install it on Recovery but when im typing "adb devices" it says list of devices attached then it is blank. I have been trying to search for solutions but I cant seem to fix it. If you have any advice it would be much appreciated. Thanks
Click to expand...
Click to collapse
This is usually an issue on the computer's side (PC?). Try to re-install HTC drivers, try another USB port, or another cable. Also, if you have USB 3.0, this is known to cause issues with adb connectivity (apparently, you can disable this).
Also, you need to be booted into OS or in recovery for adb to work (does not work in bootloader) and you need to have USB debugging activated in Settings.
And when you say "firmware" I think you mean a nandroid backup, based on the instructions previously given to you? Be careful using the term "firmware" here, as most folks use that term to specifically mean the firmware.zip that contains hboot, radio etc. (but not ROM).

paulmcclafferty said:
I was trying to adb push the firmware to my phone to then install it on Recovery but when im typing "adb devices" it says list of devices attached then it is blank. I have been trying to search for solutions but I cant seem to fix it. If you have any advice it would be much appreciated. Thanks
Click to expand...
Click to collapse
Don't you have a MicroSD ? Put the extracted nandroid on MicroSD at the right location clockworkmod\backups\ is easier than doing that ADB push.

Okay finally got the nandroid backup installed. Then when i tried to install the OTA update it took me to CWM and failed. So i then relocked and tried again to update OTA and it took me to the bootloader with a ***Relocked*** and *** Security Warning*** any ideas ?

You need to re-install the stock recovery in order to OTA. Bootloader lock has nothing to do with it (will OTA with unlocked bootloader).

redpoint73 said:
You need to re-install the stock recovery in order to OTA. Bootloader lock has nothing to do with it (will OTA with unlocked bootloader).
Click to expand...
Click to collapse
I have installed the Nandroid backup mentioned above to stock i believe. Is this the correct step or is this still not stock ? it was 1.54.61.5
Thanks

paulmcclafferty said:
I have installed the Nandroid backup mentioned above to stock i believe. Is this the correct step or is this still not stock ? it was 1.54.61.5
Thanks
Click to expand...
Click to collapse
Stock ROM backup and stock recovery are two different things.
You need to fastboot flash recovery recovery.img to replace the CWM that you have now. Inside the backup zip, there is a recovery.img .. take this out and fastboot flash it.
You need to unlock bootloader to flash it.

when using the command "fastboot flash recovery recovery.img" using the recovery.img from the unzipped nandroid folder the process runs and it says okay with no errors then when i try go into recovery the red triangle and exclamation mark appear again

paulmcclafferty said:
when using the command "fastboot flash recovery recovery.img" using the recovery.img from the unzipped nandroid folder the process runs and it says okay with no errors then when i try go into recovery the red triangle and exclamation mark appear again
Click to expand...
Click to collapse
Yes that's stock recovery. Perform the ota now

Because that is stock recovery. You don't need to get into recovery.
Just reboot, check OTA, download then select install.
Let the system do the installation on its own

HTC ONE M8 stuck in bootloop

Hey guys
I know there are similar posts out there but none who describe my exact problem^^
It's like this: Earlier today, I wanted to go back to stock, fully. Which means I downloaded the stock backup and put it on my phone with TWRP. Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
As far, as good, everything worked just fine. And to have it completely back to stock (except for the still unlocked bootloader) I came up with the glorious idea of restoring to factory settings using the options in the phone's settings... aaaand now I'm stuck in the bootloop.
I meanwhile figured out how to enter the bootloader (volume up + power til screen turns fully black, then volume down) and I'm also able to access stock recovery through that... I of course tried factory resetting it through the bootloader and the recovery, I also took the sim card out as somewhere was suggested... but ultimately, it always goes back to the bootloop.
When connecting to the PC I hear the connecting sound... but that's it. It doesn't show up and thus I also can't access it through fastboot/adb
I ran out of ideas myself, do you have any?^^
Thanks!

M4C00kie said:
Then, I changed to stock recovery by using the HTC ONE M8 toolkit from hasoon2000.
Click to expand...
Click to collapse
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
M4C00kie said:
I also can't access it through fastboot/adb
Click to expand...
Click to collapse
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
adb requires being in OS or recovery (and I'm not sure if stock recovery supports adb). And for the most part, fastboot is what you need to recover.
Need more info to help further. What CID version of the phone? If OS version number is shown on hboot screen, post it here. What are the version numbers or the stock nandroid, and the stock recovery you installed? If you can get fastboot work, do fastboot getvar all, and post the output.

redpoint73 said:
Why you would you the toolkit for that? The toolkit is woefully obsolete (hasn't been updated in over a year, going on 2 years) and therefore causes more problems than it solves. Flashing stock recovery is really easy, its a single fastboot command. Don't over-complicate it.
Click to expand...
Click to collapse
That's because I was using an older guide... good to know^^
redpoint73 said:
Are you sure you are in bootloader-fastboot mode when you try fastboot commands (this is required)?
Click to expand...
Click to collapse
That's what's strange... on the phone, it's showing FASTBOOT USB and it even makes this sound when connecting... fastboot commands still don't work though: "error: device not found"
the CID number is HTC__102, he version number of the stock nandroid and recovery was 4.16.401.10
regarding the OS number: on the hboot screen there's just written OS- <- is this the place where it's supposed to be?
thanks a lot for helping!

OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
C:\Users\aaron_000\fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.000
(bootloader) version-baseband: 1.25.2145000
(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: HTC__102
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
my version & radio number are matching the ones in this RUU
so...
what now?^^ before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
oh, and would doing this even help in my current situation?
Thanks for helping

M4C00kie said:
OK. fastboot commands ARE working (adb aren't, as predicted by you^^)
Click to expand...
Click to collapse
Did you do anything different to get it working?
M4C00kie said:
Update: as it was suggested to me on another thread, I downloaded an RUU (https://www.androidfilehost.com/?w=f...4a4f68918d8199)
Click to expand...
Click to collapse
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
M4C00kie said:
before I flash the RUU, I have to relock my bootloader, have I? and is this possible with S-ON?
Click to expand...
Click to collapse
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
M4C00kie said:
oh, and would doing this even help in my current situation?
Click to expand...
Click to collapse
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!

redpoint73 said:
Did you do anything different to get it working?
Click to expand...
Click to collapse
I might have confused adb and fastboot... pretty sure it was working all along
redpoint73 said:
Does this mean you are hopping around in other threads? Or you just read it elsewhere?
Click to expand...
Click to collapse
I initially posted this on another forum... realised too late that this one here was more appropriate and posted it here xD
redpoint73 said:
The above is not linking me to any specific file. Might be the same link as the on the following thread:
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
redpoint73 said:
Relocking the bootloader is not just possible with s-on, its an absolute requirement to RUU.
Simple fastboot command: fastboot oem lock
Click to expand...
Click to collapse
done.
redpoint73 said:
Most likely, yet. I'd say almost certainly.
Also, you should delete your IMEI and serial number from your getvar info, as these are personal data. I should have mentioned that, but I didn't know you'd get fastboot working so quickly!
Click to expand...
Click to collapse
deleted it. thanks for all your help so far!

M4C00kie said:
fixed, should link to the correct one now... have a look again
(this is it: https://www.androidfilehost.com/?w=...c00ca09c7539be86640965d7bb19a1ad4a4f68918d819)
Click to expand...
Click to collapse
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.

redpoint73 said:
File name looks right. But can't personally vouch for the particular link or source. but it has plenty of downloads, so you should be fine.
Click to expand...
Click to collapse
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ or should I rather download a zip version of it?

M4C00kie said:
question: the exe file tells me to turn on my phone... is bootloader considered turning on?^^ ?
Click to expand...
Click to collapse
As long as "fastboot" is selected in bootloader it will work.

redpoint73 said:
As long as "fastboot" is selected in bootloader it will work.
Click to expand...
Click to collapse
it worked!!
never heard a sweeter sound before than the HTC boot sound^^
thank you so much for all your help!

HTC One M8 stuck in fastboot screen since loading CWM Recovery Image

Hi, I attempted to root my phone for the first time following these instructions, which have the HTCDev.com unlocking bootloader instructions as part of them.
Output of "fastboot getvar all" is below
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0​
I did make a mistake, I loaded both the below images in the given order.
openrecovery-twrp-2.7.0.2-m8.img
philz_touch_6.26.6-m8.img
When I went into recovery I got philz touch and loaded the UPDATE-SuperSU-v2.37.zip that was instructed. However I am got stuck in permanent reboot.
I followed the instructions in this thread up until post #6, but I don't understand how to "reflash my custom recovery". I am currently on the fasboot screen after having successfully run "fastboot flash zip firmware-2.22.531.5.zip".
Is this removing the philz touch image? How is this done?
Or more what I'm after, how do I get to a rooted phone from here which is usable?
Thank you in advance for any help given!

The chosen SuperSu is way too old. I never used Philz Touch but even TWRP you loaded is way too old as well.
Flash the latest TWRP and the latest SuperSu or magisk and you're good to go.
And please remove your imei and serial no.

maultasche said:
The chosen SuperSu is way too old. I never used Philz Touch but even TWRP you loaded is way too old as well.
Flash the latest TWRP and the latest SuperSu or magisk and you're good to go.
And please remove your imei and serial no.
Click to expand...
Click to collapse
Many thanks!
Can I just clarify what flashing the latest TWRP and the latest SuperSU means? I'm running on windows, which fastboot instruction(s) in cmd do I need to run? (Sorry, I am very new to this.)

MonkeyBrains7532 said:
I followed the instructions in this thread up until post #6, but I don't understand how to "reflash my custom recovery". I am currently on the fasboot screen after having successfully run "fastboot flash zip firmware-2.22.531.5.zip".
Click to expand...
Click to collapse
Hold on, I missed this part. Why would you even flash this zip? I don't even know what that is. I'm not even sure this zip was intended for your phone. Flashing zips which are not for your device model could brick the phone.
The latest TWRP can be found here:
https://dl.twrp.me/m8/
Latest SuperSu:
https://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703

maultasche said:
Hold on, I missed this part. Why would you even flash this zip? I don't even know what that is. I'm not even sure this zip was intended for your phone
Click to expand...
Click to collapse
I thought it was resetting firware... Is there a way to remove this? "flashboot flash zip <some_correct_firmware>"?
Check out the link to the other thread, as I did (niavely) follow the instructions given.

MonkeyBrains7532 said:
I thought it was resetting firware... Is there a way to remove this? "flashboot flash zip <some_correct_firmware>"?
Check out the link to the other thread, as I did (niavely) follow the instructions given.
Click to expand...
Click to collapse
I did. Your phone is an orange one, you flashed old firmware which was meant for a t-mobile phone. Flashing random zips which are not meant for your phone could brick the device.

maultasche said:
I did. Your phone is an orange one, you flashed old firmware which was meant for a t-mobile phone. Flashing random zips which are not meant for your phone could brick the device.
Click to expand...
Click to collapse
Right, okay... Assuming it's not beyond all hope, would flashing the correct firmware possibly resolve this?
If so, where would I need to go to get the latest correct firmware for my carrier?
I can see some options on the HTC website ROM downloads, but nothing for Orange. I thought I was T-Mobile as I got the phone from EE...

MonkeyBrains7532 said:
Right, okay... Assuming it's not beyond all hope, would flashing the correct firmware possibly resolve this?
If so, where would I need to go to get the latest correct firmware for my carrier?
I can see some options on the HTC website ROM downloads, but nothing for Orange. I thought I was T-Mobile as I got the phone from EE...
Click to expand...
Click to collapse
The site only posts RUU for US phones.
Is the phone really in a bootloop or just stuck at the boot screen?
There is hope for you. Since you want to root as well we'll go this way:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Download the TWRP backup from post #3. It's the first one there for your device. After you downloaded the backup, flash the latest TWRP which I linked earlier. Boot into TWRP and restore the backup. If the phone is not booting then follow instructions in post #5 to flash firmware.
But before you go and restore a backup try to flash firmware as mentioned in post #5. You need to relock bootloader though.

maultasche said:
The site only posts RUU for US phones.
Is the phone really in a bootloop or just stuck at the boot screen?
There is hope for you. Since you want to root as well we'll go this way:
https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Download the TWRP backup from post #3. It's the first one there for your device. After you downloaded the backup, flash the latest TWRP which I linked earlier. Boot into TWRP and restore the backup. If the phone is not booting then follow instructions in post #5 to flash firmware
Click to expand...
Click to collapse
It was originally just on the White with green "HTC" text boot screen. I'm now in fastboot.
So I have downloaded the following.
SuperSU-v2.82-201705271822.zip
twrp-3.1.1-0-m8.img
I also downloaded the below (on the mega-nz.com link).
hboot 3.19.0000 - 6.xx.xxx.x (Marshmallow)
CID ORANG001
MID 0P6B10000
6.12.61.4​
as well as the below from post #5
CID ORANG001
MID 0P6B10000
fw_6.12.61.4​
I attempted to flash the TWRP, but got "'flashboot' is not recognized as an internal or external command". I am still in the directory where I downloaded flashboot and this is a new error..
I then started on the instructions in post #5, all the way up to "fastboot flash zip fw_6.12.61.4.zip" but I get the same "...not recognized..." error. My phone is now on a screen similar to fastboot, but there is just the one option, "RUU". It was on a black screen with "HTC" in the middle a moment ago when I was trying to flash the zip.

@MonkeyBrains7532
What do you mean with flashboot? Or is this just a typo? There is no flashboot command. The basic idea is:
fastboot flash recovery NameOfRecovery.img
You can also only boot into TWRP with fastboot boot NameOfRecovery.img
If you want to try to flash only the firmware first you need to lock bootloader first. I'm not quite sure if you should be on stock recovery for that. You can flash that one as well with the mentioned command

maultasche said:
@MonkeyBrains7532
What do you mean with flashboot? Or is this just a typo? There is no flashboot command. The basic idea is:
fastboot flash recovery NameOfRecovery.img
You can also only boot into TWRP with fastboot boot NameOfRecovery.img
If you want to try to flash only the firmware first you need to lock bootloader first. I'm not quite sure if you should be on stock recovery for that. You can flash that one as well with the mentioned command
Click to expand...
Click to collapse
Oh lord that was a typo, okay starting the instructions again. Sorry for the dumb mistake.

MonkeyBrains7532 said:
Oh lord that was a typo, okay starting the instructions again. Sorry for the dumb mistake.
Click to expand...
Click to collapse
Don't worry. I've been through the same once

maultasche said:
Don't worry. I've been through the same once
Click to expand...
Click to collapse
Thanks
So I continued off where I left, firstly by putting the phone in flashboot mode then repeating step 4 on post #5.
However, when I ran "fastboot oem rebootRUU" in cmd it just sat on "<waiting for device>" until I killed the command.
Is this just a question of leave it alone for a little while?

MonkeyBrains7532 said:
Thanks
So I continued off where I left, firstly by putting the phone in flashboot mode then repeating step 4 on post #5.
However, when I ran "fastboot oem rebootRUU" in cmd it just sat on "<waiting for device>" until I killed the command.
Is this just a question of leave it alone for a little while?
Click to expand...
Click to collapse
Was USB debugging enabled on your phone? Seems like it wasn't. Does it say in hboot fastboot USB?

maultasche said:
Was USB debugging enabled on your phone? Seems like it wasn't. Does it say in hboot fastboot USB?
Click to expand...
Click to collapse
I thought I had when I first got into the dev options, I may well be misremembering. It just says hboot fastboot...

MonkeyBrains7532 said:
I thought I had when I first got into the dev options, I may well be misremembering. It just says hboot fastboot...
Click to expand...
Click to collapse
Well then it's not working. It either should say fastboot USB or fastboot AC. It's been a while as I've done that, so I'm not 100% sure what it should say. So you need to go the route with twrp backup instead. Can you at least flash or boot twrp?

maultasche said:
Well then it's not working. It either should say fastboot USB or fastboot AC. It's been a while as I've done that, so I'm not 100% sure what it should say. So you need to go the route with twrp backup instead. Can you at least flash or boot twrp?
Click to expand...
Click to collapse
I am getting "waiting for device" when I run either "fastboot boot twrp-3.1.1-0-m8.img" or "fastboot flash recovery twrp-3.1.1-0-m8.img".

MonkeyBrains7532 said:
I am getting "waiting for device" when I run either "fastboot boot twrp-3.1.1-0-m8.img" or "fastboot flash recovery twrp-3.1.1-0-m8.img".
Click to expand...
Click to collapse
Do you have philztouch still on your phone?

maultasche said:
Do you have philztouch still on your phone?
Click to expand...
Click to collapse
I should do. Next step, go to recovery?
Fyi, I scrolled down in Fastboot and the menu name changed to Fastboot USB. Tried booting and flashing again, but still waiting for device. I don't know if this new information changes anything.

MonkeyBrains7532 said:
I should do. Next step, go to recovery?
Fyi, I scrolled down in Fastboot and the menu name changed to Fastboot USB. Tried booting and flashing again, but still waiting for device. I don't know if this new information changes anything.
Click to expand...
Click to collapse
Yes, boot into Philz and try to find out if the recovery can flash .img files
Never used it so I don't know :/