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!!
Dear Community,
I got my Note 3 Pro Snapdragon Version today and I tried unlocking the bootloader, installing root and TWRP.
Unfortunately after I installed TWRP, WiFi didnt work anymore so I wanted to go back to where I was before.
i tried flashing the GlobalRom with the MiFlash Tool but somehow I'm now stuck with a bootloop.
The phone starts up and shows the MI Logo but doesnt go on. I tried booting TWRP temporarily via fastboot commands so that I can try to flash flashable zip files
but it doesnt let me execute "fastboot boot xyz.img" anymore because my device is locked.
I would really love to hear any solutions or ideas. I dont want any root or something anymore. If someone has an idea Im very happy!!!
thanks a lot in advance and tell me if you need any more infos
Paul/shisaya24
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Alex3oe said:
1. keep vol + and vol - pressed while connecting USB to enter adb mode
2. check if phone is connected with "adb devices" in command line, if phone shows up, enter "adb reboot edl"
3. now you can flash via MiFlash
Click to expand...
Click to collapse
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
search miui forum for unbrick, there is 2 or 3 method without opening your device
exp: http://en.miui.com/forum.php?mod=viewthread&tid=257227
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
shisaya24 said:
Unfortunately they all do not work because they always require either a phone in download mode, and i only get to fastboot and adb sideboard or they require flashing something via fastboot but I can't do that either because it says my device is locked if I try...
Any suggestions how to flash a ROM with fastboot only or with adb sideload?
Thanks a lot
Paul
Click to expand...
Click to collapse
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Dharani_V said:
I Had The Same Issue Brother ! There are only 2 Things which you can do now .
1. Test Point Method to enter EDL
2.Give it to Service Center . I Gave Mine to Service Center ,They Fixed it in 30 mins or less and it was free
Click to expand...
Click to collapse
Can I do the test point thing myself or is it risky?
What kind of service center? A general mobile phone repair shop or a Xiaomi special one?
shisaya24 said:
First of all, HUGE thanks for your fast answer!
Unfortunately I couldnt get this to work. Since I am stuck at the Logog screen here is what I tried:
Pressing both volume buttons while Logo Screen and plugging USB.
Pressing both colume buttons while fastboot screen is up.
These two didnt enter adb mode, I guess because of the bootloop I'm in
I also tried antering recovery mode with volume up + power button. Pressing both volume buttons didnt help either but when I am in recovery like that it shows my device in adb as "sideload" device.
Maybe that helps ? Can you give further advice or am I doomed?
My idea would be: Is it possible to reflash the device completely only usinf fastboot? The only thing I seem to be able to enter is fastboot...
Is there a way from fastboot to "working phone" ?
or maybe through the "adb sideload" state?
thanks a lot in advance!
Paul
EDIT
tried installing via "adb sideload xyz.zip" command but after shortly showing a status bar on phone screen it aborted and said "Total xfer: 0.00x" on PC screen .
Also: I read "adb reboot edl" brings you to download mode so you can flash something. Tried it but the phone just rebooted the normal system, so it stuck on Logo again...
Click to expand...
Click to collapse
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
I will try that this evening when I am at home again and report. Thanks
Alex3oe said:
I've been facing the same (or a similar?) problem about a week ago but managed to get out. Knowing me for having a head like a sieve I made some notes, sadly quite rudimentary
Did you try to flash with MiFlash after "adb reboot edl"? If I remember rightly after "adb reboot edl" you got the logo like booting another way, but the light is blinking red. Then I could flash via MiFlash.
I'm quite sure that if you get a "reboot" after entering "adb reboot edl", your phone will be in edl mode.
Click to expand...
Click to collapse
Unfortunately this doesnt work. Phone reboots and shows MI Logo but red light doesnt blink and MiFlash doesnt recognize any devices.
Do you have another idea? :/
How did you unlock the bootloader, via official permission or that unofficial hack?
Sent from my Moto G using Tapatalk
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
shisaya24 said:
I didnt use the official way :/ Im so hoping my phone isnt broken. I wish i owuld have been more patient
Click to expand...
Click to collapse
Only options you have right now are:
1) using test points method which is a but cumbersome and voids warranty if you care about that.
2) go to a xiaomi service center of you have any nearby.
It is hard bricked.
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
shisaya24 said:
So there is absolutely no option to unlock bootlader via adb sideload or fastboot ?
Click to expand...
Click to collapse
Apparently, no! Whenever using unofficial methods, read precautions carefully and you missed all as I can see. Wait if someone can help you out.
apply official unlock. then unlock your device from fastboot mode.
asaharaSK said:
apply official unlock. then unlock your device from fastboot mode.
Click to expand...
Click to collapse
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
shisaya24 said:
That sounds nice and easy. I already applied for official unlock.
But: do you know if u can use the official unlock now? I can only access fastboot and adb sideload mode. Is it possible to activate official unlock from there? Or do I need a working ROM rather?
I would have thought that official unlock doesn't work from fastboot /adb sideload...
Click to expand...
Click to collapse
Does anyone know this?
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
smiley1960 said:
I have the same problem. I made the same mistakes as shisaya24. I have followed every procedure for unbricking and nothing works. I even applied for an unlock code and got it from Xiomi. I used their mi-unlock app which requires fastboot (pwr/vol-) but it gets to 50% and bombs out. It states it can't verify the phone. Can anyone please help me??
Click to expand...
Click to collapse
out of sheer desperation I tried MiPhone again and after a few tries, MiPhone started updating the OS. My phone now works again and I have an unlock code as well.
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.
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.
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: