Database Develop

[Q] Bricked Kindle Fire HD 7"?

I have a Kindle Fire HD 7" I received new in Dec of 2012. Its worked well and I have never had any problem with it.. until.
Last week it was running real slow and I turned it off. When I turned it back on I only got the Kindle Fire screen after holding the button down for at least 20-30 second. It shows on the screen for maybe a minute and then goes black. It does not turn back on unless you hold it down a long time and release and then hold the button down 20-30 seconds again.
I ordered a fastbbot cable and the device enters fastboot mode when turned on and connected to my laptop; the fastboot screen stays up as long as cable i splugged in and even after until turned off. The computer makde the USB detected noise when the cable is plugged in/out. However, using the ADB tool doesn't seem to see the Kindle. I get this:
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
After the first time I only get
error: device not found
I've tried 1.3.5, 1.30 and 1.2.3.
I have purchased spudgers in case I need to take it apart.
Anyone have any ideas?

Sounds like your fast boot drivers are not installed properly
Sent from my XT907 using xda app-developers app

Drivers?
mrkhigh said:
Sounds like your fast boot drivers are not installed properly
Sent from my XT907 using xda app-developers app
Click to expand...
Click to collapse
Ok I found a post about the ADB interface and device manager. Downloaded and installed the drivers. I now see a ANDROID DEVICE and under that a ANDROID ADB INTERFACE. That interface driver has a driver date of 8/27/12, driver version 7.0.0.1 and has three driver files:
winusb.sys
wdfcoinstaller01009.dll
winusbcoinstaller2.dll
Still same result form that command. The Android device shows up and disapperas when the Kindle is plugged in.
Thanks for any help and the rapid response.
Color me confused.

Rane0000 said:
Ok I found a post about the ADB interface and device manager. Downloaded and installed the drivers. I now see a ANDROID DEVICE and under that a ANDROID ADB INTERFACE. That interface driver has a driver date of 8/27/12, driver version 7.0.0.1 and has three driver files:
winusb.sys
wdfcoinstaller01009.dll
winusbcoinstaller2.dll
Still same result form that command. The Android device shows up and disapperas when the Kindle is plugged in.
Thanks for any help and the rapid response.
Color me confused.
Click to expand...
Click to collapse
You need to update the drives in that short period that you can see the Kindle. What mark was stating was your fastboot drives. Those are what you need to get right to use fastboot commands. You are using a 7" KFHD 2012 correct?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Sorry; didn't type that right
LinearEquation said:
You need to update the drives in that short period that you can see the Kindle. What mark was stating was your fastboot drives. Those are what you need to get right to use fastboot commands. You are using a 7" KFHD 2012 correct?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
No it stays connected and showing as an android ADK interface, it just disappears if i disconnect it. But I still get he errors when trying teh ADB command

Rane0000 said:
No it stays connected and showing as an android ADK interface, it just disappears if i disconnect it. But I still get he errors when trying teh ADB command
Click to expand...
Click to collapse
How about try what's been wrote already.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Guess I'm dense
LinearEquation said:
How about try what's been wrote already.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Guess I'm dense. the drivers are there on my laptop. Updating the driver form dev mgr doesn't find anything new. Running the command that suppose dto allow me to push a new image to it errors out.
What exactly are you referring to? Not trying to be dense but guess I am.

LinearEquation said:
You need to update the drives in that short period that you can see the Kindle. What mark was stating was your fastboot drives. Those are what you need to get right to use fastboot commands. You are using a 7" KFHD 2012 correct?
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes I have a 2012 Kindle Fire HD 7" .
Guess I;m too dense to figure this out. I'll keep reading.

Rane0000 said:
Yes I have a 2012 Kindle Fire HD 7" .
Guess I;m too dense to figure this out. I'll keep reading.
Click to expand...
Click to collapse
Your ADB drivers will not be recognized at all. This is different than most tablets. Only fastboot commands will at this time. Stop trying to figure out ADB at this pont. ADB is out of the picture at the moment. Only fastboot until the tablet is restored.
1) Get your tablet into fastboot mode.
2) Open a command window and type "fastboot -i 0x1949 getvar product" (with no quotes)
3) You should see product Tate-XXX-XX or something similar.
4) Close the command window.
5) Now use the system restore tool. Follow the OP. http://forum.xda-developers.com/showthread.php?t=1951254
6) Sometimes it does not work as bat tools are not perfect. Try a couple times and it will work.
7) Profit.

