Related
Hey guys,
Apologies if this has already been covered before; I've just tried flashing a stock recovery back onto my One (after using TWRP) to apply an OTA update but when I boot into recovery it comes up with an image of the phone and a red exclamation mark/triangle and doesn't appear to go into recovery at all - this also happens when I try applying the OTA update after downloading it.
What am I doing wrong here? I've booted the phone into fastboot, run fastboot flash recovery [recovery image name] from the command prompt and everything appears to work but there's just no recovery.
Software version is 1.12.710.17, had downloaded the appropriate recovery image.
I've also had Xposed installed, but have tried disabling it as well which doesn't seem to help.
EDIT: Have tried flashing via fastboot again, then accessing recovery through hboot and it comes up with "no image or wrong image" (this is while entering hboot menu, not into recovery). Phone is rooted and has S-OFF, I don't understand why it isn't saving the recovery image?
DOUBLE EDIT: I can flash custom recoveries via fastboot fine, although I still get the "no image or wrong image" message when entering the hboot menu (although I can actually get to recovery). Much confusion, such frustration. Wow.
BJ van Beethoven said:
Hey guys,
Apologies if this has already been covered before; I've just tried flashing a stock recovery back onto my One (after using TWRP) to apply an OTA update but when I boot into recovery it comes up with an image of the phone and a red exclamation mark/triangle and doesn't appear to go into recovery at all - this also happens when I try applying the OTA update after downloading it.
What am I doing wrong here? I've booted the phone into fastboot, run fastboot flash recovery [recovery image name] from the command prompt and everything appears to work but there's just no recovery.
Software version is 1.12.710.17, had downloaded the appropriate recovery image.
I've also had Xposed installed, but have tried disabling it as well which doesn't seem to help.
EDIT: Have tried flashing via fastboot again, then accessing recovery through hboot and it comes up with "no image or wrong image" (this is while entering hboot menu, not into recovery). Phone is rooted and has S-OFF, I don't understand why it isn't saving the recovery image?
DOUBLE EDIT: I can flash custom recoveries via fastboot fine, although I still get the "no image or wrong image" message when entering the hboot menu (although I can actually get to recovery). Much confusion, such frustration. Wow.
Click to expand...
Click to collapse
Where did you get the recovery image from? did you extract it from the OTA?
exad said:
Where did you get the recovery image from? did you extract it from the OTA?
Click to expand...
Click to collapse
Negative, I got the recovery image from this thread here:
http://forum.xda-developers.com/showthread.php?t=2701376
Just extract it from your OTA zip file. it will be in the firmware.zip file. You'll have to use 7zip or something to extract it.
exad said:
Just extract it from your OTA zip file. it will be in the firmware.zip file. You'll have to use 7zip or something to extract it.
Click to expand...
Click to collapse
Thanks for the advice, gave it a try but I'm still stuck at square one it seems. I try and boot to recovery after flashing and it comes up with the image of the phone with the red exclamation mark/triangle still.
BJ van Beethoven said:
Thanks for the advice, gave it a try but I'm still stuck at square one it seems. I try and boot to recovery after flashing and it comes up with the image of the phone with the red exclamation mark/triangle still.
Click to expand...
Click to collapse
press and hold volume up then press power.
exad said:
press and hold volume up then press power.
Click to expand...
Click to collapse
Thank you sir! I'd been holding power which was rebooting the phone.
That's at least got me into recovery, but now when I try and apply the OTA file via recovery it comes up with "/system/lib/modules/a8293.ko" has unexpected contents. Installation aborted.
It's a never-ending battle! Hahah.
Actually I am using a custom kernel as well, could that be the problem?
BJ van Beethoven said:
Actually I am using a custom kernel as well, could that be the problem?
Click to expand...
Click to collapse
yep
Figured as much. I can't seem to find a standard kernel anywhere, looks like I may have to revert back to a stock image and start again.
BJ van Beethoven said:
Figured as much. I can't seem to find a standard kernel anywhere, looks like I may have to revert back to a stock image and start again.
Click to expand...
Click to collapse
Yeah you will
exad said:
Yeah you will
Click to expand...
Click to collapse
Damn, no worries. Thanks for your help!
Got the update applied finally, managed to find a backup I'd made before flashing the custom kernel. Flashed back to stock recovery, applied the OTA and all good!
OTA Update Problem.
BJ van Beethoven said:
Got the update applied finally, managed to find a backup I'd made before flashing the custom kernel. Flashed back to stock recovery, applied the OTA and all good!
Click to expand...
Click to collapse
Sorry Im a bit of a Noob but I'm trying to get the new OTA update.
I rooted with hasoon's toolkit, Ive changed nothing on my phone except for installing some root only apps from the playstore.
My current firmware is 1.12.502.18
How do I go about getting my OTA update? I cant seem to find a link that explains this clearly.
Thank you for your time.
HTC One M8
AT&T
isaythings said:
Sorry Im a bit of a Noob but I'm trying to get the new OTA update.
I rooted with hasoon's toolkit, Ive changed nothing on my phone except for installing some root only apps from the playstore.
My current firmware is 1.12.502.18
How do I go about getting my OTA update? I cant seem to find a link that explains this clearly.
Thank you for your time.
HTC One M8
AT&T
Click to expand...
Click to collapse
Do you have the OTA update available to you at the moment? And have you flashed a custom recovery at all?
exad said:
Yeah you will
Click to expand...
Click to collapse
Hey @exad it seems I've run into the same problem as BJ van Beethoven... but I don't have a stock Kernel.. I noticed you're on Telus (so am I) you wouldn't happen to have a stock kernel from the last update would you? or could I use the one from the OTA I just downloaded? I made a copy and can unzip it and try to flash it.. I'm currently on 1.55.661.4 firmware.
thanks!!!!!
having the same issue
exad said:
Yeah you will
Click to expand...
Click to collapse
I am having the same issue only problem is I don't have a backup of my original stock. But I get the same error after flashing a stock Rom any help to how I can fix this issue. Thanks in advance
Hey Guys,
my HTC One M8 ran on GPE 4.4.3, but today came an OTA update, which I wanted to install.
So I clicked install and my phone restarted to TWRP and the update wasn't installed.
Then I found this tutorial and tried it.
http: / / htc-one.wonderhowto.com/how-to/update-your-rooted-google-play-edition-htc-one-4-4-3-without-losing-any-data-0155404/
After flashing the OTA my boot loader menu turned black (image) and i wasn't able to install any Roms, also my phone sucks on boot screen.
Image: http: / / files.tobii5.de/assets/files/1/htc.png
Is it bricked?
I don't know what to do, please help me
Help
Please help me
It's certainly not bricked if you can access the boot loader.
Which recovery have you got installed now?
ashyx said:
It's certainly not bricked if you can access the boot loader.
Which recovery have you got installed now?
Click to expand...
Click to collapse
I use TWRP 2.7.1.0 and here is a screenshot of the error, showed while trying to flash a rom
http: / / files.tobii5.de/assets/files/1/twrp_error.JPG
It was a GPE OTA? Reflash a full GPE ROM
Sir-Fix-a-Lot said:
It was a GPE OTA? Reflash a full GPE ROM
Click to expand...
Click to collapse
The device is an regular "sense-device", but i flashed a GPE Rom, and after i wanted to flash the GPE 4.4.4 OTA update, it crashed.
And the screenshot of my last post was taken, when i tried to flash the GPE Rom again.
Tobii5 said:
The device is an regular "sense-device", but i flashed a GPE Rom, and after i wanted to flash the GPE 4.4.4 OTA update, it crashed.
And the screenshot of my last post was taken, when i tried to flash the GPE Rom again.
Click to expand...
Click to collapse
Could you try a different ROM please? I would recommend SlimKat, and going from there if you want to change.
Sir-Fix-a-Lot said:
Could you try a different ROM please? I would recommend SlimKat, and going from there if you want to change.
Click to expand...
Click to collapse
I think this wouldn't change anything, because i also can't restore a sense backup, i've made after rooting my phone.
But i wonder, why my boot loader menu changed its background to black. I guess, i have to refresh the stock boot loader, but i don't know how to do that.
Tobii5 said:
I think this wouldn't change anything, because i also can't restore a sense backup, i've made after rooting my phone.
But i wonder, why my boot loader menu changed its background to black. I guess, i have to refresh the stock boot loader, but i don't know how to do that.
Click to expand...
Click to collapse
At any point did you do the GPE conversion?
im having the same problem also. I have no OS. I have a rom on my mem but it wont flash and when i boot up my device it shows a unlocked lock that wasnt there before
I'm sorry i accidentally deleted your reply but everything seems to be working. I reflashed TWRP. Im going to flash a rom and see if it works. Thanks alot for your help.
xxnatanxx said:
I'm sorry i accidentally deleted your reply but everything seems to be working. I reflashed TWRP. Im going to flash a rom and see if it works. Thanks alot for your help.
Click to expand...
Click to collapse
This a different thread, my reply is in your thread
Sir-Fix-a-Lot said:
This a different thread, my reply is in your thread
Click to expand...
Click to collapse
i have so many tabs open but thanks tho.
My Phone showes a unlockt icon too.
I have tried to reflash my recovery, but nothing changed
Ok, my phone is working again, i just flashed an RUU of GPE
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
Hi guys, my nexus 5x is locked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
MaxOptim said:
If flashing full stock (all not only system) and full wiping doesn't solve your issue sounds like the infamous hardware problem.
Make sure you didn't restore efs backup taken with twrp 3.0.2.1 otherwise look for efs fix.
Click to expand...
Click to collapse
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
ybregeon2016 said:
And how to perform was fix when I can't access Android, fastboot is limited due to locked bootloader and recovery is stock? What's the procedure?
Click to expand...
Click to collapse
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
MaxOptim said:
You can't.
If you have a locked bootloader all you can do is to flash a full ota package from stock recovery and to wipe/factory reset if it let you to.
If it doesn't fix your issue unfortunately you have to RMA the phone.
Click to expand...
Click to collapse
Forgive my ignorance but how can I do this?
ybregeon2016 said:
Forgive my ignorance but how can I do this?
Click to expand...
Click to collapse
follow instructions here: https://developers.google.com/android/ota
MaxOptim said:
follow instructions here: https://developers.google.com/android/ota
Click to expand...
Click to collapse
Actually I was talking about the RMA, I bought it in Egypt.
ybregeon2016 said:
Actually I was talking about the RMA, I bought it in Egypt.
Click to expand...
Click to collapse
ah, no idea then, sorry.
ybregeon2016 said:
Hi guys, my nexus 5x is unlocked bootloader and i was running the last Android 7.1.1 stock. I decided to try the last CM14.1, entered TWRP and made a backup. I installed CM14.1 and gapps and my phone was in a bootloop. I decided then to restore my backup, restoration was successful but when i pressed reboot system, I was in a bootloop, at Google dots logo. I flashed successfully the DP 7.1.1 image but couldn't get out the bootloop. Flashed the last stock 7.0 image with the same result. I can access fastboot and recovery but until now couldnt get my phone to start and get out this bootloop. What can I do? Is it a hardware issue as i read somewhere on XDA?
Any help and advices please, I live in a country with no Google service center and I am desperate.
Click to expand...
Click to collapse
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
dominoeflux said:
when you restored from your backup, was EFS checked when you restored? if it was then you have an EFS file corruption. I personally wrote up a solution to this, here's a link: http://forum.xda-developers.com/nexus-5x/help/efs-file-corruption-fix-t3502473
make sure you follow the instructions, this has to be done with the Nexus root toolkit command window open with your phone in TWRP recovery and hooked up to your computer. if you try this, let me know how it goes and if you need help.
edit: your bootloader is unlocked which I know for sure, you can still boot into bootloader and re-root and install twrp back onto your phone even though you're boot looping. I know because the same thing happened to me and was still able to flash a custom recovery.
Click to expand...
Click to collapse
Man i remind you that my bootloader is locked and for this reason can't start twrp.
ybregeon2016 said:
Man i remind you that my bootloader is locked and for this reason can't start twrp.
Click to expand...
Click to collapse
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
dominoeflux said:
In your original post you said it was unlocked....and how can it be locked when you don't mention locking it flashing it back stock?
Click to expand...
Click to collapse
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
ybregeon2016 said:
Bad typing, my bootloader is locked. It was unlocked then after flashing a firmware with LGUP it was locked again.
Click to expand...
Click to collapse
Oohhh OK I got you...have you been able to look in doing a tot recovery with Odin? I'm almost home so I'll see what I can do to help u out
Edit: have u tried unlocking it again in bootloader?
LGUP install a firmware as a TOT, it was a TOT file. Isnt Odin for Samsung phones?
tauio111 said:
Yeah it is the EFS problem related to buggy versions of TWRP. Just use dd to to clear the EFS partitions - the chipset will luckily autogenerate the EFS contents on first boot.
Next time dont restore EFS partition from your backups and everything will be perfectly okay.
Makes me wonder how many hundreds of people have sent the device to RMA because of this issue.
Click to expand...
Click to collapse
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
ybregeon2016 said:
Forgive me but what is DD?
I have a locked bootloader with stock recovery. What is this DD you are talking about? Will it be successful with this bootloader and stock?
Click to expand...
Click to collapse
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
tauio111 said:
try this command: fastboot flashing unlock when in bootloader mode.
If it works flash TWRP and do the guide which was mentioned before my previous post.
Click to expand...
Click to collapse
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
ybregeon2016 said:
This command is to unlock the bootloader right? But I guess if the OEM unlock is not selected in developer options within Android, it won't work, or correct me if I am wrong.
Click to expand...
Click to collapse
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
tauio111 said:
You can try. I heard somewhere that it may work if you apply it before booting the android the first time (technically your android cant boot at the moment).
Click to expand...
Click to collapse
Failed (remote: OEM unlock is not allowed)
I haven't heard anything about an working method for backup stock recovery in A/B partition system, anyone knows how to do that? I already tried adb, Flashfire, TWRP, there's no recovery partition, help
All3nS3mpai said:
I haven't heard anything about an working method for backup stock recovery in A/B partition system, anyone knows how to do that? I already tried adb, Flashfire, TWRP, there's no recovery partition, help
Click to expand...
Click to collapse
Yeah, there is no recovery partition in our phone... Why do you want to backup it?
Technical said:
Yeah, there is no recovery partition in our phone... Why do you want to backup it?
Click to expand...
Click to collapse
Because i want to install a custom one(TWRP) and still able to reinstall the stock if a new OTA is released
All3nS3mpai said:
Because i want to install a custom one(TWRP) and still able to reinstall the stock if a new OTA is released
Click to expand...
Click to collapse
You will brick your phone as simple as that... You cannot use slots A/B with stock and AOSP simultaneously.
Read the guides on my signature and take care.
Technical said:
You will brick your phone as simple as that... You cannot use slots A/B with stock and AOSP simultaneously.
Read the guides on my signature and take care.
Click to expand...
Click to collapse
And I don't want to, what I'm trying to say is that if I want to go back to stock I can do it fully, including recovery, I don't want to have two systems installed at the same time, just stock or AOSP. And thanks for that post, I'll check it, I'm new in this.
All3nS3mpai said:
And I don't want to, what I'm trying to say is that if I want to go back to stock I can do it fully, including recovery, I don't want to have two systems installed at the same time, just stock or AOSP. And thanks for that post, I'll check it, I'm new in this.
Click to expand...
Click to collapse
If you return to stock, the recovery is included. You don't need the stock recovery to go back to stock ROM. There is also a guide for "returning to stock".
Technical said:
If you return to stock, the recovery is included. You don't need the stock recovery to go back to stock ROM. There is also a guide for "returning to stock".
Click to expand...
Click to collapse
Even if the zip file doesn't include a recovery.img?
All3nS3mpai said:
Even if the zip file doesn't include a recovery.img?
Click to expand...
Click to collapse
Recovery is in our boot.img. Flash that and you'll have stock recovery.
Technical said:
If you return to stock, the recovery is included. You don't need the stock recovery to go back to stock ROM. There is also a guide for "returning to stock".
Click to expand...
Click to collapse
Does unlocking the bootloader stops the phone from receiving OTA?