Database Users

[Q] Can "see" device in ADB, not in fastboot....

Hey guys,
Bare with me please as I am fairly new-ish to Android but have some experience with Samsungs, HTCs and the beloved LG GT540.....
I appreciate if anyone can help me on my plight.....
My girlfriend was running Cyanogen Mod for the last year or so on her device and decided that she wanted to try out a different ROM on her phone....
I wanted to install the Oxegen ROM....
Originally I was thinking it would be easy and I could put it on through Clockwork Recovery and flash the zip no problem, for some reason when I rebooted to recovery clockwork would not load up on the device.... just blank screen....
Not content with this, bored on a Sunday afternoon I gave it a couple of hours of my time and in the process messed my girlfriends phone up....
What I did was I tried flashing back to stock using the LG KDZ updater, that was fine and the phone rebooted and has since stuck on the Android logo....
According to this thread : http://forum.xda-developers.com/showthread.php?t=1078745&highlight=stuck+on+android+screen I gave all this a go and I can not get the device showing up in Fastboot, I can not enable USB debugging on it either as I can not get into the phone to tick the box....
In my cmd prompt I am seeing this :
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In my device manager when my device is connected and powered on I am seeing this :
When I am connected and the device is in "download mode" my devices are like this :
I understand the steps provided in the link above and I am fairly confident I could do them if I can get the device "seen" in Fastboot....
I have installed and re-installed all the USB drivers in hope that it may be a driver issue, now I am wondering is it maybe my OS? Win7 64Bit Ultimate?
I can try it on XP netbook if thats all thats causing my issues....
I am kinda lost now and wondering have I bricked it? It will be the first phone I have if thats the case....
Any help would be appreciated, thanks a lot guys....
Mods if this is in the wrong area, please feel free to move my post.....

did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.

m1st3r1 said:
did u go to fastboot (power+camera pressed when booting up).
well, from my experience, if i flash incorrectly (via fastboot or recovery), it will go bootloops or go to clockwork, or if i flash incorrectly via kdz, i've got stuck in LG logo or got linux kernel panic.
it seems to me u've flash kdz incorrectly. flash kdz with fastboot mode via download (or emergency mode).
try this:
http://forum.xda-developers.com/showpost.php?p=13184840&postcount=42
and make sure u already install all LG drivers (u can Google those).
gud luck. if else fails, put a very sad and stupid face, act as u dont know anything, bring the phone to the LG representative in ur town.
idk for 64 bit version as i use 32 bit. u can try find pdanet driver, there is 64 bit driver there and it install fastboot well in PC.
Click to expand...
Click to collapse
Fastboot and ADB works on Windows 7 Home Premium 64bit. I installed LG Drivers then Google USB Driver. It worked then. But I know I did struggle to finally get it working.

Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!

Ko_Ka said:
Thanks a lot for the advice and replies guys....
As I said, I think my problem lies in not being able to tick the USB debugging option on the phone as I can not boot into the phone to do so....
Is there a way to enable USB debugging over ADB?
As I said, I can "see" the phone responding to ADB, just not fastboot!
I am in the process of installing everything and starting fresh on the Xp netbook, if this fails I would say its new phone time for my g/f, Sony X8 is 80 euro on our network so if the worst comes to the worst I will get her a new one....
Much appreciated guys and if anyone has anything to the thread I will be all ears...
Cheers!
Click to expand...
Click to collapse
i think u got it wrong.
read here: http://android-dls.com/wiki/index.php?title=Fastboot and here: http://wiki.cyanogenmod.com/wiki/Fastboot
first of all, i need to ask u the question (again), can u boot to fastboot (or bootloader) when u pressed power (the reject/red phone button) and camera button altogether? the fastboot screen in the phone will be like black screen, but with a little amount of backlight (u'll notice the difference) or blue screen with texts if u flash a kdz-modified-fastboot. if u cant go to bootloader/fastboot, then u need to flash a kdz with fastboot.
u can try this: when u type adb devices, type: adb reboot bootloader
though im not sure if ur gf's phone has fastboot/bootloader (might be missing during the kdz flashing that u've done).
when u type adb devices

