Unroot and OTA htc one m8 - One (M8) Q&A, Help & Troubleshooting

Me again!! Sorry for spamming but i need little help here
I have an M8x unlocked version (CID no. HTC__621), S-ON, Rooted. Yesterday pop-up OTA update (number 4.24.709.3). My phone running Lollipop 5.0.2 (4.24.709.2). The phone must be "stock" to do an OTA, so i install the stock recovery (i understand the stock recovery this and is here). Once i do that i try to install OTA and the desaster come, my phone run into bootloop (stucked in htc logo) then i remember the backup i do before, so phone is now operating. the thing, i know, with root i can't install any update, so i want to go back into pure stock sense, with stock recovery to do the update, or at least come back to one version that allow make the OTA's (Android M is coming!!!) i'm a little dumb haha, i need some good soul to teach me exactly what to do to finally leave my phone alone and you guys, thank you so much 4 help me out!! (sorry for my bad english)
HTC One M8x
CID No. HTC__621
Firmware No. 4.24.709.2
Bootloader Unlocked
Factory Unlocked
Rooted
Custom Recovery TWRP

Meliragazza2571 said:
Me again!! Sorry for spamming but i need little help here
I have an M8x unlocked version (CID no. HTC__621), S-ON, Rooted. Yesterday pop-up OTA update (number 4.24.709.3). My phone running Lollipop 5.0.2 (4.24.709.2). The phone must be "stock" to do an OTA, so i install the stock recovery (i understand the stock recovery this and is here). Once i do that i try to install OTA and the desaster come, my phone run into bootloop (stucked in htc logo) then i remember the backup i do before, so phone is now operating. the thing, i know, with root i can't install any update, so i want to go back into pure stock sense, with stock recovery to do the update, or at least come back to one version that allow make the OTA's (Android M is coming!!!) i'm a little dumb haha, i need some good soul to teach me exactly what to do to finally leave my phone alone and you guys, thank you so much 4 help me out!! (sorry for my bad english)
HTC One M8x
CID No. HTC__621
Firmware No. 4.24.709.2
Bootloader Unlocked
Factory Unlocked
Rooted
Custom Recovery TWRP
Click to expand...
Click to collapse
You cannot take an OTA if you are rooted, have custom recovery. You MUST be absolutely stock ROM with stock recovery to take and install correctly OTA updates.

similar problem.. i flashed stock recovery but still getting installation aborted..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mushfiq20 said:
similar problem.. i flashed stock recovery but still getting installation aborted..
Click to expand...
Click to collapse
You can't even update if you "unrooted" your rom.
You must have NEVER rooted stock rom + recovery !

mushfiq20 said:
similar problem.. i flashed stock recovery but still getting installation aborted..
Click to expand...
Click to collapse
It's clearly shown in the log you have a rooted device or a unrooted previously rooted device, your binary is not stock

ckpv5 said:
It's clearly shown in the log you have a rooted device or a unrooted previously rooted device, your binary is not stock
Click to expand...
Click to collapse
so now what can i do if i want to update??

mushfiq20 said:
so now what can i do if i want to update??
Click to expand...
Click to collapse
Like i said, you need a never rooted stock backup. You should have made one after you flashed twrp to begin with.
But go to the backup threads and find the one that corresponds with your software build number. Restore it and flash the stock recovery. Then you can do ota

Had the same problem
I just wanted to share my experience. I had the same problem.
So I downloaded a twrp-backup of my version, since I failed to do proper backups myself. Then I unpacked it. The system.ext4.win### can be unpacked with tar.
Then I did a: (on my linux, but should work with cygwin for windows. It gives a list of the checksum of all files under the current directory)
find . -type f -exec md5sum {} \; > stock.md5
Uploaded the stock.m5 and compared to my phones files. md5sum -c stock.md5 works if you have it installed, if not, can make a script that uses the md5-command.
What I found in this OTA for me, was that my /system/bin/app_process32 was softlinked to /system/xbin/daemonsu, and thus had the wrong md5sum.
The original was saved, so I booted twrp and adb in to restore the file.
After that the OTA would run, and all looked good, until it rebooted, and got stuck at the boot-screen. Did the hold volume-up and power to reboot into bootloader. (Did it a few times before I read online that you must unplug the usb for it to work)
My OS was the new version (6.12.709.4), so it seemed as the important parts were updated right. I searched for a backup in the recovery-thread, but there was none yet.
After that fastboot boot twrp.img, to start it without flashing. And then did a full backup of phone again, and now unpacked my backup. Just looking through to see if any other softlink was wrong, I found that /system/bin/app_process had changed to also softlink to /system/xbin/daemonsu. (It was softlinked to app_process32 before...)
So I cd /system/xbin/ && rm app_process && ln -s app_process32 app_process
Then I rebooted, and now my phone is working great with android version 6.0.
Im not saying anyone should do like this. I just telling this for those who want to look around before flashing a binary downloaded from somewhere. So as per usual, dont blame me.

