Help me save my nexus 7 please! - Nexus 7 General

Stupid story short my jellybeer's android crashes upon boot up, I forgot to turn usb debugging on before I killed it, When I go into recovery it locks up on the google logo, but I can get into fastboot which if i'm correct i could adb into it right?

Download the wug fresh toolkit and click flash back to stock and unroot and check device can't boot option
Sent from my Nexus 7 using Tapatalk HD

Thanks, I installed the ADB drivers and it suddenly went into cwm.

Ohh sweet
Sent from my Nexus 7 using Tapatalk HD

Related

Can't get into recovery from bootloader

Hi all. So I got myself into a boot loop and that usually isn't a big deal on a nexus. Power off. Boot into bootloader, and select recovery. Boom. well I am unable to get into recovery that way. I can reboot into recovery from a rom no problem. And I can adb into it with reboot recovery. Just not through the bootloader like usual.
Any thoughts?
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Awexit76 said:
Hi all. So I got myself into a boot loop and that usually isn't a big deal on a nexus. Power off. Boot into bootloader, and select recovery. Boom. well I am unable to get into recovery that way. I can reboot into recovery from a rom no problem. And I can adb into it with reboot recovery. Just not through the bootloader like usual.
Any thoughts?
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Known bug with all the Recovery's.... have to use an app or terminal
Sent from my Nexus 7 using Tapatalk 2
DJLamontagneIII said:
Known bug with all the Recovery's.... have to use an app or terminal
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Can't use an app if in boot loop.
You will need a computer and type
Adb reboot recovery
Or if you want bootloader
Adb reboot bootloader
Sent from my Galaxy Nexus using xda premium
-SNIP-
DJLamontagneIII said:
Known bug with all the Recovery's.... have to use an app or terminal
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Interesting. Haven't heard that. But would make sense. Twrp and cwm both wouldn't.
And yeah, fastboot commands work fine. So I wasn't lost. Just might not always be near my comp
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Bootloop to recovery
Awexit76 said:
Interesting. Haven't heard that. But would make sense. Twrp and cwm both wouldn't.
And yeah, fastboot commands work fine. So I wasn't lost. Just might not always be near my comp
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
If you get caught in a boot loop, here is how you need to get into recovery with the Nexus 7.
Hold volume up, volume down and power until it boots into bootloader.
Plug into USB on your Windows Computer.
Open Command prompt (in fastboot folder)
type: fastboot reboot-bootloader
It will now reboot into bootloader. You can now unplug the USB, scroll down to Reboot recovery, press power button, and it will reboot to recovery.
(Please note you have to be unlocked, rooted with a custom recovery to do this!!!)
Update, you don't have to use fastboot, or even have drivers installed. You just have to be plugged in to any comp usb. Mac windows whatever. Then you can enter recovery from bootloader. Wierd huh
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Awexit76 said:
Update, you don't have to use fastboot, or even have drivers installed. You just have to be plugged in to any comp usb. Mac windows whatever. Then you can enter recovery from bootloader. Wierd huh
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Has this bug been fixed? Or will ever be? Need a cwm update or is it a Google problem?
Bootloader problem apparently. All recoveries, including stock can't access. Hopefully someone or Google will fix eventually
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Awexit76 said:
Bootloader problem apparently. All recoveries, including stock can't access. Hopefully someone or Google will fix eventually
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
Don't trust custom bootloaders, ever
Sent from my Jelly Nexus S
Awexit76 said:
Update, you don't have to use fastboot, or even have drivers installed. You just have to be plugged in to any comp usb. Mac windows whatever. Then you can enter recovery from bootloader. Wierd huh
Click to expand...
Click to collapse
Doesn't work for me, when I do that, instead of hanging at the Google logo indefinitaly, it eventually reboots (crashes?) and boots up normally into Android.
But I'll try the "fastboot reboot-bootloader" while being in bootloader thing, if that works, good enough for me.
Yet yes, I hope they'll bring out a fixed bootloader - but I don't really think they will.
So there is still nothing we can do with that? ;c
ireun said:
So there is still nothing we can do with that? ;c
Click to expand...
Click to collapse
Well custom rom's advanced power menu works, trinity kernel toolbox, goo manager I think, and apps like that all work. But if you bork it into a bootloop you'll need a USB connection.
Until there's an update from google or someone writes a new bootloader that's how it will be.
If it helps...
After much testing (and after update)
IT HAS TO HAVE USB when VOL DN +VOL UP + ON (only) from off
Later insertions do not work.
I bet it is not a bug, I bet they wrote code for external power check during entry to recovery, etc. Thus, I also bet it is deliberate, NOT a bug, and will not go away.
There are instructions all over the web about when to plug in, on mine it has to (only) be at VD, VU, +ON.
I made a list of operations and screen responses as I tested, if of value...
Iam using trinity tool to boot into recover. It is working fine.
Sent from my Nexus 7 using xda premium
Awexit76 said:
Update, you don't have to use fastboot, or even have drivers installed. You just have to be plugged in to any comp usb. Mac windows whatever. Then you can enter recovery from bootloader. Wierd huh
Sent from my Nexus 7 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
i did it with a Nintendo wii once
Sent from my Nexus 7 using xda app-developers app
Well thx but, as why not everyone have this problem?
Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
ireun said:
Well thx but, as why not everyone have this problem?
Wysyłane z mojego Nexus 7 za pomocą Tapatalk 2
Click to expand...
Click to collapse
I just had this problem. 2 hours ago I never had this issue.
This started happening when I flash Franco's kernel.
Before I can boot to recovery by going to bootloader then choose recovery. Now I can't!
I even flash stock / re-locked and it still a no go.
I can only boot from recovery thru fastboot or while inside Android.
WTH!
EDIT: Could it be related to the build?
Here are my findings:
a) I used my mom-in-law's nexus 7 stock, never rooted = c8O = It DOES not boot to recovery from hardware buttons (bootloader then choose recovery) - but It boots to recovery from bootloader only when it is connected via USB
b) I have a C9O which was working before, but I flashed to STOCK (recovery using the Toolkit) then It can't boot anymore - so it might not be Franco's kernel
c) Friend's C9O stock, never rooted = CAN boot to recovery without having to plug in the USB.
Weird .. so maybe google will fix this.
Had this problem last night after flashing the latest AOKP. Kept getting stuck at the google screen and couldnt get into recovery at all. I downloaded the Nexus toolkit and was back working in 2 minutes. Highly recommend to anyone who has a similar problem
bovineyard said:
If you get caught in a boot loop, here is how you need to get into recovery with the Nexus 7.
Hold volume up, volume down and power until it boots into bootloader.
Plug into USB on your Windows Computer.
Open Command prompt (in fastboot folder)
type: fastboot reboot-bootloader
It will now reboot into bootloader. You can now unplug the USB, scroll down to Reboot recovery, press power button, and it will reboot to recovery.
(Please note you have to be unlocked, rooted with a custom recovery to do this!!!)
Click to expand...
Click to collapse
you sir are a life saver, I was just stuck in bootloop and this workeD!:silly:

My nexus one won't boot

I have a rooted nexus one running cm7.2 and it won't boot to boot loader or recovery or rom o
Sent from my SGH-T959 using xda app-developers app
Or fast boot so I can't do anything am I bricked
Sent from my SGH-T959 using xda app-developers app
Try to use passimg.zip method. Google it download that zip put it in or main SD. Hold trackball + power button. Good luck
Sent from my Nexus One using Tapatalk 2
I can't get to fadtboot or boot loader so I cantbdo passimage
Sent from my SGH-T959 using xda app-developers app
n1noob13 said:
I can't get to fadtboot or boot loader so I cantbdo passimage
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Do you have ADB and fastboot software installed in your PC? Either have that or download Android SDK. You can boot your phone via ADB command lines.
Yes I have it but nothing will work the charging lightbwont lightvwont light up orbanything
Sent from my SGH-T959 using xda app-developers app
Your phone needs a JTAG repair.
Sent from my Nexus One using xda app-developers app
humzaahmed155 said:
Your phone needs a JTAG repair.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
what is mean?
Search.
hi
humzaahmed155 said:
Your phone needs a JTAG repair.
Sent from my Nexus One using xda app-developers app
Click to expand...
Click to collapse
Hi. my N1 is totally dead(i think) wont boot still showing X logo and lock. I tried everything. When using Nexus 7 toolkit, toolkit say device found (showing serial number). But when i try flash using adb command everytime i get message device not found. What is problem, what is wrong?
Thanks
bagi576 said:
Hi. my N1 is totally dead(i think) wont boot still showing X logo and lock. I tried everything. When using Nexus 7 toolkit, toolkit say device found (showing serial number). But when i try flash using adb command everytime i get message device not found. What is problem, what is wrong?
Thanks
Click to expand...
Click to collapse
Can you reach the boot menu by pressing the volume down key while powering on?
Otherwise, try to check if fastboot is able to see your device and flash some new boot and system image
You have a Nexus One, not sure why you're using the Nexus 7 Toolkit..
hi
tommert38 said:
You have a Nexus One, not sure why you're using the Nexus 7 Toolkit..
Click to expand...
Click to collapse
Hi, only Nexus 7 Toolkit shows device is connected. adb mode not responding. i've just tried N7 Toolkit
---------- Post added at 10:54 PM ---------- Previous post was at 10:45 PM ----------
efxbug said:
Can you reach the boot menu by pressing the volume down key while powering on?
Otherwise, try to check if fastboot is able to see your device and flash some new boot and system image
Click to expand...
Click to collapse
Thank you for asking. able to enter boot menu and fastboot menu. but cant flash anything, i'll tried new boot new system img's. Nothing. When connecting to PC fastboot showing Fastboot USB mode is enabled. unable to do nothing via adb mode. adb mode say error device not found.
Thanks for answer
Are drivers installed? And have you installed adb and fastboot correctly?
tommert38 said:
Are drivers installed? And have you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes, installed correct. it show up in the Device Manager list.
Anyway, i go to try this driver. Thanks. Let me know u
hmm. unlucky. Still nothing. Windows take a signal when connecting phone shows on fastboot menu => fastboot usb and adb mode say error device not found:crying:
i scanned my drivers using driver genius v11, i saw android driver named Samsung_Android_4.0_usbdrivers. now i think its something wrong with my boot.img?
When you see fastboot usb, and you type fastboot devices in a terminal, what does it say? ADB only works in recovery or when your ROM is booted, so just focus on fastboot.
it say when N1 is fastboot usb mode "error device not found". thanks for advance. tomorrow i'll be ask more.
Sent from my YP-G70 using xda app-developers app
Hey guys. Finally my N1 detected in adb mode. Im used Nexus 7 toolkit, downloaded N1 official Rom (i used only boot.img from zip file)
1st ive installed toolkit, then flashed boot.img (from official rom) to /system/ folder. Finally Windows device manager say detected new device and downloading drivers.
Started cmd.exe typed adb shell => adb mode showed HT9**********. Now problem is wont boot. What i do now? :silly:
i hope u can enter fastboot usb mode. if so try flashing any recovery.img
Sent from my Nexus One using Tapatalk

