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

Issue trying to update to 4.3

(Originally posted this in the wrong forum, so I am reposting here.)
I have the Galaxy Note II with T-Mobile.
Some background: It was running Android 4.1.2. I rooted my phone once, about two weeks ago, just so I could take an image of it in case of an update issue. (I think the software was called nandroid.) Once I took the backup, I unrooted it again.
Since then, doing the Software Update check under settings never returned any results. It would just keep checking until I clicked cancel.
Anyway, when T-Mobile released the 4.3 update Monday morning, I tried updating to it using the Kies software on my PC (by connecting it through the USB cable). It got up to about 60% installation and then just hung for over an hour. So I unplugged the phone, re-plugged it back in, and then attempted the emergency firmware recovery through Kies. It went through this and got upto 76% installation and then just hung again for another hour. I again unplugged it to re-try the emergency recovery again, but every time I connected the phone, Kies would not detect it again. I re-seated the battery, rebooted my computer, uninstalled and reinstalled Kies, but Kies would not detect my phone again.
I am/was running the stock rom, but my phone won't even boot into it's normal screen. Any time I turn it again, i see the screen--"there were errors during firmware upgrade. try emergency recovery in Kies."
I can't even figure out a way to get to a screen where I can install the image I took using Nandroid a few weeks ago.
Any help or advice anyone can provide would be extremely appreciated!

Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..

Double0EK said:
Use Odin to fix it.
If you can put your phone into download mode then it should be 'saveable' ..
Click to expand...
Click to collapse
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?