Mr Hofs said:
Like i said, you need a never rooted stock backup. You should have made one after you flashed twrp to begin with.
But go to the backup threads and find the one that corresponds with your software build number. Restore it and flash the stock recovery. Then you can do ota
Click to expand...
Click to collapse
I did as u said. from the backup thread i downloaded twrp backup of matching CID, restored it and flashed stock recovery and thn tried updating via OTA. but still no luck. is it happening because i career unlocked my phone?

mushfiq20 said:
I did as u said. from the backup thread i downloaded twrp backup of matching CID, restored it and flashed stock recovery and thn tried updating via OTA. but still no luck. is it happening because i career unlocked my phone?
Click to expand...
Click to collapse
Carrier unlocking has nothing to do with the OTA. As long as the firmware, ROM and stock recovery all match, there's no reason why you cannot take OTA updates. If you are rooted, however, you cannot take the updates, they will fail to install.

Einwod said:
Carrier unlocking has nothing to do with the OTA. As long as the firmware, ROM and stock recovery all match, there's no reason why you cannot take OTA updates. If you are rooted, however, you cannot take the updates, they will fail to install.
Click to expand...
Click to collapse
all the roms of the backup thread are non-rooted stock roms right? so it should have worked i guess.. but it didn't. is there any way to directly flash marshmallow sense stock rom? i found thread for GPE edition but didnt find any for sense edition. my CID is BM____001 btw...

Meliragazza2571 said:
Me again!! Sorry for spamming but i need little help here
I have an M8x unlocked version (CID no. HTC__621), S-ON, Rooted. Yesterday pop-up OTA update (number 4.24.709.3). My phone running Lollipop 5.0.2 (4.24.709.2). The phone must be "stock" to do an OTA, so i install the stock recovery (i understand the stock recovery this and is here). Once i do that i try to install OTA and the desaster come, my phone run into bootloop (stucked in htc logo) then i remember the backup i do before, so phone is now operating. the thing, i know, with root i can't install any update, so i want to go back into pure stock sense, with stock recovery to do the update, or at least come back to one version that allow make the OTA's (Android M is coming!!!) i'm a little dumb haha, i need some good soul to teach me exactly what to do to finally leave my phone alone and you guys, thank you so much 4 help me out!! (sorry for my bad english)
HTC One M8x
CID No. HTC__621
Firmware No. 4.24.709.2
Bootloader Unlocked
Factory Unlocked
Rooted
Custom Recovery TWRP
Click to expand...
Click to collapse
Have you solved your problem ? If not yet ... you can ask in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I'll help you because all your needed files are there.
I just checked all your 9 posts, seems like you not yet solve your problem
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
mushfiq20 said:
all the roms of the backup thread are non-rooted stock roms right? so it should have worked i guess.. but it didn't. is there any way to directly flash marshmallow sense stock rom? i found thread for GPE edition but didnt find any for sense edition. my CID is BM____001 btw...
Click to expand...
Click to collapse
Which backup that you restored ? You need 4.20.666.2 and I don't see anywhere that backup is posted.

ckpv5 said:
Have you solved your problem ? If not yet ... you can ask in my thread - http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I'll help you because all your needed files are there.
I just checked all your 9 posts, seems like you not yet solve your problem
---------- Post added at 12:24 AM ---------- Previous post was at 12:21 AM ----------
Which backup that you restored ? You need 4.20.666.2 and I don't see anywhere that backup is posted.
Click to expand...
Click to collapse
i restored this one.. https://www.androidfilehost.com/?fid=23578570567722629
i know this is not 4.20.666.2. but i thought if i could climb my way up to marshmallow from 1.55.666.4 by updating again and again.

