Related
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Potetsjokolade said:
Hello, I've tried rooting my Nexus 7 (2013) with LTE for like 5 hours now...
I've done every single thing in every single thread, and I still can't do ****.
I've tried the WugFresh root toolkit, but that did not work at all for me, I uninstalled and remove what they told me to do... But nothing worked, when I followed the WugFresh toolkit I lost usb mass storage... N7 did not appear at all on my computer, which it did, before I tried to screw with it...
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
I know that was very bad written, but I'm a bit in a hurry. Anything I could do?
Click to expand...
Click to collapse
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Username invalid said:
So the current condition of your device is that ADB is nonfunctional but you are able to temporarily boot into TWRP with fastboot - is this correct?
Click to expand...
Click to collapse
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Potetsjokolade said:
I've tried doing it the manual way too, downloading all the drivers, uninstalling the other onces first.. But nothing... I could not even get the device listed in adb! I tried the full driver installation thing + automatic check if everything worked out, but the tablet would NOT run the script to reboot it into fastboot, and when I tried to restart the tablet into fastboot, and then continue to run the toolkit, it would start TWRP, the popup on my computer told me to flash something "!flashready", but I could not find it in the sdcard...
I unlocked the n7 manually, holding the volume button and power button down.
Click to expand...
Click to collapse
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
bananagranola said:
I'm not sure what this means. If you're using a toolkit, you're not doing it manually. Have you tried ADB and fastboot alone, without a toolkit? Is TWRP on your phone now? If so, you're done; just flash from recovery 1) a ROM for a custom ROM or 2) SuperSU.zip for just root.
If you don't have TWRP, does your Google boot screen has a locked icon at the bottom? If so: for ADB to work you need to have debugging turned on in your phone's developer settings. You don't need ADB though; just reboot into the bootloader by holding power and volume-down. Then type "fastboot devices" and see if anything shows up.
If it's an unlocked icon, just flash a recovery.img from fastboot.
Click to expand...
Click to collapse
Tried both manually with adb, and with WugFresh toolkit. I got WugFresh to run TWRP temporarily.
Potetsjokolade said:
Yes, that is correct, temporarily, with the toolkit I mentioned. But I do not find the files that the toolkit tells me to flash
Click to expand...
Click to collapse
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
How can I do that when my N7 does not show up on
adb devices
Click to expand...
Click to collapse
Getting "waiting for device"
Potetsjokolade said:
How can I do that when my N7 does not show up on
Click to expand...
Click to collapse
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Username invalid said:
Fastboot is separate from ADB. Your fastboot is working if the toolkit is able to boot TWRP.
Code:
fastboot devices
is what you use while your device is in the bootloader.
Click to expand...
Click to collapse
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Potetsjokolade said:
Great! I'll try that, just upoading openrecovery-twrp-2.6.3.0-flo.img to dropbox, just in case I'm able to flash it from download/
Click to expand...
Click to collapse
openrecovery-twrp-2.6.3.0-flo.img is for the WiFi model. TWRP for the LTE model is openrecovery-twrp-2.6.3.0-deb.img.
Username invalid said:
The toolkit is using the command
Code:
fastboot boot openrecovery-twrp-2.6.3.0-deb.img
to temporarily boot it over the stock recovery. Since you unlocked your bootloader manually, you can replace the stock recovery manually too using
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img
Click to expand...
Click to collapse
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
EDIT: Nevermind that stupid question
Potetsjokolade said:
Where in windows should I paste openrecovery-twrp-2.6.3.0-deb.img, so I can then flash it? It showed up in fastboot devices
Click to expand...
Click to collapse
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Username invalid said:
C:\Program Files\WugFresh Development
Then in toolkit > Advanced Utilities > Launch CMD Prompt > "fastboot flash recovery openrecovery-twrp-2.6.3.0-deb.img"
Click to expand...
Click to collapse
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Potetsjokolade said:
Flashed custom recovery + superSU
Thanks guys... Could you help me solve the problem where Nexus 7 wont show up on "my computer"? :laugh:
Click to expand...
Click to collapse
What do you see if your computer Device Manager with USB Debugging on?
Username invalid said:
What do you see if your computer Device Manager with USB Debugging on?
Click to expand...
Click to collapse
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Potetsjokolade said:
It's connected as MTP, USB Debugging is on, and it does not show up on My Computer as Nexus 7
However, if I connect it as as PTP, it will show up.
Click to expand...
Click to collapse
I've never had that problem so I can't speak from experience.
http://forum.xda-developers.com/showthread.php?t=2428061&highlight=mtp
http://forum.xda-developers.com/showthread.php?p=44219641#post44219641
Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Megaiamepic said:
Hi. I recently rooted my phone Xperia S (LT26i) and unlocked its bootloader. I had installed CWM and TWRP recovery in the phone and I have ADB and Fastboot(Android SDK) in my computer. I had earlier flashed CWM but it wasn't working so I flashed TWRP. I had downloaded a custom ROM and Gapps in the PC and I extracted the zip files and copied them into the phone (this was a mistake). I went into TWRP and did factory reset, erased cache and wiped dalvik cache unknowingly:silly: Now I can't flash ROM or Gapps and I cannot boot normally. Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?
Megaiamepic said:
Earlier, ADB used to recognize the device and now it doesn't. When I turn on the phone, the Sony logo appears and pink light glows. But it doesn't go beyond that. It repeatedly restarts the phone till the splash screen. Now I can't boot the phone normally Please help, guys.
P.S. I saw a post suggesting to enter a code in the Terminal module of TWRP but it's not working.
Click to expand...
Click to collapse
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
fipsix said:
I'v got almost similar problem right now, but beyond that I'v flashed custom kernel to mine.
I hope someone will post here soon
edit: the kernel name is Open SEMC
but I think I can get to fast boot, so changing kernel should not be problem. But how to get some ROM to the phone, when I can't connect it anyhow?
Click to expand...
Click to collapse
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.
Mirhawk said:
What do You menan by now not recognizing in adb? While being in adb? Are You able to boot to twrp?
If You both are able to boot into recovery(twrp), I recommend You boot into twrp, connect the phone to pc. Then Let the drivers install. After it, start the adb, use this command to command to check if Your device is connected:
Code:
adb devices
Copy the ROM zip to the folder of adb.
Then push the file to sdcard using:
Code:
adb push finlename.zip /sdcard
where filename.zip is Your ROM.
Click to expand...
Click to collapse
I tried using the adb command but it says "error device not found"
Megaiamepic said:
I tried using the adb command but it says "error device not found"
Click to expand...
Click to collapse
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"
Mirhawk said:
You are using windows, right? Do You see the phone connected in the "Device Manager"? It might but under "Other Devices" by the name "Sony Xperia S"
Click to expand...
Click to collapse
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:
fipsix said:
That's what I've done in the end. Bud I had problem with drivers for my xperia, it seemed that drivers were wrong or something. So I uninstalled them, downloaded new one and voila :good:
Click to expand...
Click to collapse
Do post which drivers You installed with a link. It might help the other member.
Mirhawk said:
Do post which drivers You installed with a link. It might help the other member.
Click to expand...
Click to collapse
Ooh sorry, totally forgot about that. I dont have direct link, but I will upload them somewhere tommorow.
drivers
I hope those are the right ones, because I donwloaded tons of em
http://ulozto.cz/x4tSiM6N/drivers-fastboot-adb-flashtool-by-velcis-ribeiro-rar
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
Click to expand...
Click to collapse
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
573v3 said:
If, as you say, you can enter Download Mode, you could try this Method by @hyelton :- http://forum.xda-developers.com/showthread.php?t=2785089. Any problems ask in that Thread, they will try and Help. GOOD LUCK.......:good:
Click to expand...
Click to collapse
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
MWGiants said:
OK sir, I fixed it so clearly it was not hard bricked (don't say that if you aren't sure, it would have cost me plenty of money to replace that had I not known better). What I did was use fastboot to load up an laf.img that I was able to download from someone on here. Even though I was unable to flash the laf, I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. I was then able to restore it via LGFlashtool. So yup, its fixable!
Yeah, once I got it into download mode (that was the whole problem, I was stuck in fastboot) I was able to fix it.
Click to expand...
Click to collapse
congrats. it is good to know it is fixable
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Hakem said:
That's great. And what fastboot commands did you use to execute the laf from your computer ?
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
Click to expand...
Click to collapse
Fastboot boot laf.img
But beware this doesnt work for D855. His LS980 has a unlocked bootloader
Ok thanks
Verstuurd vanaf mijn HTC One_M8 met Tapatalk
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
bikrame said:
Hey bro i m having same issue ! Can you please explain laf.img , i tried twrp.img !
What does 'laf' means
Click to expand...
Click to collapse
Hi, sorry for the late reply. I hope you've already fixed it, but if you're still having this problem then let me explain. "laf.img" is the "download mode" partition. The reason you can't use twrp.img (which is a recovery partition image) is because you're "too far gone" so to speak and not even at the point to try and get into recovery. You need to restore download mode first. If you have fastboot properly working (not going to explain that, look it up, there is plenty of info about that on here and other sites), then you can do what I did. (Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work, I cant tell you about that because I don't have one and haven't played around with one). Anyway, if you have fastboot working properly (read my first post about how it can be working as long as the phone is responsive, even if you don't get back the "devices comman", you may need to play around with the drivers to get this to work) then you need to obtain an laf.img from somwhere. I found a complete set of .img's for my model somewhere (don't remember if it was on this site or somewhere else). It took a lot of searching, but I'm sure you can find one. Once you have that and the working fastboot then run the command "fastboot boot [location of your laf.img]laf.img"
GOOD LUCK!!!
itsbighead said:
That's awesome to hear. It seems that booting the laf partition does not actually work under fastboot mode for D855 variants which is why I thought it wouldn't work for you
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
That's interesting...do you have any idea why that would be? Is it a locked bootloader like someone else mentioned? (I don't know much about the D855 model, never got to play with one). Maybe there is a workaround we can come up with...
itsbighead said:
Unfortunately its hard bricked and the repair center will know that you tampered with it. The nature of the LG bootloader makes it so that you cant write or boot any images using fastboot.
What was wrong with your method is, when you downgrade to KitKat android bootloader you have to also downgrade the bootloader, laf and recovery partition or other wise it bricks. You should have downgraded your phone using LG Flash Tool to KitKat and then root and install whatever you wanted
In your case the version mismatch between your aboot, bootloader and laf partition is the reason why it doesnt work
Click to expand...
Click to collapse
I realized the problem with the mismatched aboot after the fact... ironically it all worked out because after all of this I am now back to the original kitkat and can just root and flash as you said lol.
Complete Fix Guide
http://forum.xda-developers.com/spr...y-download-t3053985/post60106965#post60106965
Can you please post where you got your laf file? I have the same problem :crying:
MWGiants said:
I was trying to install TWRP on my phone (LS990, ZV8) using flashify app. This didn't work and after I did so, every time I would try to "reboot into recovery" the phone would get stuck and I would need to pull the battery out. I then read somewhere that the fix was to delete the aboot.img and install the kitkat aboot.img . I tried to do that, and afterwards my phone won't boot at all. It gets stuck and screen turns black and the LED flashes. It sometimes gives me an error message about the bootloader I think. If I try to boot into Download mode, it (sometimes) takes me straight into fastboot instead. When I try to run fastboot and type "devices" I either get back nothing or now I get back a "?". Maybe I don't have the proper driver. Please Please help!!!
Upsdate: Ok so I played with the drivers and although I still can't get a response to "fastboot devices" I tried to flash a recovery and I can get response on the phone to some degree. It says "fastboot: getwarartition-type:recovery" but the cmd prompt on the computer says "cannot load recovery.img".
Maybe I just need to try and flash a bootloader or a download mode. Anyone know where I can get an laf for download mode. Or Have any directions?
Please help me!!!
UPDATE: FIXED IT!!!! What I did was use fastboot to load up an laf.img that I was able to download from someone on here (took a lot of searching to find an laf.img). Even though I was unable to flash the laf (tried a bunch of times and it always gave me that "failure to write" error right at the end), I was able to use fastboot to boot up the laf.img that was on my computer and that got the phone into download mode. Bear in mind that I still wouldn't get the serial number back from "fastboot devices" so if you're having this problem and it doesn't give you the serial number back it's ok. Just try to run some fastboot commands and see if you get a response on the phone, that way you'll know if fastboot is working. Anyway, I was then able to restore it via LGFlashtool. So yup, its fixable!
Click to expand...
Click to collapse
can you please help. adb shows my device and fastboot wont. when i type in fastboot devices it doesnt show anything. tried to run commands but it always gets stuck on waiting for device..
MWGiants said:
(Although from what other people are saying if you have a D855 it will have a locked bootloader and this won't work,
Click to expand...
Click to collapse
What to do with D855 than, my friend have D855 and it's stcked in fastboot mode, doesn't allow to flash anything?
lg g3 f410 stuck at fastboot
i tried the solution it didnot work. phone accepts the cmds but remain stuck at fastboot any other method?
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
piffdaddy420 said:
So i been trying to find the answer to my issue everywhere. everything i try fails.
So basically my Kindle fire hd 8.9 is in a constant boot loop. it goes from orange w/animation, then blue w/animation... then after a period of time it says that it cant boot gives me option to factory restore (which does nothing).
when i have it hooked up to a computer, it connects for 1 second, then quickly disconnects. In device manager it comes up as "jem-pvt-prod-04" with the yellow "!". i even tried to use the amazon drivers from another post on xda, in that split second it would appear in device manager, i would update device and point it to the driver. then i will get an error saying it encountered an error installing Android ADB interface. problem encountered while trying to add driver.
Does anyone have any tips for me. im kinda stuck here and desperate with a very expensive paperweight. very upsetting!
I never tried to root, or mod this kindle fire. this problem happened on its own. or possibly after an update of some sort.
thanks guys.
Click to expand...
Click to collapse
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
monster1612 said:
You're not hopelessly bricked if your Kindle still boots to the orange logo.
Might I ask what Windows version you're using? Newer versions enforce driver signatures, and that enforcement will cause failed installations in Windows 8+ unless you disable the enforcement before installing the drivers. I would also suggest installing ADB and fastboot if you haven't already done so. (Use the 15 second ADB installer - it's on XDA, and it works wonders!)
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, actually i am using windows 10. My thinkpad has windows 7, so i will try to do this using windows 7. i will post back with results. its funny, out of everywhere i looked nobody mentioned windows 8+ having to disable enforcement. actually it will probably just be easier just to disable the enforcement. ill give it a try and report back.
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
piffdaddy420 said:
still no luck. i was able to install the driver. but it still does the same thing. only connects for 1 second when i first turn it on. idk where to go from here? any suggestions?
Click to expand...
Click to collapse
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Completely turn off the kindle and unplug it from your PC if it's connected. Open Command Prompt and type fastboot -i 0x1949 getvar product. Plug in the kindle when you see <waiting for device> outputted. The kindle should now boot into fastboot mode, from which point you can reflash the bootloader, TWRP, and the freedom-boot image in Hashcode's thread.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
ok so im in fastboot mode now. i checked out that thread that you sent. but i have another problem, how am i supposed to get cm and gapps onto the kindle? is there a command i can use to put the files on the internal sd card? and i cant do the adb commands to push the stack, and do the other commands adb since i couldnt get it loaded to begin with, i am not able to enable developer mode. it would be nice if i could do those commands in fastboot mode. there has to be a way to do this....
maybe if someone can send me the stock partitions that they backed up stock boot partititons when they did it. maybe if i flashed them onto my kindle it will allow me to get it to atleast boot up so i can get into adb.
right now this is completely bricked.
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
piffdaddy420 said:
can anyone help me? i just need the original boot loader, boot, recovery... basically whatever was backed up before you flashed it.
i aam looking for the original because i know mine was corrupt to begin with. my theory is if i load the original boot loaders and everything then maybe i can get into the kindle just so i can run the abd commands and then put cyanogenmod on it. unless someone has a suggestion on how i can get my device to be detected by adb ? the furthest i can get into is fastboot.
Click to expand...
Click to collapse
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Once you're in fastboot, you should run these fastboot commands (most of which I ripped from Hashcode's thread) to flash the bootloader, etc.:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 oem recovery
after that, you should be in TWRP, from which point you can use ADB sideload (enable in TWRP through Advanced -> ADB sideload) to flash CM. After running ADB sideload, you need to re-enable it in TWRP for each subsequent zip you want to flash.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
piffdaddy420 said:
Yes, i did all of those steps, however i never did the final step the oem recovery one...
everytime i try it now the screen turns completely red and stays there.
Click to expand...
Click to collapse
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
That's going to be a problem... hold down the Kindle till it completely powers off. Then open command prompt, type fastboot -i 0x1949 getvar product , and plug in the Kindle when you see <waiting for device>. Does this get you into fastboot mode?
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
yes it does
piffdaddy420 said:
yes it does
Click to expand...
Click to collapse
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
monster1612 said:
It sounds like you've got a newer bootloader that's been patched. Go ahead and download the files from Hashcode's thread, and type in all of the commands exactly as given in step 5. Those should fix the red screen issue and allow you to boot normally (or into TWRP, from which point you can ADB sideload CM).
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
piffdaddy420 said:
i followed that exact, i tried it a couple times before you even mentioned it. but i did it again, i redownloaded everything and did it again. just to be sure. but it still continues to do the same thing with the red screen. it goes from kindlefire for 2 seconds then red screen comes across it and stays red. idk what to do. i am so upset.
Click to expand...
Click to collapse
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Do you happen to have any stock OS backups? If you do, you should remain able to flash those over fastboot.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
piffdaddy420 said:
no, i wish i did. the whole reason i started trying this was because the kindle was in a bootloop without even trying to flash it. it would go from kindlefire (orange) then blue, then it will ask me to do factory reset. and nomatter what i did i would keep going in the same bootloop.
so i turned to here for help, and following instructions now i am in this situation.
unfortunatley since i wasnt able to get into the kindle, i was never able to do any abd backups. so i just took my chances with it.
i was actually originally asking if anyone had the original files they can send me so i can try to flash those. atleast i can get it up and running because i really have a feeling this isnt working because i need to push the stack file over thru abd first.
Click to expand...
Click to collapse
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
monster1612 said:
You should be able to separately flash the system.img, boot, and recovery from this tool via fastboot. It's stock OS 8.1.4, but it should work.
Click to expand...
Click to collapse
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
piffdaddy420 said:
ok, it provided me with all the files except the bootloader. i did it step by step... but it only gave me original recovery, and original boot.img but it didnt give me the bootloader (and yes it is still turning red)
Click to expand...
Click to collapse
anyone have any suggestions or can help me with my situation?? i am wondering if maybe someone could just send me the original backed up bootloader, boot, and recovery. i tried the original ones that were posted with that srt file. but it included everything but the bootloader. which is what i need. i know that in original thread they recommended to back up your original files (i was unable to do so because my kindle woulnt boot so i couldnt use adb to back up these files).
so if someone on here can send me the original files so i can try to get my kindle booted back up. that so far is my only theory because i tried everything else. i know people with advance knowledge would be able to help me in a heartbeat. any devs out there wanna help me out? i would greatly appreciate it!
anyone?
Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]
kunalvirk said:
Hi All,
I was running on AEX 4.6, SuperSU, Open Gapps, I wanted to install Google Tez but it doesn't work with rooted devices so after browsing there are some users who are able to use Tez by hiding root (replacing SuperSU with Magisk). I went ahead to SuperSU, tapped on Unroot Device option, accidentally i click on 'yes', when it was showing a message related to bootloader image (I don't know the message though), and now I'm unable to boot into TWRP.
Whenever I try to boot it into recovery, it shows two frames (given as urls) for as long as 1 sec, and then reboots itself.
Need your help guys!!!
Thanks in advance.
https://ibb.co/jCrOqw [frame1]
https://ibb.co/kxOsiG [frame2]
Click to expand...
Click to collapse
Use magisk and hide root for tez app
visheshjain25 said:
Use magisk and hide root for tez app
Click to expand...
Click to collapse
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....
kunalvirk said:
I will brother, but the scenario is that i'm not able to boot to twrp, however I've tried to look for it in ADB fastboot, it is showing my device but nothing is on screen, and the device is listed as unauthorized....
Click to expand...
Click to collapse
Can you access fastboot
selvarajrajkanna said:
Can you access fastboot
Click to expand...
Click to collapse
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks
kunalvirk said:
Thanks for replying brother, I can access fastboot but the screen goes black but it is recognisable in Android MultiTool and under 'adb devices' command but as unauthorized....was wondering if is there any way i can change 'unauthorized' to 'device' so that i can reflash TWRP and ROM.....
Thanks
Click to expand...
Click to collapse
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM
selvarajrajkanna said:
I don't think you can access adb when the phone is on fastboot
Use minimal adb and fastboot
Use
fastboot devices
Command to see if your device is connected
If it is connected then make sure bootloader is unlocked and flash twrp and ROM
Click to expand...
Click to collapse
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....
kunalvirk said:
bootloader is already unlocked, but the problem is that when use adb command 'adb devices' it shows my device as unauthorized.....
Click to expand...
Click to collapse
You can't access abd until your phone is booted into android
Weird, normal here.
selvarajrajkanna said:
You can't access abd until your phone is booted into android
Click to expand...
Click to collapse
So is there any other solution available that can get my phone to woking state.....:crying:
kunalvirk said:
So is there any other solution available that can get my phone to woking state.....:crying:
Click to expand...
Click to collapse
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily
selvarajrajkanna said:
I already told you
Switch off the phone completely
Press volume up and volume down and plug in the data cable
Your device will boot into fastboot
Then you are recover your phone easily
Click to expand...
Click to collapse
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......
kunalvirk said:
Thanks a lot man...!!!.....:good: It worked....actually before there was some driver issues at the machine i was using......
Click to expand...
Click to collapse
Happy to help