diggeryo said:
I am able to put it into download mode. When I follow the instructions I found for Odin, the process seems to go smoothly. However, once my phone reboots, it stays on the "Samsung Galaxy Note II" screen (with the black background). I've left it like that for over 30 minutes, and it just stays on that screen.
Should there be another step I should be following?
Click to expand...
Click to collapse
Try installing SuperSU from Playstore
It has an option of doing a FULL UNROOT
I am sure that will help.
If not then install Rom Manager from PS
Through RomManager reboot in Recovery
1.) Wipe device 3x times
2.) Wipe cache 3x times
3.) Under advance you will Find Dalvik Cache -- wipe that 3x times
[MENTION=522570 [MENTION=1065870 [user=1879310]@@@@[/user][/MENTION]@@[/MENTION]@@
But more importantly why would you want 4.3 stock anyway?
Install TWRP Recovery or ClockWorkMod recovery and install/Flash CM1 (Cyagonemod) or any other custom roms 4.4.x kitkat

Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?

Just do this un root with chain fire root away app.
Then use triangle away app.
Then find 4.1.2 MB1 stock Odin tar. The complete package .
Odin to stock .
Reboot and then update via Ota.
You have to un root first and also have to triangle away which removes flash counter in Odin.
System modified status will not allow Ota.
That's the best suggestion I have
Sent from my SGH-T889 using xda app-developers app

diggeryo said:
Nothing is really working for me.
I can't boot into normal mode. I am able to get into "download" mode, but whenever I try to load an image using the Odin software (both a stock image and a Cyagonemod image), it starts to load the image, but just hangs a certain percent of the way through.
I also can't get to that screen where it gives you the text based options to wipe your device, cache, etc.
I've tried loading both TWRP recovery and ClockWorkMod recovery (through Odin), and though it seems to load properly (Odin says "Pass"), when the phone reboots, it goes to the "Samsumg Galaxy Note II" screen (the one with white text on a black background), and just stays there.
I've gotten T-Mobile to agree to send me a new phone. But if I can't get into any of the items I mention above, how can I make sure my old device is wiped before sending it back to them?
Click to expand...
Click to collapse
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Sent from my SGH-T889 using XDA Premium 4 mobile app

wolfpack612 said:
have you tried booting into recovery? after you load the custom recovery with odin and it reboots, pull the battery put it back, then hold vol up + home and then + power. hold all 3 until recovery. try a factory reset and reboot.
Click to expand...
Click to collapse
I have. It brings me to the same screen with the Samsung Galaxy Note II text on the black background and just stays there.
So, in summary, I can get into download mode (vol down+home+power), but it seems nothing else.

Try factory settings the phone through stock recovery and then check your phone status. It should say 'normal' but if it says 'modified,' download Triangle away and run the tracking setting (it'll make your phone say normal so you can download the OTA). Given you're on tmobile and your phone is the T889 model, check for software updates and install the OTA. Your phone will take a bit and will probably be stuck on the T-Mobile 4G boot screen for several minutes (it's normal). This should work.

Chinese M9 bootlooping after OTA

Hi All,
Really hoping someone can suggest a possible solution for this one, only had the phone a few months!
So, Chinese released M9. Unlocked. Stock recovery, not rooted. Gapps installled.
Everything perfect, then today I got the 5.1 update.
Seemed like a slightly iffy install process...looked a little like it failed a couple of times and tried again.
Finally finished, the phone shows the white screen with the one logo, takes a while, opens on the desktop and turns off, back to the white screen with the logo.
I have been able to boot into safe mode, which is stable
I have been able to get to download mode and bootloader. Neither of these offer a cache wipe or a factory reset.
I have not been able to get into recovery mode, it shows a phone with a red triangle and an exclamation point.
So for my (largely uneducated) part I have two theories for the cause:
1) Gapps is somehow proving a problem, either faulting the install or causing a fatal error on startup
2) Since the update was notified and downloaded while on a VPN via Hong Kong, I wonder if I accidentally ended up with the HK version in which case I suspect there may be hardware differences (at least the radio). This seems unlikely, I would hope there were enough checks in place to prevent this happening.
No solid idea where to go from here. I have not yet tried ADB access, but even if I can connect, what will I do? Flash a new ROM? I'd rather not. And surely I'd need to root in order to do that....
At a loss, any potential solutions welcomed whole heartedly!
Thanks...

Booting into safe mode, but not booting otherwise, indicates a problem with some app or rom setting.
You're probably going to need to do a factory reset, but that's odd that it doesn't show up in bootloader or download mode. Have you tried the options in stock recovery (which is that screen with the red triangle)? Use the volume keys to change options.

Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.

Trying a factory reset from safe mode - I'll let you know what happens!

misteral1970 said:
Hi iElvis - the screen with the red triangle - there's nothing other than the red triangle, no options, no text and nothing happens if I press any of the physical buttons.
Click to expand...
Click to collapse
Hmm. It would seem the Chinese models are set up differently, which would not surprise me at all.

[SOLVED] Android Pixel XL Boot Loop, Never Seen Before

My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.

I would fastboot latest factory image.
Just hold vol- when a reboot comes it will go into bootloader.

piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709

piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Just started with me today too.
I cannot get into recovery or boot loader
rebooting using the hard button just brings up this Dump to EXT4 and then into the ROM that is havnig a ish ton of force closes.
My plan is to back up some stuff I need to copy off the phone and then start factory reset from within settings.
EDIT:
I was rooted running stock
All i did was run a backup in TWRP
issues started after reooting.
Once i factory reset and re Root i will see if I can restore backup, maybe

sb1893 said:
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
Click to expand...
Click to collapse
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!

piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April. How do I revert the bootloader?
Also, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful so far. Thanks!
Click to expand...
Click to collapse
They flashing all the parts of the image manually. Something like this happened to a buddy of mine and using the flash all wouldn't fix. He couldn't get the device to boot until he did all the images manually.

piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
Click to expand...
Click to collapse
Glad you got it working. I checked and I did link the thread I intended to. Starting at post #57 onward from that thread has the information on how to update to the May update and leverage Chainfire's VerifiedBootSigner.zip.
Thx,
S

Pixel bootloop
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!

rosendomurilo said:
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
Click to expand...
Click to collapse
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.

Phalanx7621 said:
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Click to expand...
Click to collapse
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...

rosendomurilo said:
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
Click to expand...
Click to collapse
Can you get to recovery ?

Phalanx7621 said:
Can you get to recovery ?
Click to expand...
Click to collapse
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...

rosendomurilo said:
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
Click to expand...
Click to collapse
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.

Phalanx7621 said:
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Click to expand...
Click to collapse
Perfect! Just as I expected... Probably i will do an youtube guide if it works... Thanks bro!

Can't boot OP3t after update.

A notification came up for a new update and tried to install it. The update failed on the update screen and the phone tried to reboot. I gave it half an hour but I'm certain it's stuck on the screen with the white dots circling a red one. Held down the power button to restart but still stuck.
I can get into the options menu, but selecting recovery seems to just restart. When selecting fastboot, there's no number after bootloader and baseband version.
I have little experience with rooting and flashing or whatever. Not sure what to do, any suggestions?

https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
I used this linked and it worked!
It was a bit sketchy but hey

Dygijle said:
A notification came up for a new update and tried to install it. The update failed on the update screen and the phone tried to reboot. I gave it half an hour but I'm certain it's stuck on the screen with the white dots circling a red one. Held down the power button to restart but still stuck.
I can get into the options menu, but selecting recovery seems to just restart. When selecting fastboot, there's no number after bootloader and baseband version.
I have little experience with rooting and flashing or whatever. Not sure what to do, any suggestions?
Click to expand...
Click to collapse
This is what we call a bootloop. Now you can try a factory reset, but installing TWRP si way better if you encounter these issues in the future. Try to wipe System then flash OOS and it should be fine.