Develop Bugs

Stuck on Google Screen after JB Update

Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..

bevnet said:
Hi,
I've attempted the JB update
http://forum.xda-developers.com/showthread.php?t=1737899..
fastboot flash boot boot.img etc.. which said all was well..
But now find that my phone will not boot up, doesn't get past the Google and unlock screen.
I've tried all combinations of volume buttons, I can get to the fasboot menu where I can choose either Recovery Mode, Power Off, Start or Restart bootloader.
None of these appear to do anything, recovery goes to the google a screen followed by an Android on it's back with an exclamation mark over it.. then goes to the Google and unlocked icon screen and stays there...
I fear my phone is bricked... Please help..
Click to expand...
Click to collapse
1.) Your phone is far from bricked at all. You have access to the boot loader (i.e. the screen with the options). The recovery you're seeing is stock recovery. All you need to do is go into boot loader and fastboot flash recovername (CWM) and you will have your custom recovery back to wipe data and reinstall a rom or restore a nandroid backup

Mine is doing the same thing, weird thing is, it was working since yesterday on jellybean, it just randomly froze this morning and and now won't boot..
im currently at work so i don't have admin rights to do a fastboot flash..
any idea why it would randomly stop working when i havn't flashed anything on it besides the jb rom?

Sorted..
Thanks for the comments.. yeah i was over-reacting a bit there..
I downloaded the Galaxy Nexus Toolkit, got a stock rom form gopogle, flashed it.. back to normal, well, it will be after i restore the CWM backup i took.. phew..
Thanks again
Ian.

Still stuck
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!

this has happened twice today and i think it from using volume+

Steelbully said:
I'm also stuck in the same situation(google with the unlock screen). I fear I'm a little more stuck. I also can see the recovery/restartbootloader screen. However, everything I try still comes back to that same google screen and gets hung up. Need some help!
Click to expand...
Click to collapse
Boot into recovery, wipe cache, Reboot

Fire phone with FOS 4.6.6.1 alive again!

Hello everyone so this week I decided to root, flash custom recovery and of course flash a custom ROM in this case KK-FIRE-NEXUS-ROM. Anyway the phone booted it self into recovery and after I rebooted back to the OS and seeing the amazon boot animation it went black; it did not let me turn it on, not sign of power, I plugged the power cord with no signs of it charging then I constantly pressed key combination to boot into fastboot or recovery and it happened! It booted into fastboot and let my go into custom recovery. To make this story short and hopefully this helps others to not make mistakes; I tried to restore a back up of the stock ROM but it did not work. I tried to flash the stock ROM .bin format but it also did not work. I did all of this using my linux machine then I found this options in the recovery to select different ROMS within the recovery so you can boot into them well somehow it was changed to ROM(1) so I selected STOCK, rebooted and that was it. I got my phone working without having to flash anything! or messing up anything! ​
I hope this helps somebody or stops them from flashing something that will kill their phones!​

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.

Can only boot through bootloader mode, or booting boot.img

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.

Did I brick my Pixel 3 XL?

Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.

thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
Nevermind, @sliding_billy has the answer.

I
thex2 said:
Brand new Pixel 3 XL
Enabled OEM Unlocking
Enabled USB Debugging
Unlocked Bootloader
Copied twrp-pixel3-installer-crosshatch-3.2.3-5.zip to my phone
Rebooted into bootloader
fastboot boot c:\...\twrp-3.3.1-3-crosshatch.img
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Wiped system/data/cache
Flashed AOSiP-9.0-Official-crosshatch-20190722.zip
Flashed twrp-pixel3-installer-crosshatch-3.2.3-5.zip
Rebooted
When the system rebooted, it brought me into bootloader. I selected Start and then it rebooted into Bootloader again. I then figured something went wrong with installing AOSiP, so I booted into recovery.... from TWRP, I wiped system/data/cache/storage/data in attempt to start over and flash the ROM again. This time, I rebooted the system after the wipe and upon rebooting, the phone never turned back on. Pressing and holding the power button for long periods of time doesn't seem to do anything. Any ideas where I went wrong and more importantly if I bricked my phone? Thx.
EDIT: Tried holding volume down and power button for 10+ seconds and it booted into bootloader. Not really sure where to go from here.
EDIT 2: I tried booting into Recovery. It went back to the black screen. I had to use volume down and power button to get back into bootloader. Fastboot devices does detect the phone. I'm guessing this is a softbrick and I can follow the softbrick tutorial from here? Either way, it'd be nice to know where I took a wrong turn if anybody knows. Thanks.
EDIT 3: It may also be worth mentioning that I confirmed all the md5sum's before flashing the zips or booting the img.
Click to expand...
Click to collapse
If you can get to BL and fastboot devices is recognizing it, you are only soft bricked. Do a flash-all of the factory image. You will be starting over with the exception of OEM unlock and BL unlock. Once you are up and running, go back to BL, change slots and do the flash-all again. Of course, you will be setting up again but you should be clean. Be sure to use the last Android 9 factory image for flash-all if you are not intending to go to 10 yet. There is one rock solid custom ROM for 10 (Havoc). Take a read of the install instructions as it doesn't use TWRP (not available for 10 yet). It does need the flash-all of November factory image done to both slots, so if you are looking at that do it immediately IMO since you will have to wipe anyways.

If you wipe system in TWRP then you have to flash a ROM from there. That is why it went blank when you rebooted. You have nothing to boot up on.
ADB a stock file and start over...it's not bricked.

Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/

thex2 said:
Thank you for the help guys. I will work on fixing the issue tonight. Also, thanks for the suggestion on the Havoc ROM, but I'm staying with Android 9 because of the menu navigation button at the bottom right of the older apps... https://www.androidpolice.com/2019/...utton-has-finally-been-retired-in-android-10/
Click to expand...
Click to collapse
Havoc also had pie builds if you wanted to try.