[Q] Bootloop after failed attempt to Flash new Firmware - One (M8) Q&A, Help & Troubleshooting

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

Related

[Problem] With Unroot, OTA update and Version-main not showing

First of all , Hi everyone ! And please excuse my english, it's not my native language... (wich is French)
I did not want to brick my HTC One (m8) so i went here before to do something wrong.
I received my phone the first august and I rooted it 5 days ago, when it was in kitkat 4.4.2. I did not know that i had to update it to 4.4.3 (even if every man in earth should use his brain and do the update) before to root it.... (because now i can't install custom rom to use link2sd efficiently because all of the best custom rom (that actually use .ext partition on Micro Sd card) are in android kitkat 4.4.3 or 4.4.4)
I know that this question has been asked several times but i did not find the answer for my problem, so i'm really sorry to ask this but i have to.
Okay I rooted my htc when it was in 4.4.2 with TheUnlockr methode on youtube and since then the only things that I did is :
install busybox (twrp) , es explorateur, titanium backup, diskdigger,airdroid,apptoide,root checker, lucky patcher and clean master, NOTHING else.
Now i have to unroot my HTC to finally update it to 4.4.3
Problem is : when i do "getvar all" with hasoon200's toolkit (i'm following TheUnlockr's method to unroot the phone correctly), the field where i should find my version-main is EMPTY, and I absolutly don't know how to find it since I'm a total beginner on android.
My info : HTC ONE (m8)
Rooted with kitkat 4.4.2 (TWRP recovery)
actual software in : 1.54.401.10
cidnum: HTC__203
By any chance , can anyone help me ? THX 3000 times in advance since i'm totally lost !
That NOTHING else appears to include installing TWRP 2.7.1.x, which is where the problem lies, I don't know how to get it back, other than to reflash the firmware... Catch 22 if you don't know what it is.
Perhaps narrow down with a search of MID, CID and radio version.
Sorry man i did not understand
Here is what i have got when I do a getvar :
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH443WM13877
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.005s
Howard X said:
Sorry man i did not understand
Here is what i have got when I do a getvar :
...
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
...
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__203
Click to expand...
Click to collapse
FIRST: you should delete your IMEI from your post above!
Second: it is a known issue with TWRP that, after installing it version-main is no longer shown in bootloader, as already statet in this thread.
If what you wrote is correct you are on 4.4.2 with FW 1.54.401.10.
To unroot you could search for the unsupersu.zip and install it with TWRP.
After this you can download stock recovery 1.54.401.10 (assuming you data is correct and you are on the given Android version. This should enable you to receive AND install OTAs again.
The problem is, that without S-Off it is not that easy to flash the actuall FW again.
HTCNerdYoda said:
FIRST: you should delete your IMEI from your post above!
Second: it is a known issue with TWRP that, after installing it version-main is no longer shown in bootloader, as already statet in this thread.
If what you wrote is correct you are on 4.4.2 with FW 1.54.401.10.
To unroot you could search for the unsupersu.zip and install it with TWRP.
After this you can download stock recovery 1.54.401.10 (assuming you data is correct and you are on the given Android version. This should enable you to receive AND install OTAs again.
The problem is, that without S-Off it is not that easy to flash the actuall FW again.
Click to expand...
Click to collapse
Okay i managed to S-OFF.
Do i follow the Unlocker way now or do I just use the unsuperuser from X site ?
Is it sure that i have to download the 1.54.401.10 stock firmware ? cause noone of these are with the htc_203
Thx verrry much in advance guys !
Howard X said:
Okay i managed to S-OFF.
Do i follow the Unlocker way now or do I just use the unsuperuser from X site ?
Is it sure that i have to download the 1.54.401.10 stock firmware ? cause noone of these are with the htc_203
Thx verrry much in advance guys !
Click to expand...
Click to collapse
Ok you are S-Off and got 4.4.2 with ROM version 1.54.401.10 installed right!?
If so install the unsupersu.zip in TWRP and download firmware for ROM version 1.54.401.10. After you installed the unsupersu.zip reboot to bootloader and run the following commands:
fastboot oem rebootRUU
fastboot flash zip nameoffirmware.zip
DO IT AGAIN TO FLASH IT CORRECTLY!!!
fastboot flash nameoffirnware.zip
fastboot reboot-bootloader
Make sure OS is showing in Hboot. HBoot should be 3.16 and radio 1.16 if I remember correctly.
Congrats you are back to full stock. Reboot phone and check for OTA.
Sent from my HTC One_M8 using XDA Free mobile app
The bug within TWRP has been identified, a fix has been submitted to the Gerrit of TWRP and it was also already verified and accepted.
The Next update of TWRP for the M7 and M8 should include it, if it's being build from the main tree.
mobile post
Howard X said:
First of all , Hi everyone ! And please excuse my english, it's not my native language... (wich is French)
I did not want to brick my HTC One (m8) so i went here before to do something wrong.
I received my phone the first august and I rooted it 5 days ago, when it was in kitkat 4.4.2. I did not know that i had to update it to 4.4.3 (even if every man in earth should use his brain and do the update) before to root it.... (because now i can't install custom rom to use link2sd efficiently
By any chance , can anyone help me ? THX 3000 times in advance since i'm totally lost !
Click to expand...
Click to collapse
Hello OP
Here is the Thread that talks about why the Version-main / OS is blank in HBOOT mode aka (Bootloader)
http://forum.xda-developers.com/showpost.php?p=53733669&postcount=1592
Thanks
jcbjoe said:
Hello OP
Here is the Thread that talks about why the Version-main / OS is blank in HBOOT mode aka (Bootloader)
http://forum.xda-developers.com/showpost.php?p=53733669&postcount=1592
Thanks
Click to expand...
Click to collapse
Hi guys I have almost the same problem
I had a custom recovery an Unlocked bootloader
But with CMD i flashed the stock recovery and relocked my phone to get the 4.4.4 update But I still has this message : There is no update available on your phone!
My software number is: 2.22.401.2
Any solution please :victory:
I called HTC support and they saied that my phone rooted ist and it still dont become any update more !!!
AnJo_Droid said:
Hi guys I have almost the same problem
I had a custom recovery an Unlocked bootloader
But with CMD i flashed the stock recovery and relocked my phone to get the 4.4.4 update But I still has this message : There is no update available on your phone!
My software number is: 2.22.401.2
Any solution please :victory:
I called HTC support and they saied that my phone rooted ist and it still dont become any update more !!!
Click to expand...
Click to collapse
This isn't even a similar issue as the OP, and this thread is 2 months old. Really shouldn't have dug up this old thread and posted to it. A different thread, or starting your own would have been more relevant.
Rooted phones still get the OTA notfication and download, they just won't install if it detects any system files have been modified.
Also, relocking the bootloader is not necessary to get the OTA or install.
Something else is going on. If you are stock ROM and stock reocvery, thre is no reason you shouldn't get and be able to install the OTA. Sometimes a factory reset will prompt the OTA to come through, for no explicable reason.
redpoint73 said:
This isn't even a similar issue as the OP, and this thread is 2 months old. Really shouldn't have dug up this old thread and posted to it. A different thread, or starting your own would have been more relevant.
Rooted phones still get the OTA notfication and download, they just won't install if it detects any system files have been modified.
Also, relocking the bootloader is not necessary to get the OTA or install.
Something else is going on. If you are stock ROM and stock reocvery, thre is no reason you shouldn't get and be able to install the OTA. Sometimes a factory reset will prompt the OTA to come through, for no explicable reason.
Click to expand...
Click to collapse
Ok thanks, I have already reset my phone to factory via stock recovery and I have no root and stock recovery & Rom .. so I should wait to become it
I live in germany and maybe its not available in my region ?
And sorry about posting here but I need an quick answer:fingers-crossed:
AnJo_Droid said:
Ok thanks, I have already reset my phone to factory via stock recovery and I have no root and stock recovery & Rom .. so I should wait to become it
I live in germany and maybe its not available in my region ?
Click to expand...
Click to collapse
You should check around the forums to see if your specific version has had 4.4.4 rolled out. But I know most (if not all) Euro versions have been updated by now.
AnJo_Droid said:
And sorry about posting here but I need an quick answer
Click to expand...
Click to collapse
Your issue is no more urgent than anyone else here, that takes the time to post to an appropriate thread.
Seeking quick answers and not researching anything will always lead to more issues and maybe serious ones.
Read, learn, read.... Then do. That's the XDA spirit.
If anyone has no time for that.... Then this hobby may not be for you. ?
This has been a public service announcement.

[Q] Get back to stock M8 VODAP110 - Having massive problems

Good morning guys.
I am wondering if anyone is able to help me before i go completely nuts trying to work this out. (I also hope its ok to make a new thread)
A few weeks ago i rooted my M8 following the steps on this website (htconeroot. - how-to-root-htc-one-m8/) with no issues at all. Unlocked the boot loader and also there is the software tag saying modified (my understanding is this is normal). Installed the custom recovery with no drama.
A couple of days ago i got the OTA notification that i can now download 5.0.1 (Happy days) however this is where i seem to be running into problems. I know that i need to revert to the stock recovery from TWRP and then from here need to relock the boot loader to install the OTA update. I think my main problem is that i don't know what version of the stock rom i need to install. I have tried a few but none of them will boot into recovery from the boot loader.
So this is where i am.
Boot loader works fine and will run fast boot and boot to custom recovery - does state that the OS - (Blank)
Davids-MBP:mfastboot-v2 Raynor$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxx
(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: 26b322e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
I have a swisscom locked phone (VODAP110) the software version is (3.29.166.9 from phone) however the main-version is blank, another website said i need a stock recovery (x.xx.166.x - Vodafone CH-DE (Switzerland - Germany))
The last stock recovery that i put on the phone was (3.29.161.5 recovery.img) this then would allow me to start the phone and run the OTA update. From here the phone will restart and start the update but after about 20/25% the phone will crash displaying a picture of the phone with a red triangle and upside down exclamation mark. I read somewhere that if this problem happens to erase the cache and it should fix the problem but it didn't.
Could anyone please point me in the correct direction or help me solve the problem i am having.
Do i need to ?????
1) install the correct stock recovery (if so could someone please help me find the correct version)
2) Flash the stock rom from HTCDev (no clue how to do this with fast boot and if it will restore the recovery)
3) Give up on OTA and look for a custom 5.0.1 flash and use TWRP to flash from recovery.
Thanks so much for any help.
raynordg said:
Good morning guys.
I am wondering if anyone is able to help me before i go completely nuts trying to work this out. (I also hope its ok to make a new thread)
A few weeks ago i rooted my M8 following the steps on this website (htconeroot. - how-to-root-htc-one-m8/) with no issues at all. Unlocked the boot loader and also there is the software tag saying modified (my understanding is this is normal). Installed the custom recovery with no drama.
A couple of days ago i got the OTA notification that i can now download 5.0.1 (Happy days) however this is where i seem to be running into problems. I know that i need to revert to the stock recovery from TWRP and then from here need to relock the boot loader to install the OTA update. I think my main problem is that i don't know what version of the stock rom i need to install. I have tried a few but none of them will boot into recovery from the boot loader.
So this is where i am.
Boot loader works fine and will run fast boot and boot to custom recovery - does state that the OS - (Blank)
Davids-MBP:mfastboot-v2 Raynor$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT43NWM12442
(bootloader) imei: xxxxxxxxxxxx
(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: 26b322e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.007s
I have a swisscom locked phone (VODAP110) the software version is (3.29.166.9 from phone) however the main-version is blank, another website said i need a stock recovery (x.xx.166.x - Vodafone CH-DE (Switzerland - Germany))
The last stock recovery that i put on the phone was (3.29.161.5 recovery.img) this then would allow me to start the phone and run the OTA update. From here the phone will restart and start the update but after about 20/25% the phone will crash displaying a picture of the phone with a red triangle and upside down exclamation mark. I read somewhere that if this problem happens to erase the cache and it should fix the problem but it didn't.
Could anyone please point me in the correct direction or help me solve the problem i am having.
Do i need to ?????
1) install the correct stock recovery (if so could someone please help me find the correct version)
2) Flash the stock rom from HTCDev (no clue how to do this with fast boot and if it will restore the recovery)
3) Give up on OTA and look for a custom 5.0.1 flash and use TWRP to flash from recovery.
Thanks so much for any help.
Click to expand...
Click to collapse
Maybe this one works? This is the 3.29.161.9 recovery. It's from my VODAPE17 cid
1: download the ota, take out the firmware.zip and in that zip is a recovery.img. that is your correct stock recovery that you need.
2: go to the general section - collection of backups and firmwares. Have a read there and look for your cid in the list with backups.
Please do not relock the bootloader that is not needed for an ota !
And delete your serial !
I was forgotten to paste the url: https://mega.co.nz/#!nZkCWZAL!djqZnzAlVfHslzWJxUxvW5cLKHdI9BIhr_uxzjFxbng
I also have this Problem with my M8 (3.29.166.9). I also flashed the new recovery from the OTA, but when i flashed the OTA, the recovery wrote Status 7 error ...
New download of the OTA doesn't worked..
Any Idea ?
Sorted
Petert87 said:
Maybe this one works? This is the 3.29.161.9 recovery. It's from my VODAPE17 cid
Click to expand...
Click to collapse
Hi Petert87 tried this one the other day but it didn't work for me.
Mr Hofs said:
1: download the ota, take out the firmware.zip and in that zip is a recovery.img. that is your correct stock recovery that you need.
2: go to the general section - collection of backups and firmwares. Have a read there and look for your cid in the list with backups.
Please do not relock the bootloader that is not needed for an ota !
And delete your serial !
Click to expand...
Click to collapse
Mr Hofs, You absolute legend. This was a very quick fix (No. 1) back up and running now.
onkel_Andi said:
I also have this Problem with my M8 (3.29.166.9). I also flashed the new recovery from the OTA, but when i flashed the OTA, the recovery wrote Status 7 error ...
New download of the OTA doesn't worked..
Any Idea ?
Click to expand...
Click to collapse
Hi onkel.
the process i went through was as follows.
1) force download the OTA from swisscom and copy off to computer.
2) do what Mr Hofs said above and extract the ROM and dig out the recovery.img
3) reset with fast boot - (fastboot reboot-bootloader)
4) flash recovery (fastboot flash recovery recovery.img
5) fastboot erase cache
6) fastboot reboot
7) install OTA from within booted OS
8) wait.......
Thanks for taking the time to read through my problem guys.
@Mr Hofs if you would like the OTA update or recovery.mg please let me know.
raynordg said:
Hi Petert87 tried this one the other day but it didn't work for me.
Mr Hofs, You absolute legend. This was a very quick fix (No. 1) back up and running now.
Hi onkel.
the process i went through was as follows.
1) force download the OTA from swisscom and copy off to computer.
2) do what Mr Hofs said above and extract the ROM and dig out the recovery.img
3) reset with fast boot - (fastboot reboot-bootloader)
4) flash recovery (fastboot flash recovery recovery.img
5) fastboot erase cache
6) fastboot reboot
7) install OTA from within booted OS
8) wait.......
Thanks for taking the time to read through my problem guys.
@Mr Hofs if you would like the OTA update or recovery.mg please let me know.
Click to expand...
Click to collapse
Nice mate, @Mr Hofs is a real master
Maybe you can upload the OTA, firmware and recovery on mega.co.nz and post the links here: http://forum.xda-developers.com/showthread.php?t=2701376
Petert87 said:
Nice mate, @Mr Hofs is a real master
Maybe you can upload the OTA, firmware and recovery on mega.co.nz and post the links here: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
+1 @Mr Hofs certainly is!!!!! learned loads from that guy
Recovery VODAP110
Petert87 said:
Nice mate, @Mr Hofs is a real master
Maybe you can upload the OTA, firmware and recovery on mega.co.nz and post the links here: http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
uploaded and posted on thread.
https:// mega.co.nz/#!24UliTKJ!b5h272Mwt5HS7sP9H6tiJTAS4lBFXu8iRRBqlYE6xd8
Good it worked.
raynordg said:
Hi Petert87 tried this one the other day but it didn't work for me.
Mr Hofs, You absolute legend. This was a very quick fix (No. 1) back up and running now.
Hi onkel.
the process i went through was as follows.
1) force download the OTA from swisscom and copy off to computer.
2) do what Mr Hofs said above and extract the ROM and dig out the recovery.img
3) reset with fast boot - (fastboot reboot-bootloader)
4) flash recovery (fastboot flash recovery recovery.img
5) fastboot erase cache
6) fastboot reboot
7) install OTA from within booted OS
8) wait.......
Thanks for taking the time to read through my problem guys.
@Mr Hofs if you would like the OTA update or recovery.mg please let me know.
Click to expand...
Click to collapse
THANKS !! Now it works ! My Problem was that I had the same recovery as you...
Back to stock problem
Hello,i have a similar problem. I did everthing as you,rooted,custom recovery and unlock bootloader on htcdev,all to try out custom roms like arhd and so on. But i didn't do a nandroid backup,because i'm a fool and didn't know what i was doing. When i wanted to go back to stock i tried flashing 3.29.161.9 as it's similar to our stock rom but had no luck,still no updates. When i go to fastboot my os says os-3.29.166.9,so clearly there lies i problem. i need i stock 3.29.166.9 nandroid backup so i can go to stock. i've downloaded the recovery you uploaded and put it in 3.29.161.9 rom but no luck. So can you please upload a 3.29.166.9 nandrod backup. Thanks in advance. And mister Petert87 and Mr Hofs if you have any idea how to solve my problem please tell can you tell me. Cheers guys
OTA Firmware
5.0.1 Swisscom firmware OTA
OTA_M8_UL_L50_SENSE60_MR_Vodafone_CH-DE(swisscom_only)_4.19.166.2-3.29.166.9_release_417015636rjn6nthj40isc.zip 659.7 MB
https:// mega.co.nz/#!r0UnlBRR!lfcnKjURWCaVd7ddTUQ-r80A475H81MH5i-eHp2MN0g
raynordg said:
5.0.1 Swisscom firmware OTA
OTA_M8_UL_L50_SENSE60_MR_Vodafone_CH-DE(swisscom_only)_4.19.166.2-3.29.166.9_release_417015636rjn6nthj40isc.zip 659.7 MB
https:// mega.co.nz/#!r0UnlBRR!lfcnKjURWCaVd7ddTUQ-r80A475H81MH5i-eHp2MN0g
Click to expand...
Click to collapse
No news about a nandroid backup?
in the same pickle
dexterts said:
No news about a nandroid backup?
Click to expand...
Click to collapse
Sorry to resurrect this thread, I would really appreciate if anyone could share a nandroid backup. Phone not working. I appreciate the OTA's you shared, but I am note sure how to proceed from there. Nandroid would help.
Thanks in advance.
adem_7 said:
Sorry to resurrect this thread, I would really appreciate if anyone could share a nandroid backup. Phone not working. I appreciate the OTA's you shared, but I am note sure how to proceed from there. Nandroid would help.
Thanks in advance.
Click to expand...
Click to collapse
No luck dude,no one who has the vodap110 cid is willing to post a nandroid backup. I've been searching for months
@ckpv5
Did you not have backups for x.xx.166.x, or am I mistaken?
adem_7 said:
Sorry to resurrect this thread, I would really appreciate if anyone could share a nandroid backup. Phone not working. I appreciate the OTA's you shared, but I am note sure how to proceed from there. Nandroid would help.
Thanks in advance.
Click to expand...
Click to collapse
Are you running a rooted stock ROM when your phone now not working ? If yes, can you install TWRP recovery and make backup of the system part only. Then upload it for me, I'll try to fix it. I've done this many times with other rare ROM like WIND, Taiwan version, Optus, Telstra and many more.
If possible, just PM me the link.. this is the only way that I can help you and @dexterts
EddyOS said:
@ckpv5
Did you not have backups for x.xx.166.x, or am I mistaken?
Click to expand...
Click to collapse
No. I don't have because I can't find any version nandroid for x.xx.166.x anywhere out of XDA
That's why I'm asking these guys to help them
And if that @raynordg guy respond to notification ... he can help too. He was scared about his data on nandroid backup ... system partition has no user data.
ckpv5 said:
Are you running a rooted stock ROM when your phone now not working ? If yes, can you install TWRP recovery and make backup of the system part only. Then upload it for me, I'll try to fix it. I've done this many times with other rare ROM like WIND, Taiwan version, Optus, Telstra and many more.
If possible, just PM me the link.. this is the only way that I can help you and @dexterts
No. I don't have because I can't find any version nandroid for x.xx.166.x anywhere out of XDA
That's why I'm asking these guys to help them
And if that @raynordg guy respond to notification ... he can help too. He was scared about his data on nandroid backup ... system partition has no user data.
Click to expand...
Click to collapse
Guys,one question. If i buy sunshine and s-off my m8,than i could change my cid and flash for example .401 firmware and get ota updates as my phone was a regular htc international model? Sorry for the off topic
dexterts said:
Guys,one question. If i buy sunshine and s-off my m8,than i could change my cid and flash for example .401 firmware and get ota updates as my phone was a regular htc international model? Sorry for the off topic
Click to expand...
Click to collapse
Yes ... change CID and flash EU WWE RUU if you want it on .401
If only firmware, you can restore a EU WWE backup and do OTA .. but for now only lollipop the latest and there's already lollipop RUU, you can check EddyOS thread for RUU method : http://forum.xda-developers.com/showthread.php?t=2735235