[Q] KFHD7 boot stuck at logo

Hi all,
I have a Kindle Fire HD 7" which I rooted following directions here which went fine and I've been using the rooted kindle for a few weeks. Today when I turn my KFHD on it just sits at the logo screen (no animation or anything) and refuses to boot.
I've tried hard resetting it (holding power button for 30 seconds) which did not help. I found this thread which seems similar to my problem. I was able to add a new vendor ID to the drivers and get the KFHD to show up in device manager when plugged in. However, if I try to use the fastboot command to force it to reboot it sits at "< waiting for device >".
If I do an "adb devices" the KFHD shows up there but I'm unable to do "adb shell". For most adb commands I try it simply sits at < waiting for device >". I'm hoping this means that it's at worst only soft bricked. Interestingly "adb reboot" does work but it goes back to sitting at the logo after rebooting. Does anyone have any suggestions about what to try next?
Does anyone know if the KFHD has a recovery mode I can boot into? I read a few threads that say you can access a recovery/safe mode if you hold down the up-volume button when you power on (and another that says both up and down volume buttons) but I've had no luck with that. It doesn't seem to change anything.
A little more background:
What led to my problem was that I decided to experiment with BotBrew since I'm interested in trying to compile some Linux code to run on Android. The app installed fine and I was using my KFHD normally when all of a sudden I started to repeatedly get a force close messages on some apps (I remember correctly I believe it was the keyboard). Since the message kept popping up I shut down the KFHD and when I attempted to turn it on next this began.
UPDATE: I was able to get it to run "adb reboot recovery" which loaded what I'm assuming was the Kindle recovery. There was an option for "Factory Restore" which I did. I got a kindle fire status bar (presumably for the factory restore). After the "restore" finished it rebooted and was again stuck at the Kindle Logo. Now however the device is not showing up in device manager and nothing happens when I plug it in via USB.
Odd do you have a fast boot cable, or are you attempting to enter adb commands another way?
Sent from my GT-P3110 using xda app-developers app
mrkhigh said:
Odd do you have a fast boot cable, or are you attempting to enter adb commands another way?
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
I do not have a fast boot cable (I just ordered one from SkOrPn since I figured I should have one on hand). I am using the the standard cable that came with the KFHD.
I was able to get it to run "adb reboot recovery" which loaded what I'm assuming was the Kindle recovery. There was an option for "Factory Restore" which I did. I got a kindle fire status bar (presumably for the factory restore). After the "restore" finished it rebooted and was again stuck at the Kindle Logo. Now however the device is not showing up in device manager and nothing happens when I plug it in via USB.
So what's the next step? Do I need to wait for the factory cable?
Try "adb reboot bootloader"
soupmagnet said:
Try "adb reboot bootloader"
Click to expand...
Click to collapse
Unfortunately after running "adb reboot recovery" and trying the "Factory Restore" the device no longer shows up in device manager when plugged in via usb.
I'm guessing adb is no longer on by default,
Fast boot via cable may be the only way now...just a guess tho
Sent from my GT-P3110 using xda app-developers app
When you rooted were you on version 7.2.3?
This is a Kinology HD using XDA Premium
Krsmqn said:
When you rooted were you on version 7.2.3?
This is a Kinology HD using XDA Premium
Click to expand...
Click to collapse
Yes, I was. Is that particularly important?
OK thanks, I ordered one from ScOrPn and I'll try that. If I can't wait I may make one on my own.
Sent from my HTC Desire CDMA using xda app-developers app