mushfiq20 said:
i restored this one.. https://www.androidfilehost.com/?fid=23578570567722629
i know this is not 4.20.666.2. but i thought if i could climb my way up to marshmallow from 1.55.666.4 by updating again and again.
Click to expand...
Click to collapse
You can try. But I think the OTA will detect that the ROM number doesn't match your firmware number, and fail.

mushfiq20 said:
i restored this one.. https://www.androidfilehost.com/?fid=23578570567722629
i know this is not 4.20.666.2. but i thought if i could climb my way up to marshmallow from 1.55.666.4 by updating again and again.
Click to expand...
Click to collapse
That's too low version.
Have a look the thread linked in my signature. There's a non-rooted backup 3.34.666.4. Give me 5 minutes, I put up link for 4.20.666.1 so you do only 2 OTAs to Marshmallow - 4.20.666.1 --> 4.20.666.2 --> 6.13.666.7
If you're willing to wait, I can upload 4.20.666.2 tomorrow night as it is already late here and I need to go to bed soon. Make request in my thread so I don't forget (if this is needed)
Edit : Link for 4.20.666.1 updated

ckpv5 said:
That's too low version.
Have a look the thread linked in my signature. There's a non-rooted backup 3.34.666.4. Give me 5 minutes, I put up link for 4.20.666.1 so you do only 2 OTAs to Marshmallow - 4.20.666.1 --> 4.20.666.2 --> 6.13.666.7
If you're willing to wait, I can upload 4.20.666.2 tomorrow night as it is already late here and I need to go to bed soon. Make request in my thread so I don't forget (if this is needed)
Edit : Link for 4.20.666.1 updated
Click to expand...
Click to collapse
thank you so much. . i will have to flash it tomorrow anyway. but i guess 4.20.666.1 will be good enough. i dont have a problem with doing 2 OTA's

mushfiq20 said:
thank you so much. . i will have to flash it tomorrow anyway. so it would be great if you can upload 4.20.666.2 tomorrow. but 4.20.666.1 will do too.
Click to expand...
Click to collapse
Sure can .. but will be late night here after I come home from work (also my internet is not fast enough .. to upload a nandroid takes about 2-3 hrs)

ckpv5 said:
Sure can .. but will be late night here after I come home from work (also my internet is not fast enough .. to upload a nandroid takes about 2-3 hrs)
Click to expand...
Click to collapse
you dont have to go through the hassle. this version will do.. i just hope it works.

now this is weird.. i flashed 4.20.666.1 .. and when i check for software updates i get "There are no updates available for your phone." :/

mushfiq20 said:
now this is weird.. i flashed 4.20.666.1 .. and when i check for software updates i get "There are no updates available for your phone." :/
Click to expand...
Click to collapse
Keep your hair on and wait a while. It takes time sometimes for the updates to come through. You did flash the stock recovery as well?

Related

[Q] JB OTA update fails on rooted Vodafone One X

