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:
Related
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
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
Whenever I type adb reboot oem-unlock, the device just reboots and goes into charging mode.Help?
Change PC connection type
Sent from my LG-P880 using xda app-developers app
NoobBrandon said:
Whenever I type adb reboot oem-unlock, the device just reboots and goes into charging mode.Help?
Click to expand...
Click to collapse
Maybe search for another tutorial, reinstall your drivers or do the other things that are suggested if you search for your problem.
Sent from my LG-P880
It's one of the "unlockable" models. Use the "unlock-relock" tool or the unlock script from the unlock guide.
Sent from my LG-P880 using Tapatalk 4
muellersmattes said:
It's one of the "unlockable" models. Use the "unlock-relock" tool or the unlock script from the unlock guide.
Sent from my LG-P880 using Tapatalk 4
Click to expand...
Click to collapse
If this helps,whenever I boot into recovery now,a red text saying LGE SECURITY ERROR: BOOT IMAGE or something like that
So you flashed a recovery before unlocking?
If your device doesn't boot at all, do a kdz reflash. If you can boot to the system, use one of the methods mentioned above; you only need root and USB debugging on to use it. If you don't have root but can't boot to recovery, try the "root many android" method from the index, that might do it. If it still fails, do a kdz reflash, then start again (root - unlock - recovery)
Sent from my LG-P880 using Tapatalk 4
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
I need some big help. I was having issue with my battery and phone powering off when not on a charger. I thought change the OS with Android N beta could help me with the issue.. When I was complete the fastboot commands .. I mistakenly use the lock bootloader command as well. So my devices is suck on the Google Logo.. Can someone help me with this issue?
Sent from my SM-N920V using Tapatalk
Well, try first doing a factory reset from the recovery mode.
If it doesn't help, just unlock it and flash everything again.
My bad.. I meant to add that its not let me unlock the bootloader.. Its asking me to select OEM unlock in the setting of my devices
Sent from my SM-N920V using Tapatalk
Does anyone know if you can send the software via adb from the recovery screen
Sent from my SM-N920V using Tapatalk
Try doing the factory reset through recovery, and if it doesn't work, take this steps and sideload the ota:
https://developer.android.com/preview/download-ota.html
Tried factory reset several time and that didn't work.. But I'm going to try this method when I get home
Sent from my SM-N920V using Tapatalk
TheGman125 said:
..... When I was complete the fastboot commands .. I mistakenly use the lock bootloader command as well. So my devices is suck on the Google Logo.. Can someone help me with this issue?
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3206928/
It's a link for Nexus 6p, but is about the use adb and fastboot; fits more devices
Maybe you'll find info to solve your problem.
TheGman125 said:
I need some big help. I was having issue with my battery and phone powering off when not on a charger. I thought change the OS with Android N beta could help me with the issue.. When I was complete the fastboot commands .. I mistakenly use the lock bootloader command as well. So my devices is suck on the Google Logo.. Can someone help me with this issue?
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
Google makes OTA update zips available that can be flashed even if OEM Unlock is disabled. Assuming you are still able to access the bootloader, download the latest Nexus 6 Android 6.0.1 OTA and copy it to internal storage. Enter recovery and flash. This will wipe your entire system, but your phone will be operational again.
From there, you need to go through the process of unlocking the bootloader, and then you can try installing the N preview again.