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
I think I messed up my firmware flash, by trying to flash an older 1.54 firmware from http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
After that it doesn't boot to recovery or rom, only displays the red exclamation point.
What are my options? Trying to update to the newest firmware with the method #2 on the linked thread, it gets stuck at "Sending..."
Ah I manually flashed the newer firmware with fastboot and flashed rom again, it works now. delete thread
I went to downgrade from marshmallow to lollipop 5.1.1 pb1 and I'm stuck in a bootloop is downgrading not possible or am I doing something wrong. installed the pb1 stock kernel as well after it kept bootlooping, though that shouldn't be necessary when installing a stock firmware. Any thoughts?
I feel like a complete noob, just did a factory reset and whiped the cache and I was up and running.
Downgrade path
What method did you use to downgrade back to 5.1.1? I am looking to downgrade so that i can root/unlock bootloader/ flash recovery/ install custom fw.
bsikes09 said:
What method did you use to downgrade back to 5.1.1? I am looking to downgrade so that i can root/unlock bootloader/ flash recovery/ install custom fw.
Click to expand...
Click to collapse
Just flash the older rom in odin.
I've also noticed that after unlocking the bootloader the sd card used can cause bootloops so make sure you take it out and format it after unlocking.
Hello XDA just had a question I wanted to clear up. I've had my z play -02 variant for a while now and I'm currently running lineage is 15.0. Just wanted to know if there is a way to get back to complete stock? I know the bootloader can't be locked, but is there a way to regain stock and still get motos ota's? Or is it impossible to get ota's after you've unlocked the bootloader?
OTA is working on unlocked device with STOCK ROM.
Try to flash STOCK ROM via fastboot or RSD tool.
Warning: do not try to flash MM version, OTA update from MM to N cause hard brick.
Try to flash latest 7.1.1 STOCK. I used this stock rom https://androidfilehost.com/?fid=889964283620757667 on my 1635-02 RETEU dualsim version.
Ax1qwer said:
OTA is working on unlocked device with STOCK ROM.
Try to flash STOCK ROM via fastboot or RSD tool.
Warning: do not try to flash MM version, OTA update from MM to N cause hard brick.
Try to flash latest 7.1.1 STOCK. I used this stock rom https://androidfilehost.com/?fid=889964283620757667 on my 1635-02 RETEU dualsim version.
Click to expand...
Click to collapse
Thank you!
When I try to flash it, rsd tool doesn't recognize my phone (probably because I'm in Windows 10) what's the command to flash it via fastboot?
you must be in bootloader mode for flashing.
maybe you do not have important drivers installed. I am using - https://forum.xda-developers.com/showthread.php?t=2588979
look at this before installing drivers https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
adb commands are different for each version of stock rom, because stock roms have different files to flash.
sorry for my english.
I was trying to unlock and flash custom ROM on my Realme x2 RMX 1991 device.
I succeed to unlock the device. but still have some issues with flashing TWRP as a custom recovery.
I was thinking to flash an old version of firmware like A14 instead of my current version A16. and try to re-flashing TWRP after that.
Is it worth it? and how can I flash stock firmware without using custom recovery?
I tried to flash with regular recovery, but it's juts failed because it's older than the current firmware version.
the boot image shows up but ony for less than a second and when i try to go in fastboot its the same .... less than a second