So I've managed to acquire the OTA for my CID (HTC__K18) but I can't seem to be able to flash it. There is no RUU available.
I've got as far as flashing the firmware.zip, which worked, but not the ROM itself.
Even with stock recovery and boot, when I tried flashing the rom as update.zip through the stock recovery it just says 'OEM:00' and reboots normally.
Any idea what I'm doing wrong?
Can I use customRUU to flash it? Any idea how?
(Clarification: This is NOT a JellyBean update, it's 4.0.4 and the reason I want to flash it is I need to turn it in to repairs and I want to go back to stock).
I was trying to update my firmware in the hope of using one of the custom roms available, and my M8 is now stuck on the boot screen and will not go further. Here is what I did:
Currently have a GPE M8. It is S-Off, SuperCID, Unlocked, and converted to T-Mobile (Sense) stock rom.
Was on 1.54.401.5 firmware attempting to update to a 2.22.xxx firmware.
The exact process I used was:
Boot into fastboot
fastboot oem rebootRUU
fastboot flash zip firmware.zip twice (successful after 2nd time)
fastboot reboot
After this, it will not go past the default boot screen.
I then tried to revert back to 1.54.401.5 firmware using the same process. This time, it will reboot once after the stock boot screen and go into recovery. Still unable to get back to the OS.
What am I doing wrong and how do I get out of it? :crying:
[edit] I tried to install a newer firmware again, as well as a couple of different roms. No luck, still getting stuck at the boot screen or automatically rebooting into recovery. Had to resort to using the T-Mobile RUU to get back a working phone. I still don't know what went wrong with my attempt at trying to install a new firmware or rom. [/edit]
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
thom109 said:
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
Click to expand...
Click to collapse
I did try to install a couple different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Mpegger said:
I did try to install a could different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Click to expand...
Click to collapse
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
thom109 said:
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Click to expand...
Click to collapse
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Mpegger said:
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Click to expand...
Click to collapse
always install rom first then firmware
my phone softbricked after trying to restore my cm12.1 nandroid backup (made in twrp 2.8.6.0, could being on 2.8.7.0 cause this?)
the ota for MM 1/2 is on my phone and I am thinking of flashing it. is this safe?
using a different recovery version can sometimes cause issues with backups.
downgrade back to 2.8.6.0 and try again. Once you are restored, you can upgrade to 2.8.7.0 and create a new backup.
I know I'm a bit late but I hope that I can still help.
You can download a ruu for mm sense 7 update. If you want I can leave a link then download a ruu from ruu.lalleman.net and place the mm ruu zip inside de ruu folder you downloaded and rename to rom.zip . This worked for me
fraggz99 said:
my phone softbricked after trying to restore my cm12.1 nandroid backup (made in twrp 2.8.6.0, could being on 2.8.7.0 cause this?)
the ota for MM 1/2 is on my phone and I am thinking of flashing it. is this safe?
Click to expand...
Click to collapse
You can't run an OTA with a custom ROM on the phone (need stock, never rooted ROM). And you can't flash an OTA with TWRP (at least, not easily), it requires stock recovery.
I finally managed to find out where my phone downloaded the Sprint Nougat OTA file, and copied it to my SDcard.
My phone is a Sprint HTC 10. The bootloader is unlocked and my recovery is TWRP, but other than that I am stock and unrooted.
Everyone says you need to be on stock everything to install an OTA update (though I had no issues installing previous OTA updates directly, but all of those were small), so I was reading up on flashing stock recovery.... but several people commented that flashing a stock recovery on their phone wiped it. I really don't want to take that risk, and with TWRP I can make a backup of my entire phone. So I wanted to know, if flashing an OTA update fails from TWRP, could that brick my phone bad enough that I wouldn't be able to flash the TWRP backup to restore it? Or can I recover as long as I can boot into... well, recovery. Would the OTA update overwrite the recovery too? Especially if I try to install it from within that recovery?
I was told to extract the "update.zip" file from the OTA.... but there is none in there, is the OTA zip file itself what they meant by "update.zip"?
flashing an ota with twrp won't work...at least it won't update the firmware bits.
So I found my old M83 the other day. It's running:
S-ON, UNLOCKED BOOTLOADER (NOW RELOCKED) ON TMOBILE.
I decided to try and flash the latest firmware via the sd card method, didn't work. Then tried flashing the firmware via fastboot. Fastboot didn't work either.
Now the phone only boots to the bootloader/hboot screen.
Any attempt at trying to flash firmware, or a recover, customer or otherwise fails.
I'm really hoping I can find a tmobile ruu zip to bring it back to life, however I can't seem to find a tmobile ruu zip anywhere anymore. I don't have a PC so downloading the *exe files doesn't do me much good.
Is there anyone that can please offer some assistance?
Much appreciated in advance!
What I did was to use TWRP and restore my original copy of the ROM (hopefully you still have that), if not you will need to find a TWRP backup of the ROM for the version of firmware you have and then restore the recovery for that same version (it get rid of TWRP). Then let the OTA fix update your phone. This is the route I took. Since Android 6 (MM) is the last release once you get to that stock, you can then replace the recovery (you could backup the recovery also) with TWRP, take a backup and then root or flash a new ROM.
Good luck