[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

ADB, Recovery and some issues

Hello XDA-Community,
I have an HTC One M8 (M8_UL) with the following details:
Software Status: Modified
*** UNLOCKED ***
And I have Cyanogenmod installed (latest nightly build 12.1-20151118-NIGHTLY-m8 Android 5.1.1) and TWRP 2.8.7.0
Now my GPS is not working since a while now (I can't really tell if it has even started when I moved to CM or if it happened afterwards).But GPS Status never gives me a single satellite. I have read in another topic here in the board, that getting back to Sense Stock could help. Then back to CM and everything could be fine.
But here my questions start:
1) What exactly does this S-ON mean?
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
4) Why is my version-main info empty? (see below)
Sorry for all these questions and thanks in advance for your help
C:\Users\fsc>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(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!
finished. total time: 0.053s
Click to expand...
Click to collapse
My answers below in blue font.
damarges said:
1) What exactly does this S-ON mean?
S-on/s-off is a HTC specific security flag. S-off means "security off" and in the past meant that all security checks are bypassed. On the M8, its a little more complicated than that, some things are bypassed, some are not. But it allows you to do things like flashing modified hboots, radios, unsigned RUUs and downgrade firmware. S-off is kind of a "back door" that HTC leaves for itself. But when exploited by users, such as the devs here at XDA, is handy for some pretty useful things. S-on is the "stock" condition, and means you don't have the ability to do these things. In order to get s-off, you need to use the sunshine method, which costs $25. But s-off is not required to flash ROMs, root, or return to stock.
2) So how do I know which firmware/recovery/system (I figured out that there is some difference between all this and that now my TWRP 2.8.7.0 obviously is my Recovery Tool installed at the moment.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
If you want to go back to stock recovery, you will want the stock recovery file that matches your firmware number. But for what you describe, I don't think you need or want to flash stock recovery.
System is the ROM version number, and again if you are returning to stock, you should find the nandroid that has the same number as your firmware.
Don't confuse any of the above with the software number in the phone's settings (common mistake). That number is related to the current ROM. So if you flash a custom ROM, that number just corresponds to the custom ROM, not the firmware or stock ROM number.
3) What is RUU and OTA ? As I understood its like a Operating System Update out of windows? I once downloaded a version but it always claims my battery would not be full so it would not let me update/upgrade/recover?
RUU and OTA are related, but two very different things:
RUU = ROM update utility. Its a Windows executable, normally an official HTC tool that will completely re-image your phone to stock, every single partition, and will also wipe your phone. The CID and MID of your phone need to match what the RUU is intended for. Does not require stock ROM or stock recovery to run, but has to be same or greater version number than main version (or hboot) on the phone - meaning you can't "downgrade" (unless you have s-off). Relocking the bootloader is required to RUU (again, unless you have s-off).
OTA = over the air. Its an incremental OS update, sent out by HTC. It normally requires the software number directly proceeding it, meaning you need to install them in sequence, and can't skip any. And may not be a complete image, but simply a "patch". It also requires stock recovery to be present, as well as the stock ROM. No need to relock bootloader to OTA (unlike RUU). Also, OTA will not typically wipe the phone (but you should backup before OTA to be safe, as it does sometimes wipe data).
4) Why is my version-main info empty?
Common issue. This is usually because an outdated 2.7 version of TWRP was installed at some point, wiping out the main version info (known TWRP bug).
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse
Thanks a lot for these detailed descriptions. Makes it more clear to me.
Firmware number is indicated by main version in getvar output, or by the "OS" number on the bootloader screen.
Click to expand...
Click to collapse
>> as it is empty on my getvar output I don't know which firmware/recovery to choose?
On the bootloader screen, does it read a number after "OS" in green letter?
Click to expand...
Click to collapse
>> no. its just empty "OS- " thats it.
But for what you describe, I don't think you need or want to flash stock recovery.
Click to expand...
Click to collapse
>> no actually I don't want stock recovery. I am happy with TWRP. I actually just want to have my GPS issues fixed. else I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?
damarges said:
I am really happy with Cyanogenmod.
>> do you have knowledge on how to fix the GPS issue? or if returning to Sense ROM could fix it maybe?
Click to expand...
Click to collapse
I'm not a CM user on this device, so I'm not too familiar with the issue.
damarges said:
So if I don't know my firmware/OS - number? how do I choose a proper nandroid backup? and does a nandroid backup does return my phone to sense ROM?
Click to expand...
Click to collapse
I believe your firmware is 4.16.401.x (possibly "8" where the "x" is), based on your CID, and hboot and radio numbers indicating you are on Lollipop firmware.
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
But yes, a stock nandroid for 4.16.401 will return you to the Sense ROM.
redpoint73 said:
Are you sure its a nandroid that is being discussed in the "fix" and not RUU to stock? If you direct me to the thread/post that discusses the fix, maybe I can take a look and see if I can figure anything out.
Click to expand...
Click to collapse
The links I used to gather information:
https://www.reddit.com/r/cyanogenmod/comments/3gw7fm/htc_one_m8_cm121_the_gps_doesnt_work/
On http://forum.xda-developers.com/showthread.php?t=2701376 I can not find a nandroid stock backup that is working. The link to 4.16.401.10 - TWRP Thanks to sneakyghost is not working anymore on mega :/
How do I create a nandroid backup myself (after hopefully I get fixed everything)?
I could replace my Cyanogenmod with a stock nandroid backup of htc sense. but it did not fix the GPS problem. Still not a single satellite to receive :/
Even erase modemst1 and erase modemst2 did not fix anything :/
Anyone has a hint what to do?

