Database Info

Flashed I9020A ROM on a D720, now stuck at splash screen

Had to come out of lurking for this:
- phone is a D720
- flashed I9020A ROM: Android 2.3.4/GTJ61/UCKE1 Radio/KA3 Bootloader (I didn't do it)
- phone stuck looping at splash screen
- able to put phone into 'fastboot mode' - NOTHING happens in Windows Device Manager
- able to put phone into 'download mode' - NOTHING happens in Windows Device Manager
- no recovery installed
- I have a 2nd D720 that shows up in Device Manager fine in 'fastboot mode' and 'download mode'
What are my options?
- displayed in 'fastboot mode':
HW VERSION - REV 03 (JTAG)
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020UCKE1

Go into fastboot mode and hook up to your pc.
Get your fastboot driver installed.
Flash recovery thru fastboot.
http://android.modaco.com/topic/302508-solved-using-adbfastboot-help-to-flash-recovery/

Try this:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
There is also a video what shows you to do.

Thanks for the quick replies but NOTHING happens in Windows Device Manager

You have to install the rite driver. Just cuz it installed, doesnt mean its the rite one.

snandlal said:
You have to install the rite driver. Just cuz it installed, doesnt mean its the rite one.
Click to expand...
Click to collapse
Hmm, even though (as stated in the OP):
- I have a 2nd D720 that shows up in Device Manager fine in 'fastboot mode' and 'download mode'.

I know. It is. But if your typing adb devices and nothing is showing, its the wrong driver.
Try a different usb port maybe

Adb is not for when the phone is at the splash screen. Or the bootloader screen. Or when the device is in fastboot.

Doesnt it use the same driver? Sorry don't use windows often. But OP if you can't get it to connect/ find the driver for a windows pc get a linux live cd and use terminal on that.
If you can get into fastboot you can fix it.
Avoid download mode unless you break fastboot. (which is really hard to do)

I appreciate any and all suggestions.
snandlal said:
I know. It is. But if your typing adb devices and nothing is showing, its the wrong driver.
Try a different usb port maybe
Click to expand...
Click to collapse
While the phone is in 'fastboot' mode I used USBDeview and see nothing. When I do the same with my 2nd D720, it shows.
I tried a different USB port.
themapleboy said:
Doesnt it use the same driver? Sorry don't use windows often. But OP if you can't get it to connect/ find the driver for a windows pc get a linux live cd and use terminal on that.
If you can get into fastboot you can fix it.
Avoid download mode unless you break fastboot. (which is really hard to do)
Click to expand...
Click to collapse
I'll report back after trying Linux Live.

themapleboy said:
Doesnt it use the same driver? Sorry don't use windows often. But OP if you can't get it to connect/ find the driver for a windows pc get a linux live cd and use terminal on that.
If you can get into fastboot you can fix it.
Avoid download mode unless you break fastboot. (which is really hard to do)
Click to expand...
Click to collapse
Tried LinuxLive on USB and it doesn't recongize it either.
When you say "If you can get into fastboot you can fix it", do you mean if I can boot the phone into 'fastboot mode' or accessing the phone from command prompt in 'fastboot mode'?
I made minor corrections to my previous posts.

[Q] Fastboot problem

hello,
I'm hoping someone here can help me sort out my current problem.
I've been trying to root so I can install the latest ICS port, but having problems at the Fastboot screen.
I apologize in advance if some of the references/names I'm using are incorrect.
So, I had originally unlocked my Nexus S sometime early this year. When I restart the phone, the "unlocked" lock picture shows up under the "Google" words, and when I go into fastboot mode, the Lock State is Unlocked.
I'm running 2.3.6 right now on the Tmobile version of the phone.
When the phone is on (not in fastboot mode), I can execute ADB commands and the device is recognized. As soon as I go into fastboot it isn't.
I'm running 64bit Win 7, and I have gone through the various threads that have listed this issue, and installed PDA Net drivers and still there is no solution.
In Fastboot mode, while connected to computer under device manager, it shows up under Universal Serial Bus Controllers as an Unknown Device... I'm unable to update any drivers for it, and even when I try to manually update the drivers by going to the PDANet drivers it does not allow it.
When the phone is on in regular mode in device manager it shows up as Android Phone and within that it has a listing called Android Composite ADB Interface.
As mentioned above, when phone on in regular mode everything is detected.
I installed clockwork app from market, assuming that the phone was "rooted" based on the "unlock state" in fastboot mode, but it immediately says that phone needs to be rooted because it was unable to find SuperUser file etc etc.
I've spent the better part of a few days trying to figure this out by checking all sorts of links, but I haven't found a solution. The main issue is that the phone is not being recognized when in fastboot mode when connected by USB. And I'm unable to install the proper drivers for fastboot mode.
Hopefully this makes sense, and someone can provide some insight.
Thanks in advance!

I'm not positive about this but couldn't you adb push the su binary and apk? I don't own the Nexus but I would think since its unlocked you could just push the files. If this would work I would think it's just a temporary solution to allow superuser permission. As I understand it, fastboot is the preferred method for the Nexus.
Sent from my PG06100 using Tapatalk

Did you try a fastboot command like fastboot devices?

Don't know if this applies to you but I had a similar sounding problem when trying to root my Nexus S where everytime I booted into fastboot mode I had an error message at the bottom of the screen saying something like 'fastboot status-fail Invalid command' and so I couldn't use any fastboot functions.
To get around it I used this one-click root . For some reason I got an error message halfway through for whatever reason and it wouldn't complete the root for me but it booted me into fastboot without receiving the error message and then once I was in I went and rooted manually.
The CWM is out of date on that site though (possibly the super-user zip too) so I replaced them with the latest versions and popped it in my dropbox for you, if you wanna try it out.
http://dl.dropbox.com/u/47770734/One-Click-Nexus-S.zip
Edit: just had a little look through the bat script and the initial commands that got me into fastboot properly is (with your phone in debugging mode):
adb start-server
adb reboot bootloader
Click to expand...
Click to collapse
So you could try that first if you wanna go through manually.

Know that you can't run adb command while in fastboot mode. Boot into your CWM and then you can start an adb shell and you'll be able to push all the files you want and execute all the commands you need.
Fastboot mode is for running fastboot indeed. Try 'fastboot devices' while you're in the bootloader and see if devices pop up. If not, you really have to figure out your drivers issue. Maybe remove the device completely from your PC (including driver files) and reinstall it using the PDAnet drivers.
Greetz

[Q] LG-P506 Fastboot Can See My Device But Won't Show The Serial Number

So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.

baked cake said:
So I have a LG p506 and I recently installed cyanogen-mod 10.1 on it. I had to use the November release as the newest one wouldn't load past the cyanogen logo(i let it run for a couple hours). Everything seemed to work great after that. So I put the phone in my backpack for a later date.
When i finally pull it back out the battery was completely dead, and plugging the phone into usb would not charge it. I used an external device to charge it.
Basically the only thing the phone can do now is load the lg logo, go into emergency mode, and fastboot. I can erase and flash images, I have tried system boot and recovery multiple times with different files.
However I get the same two things every time i try something:
1. when I plug the phone into usb, the phone will do its thing then give a STALL GET_DESCRIPTOR error
2. fastboot devices shows something but I get a "?" where the serial number should be.
I am not proficient enough with fastboot to try other commands. Any one have some advice?
Also, I've tried every usb port I have, theres only one that works with the phone. One of the usb ports shows up normally on the phone but fastboot won't show any devices. I am running windows 7 ultimate x64.
The one thing i haven't tried is reinstalling windows 8 on one of my hdd's and seeing if it isn't a win7 issue. Ive used it with win 8 before and it didn't give the error message.
Click to expand...
Click to collapse
fastboot doesn't show a serial number for that device. At least never has for me. If 'fastboot devices' lists something like
Code:
List of devices attached
???????? fastboot
then you're good to go.

damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.

baked cake said:
damn that was my only thing to go on lol. nothing will get this phone to boot into recovery. im about to get a sd card reader for my pc to test and see if its bad.
Click to expand...
Click to collapse
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.

shinobisoft said:
You can use fastboot to flash another recovery. Rashed should have a link in the OP for the 4.1.2 ROM you said you were using. You can continue to use the command-line if you like, but I did write a Windows app for flashing recoveries. Links in my signature.
Click to expand...
Click to collapse
ill give it a try, but i have tried just about every recovery file i can get my hands on and no luck, also looks like winds 8 doesn't want to acknowledge my phones existence. I downloaded and installed the driver from LG but still no luck, windows 8 is giving me a failed descriptor error as well.

ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.

baked cake said:
ok so i have been stumbling around for a bit and noticed something possible wrong.
Windows 7 device manager shows my device, installed correctly, but listed as USB Modem Phone ADB Port.
Shouldn't this be a fastboot port? Since ADB is only available via the android operating system, and i can't get into my operating system, all i have is fastboot.
I have ran thru quite a few fast boot recovery pages, and I don't know what im missing here.
Click to expand...
Click to collapse
I'd say that was/is the correct port name. I don't have that device anymore so I cannot say for sure.
Sent from my LG-P769 using Tapatalk

ok, so this is a follow up on some things i have tried recently.
Since my last post i have:
1. put the sdcard into my tablet, and formatted it/ ran an error scan on it via windows.
2. i then flashed a recovery file via my phones fastboot, i pulled that card put it back in tablet to see what files it installed.
3. according to windows, flash recovery installed a .LOST folder with nothing in it, which is the same thing my tablet has on its internal memory, so i don't think there's anything wrong there.
4. phone still cant boot past LG logo(or recovery), or charge the battery when plugged in.
5. I still get a stall get_descriptor error when connected via usb, and commands such as fastboot reboot don't work, tho the phone will say its rebooting (it says its rebooting then just sits there and does nothing, command prompt will say action completed).
6. one thing i have tried as well, is telling windows not to automatically install drivers, then uninstalling my phone from device manager.
Whats interesting about this was that windows was installing its own ADB modem driver from it's own library every time i plugged in the phone. After disabling auto drivers, and reinstalling my LG drivers, the phone simply remains an unknown device.
Some things I have tried include pointing windows to the driver folder, both the downloaded folder and the folder windows installed it to. Neither worked.
The next thing I tried is the have disc option on both. Although there are setup information files in the install folder (about 50 of em), pointing the phone to each file one at a time did not work.
What did work, interesting enough was pointing the phone to a set of Naked Drivers I downloaded, although none of those drivers are specifically for my phone, and they only gave me the same problem I had when i had windows auto installing its own driver.

LG L5 612 - fastboot issue
Hi,
I have an LG L5 612.
I'm trying to perform below actions, but always get "waiting for device" ... and nothing happens.
fastboot reboot-bootloader
fastboot flash boot boot.img
"adb devices" lists my device correctly, while "fastboot devices" output nothing.
C:\ADB>adb devices
List of devices attached
LGOTMS840b676a device
C:\ADB>fastboot devices
C:\ADB>
C:\ADB>fastboot reboot-bootloader
< waiting for device >

Shield K1 Tablet isn't recognized by fastboot

Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.

You have boot into the bootloader before being able to use fastboot. Just reboot your device and hold vol- during startup. The tablet will show some console messages, offering some options. If you see that screen, you can use fastboot.

bob3rt said:
Good afternoon everyone
I got my K1 for Christmas and I've been trying to root it for a few days but I can't get that far because I can't get the bootloader unlocked.
I've been following the guide based off of Nvidia's website
I've activated USB Debugging mode as seen here . Now once I've authorized the PC using the tablet. Once I run cmd in administrator mode I run
Code:
adb devices
I am able to get the serial and it says it's authorized. However if I go into Fastboot. if I check for devices it just goes back to the prompt, and if I try to run the unlock command it just gets stuck on <waiting for devices> (I've attached a screenshot here.)
At first I thought this was an issue with the OS/Drivers because I am on Win10 x64, and the shield drivers gave some error about driver incompatibility. So I loaded up a VM with win7 x32. However I am running into the exact same issue once I get to fastboot; the tablet just doesn't want to cooperate. I've booted into fastboot manually Where the options are:
Code:
[nvtboot] (version UNDEF_BUILD)
[bootloader] (version UNDEF_BUILD)
Device - locked
Continue
Fastboot Protocol
Recovery Mode
Restart
Poweroff
Nothing is recognized from there either. I've also tried multiple cables, since the Shield doesn't come with any. Anyways I've searched the older threads here for help but none of them have given me any luck. If there's something I can try I would definitely be open to hearing it and trying, I just don't know what the issue could be.
Thanks for your time everyone.
Click to expand...
Click to collapse
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.