m1st3r1 - if you ever come to Dublin, I will buy you a beer!
After nearly 3 days of pulling what hair I have left on my head out, my problem was I was mistaking Fastboot for Download mode.....
I was connecting the phone holding the volume down so it came up "download mode" now all I did was hold the camera + red button and off it went with the command from the post above....
I feel like an idiot, but im a happy idiot right now.....
Thanks a lot, means a lot to me.... (and my girlfriend!)

LOL welcome to the hackers club

LG G2 Demigod Crash Handler when go into recovery.

I have an LG G2 D802 International, that for the past 2 weeks wasn't working well,the application android.home crashed so the phone was unusable, I tried rooting and installing a custom rom but I didn't manage to install a custom recovery on Kitkat, so I decided to hard reset it, after that I finally decided to upgrade to Lollipop from Kitkat, then I decided to root the device and install a custom recovery. The problem is that I rooted the device, but I tried to install a Custom Recovery via Autorec and it didn't work, so I tried Flashify and now if I go to Recovery I got this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
, if I go into download mode I can't flash anything, LG Flash Tool 2014 crashes after I select the Language.. Now the difference between my problem and the others is that I can still manage to go into Android and use my phone normally, but I can't go to Recovery and flash anything into Download Mode! Please Help me, I really don't know what to do.
Sorry if I did some Grammaticals errors, but I'm Italian and I hate translators.
If someone knows how to restore the basic recovery that will be fantastic, and my phone is branded Vodafone, if I wanna switch to the OPEN firmware without all the things from Vodafone I can just do it by flashing it with the LG Tool?
Help me, the OS rebooted and now it's a continue bootloop, if I go to Download Mode it appears as a black screen and on the pc pops out like 30 disks, help How do I unbrick the device?

rbucket said:
I have an LG G2 D802 International, that for the past 2 weeks wasn't working well,the application android.home crashed so the phone was unusable, I tried rooting and installing a custom rom but I didn't manage to install a custom recovery on Kitkat, so I decided to hard reset it, after that I finally decided to upgrade to Lollipop from Kitkat, then I decided to root the device and install a custom recovery. The problem is that I rooted the device, but I tried to install a Custom Recovery via Autorec and it didn't work, so I tried Flashify and now if I go to Recovery I got this
, if I go into download mode I can't flash anything, LG Flash Tool 2014 crashes after I select the Language.. Now the difference between my problem and the others is that I can still manage to go into Android and use my phone normally, but I can't go to Recovery and flash anything into Download Mode! Please Help me, I really don't know what to do.
Sorry if I did some Grammaticals errors, but I'm Italian and I hate translators.
If someone knows how to restore the basic recovery that will be fantastic, and my phone is branded Vodafone, if I wanna switch to the OPEN firmware without all the things from Vodafone I can just do it by flashing it with the LG Tool?
Help me, the OS rebooted and now it's a continue bootloop, if I go to Download Mode it appears as a black screen and on the pc pops out like 30 disks, help How do I unbrick the device?
Click to expand...
Click to collapse
facing the same problem, and looking for assistances

anmsharif said:
facing the same problem, and looking for assistances
Click to expand...
Click to collapse
Have you checked your phone model by removing back cover or on imei.info ? Make sure it is actually a D802 version coz it is common in lg phones that what it look like is actually not ☺
I also bought a used lg g3 and was happy to have an open d855 due to fake rom installed in it but in fact in real it is sprint ls990.

Having the same problem with a d800
I can still boot in to Android, and gent into download mode, but I haven't test download mode yet, I would like to change te recovery to twrp so I can flash a costum ROM, is there a way of installing another recovery even tho the original recovery seams broken or something?

[SOLVED] Can't boot, can't boot recovery, oem locked, usb debugging disabled

Happened when I was updating twrp:
I downloaded the .img from their website, booted into my older version of twrp, went to flashing pressed the butting in the bottom right corner, selected the file and selected 'recovery'
Said it was successful, so I rebooted, then it wouldn't do anything anymore except for fastboot.
1. Can't boot into recovery
2. Can't boot normally
3. USB debugging disabled
4. oem locked
Only thing I can enter is fastboot.
I followed this guide, but no luck on my end.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.

passion8059 said:
Have you tried this?
http://forum.xda-developers.com/oneplus-2/general/guide-return-op2-to-100-stock-unbrick-t3229606
and
All in one toolbox by mauronofrio.
I my self had lost recovery myself and flashed stock image in toolbox and then flashed image from above link to restore to stock and started custom rom process again.
Should not erase twrp once recovered if it has reflash your previous version of twrp or hybrid version.
Hope this helps.
Click to expand...
Click to collapse
It's no use because oem is locked. That means I can't flash anything.

