My friend's phone somehow got into a reboot cycle. It loads up, launcher starts, notifications start working. Then there is a nullpointer and a core service that is failing to start then it reboots.
So as a solution I thought try wiping data/cache. When booting the bootloader it was already unlocked - not sure if we did that a while ago or what. So going into recovery, trying the data wipe, it says success and then when I start the phone it is the same, no data is gone, apps are there, reboot problem continues.
So next step, try flashing the os. I downloaded the most recent yakju build, jwr66y. My bootloader version is PRIMELA03 and the build comes with MD04, so I try:
fastboot flash bootloader <bootloader_img>
And it reports success, everything looks fine. So I reboot the bootloader and it says BOOTLOADER VERSION - PRIMELA03.
Try fastboot oem lock, says locked. Reboot, UNLOCKED. Tried flashing the bootloader and the main img with and without restarting but always get the error:
Device version-bootloader is 'PRIMELA03'.
Update requires 'PRIMEMD04'.
when trying to flash the stock rom.
I also can't boot the stock image via 'fastboot boot'. It looks successful up until it says booting and goes to the Google screen with the padlock at the bottom and just hangs.
If I try using adb sideload to push the stock update, it says verifying, then aborts.
I also tried flashing the recovery with a cwm recovery but the same problem - it says writing, OKAY, no error message, everything looks fine, then boot recovery and it's the stock recovery.
What it looks like to me is that the bootloader and possibly the entire system is failing to write to the system flash but for some reason thinks it's succeeding. How is this possible? Is the flash dead? Am I missing something basic? I haven't rooted a phone in a couple years so it's quite possible I'm just missing a step.
Thanks in advance for any advice.
I just tried flashing an older stock (imm76i), starting by flashing the radio, but again the radio flash looks successful but the kernel won't flash because it complains about an out of date baseband and sure enough, the old one is still the one it's reporting, not the one just flashed.
tried fastboot erase system and fastboot erase recovery. Both report success but recovery boots as normal and system boots as normal (still in a reboot cycle).
I should also mention, that after the system boots, there is enough time to uninstall an app. It says successfully uninstalled, but after a reboot, the app is still there (this was the first attempt to stop the reboot cycle as a custom keyboard app was suspected). But again, the changes to flash seem to not be sticking.
Hi,
Have you resolved the problem? I'm in the same situation and I don't know what to do to stop the continuous reboot. I've already tried to flash a stock 4.3 factory image, erase the user data or only unlock the bootloader but nothing works. I'm running Android 4.3 stock without root and my bootloader is locked.
thank you in advance.
Phone seems fine when in recovery, acts totally notmally. Can flash any ROM without issue, but when you go to boot it will just stay on the boot screen indefinately. The result is the same regardless of which ROM I use. I decided to flash the RUU in the end as I was getting nowhere, but the same result... just stuck on the boot screen (relocked bootloader and flashed stock recovery beforehand)
Anyone seen this before or have any ideas what might be wrong?
Finally fixed. For whatever reason, reseating the battery connector kicked it into action
Hi Folks,
I have a M8 Dual SIM which I have manged to brick. Despite reading the whole damn internet, every thread there is I have been unsuccessful in restoring. Here is the awful situation:
Unlocked boot loader
Flashed TWRP
Super SU
Flashed custom ROM
All good however after about a week the phone decided to not reboot into the OS.
Re-flashed TWRP, via fastboot, this worked however ADB wouldn't recognize the device, now its in an infinite boot loop, boot-loader is accessible but just drops into the boot again. the TWRP flash screen appears flickering during boot. No OS on the phone now, just data partitions. No Nandroid backup. I could push a ROM via ADB if I could get the recovery stable. S-ON BTW.
Any advise will be gratefully received.
EDIT: I FIXED IT. I had to go back to an older version of TWRP[2.7xx] for it to work on my older firmware.
HTC One M8 AT&T running 4.4.2, unable to update because I haven't been on AT&T for quite a long time.
Yesterday I unlocked the bootloader on my M8 for the first time and attempted to install TWRP[EDIT: ver 3.0.2] so that I could root my phone. I have the proper SDK and ADB drivers installed, fastboot is working just fine. I used the following commands:
adb reboot bootloader
fastboot erase cache
fastboot flash recovery twrp.img
From there I have tried both rebooting into fastboot[which is what the TWRP website says to do] and also going back into bootloader and booting into recovery without restarting the phone. Neither option has worked. When booting straight into recovery after flashing the recovery, my phone just says "loading recovery" in pink letters with the HTC logo on the screen and stays like that. HOWEVER, I've somehow managed to get screenshots while force restarting my phone during that, and it shows the right TWRP screen, I just can't see it. Any advice at all would be appreciated. I did search through other forum posts but I could not find my problem of the screen I cannot see.
My telephone keeps booting to fastboot after trying to update TWRP.
I am trying to restore the original ROM (apollo_eea_global_images_V12.5.12.0.RJDEUXM_20220208.0000.00_11.0_eea) and I can get the rom installed through fastboot but the phone enters a boot loop cycle. It starts up, vibrates shortly then reboots.
If i press volume up it goes into the original recovery menu. I have tried clearing everything and even entering safe mode but the phone will not boot.
Am i screwed?
Thanks in advance.
I installed the Pixel Experience recovery and side-loaded the zip and at least have a working OS.
I must be doing something wrong with the stock mi10t
Now i sided the miui zip and its working agian. I think i have misunderstood the procedure. I thought you only need to install the rom with flashboot and that was it.