Database Develop

PSA: Unlocking Bootloader Before First Boot

Many people when they first get a Nexus device, choose to unlock the bootloader right away to prevent a mandatory data wipe if they unlock it later. Myself and a few others have encountered a bootloop after doing so. If this happens to you, follow these steps.
1) If your phone is stuck in a bootloop, Hold volume up, volume down & the power button until the phone turns off.
2) Wait a minute as trying to turn the phone back on may be unresponsive.
3) Hold volume up, volume down & power to boot into the bootloader.
4) Toggle to recovery and press the power button.
5) When you see the android laying down: press and hold the power button and immediately press volume up. It should open the menu.
6) Choose wipe data/factory reset. When completed the phone will reboot and should boot to the welcome screen
Hope this helps anyone who has this issue!

If I boot once, then reboot to boot loader then unlock will I be ok? I'm getting mine tomorrow.

Thanks for the heads up. I have no doubt that I will run into this issue and these instructions will help.

Zainiak said:
If I boot once, then reboot to boot loader then unlock will I be ok? I'm getting mine tomorrow.
Click to expand...
Click to collapse
Yes.

Suppose that's from the update that happens when you first boot, we all know how well OTAs and unlocked bootloaders get along.
Sent from N7

This is related to the typical Nexus data partition situation: If the data partition is wiped, the partition needs to be regenerated in some fashion before it can be written to, and this can only be done by booting once into the OS. Recovery and bootloader are unable to complete this operation alone.
If you find yourself in the situation of having wiped both system and data, you must flash any bootable OS version to system & boot via fastboot, and boot into it once, before you will be able to install ROMs via recovery again.

This is very important and I do this with every Nexus device on first boot.
Sent from my Nexus 5 using Tapatalk

This help, also had to format "data" because i skipped the first boot and installed the recovery right away
Thanks for this post

I booted mine straight to bootloader when it came and unlocked it with no problems. I wonder why this only happens sometimes?
did those of you who got a bootloop have to download/install the OTA when it finally booted?

[Q] [SOLVED]Conflict with Recovery and SS

To my understanding, what has happened to my phone is that it is trying to boot recovery while SafeStrap is getting in the way.
To walk through the process of what happened:
I used SafeStrap to install XNote and everything worked just fine, I used the updater script and everything.
I was in XNote and I was looking through all the settings when I accidentally pressed "Reboot to recovery"
The phone did the normal splash of "Samsung Galaxy Note 3 and had the blue "Recovery Booting" text at the top.
Of course then SafeStrap Decided to show up. All three of the following resulted in the phone failing to boot(black screen and it just sits there): Waiting for 10 seconds, Pressing "Continue" and pressing "Recovery"
I even tried booting into Download Mode to try and reset this, nothing seems to work and my phone will not start up.
I didn't realize download mode on this phone is actually only Volume Down, Home, and Power, and not Volume Up. I got it into download mode and rebooted. This post can be deleted now.

lol

Possibly Soft-Bricked Moto X with flashing recovery screen

Hopefully you guys can help me with my problem. Recently, I downloaded the new Marshmallow app drawer from Android Pit's "Here's how to get Android Marshmallow's new app drawer on Lollipop". It was successfully installed and seemed to be working fine. However, Google Now gave me a message saying that it was not connected to the microphone and that I should reboot my device. Thinking that the actual reboot key combo was power and volume down, I did this and this brought me to the fastboot page. I selected and entered the power up normally option on the top, which the booted my phone to a completely black screen, from which only the "power off" option would show if I held the power button down. I was confused and concluded that the app drawer somehow soft bricked my phone. After reading up on the web, I went into recovery in the fastboot screen, then selected clear cache. Two lines of orange text appeared at the bottom saying that the cache clear was starting and that it was finishing. I hit the power button, tried to boot my phone up, then, recieving another black screen, brought back up the fastboot menu and tried to enter the recovery screen again so that I could factory reset my device. The recovery screen gave me messages about how it could not load the cache, and since then has been flashing on a set interval on my screen (going black, showing the broken Android with "no command" then going black again).
Any ideas on what I can do to fix this problem?
note: (I have not rooted my phone)

cole_15 said:
Hopefully you guys can help me with my problem. Recently, I downloaded the new Marshmallow app drawer from Android Pit's "Here's how to get Android Marshmallow's new app drawer on Lollipop". It was successfully installed and seemed to be working fine. However, Google Now gave me a message saying that it was not connected to the microphone and that I should reboot my device. Thinking that the actual reboot key combo was power and volume down, I did this and this brought me to the fastboot page. I selected and entered the power up normally option on the top, which the booted my phone to a completely black screen, from which only the "power off" option would show if I held the power button down. I was confused and concluded that the app drawer somehow soft bricked my phone. After reading up on the web, I went into recovery in the fastboot screen, then selected clear cache. Two lines of orange text appeared at the bottom saying that the cache clear was starting and that it was finishing. I hit the power button, tried to boot my phone up, then, recieving another black screen, brought back up the fastboot menu and tried to enter the recovery screen again so that I could factory reset my device. The recovery screen gave me messages about how it could not load the cache, and since then has been flashing on a set interval on my screen (going black, showing the broken Android with "no command" then going black again).
Any ideas on what I can do to fix this problem?
note: (I have not rooted my phone)
Click to expand...
Click to collapse
What is the actual model of your phone. Did you have an unlocked bootloader with TWRP?

The black screen problem can only be fixed by doing a factory reset. After you get into the screen with the dead android and an exclamation mark. You need to press power and volume buttons to make a menu appear. Then choose factory reset. Unfortunately you will lose your data, but this will fix it.
Sent from my XT1095 using Tapatalk

AGISCI said:
The black screen problem can only be fixed by doing a factory reset. After you get into the screen with the dead android and an exclamation mark. You need to press power and volume buttons to make a menu appear. Then choose factory reset. Unfortunately you will lose your data, but this will fix it.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I have solved the issue... I believe it was stuck in some sort of loop with the revovery mode, because that was flashing periodically on the screen. I was eventually able to get the recovery screen to actually stay on the screen and then reset it. Thanks for the quick reply!

d33dvb said:
What is the actual model of your phone. Did you have an unlocked bootloader with TWRP?
Click to expand...
Click to collapse
I have solved the issue but the actual model is the Moto X 2nd Generation Pure Editon without the bootloader unlocked for anyone with similar issues. Thanks for helping out!

I'm having the same issue today with a Moto X Gen 1 after accepting Verizon's OTA upgrade to Lollipop. Only I can't boot to recovery.

cole_15 said:
I have solved the issue... I believe it was stuck in some sort of loop with the revovery mode, because that was flashing periodically on the screen. I was eventually able to get the recovery screen to actually stay on the screen and then reset it. Thanks for the quick reply!
Click to expand...
Click to collapse
I'm still having the problem that you were facing and cannot get out of that loop sequence. I've booted over and over, tried to launch recovery and nothing... I see some yellow text at the bottom only briefly staying that something couldn't load, then back to the dead-droid/red triangle (no command) for a split second, over and over... I am stuck.

Pfister07 said:
I'm still having the problem that you were facing and cannot get out of that loop sequence. I've booted over and over, tried to launch recovery and nothing... I see some yellow text at the bottom only briefly staying that something couldn't load, then back to the dead-droid/red triangle (no command) for a split second, over and over... I am stuck.
Click to expand...
Click to collapse
I'm having this exact same problem too! The 'dead droid' just constantly flashes over and over, so I am unable to do anything. There was one time when I held power and the low battery icon showed up with a yellow exclamation mark triangle, but I haven't been able to get that screen again. I contacted Motorola and they told me to try and go to settings and do a factory reset... I just told you I can't turn on my phone! What the hell man. I have tried so many things online and none of them worked. From what I'm reading the only was to fix this is to flash a blank bootloader, but those files haven't been released yet.
The worst part is that I have only been using this phone for ONE DAY!:crying:

cole_15 said:
I have solved the issue... I believe it was stuck in some sort of loop with the revovery mode, because that was flashing periodically on the screen. I was eventually able to get the recovery screen to actually stay on the screen and then reset it. Thanks for the quick reply!
Click to expand...
Click to collapse
How did you get the screen to eventually stay on?

mistervino said:
How did you get the screen to eventually stay on?
Click to expand...
Click to collapse
okay so after several guides and steps, i finally got my Moto X (1st Gen) working again using the tutorial here https://www.youtube.com/watch?v=EWDwyqUF6k4
Essentially i flashed a custom recovery like the PhilZ Touch recovery here http://www17.zippyshare.com/v/40132571/file.html by renaming the "philz_touch_6.58.7-ghost.img" file to "boot.img" in fastboot mode and rebooted after that.
And that was it, phone rebooted and is working fine.

Note 5 is stuck in android recovery

hi, i have recently tried rooting my Note 5 by flashing spacex kernel, so first i had to install a custom recovery i used "twrp-3.0.2-0-nobleltetmo.img (1).tar" . i installed via odin and rebooted into recovery. Once i rebooted into it i had a message with "installing update" or something like that with an android figure and then it changed to the robot laying down with a triangle with the message "no command". i tried rebooting the phone out of recovery but it just looped back to the same message
ps. the power button on the note 5 is not responsive, and it is 32gb tmobile
thanks to anyone who can help

Have you tried using ODIN to restore back to stock.

Leo_is_m said:
Have you tried using ODIN to restore back to stock.
Click to expand...
Click to collapse
The phone doesnt go past the samsung logo and the android recovery, when i use the button combination to go to DOWNLOAD, it takes me to the download screen but doesnt go any further.
I had a problem similar to this with my note 2 which also had a broken key, i was able to mess with the key and was ablew to boot into the phone

THEJUANANDONLY said:
The phone doesnt go past the samsung logo and the android recovery, when i use the button combination to go to DOWNLOAD, it takes me to the download screen but doesnt go any further.
I had a problem similar to this with my note 2 which also had a broken key, i was able to mess with the key and was ablew to boot into the phone
Click to expand...
Click to collapse
You could flash an official update.zip from Samsung and see if that works
What device model do you have? You must've flashed the wring twrp or something, it looks like you flashed the TMobile Version. Are you in T-Mobile?

if you can see that robot lying around... its mean you did not success to flash the twrp. it still stock recovery. try push vol button up/down several time and see if the stock recovery menu appear or not.

Fire 7 shows blank screen when it boots??

Hello. So a while back I got a Fire 7 5th Gen tablet for Christmas. I rooted it using KingRoot downloaded from Chrome, then one day I was so stupid, you know how many places tell you to not install TWRP. Well, I did it anyway, and while booting to it, it shut off for a couple days. When I was finally able to get it back on, well on first hand, I don't think it's in a bootloop, but it will show amazon, the fire goes on longer that normal (about a minute), then after that's done it just shows a blank screen with only a tad bit of light with it. Please, help. I also have a Fire HD 7 that I can't get past the password because I accidentally erased the keyboard and it won't pop up and another fire 7 that will show amazon, shuts off, shows amazon, cuts off, and continues in the same sequence. Any ideas?

Restore the newest firmware.

Pix12 said:
Restore the newest firmware.
Click to expand...
Click to collapse
hi! I have the same problem when my unrooted fire 5th gen suddenly froze and I got black screen, how do i do this?

