Database Users

N7 stuck at loading screen, fastboot doesn't work, recovery mode doesn't boot.

I was running ParanoidAndroid perfectly until it crashed and not it gets stuck at the loading screen of the ROM (not the Google logo). I'm able to turn it off and get into Bootloader. From there if I choose Recovery mode, it gets stuck at Google logo.
If I plug it into the PC while in booatloader, it gets detected as "Android" but no driver (I'm sure I installed it before with the Toolkit). Toolkit just won't detect the device anymore, keeps getting stuck at the <waiting for device> command.
If I plug it into the PC while stuck at the ParanoidAndroid loading screen, I see MTP and Nexus in Device Manager but w/o drivers.
What can I do now? Any input is appreciated.
Thanks.

Bump.

Itaintrite said:
Bump.
Click to expand...
Click to collapse
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?

Xentar712 said:
Have you tried fastboot from the bootloader? Try this(assuming Windows):
-copy your recovery image of choice to your fastboot folder on your PC.
-boot to the bootloader with usb connected.
-open cmd window and navigate to fastboot folder
-type: fastboot boot insertrecoverynamehere.img
It should boot into the recovery from there. Make sure it's the same recovery you used for your latest backup.
Edit: I just read the subject line saying fastboot didn't work. Odd that it would just stop working from the bootloader like that. Have you tried manually updating the driver? Or maybe adb when it recognizes the device as MTP?
Click to expand...
Click to collapse
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.

Itaintrite said:
Thanks for the suggestion, but I figured out the problem. I'm such a dumbass. I forgot that last time I did this on a friend's computer. Apparently, the toolkit doesn't work properly on Windows 8 64-bit... (at least not on mine). I plugged it into a friend's laptop running W7 and was able to flash recovery again. Smooth sailing from there. Wonder what corrupted recovery.
Click to expand...
Click to collapse
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.

Xentar712 said:
I've never been able to cold boot my recovery - only through the goomanager app(for TWRP). I believe it's a known bug. I can only boot recovery from the bootloader when my N7 is plugged into my laptop via usb. Power or another laptop don't count. Oddly enough, It also works if I plug it into my Galaxy Nexus via USB+OTG.
Click to expand...
Click to collapse
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update

Itaintrite said:
Hm, perhaps that was the problem? But I was able to cold boot into recovery after reflashing TWRP... Anyhow, I'm glad I didn't have to restore a recovery image as I haven't made a backup since the last PA update
Click to expand...
Click to collapse
It worked for me only once after reflashing the recovery. Never again after that. Hopefully it gets fixed soon, but until then, I carry my USB cables with me if I'm flashing new roms
Sent from my Nexus 7 using Tapatalk 2

[Q] HELP!!!!!!! I may have brick my nexus 7

I'm not new to clockwork recovery, and I have flashed many Roms on my Nexus 7........ today I did a full back up of my latest ROM and I downloaded the latest version of the bug less beast .....I let rom manager do the back up and flash......then there was an error flashing the new rom and an abort and a reboot.......no im stuck on the google screen with the little un-locked lock at the bottom of the screen......if I reboot and go into recovery it just goes back to the google screen and stays there.....any clue as what I should do ??

Search around the forums for solutions.
Use the Wugs toolkit to make your work easier.

It's not bricked its standard procedure you just need to plug it in
Sent from my ADR6425LVW using xda premium

download .zip from google and restore it to your tablet (this is full wipe)

a1exus said:
download .zip from google and restore it to your tablet (this is full wipe)
Click to expand...
Click to collapse
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.

CharliesTheMan said:
To manually enter recovery from the bootloader on devices prior to 4.1.2 (don't know if it was fixed. its a glitch from google in the bootloader) you must have the USB (OEM of course) connected to a USB port on the computer. Then you can boot to bootloader and use the volume buttons to enter recovery. It may take trying a few times, like connect to usb port before powering on, connect to USB port once you're in the bootloader, etc, but that's your only issue unless when you panicked you tried some other solutions.
Click to expand...
Click to collapse
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen

GCSM said:
My recovery is not working I flashed clockwork mod and something happened to the recovery.....its like it not there....there is an option for it but when I enter it it just goes back to the google screen
Click to expand...
Click to collapse
dude, i'm told you what you need to do, i had erased manually my bootloader,recover,system,data and i was able to restore w/ what i told you it worked w/out any issues

Get fastboot. plug into your computer and do these:
fastboot flash recovery recovery.img (recovery.img is whatever file you have for recovery. IMO, get the newest touch recovery from CWM and have it in the same directory as fastboot)
fastboot reboot-bootloader
From there, leave it PLUGGED IN and get back into recovery. Worked for me.

[Q] Help with bricked Nexus 10

I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now

Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app

Thanks, that was pretty much what I did. The trick was to get it working in boot loader mode. I kept trying to reboot it, and in the end holding down power plus both volume up and down all at the same time for 2 beeps made it work.
Sent from my Nexus 10 using Tapatalk

nikkilocke said:
I am trying to root my Nexus 10. This is what I did, but it ended up bricked!
I installed the Android SDK on my Windows 7 computer, and downloaded the Android USB drivers and tools.
I turned on USB debugging, and checked I could see the device with adb list devices.
I downloaded recovery-clockwork-touch-6.0.4.3-manta.img, booted the tablet into bootloader, and flashed it
Code:
fastboot oem unlock
fastboot flash recovery recovery-clockwork-touch-6.0.4.3-manta.img
That seemed to work, so I went into recovery, but recovery had all sorts of errors - it couldn't find the sdcard, or mount most of the partitions.
Rebooting stops in the animated logo, apparently for ever.
I have since tried to reload the factory image, but the computer no longer recognises the device - fastboot devices returns nothing.
Help!!!
[Later] The tablet was running the latest O/S (if I could boot it, I could tell you the number!)
Things have got worse. Now, when I go into bootloader mode, the volume keys don't do anything any more, so I can't even turn it off now
Click to expand...
Click to collapse
I have the same problem, however I can't access my Nexus 10, fastboot devices and adb devices gives back an empty line, so I can't access the N10 with fastboot or adb, to lash a ROM. Factory reset from CWM doesn't work, ˛internal card can't be accessed from CWM ("E: Can't mount /sdcard).
How can I get out of this trouble? (Solutions in forums usually involve reflashing with fastboot or formatting the external SD card. These solutions don't work here...
Any idea would be highly appreciated...
Csaba

Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk

nikkilocke said:
Keep trying to reboot into bootloader mode, until it works. Hold down power and both volume buttons at the same time until it beeps twice. If the volume buttons then work to change the option on the left, but fastboot devices on the pc shows nothing, try reinstalling the Google drivers on the pc (via Device Manager, update drivers, have disk). (may have missed out a step in device manager instructions, but there are plenty of Google hits on installing add drivers if you don't already know how).
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
---------- Post added at 05:17 PM ---------- Previous post was at 05:00 PM ----------
ixxion said:
Sorry, I don't understand what you mean.
I can get into into bootloader mode after keeping the 3 buttons (power+volume up+volume down) pushed together (after two beeps). From there I can't boot the device. (Boot gets into the Google animation forever), so as factory reset.
Also device manager doesn't see the N10, so I can't update the drivers on my PC.
Csaba
Click to expand...
Click to collapse
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba

You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app

ixxion said:
After some repeated turning off and on, now I can see the N10 from the PC (also updated the USB drivers to be on the safe side).
If I enter the bootloader, fastboot sees the N10 in a normal form, if from there I go into recovery mode, adb sees the N10 in recovery mode. Should I proceed from here by using fastboot, or rather adb?
Csaba
Click to expand...
Click to collapse
Glad you have managed to make the device visible again (it's really scary when you can't, I know from yesterday!).
Go into bootloader mode (not recovery), and follow the fastboot instructions demkantor gave earlier in the thread.
Get your factory image from https://developers.google.com/android/nexus/images#mantaray.
Get TWRP recovery from http://teamw.in/project/twrp2/128.
At least, that's how I did it.

demkantor said:
Make sure fastboot is set up properly, may need to reinstall drivers or try another computer or try another USB
http://forum.xda-developers.com/showthread.php?t=2277112
I have a feeling the recovery you flashed was corrupt in some way, did you by chance check the md5sum of the image first?
If your able to get fastboot to recognize tab
fastboot erase recovery
fastboot erase system -w
fastboot erase boot
Download latest twrp recovery
Check md5sum
fastboot flash recovery nameofrecovery.img
Then you will either need to flash stock system.img from fastboot or boot to new recovery and adb sideload a ROM
Hopefully your emmc is not to severely corrupt to all this, best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How do I check md5sum?

Use this for windows
http://www.microsoft.com/en-us/download/details.aspx?id=11533
Or terminal for Linux
md5sum nameoffile.extention
Sent from my Nexus 7 using XDA Premium 4 mobile app

demkantor said:
You should just use volume up + power (or the whatever the volume rocker button closer to power key) never had it beep to get there
To both of you, follow the steps from above, so long as it isn't a hardware issue this will get you working
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?

ixxion said:
Thank you very much. Tablet is up and running again. :good:
Now, my next question, after being unsuccessful with CWM, I tried using TWRP for rooting the tablet, however it wouldnt start.
When I go from the bootloader into recovery mode only a laying android figure is displayed with a red triangle with an exclamation mark inside.
I have USB debugging enabled. What can be the problem?
Click to expand...
Click to collapse
That means you don't have twrp installed. That's the stock recovery. You can download twrp and use fastboot yo flash it or try the app twrp intaller which dies or fir you
Sent from my VS980 4G using xda app-developers app

Fastboot mode issue in MiA1

Hi.
Recently I decided to flash lineage os 15.1 on my MiA1
For that I have downgrade to Android nougat.
After downgrading I booted my device.
After setting up device I booted device in fastboot mode to follow further steps like flashing TWRP and all but the problem is my device goes in fastboot mode and it is not identified by abd and after that it is automatically getting restarted and is not holding in fastboot mode.
Please help??

Odd issue. What are you using to flash? If you are using XiaoMiFlash.exe, you'll want to try the (THIS WILL REMOVE ALL YOUR DATA) "clean all" option. Please note that this removes all your data.

I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.

MrUsamahh said:
I have used MiFlash tool for this and now My device automatically reboot from fastboot mode so I am not able to use adb as well to flash rom or twrp also Now MiFlash tool is not recognising the device.
Click to expand...
Click to collapse
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.

oreo27 said:
Hmm. What ROM version are you trying to flash on this? If your device isn't recognized by your PC when in fastboot mode, I'm not sure how you'd flash it.
Click to expand...
Click to collapse
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started

MrUsamahh said:
I flashed Android N Fastboot rom by selecting Clean and lock option.
After that the problem started
Click to expand...
Click to collapse
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.

oreo27 said:
It should boot if you've fully flashed it and cleaned the user data partition. If it still isn't, you'll want to wait for other members with more experience in bricks to chime in.
Click to expand...
Click to collapse
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?

MrUsamahh said:
My device is booting up without any problems.
But the problem is bootloader is still unlocked. So i am not able to update via OTA.
And as the device does not holds in fastboot mode so I am not able to do other flash work.
Is there any way I can share a video of my problem with you?
Click to expand...
Click to collapse
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.

oreo27 said:
Oh. If it's booting up fine, then you shouldn't be worried too much.
If it keeps restarting in Fastboot mode, it could be a driver issue which is preventing your PC from recognizing your device and vice versa. I'm on Windows 10 which installs drivers automatically so I've never had experience with it.
Click to expand...
Click to collapse
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.

MrUsamahh said:
https://photos.app.goo.gl/TyLendNH7XaY74bs1
Please see this video.
If i boot in fastboot mode the device should be in fastboot mode till power button is not pressed for at least 10 seconds.
But in this case it gets switched off.
I have not connected the USB to pc and nothing else.
Click to expand...
Click to collapse
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.

oreo27 said:
I think that's expected behavior? If it doesn't recognize itself being connected to a device, it'll exit fastboot mode.
I think you need to connect it to the USB cable and into your PC for it to not restart/power off.
Click to expand...
Click to collapse
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.

MrUsamahh said:
No when I connect it to pc at that time also same happens.
Previously when booted in fastboot mode it will stay ther by the time juice is out.
Click to expand...
Click to collapse
Yup. I just tested it out. It looks like you're right.

oreo27 said:
Yup. I just tested it out. It looks like you're right.
Click to expand...
Click to collapse
So do you know how can I help myself out?

wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.

Mizuru said:
wait.. what exacly did you do when you booted into fastboot? did you type "adb devices" or "fastboot devices"? also, try rebooting into fastboot mode by typing "adb reboot bootloader" in cmd, with your phone plugged into your pc, and with the proper platform-tools installed. it shouldn't really go away from fastboot mode like that.
Click to expand...
Click to collapse
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!

MrUsamahh said:
Hy man, I know basic of adb and I use cmd "adb devices"
My device is recognised when it is on.
I can also give various cmd like boot in recovery or fastboot mode or reboot and the device follow the instructions.
Please see the video that I've shared.
Once fastboot mode is on the device is automatically restarted in about 10 to 15 sec and within this time MiFlash tool or adb cmd prompt bot does not recognise my device.
I have tried to flash OTA via adb side load but it is showing error.
Help me with your input!
Click to expand...
Click to collapse
Your device doesn't get detected in your CMD prompt when it's in fastboot AND you type "fastboot devices"?
If it doesnt then you might have flashed something incorrectly.
Also, make sure to have your android drivers up to date in your pc. It's very, very likely that you don't have them installed on your PC, or they are outdated. See this: https://developer.android.com/studio/run/oem-usb.html
And this: https://developer.android.com/studio/releases/platform-tools.html

I have faced this issue. Yesterday i dirty flashed a custom rom. but i forgot how to dirty flash. i just simply flashed the rom and restarted the phone. it was mandatory to flash custom recovery and gapps after flashing a rom dirtily or normally. but i didn't. After the reboot completed, i remembered that i didn't flashed the twrp and gapps. So, i go back recovery mod, guessed i could flash twrp now. But i didn't see any custom recovery on my phone. But the phone boots, and i can use the phone. Still, i'm on that phone, while i'm typing this comment. i didn't lost my data cause i flashed dirtily. But the problem is, as i didn't flashed gapps or magisk (for root access), now i can't use google apps like, play store, and more. As i don't have root access on my phone so, i can't run flasify, to flash custom recovery. neither i can run other apps that need root. As i didn't flash custom recovery, now i can't flash gapps, magisk and whatever that needs a custom recovery.
I told some rom porter about the matter. They told me to flash stock rom. So, i was trying to flash stock rom. but flashing stock rom requires a fastboot mode. But my fastboot logo doesn't appear and it's blank. I told this to a rom porter. But he said, He doesn't know about that and he can't help.

Soft bricked phone: looking for advice

Hi
I would like to ask for some advice.
I've recently soft bricked my MI2S. I can boot to recovery (TWRP 2.8.1) and fastboot. The phone isn't recognised by Windows or Ubuntu, so I can't flash anything with fastboot. Actually, fastboot, adb or MiFlash don't detect the phone. I've tried to use a USB stick with an OTG cable, but TWRP doesn't detect the USB stick. If I boot to system, it stays on the MI logo (I can wait a full night, it won't change).
My question is, do I have a problem with my USB port? I'm equipped to solder a new one, if necessary. Or is my connection problem due to another reason? I wouldn't want to go through soldering if it is for nothing. Especially, when I started to mess up with the phone, it was locked with a different MI account (it was my wife's account, but it took me a few days to connect the dots together), and I couldn't connect with MiFlash, adb or fastboot either.
The steps I did to get it soft bricked:
Flashed TWRP 2.8.1 with fastboot
Rebooted to recovery
Rebooted to MIUI (a few times)
Attempted to flash TWRP 3.5.0 (my memory fails a bit there, I think I did it via fastboot)
The last didn't work because I'm still on TWRP 2.8.1
And I can't add any more zip file to flash via recovery, nor can I use adb sideload or flash with fastboot.
Any advice or comments are more than welcome. You may just have an idea that I didn't think of.
Regards
Matt

Quick update:
I don't know if you would agree, but I can't see my issue to be a software one (the device not being recognised)
I've ordered a USB port directly from China and I'll see if I can unbrick the phone from that point.

It's great that you can still access to recovery and fastboot.
First, I advice you to back up your data.
If you cannot use adb sideload or flash with fastboot.
Try in fastboot mode
- fastboot erase cache;
- fastboot erase system;
- fastboot erase userdata.
See if that can solve your issue.