Related
Yesterday I purchased an ATT LG G2. Not content to leave anything alone, I rooted and installed recovery as soon as I got home. I used some unfamiliar techniques with this phone, but I assumed they were new.
Root - Towelroot
Recovery - AutoRec
I rebooted after installing towelroot and everything seemed fine. AutoRec seemed to install fine as well but later when I went to reboot problems arose.
I can't enter download mode. The phone is stuck in fastboot mode. In Windows it's recognized as an unknown Android device. Ubuntu/Knoppix do not recognize it at all. These two facts have prevent me from attempting many of the recovery methods available here on XDA.
I cannot enter recovery. Factory resetting does not work either, instead it dumps me right back into the fastboot mode.
Any advice? If I could at least get a machine to properly recognize the device I could attempt some of the recovery methods.
Some other interesting facts:
-Connected to Windows:
--Fastboot mode started
--udc_start()
--reset
--portcharge
--reset
--portcharge
-Connected to Linux (10.04 Ubuntu)
--Fastboot mode started
--udc_start()
--reset
--portcharge
--reset
--portcharge
--fastboot: processing commands
I have made several more attempts to install the drivers properly. None have been effective so far. My device is shown an "Android" with the yellow warning symbol when connected. I followed the supplementary instructions to choose the lgx64bus.inf. It provides many additional options however most of them do not work.
I had this problem;
Look through this thread.
http://forum.xda-developers.com/lg-g2/help/download-mode-t2818828
Unfortunately my problem is a little different. I cannot access recovery mode.
jconnell said:
Unfortunately my problem is a little different. I cannot access recovery mode.
Click to expand...
Click to collapse
1. download fastboot
2. downlaod laf.img, aboot.img, boot.img for your version (or just aboot.img and laf.img)
fastboot flash aboot aboot.img
fastboot flash laf laf.img
bender_007 said:
1. download fastboot
2. downlaod laf.img, aboot.img, boot.img for your version (or just aboot.img and laf.img)
fastboot flash aboot aboot.img
fastboot flash laf laf.img
Click to expand...
Click to collapse
I can't get my phone to communicate with any machine. Windows 7 / Ubuntu / Knoppix / Windows XP.
jconnell said:
I can't get my phone to communicate with any machine. Windows 7 / Ubuntu / Knoppix / Windows XP.
Click to expand...
Click to collapse
You stated this" In Windows it's recognized as an unknown Android "
So your device is communicating, you just need a method of communication.
try the above
Gabriel51 said:
You stated this" In Windows it's recognized as an unknown Android "
So your device is communicating, you just need a method of communication.
try the above
Click to expand...
Click to collapse
You're absolutely right. I suppose then that it's communicating improperly?
jconnell said:
You're absolutely right. I suppose then that it's communicating improperly?
Click to expand...
Click to collapse
It's an unrecognized connection, however there are other methods of connecting to your device such as the one bender_007 mentioned
jconnell said:
You're absolutely right. I suppose then that it's communicating improperly?
Click to expand...
Click to collapse
Ok, I've got few minutes free.
Can you install teamviewer and send me the details via pm ? I'll try to help you.
bender_007 said:
Ok, I've got few minutes free.
Can you install teamviewer and send me the details via pm ? I'll try to help you.
Click to expand...
Click to collapse
Team viewer is an excellent program, I use it often to help people with windows products.
I just used it a few minutes ago...
Here is the link to the download;
http://www.teamviewer.com/en/download/windows.aspx
bender_007 said:
Ok, I've got few minutes free.
Can you install teamviewer and send me the details via pm ? I'll try to help you.
Click to expand...
Click to collapse
I'm on a work computer right now. I can use it, but it may not be available for another 30 minutes or so. I work in the healthcare industry and I use the computer simultaneously for patient scan acquisition and personal use.
jconnell said:
I'm on a work computer right now. I can use it, but it may not be available for another 30 minutes or so. I work in the healthcare industry and I use the computer simultaneously for patient scan acquisition and personal use.
Click to expand...
Click to collapse
I'll be home in 2-3 hours. Then I'm free and can assist you.
bender_007 said:
I'll be home in 2-3 hours. Then I'm free and can assist you.
Click to expand...
Click to collapse
Reading this makes me glad I'm retired!
bender_007 said:
I'll be home in 2-3 hours. Then I'm free and can assist you.
Click to expand...
Click to collapse
I sincerely appreciate the help.
As an aside, when I try to communicate with the phone via fastboot, it hangs on <waiting for device> indefinitely.
jconnell said:
I sincerely appreciate the help.
As an aside, when I try to communicate with the phone via fastboot, it hangs on <waiting for device> indefinitely.
Click to expand...
Click to collapse
It's drivers 99% ..the only thing that actually is weird that ubuntu doesn't recognize it(fastboot part..)
ok, let's do it
Ok, we fixed the dload mode.
If someone is free to guide him with the tot flashing(never needed to flash tot file, I use kdz)
bender_007 said:
It's drivers 99% ..the only thing that actually is weird that ubuntu doesn't recognize it(fastboot part..)
ok, let's do it
Ok, we fixed the dload mode.
If someone is free to guide him with the tot flashing(never needed to flash tot file, I use kdz)
Click to expand...
Click to collapse
Thanks to the kindness of Bender_007, I now have download mode again.
I'm attempting to revert to stock using the TOT method and the LGFlashTool. I'm getting some errors from the flashing tool.
"Model Information Check Fail"
I've doubled checked that I'm using the right TOT and DLL with no luck. Any ideas?
jconnell said:
Thanks to the kindness of Bender_007, I now have download mode again.
I'm attempting to revert to stock using the TOT method and the LGFlashTool. I'm getting some errors from the flashing tool.
"Model Information Check Fail"
I've doubled checked that I'm using the right TOT and DLL with no luck. Any ideas?
Click to expand...
Click to collapse
It does sound like you have the wrong tot or/and dll file but could simply be a fubared usb port?
Are you plugged directly into your computer and not a hub>?
Gabriel51 said:
It does sound like you have the wrong tot or/and dll file but could simply be a fubared usb port?
Are you plugged directly into your computer and not a hub>?
Click to expand...
Click to collapse
I'm using a new MBPr running W7 in a bootcamp partition. I've tried using both of the available USB ports. I've downloaded the TOT file twice and I've tried it from two different external sources (Thumdrive, USB3 External). No luck from either. There's no room left on the bootcamp partition so I have to use an external source.
I'm certain I have a D800, also confirmed by bender_007. I'm also certain I'm using the correct DLL and TOT. I've also tried twly.o different cables.
The only thing I can think of are that some of the drivers installed when I was working with bender_007 are interfering with the drivers. I need to be using. I'll try that now actually...
jconnell said:
I'm using a new MBPr running W7 in a bootcamp partition. I've tried using both of the available USB ports. I've downloaded the TOT file twice and I've tried it from two different external sources (Thumdrive, USB3 External). No luck from either. There's no room left on the bootcamp partition so I have to use an external source.
I'm certain I have a D800, also confirmed by bender_007. I'm also certain I'm using the correct DLL and TOT. I've also tried twly.o different cables.
The only thing I can think of are that some of the drivers installed when I was working with bender_007 are interfering with the drivers. I need to be using. I'll try that now actually...
Click to expand...
Click to collapse
I see it's a Mac, I know nothing about those even though you are running W7, the driver interface has to be different for Mac peripherals
Not working anymore.
Sorry.
Do you mean that you had your old tablet already killed, and then you recovered it following these steps?
You can see it here, in my Twitter
https://twitter.com/victorcangil16/status/642389331768942592
Can anyone confirm this on a separate dead tablet? if so its a pretty damn good find.
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
jo2e said:
Hi Victorcangil 16,
Could you exactly discribe how did you make this miracle (which drivers...) ?
Thanks
Click to expand...
Click to collapse
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Victorcangil 16 said:
I used Windows 10 with the NVIDIA Family USB Drivers. I made the process I described in the first post
Click to expand...
Click to collapse
Ok,
Thx for your reply Victorcangil 16.
But how did your device was recognized by windows before done this process ? APX or something else
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Victorcangil 16 said:
It was reconized as normal device by Windows, like if I plug my phone to the PC. And the drivers I had to configure them manually, if not, It gives me error when doing FastBoot
Click to expand...
Click to collapse
It stay on :"<waiting for device>"
And my tablet is not reconized as normal device but as "APX"
What does APX mean?
Change the ADB drivers interface using the next process:
Search in Windows: Device Manager
If the ADB interface has a Yellow alert, Right Click, Update Drivers, Select from Computer, Use Disk, Use all, and then select the file in the NVIDIA Drivers folder (in my case, Downloads). Accept,
Victorcangil 16 said:
What does APX mean?
Click to expand...
Click to collapse
I don't known. My tablet appears like that in the peripherics manager ...
If you hace skype, I can help you easily
Victorcangil 16 said:
If you hace skype, I can help you easily
Click to expand...
Click to collapse
Yes i have skype.
But i think i got the problem : my tablet wasn't rooted and the bootloader was locked...
I think you saved your shield because it was rooted...
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Victorcangil 16 said:
I thinks is that. If is has not unlocked bootloader, you can't change nothing. But to unlock it, just type in Fastboot: "fastboot oem unlock" (tablet will Factory Reset)
Click to expand...
Click to collapse
Same thing with this command : <waiting for device>
:/ I think something is going on with Drivers
Hi, one question for such kind of reactivation - root is required ?
Yes, Root and Unlocked Bootloader are required ro recover the "killed" Tablet
Just bought by mistake deactivated Shield...is it possible to make root via fastboot ?
Hi!
First of all, I'm sorry for my English...
I have unlocked and rooted my device (Huawei P9 lite).
I have install the TWRP bootloader and I tried to install a new costum ROM, but my device was turned off and never opened again. (Maybe: Low battery).
I try to charge my device but it didn't recognize the charger. So, I removed the battery from device (with the help of a technician) and charging it.
After all, I tried again to root and install TWRP but the device doesn't open or recognized of my PC...the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
What am I doing?
First of all....
What exactly did you try to flash? Which "custom ROM" are you talking about?
Schlengge said:
First of all....
What exactly did you try to flash? Which "custom ROM" are you talking about?
Click to expand...
Click to collapse
I download the costum ROM from here: http://forum.xda-developers.com/huawei-p9lite/development/dev-cyanogenmod-13-huawei-p9-lite-t3465612
Use <[DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim> and try again to da all from begining...
- check bootloader - lock/unlock
- flash stock recovery/twrp
- root it if is necessary
- copy update.app to SDcard into dload folder and try to reflash device.
I tired... but it didn't recognized my device!
Vangeliskar1 said:
I download the costum ROM from here: http://forum.xda-developers.com/huawei-p9lite/development/dev-cyanogenmod-13-huawei-p9-lite-t3465612
Click to expand...
Click to collapse
Okay so that is interesting.
Have you followed the exact instruction on the Website of Meticulus?
The CM Rom is HIGHLY alpha and cannot be flashed without a strict preparation.
Are you able to boot your phone into fastboot mode?
Schlengge said:
Okay so that is interesting.
Have you followed the exact instruction on the Website of Meticulus?
The CM Rom is HIGHLY alpha and cannot be flashed without a strict preparation.
Are you able to boot your phone into fastboot mode?
Click to expand...
Click to collapse
No...
I can't!
It doesn't work (Volume down + power key)
Vangeliskar1 said:
No...
I can't!
It doesn't work (Volume down + power key)
Click to expand...
Click to collapse
So the device does not respond in any way?
Hmm...
Maybe refer to the CM thread and hope that someone there can help you.
Don't know if Meticulus checks out this forum section.
You said: the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
So, the device is recognized by PC in fastboot mode or not?
gtdaniel said:
You said: the only thing to do is to be recognized by the PC in fastboot mode but not allowing me to do something in the command window.
So, the device is recognized by PC in fastboot mode or not?
Click to expand...
Click to collapse
Maybe...I don't know!
I have this message:
C:\adb>fastboot devices
9JT0216627000650 fastboot
C:\adb>
Ok. Try to use this tool [DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim>
And tell here what appears to work or not...
gtdaniel said:
Ok. Try to use this tool [DEV] VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim>
And tell here what appears to work or not...
Click to expand...
Click to collapse
I had tried bu it doesn't work...
I have this massage:
Drivers on PC are installed right? Just to make sure...
May be I'm wrong, there is two options to active in develloper menu ? USB debug and OEM I don't know why ?
Excuse me if I'm off topic.
Schlengge said:
Drivers on PC are installed right? Just to make sure...
Click to expand...
Click to collapse
Yes everything is allright!
I have install and Hi suite!
Phone have any control? Reboot? Power?
When you conected to PC at Devices on PC appear something?
No...it is dead....
On PC: yes! It is apeared to devices
Ok! If appear in Devices is a chance to get it back to life...
It should be recognized in fastboot mode to... (where appears with serial number).
In that stage try that tool to see if is any information visible in status (model, serial number, build number etc)
gtdaniel said:
Ok! If appear in Devices is a chance to get it back to life...
It should be recognized in fastboot mode to... (where appears with serial number).
In that stage try that tool to see if is any information visible in status (model, serial number, build number etc)
Click to expand...
Click to collapse
It is apeared at devices with that name: android Bootloader Interface
Tool?
Which tooL?
In comand window?
That tool: VNS-L21-L22-L31 [EUROPE] Toolkit [0.0.0.8] Bootloader/Recovery/Root/Dual-Sim
You attached a image with phone in fastboot mode. Can you replicate again that stage?
In that stage use that tool and see if phone appear there.
Hey guys i just updated to firmware 327 from 326.. I am using fully stock rom with locked bootloader.. I wanted to unlock bootloader but was unable to do so.. Whenever I try to run the unlock.bat file the black cmd screen remains stuck and nothing happens.. Plz help me i wanna try few roms so help me to unlock bootloader (6gb variant)
Is this because of the latest firmware??
Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your
andriyhar said:
Hi.
Link for official unlock tools
Look on the Driver & Tools
Version UnlockTool 2018/05/04548.6 KBytes
Unlock Device App: Unlock boot loader
Notice:
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App,
including but not limited to the following: once you activate the App you will not be able to recover your
Click to expand...
Click to collapse
Bro official unlocking method will void warranty even after i relock my bootloader later right? So i wanna do it the unofficial way so i can relock bootloader and go back to stock if I wish and would get ota updates
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
Yes it's detected.. Bt the black cmd screen gets stuck while unlocking
Any solution guys plz need help
try using cmd prompt in administrator mode....
ujilraj said:
try using cmd prompt in administrator mode....
Click to expand...
Click to collapse
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/
Well, I am not an expert in this. It should just work. And the Windows 10 thing is absurd. I am using Windows 10. Plus, development mode is not enabled in my laptop.
Credits to the following -
@Sudeep Duhoon for this guide - [UNLOCK/RELOCK] Bootloader Unofficailly and Flash TWRP+Root
ASUS for phone, drivers, rom, this and that
Mod edit. Link removed. Reference: https://forum.xda-developers.com/one...rward-t3765018
@Saktis_STi for raw factory rom
@Shivam Kumar Jha for fixing the script
@Sujeet Ranipa for drivers link
@esashwin for testing
Use unlock.sh instead of unlock.cmd
If the phone is indeed detected in fastboot mode using
Code:
fastboot devices
, try running the script from unlock.sh instead of unlock.cmd.
I have not been unable to flash fastboot stock ROM from this laptop using the .bat file but for some reason, .sh file works fine.
Just install Git on windows. It will give you a wrapper to run shell scripts on your windows machine (Git BASH).
Again, I am not an expert. This might not work but at least it won't corrupt anything.
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
_uchihaitachi_ said:
Tried already bro nothing works i read somewhere that windows 10 have issues to unlock bootloader and everything works fine with windows 7.. But this thing doesn't make any sense according to me :/
Click to expand...
Click to collapse
Try anyother pc
Many users solved unlock problems by changing pc
yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
Ok bro thanks for help.. Will try on another pc coz my pc has only 3.0 and 3.1 ports ?
iamfarhanansari said:
Try anyother pc
Many users solved unlock problems by changing pc
Click to expand...
Click to collapse
Ok bro thanks for help
Phone is not detected.
baunthiyal said:
I unlocked my boooader after updating to 327.
Is your phone detected in Fastboot mode?
Click to expand...
Click to collapse
I have this same issue my phone is not detected.
Please help.
I too have same problem
C:\>cd unlock
C:\unlock>fastboot devices
J7AAGF02D693CWW fastboot
C:\unlock>unlock
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
Solution to unlocking bootloader where screen blacks out on flashing
yuvatheja said:
This happened to me as well, its problem with your pc(i mean drivers or just your os or maybe the usb ports, use 2.0 ports preferably) i have two pcs with windows 10 installed in both. One is updated and the other outdated. It failed in my updated pc, tried all methods like install, uninstall drivers, disabled driver signing, used different cables, used different usb ports 3.0, 2.0 but nothing worked. Atlast i gave it a try with my outdated windows 10 pc. It worked liked a charm. It has something to do with the drivers i suppose. Try in a different pc it might just work right for u as well
Click to expand...
Click to collapse
I had the same issue, after reading to many webpages, stumbled on this official unlock tool apk. Once the bootloader is unlocked using the app, the phone reboots into ASUS UNLOCK MODE with device status as unlocked and message to restart the phone. Heres the catch this is already the fastboot mode so flash TWRP at this stage. If you restart the phone in fastboot before flashing twrp, on running the flash cmd the screen of your phone would black out with a message "press any key to shutdown". Hope this helps.
unlock tool apk
then how do I install that official unlock tool in fastboot mode. since I can only access CSC FASTBOOT MODE.
I'm trying to get this bootloader unlocked and haveing one heck of a time getting my Windows 10 Pro machine to pull anything for fastboot devices.
Nothing shows. I have the latest drivers installed, as well as the latest SDK. I have OEM Unlocking in Dev Options on the phone.
Any ideas?
even tried
fastboot -i 0x2e17 devices
when i had the google drives installed fir the device, it showed, but not with the official drivers.
and... using
fastboot -i 0x2e17 flashing unlock (or unlock_critical) showed only the fastboot help information...
kevp75 said:
even tried
fastboot -i 0x2e17 devices
when i had the google drives installed fir the device, it showed, but not with the official drivers.
and... using
fastboot -i 0x2e17 flashing unlock (or unlock_critical) showed only the fastboot help information...
Click to expand...
Click to collapse
From command line
Phone in bootloader
Type fastboot --version
And see if the path is pointing to the essential drivers folder on C
Sent from my PH-1 using Tapatalk
clsA said:
From command line
Phone in bootloader
Type fastboot --version
And see if the path is pointing to the essential drivers folder on C
Click to expand...
Click to collapse
ill do that once im back on my windows machine tomorrow.... in the meantime, worked perfect on my linux box
clsA said:
From command line
Phone in bootloader
Type fastboot --version
And see if the path is pointing to the essential drivers folder on C
Sent from my PH-1 using Tapatalk
Click to expand...
Click to collapse
Oddly enough it shows as 'unrecognized option'
I set the path to my C:\adb folder which is where I put the latest platform tools from google.
I'm only slightly concerned, so it's not that big of a deal... I do have my linux box that has no issues... this is more of a convinience issue that anything else.
kevp75 said:
Oddly enough it shows as 'unrecognized option'
I set the path to my C:\adb folder which is where I put the latest platform tools from google.
I'm only slightly concerned, so it's not that big of a deal... I do have my linux box that has no issues... this is more of a convinience issue that anything else.
Click to expand...
Click to collapse
I'll bet you $5 you have a dodgy cord. I say this because I had all sorts of problems the first few days I had this phone until I purchased a good USB C 3.1.0 cord.
swiftbones74 said:
I'll bet you $5 you have a dodgy cord. I say this because I had all sorts of problems the first few days I had this phone until I purchased a good USB C 3.1.0 cord.
Click to expand...
Click to collapse
Thought that too. Replaced with 3rd party cord, same issue. Still no issue with either cord on Linux box
kevp75 said:
Thought that too. Replaced with 3rd party cord, same issue. Still no issue with either cord on Linux box
Click to expand...
Click to collapse
Well I guess I owe you $5.
swiftbones74 said:
Well I guess I owe you $5.
Click to expand...
Click to collapse
LMFAO
What you said is common. I had it happen to me on my S7 Edge, and my Honor View 10, so ...