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.
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.
Okay, so, I followed the guide to root my device. And everything went smoothly, until the new version of Android (8.0.0) was released for the phone and I made the mistake of trying to install it using the stock installer rather than through TWRP. Of course, it failed and I ended up doing the installation manually. Now, whenever I try to reboot my phone, it boots straight into recovery (which gives me the "No Command" error because TWRP is inexplicably missing). If I load up Bootloader (Volume Down + Power) and select START, then the phone boots like it should and I can use it just fine.
I've tried wiping the data through TWRP (After flashing it to recovery for the umpteenth time) thinking that would help, but no. It still boots directly into recovery. The command "fastboot oem fb_mode_clear" using minimal ADB and fastboot doesn't work either. Any help would be appreciated. I have no idea what else to do.
try to plugin charge cable and reboot again.
Nope. Still boots to recovery.
Hi, did you ever manage to solve this? I have the exact same problem.
Fiksdal said:
Hi, did you ever manage to solve this? I have the exact same problem.
Click to expand...
Click to collapse
try to boot to bootloader, and then use the option start
I just noticed after doing a clean install of the C3 factory image using -w that I am unable to boot to the stock recovery. It seems to be missing from my installation. Any ideas why I may be unable to boot to recovery? All I get is a dead Android logo with "No command" or it boots up my system after restarting. I've tried booting from the bootloader numerous times and never seems to work. Is it possible that the stock recovery was never installed? I did no perform a --slot all when installing Android 10 so maybe that's the issue? Any suggestions would be great as I can't seem to find a solution to this in the forums or Google searching. Thanks.
You have to go one step beyond the no recovery screen to see the recovery commands. If presented with an image of a broken Android with “No Command” printed on the screen, press and hold the Power button. Press the Volume Up button once. Then release the Power button.
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
rspkt said:
Seems I can't even get to the broken Android screen now. In the bootloader if I select boot recovery it just boots my system and never shows the broken Android anymore. Very odd. I'm stumped.
Click to expand...
Click to collapse
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
sliding_billy said:
I am not sure what you are referring to "boot recovery." Are you entering the bootloader in some way other than volume down +power? The option when using the up/down in bootloader is Recovery mode. That will get you to the broken android and no command. At worst though, you can flash boot.img and get your stock recovery/kernel back/unroot.
Click to expand...
Click to collapse
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
rspkt said:
I can enter the bootloader via adb or with the power + volume down no problem. When I select recovery from the bootloader it boots to the Google logo then blank screen and seems to reboot again straight to my system. I may have to try to revert to the stock boot.img like you suggested and see if that solves the issue.
Click to expand...
Click to collapse
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
sliding_billy said:
OK, that makes better sense. You are pretty clearly in a bootloop. Just confirming the terminology. Flashing stock boot might get you out of the loop, but after rereading your initial message it sounds as if some info is missing. After the flash-all, did it ever get to the setup screen where you enter your gmail account name, etc. Did it get through that to the actual OS, and if so what else did you do that got you into the bootloop? Root attempt?
Click to expand...
Click to collapse
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
rspkt said:
Ya my phone setup fine through all the initial setup steps as if it was a new device and the system works perfectly. I did root and install Kirisakura kernel but only after few days of using stock. Just noticed after setting everything up the recovery seems to be missing when I tried to boot into it. I may try and start from scratch again cuz obviously something got broken during the factory image installation using -w.
Click to expand...
Click to collapse
I missed the post by @jd1639 while I was replying. It doesn't sound like anything got messed up as a result of the -w. Because stock recovery is part of boot now, you just need to stay out of there unless you flash boot.img first. Not doing the --slot all wouldn't have any impact unless you install a custom ROM, an OTA or do a manual slot change. Since it was the first time I had done a completely clean wipe in a while when I flashed 10 (after custom ROMs, OTAs, etc), I actually did flash-all (with -w) to both slots. I did a flash-all on B and finished setup, and then booted back to BL, changed slots manually to A and did a second flash-all. Only after that did I start gettin gthe phone ready for daily function. Not sure it helped anything but my OCD, but it was fun to watch the fastbootd thing run a few times. :silly:
jd1639 said:
I get the same thing where it won't boot to recovery from the bootloader, but goes back to booting to system. It's because I'm rooted. Flash the stock boot image and you'll be fine.
Click to expand...
Click to collapse
I never would have assumed having root could cause this issue.
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.
So I loaded Lineage OS 19.1 just fine, but it caused a few issues so I decided I'd flash it back to a global stock ROM.
My first step after factory resetting the phone was going into the bootloader and wiping user data. Now I just get the boot screen and restarts when it usually would go past it.
The phone is not responding to any button press combinations as well as not loading into the bootloader when a usb is inserted while the volume down button is being help in the brief off time between restarts.
Am I stuck, do I just need to put a new motherboard in the phone? Should I not have wiped user data from the bootloader, and instead used the recovery to do so?
I do have another motherboard from a working parts phone except its Google locked, but I've heard and seen that there are ways around that.
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
SurvivalHorror said:
do you have boot.img flashed without errors? on some devices, you need to add fastboot flash:raw boot_a boot.img
Click to expand...
Click to collapse
Well I did. But now it won't accept inputs. I've already swapped the motherboard. It works, but I decided to go back to Lineage AGAIN, as the stock ROM is has WAY too many issues, and now it has a similar issue after sideloading the zip from lineage. Although the recovery partition booted just fine after I flashed it with the lineage recovery img.