Develop Bugs

Samsung galaxy nexus bootloader can't make changes to flash

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.

Can't get to Recovery mode any more.

Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.

dubsteps said:
Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.
Click to expand...
Click to collapse
the "fastboot erase cache" should be done after flashing recovery:
Code:
fastboot flash recovery <name of correct twrp version>.img
fastboot erase cache
no need to wait for it to die out, POWER + VOLUP (possibly under a bright light) should do a forced reboot

nkk71 said:
the "fastboot erase cache" should be done after flashing recovery:
Code:
fastboot flash recovery <name of correct twrp version>.img
fastboot erase cache
no need to wait for it to die out, POWER + VOLUP (possibly under a bright light) should do a forced reboot
Click to expand...
Click to collapse
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).

dubsteps said:
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).
Click to expand...
Click to collapse
Not sure which recovery you're trying to flash but you might try a different version.

Magnum_Enforcer said:
Not sure which recovery you're trying to flash but you might try a different version.
Click to expand...
Click to collapse
I flashed TWRP 2.8.0.1 and it worked fine until I decided to try to get rid of the red text on the HTC bootloading screen.

dubsteps said:
Thanks so much for the tip on POWER + VOLUP to reboot the phone!
I then booted the OS ok (no cell signal though), rebooted to Fastmode, ran Minimal ADB and Fastboot: flashed the recovery file successfully, and then formatted the cache with the command line text stated.
When booting to Recovery, it's still not going into Recovery mode. Just sitting at the HTC screen with the writing at the top: Entering Recovery...
The phone also seems to be a bit sluggish now - just seems to be taking longer than normal for the parts that still work ok (loading the OS).
Click to expand...
Click to collapse
have you made sure
1- the recovery is the correct one for your phone
2- the file isnt corrupt (check MD5)
i don't know if this is related to the modded hboot (it shouldnt be) but who knows, i dont like messing with hboot

If all else fails, RUU and start over.