Thanks
LinearEquation said:
Your ADB drivers will not be recognized at all. This is different than most tablets. Only fastboot commands will at this time. Stop trying to figure out ADB at this pont. ADB is out of the picture at the moment. Only fastboot until the tablet is restored.
1) Get your tablet into fastboot mode.
2) Open a command window and type "fastboot -i 0x1949 getvar product" (with no quotes)
3) You should see product Tate-XXX-XX or something similar.
4) Close the command window.
5) Now use the system restore tool. Follow the OP. http://forum.xda-developers.com/showthread.php?t=1951254
6) Sometimes it does not work as bat tools are not perfect. Try a couple times and it will work.
7) Profit.
Click to expand...
Click to collapse
I appreciate you taking the time to write this; I'm dealing with a SCCM project right now and very time limited, which makes my kindle doing this at this time most frustrating. I hate to repay such kindness with more questions but I find I must.
When I did as you suggested I got the following (showed directory to indicate what version of files I am working with). Second command is from the OP comments from the the link you gave. I've rebooted and done it again, this time closing the command window between the GETVAR command and the ADD command with same result. Any ideas what my next step should be?
C:\SRT>dir
Volume in drive C is OSDisk
Volume Serial Number is 0E85-569D
Directory of C:\SRT
01/08/2014 07:55 PM <DIR> .
01/08/2014 07:55 PM <DIR> ..
11/13/2012 06:15 PM 815,104 adb.exe
11/13/2012 06:15 PM 96,256 AdbWinApi.dll
11/13/2012 06:15 PM 60,928 AdbWinUsbApi.dll
09/29/2012 11:50 AM 768,858 dx.jar
09/29/2012 11:50 AM 140,800 fastboot.exe
01/08/2014 07:55 PM <DIR> images
04/07/2013 06:47 AM 4,039 SR Tool.bat
6 File(s) 1,885,985 bytes
3 Dir(s) 210,208,550,912 bytes free
C:\SRT>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.001s
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

follow
Rane0000 said:
I have a Kindle Fire HD 7" I received new in Dec of 2012. Its worked well and I have never had any problem with it.. until.
Last week it was running real slow and I turned it off. When I turned it back on I only got the Kindle Fire screen after holding the button down for at least 20-30 second. It shows on the screen for maybe a minute and then goes black. It does not turn back on unless you hold it down a long time and release and then hold the button down 20-30 seconds again.
I ordered a fastbbot cable and the device enters fastboot mode when turned on and connected to my laptop; the fastboot screen stays up as long as cable i splugged in and even after until turned off. The computer makde the USB detected noise when the cable is plugged in/out. However, using the ADB tool doesn't seem to see the Kindle. I get this:
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
After the first time I only get
error: device not found
I've tried 1.3.5, 1.30 and 1.2.3.
I have purchased spudgers in case I need to take it apart.
Anyone have any ideas?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2551661

Rane0000 said:
I appreciate you taking the time to write this; I'm dealing with a SCCM project right now and very time limited, which makes my kindle doing this at this time most frustrating. I hate to repay such kindness with more questions but I find I must.
When I did as you suggested I got the following (showed directory to indicate what version of files I am working with). Second command is from the OP comments from the the link you gave. I've rebooted and done it again, this time closing the command window between the GETVAR command and the ADD command with same result. Any ideas what my next step should be?
C:\SRT>dir
Volume in drive C is OSDisk
Volume Serial Number is 0E85-569D
Directory of C:\SRT
01/08/2014 07:55 PM <DIR> .
01/08/2014 07:55 PM <DIR> ..
11/13/2012 06:15 PM 815,104 adb.exe
11/13/2012 06:15 PM 96,256 AdbWinApi.dll
11/13/2012 06:15 PM 60,928 AdbWinUsbApi.dll
09/29/2012 11:50 AM 768,858 dx.jar
09/29/2012 11:50 AM 140,800 fastboot.exe
01/08/2014 07:55 PM <DIR> images
04/07/2013 06:47 AM 4,039 SR Tool.bat
6 File(s) 1,885,985 bytes
3 Dir(s) 210,208,550,912 bytes free
C:\SRT>fastboot -i 0x1949 getvar product
product: Tate-PVT-08
finished. total time: 0.001s
C:\SRT>adb shell su -c "reboot bootloader"
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
I don't see the images being pushed.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app

