Nexus 5 Stuck in bootanimation with flying dots (No usb debugging)
Hi,
I have this nexus 5 which was not rooted, the usb debugging option is off and the bootloader is in locked state as nothing has been done on it in the past.
The phone is stuck on flying dots animation. I have tried various methods but all require usb debugging to be on. How can I go back to stock without having to turn usb debug option on? I have seen some mentions of fast oem unlock, but how do I do that?
Thanks!
The first thing you do is go here and look for how to return to stock, http://forum.xda-developers.com/showthread.php?p=53439068. Then remember this thread because it had everything you'll ever need.
Sent from my Nexus 9 using XDA Free mobile app
buhnanafone said:
Hi,
I have this nexus 5 which was not rooted, the usb debugging option is off and the bootloader is in locked state as nothing has been done on it in the past.
The phone is stuck on flying dots animation. I have tried various methods but all require usb debugging to be on. How can I go back to stock without having to turn usb debug option on? I have seen some mentions of fast oem unlock, but how do I do that?
Thanks!
Click to expand...
Click to collapse
+1
jd1639 said:
The first thing you do is go here and look for how to return to stock, http://forum.xda-developers.com/showthread.php?p=53439068. Then remember this thread because it had everything you'll ever need.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Hey man thanks, I have seen that but again it requires usb debugging. However I did find this program that unlocks bootloader WITHOUT usb debugging on!!!! It's called Unlockmybootloader v2 by yashade2001. Now I can continue my journey onto trying to return to stock! Wish me luck :fingers-crossed:
buhnanafone said:
Hey man thanks, I have seen that but again it requires usb debugging. However I did find this program that unlocks bootloader WITHOUT usb debugging on!!!! It's called Unlockmybootloader v2 by yashade2001. Now I can continue my journey onto trying to return to stock! Wish me luck :fingers-crossed:
Click to expand...
Click to collapse
You do not need usb debugging enabled to use fastboot. To unlock the bootloader all you need to do is have fastboot instated on your pc, then boot into the bootloader and run the command fastboot oem unlock. I highly encourage you do read the thread I linked you to and learn about your device. There's a lot there so focus on how to return your device to stock and how to unlock the bootloader, root and flash a rom. You'll thank me in the long run
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You do not need usb debugging enabled to use fastboot. To unlock the bootloader all you need to do is have fastboot instated on your pc, then boot into the bootloader and run the command fastboot oem unlock. I highly encourage you do read the thread I linked you to and learn about your device. There's a lot there so focus on how to trying your device to stock and how to unlock the bootloader, root and flash a rom. You'll thank me in the long run
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I have tried cmd prompt fastboot oem unlock before with fastboot installed, it didn't work. And even for that it said usb debugging must be on. Also new problem persists, flash-all.bat file to flash factory images is giving me error such as
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1046364912 bytes
error: update package missing system.img
buhnanafone said:
I have tried cmd prompt fastboot oem unlock before with fastboot installed, it didn't work. And even for that it said usb debugging must be on. Also new problem persists, flash-all.bat file to flash factory images is giving me error such as
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 1046364912 bytes
error: update package missing system.img
Click to expand...
Click to collapse
Alright, first Google 15 second adb install xda. That'll setup fastboot and adb on your pc and make it so you don't need to worry about what directory your running fastboot from.
Then, in the thread I linked you to look for how to return to stock and follow method 2, the long method. Flash-all.bat doesn't work almost all the time.
Don't worry about the *.sig errors. Those are normal.
Sent from my Nexus 5 using XDA Free mobile app
Here is your solution: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
eross said:
Here is your solution: http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
Click to expand...
Click to collapse
Man, that's a lot of messing around when the first step should be trying to flash the factory images. Then, maybe trying to fix the persist partition. And you're fix requires usb debugging enabled which the op doesn't have.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Man, that's a lot of messing around when the first step should be trying to flash the factory images. Then, maybe trying to fix the persist partition. And you're fix requires usb debugging enabled which the op doesn't have.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
That is why you first flash Android 4.4. It will boot with a corrupted persist partition, enough to enable usb debugging.
Yeah but prob no need for all that
Sent from my Nexus 5 using Tapatalk
ldubs said:
Yeah but prob no need for all that
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It was for me and quite a few others..... Nothing to lose by trying.
buhnanafone said:
Hey man thanks, I have seen that but again it requires usb debugging. However I did find this program that unlocks bootloader WITHOUT usb debugging on!!!!
Click to expand...
Click to collapse
I started and restarted a reply to this post but I'm just baffled. I'll just say that you don't understand USB debugging at all.
Yeah, bootloader has nothing to do with usb debugging. In order to fix persist partition, you need adb, which requires usb debugging, which can only be enabled from a working OS (AFAIK).
Related
Hi,
Sorry if this is a silly question I'm relatively new to android but after rooting and flashing Cyanogenmod on my Nexus 5, it doesn't come up every time I use the adb devices command. Did I do something wrong?
loolnicetry said:
Hi,
Sorry if this is a silly question I'm relatively new to android but after rooting and flashing Cyanogenmod on my Nexus 5, it doesn't come up every time I use the adb devices command. Did I do something wrong?
Click to expand...
Click to collapse
Are you sure you have USB debugging enabled?
kilometers4 said:
Are you sure you have USB debugging enabled?
Click to expand...
Click to collapse
Oh wow, I'm guessing the root completely wiped my settings, thank you!
Also switch from media to camera mode and you will see your device
Sent from my Nexus 5 using XDA Premium 4 mobile app
FYI I'm getting this same problem with my Nexus 5 after the OTA 4.2.2 update. I have re-rooted and tried a bunch of stuff to make this work. It was working before. I enable USB debugging, switch to camera mode, run "adb devices" on my Arch Linux 3.12.5 host, am asked to allow computer with RSA key BLAH:BLAH:BLAH and get back a listing showing no devices. If I don't accept the computer's key fast enough I get back a listing saying "DEVICE_ID_HERE unauthorized".
hey guys i got my nexus 5 yesterday and i wanted to root it . so i downloaded toolkit and installed everything . but whe i tried to unlock the phone it said it couldnt find the adb . so i followed the guid and i did everything by the book and in device manager it recognized it as a samsung android phone > google nexus adb interface . so i retried the unlock a few times and i got nothing again .
if anyone can help me it would be great .
if you need more info just ask
I've had good luck with the android nacked usb drivers, Google them. Then follow this guide http://forum.xda-developers.com/showthread.php?p=47025283
jd1639 said:
I've had good luck with the android nacked usb drivers, Google them. Then follow this guide http://forum.xda-developers.com/showthread.php?p=47025283
Click to expand...
Click to collapse
how do i install them ?
danielbr14 said:
how do i install them ?
Click to expand...
Click to collapse
In Windows device manger you probably have a usb port when an "!" On it. Right click it then manual install the usb drivers. You'll have to browes to whet you downloaded the drivers
jd1639 said:
In Windows device manger you probably have a usb port when an "!" On it. Right click it then manual install the usb drivers. You'll have to browes to whet you downloaded the drivers
Click to expand...
Click to collapse
it said that the drivers are already installed so what should i do now ?
danielbr14 said:
it said that the drivers are already installed so what should i do now ?
Click to expand...
Click to collapse
Google "nexus 5 diagnosing usb drivers xda"
why use a toolkit on a nexus device? its easier to root your nexus without a toolkit.
1. "fastboot oem unlock" via fastboot unlocks the bootloader.
2. flash a custom recovery via fastboot
3. flash the su binaries(supersu) in your new recovery.
4. reboot and profit, thats it.
danielbr14 said:
hey guys i got my nexus 5 yesterday and i wanted to root it . so i downloaded toolkit and installed everything . but whe i tried to unlock the phone it said it couldnt find the adb . so i followed the guid and i did everything by the book and in device manager it recognized it as a samsung android phone > google nexus adb interface . so i retried the unlock a few times and i got nothing again .
if anyone can help me it would be great .
if you need more info just ask
Click to expand...
Click to collapse
I used this...http://www.youtube.com/watch?v=KnlUdjUaD3Q
and this....http://www.wugfresh.com/nrt/
with zero issues
P.s.
I was a first time noob.
simms22 said:
why use a toolkit on a nexus device? its easier to root your nexus without a toolkit.
1. "fastboot oem unlock" via fastboot unlocks the bootloader.
2. flash a custom recovery via fastboot
3. flash the su binaries(supersu) in your new recovery.
4. reboot and profit, thats it.
Click to expand...
Click to collapse
might want to add after you unlock the bootloader to boot into the device once.
jd1639 said:
Google "nexus 5 diagnosing usb drivers xda"
Click to expand...
Click to collapse
i still can find a good answer on how to solve my problem.
danielbr14 said:
i still can find a good answer on how to solve my problem.
Click to expand...
Click to collapse
Do you have usb debugging enabled in developer options on your phone?
jd1639 said:
Do you have usb debugging enabled in developer options on your phone?
Click to expand...
Click to collapse
yes i do .
Zepius said:
might want to add after you unlock the bootloader to boot into the device once.
Click to expand...
Click to collapse
why? i didnt. my nexus 5 never ever booted up stock. before i ever booted it, it got unlocked and flashed first.
simms22 said:
why? i didnt. my nexus 5 never ever booted up stock. before i ever booted it, it got unlocked and flashed first.
Click to expand...
Click to collapse
what does it have to do with anything ??
danielbr14 said:
what does it have to do with anything ??
Click to expand...
Click to collapse
You're probably going to have to go into device manager, view hidden, and delete each usb port that is not being used and start over. Don't have your phone connected when you do this. It's a pita. Then reboot your computer, than plug your phone in. Also make sure you're using the usb cable that came with your phone and usb ports in the back of your pc
simms22 said:
why? i didnt. my nexus 5 never ever booted up stock. before i ever booted it, it got unlocked and flashed first.
Click to expand...
Click to collapse
some people have reported issues if you didnt let the device 'reset' itself after you unlocked the bootloader so it could rebuild the data partition.
its more of a precautionary thing than anything else.
jd1639 said:
You're probably going to have to go into device manager, view hidden, and delete each usb port that is not being used and start over. Don't have your phone connected when you do this. It's a pita. Then reboot your computer, than plug your phone in. Also make sure you're using the usb cable that came with your phone and usb ports in the back of your pc
Click to expand...
Click to collapse
you mean uninstall everything in the universal serial bu controller tree ?
danielbr14 said:
you mean uninstall everything in the universal serial bu controller tree ?
Click to expand...
Click to collapse
Yep, that's not currently being used. You don't want to lose your keyboard, etc.
jd1639 said:
Yep, that's not currently being used. You don't want to lose your keyboard, etc.
Click to expand...
Click to collapse
i dont know how to find wich one is in use and wich one isnt.
danielbr14 said:
i dont know how to find wich one is in use and wich one isnt.
Click to expand...
Click to collapse
The ones that are grayed out are not in use the darker ones are
Long story short, installed clockwork mod recovery in attempt to install a cyanogen nightly. I stupidly formatted everything including data and SYSTEM! Now I can only boot to recovery. When I plug the nexus into any PC it's not picked up as an unidentified piece of hardware on windows so I can't push another rom or adb sideline commands result in "waiting for device". Any suggestions? Should I attempt to RMA?
Reinstall drivers. Boot into the bootloader and flash the factory image.
El Daddy said:
Reinstall drivers. Boot into the bootloader and flash the factory image.
Click to expand...
Click to collapse
Thank you!! I never used the USB cable that actually came with the NEXUS until just now, the PC finally detected the phone as i was in the Bootloader and start automatically Download and Writing, rebooting itself and looks like it's booting up. Thanks again. Very quick response.
I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???
Check USB drivers. Might not be working
Sent from my Nexus 5 using Tapatalk
wltnkyl said:
I accidentally formatted system as well, slip of the finger. I am unable to get my computer to recognize my device, "fastboot devices" lists nothing. Have tried flashing factory software, but it just says "waiting for device". Any suggestions???
Click to expand...
Click to collapse
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.
bitdomo said:
If you are on windows 8 or 8.1 you have turn of driver signiture enforecment. http://sixcolumns.com/how-to-disable-and-bypass-driver-signature-enforcement-in-windows-8/
To make adb works when you are in recovery you need the naked usb drivers. Turn on sideload in the recovery and on a cmd type this: adb sideload path_to_your_rom_file.zip end hit enter.
Click to expand...
Click to collapse
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!
wltnkyl said:
Thank you so much!! Unfortunately I am only able to hit the THANKS button once. I thought for sure that it was done for!
I have bricked my phone before, but have always been able to find a workaround. This time, not so much.
Again, Thank You!!
Click to expand...
Click to collapse
you can also try unlock bootloader, flash factory images. and bumm your phone works again.
install fastboot and etc... http://forum.xda-developers.com/showthread.php?t=2588979
guide to return stock http://forum.xda-developers.com/showthread.php?t=2513701
Oh and send me an e-mail: [email protected] then I will instruct you to downlaod teamviewer, so I could resolve your driver problems
You should give wag tool a try it completely brings you back to stock
Sent from my Nexus 5 using XDA Premium 4 mobile app
I can't get my droid ultra to be recognized other than offline and can't flash it back to try the root method it says i need the fastboot o bake driver .RSD lite doesn't recoginze it in fastboot can anyone suggest a fix i have installed moto device manager 5 times each differet downloads
If I boot it up in bp mode red lite see the phone until it reboots to fastboot the it says it didn't switch modes but it seems to
Sent from my XT1080 using XDA Premium 4 mobile app
Make sure USB debug is enabled. Make sure the phone is not on the lock screen while plugged in. Unplug and replug the device. Restart the adb service (adb kill-server, then adb start-server).
These are the easiest things to try that come to mind.
Debugging is on ,lockscreen is not on . unplugged my phone and killed and restarted the server and still showing offline. Just used the same computer to unlock a HTC droid incredible 2 today and restore a lg optimus elite from a bootloop cycle. So I am pretty sure its not a issue with the computer I am using ,but I guess its time to try another computer and see if it changes anything. Any ideas or help is much appreciated and thanks nimdae for the input
Sent from my XT1080 using XDA Premium 4 mobile app
Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app
akellar said:
Make sure you have updated adb to the latest
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Glad you mentioned that has been quite some time since I updated it. Will get it done when this lg p930 is finished and be back .with good news I hope
Sent from my XT1080 using XDA Premium 4 mobile app
Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.
kcipopnevets said:
Yes, if it reports offline, then you don't have ADB 1.0.31. Type "adb version" and make sure it's 1.0.31.
Click to expand...
Click to collapse
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app
dogie425 said:
OK your right . how do I get the new one download it from the android SDK website? Well that's what I'm going to do tonight thanks all for the great help
Sent from my XT1080 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You should be able to update the tools through the manager, though I've been having trouble using the latest manager myself (it doesn't load). Otherwise, you can go to dev.android.com and download the latest package which includes the tools.
Got the new version install . and I plan to flash back to 4.4 version 19.5.3 for my phone. RSD lite is still not detecting the phone when it switches to fastboot so that brought up the question in my mind do I need to update fastboot or was this done when I updated the adb and is there anything else I might be forgetting to do b4 I start this since I will be using the manual method to flash this in fastboot? Any and all feedback is greatly appreciated. This is my everyday driver and I'm still paying for it thru the edge plan.
Sent from my XT1080 using XDA Premium 4 mobile app
Have you tried putting your phone in fastboot mode then connecting it to pc
TRIED Flashing thru fast boot
so i got the nerve to try downgrading my ultra with fastboot since rsd won't detect my phone when it switches to fastboot using this tutorial http://forum.xda-developers.com/showthread.php?t=2580060 all went well except on the mfastboot command i got this responce
C:\ANDROID PWNAGE\adt-bundle-windows-x86_64-20130917\adt-bundle-windows-x86_64-2
0140321\sdk\platform-tools>mfastboot flash system system.img
(bootloader) Variable not supported!
target max-download-size: 768MB
sending 'system' (574208 KB)...
OKAY [ 36.243s]
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 59.547s
and it said on the screen mfastboot error invalid piv image size for system
now the phone won't boot just jumps right back to the bootloader screen
tried it 2 more times and still no joy same out come so what do i do now? download the file again and try once more . and do i need to repeat all the steps b4 this command or will just running this command alone be fine to fix me HELP pls
Lordomn said:
Have you tried putting your phone in fastboot mode then connecting it to pc
Click to expand...
Click to collapse
yes i tried that but found out my adb was an older version and need to be updated its seeing the phone fine now. just have to figure out my latest problem
GOOD NEWS i unzipped a second download i had in my downloads folder and used that system img file to try flashing and it when through. phone is rebooting now. time to clam down and try me some pie in a bit
(thanks jcase for the pie)
You need to update your adb and fastboot files if your devices is shown as offline...
joel_sinbad said:
You need to update your adb and fastboot files if your devices is shown as offline...
Click to expand...
Click to collapse
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app
akellar said:
Pretty sure we established that roughly 3 weeks ago
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Lol
usb debugging is not necessary for fastboot commands, only ADB; however, it sounds to me like you do not have the proper drivers installed for the device if RSD is not detecting it. I would delete all Motorola drivers and Motorola Device manager, reboot computer with device unplugged, reinstall Device Manager, and then connect device. You can also download Minimal ADB and Fastboot (Google search) and it is a lot less hassle than trying to use the SDK.
You may also try using a different USB cable on a different USB port (not USB 3.0). Sometimes that causes problems.
In the end my problem was my SDK was not updated ,so the device was only seen as offline as for why rsd doesn't detect it in fastboot I do not know ,but I was able to manually flash it in the end. Now I'm loving w/p off and root with safe strap installed despite the locked bl
Sent from my XT1080 using XDA Premium 4 mobile app
Warning: This will delete all your data. You'll also see a large warning every time you turn on the device (attached), this disappears in less than a second.
Turn on developer mode
Turn on OEM unlock and USB debugging
Install LG drivers
Windows: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425
Mac: http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00320110909
Type adb devices and authorize your computer on the phone
Type adb reboot bootloader
Type fastboot devices and make sure your phone shows up
Type fastboot oem unlock
Type fastboot getvar all
Should say (bootloader) unlocked:yes
Type fastboot reboot
What's the purpose for an Unlock bootloader?
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
bhagiratha said:
What's the purpose for an Unlock bootloader?
Click to expand...
Click to collapse
At this point, nothing. It's a prelude to rooting.
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
Try fastboot devices and reinserting the usb cable. Doesn't make sense that adb sees it but fastboot does not unless it's a different driver. I think fastboot driver differs actually so do that driver too.
Ubuntu
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
You can also load Ubuntu on a flash drive and boot your computer from the flash drive. Then run the commands.
https://www.ubuntu.com/
Cheers
heldc said:
When I type in fastboot oem unlock, I get < waiting for any device >
And it waits, forever. (well, ok, like 15 minutes until I get impatient and pull the battery)
I'm on windows 10, installed the drivers from this post. When I check the device manage, the phone is listed as Android Bootloader Interface. I try updating the drivers by pointing it to the LG drivers folder, it says drivers are up to date. I've got ADB and OEM unlock both enabled in developer options. I've tried the phone on different USB ports, the cable works fine when the phone is booted normally, I've tried launching minimal adb&fastboot as admin and regular. What am I missing/doing wrong?
Click to expand...
Click to collapse
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
cordell12 said:
ADB reboot bootloader boots straight into the OS on AT&T v20 :crying:
Click to expand...
Click to collapse
Do you guys have the oem unlock option at least?
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
wing_addict_usa said:
Do you guys have the oem unlock option at least?
Click to expand...
Click to collapse
yup, even warns us that certain things won't work if we enable it. adb works just fine too
cordell12 said:
yup, even warns us that certain things won't work if we enable it. adb works just fine too
Click to expand...
Click to collapse
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
wing_addict_usa said:
It's the first step to rooting. If you plan to root, wiping your data now may be preferable.
Click to expand...
Click to collapse
It's quite possible the process of rooting will wipe the phone anyway.
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Click to expand...
Click to collapse
power device off, hold volume up and keep it down and plug in USB cord while it's connected to PC. I tried fastboot from download mode though. the logs do look interesting, wonder what a T-MOBILE device says
Double0EK said:
First be on your c:\
Type in adb devices
If your phones serial comes up type in..
Adb reboot bootloader
Then
Fastboot oem unlock
Click to expand...
Click to collapse
Yup, I did that. And then I get an error. Well, not an error, just a lack of response. fastboot devices returns nothing. I'm currently downloading the full sdk, on the theory that perhaps it's a problem with the installation of 'minimal adb and fastboot' I have.
---------- Post added at 08:07 PM ---------- Previous post was at 07:36 PM ----------
manufan721 said:
Also what helped me was downloading android studio with the sdk.. It installs android drivers which were necessary for me at least to get past the waiting for device message, windows located the drivers on my c drive and boom... Unlocked Bootloader.. Just saying
Sent from my LG-H918 using XDA-Developers mobile app
Click to expand...
Click to collapse
Did you do anything specific after installing Android Studio to get it to install the drivers? Cos I've installed Android Studio, but am still having the same problem-fastboot devices returns nothing, and fastboot oem unlock hangs on <waiting for device>. I went into device manager and had it search the entire C: for drivers for the android bootloader interface, and it gave the same 'already up to date drivers' message as before I installed Android Studio.
EDIT- Even after installing the Google usb driver, no luck. Giving up for the weekend.
I'm a newbie, may I know have to fastboot from download mode?
having same issue just hangs at Fastboot oem unlock if anybody can help thanks in advance
twistedvip said:
Yeah I am really curious if there may still be a way to unlock the bootloader with out AT&T variant. I wish I kept my phone on the Download Mode when I had gotten into it because I wanted to see if by any chance that might actually get fastboot to read the phone..
I'm curious if there's anyone with a T-Mobile variant that has their bootloader unlocked and wants to view their debug logs (specifically last_log/last_kmsg). As I was looking through mine and tried to boot into bootloader these lines were the only things I saw that might have interested me at all. I'm just curious on what the values are on their phone.
Code:
last_log
[ 0.711419] ro.boot.flash.locked=1
[ 0.711784] ro.bootloader=unknown
[ 0.711817] ro.oem_unlock_supported=1
last_kmsg
<6>[ 1.077087 / 01-01 00:00:01.069][3] [70] SW3800_Authentication [vendor code: 1]
<6>[ 1.077120 / 01-01 00:00:01.069][3] [110] set_dload_mode: download_mode:0
Click to expand...
Click to collapse
[ 0.711817] ro.oem_unlock_supported=1 1=YES
did some digging into last_kmsg while trying to boot into bootloader (AT&T device) and found a reason it may not be allowing it.
http://forum.xda-developers.com/showthread.php?t=2708466
Its a start :good:
of course we need root in order to dd anything
LG issued a new driver update for the v20. Driver version is 4.1.1+. You can get the driver from the website.