Nexus 7 No Recovery/No Fastboot RESOLVED PLEASE DELETE - Nexus 7 Q&A, Help & Troubleshooting

Hey XDA!
Got my Nexus into some trouble today. I Was running stock rooted 5.0.2, received an OTA update for 5.1. Ran the update and it sent me to my TWRP 3.0 recovery. Restarted the device and found out the update did not work, leaving me at 5.0.2. Ran the update again like a tard, took my to the stock bootloader. TWRP is now no where to be found... In fact there is no recovery to be found. When I select the recovery option in the bootloader it goes to black screen then redirects back to the bootloader. When I select the "start" option, it's reboots the device taking me to the bootloader. I have attempted a hard restart with the power button but the device hangs on the Google logo forever. I have tried to use the Nexus Root Tool but it can't help me since the device won't connect via fastboot, or ADB.
Any help is appreciated.

Hallo,
got the same problem, how did you resolve it ??? Thanks a lot ...

Same here. I can't connect to the device by no means. How did you solve your problem?

Tallyphillips said:
Hey XDA!
Got my Nexus into some trouble today. I Was running stock rooted 5.0.2, received an OTA update for 5.1. Ran the update and it sent me to my TWRP 3.0 recovery. Restarted the device and found out the update did not work, leaving me at 5.0.2. Ran the update again like a tard, took my to the stock bootloader. TWRP is now no where to be found... In fact there is no recovery to be found. When I select the recovery option in the bootloader it goes to black screen then redirects back to the bootloader. When I select the "start" option, it's reboots the device taking me to the bootloader. I have attempted a hard restart with the power button but the device hangs on the Google logo forever. I have tried to use the Nexus Root Tool but it can't help me since the device won't connect via fastboot, or ADB.
Any help is appreciated.
Click to expand...
Click to collapse
you mention it wont connect via fastboot but you can still reboot with the pwr + vol- to get menus of some kind.. ? if the screen is backlite even just a blank screen but you can see it light up theres still hope. All i can say is try to reboot the device into fastboot an then try Nexus Root Toolkit an see if you can reset to Factory to restore the stock recovery partition along with reset the OS to which ever you select and start over .. Good Luck Flashing... the only way i can say your SOL is if when you plug it into your PC an it pops up with the error "Device Malfunctioned,....." then you SOL Good Luck Flashing :good:
EDIT: Sorry didnt notice it was resolved in the title..

Related