Magnum_Enforcer said:
If all else fails, RUU and start over.
Click to expand...
Click to collapse
Ok, I redownloaded the latest TWRP: 2.8.3.0 for the M8, checked it via MD5. I tried flashing the recovery file and nothing has changed... ( I now notice my phone won't connect to Bluetooth or wifi now)
Seems like all else is failing. I'll have to try RUU now. I'm starting to look around the M8 forum for info on RUU. Got anything threads handy to help me?

dubsteps said:
Ok, I redownloaded the latest TWRP: 2.8.3.0 for the M8, checked it via MD5. I tried flashing the recovery file and nothing has changed... ( I now notice my phone won't connect to Bluetooth or wifi now)
Seems like all else is failing. I'll have to try RUU now. I'm starting to look around the M8 forum for info on RUU. Got anything threads handy to help me?
Click to expand...
Click to collapse
Which carrier are you on?

Magnum_Enforcer said:
Which carrier are you on?
Click to expand...
Click to collapse
Originally the phone was with Rogers Wireless. I had to SIM unlock the phone so I could use it on Bell Mobility.

dubsteps said:
Originally the phone was with Rogers Wireless. I had to SIM unlock the phone so I could use it on Bell Mobility.
Click to expand...
Click to collapse
imho, try reflashing your firmware again (that would include stock hboot)

by removing the red writing you actually installed a custom hboot i think ...revert to your original hboot should fix things for you

nkk71 said:
imho, try reflashing your firmware again (that would include stock hboot)
Click to expand...
Click to collapse
Ok, so I flashed stock recovery and went to HBOOT>RECOVERY -> pressed VOLUP and POWER at red triangle w exclamation point screen.
- Wiped Cache, Factory Reset data (not sure if that is needed, but did it in case)
rebooted and the phone is working again (AND the red text is gone at startup)

dubsteps said:
Ok, so I flashed stock recovery and went to HBOOT>RECOVERY -> pressed VOLUP and POWER at red triangle w exclamation point screen.
- Wiped Cache, Factory Reset data (not sure if that is needed, but did it in case)
rebooted and the phone is working again (AND the red text is gone at startup)
Click to expand...
Click to collapse
nice :good::good:
no reason for custom recovery not to work since you were able to get to stock recovery, i've seen a few rare cases on the m7 where you had to delete the twrp settings file on the sdcard for it to work when going from one version to another (though really a very rarely)

nkk71 said:
nice :good::good:
no reason for custom recovery not to work since you were able to get to stock recovery, i've seen a few rare cases on the m7 where you had to delete the twrp settings file on the sdcard for it to work when going from one version to another (though really a very rarely)
Click to expand...
Click to collapse
Ok, it's definitely the download for the TWRP recovery I had. I'm able to reflash stock recovery and reflash other TWRP downloads (another download of the newest, then maybe 2.7.x.x)
-
OK, I flashed with TWRP 2.8.1.0 and that worked ok. I did MD5 the 2.8.3.0 TWRP, but it just won't work.
Thank you so much nkk71 and everyone who replied to my thread!

dubsteps said:
Hello,
I've had this phone for about a week and got it configured the way I prefer: S-Off, unlocked Bootloader, SIM unlocked, rooted. I flashed the latest Beanstalk 4.4.4 ROM and life was pretty good.
The only thing was the power on screen had red writing, so I followed this thread: ★ ☆ [MOD] Remove Red Text on Splash Screen | m8 hboots | ALL Variants and it worked! It did remove the red writing, but now I can't boot into Recovery mode.
I tried getting to Recovery mode through HBOOT and also from the OS reboot menu. When the phone tries to get into recovery mode, it stalls at the HTC splash screen and states: "Entering Recovery..." at the top of the screen, but never gets there. I then have to wait for the phone to run out of power, before I can put it on the charger and then be able to boot into the Bootloader or the OS.
So then I found a thread to erase the cache using Minimal ADB and Fastboot: fastboot erase cache
which it did successfully. I then booted to the OS, and now I've lost my cell signal,
I booted back to fastboot and from my computer ran Minimal ADB and Fastboot: fastboot flash recovery twrp.img
which it did successfully. I then tried booting to the Recovery and again I get the HTC start up screen with: "Entering Recovery..." at the top of the screen.
So now I'm waiting for the phone battery to die off a fully charge. Before I do anything else, I would like some of your help with what my next step should be.
Please help!
Thank you.
Click to expand...
Click to collapse
Got a similar problem like this one
unlocked bootloader
flashed twrp using the fastboot process of cmd
but i CANT get into RECOVERY MODE
when i click Recovery only a screen flashes saying "Entering recovery" and comes back to the bootloader screen showing HBOOT
PLEASE HELP
A TOTAL NOOB

Robin on Nougat Won't Boot After Flashing TWRP

I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?

Saaber said:
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Click to expand...
Click to collapse
My guess is you messed up the boot.img, or worse you corrupted some partition. If it's the boot.img, go get the latest factory image, unzip it, and move the file 'boot.Img' onto where your adb and fastboot files are located. Then go into fastboot on your Robin, and run this command on your PC:
Fastboot flash boot boot.img
If you corrupted something, you basically need to go into fastboot and use the flash-all.bat in the already unzipped Robin_nougat_88 folder to bring your phone back bone stock.
Hope that helped
Had this issue with my phone at first, but eventually just fixed it anyway by flashing the decrypted boot.img.

I ended up fixing it the same way you did. No matter how many times I took it back to stock by flashing the files in the Robin_nougat_88 folder and then flashing TWRP, no matter which version of TWRP I used, it would never boot. I finally flashed TWRP, then booted back into recovery, wiped the phone, loaded and flashed the decrypted boot image and SuperSU, and then the phone booted fine. I should have just done that in the first place since it was always my intention to unencrpyt it and rooted it again, anyway.

Missing Recovery on Android 10

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.

Razer Phone 1 Stuck in Bootloop after Wiping Userdata

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.