I have a SIM free M8 running stock 2.22.401.5 (inc recovery) but S-Off.
Got the OTA notification and selected to install it. It reboots to stock recovery but after a few seconds when the green progress bar is about a 1/3 full, it stops and a red warning triangle appears.
After a couple more minutes the phone reboots and is still on the old version. Tried again but the same result.
Any advice would be warmly welcomed.
Any errors messages?
HTC One M8
Elisha said:
Any errors messages?
HTC One M8
Click to expand...
Click to collapse
None at all.
I dont believe it matters as the last OTA was successful, but I am also superCID and bootloader unlocked.
I've also just wiped the cache partition using stock recovery but still no dice.
Did you installed any system mods? Like H/K sound mod or custom kernel?
K-a-M-u-Z-u said:
Did you installed any system mods? Like H/K sound mod or custom kernel?
Click to expand...
Click to collapse
No. I haven't even rooted since the previous ota.
stuart0001 said:
No. I haven't even rooted since the previous ota.
Click to expand...
Click to collapse
maybe a stupid question, but do you have enough free space on the device?
K-a-M-u-Z-u said:
maybe a stupid question, but do you have enough free space on the device?
Click to expand...
Click to collapse
Yep, 6GB of internal free.
I feel a factory reset impending.
stuart0001 said:
Yep, 6GB of internal free.
I feel a factory reset impending.
Click to expand...
Click to collapse
If you are going to do a factory reset, you can save all your data easily.
you can flash TWRP recovery, make a backup of DATA partition, Wipe factory reset and reflash Stock recovery, apply the OTA.re flash TWRP recovery again and Restore only DATA partition backup.after that you can revert back to stock recovery if that your wish.
this way you will have all you user data with a clean SYSTEM partition without having to install and reconfigure all your system from scratch.
K-a-M-u-Z-u said:
If you are going to do a factory reset, you can save all your data easily.
you can flash TWRP recovery, make a backup of DATA partition, Wipe factory reset and reflash Stock recovery, apply the OTA.re flash TWRP recovery again and Restore only DATA partition backup.after that you can revert back to stock recovery if that your wish.
this way you will have all you user data with a clean SYSTEM partition without having to install and reconfigure all your system from scratch.
Click to expand...
Click to collapse
That's great advice Thank you. [emoji106]
I'm still getting the same issue after a factory reset. Any ideas?
Do I need to relock my bootloader?
stuart0001 said:
I'm still getting the same issue after a factory reset. Any ideas?
Do I need to relock my bootloader?
Click to expand...
Click to collapse
Your phone is not rooted?
Edit: I read the previous posts and i think is because u have SuperCID, i think u must have your original CID.
same here.. i also flashed the 3.xx update. im on s-off, supercid and my custom rom was viperone 2.5... when i was flashing the update, error 24 appeared. im already on supercid so i wonder why would it fail. so i reflashed the previous firmware which is 2.22.401.5.. it went well but then when im alrady on my homescreen, i notice that i don't have a signal from my mobile network and after a few minutes the phone restarts. could you help me?
I'm officially a dumbass. I managed to open the stock recovery right after it failed and saw the issue. It said.
platform.xml unexpected content
This was from when I applied a previous SD card write fix patch.
After reflaahing a stock ROM it updated fine.
A couple of things puzzle me though. Why did the system restore not revert this file to original and why did the last OTA go through ok when I'd had the patch installed prior to that also.
Related
I'm selling an HTC One V and I would like to flash the kernel back to stock (it's currently on Titanium).
I've tried the All In One Toolkit kernel flash option, wiped cache and davlik (and even full factory wipe), tried restoring from my CWM nandroid backup.
Restoring always seems to go OK with no errors, but whenever I got to About in phone settings it still shows the kernel as Titanium.
Any ideas?
britbloke said:
I'm selling an HTC One V and I would like to flash the kernel back to stock (it's currently on Titanium).
I've tried the All In One Toolkit kernel flash option, wiped cache and davlik (and even full factory wipe), tried restoring from my CWM nandroid backup.
Restoring always seems to go OK with no errors, but whenever I got to About in phone settings it still shows the kernel as Titanium.
Any ideas?
Click to expand...
Click to collapse
did you relock the bootloader 1st?
Hi
Relock bootloader and use the RUU
Thats IMHO the easiest to get it back to stock
Regards
max
No, I didn't relock the bootloader. I'm a noob at kernel flashing so I didn't realize that I had to do that.
There's no RUU for my Canadian Koodo One V, so I can't revert to stock that way.
britbloke said:
There's no RUU for my Canadian Koodo One V, so I can't revert to stock that way.
Click to expand...
Click to collapse
Sorry - didnt know that
regards
max
britbloke said:
No, I didn't relock the bootloader. I'm a noob at kernel flashing so I didn't realize that I had to do that.
There's no RUU for my Canadian Koodo One V, so I can't revert to stock that way.
Click to expand...
Click to collapse
contact football he might be able to get you the RUU might cost you 11euro's though
My M7 had quite the meltdown yesterday, highlighted by what seems to be a corruption of my cache partition. Long, long story short, I was able to use the ruu to 2.10.605, where everything seemed fine. Funny enough, I kept s-off and an unlocked bootloader through the process.
I was content to keep the phone as is, since my f'ing with it surely caused the cache issue. But, to be safe, I rerooted, installed CWM (TWRP will not install for me, despite a dozen efforts), and backed up. Then, to see if the problem had been solved, I tried to wipe cache, but no dice. I won't be installing original ROMs anymore, it seeems. Not a huge deal since I at least have a functional phone, but now it has downloaded 4.4 and wants to update. A couple of questions:
Should I assume that the update will likely run into cache-related issues?
Will the update relock the bootloader and/or return the phone to S-on?
If either of these is a yes, I'm thinking about using the 2.10 ruu again, returning everything as was, and then installing santod's OTA killer. I can live with 4.3 on this phone for another year - not ideal, but considering the alternatives...
Thanks in advance to anyone who might have an idea about all this.
dmdubois said:
My M7 had quite the meltdown yesterday, highlighted by what seems to be a corruption of my cache partition. Long, long story short, I was able to use the ruu to 2.10.605, where everything seemed fine. Funny enough, I kept s-off and an unlocked bootloader through the process.
I was content to keep the phone as is, since my f'ing with it surely caused the cache issue. But, to be safe, I rerooted, installed CWM (TWRP will not install for me, despite a dozen efforts), and backed up. Then, to see if the problem had been solved, I tried to wipe cache, but no dice. I won't be installing original ROMs anymore, it seeems. Not a huge deal since I at least have a functional phone, but now it has downloaded 4.4 and wants to update. A couple of questions:
Should I assume that the update will likely run into cache-related issues?
Will the update relock the bootloader and/or return the phone to S-on?
If either of these is a yes, I'm thinking about using the 2.10 ruu again, returning everything as was, and then installing santod's OTA killer. I can live with 4.3 on this phone for another year - not ideal, but considering the alternatives...
Thanks in advance to anyone who might have an idea about all this.
Click to expand...
Click to collapse
Question for you...
Where did you get your Recoveries from that you installed or tried to install?
Did you grab the versions for the m7vzw in our Verizon HTC One Original Development section?
Or did you install one intended for the International m7?
santod040 said:
Question for you...
Where did you get your Recoveries from that you installed or tried to install?
Did you grab the versions for the m7vzw in our Verizon HTC One Original Development section?
Or did you install one intended for the International m7?
Click to expand...
Click to collapse
Yes, I got them from this site, under that section. I just installed Phil's CWM, which booted, and allowed me to clear the cache (!), but now I can't install a rom. I tried your NuSense Max and your odexed 4.42....in both cases I got a status 7 error. (Before I tried either one, I updated the firmware, fyi.)
Fortunately Phil's CWM backup process is simpler and faster. Unless there are other suggestions, I think I'll tried flashing your OTA killer and live with 4.3
Thanks again.
dmdubois said:
Yes, I got them from this site, under that section. I just installed Phil's CWM, which booted, and allowed me to clear the cache (!), but now I can't install a rom. I tried your NuSense Max and your odexed 4.42....in both cases I got a status 7 error. (Before I tried either one, I updated the firmware, fyi.)
Fortunately Phil's CWM backup process is simpler and faster. Unless there are other suggestions, I think I'll tried flashing your OTA killer and live with 4.3
Thanks again.
Click to expand...
Click to collapse
Twrp 2.6.3.3 or 2.6.3.4 will install those Roms.
You can always do fastboot erase cache
That will clear the cache.
Until a newly installed recovery has booted into the OS once, it usually won't clear cache.
Sent from my HTC6435LVW using Tapatalk
santod040 said:
Twrp 2.6.3.3 or 2.6.3.4 will install those Roms.
You can always do fastboot erase cache
That will clear the cache.
Until a newly installed recovery has booted into the OS once, it usually won't clear cache.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
It worked.
I don't know what in the hell I've been doing (I swear that's the same TWRP file I've been using) but, just like that, it booted, and successfully installed your NuSense Max Rom. No more 4.3, no cache issues, no more worry about OTAs. You're the man!
Thanks a million.
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
houston33 said:
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
Click to expand...
Click to collapse
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
xunholyx said:
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
Click to expand...
Click to collapse
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
408
so from where i am now i can just go to twrp and install android rev 21? or do i have to use adb sideload?
is 21 even compatible?
i swore i wasnt gonna mess on with this phone.........
houston33 said:
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
Click to expand...
Click to collapse
You sure can. The newer firmware is needed for 4.4.4 ROMs. If you had 2.5, reflash it. It will work with the newest firmware as well. Just not the old stuff.
Here's a pointer: A dirty flash of the ROM you are currently running will reset your tweaks, and often fix problems you are having. When I start having glitches, I first reboot. If that didn't work; and I can't find a solution on XDA easily, I reflash my ROM; the dirty way. It really does help to clear up stuff, especially if you are using themes and tweaks.
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
houston33 said:
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
Click to expand...
Click to collapse
In TWRP, you can manage files easily.
Click advanced > file manager
There you can copy files, move them and change permissions. Plus deleting and renaming them.
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Vesten said:
Right, so. Managed to unlock and root my M9 successfully, no problems, using a good guide, which included making a Nandroid backup prior to rooting.
So I decide to get rid of LeeDroid and restore my Nandroid backup. All went well. Then TWRP asks if I want to install SuperSU as my device isn't rooted. So swipe yes, and it goes through the usual list, and just as it gets to the last line my phone goes off, and reboots.
I've tried both the stable and beta and always get the same damn crash/reboot, tried the mounting methods, but NOTHING works!
Could anyone shed any light as to why? It's the GSM variant of the M9.
Click to expand...
Click to collapse
what exact version of twrp?
Is the backup a system IMAGE backup?
are you entering TWRP in read-only mode?
When you try to restore now, what does the terminal output say?
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Vesten said:
TWRP version 2.8.7.0
The backup was made using TWRP after flashing it for the first time, which included the usual data, system, etc.
Not sure about TWRP entering read only mode. I read it only does this on unmodified software. Mine is still saying modified even after restoring my nandroid.
Also unsure of what the terminal says without copying the log. Can restore it as many times as I want.
Can't be much more help until I get to a PC.
I'm still S-On, etc. Have a feeling it's to do with the TWRP read only thing...
Click to expand...
Click to collapse
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
I'll have to check, but don't think it does.
I'll try that new version of TWRP and report back.
Many thanks for the help, greatly appreciated.
jollywhitefoot said:
well, when you go to restore twrp, does it say unable to wipe system/cache, etc?
If so, go into the mount menu and put a check mark in the system read only box, then uncheck it and try to restore again.
If that doesn't work, try updating to the latest twrp, which is 2.8.7.1. http://forum.xda-developers.com/devdb/project/?id=8915#downloads
Click to expand...
Click to collapse
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Vesten said:
Flashed that latest TWRP. Then tried flashing SuperSU. Same thing. Just shuts off completely and reboots back to Android.
In the mount menu, system is unchecked. and the bottom "Only mount system read-only" is also unchecked.
The Terminal log gets to..
"Placing files..."
Restoring files..."
Then shuts off. I'm starting to think I'm going to have to flash a stock RUU and start from scratch.
BTW this is after checking system. It seems to do nothing at all.
EDIT: Would not having an external SD in it matter at all? I originally flashed SuperSU using the internal SD card.
Click to expand...
Click to collapse
What happens when you restore your backup and reboot without installing supersu?
jollywhitefoot said:
What happens when you restore your backup and reboot without installing supersu?
Click to expand...
Click to collapse
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Vesten said:
Will let you know soon. Just restoring again.
When I made the Nandroid backup, there's a new option to backup recovery too, which I did. Could this mean anything? I'm assuming it's backed up TWRP because stock obviously wasn't present when making the backup.
Will try and screenshot the log.
Click to expand...
Click to collapse
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
jollywhitefoot said:
Yeah backing up recovery doesn't matter....as you suspected it just backs up twrp, so if you backed up the older version, then updated it, don't restore the old version
Click to expand...
Click to collapse
Interesting. There's nothing saying it couldn't write anything..
Just tried opening SuperSU from my restored backup, and hits me with "There is no SuperSU binary installed!" This is a problem, blah, blah, etc.
Then tried check-boxing the 'system' box in the Mount section. Then tried flashing UPDATESuperSu.VsXX and just gave me the usual as said above. Crashed and reboots.
https://www.dropbox.com/s/cvkclw8xuzua4u3/2015-07-20 21.56.37.png?dl=0
Losing the will to live! Ha
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Vesten said:
What about trying to push SuperSU via ADB?
EDIT: Think I'm getting ahead of myself. Not possible to flash SuperSU via ADB is it..?
Click to expand...
Click to collapse
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
jollywhitefoot said:
The only way I ever do it is by swiping to install as I'm rebooting out of recovery.
Click to expand...
Click to collapse
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Vesten said:
Would you say the nuclear option would be to sit and bide my time until a decent RUU becomes available and start from scratch?
Click to expand...
Click to collapse
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
jollywhitefoot said:
What's your ultimate goal? Stock, rooted? What cid and firmware are you on?
Click to expand...
Click to collapse
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Vesten said:
Well I was going to sell the phone, since it's only 2 weeks old, and obviously for warranty reasons. So back to 100% stock, which includes it saying Software Status: Official and it saying "Locked" instead of re-locked.
CID is HTC__001
Firmware is Lollipop 5.0.2 - Software version 1.40.401.8 (CL549783 release-keys)
Click to expand...
Click to collapse
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
jollywhitefoot said:
Then yeah, just ruu back to stock and bobs your uncle. You don't have to wait, an ruu is available for 1.40.401
Click to expand...
Click to collapse
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Vesten said:
What about stock recovery? Is that included I take it...?
Still getting used to all this in-depth flashing Android stuff. Managed to convert my M8 to the GP Edition without any trouble.
Click to expand...
Click to collapse
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Wow, thankyou! I've been Googling RUU's all night at work and found nothing like this. Think I'll do that and flash the RUU and start afresh!
Getting a killer 17.4 kbp/s though. 100mb connection wasted. Ha!
jollywhitefoot said:
Yeah. That's included. If you did that then you can get that thing back to stock.
Probably find the ruu here: http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
Yay it worked! Using a stock image from that link. Something must of been really screwed up. I'm now re-rooted! Many thanks for your help!
I'm currently rooted with a custom recovery and s on. There is an OTA available for my phone. What do I do?
Sent from my HTC 10 using XDA-Developers mobile app
flash the RUU that's for your phone variant to go back to stock, take the OTA, reinstall twrp, then reinstall superuser and your good to go. you can also wait to see if someone uploads the OTA here and youll be able to skip going back to stock but you have to wait a bit longer till someone does that.
afuller42 said:
flash the RUU that's for your phone variant to go back to stock, take the OTA, reinstall twrp, then reinstall superuser and your good to go. you can also wait to see if someone uploads the OTA here and youll be able to skip going back to stock but you have to wait a bit longer till someone does that.
Click to expand...
Click to collapse
Does this require wiping the phone? Where would I get the RUU?
most RUUs will not wipe your personal data or sdcard. where to get the RUU depends on your phone carrier
afuller42 said:
most RUUs will not wipe your personal data or sdcard. where to get the RUU depends on your phone carrier
Click to expand...
Click to collapse
Not true. RUU will wipe internal data. You dont need to run RUU. Just restore your stock unmodified system image, boot and recovery then boot to system and take ota. There is a thread in the guides section with all the info and downloads you will need
yldlj said:
Not true. RUU will wipe internal data. You dont need to run RUU. Just restore your stock unmodified system image, boot and recovery then boot to system and take ota. There is a thread in the guides section with all the info and downloads you will need
Click to expand...
Click to collapse
the RUUs i ever used never wipe internal storage or data, they do wipe system removing root
afuller42 said:
the RUUs i ever used never wipe internal storage or data, they do wipe system removing root
Click to expand...
Click to collapse
Are you sure? RUU makes your phone completely stock.
yldlj said:
Are you sure? RUU makes your phone completely stock.
Click to expand...
Click to collapse
I'm very sure 110% about the ones I have used do not wipe data.
yeah they make them 100% stock but your data is still there. what you wont have is twrp, superuser, and whatever rom you used before. youll still have to factory reset before or after the ruu installs to have your stuff removed, I prefer doing a format in twrp first. There may be some ruus that do a whole wipe but I have never seen/ used one personally.
They also do not relock bootloaders or make you s-on again
I've flashed RUUs that wipes internal storage such as the one I ran recently before I sold my M9 and others that didn't. If unsure I would suggest backing up internal just in case.
RUU also won't touch S-OFF. cmd must be ran in bootloader to set it back to S-ON