[Help] Bootloop, no adb no fastboot

I just tried to flash 2nd booltloader and tarp recovery on my 7". I went to reboot into recovery one got a Bootloop. It flashes kindlefire for 5 seconds and then goes black for 5 seconds and on and on for about a minute and then shuts down. When I try fastboot my computers hang at and adb says no device. I searched the forum and googled and found nothing so I'm sorry if I missed the answer somewhere. I do have the drivers installed on my computer. I appreciate any help or advice
Sent from my LG-E970 using xda app-developers app
popshovit said:
I just tried to flash 2nd booltloader and tarp recovery on my 7". I went to reboot into recovery one got a Bootloop. It flashes kindlefire for 5 seconds and then goes black for 5 seconds and on and on for about a minute and then shuts down. When I try fastboot my computers hang at and adb says no device. I searched the forum and googled and found nothing so I'm sorry if I missed the answer somewhere. I do have the drivers installed on my computer. I appreciate any help or advice
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Im haveing the same problem
Yeah I tried everything I know of so hopefully someone has a trick. I'm thinking about sending it for warranty but if they see it was rooted then I might be sol.
Sent from my LG-E970 using xda app-developers app
You say you got in in fast boot or that you were trying to from adb? Because if your trying to get it in fast boot your going to need a factory cable. From there once its in fast boot you plug it back in to your PC with the normal cable and run fastboot.exe -i 0x1949 getvar product
That should return Tate something. If that happens you should be able to fix it.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
I can't even get it in fastboot. I have the cable that it came with. maybe I'm nit doing something right. How should I do it with the factory cable. So far I've tried adb = device not found and fastboot = waiting for device
Sent from my LG-E970 using xda app-developers app
popshovit said:
I can't even get it in fastboot. I have the cable that it came with. maybe I'm nit doing something right. How should I do it with the factory cable. So far I've tried adb = device not found and fastboot = waiting for device
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
A factory cable puts kfhd7 in fast boot automatically, not the cable that comes with device,search eBay for Motorola factory cable around 4 euros
Thank you. I'll give this a try
Sent from my LG-E970 using xda app-developers app
fixed
So i ordered the factory which put it right into fastboot. downloaded kfhdsrt, restored system,boot,recovery and it booted up and is running great. thanks for the help. it as fixed within a half hour from when i got the factory cable in the mail :good:

Bonehead Move

I have a unlocked X, was trying to install a new rom via recovery and something went wrong...but I forgot to do backup so now its on a boot loop and I didnt have USB debugging enabled. Is there anyway to load new another rom to the phone so that I can install via recovery since I dont have usb enabled?
Yes power the device off by holding the power button and volume down, after the display is off let go of the power button. You can flash recovery or boot to recovery from there
Sent from my Nexus 6 using Tapatalk
Durteedee said:
Yes power the device off by holding the power button and volume down, after the display is off let go of the power button. You can flash recovery or boot to recovery from there
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I can boot into recovery but how do I transfer the new rom to the phone so I can install via recovery? I dont know how to move it from my PC to the phone.
You should look up side loading via adb and most newer recoveries allow you drag and drop once it's booted, you are using a custom recovery for your phone correct?
Sent from my Nexus 6 using Tapatalk
Durteedee said:
You should look up side loading via adb and most newer recoveries allow you drag and drop once it's booted, you are using a custom recovery for your phone correct?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
yes team win recovery v2.6.3.1
In advance you will find sideload via adb, I am sure you have fastboot/adb commands on your PC as well an understanding of how sideloading works
Sent from my Nexus 6 using Tapatalk
when I go into terminal, type abd devices, I dont see any attached...dont I need usb debugging on to be able to see device?
mario24601 said:
when I go into terminal, type abd devices, I dont see any attached...dont I need usb debugging on to be able to see device?
Click to expand...
Click to collapse
dont use adb use fastboot.
"fastboot devices"
wildblade64 said:
dont use adb use fastboot.
"fastboot devices"
Click to expand...
Click to collapse
thanks but its still not connecting....not sure what im doing wrong.
Also trying a otg cable but phone is not recognizing it. Any suggestions? Thanks
Sent from my ONE E1005 using Tapatalk
Since I didn't have USB debugging on when it went into boot loop, am I screwed or how can I move a new rom over? I do have win recovery I am able to boot to recovery but can't figure out how to load new rom. Any help would be appreciated. Thanks
Sent from my ONE E1005 using Tapatalk
Might have to start from scratch....flash the latest 5.1 firmware again....and bootloader if you haven't done so yet.
[quote name="DJ_Tomato" post=65476125]Hello
I am receiving phone calls, and when i answer they can't hear me and i can't hear them
So buggy, can't work with it, i have lost important calls, please help me[/QUOTE]
Had the same issue, fixed it by updating the bootloader.
I followed option 5 on this link.
http://forum.xda-developers.com/showpost.php?p=61142892&postcount=2
You will need to find the correct files for your phone varient from here.
http://forum.xda-developers.com/moto-x/development/xt1053-retail-stock-lollipop-flashable-t3155843
NOTE:-
Sent from my ghost using Tapatalk
---------- Post added at 11:58 PM ---------- Previous post was at 11:54 PM ----------
First link, option 5. Had a similar problem where I can go to recovery but my internal was deleted...I had nothing. Nor did I have a system.....I couldn't restore a backup nor flash a new ROM. I had nothing but recovery....so I googled the 5.1 firmware update and modem....and followed option 5 with mfastboot. Phone is up and running fine.
Sent from my ghost using Tapatalk
mario24601 said:
Since I didn't have USB debugging on when it went into boot loop, am I screwed or how can I move a new rom over? I do have win recovery I am able to boot to recovery but can't figure out how to load new rom. Any help would be appreciated. Thanks
Sent from my ONE E1005 using Tapatalk
Click to expand...
Click to collapse
Anyone have any recommendations? thanks
Finally got it working, took ALOT of trial and error! If anyone has same issue I can give step by step...not that Im good at this stuff but I can share what I learned

Categories

Resources