Hello all, my LGWR doesn't enter anymore in fastboot mode (swipe from 11 to 5 does nothing) i was wondering if a fastboot cable would help, i saw that some moto and kindle devices can be unbricked with that cable.
Cannot post a link yet but search on amazon "Fastboot-Motorola-Factory-Atomic-Market"
have any of you tried that ? i think in the case of LGWR the cradle should be opened and pin 1 (Vcc) connected to pin 4 (NC). maybe trough a resistor ? of what value ?. I ordered a cradle from china to "hack" it but it takes 30 days to reach me... Somebody can try that faster than me (have a cradle, open it etc)?
thank you
did you try abd to enter fastboot?
when i connect it to PC it says "usb device not recognised" and "unknown device" and i cannot add a proper driver. I tried a few drivers, which one should i use?
thank you
furygreen said:
when i connect it to PC it says "usb device not recognised" and "unknown device" and i cannot add a proper driver. I tried a few drivers, which one should i use?
thank you
Click to expand...
Click to collapse
i format my pc, install windows 10 enterprise, then install adb 1.4.2 from here http://forum.xda-developers.com/showthread.php?t=2588979..when connect smartwatch, windows find the driver..if adb see your smartwatch you solve your problem i hope
does the watch boot?
sometimes it restarts after a few seconds (during coloured balls animation), sometimes it boots up to "Android is stating / app xx of xx" and after it finishes "Power off.../shutting down"
So I ran into a problem while flashing a file that brought me to a bootloop, and in most tutorials i need to get into the recover but I can't do that when my Vol Down button doesn't works, is there any way to boot into recover without it?
I have TWRP, and when I try to use adb, it doesnt recognize my device (I hear the windows sound that something was plugged in when I plug it in, and yes, the adb worked before that)
Now that I restarted the phone (by taking out the battery flat cable thing and plugging it back in) it turns on into a white screen with a battery sign, I still hear the sound when i plug it in tho...
Now it came back to the bootloop and in the ADB it shows the device as unauthorized, is there any way to do change it to "device" ?
Message that appears when I try to use "adb reboot bootloader"
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Click to expand...
Click to collapse
That's the only phone I have, so any information and try would be appreciated
Hello everyone,
It seems that my worst nightmares came up, and got my device bricked while trying to flash it to a stock ROM (had a custom multilingual ROM installed by the chinese seller), and now it's in a strange stage, as Windows detects the Qualcomm port, but adb can't see it.
The adb devices list is in blank, and QPST detects everything, but when trying to flash the device, the error message on the screenshot appears.
Also tried to do it with MiFlash, but didn't worked too.
Any idea about how to solve this?
Thank you in advance for your help.
P.D.: My device is in black screen, so no menu or anything.
P.D.2: Already downloaded the Android SDK in order to try it's ADB, but it didn't worked too.
Now after some research, I found out that the "ADB interface" is not showing in Windows device manager
I tried to install it manually, but can't find a way to get it working, and after the flash, USB debugging was set on, so can't figure out what could be happening...
Is it possible it's completely dead?
Any idea?
Just to say that I have tried multiple combinations while plugging the device to the PC, and didn't worked...
I mean, the PC seems to react, but always with the same end, only shows the Qualcomm port 9008, nothing about the adb...
Getting out of ideas, anyone more has some?
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Zukunft said:
did you start the tool with admin rights?
read a Little bit here
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-z2131-only.104/
if you have a Z2 pro take this
http://zukfans.eu/community/threads/howto-flash-a-stock-zui-rom-zuk-z2-pro-z2121-only.57/
Click to expand...
Click to collapse
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Noggin said:
Yeah, I already started the cmd with admin rights, but the problem is that adb does not works, as the device is not turning on.
As you can check in my first post, in the screenshot, after running the "adb devices" command, it doesn't gives any kind of error, just returns a blank list.
Click to expand...
Click to collapse
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
arif_kholid said:
adb will never recognized it, in 9008 mode or it's called EDL, the only program that recognized the port is QFIL / Miflash. if you get an error when flashing you must reset your phone again to repeat the process by pressing power button for a couple seconds. if your bootloader already unlocked that must be simpler to do, just press power button for a couple minutes until shor vibration then press vol up + vol down and connect to usb at the same time..
Click to expand...
Click to collapse
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Noggin said:
Thanks for the info, I've tried the vol + and vol- buttons after the short vibration, and the PC does not detect the device...
Is it there any other way to get the device detected by the PC?
Actually, the only thing the device does, is the following:
After pressing the PWR button for around 5-7 seconds, it makes a short vibration and the notifications led makes a flash in green colour, but nothing more... If you keep pressing it, around 7-8 later, it makes a litte bigger vibration and a flash on green too... And if you continue, it does on, and on, and on...
Any idea? Anyone told me about getting a Xiaomi Deep flash cable, but I'm not sure about if that will work or not...
Click to expand...
Click to collapse
i've already tried xiaomi deep flash cable, and its work on my z2 plus, that's how to force phone into 9008 mode.. and also, dont add space between folder names where your firmware files there or there will always sahara fail
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Well, finally, I talked with the aftersales dpt from the shop where I got the device, and returned it, and incredibly it seems it was defective.
The guy from the tech dpt said that it wasn't supposed to die that way, so they returned me a brand new device, and fortunately it's up to date with ZUK's last official ROM.
Thank you everyone for your ideas and help, now I can enjoy this great device
My Zuk Z2 plus got stuck after TWRP, I need help badly.
sirmclord said:
Hey man!
I had the same Problem!
Sahara error, no reaction from device, black screen, port recognized in qfil etc.
I found out that this behaviour of the device means, that it is in EDL-mode.
what helped ma was:
1) Unplug everything.
2) Set up the QFIL Tool completely, but do not hit "Download Content".
3) Try to "reboot" the Zuk Z2 Pro by pressing the power button for several seconds. Kind of resets everything.
4) Plug in USB
5) execute: "adb reboot edl" via adb
6) unplug USB
7) plug in USB and immediately (within a second!) hit the "Download Content" buton, just after it is clickable.
8) dowload should start without sahara error
Hope it works! :good:
Click to expand...
Click to collapse
I will tell my issue
I bought this device this July month, I was encouraged seeing you guys did a lot of flashing, I thought I could flash myself but it became a nightmare now.
I am not that much technical so please bare my usage of words below, but I need a real help.
I was doing the basic TWRP for getting the AICP ROM 12.1 but after wiping the data from TWRP my device doesnt get recognized for the Sideload and I did whatever I can but it doesnt detect my phone, so I am having a screen with Start "Green" which is showing the device status as unlocked and when I click on Recovery it goes to the Zuk logo and doesn't have any sign after that.. stuck really
I tried using QFIL but my device detects as 900H but not 9008 also adb doesn't detect my device at all after this.
I think I really did a hard brick of my device.
I dont want to loose hope, I want your help really badly.
For those of you who had the same problem don't give up! I was in that same situation and I solved by putting my phone on EDL via this method
https://www.youtube.com/watch?v=2m44xKog-dI
After plugging the phone for the second time and QFIL recognize as EDL mode I clicked on download content as fast as I could so it started to flash the ROM that I spent like 10h trying to figure a way to do it lol. Anyways, the procedure is the same as putting into EDL via adb fastboot, the only difference is that you make it through a "fake" deep flash cable as that guy in the video shows.
formerly rooted H811. I unrooted with supersu and attempted to relock the bootloader. But It didn't take. It appears to be in some in between galaxy.
I get into fastboot, but "fastboot devices" comes up empty.
Would like to lock to update to 20X. No PC, only Mac.
LG Bridge sees USB, but not phone.
Help appreciated.
You do realize locking the bootloader will perform factory reset and wipe your data. Are you trying fastboot through MAC, not sure how it is different from PC so if that is causing the issue can't help much.
Is usb debugging enabled, and you have given permission in the pop-up that pops up on phone screen when you connect it to MAC/Computer the very first time? It is possible you missed that permission pop-up the first time and now permission is denied permanently. You may wanna uninstall and reinstall LG driver/device, connect phone again, and look for that permission pop-up on phone screen and allow it. Try connecting usb cable in different usb port too, that might make the pop-up appear again. Also, remember if bootloader is altered or you got custom recovery, phone will possibly soft brick and you will need to use LG Bridge or LG UP with phone in download mode to reflash kdz. Hope this helps.
Edit: For the permission pop-up to show, the phone needs to be turned on, be in mtp mode, and usb debugging to be enabled. Then once you have given permission, you use adb command to reboot into bootloader or i think with phone off, hold the volume down button while you connect to usb cable and not let go of the volume down button till phone is in fastboot menu.
Hi,
I wanted to install Lineage OS on my Sony Xperia XZ2 compact. It has the latest stock firmware installed.
adb devices lists my device, preconditions are ok (bootloader unlock yes and debugging enabled and authorized)
adb reboot bootloader: the phone turns off, red light for 3 seconds, vibration, cyan light and black screen
fastboot devices simply does nothing
turn phone on again
turn off phone
hold volume down + power on -> vibration, "SONY" appears, "SONY" disappears, vibration, phone boot into normal work mode
I do not get into fastboot mode
Any ideas?
Best regards,
Ghost
Trash
Trash
RelaxIamOnlyAghost said:
adb reboot bootloader: the phone turns off, red light for 3 seconds, vibration, cyan light and black screen
fastboot devices simply does nothing
Click to expand...
Click to collapse
Can you try
Code:
fastboot getvar all
If your device is recognized correctly it should either give you a long list of values or an error.
Else you get something like "Waiting for devices".
< waiting for any device >
nothing else
RelaxIamOnlyAghost said:
< waiting for any device >
nothing else
Click to expand...
Click to collapse
Okay. Then it makes sense that "fastboot devices" shows nothing.
Your problem is that your computer doesn't detect your phone in fastboot mode.
I think your cable should be okay (since adb works) but maybe you need some additional drivers?
You can also try solutions you find in the web if you search something like this:
Computer doesn't detect phone in fastboot
Click to expand...
Click to collapse
Or "Windows" instead of "Computer" if you use windows etc.
User699 said:
Okay. Then it makes sense that "fastboot devices" shows nothing.
Your problem is that your computer doesn't detect your phone in fastboot mode.
I think your cable should be okay (since adb works) but maybe you need some additional drivers?
You can also try solutions you find in the web if you search something like this:
Or "Windows" instead of "Computer" if you use windows etc.
Click to expand...
Click to collapse
Ok, I got it. I did not turn "driver signature enforcement" off on my Win 10 system (but I got no error during driver install). After switching off "driver signature enforcement" and re-installed the adb and fastboot drivers, I got a warning that a driver without signature will be installed. I confirmed that warning and now fastboot is working well.
Hello, hopefully someone can help me.
I have the same problem as mentioned above. I also tried to deactivate driver signature and install new but it didn't work. Maybe I did it wrong.
I used this command and rebooted with deactivated driver signature.
shutdown.exe /r /o /f /t 00
I also tried to install specific adb drivers for xperia xz2c manually instead of universal adb drivers.
Any more ideas?
Thanks and regards
I'm facing the same problem. I've installed multiple adb drivers, with and without driver signature enforcement, and nothing works.
adb works fine, and device is listed, but as soon as I do an adb reboot bootloader, the device is gone. Also, for some reason, I do not see any cyan blue LED lighting up in my unit (the LED itself does work though).
Was able to fix it. The trick is to start the phone into fastboot (vol down+power), and then go to Device Manager and install the drivers from Sony on the recognized device.
a.bispo said:
Was able to fix it. The trick is to start the phone into fastboot (vol down+power), and then go to Device Manager and install the drivers from Sony on the recognized device.
Click to expand...
Click to collapse
Hi, a.bispo, do you have any link for these driver because I have tried several on sony website and none work for me.
Thank you,
I got them from Sony's website as well.
The trick was putting the phone into fastboot, letting Windows recognize it, and then manually install those drivers' files.
Just an update from my experience: I had to go into device manager and select an alternative driver for the Android! device that popped up. Not sure if this is mandatory or not but I did this after the fastboot devices step where my device isn't detected.