Trying
LinearEquation said:
I don't see the images being pushed.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran the SR Tool even though the previous step gave an error (adb shell su -c "reboot bootloader"). I tried the clear cahe and userdata first. Afterwards the Kindle Fire logo was animated but no other change (never loaded even after 1/2 hour) and then tried pushing an image (option 2) which it said succeeded, but I get nothing on the screen but the logo. I'm going to try the latest SRT, not the 1.2.3 (which seemed to match up with my kindle best) and see if I can get it to work form that. At this point its kinda worthless and don't get the red triangle at any time.

Rane0000 said:
I ran the SR Tool even though the previous step gave an error (adb shell su -c "reboot bootloader"). I tried the clear cahe and userdata first. Afterwards the Kindle Fire logo was animated but no other change (never loaded even after 1/2 hour) and then tried pushing an image (option 2) which it said succeeded, but I get nothing on the screen but the logo. I'm going to try the latest SRT, not the 1.2.3 (which seemed to match up with my kindle best) and see if I can get it to work form that. At this point its kinda worthless and don't get the red triangle at any time.
Click to expand...
Click to collapse
\well I ran the latest SRT tool and selected "restore-factory recovery". I went through the process in under 10 seconds. I toook it out of fastboot, restarted it got the animated logo and then the red triangle and option to restore to factory specs. After about 20 minutes the progress bar was complete but it has not restarted and is just sitting there, now for an hour plus.

I would try kindle fire first aid, some have more luck using its restore feature then people that use SRT.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

Hey i have some problem regarding accessories can you go accessories section and solve my prob

It looks like the computer recognizes the device. You won't have adb access while in fastboot mode. Have you tried simply using the fastboot reboot command?
Sent from my KFSOWI using xda app-developers app

So I have the same issue up to now. I read tons of thread around here. Tried several ways to fix my Kindle but no luck. at one Point i had root twrp and now i have nothing. My kindle is stuck on the logo screen with no animation. I can't even get it to fastboot or anything. I can just shut it down but when I power it back up it just gets stuck on lo the white/yellow logo. My computer can't read it. tried installing driver and nothing. Tried the commands "fastboot -i 0x1949 getvar product" but just stays on "waiting for device".
What else can I do? thanks

If you don't see the blue logo then you will need a fastboot cable to get into fastboot mode.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app

stunts513 said:
If you don't see the blue logo then you will need a fastboot cable to get into fastboot mode.
Click to expand...
Click to collapse
No there is no Blue logo. Just the white/red or yellow logo.. I have a fastboot cable but it wont read it.

Good guide for changing OS?

I'm looking for a good guide to changing the OS of my kindle fire 7" 2nd gen to some sort of regular android, It's been ages since I flashed any roms (ages may sound exaggerated, probably like 4 or 5 years?) and that was only a couple times to find one I liked for an older htc desire so I'm not really sure where to begin. I've rooted the kindle in an attempt to install the google play store but I can;t get it to work, so I reset it to factory defaults.
Bottom Line - Anyone have any suggestions of where i should start with guides to change a Kindle Fire 7" 2nd gen OS to android?

Patey07 said:
I'm looking for a good guide to changing the OS of my kindle fire 7" 2nd gen to some sort of regular android, It's been ages since I flashed any roms (ages may sound exaggerated, probably like 4 or 5 years?) and that was only a couple times to find one I liked for an older htc desire so I'm not really sure where to begin. I've rooted the kindle in an attempt to install the google play store but I can;t get it to work, so I reset it to factory defaults.
Bottom Line - Anyone have any suggestions of where i should start with guides to change a Kindle Fire 7" 2nd gen OS to android?
Click to expand...
Click to collapse
@seokhun's excellent tutorial will help you out immensely. Make sure you know what software version you have, as that will determine how you root. If you have 7.5.1, you may have trouble rooting.
Sent from my Amazon Jem using XDA Labs

The 2nd bootloader twrp thread is a good place to start.
Read the first page and the last page all information and files are there.
You'll need adb and fastboot drivers
First step root
Second step enable adb debugging in security
Third step install drivers
https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip
Fourth step download all needed files
(Link on last page from 2nd bootloader in kf2 android development)
Fifth step get adb and fastboot working
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing*or*XDA*
extract files
run KindleDrivers.exe
Then manually select drivers*
Open device manager Settings>Devices>Device Manager
boot to fastboot mode*
Connect Kindle Fire
(If Kindle is not listed as*Android>Android Composite ADB interface)
select*Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select*Android or Android Phone*(or ADB Interface or Android Device)
Select*Android Composite ADB interface*for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or*Android Composite ADB interface
next
you may have to reboot pc
...
Download minimal adb and fastboot debugging (Google it)
You can test adb by typing
Adb devices
You can boot into fastboot mode by typing
Adb shell su -c "reboot bootloader"
You can test fastboot by typing
Fastboot -i 0x1949 devices
Now that you're at that point
You can follow hashcodes directions on page 1
http://forum.xda-developers.com/showthread.php?t=2100963
---------- Post added at 03:55 AM ---------- Previous post was at 03:53 AM ----------
That was horrendous I apologize.
---------- Post added at 03:58 AM ---------- Previous post was at 03:55 AM ----------
Fastboot driver is where I got hung up.
You basically have to go in and tell it you're an adb composite device.

mrkhigh said:
The 2nd bootloader twrp thread is a good place to start.
Read the first page and the last page all information and files are there.
You'll need adb and fastboot drivers
First step root
Second step enable adb debugging in security
Third step install drivers
https://s3.amazonaws.com/android-sdk-manager/redist/kindle_fire_usb_driver.zip
Fourth step download all needed files
(Link on last page from 2nd bootloader in kf2 android development)
Fifth step get adb and fastboot working
Download kindle_fire_usb_driver.zip from Amazon site
Connecting Your Fire Tablet for Testing*or*XDA*
extract files
run KindleDrivers.exe
Then manually select drivers*
Open device manager Settings>Devices>Device Manager
boot to fastboot mode*
Connect Kindle Fire
(If Kindle is not listed as*Android>Android Composite ADB interface)
select*Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select*Android or Android Phone*(or ADB Interface or Android Device)
Select*Android Composite ADB interface*for Stock rom or recovery/adb sideload
Select Android ADB interface for Fastboot mode
or*Android Composite ADB interface
next
you may have to reboot pc
...
Download minimal adb and fastboot debugging (Google it)
You can test adb by typing
Adb devices
You can boot into fastboot mode by typing
Adb shell su -c "reboot bootloader"
You can test fastboot by typing
Fastboot -i 0x1949 devices
Now that you're at that point
You can follow hashcodes directions on page 1
http://forum.xda-developers.com/showthread.php?t=2100963
---------- Post added at 03:55 AM ---------- Previous post was at 03:53 AM ----------
That was horrendous I apologize.
---------- Post added at 03:58 AM ---------- Previous post was at 03:55 AM ----------
Fastboot driver is where I got hung up.
You basically have to go in and tell it you're an adb composite device.
Click to expand...
Click to collapse
sorry it took me so long to get back to this. I've gotten as far as testing fastboot, it doesn't return anything whether the kindle is in fastboot mode or not :S have I done something incorrectly? it seems to be properly rooted, I can enable root explorer in es explorer, although the steps didn't exactly match the tutorial.

Android 6.0.1 G920AUCU3CPC2 AT&T Flashing Instructions

Moving this to it's own thread so it's easier to follow the discussion.
Special thanks to s629c for finding the dialer code that led to the download link and Dante087 for finding the download link.
Generic instructions for sideloading OTA package:
Flashing via this method WILL WIPE EVERYTHING SO BACKUP FIRST. Short tutorial (I'm not responsible for anything that goes wrong, but this worked for me):
1) BACKUP
2) Download package (see links farther down in post)
4) Reboot into recovery. Turn off phone and wait a minute for it to completely turn off. Hold down Volume Up + Home + Power until you see a little Android guy. It will say Applying System Update or something like that possibly, and just let it do it's thing until a menu comes up.
5) Select Apply Update from ADB
6) Make sure you have Android Platform Tools on your computer (there's other guides for this)
7) command 'adb sideload <path to downloaded file here>'
8) Wait patiently
9) Phone reboots and will hang at AT&T logo for 5+ minutes. Just wait this out
Links
Starting at OJ9
To PC2: https://xdmd.sl.attcompute.com/agents/48653/1488/SS-G920AUCU3BOJ9-to-U3CPC2-UP
To PD6: https://xdmd.sl.attcompute.com/agents/48653/1488/SS-G920AUCU3BOJ9-to-U3CPD6-UP
Starting at PC2
To PD6:
First, go to PD4: https://xdmd.sl.attcompute.com/agents/48653/1488/SS-G920AUCU3CPC2-to-U3CPD4
Then, go to PD5: https://xdmd.sl.attcompute.com/agents/48653/1488/SS-G920AUCU3CPD4-to-U3CPD5-UP
Finally, go to PD6: https://xdmd.sl.attcompute.com/agents/48653/1488/SS-G920AUCU3CPD5-to-U3CPD6-UP