Hello guys,
I have a HTC One X from Vodafone, rooted, unlocked, stock rom, custom recovery, and today (FINALLY ) I received the OTA update to Jelly Bean.
I downloaded it and tried to install it using the custom recovery but it was failing on some assert. I guessed that it was because of the recovery so I flashed back the stock recovery and tried to install; fail again.
Went online and found the directory for the update log and saw an entry saying that there was a problem trying to verify the stock Dropbox apk that comes with the phone and that is placed on /system/apps. I read somewhere that if you modify something on the stock apks the OTA would fail, and unfortunatelly I did, I flashed the Galaxy S3 Dropbox apk on my phone, but that's not the problem, the problem is that I deleted the flashed Dropbox and the stock Dropbox from /system/apps without knowing it and the OTA is still failing.
My guess is that if I can flash the stock Dropbox apk to /system/apps, the OTA will try to verify it and will succeed, and therefore I'll have finally Jelly Bean on my branded device (as I said, is just a guess) so if someone could please send me the stock Dropbox apk, the one located in /system/apps as well as any other file located there that could possibly be related to Dropbox app, it will be very very appreciated.
If you guys think that I'm missing something here and even after flashing the stock Dropbox apk the OTA will still fail for some karma related reasons, please let me know and help me out.
If you need any other info from my phone let me know too.
If you need the .zip file with the official update from Vodafone I have it too.
Thanks in advance.
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
nemer12 said:
TO update OTA you SHOULD HAVE ONLY stock recovery and STOCK boot.img(kernel) ..and this way everything will be ok.
Click to expand...
Click to collapse
Well yes I have stock recovery (replaced the custom recovery yesterday) and stock kernel, I haven't changed the kernel yet, and according to the log the problem is with Dropbox. I'll try to find it and paste it here so you guys can see it.
Thanks.
Just flash the RUU, update OTA and reroot.
Alright, will do and I'll let you know how it goes. Thanks
Netrunner16 said:
Alright, will do and I'll let you know how it goes. Thanks
Click to expand...
Click to collapse
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
If you only unlocked the bootloader the update should run fine !!! If it fails you did change some more !
prankstarr said:
I have exactly the same problem and I dont know what to do!
I'd like to just flash the Android Revolution HD JB ROM but im scared of bricking my phone and there is no easy guide to accomplish this - the guides ive seen on youtube are for other ROMS...
So, now that JB is out OTA for my stock ROM I want to update to it but I get stuck...
All ive done is unlock my bootloader - Ive never even flashed a custom ROM!
Wish I'd never done it now...way too complex
Click to expand...
Click to collapse
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Netrunner16 said:
I think they're right, if I hadn't touched the system apps then I think the update would work, having only unlocked and rooted. Right after you try to install the update, go to /cache/recovery/ and check the logs for any clues on why the update is failing.
I'll try flashing the RUU for my phone, then applying the OTA and the rerooting as suggested, maybe you should try the same.
Click to expand...
Click to collapse
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
prankstarr said:
I unlocked the bootloader (HTCDev)
I flashed CWR...
That was it (I am running a different launcher but that makes no different right??)
How do I get the RUU for Vodafone UK? Is that the stock ROM? Sorry, I am not very good with this stuff...I was okay at rooting my Desire HD but this is another level
Click to expand...
Click to collapse
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
MarcelHofs said:
And rule number 1 after flashing cwm custom recovery is
always do a nandroid backup from the stock rom ! Now you know why its important.so when you go to JB and start rooting and running custom roms.....do the nandroid backup to avoid these situations !
Click to expand...
Click to collapse
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
prankstarr said:
But I still have the stock ROM. I never flashed a custom ROM. I wanted to flash a JB rom, thats why i rooted...then I discovered that my CID was not capable of getting a JB ROM so I just left it rooted but on stock voda ROM...
Click to expand...
Click to collapse
But you said you had CWR, you need to flash the stock recovery back and then try the update.
MarcelHofs said:
You need to flash the stock recovery !
Do this command
Fastboot getvar version-main
If a number pops up starting with 2.17 you need to flash back this recovery
http://db.tt/U5CK4noo
And yes you did more than just unlock the bootloader, be specific .... it's necessary for this phone otherwise it gets confusing !
Click to expand...
Click to collapse
Okay cool - will try although I thought I flashed stock recovery. I got rid of CMR when I got in from work today ... recovery img was in the fastboot folder i used when unlocking bootloader.
---------- Post added at 12:20 AM ---------- Previous post was at 12:14 AM ----------
Netrunner16 said:
But you said you had CWR, you need to flash the stock recovery back and then try the update.
Click to expand...
Click to collapse
Yes, I thought i flashed stock before but am about to confirm
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
MarcelHofs said:
Doesn't matter .... Did u read my post above yours ....
Last time .....
You need stock rom,stock kernel, STOCK RECOVERY....not the custom cwm recovery. That's why the update fails. :thumbup:
Click to expand...
Click to collapse
Yes, sorry - i did read it and it did say 2.17xxx...I downloaded the recovery you pointed me to but expect i need to re-unlock the bootloader. (I re-locked it before thinking that was causing the issue...)
Anyway, soon I should know if this works
By the way, I really appreciate you helping me - i've been trying to sort this out all evening!
---------- Post added at 12:34 AM ---------- Previous post was at 12:29 AM ----------
MarcelHofs said:
The goal after unlocking the bootloader is to flash a custom recovery to flash different roms.....therefore i doubt u flashed the stock recovery.....unlocking the bootloader and flashing a stock recovery doesn't make sense
Click to expand...
Click to collapse
There is a good chance you are correct. The file in my fastboot folder said recovery and I assumed it was what I was after but it may have been connected to something that I was told to download in the unlocking process (I followed a guide on Youtube by a chap called cursed4eva)
I'm reunlocking the bootloader now because I got an error wh3n i tried to flash that recovery img. "writing 'recovery'... FAILED (remote: not allowed)"
---------- Post added at 01:24 AM ---------- Previous post was at 12:34 AM ----------
Okay - so I
1/ reunlocked the bootloader which basically wiped the phone back to its initialt state all be it with an unlocked bootloader.
2/ once again completed the OTA download of Vodafone Jellybean for the One X
3/ flashed the 2.17 recovery img that Marcel provided
4/ tried to update
5/ am currently looking at a download / progress bar! (YESSSS!)
6/ am hoping this works!
Thanks a lot Marcel. I very much appreciate your patience!
dr9722 said:
Just flash the RUU, update OTA and reroot.
Click to expand...
Click to collapse
I already have the RUU for my phone, and I was planning to follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1660807
But I was thinking, what if I flash only the system.img instead of all the 3 files? I already have the stock recovery (the one you provided) and I've never changed the boot.img so I still have the stock one.
What about if I flash the system.img only, and then try the OTA update? Do you think that would work?
Thanks for the help.
Yes you can try that, the phone is already wiped with unlocking the bootloader, i never tried it. But in logical terms it is possible yes. If doesn't work you can always run the complete ruu !
That's weird, I'm getting error 00000006 when trying to flash the system.img.
Reading on other posts that's related to the size of the file, which is around 1 GB. If I can't flash the system.img I think I wont be able to run the entire RUU either.
Do you know a way to bypass this error?

Problems to get stuck ota to work

Hello i got a massive problem getting my 4.4.4 ota to work. I found an old stock backup and everything seemed fine ota start downloading and whatnot. So the phone restart in recovery not in hboot and try to flash the download ota pack. But everytime it produces an error.
By the way bootloader is unlocked and there's a tempered label I'm s-on and firewater doesn't work.
Any help? I'm so sick of have to use 4.4.2 droid...
Stock recovery installed ?
Old stock backup is pure stock with nothing removed ?
What's the error listed in recovery ?
What's your software version no. ? Maybe a proper backup is around somewhere especially here : http://forum.xda-developers.com/showthread.php?t=2701376
ckpv5 said:
Stock recovery installed ?
Old stock backup is pure stock with nothing removed ?
What's the error listed in recovery ?
What's your software version no. ? Maybe a proper backup is around somewhere especially here : http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
So how do i install stock recovery? Where do i get software version number? Feel like a noob -.-
Darkmind82 said:
So how do i install stock recovery? Where do i get software version number? Feel like a noob -.-
Click to expand...
Click to collapse
Read the thread that I linked above ... see Q&A in post #2.

Update to Android 6 and TWRP

I have installed the TWRP and just wanted to update to Android 6. The problem is, that once the download finishes and the phone reboots, it puts me in the TWRP instead of installing the update. How do I proceed to update my phone to Android 6?
You want to install OTA on TWRP? Not gonna work, find your software number(4.xx.xx.xx) in Settings/about. Then flash stock recovery(numbers must match with software number) and try to apply OTA. You might need clean stock(non-rooted) rom.
I checked my version and it says 4.16.401.13, so I downloaded the stock+recovery+4.16.401.13_M8 and flashed it via adb using "fastboot flash recovery img". When I wanted to install the OTA I got into the recovery and got this: http://imgur.com/FpVk5Sg
Afaik I have the official ROM and just got root access for a few apps back in the days
Moon key said:
I checked my version and it says 4.16.401.13, so I downloaded the stock+recovery+4.16.401.13_M8 and flashed it via adb using "fastboot flash recovery img". When I wanted to install the OTA I got into the recovery and got this: http://imgur.com/FpVk5Sg
Afaik I have the official ROM and just got root access for a few apps back in the days
Click to expand...
Click to collapse
unexpected contents(i think thats some root binaries etc)...
Anyways, check this thread and download stock twrp nand for your 4.16.401.13 firmware from here, follow the steps carefully, it's easy. http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Thank you! Am I seeing that right, that all of my apps and co will be gone afterwards?
Yep, but you can always backup apps(+data of apps) with titanium backup pro and restore later.
Послато са m8 уз помоћ Тапатока
Imotep95 said:
unexpected contents(i think thats some root binaries etc)...
Anyways, check this thread and download stock twrp nand for your 4.16.401.13 firmware from here, follow the steps carefully, it's easy. http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Click to expand...
Click to collapse
Hi I have same problem. I have tried method described in link above but nothings hapen. I got same Error message! My phone is rooted bootloader unlocked but not S-off. Also i have tried to update on Cyanogenmod 13 but no luck same error message.
Please help
DataMan2011 said:
Hi I have same problem. I have tried method described in link above but nothings hapen. I got same Error message! My phone is rooted bootloader unlocked but not S-off. Also i have tried to update on Cyanogenmod 13 but no luck same error message.
Please help
Click to expand...
Click to collapse
You need to find your matching recovery, cant just use whatever u want...
Sent from my HTC One_M8 using Tapatalk
I'm having the same problem. I'm s-off as well and have an unlocked bootloader and stock recovery but my normal rom and I can't update I get the same error message
Edit: I just flashed the stock kitkat unrooted nandroid rom and also flashed the stock recovery and I got the ota updates and now I'm currently on marshmallow thanks for the help everyone c:
adamaliace said:
I'm having the same problem. I'm s-off as well and have an unlocked bootloader and stock recovery but my normal rom and I can't update I get the same error message
Click to expand...
Click to collapse
Either need to install a stock (never rooted) ROM, of you have the wrong stock recovery.
redpoint73 said:
Either need to install a stock (never rooted) ROM, of you have the wrong stock recovery.
Click to expand...
Click to collapse
Thanks I'll try that
Imotep95 said:
You need to find your matching recovery, cant just use whatever u want...
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I have original stock recovery which I downloaded from link you gave us. http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I followed procedure explained in link but no luck with installation OTA update niether CM 13 Nightly build.
DataMan2011 said:
I have original stock recovery which I downloaded from link you gave us. http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I followed procedure explained in link but no luck with installation OTA update niether CM 13 Nightly build.
Click to expand...
Click to collapse
You haven't posted enough information. Posting that you have the "same problem" isn't helpful, and usually leaves us lacking the specific information needed to help you at all.
Do fastboot getvar all, and post the output (delete IMEI and serial number).
Also, is Bootloader is unlocked?
Is the phone currently on stock ROM? Rooted?
What version TWRP?