M8 return to stock issues - no wifi, no data connection

Good evening folks.
I have an M8 which I am struggling to return to stock.
It's a VODAP001 CID but I previously had a Three.co.uk rom flashed and was fine for over 12 months, but obviously my OTA updates would fail due to the mismatch of CID and rom which would result in throwing up an error regarding tampered software.
A few days ago I decided to attempt going back to stock but have run into issues. I'm no expert and learning as I go, and could really do with some help as I've gone as far as my understanding has taken me. I think that "161" recoveries and nandroids are important here, but whatever I've tried so far is failing.
I found a stock RUU exe suited to the vodap001 which installed without issue, however this has now resulted in the handset having no data or wifi connectivity. The wifi switch in the phone's settings is greyed out and won't turn on, the data connection shows as disconnected no matter what I enter into APN's.
https://www.androidfilehost.com/?w=...a359c418083ba13ada2f597b2e3ee8fa73e877a10c9c0
I've found further RUU's which don't even open on either of my machines, and a fair few posts by others who have had issues with RUU's that involve removing and re-installing C++
Here's one such page I went through to try and resolve the issue:
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Could this be due to incompatible firmware radio versions? I've used twrp to unlock and relock the recovery and bootloader a dozen times over the last 24 hours and the result is always the same - no wifi, no data connectivity.
Clearly I'm doing something wrong and my understanding has reached a point where I have half a dozen zip files, rar files, img files etc on my desktop, trying to learn how to correctly use the all-in-one toolkit while getting my head around twrp and stock recoveries.
I've been able to find other RUU's with more specific reference to the VODAP001 but they won't open on either of my machines.
Pretty much bamboozled now and well out of my depth!
Several of my apps (such as online banking) require that I am not rooted.
At this stage I couldn't care less if I get a newer droidOS version than the 12 month out-of-date system I was previously running with an incorrect CID which kept me from OTA updates, anything is preferable to the current situation of no wifi, no network data.
Any expert advice and understanding of this situation I've created would be greatly appreciated, I've clearly gone out of my depth with this and struggling to make sense of it!
Thank you :highfive:
anyone?
xandercom said:
anyone?
Click to expand...
Click to collapse
Post fastboot getvar all result (without serial & imei no.) then we'll see what actually that you need.
Reading above suggest that you installed a ROM not meant for your hboot version or device version
ckpv5 said:
Post fastboot getvar all result (without serial & imei no.) then we'll see what actually that you need.
Reading above suggest that you installed a ROM not meant for your hboot version or device version
Click to expand...
Click to collapse
Thank you
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.3
(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: VODAP001
(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: 255f41e7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
First - remove serial & imei no. from your above post.
Your problem is the baseband which suggest that you installed a wrong backup which I believe was 4.19.161.2 and then updated to 4.19.161.3 .. so the baseband failed to be updated because there is no radio update in 4.19.161.3
It's not easy to fix with a S-On device. But you can try this and see how it goes ...
Download and restore TWRP backup 3.29.161.9 and install its stock recovery then do OTA to 4.19.161.2 and then 4.19.161.3
I after restore 3.29.161.9 and still no wifi and no data for you to proceed OTA, then go for a lower version 2.22.161.6 and its stock recovery, reboot and see whether there is data and/or wifi. If there is then do OTA.
In any case, never relock bootloader, not needed at all
Download files from : http://forum.xda-developers.com/showpost.php?p=63851107&postcount=5812
If these fail, you don't have any other choice but to S-Off the device. The problem is how to S-Off when you don't have a working data and/or wifi.
Try the above procedure and see how it goes and report back.
ckpv5 said:
First - remove serial & imei no. from your above post.
Your problem is the baseband which suggest that you installed a wrong backup which I believe was 4.19.161.2 and then updated to 4.19.161.3 .. so the baseband failed to be updated because there is no radio update in 4.19.161.3
It's not easy to fix with a S-On device. But you can try this and see how it goes ...
Download and restore TWRP backup 3.29.161.9 and install its stock recovery then do OTA to 4.19.161.2 and then 4.19.161.3
I after restore 3.29.161.9 and still no wifi and no data for you to proceed OTA, then go for a lower version 2.22.161.6 and its stock recovery, reboot and see whether there is data and/or wifi. If there is then do OTA.
In any case, never relock bootloader, not needed at all
Download files from : http://forum.xda-developers.com/showpost.php?p=63851107&postcount=5812
If these fail, you don't have any other choice but to S-Off the device. The problem is how to S-Off when you don't have a working data and/or wifi.
Try the above procedure and see how it goes and report back.
Click to expand...
Click to collapse
Hey,
Thank you for your detailed response!!
I'm just about to do the first OTA having installed and then stock recovery. Do you mean install one of the many OTA files I've seen, or do you literally mean let the phone upgrade through the normal over the air updates? If it's the latter I can tether the handset to use my workstation's internet connection so no trouble there.
Let the phone upgrade through the normal over the air update after you restore the 3.29.161.9 backup and 3.29.161.9 stock recovery
(You can't do manual OTA update with S-On device, won't work)
You can read HOW-TO to understand better in post #1 in my thread linked in my signature.
Good luck & good night
ckpv5 said:
Let the phone upgrade through the normal over the air update after you restore the 3.29.161.9 backup and 3.29.161.9 stock recovery
(You can't do manual OTA update with S-On device, won't work)
You can read HOW-TO to understand better in post #1 in my thread linked in my signature.
Good luck & good night
Click to expand...
Click to collapse
Thank you! after I installed 3.29.161.9 and stock recovery but still no wifi or data, so I've connected to the PC through USB to share my PC's internet. It's currently downloading and installing 4.19.161.2
xandercom said:
Thank you! after I installed 3.29.161.9 and stock recovery but still no wifi or data, so I've connected to the PC through USB to share my PC's internet. It's currently downloading and installing 4.19.161.2
Click to expand...
Click to collapse
When the installation is successful, you should have data & wifi because the OTA should install the updated baseband. Then do the next OTA.
I'll check your progress tomorrow
ckpv5 said:
When the installation is successful, you should have data & wifi because the OTA should install the updated baseband. Then do the next OTA.
I'll check your progress tomorrow
Click to expand...
Click to collapse
Thanks for the follow up.
4.19.161.2 OTA has installed but no change to the wifi or data being inoperative.
I'm just letting it OTA to 4.19.161.3 to see if that makes any difference.
Unfortunately no change, so I will now try again with the 2.22.161.6 as you've suggested!
ckpv5 said:
When the installation is successful, you should have data & wifi because the OTA should install the updated baseband. Then do the next OTA.
I'll check your progress tomorrow
Click to expand...
Click to collapse
2.22.161.6 seems to have done the trick, wifi and data working now, I will let it update itself after I've restored stock recovery.
Thank you once again for your very helpful advice. I understand a little better now and will know what to look out for if I ever go off-stock again.
Merry Christmas!
xandercom said:
2.22.161.6 seems to have done the trick, wifi and data working now, I will let it update itself after I've restored stock recovery.
Thank you once again for your very helpful advice. I understand a little better now and will know what to look out for if I ever go off-stock again.
Merry Christmas!
Click to expand...
Click to collapse
Good to know ... so after all OTA done up to 4.19.161.3 ... everything good ?
At least this going to help many people with same problem of restoring wrong backup that are not meant for their hboot version.
ckpv5 said:
Good to know ... so after all OTA done up to 4.19.161.3 ... everything good ?
At least this going to help many people with same problem of restoring wrong backup that are not meant for their hboot version.
Click to expand...
Click to collapse
Yes, everything works as it should and OTA'd up to 4.19.161.3.
I was previously running a much older rom and clearly used the wrong CID as I was getting errors with OTA's. Although my handset is on three's network it was originally a vodafone handset. I had updated through the HTC all in one tool kit a three rom without understanding the issues with CID's.
So effectively I've been without any updates to the handset for nearly 18 months. It's great to finally get some official OTA's and jumped quite a few android versions!
Your help has been very much appreciated sir!

Categories

Resources