dzidexx said:
Adb works in normal mode.
Fastboot works in Bootloader mode.
Reboot to BL and type "fastboot devices", if no device go to K1 and select "fastboot protocol". Select on/yes.
Click to expand...
Click to collapse
Hey there, sorry for my late reply, I've been swamped with work. I've tried your advice with no luck so far.
I can reboot to the bootloader, but when I select "fastboot protocol" I don't get to choose Select on/yes. it just refreshes the screen with the same options that I listed above. If you'd like when I get home I can provide a screenshot of my tablet so you can see the options, but I'm not getting anything like you described. Am I missing something?
Thank you for your time so far helping me.

Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt

I had the same issue and lasted untill I tried different usb cable
Shield K1 connectivity is very sensible to cable quality
try others

dzidexx said:
Connect k1 to pc, type in cmd:
adb devices
adb reboot bootloader
fastboot devices
/Enable fastboot protocol on k1, type again/
fastboot devices
Give here screenshot from pc - all command/answers in cmd. @bob3rt
Click to expand...
Click to collapse
Hey Sorry again for a late response! However the good news is that I got it working!
What I ended up doing was hooking up the tablet to my Raspberry Pi with MATE and running adb/fastboot there. I originally ran into the same issue, but since I was able to sudo fastboot everything was recognized and seemed to work fine. I appreciate all of your help, and I apologize once again for the late replies!

