i have a linsay 7-xhd that got stuck after using the above command have no adb access from the boot screen and it will not boot into recovery. any ideas to get to recovery or fix? there is no roms firmware or anything available for this device?
I let the battery drain all the way (thankfully the battery isn't great and wasn't fully charged) and i was able to boot into the os. i still wish to access the bootloader any ideas why it would cause a boot loop?
This won't really help, but next time make sure the device is recognized first. That way you know the computer sees it. I start a terminal session with adb devices command first. If nothing comes up( if the phone's on, I get the serial number, if it's on twrp, I get the dev name as in the one in build prop) adb doesn't see it. I go from there, and do what I am trying to do, then use adb reboot bootloader to reboot. The good thing about using twrp is that internal storage shows up, plus sdcard access is shown on the computer, when adb is working right. I don't use windows though, seems that things work better with ubuntu.
Related
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!!
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 I have had my Droid DNA for a few months and I've been messing around with it and doing fine. Since I installed TWRP it allows me to delete internal storage...
Oops, there goes my ROM I had saved. Now I'm stuck in either bootloader or recovery. I can't get ADB to recognize my DNA to save my life. It's really really irritating.
I've tried flashing a zip with fastboot since fastboot can recognize my device but ADB can't and it didn't work.
I have Minimal ADB installed and HTC sync manager, but i installed sync after i messed it up so idk if it installed the drivers.
I need a step by step instruction guide to get this to work. I can't find it anywhere. I keep getting no ADB devices and it saying server out of date and what not. I've been searching for hours and hours.
I can't get this to work. I even bought a new phone in the meantime to get me by and that's not exactly what I wanted to do... Any help would be appreciated. Thank you very much!!
No one?
Pretty quite.. I recently had this happen as well.. No fear tho.. If you have twrp already installed your golden.. Download a rom 2 your computer and on twrp goto advanced and sideload.. Command prompt on your computer.. Easiest if found is running xp. Get to your folder of adb hit control and right click poem command prompt here.. adb devices, then adb sideload rom(name). zip.. Your computer will find your device then , and if it didn't send it will allow you to file Explorer.. Throw a rom on your internal reboot into twrp and flash
Æaa..\../
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
dyllysoilly said:
I am lucky I switched to TWRP before this happen, but alas, it's hanging at starting ADB Sideload, doesnt show up in devices either. How do I make it visible so i can just use file explorer from my PC to sideload it?
Click to expand...
Click to collapse
You can restrt the phone. Hold down power and volume down together. Then you can reaccess the bootloader from there. If you have twrp you can just go through the file manager instead of messing with sideload.
A few days ago, my Razr Maxx HD crashed and won't boot. It is locked, and not rooted. Initially, it wouldn't ever get past the red circle initial splash screen and would stay on that for hours. I was able to press the Power+VolUp+VolDown to get to the menu to Restore, Normal Boot, etc... I was able to get to the dead android guy one time and one time only thus far. I tried to take it into a store, but they did a very half-hearted attempt and trying to get it to work again. Since then, I have never been able to get as far as I did prior in trying to recover anything.
Now, it almost immediately just boots into fastboot with an error of Kernel Boot Failure.
My phone does/did have Developer Options enabled, and I was previously able to use it with Android Studio, and deploy apps to it, so I know the drivers are loaded on my computer fine, and I am using the same cable.
Ultimately and if possible, I am wanting to retrieve the data off the phone. From what I am seeing I THINK it is still possible.
When I connect the phone to my computer, and it is in fastboot, I can type this in the cmd prompt: "fastboot devices". It sees it and lists it as a device. On my phone, I also get the message of "USB connected", or "USB disconnected" (if I disconnect it). In the Windows Device Manager, when I plug it in, it detects the hardware change, and I get the entry for "ADB" in the Device Manager. If I disconnect it, it goes away. So, windows does see it on some level. In that same command prompt, if I type "adb devices", it does not see any devices attached.
If I can get adb to work, I should be able to pull the data off. Knowing that it goes into boot failure, should adb even work? Does it need to boot up far enough for adb to work, or should adb work no matter what?
I've looked into unlocking to install TWRP or similar, but doing so, deletes data which defeats the purpose in all of this.
I can still get to the menu to boot into Normal, Recovery, BP Tools, etc... but so far any option I try puts me back into Fastboot.
Any thoughts? Anything for me to try?
Unfortunately, you're out of luck in this situation. ADB only functions while booted or in a recovery (for retrieving data, it would need to be a custom recovery, which is not an option at this stage for your type of phone). You can not retrieve info in fastboot mode and restoring the phone's software/firmware via fastboot or RSD Lite will also wipe the data.
Hello!
I cant get further on with an my tablet an RK3168 device.All the specs are in this topic, because i was looking for a rom:
http://www.arctablet.com/blog/forum...ssible-clean-4-2-2-or-a-customcwm-rom/#p60994
But i ran into things what i can not really understand or place, and i also already tried a lot already..Maybe its the soc itself, hope someone can help me a little bit.
I wane install a rom, so i first made an backup with RK1.2tools and this backup is ready in flashtools1.37 from finless.It finds rk loader and its ready to flash..
But here i get stucked, adb works, minimal adb &fastboot , google usb driver, with usb debugging on..Adb works, but for example fastboot reboot-bootloader..Only switches off the device, it doesn't boot up in any mode...Tried button combinations but only recovery can show up.So no commands work for fastboot plus starting fastboot with keys, looks impossible.Also in recovery there is no fastboot.In adb i can see all the commands, but everything what starts with fastboot, will give me only an waiting for device output..Also adb shell gives me root, rooted with kingroot..But same thing, goes off and no fastboot..And yes adb has permissions from kingroot.
Because adb works, i can not believe that fastboot would not work, i think myself its the tablet who first has to boot into it before a driver will work.But fastboot oem unlock or fastboot flashing unlock bootloader all are not working.But why it even doesn't start in any fastboot from command pff i cant understand that..
On the internet i see that even fastboot has an screen..Could it be locked or so?
Only weird thing besides that is this! If i put it off, plug in usb cable and charger!!Press vol up or power, battery shows up loading..And i see rockusb device in device manager win7.I can install adb or fastboot on top off rockusb device.But adb shows no server running.And adb devices gives this: 1234567890ABCDEF Device....Thinks its no fastboot but very weird.It only works this way when charger is inserted and battery is loading..
Besides that, rooting was also a pain ...Tried rk188 solution for rk3168, but double zero after 3 times booting..Looks rooted, but Su is not there and cant get installed.It always ends like that, with or without kingroot.And other ways the same, with emulator pushing su and removing kingroot..Doesn't allow Su to be installed properly.
Nothing looks logical for me at the moment. No fastboot, but seems flash ready in RK1.37 tools.Is there a way around fastboot to find out first if my loader is unlocked.
I don't wane brick it with an locked loader, so how to get further on from here or are these soc different from others?
Thanks for any help!:good:
Erik
I