Database Info

[HELP] Nexus S can't boot recovery

Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!

Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot

albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!

You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.

albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?

Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.

I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance

Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.

polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s

Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?

polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked

Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.

You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q

UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes

polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...

I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!

[Q] No Fastboot Mode. Stuck in unfamiliar 'Cyanogen Recovery'

So my OnePlus One started dying when I would still have about 10% left. I thought it might be a bug or something with he CM12 nightlies so I wanted to revert back to stock. I transferred all of my media to my comp, got the 64gb zip from the "Revert back to 100% stock" thread, plugged my OnePlus One in, went into fastboot mode, made sure my comp recognized my phone ("fastboot devices") and clicked the "flash-all.bat" or whatever (not on MY comp right now, don't know the exact name) aaaaand some crazy stuff happened.
My phone started rebooting constantly, back into fastboot mode. This isn't how it worked with my Nexus 5 but the command window looked like it was doing what it was supposed to do. Then it got to sending the "system" and FAILED saying the file was too large. My phone rebooted and now it doesn't get past the first splash screen with the 1+ logo and "powered by android"
When I try to get into the bootloader nothing happens, but sometimes I get into the "Cyanogen Recovery" which I've never seen before. I wish I could take a screenshot and post it. It's options are:
Reboot system now
Apply Update
Wipe data/factory reset
wipe cache partition
wipe media
If I could get into fastboot mode I think I would be fine, but I can't.
When I go to "Apply update" I have the option to "apply from adb" and do the adb sideload thing, which I'm not very familiar with.
I think I might be in trouble, could anybody help me?

Is adb working while in recovery? It should. Try using the adb reboot bootloader command.
Transmitted via Bacon

Try pressing Power + Volume Up until your phone boots into fastboot mode and then run flash-all.bat again. If it is not working again, boot to fastboot mode and do all the steps by hand.

Nexus 5 stuck in the worse bootloop [tnks 4 the help in advance]

Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED <remote: flash write failure>
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
phone details:
hammerhead d821(E) 32GB
hw version- rev 11
bootloader version: hhz12k
Cheers
Mattia

I think your emmc chip has gone bad and that is why you are getting locked bootloader everytime you reboot the phone as it is not able to hold any memory.
I suggest RMA if its in warranty

tiapnn said:
Hi everyone I first want to sincerely thank everyone that will answer to try to help me solve these problems with my nexus.
So the other day my nexus suddenly decided to stop being awesome and it started to be a pain in the ass instead.
When I turn it on it just keeps loading the booting animation of android 6 marshmallowand it never turn on. I identified this problem as a "bootloop" and i tried solving it anyway but it's being really hard and i'm almost getting no results.
I first tried with going into recovery mode. from the fastboot the recovery mode won't start, pops out a died android with a red triangle on it. Pressing volume up and power from that screen got me to another menu. I tried wiping the cache and wipe all the datas/ factory resets but no results. the crappy marshmallow animation goes on till forever.
On the screen that follow the dead android appears the error: E: failed to mount /cache (Invalid argument).
After that i tried with the famous sdk tools.
I am able to unlock the bootloader with the command [fastboot oem unlock]. however after unlocking it, if I turn the phone off and on again it auto lock itself.
i tried to flash a recovery image with the command [fastboot flash recovery recovery.img] but it won't flash. I unlock the device first, and then i try to flash the images. it says ok after the sending but on the writing says FAILED
same things happen flashing anything else (android factory images etc.)
I can't use adb, i d need to put the usb debugging mode from the developer options but since I coulnd't turn it on I don't know how to turn this option on.
So i discovered existed a "download mode"
Apparently for the nexus5 you have to push volume up and then connect it to the usb to enter in it. I tried many times and it just don't go to download mode (is this the correct procedure??)
I installed the last google divers, no results.
I really don't know what to do, do you guys have any ideas about how to save it?
phone details:
hammerhead d821(E) 32GB
hw version- rev 11
bootloader version: hhz12k
Cheers
Mattia
Click to expand...
Click to collapse
OK so ur ennc chip is NOT dead, that little Android with the triangle is stock recovery, which u can do nothing with, ur going to need a PC, preferably running ubuntu or some other form of Linux with adb and fastboot installed, i cam help with that too if u need it, once u get that settled what u need to do is this, download TWRP for ur hammerhead and rename it recovery.img, place it in a folder u have access to. Open a terminal and connect ur nexus to the pc with USB cable, and boot into bootloader. Then type this into the terminal:
cd (folder with recovery.img in it)
fastboot reboot bootloader (this should boot u back into bootloader if ur device is connected right)
fastboot flash recovery recovery.img
fastboot reboot recovery
This will boot u to TWRP in which u can perform a factory reset, if this doesn't work and ur still in a bootloop, download ur fav rom and gaps and flash it, this will take care of everything
And there is no download mode on the nexus that would be bootloader mode, so let me get this right, what system are u on, and did u try manually formatting with ADB? What happens when u do, I would force format cache, system, boot, and userdata and then flash recovery, that might work
Sent from my Nexus 6 using Tapatalk

Stupid me, tried Auto Root CF for Pixel and now it is bootlooping badly, No ADB

Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.
It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.
I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.
ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.
Any body have any ideas?

boot-to-root is for Android O, you have to follow this guide

I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.

You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/

jdkzombie said:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
Click to expand...
Click to collapse
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:
fastboot flash --slot _a boot boot.img
fastboot flash --slot _b boot boot.img
Then reboot normally.

falsh factory image inside the bootloader, don't need to go to recovery.

Step by Step
Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.
So for the less patient I will break down the steps to do stop the bootlooping.
DON'T PANIC
Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.
Hold Power + Volume Down until it boots into the Fastboot mode.
[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]
Connect your Phone to your computer using a USB 3.0 port.
[My PC wouldn't recognize my phone at all when connected to USB 2.0]
Download from Full Factory Image from Google. { https://developers.google.com/android/images }
[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]
Navigate to where your SDK/Fastboot folder is on your PC
[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]
Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).
Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.
["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]
Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.
Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.
At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.
Good Luck.

Factory mode formats ALL data? Start up failed, only bootlader problem?

Hello guys, I try to explain myself as best as I can.
I have a Motorola Moto G7 power NOT rooted.
I tried to clean the cache from the menu that appears with Volume down+Power on. I chose "Recovery mode" but no menu appeared. So I chose "Factory mode", I thought that various voices appeared, but from that moment the phone hasn't started up anymore and he tells me:
Code:
start up failed
your device didn't start up successfully
use the Software Repair Assistant on computer to repair your device
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot reason: Fall-through from normal mode
I downloaded that software but it will flash the device.
I have already tried:
- "restart bootlader": it remains on recovery mode.
- "recovery mode": for half a second, the Motorola logo appears and then:
Code:
start up failed etc
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
- "start": same error above
Now, beyond the fact that I ****ed up and I am aware of it, can I recover only the bootloader? When I chose "Factory mode" none writing appeared, so... it's possibile that my phone was completely formatted in one second? I thought the data, settings, etc are still there but it just screwed the bootloader, is it possible? And how to fix it? I found only guide to flash the phone.
Thanks.

Solved!
Luckily, "factory mode" did not cancel my data, I searched better on the forum and found a way to flash the original firmware without losing data. The Software Repair Assistant flashes only with complete formatting, so you have to change a string of a flashfile.xml before flash with the Software Repair.
Thanks to here and here for the instructions, here a summary:
(The program does not have the download progress bar. You can see the full download from:
- the Rescue now button turns orange
or
- the complete file in C: \ ProgramData \ LMSA \ Download \ RomFiles \ YOUR_FILE.xml )
Once the firmware is downloaded, don't continue with flashing.
Open C:\ProgramData\LMSA\Download\RomFiles
Select the firmware for the device you want to flash
Open the flashfile.xml with a text editor like notepad++ (https://notepad-plus-plus.org/) (I used standard notepad)
Delete this line
Code:
<step operation="erase" partition="userdata"/>
save the changes
Continue the flashing with LMSA
Click to expand...
Click to collapse
At the end, the phone turned on as I left it, apps, data, settings, everything
PS: you can find the Software on the official lenovo support
https://support.lenovo.com/in/en/downloads/ds101291

Sbubba said:
Hello guys, I try to explain myself as best as I can.
I have a Motorola Moto G7 power NOT rooted.
I tried to clean the cache from the menu that appears with Volume down+Power on. I chose "Recovery mode" but no menu appeared. So I chose "Factory mode", I thought that various voices appeared, but from that moment the phone hasn't started up anymore and he tells me:
Code:
start up failed
your device didn't start up successfully
use the Software Repair Assistant on computer to repair your device
AP Fastboot Flash Mode (Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot reason: Fall-through from normal mode
I downloaded that software but it will flash the device.
I have already tried:
- "restart bootlader": it remains on recovery mode.
- "recovery mode": for half a second, the Motorola logo appears and then:
Code:
start up failed etc
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Boot up failed
- "start": same error above
Now, beyond the fact that I ****ed up and I am aware of it, can I recover only the bootloader? When I chose "Factory mode" none writing appeared, so... it's possibile that my phone was completely formatted in one second? I thought the data, settings, etc are still there but it just screwed the bootloader, is it possible? And how to fix it? I found only guide to flash the phone.
Thanks.
Click to expand...
Click to collapse
Edit:
I'm not sure why selecting factory mode would cause such a problem.
Glad you got it working again.
Sent from my Moto E (4) using Tapatalk