For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:

0mad said:
For those that don't have a Raspberry Pi to follow the OP solution (like me), it's likely that your drivers aren't up to date on your PC.
Go here... https://docs.nvidia.com/gameworks/content/devices/shield_flashing_from_image.htm
And follow the initial instructions in the introduction paragraph and get yourself NVIDIA CodeWorks for Android. Once downloaded and installed you'll then see the shield in your fastboot devices list.
:good:
Click to expand...
Click to collapse
Worked like a charm! Thanks.

TF700 - unrecoverable botloader error

Hello
I need help with my TF700.
I had this tablet for some time. It was unlocked with TWRP and ZOMBI-POP.
Last week I wanted to upgrade it for KIT-Kass 7.1
I wanted to update my TWRP for kang wersion ( 2.8.7.4) through TWRP and during the process it rebooted.
Then I've got a bootloop on normal starting. I can't get into recovery mode through power + vol up - tablet has no respond for that
I can only go to fastboot through power + vol down but when I connect it to windows with adb drivers or to linux(FWUL) it sees no device and no respond for any command.
Do You have any idea what to do ?
Thank You in advance

Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP

Nektopoli said:
Sorry to say this but, if you can't send it commands then you are most likely hard bricked. What OS are you running on the computer with fastboot on it? - NP
Click to expand...
Click to collapse
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.

marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Do you have access to a Windows 7 computer/laptop. There's an issue with Windows 10 and the fastboot drivers not working together, and causing a problem like yours. - NP

marmacapp said:
This sounds not so good. I use windows 10 but as I said also I used FWUL to try.
Click to expand...
Click to collapse
Found this in another thread, windows 10 fix. - NP
"I used Windows 10 and had to disable driver signature enforcement. Once I did this the PC recognized the tab without issue. "
To disable;
http://www.thewindowsclub.com/disable-driver-signature-enforcement-windows

Thank You for the info, but I have laptop with Windows7 and still the same.
But if I have text on screen like this Starting fastboot USB download protocol can the device still be hard-bricked ?
Maybe I am missing some drivers ?

I would d/l Minimal ADB and Fastboot from here;
https://forum.xda-developers.com/showthread.php?t=2317790
and Universal_Naked_Driver_0.72 here; - NP
https://forum.xda-developers.com/showthread.php?t=2263822

For now the problem is I can not install the "naked driver" because devices manager can not see TF700 when it is connected, so I can't update the driver

Have you tried sending the [fastboot reboot] command to see if the tablet will reboot. When I bricked my TF201t my laptop didn't see it but it still took the commands allowing me to wipe the recovery partition and install the correct TWRP. - NP

Dear Guys
I know that this topic is quite old, but I am still fighting with this problem.
I tryied different drivers, 3 different computers ( two with windows 10 one with windows 7) and I can;t connect to fastboot.
The tablet is in this mode, but when I will use adb and type any command like fastboot reboot - it displays "waiting for device"
Do You have any idea what else can I try ?
Best regards

Hi,
me too! I was using it at lunch - no problem. Got home and turned it on and unrecoverable bootloader error.