hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
anyone knows?
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
Yes, you can access ADB while in a bootloop.
Theonew said:
Yes, you can access ADB while in a bootloop.
Click to expand...
Click to collapse
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
runingwild said:
so you mean i can access ADB even though im not rooted and im s-on? that would be good news for me.
and how should i do it? when i type in the command adb shell, it says Error: device not found, while the phone was in the boot menu.
thanks
Click to expand...
Click to collapse
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
yes you can I have this before and it's working
runingwild said:
hi all,
my phone is stuck in a bootloop. and its Not rooted. all i can do is go to the boot menu. I want to use ADB to see if i can read the phone data (like sms...). Is there any chance that the device will be recognized when i connect it to the PC by usb with ADB?? or is it impossible? maybe ADB needs the phone to be operating normally to be recognized.
and what if i use the Fastboot program? same thing?
thanks
Click to expand...
Click to collapse
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again
Click to expand...
Click to collapse
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
mustafah822000 said:
yes you can I have this before and it's working
Click to expand...
Click to collapse
that can be helpful for me. How did you do it?? was it in bootloop too? not rooted?
Theonew said:
ADB does not require a rooted device, neither does it require S-OFF. So yes, you can. Type:
Code:
adb devices
to see if your device is recognized. If not, you'll need to install the drivers for it (or assoiciate adb drivers with it).
Click to expand...
Click to collapse
kuisma said:
No, you can not use ADB if the phone is stuck in a boot loop.
ADB requires a server process at the device side. If the device crashes during boot (i.e. a boot loop), this process is at best only started just before shut down again, or even more likely, not even started in first place. Hence ADB isn't usable unless the device is up and running. ADB does not require a rooted device, but gives you more privileges with root (accessing the phone as the user "root" instead of user "shell").
Fastboot on the other hand, is something completely else. To use fastboot you don't need to start the Android system as above, but instead enter the phone's bootloader. This is done via some key-combination specific to you device type (e.g. vol-up + power on). You are very likely able to enter fastboot mode even if the phone are stuck in a boot loop trying to start Android.
Click to expand...
Click to collapse
Theonew said:
In the time the process runs, you will have access to ADB. You just need correct timing (managed to root one of my devices this way).
Click to expand...
Click to collapse
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
runingwild said:
when i connect the phone by usb to ADB, its not being recognized. I type in adb devices and no devices show up. Maybe its because there is no way to connect to Adb in my situation (not rooted, S-on, stuck in a bootloop, and did not switch on the usb debugging in the phone settings). Or maybe its because of the driver.
I have a file which is the driver i need. but i double click on it to install it and it wont do anything. i dont know what to do with it. any ideas? i want to give it a try and see if ADB works with this driver.
Click to expand...
Click to collapse
Its a driver issue. Check device manager for your "unknown device," then associate adb drivers with it.
you can use adb once the kernel has loaded so root or any other factor shouldn't affect it
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
if u are bale to get into fastboot flash a stock ruu and it should work fine
well, what if i cannot access recovery mode or fastboot menu as you have said so. my HTC desire 310 is having bootloop and cant enter recovery. HELP PLEASE!!
Related
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Tommyboy77 said:
Hello I am going in circles trying to get my phone back up and running. It can only load into twrp or recovery and i have a custom rom i am trying to flash because accidentally erased the whole phone alongside the operating system. Now no matter what i do i try to run adb devices in the command prompt and shows device not found....unsure what to do at this point fasboot devices clearly shows it...any ideaS?
Click to expand...
Click to collapse
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
es0tericcha0s said:
If you can do "fastboot devices" then that means you are either in bootloader or fastboot mode. If that is the case, then "adb devices" would not find your device because it's not in the correct mode to be able to do so. You can access your phone with adb when it's either booted or most recoveries, but fastboot/bootloader mode is only for fastboot commands. Without knowing what phone you have and what update it is / was on, I can't really provide any more direct help. But typically there is a way to reload the OS via fastboot on most devices such as HTCs, Motorolas, and Nexus devices, to name a few.
Click to expand...
Click to collapse
adb devces does not work in clockwork mod either.....what is the easiest way to get this custom rom sent to my internal sd card if the phone wont boot up and os is wiped off the phone? it is an htc one...
adb should work in CWM... You might have to manually load the driver. Even if every driver works when the phone is booted and all, Windows can still have issues finding the right one in recovery. Check in your device manager. If that doesn't work, then you'll have to see if your recovery supports USB OTG and see if you can load like that. If none of that works, you'll have to reload the OS via RUU and start over with root/recovery/etc.
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
C13v3r0n3 said:
Mount USB and copy it from your PC to the phone or do sideload.
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Neither of those things are options for the OP. He can't boot, so he can't mount USB (mounting USB in recovery hasn't worked for most phones since JB where most phones don't support USB mount - only MTP) and he can't sideload because he hasn't been able to get ADB working.
His options now are:
Find out why the adb driver isn't loading so he can just adb commands to push the file or sideload
USB OTG
Return to stock via RUU
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Bump, need help ASAP
Alex311360 said:
So recently, I downgraded to 13.3.1.0, and installed Safestrap (not the one for later versions). However, after restarting and adding a ROM slot, it wouldn't let me do anything with stock.
I restored stock, but still nothing.
The odd thing is, whenever I press the power button, it will still make noise.
I can access fastboot, Safestrap, and the default recovery.
What do I do?
Click to expand...
Click to collapse
If you can enter safestrap recovery, check if you can establish adb access:
so enter safestrap and connect kindle to your pc or laptop. Then start cmd window or terminal if you using linux, and try:
adb devices
it should return:
list of devices attached
xxxxxxxxx recovery
if you can achieve that your kindle in safestrap recovery is recognized by win/linux, you can try this:
1. Download this 13.3.1.0 (Kindle HDX 7") update - pure amazon FireOS so OTA updates enabled - do not connect to wifi/register your kindle if you want root and use of custom recovery after flashing this
A. Now, since I am not expert for adb installing pushing repairing etc., read this thread [HOWTO] Unbrick your device
B. If that for whatever reason wont work, you can try sideload update-kindle-13.3.1.0_user_310079820.bin (rename .bin to .zip before sideloading) through safestrap recovery, but because Safestrap is only TWRP "based", I cant guarantee that this will work either (it should, but this is one way ticket, your working safestrap recovery will be destroyed in the process of update and if things dont go as they should, your kindle is bricked for good):
0. connect kindle to pc/laptop
1. enter Safestrap, tap Advanced -> ADB Sideload -> Swipe slider to start Sideload
2. on pc/laptop open cmd/terminal, type adb devices, you should see:
List of devices attached
XXXXXXXXXXXXXXXX sideload
3. type adb sideload update-kindle-13.3.1.0_user_310079820.zip
4. You will see a progress bar in the command prompt indicating that the Zip file is being copied to the device. Once the file is transferred, the Zip is automatically installed on your device.
OK fingers crossed, I hope something will work, but things can go wrong, so it is up to you if you try this or not ...
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Alex311360 said:
On a scale of 1 to worse, what happens if ADB sideload refuses to work? It just freezes at starting and does nothing afterwards, and I have to cancel.
Click to expand...
Click to collapse
You can also try to unlock your bootloader (since you have compatible FW) and proceed to flash cuber signed recovery (TWRP 2.8.5.0) through fastboot and then from TWRP you can do necessary steps to recover your kindle quite easily - if you are familiar with TWRP flashing...
Regarding sideloading I honestly dont know how it will react - never try it - it was developed exactly for quick system recovery, but you must be flashing 100% working rom ...
Personaly I would go for bootloader unlock and then flash TWRP 2.8.5.0 from which sideloading feature (If you want use that) must working... :good:
Do you require a factory fastboot cable for that?
Alex311360 said:
Do you require a factory fastboot cable for that?
Click to expand...
Click to collapse
No, standart USB cable is enough.
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Alex311360 said:
Can you give me a link on how to do this? I know I'm sounding very noobish, but I'm a tad new to this.
Click to expand...
Click to collapse
Sure, here is original post from dpeddi.
... and here is how to for windows ... :good:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Alex311360 said:
Hey, sorry it's taken me so long to reply. Was busy with school.
For some reason it won't connect to the device in fastboot, it just says "waiting for device", even the Kindle says "Ready." and does nothing.
What do I do?
Click to expand...
Click to collapse
If your OS is Windows 7, you can try install these drivers and then try again.
jeryll said:
If your OS is Windows 7, you can try install these drivers and then try again.
Click to expand...
Click to collapse
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Alex311360 said:
Still no dice. Doing fastboot devices or adb devices brings up nothing.
Please note I have done the following things:
- did a kindle fire system restore with safestrap restore still installed
- adb sideload doesn't work in safestrap
- fastboot drivers used installed does nothing
Still stuck.
Click to expand...
Click to collapse
On which FW you were before downgrading to 13.3.1.0?
Weird thing with windows and these drivers is it sometimes command fastboot -i 0x1949 devices does nothing, while actually direct commands like
fastboot -i 0x1949 getvar product
fastboot -i 0x1949 getvar version
fastboot -i 0x1949 getvar kernel
works as expected...
Anyway to restore system on your kindle you need working connection between kindle and PC/laptop, so you can use adb commands to restore your system, or after bootloader unlock, you can use fastboot commands to flash required/missing components. I have tested while in safestrap kindle is recognizable by adb devices, if you can achieve that, you can continue with how to unbrick thread I posted before.
You can also learn how to install/use Linux, where adb and fastboot device recognition/commands works 100%...
I must leave for work now ...
So, some kind of miracle happened, and I found the source of the problem.
Upon trying to update to 13.3.2.4, it reboots the phone instead of installing it. I try booting into Safestrap, and it does Open Recovery Script, causing it to boot to a black screen upon booting to the actual thing.
I don't know how to fix Open Recovery Script doing that, but all I had to do to get it back to normal was reflash the 13.3.1.0 amazon OS onto stock.
Enabling USB Debugging through ADB? Im Stuck at Black Screen W/ "Unauthorized" in ADB
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Mcfinnipoop said:
So I've had a few problems lately, all leading up to my Kindle being Bricked at Black screen after Recovery reboot attempt.
Using ADB, My Device is showing up, however I am getting "Unauthorized" and cannot access any root functions, or push commands to the Kindle.
I'm trying to do a Reset/Brick Fix by flashing the OTA update and start from scratch(Stock), but have no way of doing so via ADB because I can't push anything to my once rooted device, now saying it's UnAuthorized.
Is there an ADB command to either Root this thing, or even just to enable debugging mode via usb without actually going into the system? My System appears to be missing, or not running for whatever reason.
Is there ANYTHING I can do to get this thing up and running again? ADB Is Recognizing the device, but "ADB Shell" is giving me the same Unauthorized error.
Click to expand...
Click to collapse
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
macstibs said:
Same problem - can't boot into the os so can't enable USB debugging to get to adb access.
adb devices returns the SN with "unauthorized"
Click to expand...
Click to collapse
No recovery if bootloader remains locked.
Davey126 said:
No recovery if bootloader remains locked.
Click to expand...
Click to collapse
Still a pretty nice tablet - sucks that there's seemingly no fix to this (especially after I paid $100 for a new lcd)...
I unlocked the bootloader and went to root. on the first reboot after rooting it's stuck on the boot animation. When i plug the device into my PC and use the cmd prompt "adb devices" it won't see it. I help the power button and vol down to get to fastboot and my pc still won't see it. i've tried to factory reset though fast boot, says erasing, then reboots and still stuck. I updated everything in adb and still nothing. Everything went fine with unlocking the bootloader, but rooting it totally messed something up.
I can't seem to figure out how to get my PC to see this thing again. It's kind of a crap tablet to begin with, and now i brick it? totally frustrated.
Thanks
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Sent from my Nexus 9 using Tapatalk
Adb can do almost nothing when your device is in fastboot mode. Use fastboot to see if your device is connected to your computer if you didn't do so.
try "fastboot devices".
corkiejp said:
try "fastboot devices".
Click to expand...
Click to collapse
I just got "waiting for any device". I have the path set up to "C:\android-sdk\tools;C:\android-sdk\platform-tools". I haven't changed anything since i unlocked the bootloader so i'm just confused.
kacang87 said:
when you connect to pc,did you hear pop up connect sound..if yes then you connect to your pc..download google factory image,flash system.img,boot.img and all other .img image..hopefully you can restore tab back to nermal..good this is your tablet already unlocked bootloader.
Click to expand...
Click to collapse
The safely removed hardware icon does show up in the task bar. When i got to printers and devices there is an "android".
https://www.dropbox.com/s/a5chez6r9cuxjzo/Capture.JPG?dl=0
Can i use that port to force adb to see it? Not sure if this helps
gotta run to work, i'll mess with it this afternoon. Thanks guys.
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
corkiejp said:
First make sure your in "fastboot" mode and not in the bootloader.
Your device should show up as under Android Device as "Android Bootloader Interface" in device manager on your PC.
If not there then your drivers are not configured correctly, Nexus Root Toolkit has a guide on how to setup drivers correctly.
Click to expand...
Click to collapse
I tried uninstalling the drivers from device manager and that didn't seem to do it. I went into the sdk and deleted them from the sdk then reinstalled them through the sdk and that seemed to work. I feel like i should have thought of that! duh. flashing CM13 now! hope i can get this to work haha jeeze.
thanks for the help guys
Hello,
I have specific problem.
I was on the stock rom 10.3.6... with root and twrp installed. So I wanted to update to Miui 11 and I uninstall Magisk and done the update through the twrp.
So, in order to back magisk I wanna to go to twrp via fastboot and PC. But I am constantly getting message "ADB devices unauthorized". Anyway... this is only happening when phone is shutted off(in order to go to fastboot mode). When phone is turned on everything is fine and I can se device via adb command prompt. I tried any written solution on internet but nothing could solve the problem. When I connect turned on phone I regularly get the question to authorize phone and I click ok. And while phone is turned on everything is fine and I have accsess to internal and external memory of phone.
Is there any possible solution to solve this stuck ? Is there some other way to boot into twrp besides fastboot ? For now I would skip installing magisk via stock recovery or without twrp access.
Thanks infront !
This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.
EugenStanis said:
This is how its susposed to work. Device should be online when turned on, and not when off. This is first time i heard someone try to connect device wiht adb via fastboot.
Click to expand...
Click to collapse
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?
visinacgile said:
Thank you for reply.
I think that the reguar way for boot into twrp via pc is that your phone is turned off. Than you connect with pc and start adb commands. I dont understand, really.
Ok, how can I boot into twrp without pc if dfe is not flashed ?
Click to expand...
Click to collapse
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter
EugenStanis said:
You use fastboot instead of adb commands when phone is off. Put your phone in fastboot mode and type commands like fastboot boot (drop your twrp image here) and hit enter
Click to expand...
Click to collapse
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?
visinacgile said:
Yes. My mistake... huge. Thank you. I forget tottaly.
Should I delete this thread ?
Click to expand...
Click to collapse
No problem. Leave it like it is for other users :highfive: