[Solved] ADB without Debug Mode ON - Nexus 5 Q&A, Help & Troubleshooting

EDIT: see my 2nd post
Guys, I recently flashed a ROM and i got a black screen of death (i can only press the power button, and then tap on Power Off).
I tried to flash a stock ROM, still black screen. So I decided to use the factory image from Google but I cannot see my device with ADB since the Debug Mode is OFF.
I have access to TWRP recovery.
How can I bring it back to life?
Thank you!

Alexéin said:
Guys, I recently flashed a ROM and i got a black screen of death (i can only press the power button, and then tap on Power Off).
I tried to flash a stock ROM, still black screen. So I decided to use the factory image from Google but I cannot see my device with ADB since the Debug Mode is OFF.
I have access to TWRP recovery.
How can I bring it back to life?
Thank you!
Click to expand...
Click to collapse
The first problem is that you try to use adb to flash stock rom and not fastboot
The second problem is that because of the first problem you dont know what is fastboot and how to use it and when.
The third problem is that you dont know the "enable usb debugging" is for just enabling the adb commands for the android OS. It has nothing to do with if you are in recovery.
The solutions:
No 1: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
No 2: http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833

Lol, i do know what is fastboot, how to use it and when. I am using android sdk since those programs weren't even in the platform-tools folder.
I wrote the post in a hurry. You probably didn't understand what I really wanted to say.
You have to have debug mode enabled in your device to use adb or fastboot or whatever. I hadn't. Couldn't go further a black screen.
I was installing (with wipes as usual) many Roms getting the same black screen after boot (only power button working).
Then I noticed a time that I had a reboot and the system was reinstalling a 2nd time.
To fix the problem I used the tool inside TWRP to fix the partitions on the file system (repair).
After that everything works.
Cheers.

Related

[HELP] Nexus S can't boot recovery

