I recently installed Evolution X 4.1.69 after unlocking my bootloader in my Pixel XL. After installing the custom ROM, I found that the OEM locking has been greyed out in the developer option.
Since the built of the custom ROM wasn't stable at that time, I decided to revert back to stock ROM. Unfortunately, I relocked my bootloader before recovering the factory image of the stock ROM.
After that, my phone screen starts flashing with the Google sign and keeps rebooting. I am able to access fast boot but I cannot access recovery mode from there. Pressing the recovery option from there will still lead me to a continuous boot loop, similar to what happen whenever I boot the phone.
I have tried these attempts with no avail.
1. fastboot oem unlock, failed since my bootloader is locked.
2. fastboot oem reboot-download, it causes continuous bootloop.
3. adb sideload bootloader.img, since I cannot access recovery mode, sideloading the factory image doesn't work as well.
4. flash factory image, failed as it still requires me to have an unlocked bootloader in order to do so.
Any suggestions on what I should do besides replacing the motherboard or RMA is greatly appreciated! Thanks!
you relocked your bootloader.
user error.
You sound pretty sure that you locked your bootloader. Did you actually go through steps to do so? Or was it just the grayed out option in developer settings? Have you tried to boot to TWRP or Lineage Recovery from fastboot?
Related
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.
I have a 32gig flo, I was running 4.4.4 with TWRP and ElementalX kernel. I tried to flash 5.02 with NRT and it all went wrong. First, while flashing it got stuck at the bootloader screen - pics / screenshots here. Then I realized the bootloader was locked, so I tried to unlock the bootloader with NRT and it got stuck in a boot loop. I pulled battery and tried the “Flash Stock + Unroot” feature to go back to stock 4.4 and the command prompt came up and said it was successful, but it's stuck in another bootloop, and now I can't even get back to the bootloader menu. I didn't use force flash mode and it said to try that but i can't get to that point. am I screwed? :crying:
edit: got into bootloader menu, used force flash mode and it's stuck in a boot loop again.
I just realized there were some text documents in Simple Notepad that i would have liked to keep. Is there any way I can recover them?
Hi my nexus 5x has started bootlooping on the google screen for no apparent reason. I have not rooted the device and it's bootloader is locked. I'm able to fastboot but selecting recovery mode returns me to the loop. I've tried using wugs nexus toolkit to flash stock but the it just returns me to the loop as the boot loader is locked. Is there any way to unlock the bootloader or return to factory settings/get out of the loop?
There is literally like five threads describing the same issue. Take a look in the Q&A forum
helpmynexuspls said:
Hi my nexus 5x has started bootlooping on the google screen for no apparent reason. I have not rooted the device and it's bootloader is locked. I'm able to fastboot but selecting recovery mode returns me to the loop. I've tried using wugs nexus toolkit to flash stock but the it just returns me to the loop as the boot loader is locked. Is there any way to unlock the bootloader or return to factory settings/get out of the loop?
Click to expand...
Click to collapse
I think you probably have failing EMMC. Sometimes if you keep playing with it or let the battery drain, it eventually boots once or twice before going bad again. If this happens you should immediately go into developer options and enable OEM unlocking.
If for some reason you can reinstall factory images and that works great. If not you probably need to try the LGUP method with the TOT file. Search and you'll find it.
If that fails, you probably need to get a new phone.
Hi guys,
So my problem is that my phone (Rio-L01) only boots to the fastboot&rescue mode screen, i can also make it to the Huawei e-recovery screen but i can't get it to download an update. I tried the adb fastboot method with no success, I flashed boot, system and recovery images by extracting them from the stock update file but it failed because the phone is FRP locked. From my perspective it seems that I need to access to the phone to FRP unlock it but I can't do that because the phone is FRP locked, does anyone can provide help or am I doomed ?
I can't seem to get my z2 to boot normally. I can get it to boot in to android if I select Start in the bootloader menu, or if I fastboot boot the boot.img. I've wiped & reset my phone numerous times with ALBUS_C_OPSS27.76-12-28-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC, only to be presented with a "No command" screen if I try and boot it normally. Any insight to this?
Are you using the right firmware? Try 76-12-25. And your bootloader is unlocked?
I have the same issue with my XT1710-06 on both stock Oreo and LOS 15.1. Tried wiping and reflashing roms and different versions of TWRP but neither of those fixed it. With no recovery it just goes to the "No command" screen, otherwise it will reboot to recovery unless you boot by pressing Start in the bootloader mode. Everything works perfectly normally otherwise though, so I just don't reboot my phone often and go through bootloader each time.