I'll look for the link after this initial posting and add it after. Download the proper firmware and place the .zip into the same folder as platform-tools (the folder you use to use ADB.) Follow the steps below first, to possibly resolve issues before flashing firmware.
1) power down device. If you can't, press the power button and hold until device turns off.
2) When it's off, first press the volume down button and hold it, then press and hold the power button until the recovery screen comes up.
4) Scroll to 'wipe cache partition.' Select it with the power button. You won't lose any user data or files, yet.
5) Select reboot.
6) If problem is still there, follow steps 1-2 again.
7) Scroll to factory reset and select with power button. You WILL lose all user data and files.
8) Wipe cache partition again (I do this often if I go through resets).
9) Select reboot.
10) If problem STILL persists...Repeat steps one and two. Plug in tablet to PC. Select "make an update vis ADB" or something similar.
11) type: adb sideload xxx.zip (x being the firmware file).
12) That should do it assuming your device is recoverable.

DragonFire1024 said:
I'll look for the link after this initial posting and add it after. Download the proper firmware and place the .zip into the same folder as platform-tools (the folder you use to use ADB.) Follow the steps below first, to possibly resolve issues before flashing firmware.
1) power down device. If you can't, press the power button and hold until device turns off.
2) When it's off, first press the volume down button and hold it, then press and hold the power button until the recovery screen comes up.
4) Scroll to 'wipe cache partition.' Select it with the power button. You won't lose any user data or files, yet.
5) Select reboot.
6) If problem is still there, follow steps 1-2 again.
7) Scroll to factory reset and select with power button. You WILL lose all user data and files.
8) Wipe cache partition again (I do this often if I go through resets).
9) Select reboot.
10) If problem STILL persists...Repeat steps one and two. Plug in tablet to PC. Select "make an update vis ADB" or something similar.
11) type: adb sideload xxx.zip (x being the firmware file).
12) That should do it assuming your device is recoverable.
Click to expand...
Click to collapse
It doesn't pop up on the computer whenever a plug it in + i can't boot it into recovery, attempting to do so will cut it off and it will cut back on.

WilliamTheKingAS said:
It doesn't pop up on the computer whenever a plug it in + i can't boot it into recovery, attempting to do so will cut it off and it will cut back on.
Click to expand...
Click to collapse
See this thread..
If I recall, I don't think a notice pops up when you plug it in in recovery/fastboot. Try plugging it in and let it get a full charge from a wall outlet. Then try to power it back on into recovery while it is still plugged in. Don't plug it into your PC until you get past the recovery screen and select add update from adb. You might have to do that a few times. I had a similar problem on my XT907 phone where it would reboot every time I got into the recovery screen and I eventually was quick enough to get into fastboot to do what I needed.

DragonFire1024 said:
See this thread..
If I recall, I don't think a notice pops up when you plug it in in recovery/fastboot. Try plugging it in and let it get a full charge from a wall outlet. Then try to power it back on into recovery while it is still plugged in. Don't plug it into your PC until you get past the recovery screen and select add update from adb. You might have to do that a few times. I had a similar problem on my XT907 phone where it would reboot every time I got into the recovery screen and I eventually was quick enough to get into fastboot to do what I needed.
Click to expand...
Click to collapse
No, like I can't get into recovery AT ALL.

Pix12 said:
Restore the newest firmware.
Click to expand...
Click to collapse
I can't get into recovery to do so

WilliamTheKingAS said:
I can't get into recovery to do so
Click to expand...
Click to collapse
I would wait and see if anyone else comments. I have not yet had the unfortunate experience of being totally cut off from recovery. Sorry I couldn't help

I've even tried talking Amazon to giving me a replacement. I'm pretty sure his name was Ajit and he said I was off the 90 day warranty, so sadly I don't even know what to do. I did learn something though. Whilst trying to boot it into recovery it becomes stuck on the Amazon logo. What if it's in recovery, but just not showing any recovery screen. This is all I know what I can do??

So m
So my theory is that there is access to recovery, but when you're in it, it only shows Amazon until you force it off. Could this possibly help anyone fix their own fire 7 5th gen. Because if you find out anything hit me with it. It could be helpful to others reading this post.

WilliamTheKingAS said:
No, like I can't get into recovery AT ALL.
Click to expand...
Click to collapse
There is no recourse if you can not access the 'stock' recovery environment. The persistent Amazon logo simply indicates the device is stuck in the early stages of booting. Sorry for your loss.