Hi there!
I have my loved One Plus X broken. Black and broken screen, imposible to see, I dont know if the touch screen even works, I'm guessing not.
I'm trying to recover the data in the phone by usb, the problem, I have no usb debugging so I searched for help, and I discover this post.
When I use the command "adb shell" that returns "error: closed".
I tried updating the drivers, the adb, restarting PC and phone... Nothing works.
Anyone knows how to fix it so I can recover the data?
If there is a form that I can recover the data by commands it will work aswell.
Thanks!
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!!
So, I was messing some things up in safestrap and I decided I want to do a fresh start on my phone. So I went to the wipe section and wiped everything.. Now as I can tell, I have no /system folder, no OS, nothing. I can access bootloader. After intense reading and searching, I managed to connect my phone via adb, adb devices command shows the ID of my phone in a sideload state. Sideloading a rom never worked, tried many of them, at best I got an error about getprop file missing - tried to modify the updater-script using an editor after instructions but still nothing. My main issue is that while adb works fine, drivers are 100% fine, upon entering phone into fastboot mode, it disconnects and there is nowhere to be found under device manager. If I could get it to work in fastboot I could then use RSD lite to flash a stock rom. Also, the only command that works from adb is the # adb sideload filename, anything else returns error:closed. Even tried #adb usb #adb remount and so on. Is my phone a garbage at this point?
forgot to say also, tried to connect via fastboot under windows 7 sp1 / xp sp3 / ubuntu 14.04 .
bump
bump..
I'm having trouble using ADB with my phone. It is a Galaxy J36, and is stuck in a bootloop. (yes I tried wiping the cache, didn't work ) Every tutorial online is telling me to use adb, so I downloaded the Samsung drivers to my computer. I already have the android sdk. When I plug my phone in to my computer, the command "adb devices" does not recognize my phone. It just shows "list of devices attatched" with nothing under it. I've tried entering odin mode, the system recovery menu, and the boot up screen, but I still get nothing. What do I do? Thanks in advance.
UPDATE: Forget ADB, odin saves the day! https://www.youtube.com/watch?v=BciQSJJsOVc
Hey guys, I just got LG l9 from my friend but it is (I am afraid, not knowing much about mobiles) bricked.
When I turn it on it says:
-------------------------------------
Secure booting unsuccessful!
Cause:
-------------------------------------
and after that it turns off. If I charge it it turns on and shows battery charging. At combination of Volume+, power button it goes in Recovery mode.
It shows "This mode is for data backup service center. After removing and reattaching battery, press power key to reboot and keep using phone" and from there I can't do anything, just able to take out battery.
If I try combination of Volume-, power button it shows little android and loading bar, after few sec it restarts and shows booting unsuccessful.
I am not sure what he did with it, but pretty sure he rooted it. Is it possible to fix it, hope someone will provide me some help
Thanks !
It is possible to fix, you need to unbrick it. Find the stock rom for your device and find a good tutorial on how to flash em. Good luck!
Thanks for the reply ! I found everything I need, but I got problem - cant enter download mode. On combination of Volume+ and plugging cable I get S/W Upgrade, and on combination Volume+&- and plugging cable I get nothing. Any ideas how to get in that download mode? Thanks!
Infam12 said:
Thanks for the reply ! I found everything I need, but I got problem - cant enter download mode. On combination of Volume+ and plugging cable I get S/W Upgrade, and on combination Volume+&- and plugging cable I get nothing. Any ideas how to get in that download mode? Thanks!
Click to expand...
Click to collapse
www.hardreset.info/devices/lg/lg-p760-optimus-l9/emergency-mode
Try that, then in adb, type adb devices and see if your pops up, if not, try fastboot devices. If it popped up in adb, you can sideload the zip file, if on fastboot, you can flash it.
Try that, then in adb, type adb devices and see if your pops up, if not, try fastboot devices. If it popped up in adb, you can sideload the zip file, if on fastboot, you can flash it.
Click to expand...
Click to collapse
Thanks for your patience and answers! Problem is I cant reach emergency-mode. I always get S/W Update. Under adb devices I can see my phone in recovery mode (was thinking maybe emergency=recovery mode). I tried sideload, it starts loading but after some time I get error:closed. I tried doing adb usb before as well but gave no results.: . Any other ideas? Is there any way to "make" phone run ROM from SD card (in recovery mode can't navigate anywhere like I can on my other phone).
Again thanks for your help and time!
Infam12 said:
Thanks for your patience and answers! Problem is I cant reach emergency-mode. I always get S/W Update. Under adb devices I can see my phone in recovery mode (was thinking maybe emergency=recovery mode). I tried sideload, it starts loading but after some time I get error:closed. I tried doing adb usb before as well but gave no results.: . Any other ideas? Is there any way to "make" phone run ROM from SD card (in recovery mode can't navigate anywhere like I can on my other phone).
Again thanks for your help and time!
Click to expand...
Click to collapse
If it sees your phone as recovery, you can be rescued! Run adb shell and once the shell has popped up, type ls and if you see the phone structure of directories, you can exit the shell and push the file from your pc to your phone. But before you push, I want you to try to run adb reboot-bootloader and see if fastboot recognises it.
RAZERZDAHACKER said:
If it sees your phone as recovery, you can be rescued! Run adb shell and once the shell has popped up, type ls and if you see the phone structure of directories, you can exit the shell and push the file from your pc to your phone. But before you push, I want you to try to run adb reboot-bootloader and see if fastboot recognises it.
Click to expand...
Click to collapse
I think I am making some progress. First on adb reboot-bootloader my phone reboots into secure booting unsuccessful, same as before. On the adb shell/ls I get to see cache, charger, data, default.prop, dev, etc, system, temp and lots of other things. I guess that are directories we are looking for. But when I go adb push filename.zip /data/media I get failed to copy filename.zip: Permission denied. Guess nothing can work at first, sorry
https://forum.xda-developers.com/showthread.php?t=2216896 Have you tried this?
RAZERZDAHACKER said:
https://forum.xda-developers.com/showthread.php?t=2216896 Have you tried this?
Click to expand...
Click to collapse
This gets complicated, I found xloader and uboot, but problem occurs when I try to install fastboot drivers, says third party doesn't contain digital signature information?? I think I was close with shell from adb, just how to get privilege to push files? Tried so many methods.. Thanks again on help.
I think I may have posted this initially on wrong forum here, so sorry for the repost:
Hi, I have MI7 and after wiping data (noticed at show 2% complete and just returns, saying wipe was done, so maybe that is a sign of something) and rebooting it keeps saying that there was a factory reset and I need to enter password. I keep going into MI 3 Recovery and choosing MI Connect and trying ADB but `adb devices` simply lists a sideload entry and adb shell keeps returning error:closed. So `adb shell rm /data/system/gesture.key` doesn't work as it returns `error closed`. The MI PC Console tool doesn't detect the phone.
If I type `adb reboot-bootloader` my phone shows Fastboot but no menu. Just hangs at fastboot. `fastboot devices` returns a fastboot device.
So seems like there are some signs my phone is able to be communicated with, but none of the usual commands are helping me get anywhere...
Really not sure how to totally reset this device so I can start all over again. This factory reset loop just doesn't want to go away.
Any ideas how to get this phone to behave like it is brand new, regardless how technical?
thanks,
Brian