Could someone please help?? I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ota.zip
error: protocol fault (no status)

skullymullins said:
Could someone please help?? I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ota.zip
error: protocol fault (no status)
Click to expand...
Click to collapse
It probably means either the phone isn't connected or isn't accepting sideload.
Try the command 'adb devices' and post your output from that command.

How to install ADB-
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Sideloading-
When sideloading in adb, type in "adb sideload [path to ota.zip]" (without quotes, example of filepath on windows c:\users\account\desktop\ota.zip)
Possible Errors when attempting-
Didnt type filepath and just put ota.zip
encrypted: decrypt before updating
~I will update as needed
---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------
skullymullins said:
Could someone please help?? I get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ota.zip
error: protocol fault (no status)
Click to expand...
Click to collapse
did you forget to type in the file path of the file?

Link in step 2 requiring login name and password. Did they lock it up? If so, can someone host it?
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app

netter123 said:
Link in step 2 requiring login name and password. Did they lock it up? If so, can someone host it?
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
Click to expand...
Click to collapse
Yep, looks like they locked it down
Is someone able to upload to Mega or another service? I won't be able to for a couple hours.
It really is amazing though how quickly AT&T was able to "test" locking down that website though

Doing so now

The link in the OP is incorrect, it has the ellipses (...) indicating it must have been copy/pasted from the original post rather than copy/pasted from the link itself. Correct link should be in the original post in the other thread.

jlongrc said:
The link in the OP is incorrect, it has the ellipses (...) indicating it must have been copy/pasted from the original post rather than copy/pasted from the link itself. Correct link should be in the original post in the other thread.
Click to expand...
Click to collapse
Ah good catch. Fail on my part. I updated the OP. Guess AT&T hasn't locked it down yet.

https://xdmd.sl.attcompute.com/agents/48653/1488/SS-G920AUCU3BOJ9-to-U3CPC2-UP link still works

I'm getting a * cannot read update.zip * error. Whats the solution to this? I am using the correct path and have downloaded the update twice now.

NotNathan said:
I'm getting a * cannot read update.zip * error. Whats the solution to this? I am using the correct path and have downloaded the update twice now.
Click to expand...
Click to collapse
I have the same problem When I was trying to solve this porblem, my phone was in update mode, it factory reset itself! So I need to find a way to fix this problem to get the MM at least

Uploaded the file in case AT&T blocks it - http://www.filedropper.com/ota

NotNathan said:
I'm getting a * cannot read update.zip * error. Whats the solution to this? I am using the correct path and have downloaded the update twice now.
Click to expand...
Click to collapse
Some people were reporting that in the other thread. I think the solution was different path (put it directly in C:/), different cable, different USB port, or different computer.

Dante087 said:
Uploaded the file in case AT&T blocks it - http://www.filedropper.com/ota
Click to expand...
Click to collapse
Thanks! Updated OP with your mirror

schhy said:
How to install ADB-
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Sideloading-
When sideloading in adb, type in "adb sideload [path to ota.zip]" (without quotes, example of filepath on windows c:\users\account\desktop\ota.zip)
Possible Errors when attempting-
Didnt type filepath and just put ota.zip
encrypted: decrypt before updating
~I will update as needed
---------- Post added at 08:02 PM ---------- Previous post was at 08:01 PM ----------
did you forget to type in the file path of the file?
Click to expand...
Click to collapse
If I remember correctly, another common error also is spaces in the path to the filename.
I think then you have to put the path and file in quotes like "C:\path with spaces\update.zip"

doubled up

I am having a problem where it says adb installs are disabled on my phone in recovery mode... Anyone know whats going on? USB debugging is enabled.

mrblatz said:
I am having a problem where it says adb installs are disabled on my phone in recovery mode... Anyone know whats going on? USB debugging is enabled.
Click to expand...
Click to collapse
Are you encrypted?
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app

schhy said:
Are you encrypted?
Sent from my SAMSUNG-SM-G920A using XDA-Developers mobile app
Click to expand...
Click to collapse
I was, but I did a full factory reset and I am no longer encrypted.
Thanks for helping me btw.

Downgrade & Root LG G4 LS991 / SPRINT ONLY ZVA-ZV6

