I was able to upgrade to gingerbread update zv7.. I was also able to root.. I tested my root with root checker in market, so I know it was a full root. I even went into terminal emulator and su'd in, got my # symbol. I then ran revo toolkit to get cwm on her, but when she installed my recovery, it gave a mismatch'd md5 and told me not to reboot.. As my luck would have it, my battery decided to crap out a few minutes later, and upon replacing the battery, my phone is stuck booting into fastboot: black screen, white writing:
fastboot mode started
usb init ept @ 0x3e000
smsm_read_alloc_entry type : 402
smem_read_alloc_entry size read 1816
smem_read_alloc_entry size passed 1816
smem ram ptable found: ver: 0 len: 6
fastboot_init()
fastboot maximum download size : 450mb
udc_start()
adn then it tells me my usb was connected and then disconnected a few times over.. I dont have fastboot drivers anywhere on the machine, and I've tried multiple ports and such to no avail
EDIT: was able to attempt on home windows 7 x64 pc, and as soon as I plugged in, fastboot drivers recognized and installed. I was able to fastboot erase recovery and install clockwork recovery. Then i fastboot rebooted and got to clockwork, where I was able to get back into my OS. Will attempt to verify root and redo clockworkmod through revo toolkit when I get home in a bit
It may sound strange, but try the drivers from easy tether.
Sent from my VS910 4G using xda premium
link to said drivers?
mtmichaelson said:
It may sound strange, but try the drivers from easy tether.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
Downloaded/installed easytether, to no avail. Still not recognizing lg in fastboot mode
Related
Hey so I currently have an unlocked bootloader and I try to flash a custom recovery via fastboot yet it hangs on < waiting for device > every time.
I have followed the cyanogen mod wiki step by step. It hangs on clockwork and amon RA. USB debugging is enabled. When I boot into recovery it says fastboot I then connect it to my computer it says fastboot USB.
I'm sure it will be some little setting that's wrong. I am currently running 2.3.4 stock, no root so rom manager is a no go.
I guess what I'm asking is does anyone know what I can do to flash a custom recovery?
Have you tried "fastboot devices" to make sure you have a connection?
What kind of computer are you using (Win/Mac/Linux)?
Fastboot devices gives an empty line the a new terminal line.
Also I'm running win 7.
My initial suggestion would be to update your drivers for fastboot. I have had this happen a couple times and a driver update resolved it for me.
Sent from my Nexus One using XDA Premium App
CapStone said:
Fastboot devices gives an empty line the a new terminal line.
Also I'm running win 7.
Click to expand...
Click to collapse
That means your phone is not connected. Update the drivers, as suggested above...
Much appreciated I will try this when I get home tonight.
Was trying to restore from xdabbeb's KitKat rom. Download mode wouldn't work so I tried to flash an older Malladus version. I got a boot loop and now no recovery, the screen goes black in it, or download mode. When I try to go into download mode it shows [1040] Fastboot mode started [1090] udc_start() [1260] -reset- [1270] -portchange- [1280] -reset- [1290] -portchange- [1330] fastboot: processing commands. Thanks in advance for any help :good:
http://forum.xda-developers.com/showthread.php?t=2582142 Check this thread out...I suggest an app called adb 15 seconds. So you don't have to install the entire android sdk kit to get adb command line. Also you could use ubuntu booted to a usb stick. Also check this forum post as well http://forum.xda-developers.com/showthread.php?t=2451696&page=33
Sent from my VS980 4G using XDA Premium 4 mobile app
So I seem to have made the mistake of formatting data - don't ask me why, I wasn't thinking. Now I cannot get past the bootloader or the Google splash screen. On Windows BTW.
Things I've attempted:
ADB and Fastboot - When I ran the command to unlock, it said I already was. :good:
CF's root - Rooted
Wug's toolkit - Tried returning back to stock img, but says ADB device was not found. Step 1 was to enable USB debugging, but I cannot boot into the ROM so that is a no-go. I am using the original OEM cord. I've tried using another USB port as well... nothing.
If I am missing something, please let me know. The drivers should be good to go since I upgraded them 2 days ago.
Update: Dowloaded TWRP and installed via Fastboot. Restarted bootloader, booted into recovery, and the TWRP splash screen popped up. Shortly after that, the Google screen came up and is hung.
I found this thread http://forum.xda-developers.com/nexus-6/help/help-nexus-6-stuck-bootloader-t2949817. When I type fastboot devices, it shows my device's serial number.
Are you sure you didn't delete data? Formatting should not cause that issue. You can flash the stock userdata.img back and stock boot.img
Sent from my Nexus 6 using XDA Free mobile app
or, while in twrp, adb push/sideload a rom(and gapps) to your phone and flash it in twrp recovery.
SO I foolishly issued the fastboot command via ADB when it was working. I started to issue commands in order to install the 2nd bootloader and recovery. Since that point, the Kindle isn't recognized by Windows 10 Pro anymore and I've tried just about every utility, method and button combination there is.
I read that ADB only needs 4 seconds -/+ to initiate commands once the Kindle powers up. I've tried to issue the ADB to get it to boot back in normal mode and it always sits on <waiting for device>. I attached a screen shot showing what comes up in device manager. I've uninstalled the drivers, reinstalled but to no avail.
At this point, I'm willing to try anything. Stand on my head and shake the Kindle 5 times while rotating it clockwise....anything would help.
*UPDATE* I just more or less wiped my laptop which I have all the ADB drivers on as well as Android Studio. I'm going to run some tests to see if I can get that 4 second gap to initiate an ADB command to get the fastboot to go into normal boot more 4000.
*UPDATE 2* I managed to get generic ADB drivers as well as FASTBOOT drivers installed on my laptop. I can communicate with the Kindle a little. At this point, I've tried to issue ADB commands to restart with bootloader and other commands, but it only reboots back into FASTBOOT. The only thing I've been able to see is with KFFA, I can reboot to normal mode but it just comes back to FASTBOOT. I can also issue the test FASTBOOT and it gives me an ID and recognizes the Kindle. I've tried other options within KFFA but nothing seems to stick. I'm now officially stuck. Any help would be fantastic.
*UPDATE 3*
Thanks to this thread http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
I was able, or am in the process of loading a 2nd bootloader + TWRP and then on to CM13.
Any ideas?
Windows 10 Pro
Kindle Fire HD
Rooted with Kingroot
No Fastboot cable
Lots of frustration
Eh back to square one. It reverted and there is no TWRP recovery. It's stuck in FASTBOOT and will take most fastboot commands but I can't get ADB and the drivers loaded to issue any sideload commands.
This is weird.
Hello I have bricked my kindle fire and having similar driver issues I am able to get into fastboot mode with a diy factory cable boot any fastboot command comes back waiting for device . Can I ask where you got drivers please?
I used these:
http://forum.xda-developers.com/showthread.php?t=1890413
I also ran like every single recovery tool out there to help me fix this. After I did fix it, it updated to latest version and there is no root yet for it. I sold it.
If you need help, I think I might still have all the tools I used to get this back to stock and working.
Regards,
rast4man
I really need help with flashing my d950 with any rom idc which one.
I was on kk but the phone was full of virus when i got it. I flashed twrp 3.1.0 and from there formatted everything being sure that i can connect it somehow afterwards to flash it with stock rom.
Now the phone is stuck on lg logo with flashing led.
I can go to twrp but adb cant connect so i can sideload, otg drives (fat32) are not discovered by the phone.
Then there is download mode in which i can go when the phone is not connected to pc. It stays in download mode but it is not discovered by windows or flash tools or any software. Tried more than one pc and installed drivers and software more than once
When i start download mode with the phone connected to pc then it just resets as soon as it loads.
In windows when it is on lg logo port lge(com 41) shows up and modem lge also shows up. When in recovery or download nothing shows up in windows.
I am completely puzzled by this and hoping someone can help me with this phone
**UPDATE**
After hours of trying i finally fixed it! The solution is difficult and long and not found anywhere in full, but since its an old phone and nobody probably need it i will not post it but if ever anyone ever does plz ask and i will share it. Thx!
how?
How did you get your system to read the phone in dl mode. I cant get it to work!
df21d950 said:
I really need help with flashing my d950 with any rom idc which one.
I was on kk but the phone was full of virus when i got it. I flashed twrp 3.1.0 and from there formatted everything being sure that i can connect it somehow afterwards to flash it with stock rom.
Now the phone is stuck on lg logo with flashing led.
I can go to twrp but adb cant connect so i can sideload, otg drives (fat32) are not discovered by the phone.
Then there is download mode in which i can go when the phone is not connected to pc. It stays in download mode but it is not discovered by windows or flash tools or any software. Tried more than one pc and installed drivers and software more than once
When i start download mode with the phone connected to pc then it just resets as soon as it loads.
In windows when it is on lg logo port lge(com 41) shows up and modem lge also shows up. When in recovery or download nothing shows up in windows.
I am completely puzzled by this and hoping someone can help me with this phone
**UPDATE**
After hours of trying i finally fixed it! The solution is difficult and long and not found anywhere in full, but since its an old phone and nobody probably need it i will not post it but if ever anyone ever does plz ask and i will share it. Thx!
Click to expand...
Click to collapse
Are you sure you are in the same situation as i was?
My download mode was not working at all (phone reset when entered downolad mode). I had twrp recovery but usb otg not working nor adb and i could not transfer a rom so i can flash it so I had to short the test point on the motherboard so i could put the phone in qhsusb 9008 mode. This is not easy and its dangerous to kill the phone.
Then you need to download a stock rom and extract aboot, boot, laf, recovery, backupgpt and a few more files with LGFirmwareExtract and flash them one by one with boarddiag application. Then you get normal download mode back and flash any rom you want.
If you tried all the easy solutions like different cables or other pc or different lg drivers and its still not working then you probably need to do the same as me. If you do tell me and i will give you details how i did it. This really is a last resort cause you could easily fry the phone! I've read many people destroyed their phones like this!
not as bad
My problem is that the lg flash tool wont read my phone Ive tried everything and I cant get it to work.
I bought this phone because my other one died and it has jellybean on it. I wat kitkat on it . Thats what Im trying to do.
If you installed the lg drivers you should see an lge android port in device manager. You should go to properties and in advanced change the com port to 41. Unplug the phone and replug it then flash tool will connect to it. Or you could try downloading the rom and use lg up tool or even lg pc suite to update it. Also try the guide from dfuse https://forum.xda-developers.com/showthread.php?t=2666763 and use adb to flash the kit kat rom.
I'm new to lg phones so thats as much as i know to do with it! Unfortunately there is not too much info for this phone anywhere. It took me two weeks to figure out what to do and a lot of luck!
df21d950 said:
Are you sure you are in the same situation as i was?
My download mode was not working at all (phone reset when entered downolad mode). I had twrp recovery but usb otg not working nor adb and i could not transfer a rom so i can flash it so I had to short the test point on the motherboard so i could put the phone in qhsusb 9008 mode. This is not easy and its dangerous to kill the phone.
Then you need to download a stock rom and extract aboot, boot, laf, recovery, backupgpt and a few more files with LGFirmwareExtract and flash them one by one with boarddiag application. Then you get normal download mode back and flash any rom you want.
If you tried all the easy solutions like different cables or other pc or different lg drivers and its still not working then you probably need to do the same as me. If you do tell me and i will give you details how i did it. This really is a last resort cause you could easily fry the phone! I've read many people destroyed their phones like this!
Click to expand...
Click to collapse
hello, which contact points did u short to enter download mode 9008?
i have the same problem as yours. thx.
I'm in a similar situation with my G Flex D950.
It does not boot, remains at the LG logo and seems to loop trying to boot again and again with the green LED flashing.
Pressing POWER+Vol.Down does nothing.
Trying to enter in Download Mode by pressing VolUp while connecting USB, displays the Download Mode screen for less than a second and then enters fastboot mode.
I have a laptop with Win7 and all the drivers and apps correctly installed (already flashed successfully another LG mobile). With the D950 in fastboot mode I run the command fastboot in the laptop and it communicates with the phone but without any useful result as no erase or flash commands executed successfully.
E.g.
>fastboot erase boot
PC reply:
erasing 'boot'...
FAILED (remote: failed to erase partition)
finished. total time: 0.047s
PHONE reply:
fastboot: getvarartition-type:boot
fastboot: erase:boot
partition_get_size 16777216 bytes
Full Erase partition boot
Error 2: Failure sending erase group start command to the card (RCA:2)
>fastboot flash aboot aboot.img
PC reply:
target reported max download size of 1862270976 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.043s]
writing 'aboot'...
FAILED (remote: flash write failure)
finished. total time: 0.080s
PHONE reply:
fastboot: getvarartition-type:boot
fastboot: getvar:max-download-size
fastboot: download:00100000
fastboot: flash:aboot
partition_get_size 1048576 bytes
Error No.2: Failure sending write command to the Card(RCA:2)
Do you believe that your experience with your phone can help me with this situation?