Please help! Nexus 10 stuck on google X during failed root :(

Hey guys
I tried the one-click root toolkit for mac from android rootz.
Something apparently has gone wrong during the root and I got some error messages and it didn't proceed. Next thing I know the nexus is stuck on google X logo and that's it. It won't load. I tried to recover through the recovery mode a couple of times but now I get the red warning sign when I go into recovery mode. This is only the second day I've had the nexus for. I feel like crying. Please Help
When the red sign appears press the volup down buttons and power button randomly until you get into recovery then factory reset
My 7 and 10 both did that. Just hold power until it turns off, then boot a recovery, wipe everything except system and reboot. It'll come up ok.
Sent from my Nexus 10 using Tapatalk HD
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
scooterbaga said:
I'm having the same issue. However, the recovery I have installed is the non-functional CWM. So I can't factory reset. (I managed to once before CWM bombed, but it didn't change anything.)
I've tried several options via the toolkit. After fighting with the app all day it's finally wound up just saying it can't find adb? (I have a growing dislike for this app and have since uninstalled it.) Adb is right where it belongs and seems to run fine from cmd.
I also can't seem to flash anything via fastboot for some reason. The device throws "failinvaild id command" and fastboot immediately crashes on my laptop.
I managed to get it unlocked. However, I'm unable to flash anything to straighten it out...
Any help would be great.
Click to expand...
Click to collapse
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
bg1906 said:
Watch this video starting at the 6:30 mark.
http://www.youtube.com/watch?v=YtLvlrUDB04
Click to expand...
Click to collapse
Thanks for the info. My situation wasn't quite the same as my CWM was the real issue, which wouldn't run long enough to allow for the factory reset boot-loop solution. Kept at it and managed to get CWM to finish the individual formats/resets one at a time.
With a now bootable device, I'm off to replace the recovery... Thanks again.

locked bootloader wont unlock

Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers
truebattleaxe said:
Hi everyone. Here is the deal im having with my nexus 7 (not the 2013 model) with jop40d.zip. The person I purchased from didnt tell me it was soft bricked. It seems as though he tried to root it but failed while at the same time relocked the bootloader. So I've tried almost everything in my mind to get it back to normal. It wont let me adb sideload the stock rom it says "installation aborted" or any other rom. Also when i boot up it goes directly to the bootloader which gives me the options start, restart bootloader, recovery mode, power off. start obviously does nothing. restart bootloader just for some reason turns the device off, recovery mode takes me the caution sign where i can adb sideload or factory restore. factory restore hangs and doesn't do anything then shuts off. adb sideload always fails when loading up the zip files. i factory restored the cache. I'm not sure what to do anymore. I spent a fair amount of money on this device but now it all seems like a mistake. Can anyone who has fixed this issue help me out? I would deeply and greatfully appreciate it.
-Cheers
Click to expand...
Click to collapse
also I wanted to add. I have the android sdk installed and all drivers installed properly. as well as adb/fastboot.
Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Stop trying to use adb, follow the sticky at the top that says flashing a factory rom using fastboot/return to stock. If you can't type fastboot devices and get a serial number return then the drivers are not installed properly.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
hey slow cobra. yes fastboot does recognize the device. however fastboot oem unlock doesn't do anything.

Lollipop OTA Failed Update!

Hi,
Last night google pushed out the Lolllipoop update to my phone. I have stock android, nothing is rooted or changed.
It downloaded the update, installed it and rebooted into a forever lasting startup animation.
After a night of this i tried to restart the phone, same situation as above.
I resorted to go into recovery mode and wipe the phone, get image of dead droid stating command not find.
Atleast bootloader works.
I use mac, im a bit geeky, but i have troubles find a good guide that lets me completely flash the phine back to 4.4 when you are in the situation of a halfass os on your phone.
HELP or at point to where i can complain to google
ropapa84 said:
Hi,
Last night google pushed out the Lolllipoop update to my phone. I have stock android, nothing is rooted or changed.
It downloaded the update, installed it and rebooted into a forever lasting startup animation.
After a night of this i tried to restart the phone, same situation as above.
I resorted to go into recovery mode and wipe the phone, get image of dead droid stating command not find.
Atleast bootloader works.
I use mac, im a bit geeky, but i have troubles find a good guide that lets me completely flash the phine back to 4.4 when you are in the situation of a halfass os on your phone.
HELP or at point to where i can complain to google
Click to expand...
Click to collapse
Long lasting boot animation means, it is call boot-loop. It happens to some people (including me) who upgraded to Lollipop. Try factory data reset using stock/custom recovery and see it is booting or not. It worked for me and some other people.
Factory data reset will erase all your data.
steps to boot in to stock recovery
1.Power off the Nexus 4.
2.Press and hold at the same time Volume Up, Volume Down and Power buttons.
3.When you’re at the Bootloader / Fastboot main screen press Volume Up until the Start text turns to Recovery mode.
4.Press Power to boot the Recovery Mode.
> shortly you will see a green Android laid on its back with a red exclamation mark.
5.Press and hold Power button and immediately press the Volume UP.
This will open the Stock Recovery mode of your Nexus 4.
You can download factory images for Kitkat 4.4 and Lollipop 5 from google website. Extract that file and you will find a file with the name Flash-All. Simply running the Flash-all script will erase all the contents in the phone. To avoid that, just remove the -w from the line
fastboot -w update ....zip
I hope this helps you!:good:
[resolved] Thanks
Thank you,
This should help people in the same situation. I did not manage to test your solution but the logic is there.
I found a toolkit for mac that rooted and installed kitkat 4.4.4. for me.
When google pushes lollipop again and if a boot-loop happens again, i will definitely give your method a go!
Thanks,
R

[Q] Rooted Nexus 10 Stuck in Bootloop, Please Help!

Hello all,
Any help with this would be seriously appreciated. I rooted my Nexus 10 a while back, maybe two years ago. I'm not very proficient with this stuff. Anyhow I decided to do the OTA upgrade to 5.0...I was concerned something would go wrong unless I went to stock first, but I read that the only thing that would happen is root would be removed.
Anyhow, the tablet appears stuck while booting. I see the Google screen first with the unlocked indicator on the bottom. A few seconds later is the Android logo on its back, a red triangle over it with an exclamation point and "no command" written below". It stays that way for a minute or so, tries to reboot and goes back to the no command screen. I can't even power off, when I try to do so it just powers back on by itself and ends up at the no command screen again.
I tried booting into recovery (power, volume up, volume down). My options from here are either Start, Restart Bootloader, Recovery Mode or Power Off. Every option I choose leads to the No Command Screen (except power off, which powers off). No idea what to do from here.
Any help at all would be appreciated. As you can probably tell I don't have much experience with this and just wanted to go back to unrooted stock. If you have advice, please be clear. I can follow directions well enough, just don't have much experience here. Thanks in advance.
Same here, bootloop.
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Guys, if your device is connected in fastboot (try "fastboot devices") then you can flash roms or recovery (and then flash rom) from there. There are multiple threads with the same problems out there which were fixed. E.g: http://forum.xda-developers.com/nexus-10/help/bricked-t2948546
In my example, I flashed TWRP recovery from fastboot, then installed custom ROM from recovery (official ROM failed to install for some reason). Try this, it might help.
danweis said:
Same thing here. A seemingly short download of Lollipop (even though I have 50Mbs internet). Installation, reboot, and now it loops endlessly. I can get to the bootloader or into Download mode, but that's all. Recovery mode just reboots. I was rooted and had TWRP installed. Other than that, I was running stock 4.4.4.
I've rooted all my devices, and installed various ROM's on several devices. I have the full ADB installation. I have the Nexus Root Toolkit installed. The problem is, the device will not show up under "Devices" on the computer itself. I've installed every USB driver there is (and uninstalled each one after it does not work, so no I do not have several USB drivers installed). Of course nothing shows up using "adb devices" either. Nexus Root Toolkit also cannot find any devices. I've read everything on this subject I can find, and there are no answers out there. Anyone have ANY ideas??
Thanks
Click to expand...
Click to collapse
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Aresmar said:
Go to Fastboot mode (pwr+both volumes), Than select recovery after a while an android with Exclamation mark appears which is a stock recovery screen. To access the stock recovery menu press and hold power than press one of the volume keys so the menu will appear. Than do a factory reset and clear caches. You can than reboot and wait for boot animation to finish (it wont take long this time) and you will boot.
If this doesnt work you can flash a stock factory image easily from fastboot again.
Click to expand...
Click to collapse
I also had the same problem... I followed these instructions and now my Nexus 10 can boot normally (it took a long time to boot).
Only problem is all my data was deleted.... stup*d f*cking sh*t!!!!!!!

How to boot LG Leon into recovery?

I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Yeah, it was because the stock recovery doesn't exist as a menu, when you're running stock and enter the adb command "adb reboot recovery" it will reboot to the "factory reset mode" and the actual file of this mode is stored on partition named "recovery". Choosing the factory reset option boots the custom recovery because it replaces the said " factory reset mode" and that's the trick.
You can access recovery from the powered off state by holding volume down and power on until you see the lg sign. Without letting go of volume down, depress on the power button before clicking it back in and holding both buttons in until you see twrp pop up.
If you reboot to recovery now, it''ll probally say secure booting error. Simply go to the Developer options and enable OEM Unlock and that'll make you boot to it
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
kruc Ire said:
You boot in the download mode by holding the vol up 10 seconds and during this 10 seconds you insert the usb. The LG Leon brand screen will come on a minute then it will go into download mode. It says not to unplug until firmware is done updating. So I guess you should have your custom recovery or whatever before you do this. I have only got this far, and thusly it sits. All Dressd up with no where to go...haha
Click to expand...
Click to collapse
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
kruc Ire said:
can't find "enable OEM" at all in developer options. have phone hooked computer, and on, it's sending and receiving. No OEM. Isn't there.
See, I'm trying to root this without using KingUser. Since I found that it was pretty easy to do from the very beginning with Samsung, and I just don't see any way to do it here. I can't get ADB Devices command to see the phone.
Click to expand...
Click to collapse
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
duffycop said:
I think I have the same issue, but I rooted my phone using kingroot, I haven't tested the adb commands, I just want to use twrp but no luck, it says Secure booting error and I can't find OEM Unlock option in Developer Menu.
Click to expand...
Click to collapse
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
kruc Ire said:
I got a good way to get it rooted with SuperSU. Ran a command window script I found out there. It worked and now I have SuperSU root. I also figured out how to get into recovery. It looks as though my phone is not the standard LEON that people are talking about here. It's got a few designations, and the T Mobile site advertises a Leon that seems very similar and is called by the name most are using..
Anyhow my LG Leon is designated as a H320. It also carries a v10 desiganation, v10b. The v10 is variable from a-h or a-i. It would seem that once it is updated to 5.1.1 android it gets upped, and becomes unrootable. Mine being a v10b was rootable, but it took me a while to get used to it, and make the command window work.
Unfortunately for me one of many things I tried before getting it rooted, was ADB fastboot. And since this told me to wait for too long, I pulled the plug on it and pulled the battery to get back into "normal" operations. Perhaps I should have waited, because after finding out a few things about the phone, I discovered the true way to get it into recovery:
The real way into recovery for my phone, is to (from power off state) hold the volume up, a few seconds, then plug the USB cable which is going to the computer into the phone. While holding the volume up until it comes to recovery. This will activate the recovery, (Now for me it activates that fastboot command line...and does nothing else). This was the bit of information I could have used from the beginning, that no one knows. All these places tell you to hold the power and volume up, and then let off power when the screen changes, but that never worked even once. You just hold the volume, and plug the USB from computer. This works.
For me it goes into a "FASTBOOT" header at the bottom of the screen that never changes.
I believe it does this because of my unsuccessful attempt to fastboot it before. And it does not have the right driver to get recognized in the computer. So I'm screwed as far as the recovery goes now.
It is rooted though. And it doesn't seem to have any alternate ROMS available anyways. so we're dealing with the loss of the recovery.
When I do try to use an app such as TWRP manager or CWM (ROM) Manager to reboot into recovery, I get a "boot certification verification -1" error instead of the fastboot line at the bottom of the startup screen and it boots normally from there. So many people asked about this "boot certification verification -1" and NO answers are available anywhere online. So that's where it stands for this phone right now.
Anyone know what driver I should use to get the thing recognized in the computer? I have downloaded a zipped fastboot tools, and it won't get recognized inside the driver manager as "android" only as "unknown device" so I can't use that route....I'm thinking about doing a factory reset to try to erase the fastboot attempt. That may not help though. Anyone?
Click to expand...
Click to collapse
I dunno, I have the H340AR, with this phones happens the same that with the Samsung Galaxy Ace 3, there are, 3G versions, 4G versions, regional versions, etc.. GA3 have 7275R, 7275B, 7272L, 7272T, I dunno, maybe if we could get a device tree for a H340 and an H320 we could make some TWRP and CM compiling, but I just can't figure it out how to make a device tree or even where to begin..
I successfully rooted my H340AR with Kingroot, it works like a charm. I haven't tried fastboot and I tried to install TWRP in this link https://dl.twrp.me/c50/ but I get that F error "Secure booting error". I guess I have my bootloader locked, so I'm trying to figure out how to unlock my bootloader.
I'm trying to contact with some developers and see if anyone can help me build a device tree.
]
Hi, I have that same phone H340AR LTE. I rooted it with Kingroot and also tried to use TWRP to gen into recovery and got that Security error. I only pulled out the baterry and turn it on again so it booted normally. I made a factory reset because I read that it could be a problem of OTA firmware update. Then I installed TWRP and BusyBox again and tried to get into recovery from TWRP option. When I did that, it showed up the Android lying in his back with a red triangle. I pulled a out the battery again and yes, it seems very dumb and simple but it worked and could reboot the phone.
However, I can't get into recovery from TWRP yet. I read that the problem with us not being able to unlock the bootloader(we don't have the OEM option) is because Leon has Lollipop 5.0.1 and OEM is for 5.1.1
pedrovay2003 said:
I've successfully rooted my T-Mobile LG Leon, and I've successfully installed TWRP, but for the life of me, I can't get the phone to boot into recovery. I can RE-boot into recovery from TWRP manager, but I can't actually boot into it from a fully powered-down state. I've tried every combination of the power and volume buttons I can think of, and nothing ever works. Download Mode works, the factory restore menu works, but I CANNOT get into recovery. Is there a very specific set of instructions anywhere that I can follow?
EDIT: Okay, I finally figured it out: You need to actually select to do a factory reset, and it throws you into the recovery menu.
Click to expand...
Click to collapse
when i pressed factory reset all it did was to a factory reset even though i flashed twrp.img successfully... help?
lg leon h345 lollipop 5.1.1
This device has a locked bootloader. If you flash a custom recovery on it, it will not boot into recovery, but will report a security issue. You will lose all recovery functionality, including factory reset, adb, fastboot. If your phone fails to boot, you have a brick.

Categories

Resources