Verified Downgraded from ZVA to ZV6 with full root access
LS991 Sprint Only.
QUICK GUIDE & TESTING
(Please read the entire guide before trying anything.)
I nor anyone at XDA is responsible for anything that may happen to your device.
Simply, by taking incentive to change the stock setup provided by the manufacturer for your device; you assume all responsibility for anything that happens.
download LGUP
http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
(Thanks to shakeyabooti)
download LS991ZV6_00.zip and extract to get .tot file with winrar/7zip or any other unzipping program
http://downloads.codefi.re/autoprime/LG/LG_G4/LS991/LS991ZV6/LS991ZV6_00.zip (or google/xda search for mirrors) (Thanks to autoprime)
download LGROOT
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
(Thanks to Unjustified Dev)
download LG Drivers
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772 (or google)
(Thanks to Unjustified Dev)
download rootedsystem.ls991.zip and extract to get .img file with winrar/7zip or any other unzipping program
http://forum.xda-developers.com/sprint-g4/general/zv6-root-success-t3205963/page3
(scroll down to parin11's post. #29 and thank you to both parin11 and mswlogo)
-install drivers
-enable oem unlock in developer settings
-plug device in as charge only, switch to mtp to verify drivers are working correctly, then disconnect
--if on mtp then switch to charge only to verify drivers are working correctly, then disconnect
-enable usb debugging
-reconnect and drivers auto install
-disconnect after 2 minutes.
--while you wait;
-for LGUP extract and install _dll version then the second msi.
-for LGROOT extract to a folder to keep things organized
-remove the back cover of your device and leave it off for access to battery pulls.
-power off device
-hold volume up key and plug in your device and keep holding the volume down key until it passes the screen that says download mode.
-open LGUP
-make sure UPGRADE is checked/has a little circle/bullet point
-click in the empty space directly to the right of where it says BIN with the checkmark
-3 dots will appear to the right of the program in the same row that says BIN; which is your browse option
-navigate to LS991ZV6_00.tot and select
-reconfirm your UPGRADE option is checked
-press start and allow the device to fully complete the process.
-your device will boot to the loading screen right before showing the android desktop and "freeze"
-In most if not all new flash scenarios; your device will not boot up until a factory restore and clear cache is done.
-To do this you must simply remove the battery and usb cable from your device AFTER it has hung on the logo for about 3 minutes / 180 seconds.
(Most new devices average a first time boot of up to 150 seconds maximum to be considered fully "loaded")
-With the battery and cable removed; hold the power and volume DOWN button together at the same time.
-insert the battery while holding these buttons together and just wait while holding them and you will see it says booting into recovery.
-once your in the recovery you use the power key to select and the volume keys to navigate.
-navigate to factory restore/reset hit the power button, navigate to "yes" out of all the "no's" and hit the power button again
-it will say its complete and either ask you to go back reboot or return to menu. RETURN TO THE MENU, do not boot up yet.
-Once returned to the main menu you will see it says clear cache. Select and press yes and now you can select reboot; or return to menu then reboot.
Your device will be on ZV6 stock and fully booted after this.
Now this is where it gets kind of odd because my device never actually loaded the rootedsystemls991.img file nor did I run a root script
when attempting to flash it with the steps listed in the other root guides BUT i followed this guide from step one to step 9 (and outlined continuing through the guide)
http://forum.xda-developers.com/android/development/guide-root-method-lg-devices-t3049772
this allowed all the necessary rooting files to be in the places necessary to execute the root but I did one extra step
I did an adb.exe push rootedsystem.ls991.img /data/local/tmp command as well while the device was on the home screen.
This was so I could basically emulate the command listed by |Unjustified Dev| as it also states to do in the ZV5 guide.
So this is what I did,
-After my device booted up and loaded to the home screen on stock zv6, I opened the LGROOT folder
-held shift and clicked "open command prompt here"
-when cmd opened I ran the following command
adb.exe devices
This allowed me to see that my device was connected to the PC with its generated serial number.
-then i ran the following command
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp
-After this I applied the command to push the .img file to the same location. This was the "emulated command" I spoke of.
adb.exe push rootedsystem.LS991.ZV6.img /data/local/tmp
-I then added the .img file directly to the Internal Storage / Stock Phone MTP storage
-Afterwards I simply powered off my device, removed the usb cable, held the volume up button, then plugged it back in still holding the volume button until
the text download mode was gone again; and no this is not a timing thing im just saying that again incase anyone forgot how to get into download mode. lol.
-I then ran the ports.bat file included in LGROOT to find the COM port drivers.
-Followed up with this command
Send_Command.exe \\.\COM8 (<--Replace number here with the COM port listed for the "DIAG" portion of the device.)
-Now, still in download mode I executed this command about three times with no avail.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
(Which by the way I had the file in both the MTP side of root and in the data/local/tmp)
or you could change it to /data/local/tmp/ like
dd if=/data/local/tmp/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This would possibly solve the issue I was having. So you would have root now.
THIS PART REQUIRES TESTING.
BUT continue reading you'll be shocked.
sidenote:
They state that all you have to do is put the .img file into the root of your Internal Storage / Stock Phone MTP storage
and run the command in download mode but this failed when I tried to execute it.
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
The command above was the command they listed to be able to restore the device from stock to stock with root access. Please note I tried this command while the phone was turned on in debugging with enable oem unlock on, while in download mode and while in recovery mode all with debugging and enable oem unlock checked with either no response / device detected, or attempts causing the command prompt to show the # symbol after a few seconds of executing the line above which shouldn't happen,
since the size of the file is 4GB... The ENTIRE SYSTEM PARITION. -_-. There is a considerable amount of hangtime here is what I'm saying.
If the dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0 command worked for you then great, boot up and enjoy root! BUT.
For those who didnt have luck doing so with the command that failed me above, for some odd reason after pushing both the SuperSU bundle and the entire .img file to /data/local/tmp/ with the files in the internal storage /data/media/0/ as well
trying to only execute the command for the .img (/media/0/ not /local/tmp/) | (not the "fixed" command") and NOT for the SuperSU
eg.
-This was for the image which was the only one I used. (USED)
dd if=/data/media/0/rootedsystem.LS991.ZV6.img bs=8192 seek=65536 count=557312 of=/dev/block/mmcblk0
This was for root only which I did not touch. (NOT USED)
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
-This caused the device to simply show the # sign almost immediately as I spoke of above.
-I typed in LEAVE and the device booted back up.
-The odd thing I'm speaking about is when I turned the device back on it showed that SuperSU was installed and was requesting to be "updated".
-I chose normal and it asked for a reboot. Rebooted started back up and it asked for root access when I clicked on it.
-Granted and successful.
-Went to the playstore.
-It said update next to SuperSU which was even odder.
-Clicked it and updated it and it got the latest version, asked for one more reboot, started back up, then I opened the app. Everything was normal.
-Downloaded root checker basic, titanium backup, and greenify immediately.
All passed with flying colors.
-There is an error that pops up in titanium backup regarding adding underscores or slashes into modified file directories for backup purposes assumed but
opening greenify ended up picking up this issue and requesting to fix it.
Why not right?
-Heh. It worked.
I have never experienced this type of latency within programming so this is extremely odd and without executing the SuperSU script command or,
a sucessful flash of the .img it just seems too odd, but; there you have it! All of the mods / developers working on this device I would like to hear
your insight on this.
So you have two options. Follow what I did or test the command with /data/local/tmp/ and try your luck flashing stock with root again or just run the root script on stock instead of trying to flash from stock to stock rooted.
Thank you and enjoy your root!
P.S. I didn't end up experiencing this issue since it works perfectly but in the event that SuperSU does not install after trying to flash the .img and getting
the 2 second delay with the # sign appearing immediately and rebooting after 3 attempts I would have personally tested the original adb SuperSU script command recommended for the ZV5 users
which was listed above and is
sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
And for the love of your device. Don't try to update your device from an older version using this method. Ayeeeyiyiy
I will re-test what I stated and make a completely organized guide and video for everyone.
I just wanted to let you all know now to assist the entire community in understanding this device's root process a little more.

Will this work with brand new phone?
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.

wow, thanks!
Thanks for all your hard work. This phone has been one of my best and the only thing missing has been root, etc. Chewing over your instructions and thoughts. My confidence level is not quite there to pull the trigger, but i'm getting close. Hoping this is a promising method for those of us on Sprint ZVA. I will continue to do research and watch this thread. Thanks so much for your time, tips and expertise.

brpaaron said:
This method looks exactly like what I would need if I were to sign up with Sprint and get a brand new G4 from them. I just want to make sure that this method would work on the brand new phone to get root access and possibly flash new ROMs to the device. I have gotten burned before by getting devices that I think would work only to find out I had gotten an unsupported variant. Any knowledge would be greatly appreciated. Thank you.
Click to expand...
Click to collapse
As long as its not been updated to zvb. Antirollback implemented on zvb

Still running zv6
I am still running zv6 and never updated. Do I need to update to downgrade to root or can I just skip to after the downgrade?

i am running zv9 i can not stock zv6

I have ZVC can i downgrade to ZV6?
LG G4 LS991.
LG G3 D850 ROM Fulmics 6.6
Recovery TWRP v2.8.7.0 bumped

LS991 ZVD
Hi there does anyone know whether or not it will work on the ls991 zvd update??? Sprint variant

Ls 991 ZVD
Will this method work on ls991 zvd i havent found anything on it

Expo6810 said:
Will this method work on ls991 zvd i havent found anything on it
Click to expand...
Click to collapse
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower

TheMadScientist420 said:
No. Zva or lower. You will brick it.
---------- Post added at 02:28 AM ---------- Previous post was at 02:28 AM ----------
No zva or lower
Click to expand...
Click to collapse
Is there anything i can do for my zvd

Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as far as i know. nothing
new root methods and tweaks come out everyday.
all the good devs as far as i know have stopped developing g4 and moved on due to the locked bootloader d other issues
---------- Post added at 09:24 AM ---------- Previous post was at 09:17 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
a root method has been exposed on the g5
intime it may come for the g4 also but not adapted rite now

Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
Right now i have ZVC software version can i downgrade zv6????

hawzsth said:
Right now i have ZVC software version can i downgrade zv6????
Click to expand...
Click to collapse
no u will brick

TheMadScientist420 said:
no u will brick
Click to expand...
Click to collapse
its already brick any solution...... now its show 9008 no power on ...

hawzsth said:
its already brick any solution...... now its show 9008 no power on ...
Click to expand...
Click to collapse
octoplus box with jtags the only fix
thats a hardbrick
---------- Post added at 08:30 AM ---------- Previous post was at 08:29 AM ----------
Expo6810 said:
Is there anything i can do for my zvd
Click to expand...
Click to collapse
as of rite now no

If I downgrade my zva will it allow me to sim unlock it

Somebody know if can downgrade ZVI to another version

Pls any update on locked bootloader?

Thank you!
Just learned here enough. Thank you!
I just head through UsU thread after reading this; Respectively thanks for the post again! ??

How to solve adb bad_alloc problem when trying to sideload update?

Hi,
Im trying to update my OP3T with adb sideload but i keep having these error?
what should i do?
Thanks

zevim2005 said:
Hi,
Im trying to update my OP3T with adb sideload but i keep having these error?
what should i do?
Thanks
Click to expand...
Click to collapse
Which adb version do you use?
Type the command: adb version
Sent from my ONEPLUS A3003 using Tapatalk

Is saying 1.0.39

Which OS do you use?

4.1.3 and im triyng to flash open beta 4!

I mean the OS on your PC. Not Andoid which is kinda obvious when someone uses adb.

yep ypu re right kkk,windows 10

Any previous adb versions on your PC. From where did you download it?

just received my new notebook,came from windows 10....downloaded from google new just adb files....

Try this version. Make sure to issue the command "adb kill-server" before you fire up the other version.
Report back, pal.

download minimal adb and fastboot google for it
---------- Post added at 09:05 PM ---------- Previous post was at 09:04 PM ----------
here you are https://forum.xda-developers.com/showthread.php?t=2317790

https://dl.google.com/android/repository/platform-tools_r25.0.3-windows.zip

both didnt work,cannot read the file error....

Must be file related then. What's in the zip file?

the open beta 4,downloaded twice from op website!

Probably corrupt update.zip, if not don't update file for your phone (example for 3 instead of 3t).

Ok,after a lot of searching,i found out that my problem was that windows 10 decided to install leeco drivers instead of google adb drivers.
So i remove the leeco drivers following this guide and then Installed Google drivers and successfully worked with adb links that you guys provided,so thank you very much for the help!
Guide by nAFutro on reddit:
A few steps to get rid of the LeMobile pesky driver.
Have the device manager opened "devmgmt.msc". Make sure the LeMobile is visible in the device tree by connecting your phone or tablet.
Open the Command Prompt with Admin privilege. type "pnputil /enum-drivers" This should generate a list, lookup the "Published Name" value of the LeMobile driver, should be something like "oem??.inf" Remember this name.
Use the following command in the Command Prompt with Admin rights: "pnputil /delete-driver oem??.inf /force" Of course oem??.inf should be the name you found in step 2.
Go to the device manager. Right-click on the LeMobile device still shown in the device manager and select "Update Driver Software". Now you can browse to your preferred driver like the one in location "C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
And You're done! Cool thing is that you will have to do it again if you connect a tablet or something new and Microsoft decides the LeMobile driver is better then Googles driver...