Hi all,
Been given a Nexus S i9023 by my brother who has been "tampering" with it and now it seems a bit messed up.
When booting up - it gets stuck on the "Google" screen with a padlock on it... I can get into fastboot and I can flash recovery but when I attempt to load any recovery - I get that same Google screen with the padlock! I've downloaded a stock rom and even flashed system etc via fastboot but that still gets me nowhere past the damn padlock!!
I've tried to "fastboot boot recovery.img" and I still get the Google screen with the padlock but it says "Fastboot status - OK" on the bottom left.
I've searched and searched but everyone just seems to give tips on how to flash recovery. I know how to flash recovery; it just seem to be going into it though! Could the internal memory be screwed?
Thanks for any advice!
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
albundy2010 said:
Sounds strange for sure. You try from within the OS? Enable USB debugging and adb reboot recovery.
Doubt it will work but its worth a shot
Click to expand...
Click to collapse
The phone stops at Google with the padlock on boot! Can't even get into the OS. Going to try to unbrick it and Odin but left my ubuntu laptop at my parents and can't be bothered to go get it... couldn't get it to work booting off cd rom. Kept giving me the "SBL Injection Failure Failed to find device" error booting ubuntu on a CD!
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
albundy2010 said:
You may have a storage issue.
I seen you tried to flash system and boot recovery with fastboot ( which should have booted) but did you try to flash them all and wipe. The command is fastboot -w update file name.
I think Odin is a windows only tool anyways by the way.
Click to expand...
Click to collapse
No idea why I said Odin - I meant the unbrickable recovery thing.
I tried Odin with a Jig last night; got it into download mode and flashed with odin. Got the same result.
fastboot -w also gives the same issue...
If I have a storage issue - is there any way I can tell?
Basically you can tell by the issues you're having. Doing all the proper stuff to flash images etc and still having a booting/working device.
As far as a actual diagnostic tool I don't know of one. But it sure sounds like a hw issue to me.
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Pironi90 said:
I have the following problem: since a few weeks I'm unable to enter recovery.
This is what I do:
- shut down my phone
- press the power button while holding the volume up
- than I get a screen where I can choose from 4 options using the volume controls and selecting an option with the power button
- I select 'Recovery' and press the power button
- I get the usual black screen with Google logo and padlock
- but instead of getting into my recovery, I get a black screen with a Droid lying down, the 'chest' opened and some kind of small warning triangle above it..somebody who knows what I have to do??
Thanks in advance
Click to expand...
Click to collapse
Reflash your recovery using fastboot.
polobunny said:
Reflash your recovery using fastboot.
Click to expand...
Click to collapse
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Pironi90 said:
And where can I find how to do this? I'm a total newbie for this kind of stuff and I found some hits on google (e.g. http://forum.xda-developers.com/showthread.php?t=1757146) but I'm actually a bit scared to damage my phone or something by doind something wrong or applying some method that's actually made for another device or so.. :s
Click to expand...
Click to collapse
Flash custom recovery.img part
http://wiki.cyanogenmod.org/wiki/fastboot#Flash_Custom_Recovery.img
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
polobunny said:
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
I think so yes, I could access recovery before if that's what you mean by unlocked
Pironi90 said:
I think so yes, I could access recovery before if that's what you mean by unlocked
Click to expand...
Click to collapse
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
You are entering recovery. Stock recovery
If you want a custom one either flash with fastboot or if you're rooted with a app. Goo manager. Rom manager etc.
Keep it mind that if you're on a stock ROM the custom recovery gets overwritten back to stock when the phone boots up the os
Q
UselessSniper001 said:
When u boot on the Google screen on the bottom centre does it have a padlock? If so then it is unlocked.
Click to expand...
Click to collapse
Then my phone is unlocked yes
polobunny said:
You need ADB (and ADB drivers installed, strongly recommend PDANet Android Drivers) and fastboot executable.
Custom recovery I suggest you use Clockworkmod Recovery.
I imagine your phone is already unlocked?
Click to expand...
Click to collapse
In installed the drivers and I installed the fastboot executable, but what do I have to do next? If I run the fastboot.exe, it just quickly shows a CMD-window and then disappears.
Edit:
I just discovered that, when I'm at the bootloader (I think it's called that way, the screen where you can select recovery), and I choose to reboot, I get the same 'error' as when I try to enter recovery.
Edit:
Alright, I was able to flash a new recovery, using cmd, but now when I try to enter my recovery, the phone gets stuck at a black screen with Google logo and padlock...
I have same problem as wolverine_2k who made the post. My nexus, can't start, I tried reboot and recovery but didn't work. After reboot or recovery I see Google logo, than Nexus screen and that is it. It didn't move to home screen and it stay with lighting screen all the time till I remove the battery. I can't power off it and don't know what to do. I can't transfer data with my PC (it don't recognize the device - only notice that "unknown device" is connected). Please any ideas?
P.S.: My English is not good, if someone answer do it simple please
Thanks!

[Q] Nexus 5 Recovery broken and OS is missing

Hello Everyone. Normally I´m the quiet Reader and not the Active Poster but I need your help guys.
I have a problem since yesterday and I tried to fix it by myself with searching everywhere but couldn´t do it by myself.
What I had before:
Optipop 5.0.2 with Racer Kernel (both had Builds from January) + TWRP 2.8.1
What I wanted to do:
Flash Grogg's AOSP 5.1 and newest Code Blue Kernel
What happenend:
I factory resetted and successfully flashed Grogg's AOSP 5.1 and Code Blue Kernel but had Problems with FCing Clock and Dialer so I tried to reflash both after wiping completely (even internal storage), mounted it and put the needed new files on the internal storage.
I reflashed the Custom Rom + Custom Kernel and the newest Radio, wiped Cache/Dalvik and rebooted. It booted and the notification screen with 'optimizing apps' appeared. After that that screen went black and nothing else.
It was lit so I´knew that the device wasn´t shut down and tried to rebbot sincee nothing happened. I noticed that it was possible to reboot or shut down the device normally so there might have been a Problem with the Rom.
I retried the whole procedure and this time the notification screen didn´t show up after the boot logo and went directly to the black blank screen but i still had the possibility to rebbot/shut down the device normally. This time I didn´t wipe the whole storage and this time it got stuck at the boot logo and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
My Problem is that I can´t connect my device to the computer, find it with 'adb devices' and reflash the Recovery with fastboot. The device is shown as 'android' in device manager in Windows 7 and nothing else. I already tried to un- and reinstall the Google drivers and that whole stuff but it doesn´t work for God's sake. adb doesn´t list my device and the 'list of devices attached' is blank although my device is connected.
I know my phone is soft bricked and that it is possible to fix that although I don´t know why it even broke the OS and Custom Recovery.
Can anyone help me out with a step-for-step-guide to fix the adb Problem and explain me why that blank screen even happenend?
Edit: If I´m in fastboot mode the device is shown as >Android Bootloader Interface< and isn´t listed with 'adb devices'. If it is powered off it is shown as >Android Composite ADB Interface< but is listed with 'adb devices' but I can´t flash the Custom Recovery.
Beyazid said:
My Problem is that I can´t connect my device to the adb to reflash the Recovery.
Click to expand...
Click to collapse
You don't use adb to flash a custom recovery. You use fastboot. That's your first problem.
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Beyazid said:
I actually meant that it isn´t shown with the command 'adb devices' I will change that in the text
Edit: I also noticed that the fastboot mode is always on in the bootloader although the device isn´t connected to the pc. Shouldn´t it only be active if it´s connected?
Click to expand...
Click to collapse
I see a couple problems here.
First one is use the newest version of TWRP. You can get that from my signature.
Second is Code_Blue may not be compatible with the ROM you are testing.
You don't need ADB at all for this, you need fastboot.
As I said. I just use adb to make sure that my device is found by and connected to the pc. I know that fastboot is used to flash everything but my Nexus 5 isn´t even shown. So how can I get my phone connected to flash the custom recovery?
And it seems like it is compatible since it worked the after the first installation and boot
FFS, XDA. I had just written a huge ass post on how to use fastboot properly, with the proper commands and ****, and you logged me out, making me lose all that. F U.
Beyazid said:
and the Custom Recovery seems to be broken, too. The screen shows the dead Android with the red triangle.
Click to expand...
Click to collapse
This is the stock recovery.
You need to put your device in fastboot mode, REFLASH TWRP again with fastboot, then STRAIGHT FROM FASTBOOT select (with vol keys and Power) "Restart recovery". When you're in TWRP, wipe data/factory reset, reflash rom, gapps, REBOOT, PROFIT.
`fastboot devices` and `adb devices` are two commands to check if an active connection exists, between the host interface (on the PC, look at it as servers) and the device interface (look at it as clients). both commands will only return your device's SN IF drivers are correctly installed (speaking on a basic level, and about Windows). If you execute those commands, no SN comes up, then you need to fix drivers FIRST. Not even worth trying to do other commands.
`fastboot devices` only works here -> http://bazalabs.com/wp-content/uploads/2014/07/20140705_215603.jpg
`adb devices` works in TWRP/CWM (NOT in stock recovery) and in Android itself (needs USB Debugging active).
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Beyazid said:
Thanks for the help. I was able to flash the Custom Recovery and the Custom Rom with and without Code Blue Kernel but in both ways the phone loads, sets up at the boot logo and goes straight into the blank black screen which appears without the notification screen of the apps that get optimized.
I can manually turn off, reboot.or take a screenshot which clearly indicates that the Rom itself is installed.
How can I fix that problem?
Thanks in advance
Edit: Tried with the Blue Code Kernel which gave that blank screen and wiped everything but internal storage and reflashed just the Custom Rom which gave me the same result
Could it be because the system.img or boot.img are missing??
Click to expand...
Click to collapse
Try another ROM.
System.img .. boot.img.. comes with the ROM you flashed (well, not exactly, but both partitions do get written to), so no, they're not missing.
I gave it another try and fixed it.
I'll write it down so anybody who ever faces that problem can solve that, too.
Follow that guide (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701) step by step and after a few minutes of flashing and a few minutes of booting you should get a clean and fresh Android Version on your device. It removes all the old files and installs the newest files.
And thanks guys for helping me out with that adb/fastboot mistake. Kudos to you

Need help! Super soft Bricked stock phone. Tried many methods!

Hi all. So my stock opo somehow got bricked overnight while charging. It's completely stock and I have no idea why.
Status of my problem:
-Stuck on Android boot screen.
-Able to access fastboot.
-Can't access recovery mode
-No TRWP
-it's still locked
-Tried unlocking with fastboot oem unlock cmd / toolbox but it just reboots back to android stuck screen after its done but its still locked after checking with fastboot oem device-info cmd.
*USB debugging not enabled (cant enable it cuz i cant go in my phone duh)
-Cm11 33r I think...
-Installed android adb on device manager
But couldn't detect it on the list ("adb devices" cmd)
-Able to detect serial using fastboot device cmd tho.
-Tried universal adp, adb bootloader driver, Samsung adb driver, composite driver and it still won't detect it on list.
-Tried using another usb port.
-computer doesn't detect phone unless I go on fastboot or hold power+up volume for 10 sec (this shows QHUSB_BULK)
-Tried using msm9874downloadtool.exe with cm 11, doesn't do anything even tho it's completed and it's green.
-Tried using msm9874downloadtool.exe with color os but it doesnt work as well, in fact, it made my screen have multiple grey lines vertically across my screen and no fastboot display or android display.
-Tried just flashing Cm11 33r images but it won't work cuz I'm locked.
-Tried unlocking but goes back to my other problem of device not being on the list and not having usb debugging enabled.
Tldr;
Phone stuck on Android boot screen
USB debugging not enabled
Phone is not unlocked so I can't flash anything
Thanks for your time and effort. I really need help.
I still need help guys plzzz. Thankss
Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk
ackliph said:
Have you tried getting into download mode? I think you power it off. Connect to USB and hold vol down? Or vol down + power. Something like that. Once in DL mode, flash it. There's a tutorial somewhere.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
download mode? you mean fast boot? power + down doesnt load anything. Power + up goes into fastboot mode.
And i cant flash anything because you have to unlock the phone first. But mine is not unlocked. And i cant unlock it with fastboot oem unlock cmd because all it does it reboots my phone. Yes i checked if im unlocked after that with fastboot oem device-info.
First try to go to recovery by pressing volume down+ power button at the same time and then clear data and factory reset. This will wipe out ur data on phone but u can revive ur device by flashing stock rom using flashing tolls available... Check youtube videos for flashing tools.
Once you clear the data and factory reset from recovery mlde then ur device will be at the state where there is no OS in it n just a stock kernel. Give it a try and let me know
I can't get into recovery. Power + down only stays at android boot screen.
Have the exact same issue. Did you find a fix???
Even if your bootloader is not unlocked you can flash stock rom. Use oneplus one flashtool and flash cm11s. There are plenty of videos available on net for these problem, just go through them or try the hard bricked video to solve your problem. I hope it helps you. I lost my one device because of a silly mistake so i know the pain.
I've tried flashing stock rom. Cm11 33r. But it keeps telling me I'm locked.
put it on fastboot mode, download the stock rom from this:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Choose carefully between 16gb or 64
unzip the file and click on the flashall.bat or something like that , it's a script and it will flash everything
and you should be good
you will loose all your data, i don't know if you dont flash userdata and you remove it from the file and remove it's line from the script, maybe you wont loose your data, but try it
if you want i can help you through teamviewer

Stuck at fastboot. Need help

Hello everyone. I unlock bootloader without any problem. Gotback to normal phone interface to enable again USB debugging and advanced reboot. Then I reboot to fastboot again to install the TWRP recovery. I typed fastboot boot imagefilename.img without any errors and im here waiting like 1 hour in fastboot mode image to go into twrp recovery. Just to mention that I can turn off the phone and go back to normal interface fine if I long press + - and the power button. It seems like everything im doing is fine but im just waiting to actually go to recovery. Sorry for the English mistakes. Couldnt find anything to other threads similar to my problem. Thanks in advance
Edit: I checked if im using the right twrp file multiple times.

Pixel 4a stuck in fastboot mode

Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Maybe you can use this guide:
[GUIDE] UNLOCKING, DOWNGRADING TO A10, TWRP, ROOT
Hello, I'm posting this guide for those (like me) who can't do without TWRP on their device. I'm providing only a step-by-step explanation. Credits to @nikamura for his kernel and TWRP...
forum.xda-developers.com
And start on this line in "First Step" section:
Plug the phone into a usb port of your pc.
Then complete all the tasks in "Second Step" section to get your phone at least booting in android 10.
ifixibrick said:
Tried to follow this guide to root my pixel 4a and completed all steps up to 3.4. My phone is now stuck in fastboot mode and I can't get into recovery mode to do a factory reset. Not sure what to do, I'm a little lost. I accidentally used this or this image for Android 10 when I think I should have used this image for Android 11.
Any help would be very appreciated.
Click to expand...
Click to collapse
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Raj Pandiyan said:
Run the online flash tool from bootloader screen bro. Make sure you install adb and fastboot tools.
Click to expand...
Click to collapse
How do I do that? I seem to be stuck in fastboot mode.
ifixibrick said:
How do I do that? I seem to be stuck in fastboot mode.
Click to expand...
Click to collapse
Is it bricked? Cannot flash stock Android to remove ArcaneOS
I recently purchased a used Pixel 4a, and I now understand why the seller was offering such good price for it and why he refused to respond to me now I have it. This phone has ArcanseOS 10 installed, which has only 3 apps installed... Setting...
forum.xda-developers.com
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
jawz101 said:
reboot to recovery, press volume up + power to bring up the recovery settings, turn on sideloading
then adb sideload the factory image.
Click to expand...
Click to collapse
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
ifixibrick said:
Hello. Currently stuck in fastboot mode. Using the volume buttons to select recovery mode and pressing the power button to go into it doesn't take me to recovery mode. The screen briefly goes dark before entering fastboot again. I think the phone is trying to restart but not getting past fastboot mode.
Click to expand...
Click to collapse
Can you type fastboot reboot recovery and get into recovery mode? You'll see a little Android guy with a red thing if you're in there.
If that doesn't work- it almost sounds as though your recovery partition is deleted or something. You can reflash the recovery from fastboot.
Hey, I had the same problem. I've got it resolved now and wasn't able to find any help on how to resolve it, but this thread is as close as it came, so in the off chance that somebody else comes along, I thought I'd write up the steps I took.
Because it was in fastboot mode, I was able to easily restore my phone to factory settings by running flash factory image script I downloaded here.
My original image was sunfish-rq3a.210605.005-factory-be541467 which I followed the steps with but couldn't get it to work. I got to the Google logo with a status bar that just ran forever. But the flash-all.sh script worked to get the phone booting again.
So what I did to get Magisk to work was to use that same factory image site to download an older version. I used a version that was listed in a different root guide with the idea that maybe the version I tried before wasn't compatible with magisk, but presumably the one from the guide was. So I tried sunfish-rq1a.210105.002, ran the flash-all in fastboot, and confirmed that it booted--it did.
Next I redid 2.2 through 3 and it worked, and the boot completed with Magisk installed. Everything seems to be working fine now.

Categories

Resources