4.19.161.2 RUU for Vodafone UK (VODAP001) ?

Hi Guys,
I am looking for the 4.19.161.2 RUU for Vodafone UK (VODAP001) , I downloaded one from here but it doesn't launch.
Can anyone help? I have reverted my phone with the 4.19.161.2 nandroid and restored the 4.19.161.2 recovery, i went to do an OTA update and it fails so if someone could help that would be great.
Kind regards
Jamie
Here is an image of what happens when i look at the ota update log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
montythebrave said:
Here is an image of what happens when i look at the ota update log
Click to expand...
Click to collapse
That usually means you have the wrong stock nandroid, or the wrong stock recovery.
What does it say for OS number on your bootloader screen?
redpoint73 said:
That usually means you have the wrong stock nandroid, or the wrong stock recovery.
What does it say for OS number on your bootloader screen?
Click to expand...
Click to collapse
Oh shoot! really?
Does this image help?
montythebrave said:
Oh shoot! really?
Click to expand...
Click to collapse
That is usually what the "fingerprint" error message means, yes.
But in your case, it looks like you properly matched the stock nandroid and stock recovery to your OS (main version) number. I know that probably seemed like a stupid question (that you properly matched those). But you never know, sometimes it pays to check the seemingly obvious stuff first.
So this is the OTA update that was automatically downloaded to your phone when you checked for an update in Settings? Or did you load it manually?
redpoint73 said:
That is usually what the "fingerprint" error message means, yes.
But in your case, it looks like you properly matched the stock nandroid and stock recovery to your OS (main version) number. I know that probably seemed like a stupid question (that you properly matched those). But you never know, sometimes it pays to check the seemingly obvious stuff first.
So this is the OTA update that was automatically downloaded to your phone when you checked for an update in Settings? Or did you load it manually?
Click to expand...
Click to collapse
Yeah I was 100% sure everything matched, thi is just the OTA update it automatically downloaded and tried to install through the settings menu.
montythebrave said:
Yeah I was 100% sure everything matched, thi is just the OTA update it automatically downloaded and tried to install through the settings menu.
Click to expand...
Click to collapse
That's odd, I don't see why the OTA is failing then. Software says "Official" on the bootloader screen?
You might also try the stock nandroid and stock recovery files for 4.19.161.3. Again, you properly matched the OS number (and .3 actually doesn't match). But I don't think it hurts anything to try.
redpoint73 said:
That's odd, I don't see why the OTA is failing then. Software says "Official" on the bootloader screen?
You might also try the stock nandroid and stock recovery files for 4.19.161.3. Again, you properly matched the OS number (and .3 actually doesn't match). But I don't think it hurts anything to try.
Click to expand...
Click to collapse
But if it doesnt match isint this a waste of time?
I was really looking for the RUU file so I can 100% put it back to stock.
montythebrave said:
But if it doesnt match isint this a waste of time?
Click to expand...
Click to collapse
Not necessarily. Sometimes the files will work, when the numbers are that close together.
I don't know of or have access to the RUU for your version number, so I'm trying to think out of the box here.
montythebrave said:
Here is an image of what happens when i look at the ota update log
View attachment 3668710
Click to expand...
Click to collapse
redpoint73 said:
Not necessarily. Sometimes the files will work, when the numbers are that close together.
I don't know of or have access to the RUU for your version number, so I'm trying to think out of the box here.
Click to expand...
Click to collapse
His mistake is wrong recovery version. He is using the old KitKat recovery 2.22.161.6 to update 4.19.161.2 to 4.19.161.3
The error clearly stated "this device has htc/vodafone_uk/htc_m8:4.4.3/KTUL84L" recovery image
but the expected recovery is htc/vodafone_uk/htc_m8:5.0.1/LRX22C
ckpv5 said:
His mistake is wrong recovery version. He is using the old KitKat recovery 2.22.161.6 to update 4.19.161.2 to 4.19.161.3
The error clearly stated "this device has htc/vodafone_uk/htc_m8:4.4.3/KTUL84L" recovery image
but the expected recovery is htc/vodafone_uk/htc_m8:5.0.1/LRX22C
Click to expand...
Click to collapse
Aaaah ok so which recovery should i install? I appreciate your help
montythebrave said:
Aaaah ok so which recovery should i install? I appreciate your help
Click to expand...
Click to collapse
As written above, you need to install either 4.19.161.2 or 4.19.161.3 stock recovery image as you're updating from 4.19.161.2 to 4.19.161.3
ckpv5 said:
As written above, you need to install either 4.19.161.2 or 4.19.161.3 stock recovery image as you're updating from 4.19.161.2 to 4.19.161.3
Click to expand...
Click to collapse
I downloaded a link on this forum which said it was the 4.19.161.2 stock recovery but it must of been incorrect, do you have a link for it?
Kind Regards
Jamie
ckpv5 said:
As written above, you need to install either 4.19.161.2 or 4.19.161.3 stock recovery image as you're updating from 4.19.161.2 to 4.19.161.3
Click to expand...
Click to collapse
I just found this - http://forum.xda-developers.com/showthread.php?p=62516597#post62516597 and downloaded and flashed 4.19.161.3 recovery: https://mega.nz/#!3U8hmQBT!nxY_ZG-5P...Sy8VZ7VtazWFzw
It all seemed to update fine now, thank you so much for your help!
I have 1 last problem, i have the supersu installer on my phone and i want to remove it, how do I go about doing that?
Infact, the update hasnt went very well....
it boots up the htc splash screen then it goes to a black screen and nothing... its went from bad to worse , any suggestions?
I managed to get into the the recovery log, here is what it reports (i took the sd card out to see if it would boot without it in case this was causing it to fail to load)
You can't use a rooted ROM to OTA.
You need a non-rooted ROM for that.
Read and everything that you need is linked in my signature.
Restore 4.19.161.2 backup and its stock recovery then try again.
I can't always reply because I'm on holiday in Krabi, Thailand.
I have only 50mb free data daily.
ckpv5 said:
You can't use a rooted ROM to OTA.
You need a non-rooted ROM for that.
Read and everything that you need is linked in my signature.
Restore 4.19.161.2 backup and its stock recovery then try again.
I can't always reply because I'm on holiday in Krabi, Thailand.
I have only 50mb free data daily.
Click to expand...
Click to collapse
When I create a backup with the latest TWRP it says successful, i then reboot into recovery again and mount data and i see the twrp folder but when i go into it, it is blank.

Having trouble flashing ota after returning to stock.

Hi guys. I need ur help on this one .
I've had the m8 since new and first things I did was unlock bootloader to install custom roms. The phone was never s-off !
So, I've been having connectivity problems and I have to bring it in to have it looked at. But my current provider(Eastlink) won't support rooted phones or phones with custom roms. So since last night I decided to put it right back to stock and update it. This is where I ran into problems and the problems I've found are most likely what is causing the initial connectivity problems.
So I restored my original nandroid backup, flashed original recovery and went to do the ota update which will update the phone to MM. But when it flashes the OTA it always comes up with a (status 7) installation aborted with this message ... (see pic) something about was expecting build fingerprint of htc/Rogers_wwe but mine has htc_europe.
Also, there is no OS version in bootloader(see pic).
Any help would greatly appreciated.
Thanks
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
redpoint73 said:
You restored the wrong stock ROM and/or wrong stock recovery.
OS number missing is a symptom of using a very outdated version of TWRP (known bug).
Click to expand...
Click to collapse
Thanks for the reply. I was thinking that it could be a wrong stock recovery but the stock rom is a nandroid backup I had taken when I bought the phone.
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
rogerrulez said:
THe version of twrp I've been using is twrp-3.0.2-0-m8.img
Click to expand...
Click to collapse
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Oh, ok thanks for clearing that up. Makes sense.
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
http://forum.xda-developers.com/showthread.php?t=2694297
redpoint73 said:
I see you've had the device a long time, and unlocked bootloader right away. So you had an older version TWRP at one time, which wipes the OS number. Updating to a new TWRP does not fix the problem. The only way OS number will show up again is if firmware is installed by flashing firmware.zip, RUU, OTA, etc.
Click to expand...
Click to collapse
Also I wanted to mention was that I'm pretty sure I had the stock recovery which was on my computer with the htc m8 stuff since Jan, 2015. But that one doesn't seem to be working. But I could be wrong on that. It could be from a different phone now that I look at that folder more closely.
rogerrulez said:
Any idea where I can find the correct recovery ? I was thinking of asking this member ?
Click to expand...
Click to collapse
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
redpoint73 said:
What's the software number (phone Settings>About>Software information>More>Build number) now that you restored the stock ROM nandroid you made previously?
Click to expand...
Click to collapse
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
rogerrulez said:
I'll check as soon as the phone boots up. But I think I may have found the problem with recovery. I'll post results back soon. I think I was trying to flash the stock recovery with the bootloader locked. Long night ... :\
Update: Build number is 4.20.631.3 CL463267 release-keys
Going to try the ota right now ...
Click to expand...
Click to collapse
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
rogerrulez said:
Same result but with a different message. Now it says htc/rogers_wwe/htc_m8:5.0.1/LRX22C/463267.2:user/release-key.
Click to expand...
Click to collapse
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
ckpv5 said:
Your recovery version is wrong.
It expect recovery version 4.20.631.3 or 6.13.631.7 but you installed 4.20.631.2
Click to expand...
Click to collapse
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
rogerrulez said:
Thanks ! Ok, I'll try it again. I just flashed 4.20.661.3_recovery.img But I'm not sure if this is a Rogers recovery or international.
Hopefully that works ...
Click to expand...
Click to collapse
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
rogerrulez said:
Did not work. Apparently this recovery was for a Telus device. I need a Rogers recovery.
Anyone have a link to one that's required ?
Click to expand...
Click to collapse
Check the backup thread linked in my signature. Everything you need are there.
ckpv5 said:
Check the backup thread linked in my signature. Everything you need are there.
Click to expand...
Click to collapse
Hi ckpv5,
I installed one of ur stock recoveries 4.20.631.3_recovery from ur collection, and now I am getting this error while doing the OTA.(see attached pic).
Any ideas ?
Update ...
I decided to go and flash the firmware.zip file from within the OTA file. It flashed ok and I now have an OS version in the bootloder.
But now it won't go any further then going to the bootloader, which I have to force into. Goes to black screen.
I then tried to flash the OTA file the same way "fastboot flash zip RUU.zip(renamed) and it fails to flash. So now I am soft bricked.
Never been in this situation before and need some advice please !
Solved!
After flashing the firmware from the OTA zip file I forgot that everything would be wiped. So here's what I did ...
1. Unlock bootloader.
2. Flash recovery.
3. Restore nandroid backup.
4. Boot up then shut down and flash proper version of stock recovery.
5. Relock bootloader.
6. Install OTA !
Thanks guys for all ur help

Categories

Resources