Database Users

[Q] Get into recovery without ADB?

I'm trying to get into recovery mode because I'm stuck on a boot loop, but I can't manage to do it. I've Googled and Googled but the only thing I've managed to find was how to get into download mode, and factory reset. All of the instructions for getting into recovery require you to use adb, but neither adb nor fastboot work for me in any of the modes I've mentioned.
So how can I get into recovery mode (or at least fastboot) without using ADB?
For future reference, since I can't seem to find a single guide out there for this:
Factory Reset Mode
Completely power off phone (hold power button until it resets, keep holding after LG logo shows up to power off)
Hold Vol.Dn + Power until screen powers on
When screen power on, release and hold Vol.Dn+Power again
Downlaod Mode
Completely power off phone (look above)
Hold Vol.Up
Connect USB Cable

AlexRamallo said:
I'm trying to get into recovery mode because I'm stuck on a boot loop, but I can't manage to do it. I've Googled and Googled but the only thing I've managed to find was how to get into download mode, and factory reset. All of the instructions for getting into recovery require you to use adb, but neither adb nor fastboot work for me in any of the modes I've mentioned.
So how can I get into recovery mode (or at least fastboot) without using ADB?
For future reference, since I can't seem to find a single guide out there for this:
Factory Reset Mode
Completely power off phone (hold power button until it resets, keep holding after LG logo shows up to power off)
Hold Vol.Dn + Power until screen powers on
When screen power on, release and hold Vol.Dn+Power again
Downlaod Mode
Completely power off phone (look above)
Hold Vol.Up
Connect USB Cable
Click to expand...
Click to collapse
the factory reset mode woks without adb, when you get to the mode press power twice to confirm doing a factory reset(it wont actually wipe your phone) and you should get into recovery

aliaksei said:
the factory reset mode woks without adb, when you get to the mode press power twice to confirm doing a factory reset(it wont actually wipe your phone) and you should get into recovery
Click to expand...
Click to collapse
Wow thanks. That's a weird process

So even though there is a scary message up that says your phone will be wiped, it doesn't actually happen and you will just go to recovery?

I'm curious about this as well since I heard about people losing data due to this hardware button combination.

AlexRamallo said:
I'm trying to get into recovery mode because I'm stuck on a boot loop, but I can't manage to do it. I've Googled and Googled but the only thing I've managed to find was how to get into download mode, and factory reset. All of the instructions for getting into recovery require you to use adb, but neither adb nor fastboot work for me in any of the modes I've mentioned.
So how can I get into recovery mode (or at least fastboot) without using ADB?
For future reference, since I can't seem to find a single guide out there for this:
Factory Reset Mode
Completely power off phone (hold power button until it resets, keep holding after LG logo shows up to power off)
Hold Vol.Dn + Power until screen powers on
When screen power on, release and hold Vol.Dn+Power again
Downlaod Mode
Completely power off phone (look above)
Hold Vol.Up
Connect USB Cable
Click to expand...
Click to collapse
What's the difference between the factory reset mode and the download mode? I couldn't get the Factory Reset mode to work so I tried the download mode method and it worked but it took me to a screen that says "Firmware Update: Do not unplug the USB connection until the process is complete"... But it sits at 0%. What should I do?

SikkNazty said:
What's the difference between the factory reset mode and the download mode? I couldn't get the Factory Reset mode to work so I tried the download mode method and it worked but it took me to a screen that says "Firmware Update: Do not unplug the USB connection until the process is complete"... But it sits at 0%. What should I do?
Click to expand...
Click to collapse
I think download mode is to restore/update the software through LG's tools in case of corruption or something that doesn't let you get into recovery. I got the same message as you with it being stuck at 0%, but I just held the power button until it turned off. Nothing happened to the phone or my data.
And on the factory reset screen, even though it says it'll wipe everything, it actually won't (at least for me it didn't). It just took me into TWRP (recovery mode). However, if you don't have TWRP installed, then I think it actually will wipe all your data.

[Q] Dead LG G2 Sprint

I have lg g2 sprint version. I have unlocked it by following a tutorial on youtube. On the ui there was a message that there is software update and i tapped to install it, but it was stuck on fastboot mode started udc_start() so i followed tutorial from a forum and fastfbooted boot aboot recovery and laf, but forgot to run fastboot reboot and turned off and on the phone. Now when I try to start the phone it shows the lg logo and after that only the led is flashing no matter if it's charging or not. Any ideas what to do? I have plugged it in to power it, but I am not sure whether it's charging now.
I can enter in download mode by pressing volume up and power button, but I don't have pc near me to try to flash to stock.

lolopopolo said:
I have lg g2 sprint version. I have unlocked it by following a tutorial on youtube. On the ui there was a message that there is software update and i tapped to install it, but it was stuck on fastboot mode started udc_start() so i followed tutorial from a forum and fastfbooted boot aboot recovery and laf, but forgot to run fastboot reboot and turned off and on the phone. Now when I try to start the phone it shows the lg logo and after that only the led is flashing no matter if it's charging or not. Any ideas what to do? I have plugged it in to power it, but I am not sure whether it's charging now.
I can enter in download mode by pressing volume up and power button, but I don't have pc near me to try to flash to stock.
Click to expand...
Click to collapse
The situation after a couple restarts is:
When I put to charge the lg logo appears and the led is flashing from yellow to blue
if I hold down and power button it says "Recovery mode. Loading..." and nothing happens
If I hold up and power button it enters download mode
Can I charge the phone in order to flash it to stock?
p.s. I am turning it off by holding the power button for ~20 sec

LG D802 fastboot problem

Hey guys. I bircked my LG a couple of days ago and now it's in:
[810] fastboot mode started
[860] udc_start()
I cannot enter download mode because the phone will not shut down. When pressing and holding the power off button it turns off for a mere second and then the LG logo comes up and i get into fastboot again. The phone will NOT turn off.
When I connect it to the PC it is not detected as qhsusb_bulk in device manager but as a CMCC ADB Device>CMCC Composite ADB interface.
Any help is appreciated.

zeleman1a said:
When pressing and holding the power off button it turns off for a mere second and then the LG logo comes up and i get into fastboot again. The phone will NOT turn off.
Click to expand...
Click to collapse
hold pwr button longer, don't let it go when LG logo shows... only then the device will power off completely...
after that, search on how to enter the recovery (depending on your bootloader - see dorimanx kernel thread op)

60nine said:
hold pwr button longer, don't let it go when LG logo shows... only then the device will power off completely...
after that, search on how to enter the recovery (depending on your bootloader - see dorimanx kernel thread op)
Click to expand...
Click to collapse
I think I have TWRP. When it's turned off and and i press power+volume down and then when LG logo shows i press and hold them again i get into factory hard reset.
EDIT:I don't think i have recovery set up btw.

zeleman1a said:
I think I have TWRP. When it's turned off and and i press power+volume down and then when LG logo shows i press and hold them again i get into factory hard reset.
EDIT:I don't think i have recovery set up btw.
Click to expand...
Click to collapse
if you have a twrp recovery - it will first show "factory reset", you say "yes" 2 times and it will enter twrp (it will not wipe anything)
if you have stock recovery - then don't press "yes" in the reset screen...
did you by any chance flashed a kernel recently?
fastboot error message is commonly shown when people flash the kernel which is not for their variant - and this can easily be solved with flashing the right variant kernel... (i.e. you have d802 variant and you flashed kernel for d800 variant and vice versa)

Bricked Storm

Hello, I have a problem with my storm. Two days ago I received it and flashed the then latest cm13 and its corresponding recovery. Everything seemed to work just fine until yesterday when there appeared to be an ota update. After the download finished, the phone rebooted itself and is since then stuck with a black flickering screen. Every attempt to start the phone using recovery or bootloader seems to fail, as the phone keeps showing me the black flickering screen, no matter the combination of keys (vol+/vol-) I use to turn it on. If during the black screen I plug the phone to the computer adb can actually see the phone but says it's not authorized to perform any command. On the other hand fastboot won't even see the device.
Is there anything else I can try before sending it back to wileyfox?
Thank you in advance

I've made some progress, I found out that the device can be forced to Qualcomm HS-USB QDLoader 9008 mode by turning it off and then connecting it to usb while holding vol+ and vol-.
I've also found the stock firmware at https://cyngn.com/support.
Now it would be great if somebody could help me, and the others in my situation, to figure the wole QFIL unbricking out, because I'm overwhelmed, and can't seem to find the right info on google.
Thanks to anyone who'll care to help, or share some info

I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.

miSAKe said:
I had a similar issue so have created a thread with stock recovery instructions, which resolved the issue for me.
http://forum.xda-developers.com/wileyfox-storm/help/how-to-flash-stock-images-brick-recovery-t3319617
I hope this helps.
Click to expand...
Click to collapse
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.

maxxie00 said:
Thank you for your reply.
Unfortunately this does not seem to be applicable to my case because on my device fastboot mode doesn't seem to work.
I've spent an entire afternoon trying to get it to boot to fastboot mode using different vol keys combinations and timings, but none of them seemed to work. No matter the combination, it just kept booting to a black screen flickering.
I'm starting to think that it could be some problem unrelated to my actions because if, as I think it is, recovery mode and fastboot mode are two separated things, nothing I did would justify this kind of behaviour.
Click to expand...
Click to collapse
Sorry to hear you are still having trouble, it does sound like the same issue, was a CM13 update from the last couple of days, upon reboot I saw the wileyfox logo but when the Cyanogen logo would normally show during boot it displayed a black screen, which would flicker every few seconds. Holding vol- and power to reboot resulted in the same thing so I was unable use recovery.
When the display was black and connected via USB I was able to see the device using ADB but like you no commands were authorised.
Leaving the phone plugged in via USB and holding down vol+ and power until it rebooted I was able to enter fastboot, once the fastboot prompt was displayed on the screen I attempted using fastboot to boot from a custom recovery, unfortunately that just resulted in the same blank screen for me. I also tried booting the stock recovery with the same result, I admit I did not try many older CM recoveries, but I wanted to revert to CM12.1 anyway, as the accelerometer and gyroscope not working in CM13 at the moment is no good for me.
Only thing that worked was a stock restore, so I think something beyond the recovery got broken as you could not even boot a previously working recovery.
For the sake of sanity it may be work getting someone else try booting it into fastboot before resorting to Wileyfox support. Though your phone is really new so could claim a refund or replacement from the seller, that would probably be faster.
FYI if you do end up sending it to Wileyfox support they do flash it back to stock, I had a broken screen replaced, was repaired and back to me in just under 2 weeks.

What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot

maxxie00 said:
What would be exactly the timing for it to boot to fastboot mode?
Because I just tried (again...) to plug it to the computer while powered off, then it powered on on its own.
After that I rebooted it by holding together power and vol+ and immediately after it rebooted (right after the vibration) I let the power button go and kept holding the vol+ until the black screen appeared again... no fastboot
Click to expand...
Click to collapse
Hi,
Just tried a few combinations to check timings for you.
Powered off, not plugged in, holding vol+ while plugging in phone end of usb connected to computer, keep holding vol+ -> boots straight to fastboot.
Powered on, already connected to computer via usb, holding vol+ and power, release power when vibrates to indicate reboot but keep holding vol+ -> boots straight to fastboot.
Are you seeing the black and white Wileyfox logo when first booting? When going to fastboot it should skip that. If you are not seeing the logo it might not show the fastboot screen either. You can try following the steps above and then issuing fastboot devices from a command/shell session to see if you are in fastboot mode.
I hope that is of some help.

Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...

maxxie00 said:
Thank you but I can confirm that neither of these combinations work for me. When rebooted/powered the device shows the wileyfox's logo.
If I use your first method it just seems to freeze on the wileyfox's logo screen, and the computer won't even see it (it's not listed on the usb devices list) so fastboot's not an option.
If I use your second method, or any other I tried, it shows me the wileyfox's logo and then proceeds to the black screen, which can be seen just by adb (not fastboot) but I'm not authorized to perform any action like you described for your issue.
I'm out of ideas so I'm sending it back and getting it replaced. On the cyanogenmod irc they told me that to brick it like that it cannot be done just by accident but it should require a lot of deliberate effort, and that just installing cm13 + recovery doesn't justify this problem nor does an OTA update, so it's probably some other (hardware?) issue with a very bad timing.
I'm kind of sure it's not the vol+ button that's damaged, because if I leave the device powered off and then proceed to plug the USB while holding together vol+ and vol- it powers on, but the screen stays off meaning the Qualcomm HS-USB QDLoader 9008 mode has been triggered.
Anyway thank you for your help, I could rule out my inability to start the fastboot mode and blame it on the phone xD
Hope I'll be luckier with the next one...
Click to expand...
Click to collapse
No problem, I hope you have more luck with the replacement.

Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you

maxxie00 said:
Here I am again, new device, still can't boot to fastboot mode (this time I didn't flash anything, just unlocked bootloader so it's not bricked).
"adb reboot-bootloader" works, advanced reboot menu works, yet the vol+ combination hangs on the vendor's logo.
I'm contacting cyanogen os people to try to understand what might be the issue...
Could you please confirm that your device boots into fastboot mode when using the vol+ way? thank you
Click to expand...
Click to collapse
Hello again,
So these 5 methods work for me, someone else may have other experiences:
Phone powered off, hold vol+ while connecting USB, other end of USB already plugged into PC, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on, already connected to USB, other end of USB already plugged into PC, hold vol+ and power until reboot vibrate, continue holding vol+ until booted to fastboot (almost instant).
Phone powered on and in OS, already connected to USB, other end of USB already plugged into PC, debug enabled, from ADB console, adb reboot fastboot or adb reboot bootloader
Phone powered on and in OS, advanced reboot options turned on, hold power, select reboot, select bootloader, reboot
Phone powered on and in Recovery, select reboot to bootloader
Currently I am running stock everything.
Perhaps try different USB cables or ports, though I still get to fastboot without the USB cable plugged in.
My Storm was a pre-order so is one of the first releases, it is possible they have changed something since.
Edit: I have come across a thread on the Cyanogen forums which implies this may be related to encrypting your device: http://forum.cyanogenmod.org/topic/117661-bootloader-hangs/ - I see you have been there already
as reference mine is not encrypted at the moment

Hard brick of Z5C ... can I save it?

Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?

apsommer said:
Well, I did it this time.
In a valiant attempt to install a custom ROM, I erased every partition using fastboot,
Code:
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot erase recovery
fastboot erase cache
Now what I meant to do here was flash a recovery, using
Code:
//fastboot flash recovery TWRP.img
but repeating this so many times over the last 48 hours, I did not do above and instead went quickly right into below,
Code:
fastboot reboot
The system rebooted as I told it to ... right into a black void of nothing. Now their is no 'recovery' image and no 'bootloader' image ... the phone is hard bricked, won't turn on at all, dead. I was so close to getting to the custom ROM! Is there any chance to get it back into recovery mode? or have I learned a $350 lesson?
Edit: Further research indicates it may be possible to force the system into fastboot using a USB jig. Has anyone tried this method?
Click to expand...
Click to collapse
When you plug it in while holding volume up what happens?

TheVan28 said:
When you plug it in while holding volume up what happens?
Click to expand...
Click to collapse
Nothing. LED flashes red every few seconds. The same response if plugging it in without holding volume up. Along these same lines, holding the power button on for a few seconds causes the small vibration haptic feedback to occur as if it is turning on normally ... but nothing happens the phone remains dead. Similarly, holding volume down and the power key causes a small vibration haptic feedback as it was booting into recovery ... but nothing happens the phone remains dead. I haven't seen anything on the screen appear, or the phone turn on it any way, since executing the fastboot sequence previously described.

Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk

Ilko said:
Whatever you did, you should still be able to enter in flash mode and flash a stock firmware. And by this I mean full stock firmware, not a ROM.
Sent from my E5823 using Tapatalk
Click to expand...
Click to collapse
Ok, that would be great. I would be thrilled to get the stock ROM back, at this point getting the phone to turn on at all would be a victory! Would you please describe precisely how to do enter flash mode with the phone in the current state? To reiterate, the phone will not turn on in any way (normally, or volume down + power to boot into recovery). The only life in the device is a slow blinking red LED when it's plugged in, and a quick vibration after holding the power button. The screen has not turned on in any way, or the LED shown any color other than red, since executing the fastboot sequence previously described.

hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats

The power key has nothing to do in this context. It is used only to boot into recovery or force OFF.
While holding VOL ↑, plug the USB cable to your PC to enter into fastboot mode (blue light)
While holding VOL ↓, plug the USB cable to your PC to enter into flash mode (green light, or maybe nothing)

TheVan28 said:
hold power button + volume up and to force shutdown
and then hold volume up (or down, i don't quite remember) while connecting it to a pc (hold the button while connecting the usb cable).
If the led turns green or blue, congrats
Click to expand...
Click to collapse
Nothing. Device still unresponsive as described.

does your PC detect the device ? (new device sound notification)

Ilko said:
does your PC detect the device ? (new device sound notification)
Click to expand...
Click to collapse
No, the PC does not currently detect the device. All drivers are correctly installed as the phone was recognized accurately prior to the described fastboot sequence.

This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.

Ilko said:
This is weird. I already erased everyting via fastboot too a while ago, and I could still flash it.
Just to be sure.... unplug all other "smart device" before anything (drivers can't handle more than one device at a time when it comes to FB or flash mode). Open the device manager and let it to the foreground. While you hold the vol down key, plug it and keep holding it until the device is detected. Don't expect any reaction on phone's screen, it remains OFF in both fastboot and flash mode. So, if the device manager reacts, you win.
Click to expand...
Click to collapse
I'm getting something here which is very encouraging! Executing your sequence causes the device manager to blink (refresh) as if it sees something, however no new devices are recognized in the tree. The phone LED goes to a solid green, reminiscent of a fully charged battery, stays on for about 30 seconds, briefly blinks red and then back to green, etc. The device manager is certainly reacting here it just doesn't recognize the device.

So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)

Ilko said:
So here we are, you win. Because you have the "two", detection and green led. And if this state goes off after a certain time, it is normal. There is a kind of countdown and the device quits that mode if nothing is sent to it. You should be able to flash a firmware now with flashtool software.
Just ensure you have proper drivers installed properly (WinUSB drivers need to turn signature verification OFF before or Windows will block the installation)
Click to expand...
Click to collapse
Unbelievable! You saved me! I'm back up with the stock ROM and peace of mind to attempt the custom ROM process again. Saved me $350 ... thank you!!

That's great : )
It is almost impossible to hard brick a Xperia. If something goes wrong, remember flashtool ^^