toolbox should still help you unlock bootloader again

Just use the Qualcomm factory restore image to return the phone to original shape of things.

passion8059 said:
toolbox should still help you unlock bootloader again
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pitrus- said:
Just use the Qualcomm factory restore image to return the phone to original shape of things.
Click to expand...
Click to collapse
I have no idea how I would do this without being able to flash anything.

Do you mean that the Qualcomm download program also crashes like fastboot? Sounds like you either have some problems with your windows installation or perhaps you haven't searched for and downloaded the Qualcomm restore if your still trying to flash the ordinary way instead of the emergency way.

Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys

Theevilsocks said:
Was able to fix it when I was messing around. Not sure what I did but it worked.
Thank you for all your help guys
Click to expand...
Click to collapse
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc

Redjax said:
I'm having this problem too, and this isn't helpful. What were the last steps, or at least some of them, that you took to get it working? Which toolkit/script/program were you using? etc
Click to expand...
Click to collapse
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.

Theevilsocks said:
I used this tool: http://forum.xda-developers.com/oneplus-2/general/guide-official-op2-stock-reset-to-oos-3-t3402020
I fiddled around a bit with it, but I'm not sure what I did, and I already deleted the files.
Click to expand...
Click to collapse
Literally JUST finished with this guide, and my OP2 is alive again! I was going to come back and post. Thanks for the link.
Anyone trying to use this guide without success:
There's one very important step I somehow missed. You MUST disconnect your phone, hold the power button for ~15-20 seconds until it's off, and hold the Volume+ button, THEN plug it back in. Your computer will make the "device connected" sound, but the screen will stay black. THIS IS OK! That means you're in a special recovery, which is where you need to be for the tool.
I also installed the certificate file in the folder I downloaded, then rebooted (it did not work before a reboot, but did work after).
So, the steps:
1. Download the files, make sure your signature signing for drivers is off.
2. Install the trusted certificate, then the driver.
3. Reboot PC
4. Power off phone (hold power for 15-20 secs), hold volume+, then connect through USB (wait for device connected sound, screen on phone will still be black)
5. Run the tool (I ran as admin, not sure if that's required)
6. Weep with joy that you finally found a solution that works.

i probably hard bricked a1 open for any ideas ( only launch in edl mode)

Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

onursewimli said:
Hello I recently bought mi a1. First time using xiaomi or aosp kind of devices. I didnt know anything about fastboot, adb etc. Thanks to xda users learned it and open bootlock my phone. I flashed twrp magisk etc and working flawlessly. After oreo update i want to clean flash my device. Since first time using android to now i always made a clean flash to my phones when changing roms or updating major updates. I think this time is the beginning of my agony When i flashed oreo and factory reset the device stuck at first time opening. I waited about 10mins more or less and a bit hasty i turn off my phone. When i turn on the device keep bootlooping to twrp. I have done a thing seen in a thread that i couldnt remember now i will add when i found it.
Now my device doesnt respond to any buttons. No power off no power off + volume up etc. all the combinations No fastboot no adb etc.
*When i plugged in to my pc white led keeps blinking. I searched google about it i thinks its in EDL mode.
When i look at the device manager it says Qualcomm HS-USB QDLoader 9008 (COM6)
When try to flash fastboot room via xiaomiflash it couldnt read hello packet and says Can not read from port COM6
When i use eMMC DL Tool for Customer ENG v5.2.0 R it says Failed to connect phone
When i use QFIL 2.0.1.1 it says sth about sahara. ( i try to flash now but it no errors however nothing on phone.)
Rom i try to flash is tissot_images_7.12.19_7.1
Click to expand...
Click to collapse
Oh, I know that feeling of having bricked one beloved device or at least thinking it is bricked. So I did some new year's digging for you and maybe found a way to help.
Assuming your bootloader is still unlocked and it is really the EDL mode (at least it sounds a lot like it reading the info you have provided) you should have still some good chances.
Please follow this tutorial found here: http://en.miui.com/thread-294318-1-1.html
And for flashing the firmware you are looking for, please have a look at my thread over here, which leads you to the best suited download package of version 7.12.19, that I could find:
https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
So give it a go, good luck & please provide your feedback here.
Maybe it can help others too
Edit: I guess the part which is probably the most important is the qualcomm driver

hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.

onursewimli said:
hello thank you for help however i almost tried everything that could be tried. nothing happened. i sent my phone to service. hope they would repair with no additional cost.
Click to expand...
Click to collapse
Did they fixed it? Without any cost?

Z17 Mini S - Bootloop / stuck on Boot Screen

Hey guys!
Recently got myself the Z17 Mini S and installed TWRP (chinese version).
Then I rooted the phone, cleaned everything, and installed the latest ROM (found on the Nubia Homepage).
Worked fine, and so I installed GApps.
But I installed the whole package with lots of "useless" apps (Google Reader etc.) and wasn't able to uninstall them for some reason.
So I wiped everything again, cleared the caches, and re installed the ROM.
Now the phone is stuck on the "Nubia" logo when booting up and I can't start it anymore at all (TWRP still works).
I tried wiping and reinstalling the ROM several times, and also tried the older versions of the ROM, but nothing fixed my issue, still stuck on the boot screen.
I'm in a really desperate spot right now, so thanks for any kind of help!

install the rom, reboot. If the phone stucks on the nubia logo, go back to the TWRP, root the phone, reboot, and it will boot normaly

bakchich said:
install the rom, reboot. If the phone stucks on the nubia logo, go back to the TWRP, root the phone, reboot, and it will boot normaly
Click to expand...
Click to collapse
Hey, thanks for replying!
The phone should be rooted ( I managed to do that before it crashed if I recall correctly) and I tried reinstalling the ROM and cleaning everything after that already, without any success.
Here's some more information I can provide:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://i.imgur.com/t19Ko8V.png

Ok, got a little update:
I found a way to recover the phone by going into the Nubia emergency recovery and flashing the ROM with it, which makes it work again.
But now the phone isn't rooted anymore and I can't install GApps, because named emergency recovery can't install the GApps .zip.
So I reinstalled TWRP for that, but now it's stuck at the boot screen again!
I don't know how the root the phone without TWRP, but as soon as I install TWRP I can't boot it anymore.
And without root permissions, I can't install GApps with the OpenGApps app either...
edit: just saw your reply on the other thread, I'll give it a try!

Stuck at this screen
I had RR_N_5.8.5 on my z17 mini.
Tried to install LOS15.1 but error:7 was coming continuously.
I used nubia emergency tool 1.1.4 recovery to go back to original ROM as RR was not even allowing reset.
Now stuck at this screen YOU HAVE SHOWN.
adb devices - no device shown
fastboot devices does not show any device
windows device manager shows Qualcom HS-USB 9008 (com14)
nubia emergency tool detects device but can only run recovery, other two options does not work.
Got stuck............................how to flash twrp now............................PLEASE HELP.
==========================
ALL DONE
=========================
I uninstalled all mobile drivers from my windows10.
Rebooted and reinstalled only ZTE and Qualcomm drivers.
Started and done.........................................Installed TWRP without rooting---yes ---without root
When restarted and checked with magisk - it said device not rooted.
Went back to twrp and installed superSU .. and done.
I have problems :
The device is working perfectly ---- many many many thanks for the ROM on oreo.
1. Battery performance is poorer than original - originally this device was never a good performer.
2. THE MAIN ISSUE - twrp can read the SD card, installs file from it but after booting it is not able to access the SD card - says non supported. Tried with 16/32/64/128GB cards. Tried to format SD with it simply can't format and quits after 20% with every card.
3. A typical problem same with A710FD and Z17mini(6GB128GB) - can not receive calls if and only if google phone is not the default app. Tried Drupe, Contacts, True Phone, tru caller and whatever I got on playstore!
Its only 20Hours after installation so may some other issues pop up later. I dont play games or anything. Minimal user in true sense.
BUT AGAIN---MANY MANY THANKS FOR THE HARD WORK TO GIVE THIS ROM.
Risuno said:
Hey, thanks for replying!
The phone should be rooted ( I managed to do that before it crashed if I recall correctly) and I tried reinstalling the ROM and cleaning everything after that already, without any success.
Here's some more information I can provide:
https://i.imgur.com/t19Ko8V.png
Click to expand...
Click to collapse