I've been a lurker of this forum for years. I just joined and I've always done my research before posting anything. But I'm at a loss right now and I do not know what to do.
I have a Kindle Fire HDX 7" (Thor), yesterday I was trying to flash an Android ROM on it. I got up to the point where I was in TWRP, and I accidentally factory reset the Kindle thru TWRP. When the Kindle rebooted, it showed a screen that said something like...
"Kindle Fire System Recovery; Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue."
The choices it gave me were, "Reboot your Kindle" and "Reset to Factory Defaults"
I rebooted my Kindle as a first choice, and it booted back to the same screen. So then I reset to factory defaults. Nothing worked and it kept bringing me back to that screen. I'm guessing there is no bootloader or anything on the Kindle.
I left the Kindle on for hours as I was trying to find my fastboot cable knowing that I would probably need it to fix this problem. I then turned off the Kindle hours later (press and hold until screen shut off). I did have a full battery prior to trying to put an Android ROM on the Kindle.
This morning I found my fastboot cable, but when I pressed the power button on the Kindle, it will not turn on. No response from it at all. Did I drain the battery?
When I plug my Kindle to my computer using the fastboot cable, it was showing me "QHSUSB_BULK" in the USB device list. I tried ADB, but it says "error: device not found".
When I plug my Kindle to charge, it doesn't show the low battery/charging indicator like it used to.
What should I do next? Is my Kindle permanently bricked?
I need mad help right now!
Try to boot into twrp, but you may bricked your device permanently because you did a factory reset with the default kindle recovery
Sent from my KFTHWI using XDA Free mobile app
MinerBoy004 said:
Try to boot into twrp, but you may bricked your device permanently because you did a factory reset with the default kindle recovery
Sent from my KFTHWI using XDA Free mobile app
Click to expand...
Click to collapse
Okay, one question, how would I boot into TWRP? I ask only because the Kindle is not starting up, and when I plug the fastboot cable, the computer is not recognizing it.
Junava said:
I've been a lurker of this forum for years. I just joined and I've always done my research before posting anything. But I'm at a loss right now and I do not know what to do.
I have a Kindle Fire HDX 7" (Thor), yesterday I was trying to flash an Android ROM on it. I got up to the point where I was in TWRP, and I accidentally factory reset the Kindle thru TWRP. When the Kindle rebooted, it showed a screen that said something like...
"Kindle Fire System Recovery; Your Kindle doesn't seem to be able to boot. Resetting your device to Factory defaults may help you to fix this issue."
The choices it gave me were, "Reboot your Kindle" and "Reset to Factory Defaults"
I rebooted my Kindle as a first choice, and it booted back to the same screen. So then I reset to factory defaults. Nothing worked and it kept bringing me back to that screen. I'm guessing there is no bootloader or anything on the Kindle.
I left the Kindle on for hours as I was trying to find my fastboot cable knowing that I would probably need it to fix this problem. I then turned off the Kindle hours later (press and hold until screen shut off). I did have a full battery prior to trying to put an Android ROM on the Kindle.
This morning I found my fastboot cable, but when I pressed the power button on the Kindle, it will not turn on. No response from it at all. Did I drain the battery?
When I plug my Kindle to my computer using the fastboot cable, it was showing me "QHSUSB_BULK" in the USB device list. I tried ADB, but it says "error: device not found".
When I plug my Kindle to charge, it doesn't show the low battery/charging indicator like it used to.
What should I do next? Is my Kindle permanently bricked?
I need mad help right now!
Click to expand...
Click to collapse
By TWRP you mean safestrap recovery? If you flashed through safestrap other ROM than Nexus for Safestrap 1.0.1 (which one BTW? Did you flash by accident ROM for Hdx 8.9?) that could be the first reason for bricking your kindle... Safestrap is not TWRP, is only TWRP based and works differently than TWRP 2.8.5.0, also safestrap is located on system partition, but TWRP 2.8.5.0 when installed is flashed to recovery partition...
Doing factory reset through safestrap should be relatively safe unless you mess with advanced wipe and delete/wipe system partition - this effectively erase content of /system including safestrap recovery, this could be the second reason for bricking your kindle.
If you had installed real cuber signed TWRP 2.8.x.x, then the only thing I can think of is that you tried to flash one of amazon update bins with TWRP, these bins when installed replace content of the recovery partition with Amazon FireOS recovery, successfully deleting real TWRP in the process, but this should end with booting to FireOS...
Junava said:
Okay, one question, how would I boot into TWRP? I ask only because the Kindle is not starting up, and when I plug the fastboot cable, the computer is not recognizing it.
Click to expand...
Click to collapse
Just hold the volume up button (+) when it's booting.
However, I'm not really sure of your situation, because TWRP should've replaced the stock recovery.
I finally got it to turn on somehow. And this is the screen that it's giving me (see attachment). I tried both of the options given and it'll bring me back to the same screen.
Also, before I was able to power on the Kindle, it'll say QHSUSB BULK in the connected usb devices when I use my fast-food cable on it. But when I have the Kindle powered on it says Unknown Device.
If I can get the Kindle to respond to adb I can probably work from there. But my computer is not recognizing it.
What version of fireos you had? maybe is possible to unlock bootloader.. but you should know mmc manfid and serial. We don't know yet how to get emmc serial from bootloader only.
dpeddi said:
What version of fireos you had? maybe is possible to unlock bootloader.. but you should know mmc manfid and serial. We don't know yet how to get emmc serial from bootloader only.
Click to expand...
Click to collapse
I had to rollback as I was following the guide on the post in the developmental forum on here. Will the manufacturer id be on the box? I still have the original box for the Kindle.
Sent from my VS980 4G using XDA Free mobile app
Actually you can get it from adb without root
My Kindle is not communicating with adb. I've been trying all week and doing a lot of researching. I either get an "Unknown Device" or "QHSUSB BULK" in the connected usb list.
Sent from my VS980 4G using XDA Free mobile app
Dies it go in fastboot mode with vol+ vol- power?
Junava said:
I finally got it to turn on somehow. And this is the screen that it's giving me (see attachment). I tried both of the options given and it'll bring me back to the same screen.
Also, before I was able to power on the Kindle, it'll say QHSUSB BULK in the connected usb devices when I use my fast-food cable on it. But when I have the Kindle powered on it says Unknown Device.
If I can get the Kindle to respond to adb I can probably work from there. But my computer is not recognizing it.
Click to expand...
Click to collapse
How did you get to that screen? do you remember what you pressed?
dpeddi said:
Dies it go in fastboot mode with vol+ vol- power?
Click to expand...
Click to collapse
Nope.
Silverclaw280 said:
How did you get to that screen? do you remember what you pressed?
Click to expand...
Click to collapse
I held the power button for maybe a good 30 seconds and it powered on and took me to that screen. I'd usually have to keep trying to get the Kindle to power on, and when I do, that screen is all it'll do.
Turn kindle off.. then press and keep pressed vol+ and vol- and keep them pressed. Turn on kindle while pressing both volume. You should enter into fastboot. If we found a relation between emmc serial and kindle serial number you should be able to fix it. (I think your boot.img is corrupted)
Silverclaw280 said:
How did you get to that screen? do you remember what you pressed?
Click to expand...
Click to collapse
I was able to get back to that screen by following the steps in this quoted post.
My Kindle gets the same status. It was safestraped, locked on 3.2.8. Tried to update it with OTA to 4.1.1, it downloaded firmware, checked and rebooted, after that device won't boot up and on connect to pc detects as QHSUSB_BULK. The only way i found is to ask replacement at support
modi said:
My Kindle gets the same status. It was safestraped, locked on 3.2.8. Tried to update it with OTA to 4.1.1, it downloaded firmware, checked and rebooted, after that device won't boot up and on connect to pc detects as QHSUSB_BULK. The only way i found is to ask replacement at support
Click to expand...
Click to collapse
(reposting as a warning to those who may stumble across this thread)
This seems to be the recent fate for many who have rolled back to 3.2.8 and not blocked OTA using HDX Toolkit or an equivalent blocker (renaming otacerts is not reliable). It appears Amazon attempts to push an update that ultimately corrupts the boot partition. Not much you can do to fix it with current techniques/exploits.
If the device is still under warranty Amazon will likely replace it. Just say it died during an update.
Related
My wife started her Kindle Fire HDX 7” 5 days ago it took a while thinking and then went to the Fastboot screen. The device has not been rooted and is just a straight forward Kindle Fire HDX.
I tried restarting the Kindle etc. but every time it still only boots up to Fastboot screen, I connected the Kindle up to my PC's while I can not see any files on it, I can see the device.
Is there any way I can fix it or does she have a expensive paper weight?
Need more info
hilsdon1 said:
My wife started her Kindle Fire HDX 7” 5 days ago it took a while thinking and then went to the Fastboot screen. The device has not been rooted and is just a straight forward Kindle Fire HDX.
I tried restarting the Kindle etc. but every time it still only boots up to Fastboot screen, I connected the Kindle up to my PC's while I can not see any files on it, I can see the device.
Is there any way I can fix it or does she have a expensive paper weight?
Click to expand...
Click to collapse
Have you tried getting into recovery by holding down the Power and VolumeUp(+) buttons together?
draxie said:
Have you tried getting into recovery by holding down the Power and VolumeUp(+) buttons together?
Click to expand...
Click to collapse
Yes tried this still only boots to fast boot screen?
Try this: http://forum.xda-developers.com/showpost.php?p=58270390&postcount=4
EncryptedCurse said:
Try this: http://forum.xda-developers.com/showpost.php?p=58270390&postcount=4
Click to expand...
Click to collapse
Thanks for this it did not work but came close.
The first command fastboot -i 0x1949 oem idme bootmode 4000 comes back with a message on the Kindle and the CMD screen, as:-
Fail: oem idme not allowed for locked HW.
The second command fastboot -i 0x1949 reboot
reboots the Kindle back to fastboot menu.
Scary... but probably a timing issue only
hilsdon1 said:
Yes tried this still only boots to fast boot screen?
Click to expand...
Click to collapse
Try a few more times and do it "carefully" !
Seriously: last weekend I was messing around with the 4.5.2 kernel (boots, adb works, but no screen),
and at some point during my endevaours I got into this same scary situation, but I managed to get back to TWRP
after a few tries. I think it could be a timing issue. Easy to get confused when stressed...
So, here's my suggesttion:
Hold the Power button until the unit switches off.
Then hold Power + VolumeUp until the display lights up.
Let go off the buttons.
With some luck your recovery will show up.. keeping fingers crossed!
Thanks for the reply, have tried over 30 times still no luck. Will carry on trying.
Hate that white kindle fire logo! Especially as of all our machines this was the only untouched one. All the others have been tweeked or rooted I was not allowed to touch this one!
Oh well pretty paper weight.
hilsdon1 said:
Thanks for the reply, have tried over 30 times still no luck. Will carry on trying.
Hate that white kindle fire logo! Especially as of all our machines this was the only untouched one. All the others have been tweeked or rooted I was not allowed to touch this one!
Oh well pretty paper weight.
Click to expand...
Click to collapse
Have you tried Amazon's customer service?
They tend to be fairly helpful and your device was not even tampered with, you say...
I'd be interested to hear what they have to say.
A replacement would be a likely option..
draxie said:
Have you tried Amazon's customer service?
They tend to be fairly helpful and your device was not even tampered with, you say...
I'd be interested to hear what they have to say.
A replacement would be a likely option..
Click to expand...
Click to collapse
Actually, having read through the fastboot source code, I think I may have found another solution
using the "fastboot -i 0x1949 update magic.zip" command, where you' ll need to get a pristine
boot.img and system.img from a working Kindle and zip those along with an android-info.txt file
to create magic.zip... (I'll post more details, if needed, when I have time; now, off to bed.!)
Interestingly, the "update" command is NOT blocked on my otherwise locked HDX 8.9!
I'd expect signature checking (if not at flash time, then at boot time); so, be careful what
you put in your zip file.
Thanks everyone for help and advice in the end the device had to be replaced. One thing I learnt was to hold the power button down for 40 seconds and then press power button and + button. Amazon support gave me that one. To do factory reset.
However even after that it started up but to Encryption failed screen do factory reset, even after factory reset would go no further
Robert
I think i bricked my kindle fire HDX 7 it wont turn on any more when i flashed bootloader via twrp (i think?), are there any fixes or solutions? or none?
Silverclaw280 said:
I think i bricked my kindle fire HDX 7 it wont turn on any more when i flashed bootloader via twrp (i think?), are there any fixes or solutions? or none?
Click to expand...
Click to collapse
more details, please. wont turn on? not even the grey kindle logo?
Nope no logo or anything I dont remember what version I had but when I flashed bootloader in twrp it said successfully so I thought everything was ok then I rebooted and it wont turn on.
Silverclaw280 said:
Nope no logo or anything I dont remember what version I had but when I flashed bootloader in twrp it said successfully so I thought everything was ok then I rebooted and it wont turn on.
Click to expand...
Click to collapse
I'm going thru the exact same issue. It will not turn on. Not even a back lit black screen will show. I posted a thread over here http://forum.xda-developers.com/kindle-fire-hdx/help/kindle-fire-start-t3059515
Junava said:
I'm going thru the exact same issue. It will not turn on. Not even a back lit black screen will show. I posted a thread over here http://forum.xda-developers.com/kindle-fire-hdx/help/kindle-fire-start-t3059515
Click to expand...
Click to collapse
sorry to hear that i hope this will get fixed soon...
Junava said:
I'm going thru the exact same issue. It will not turn on. Not even a back lit black screen will show. I posted a thread over here http://forum.xda-developers.com/kindle-fire-hdx/help/kindle-fire-start-t3059515
Click to expand...
Click to collapse
Try long pressing (20 sec) the power button. Not a solution but may provide additional information that could aid in further recovery. Also try power & volume up button (+) together as suggested by EncryptedCurse in the other forum. Release the power button immediately but keep volume up depressed until there is a response.
Also try keeeping the power button pressed for about 2 minutes (count them) and see if that works.
My Kindle fire HDX 7 i think bricked any solution?
I was trying to root my Kindle fire HDX 7 for android apps and google apps on it. it was successfully rooted and google play services working on it perfectly. Than suddenly google play stop working on it. but games installed on it working properly. Then i go to recovery option and press the Wipe button "Cache and Dalvik Cache". after that my Kindle fire HDX 7 boot and stuck on Kindle fire starting Grey logo. I tried to factory reset but still keep stuck on start logo. While connected to PC, only hear one connectivity beep with PC and in device manager only shows connectivity as MTP USB device. But no device show in my computer. Snapshot attached. Please assist any solution.
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon's wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Leav320 said:
Help! I have a newer HDX 7 that is stuck trying to reboot. The device powers up to the gray kindle fire screen but sits there for a minute or so and then the screen flashes and it starts all over. The device does not recognize the power button. I've tried the hold the button for 40 seconds to reset but it just keeps going through this loop while holding the power button. When I connected it to my PC (Win7), it does not see the device. If I connect another Andriod device, it sees it imeadiately.
I'm a complete noob with this but I'm actually in IT, just not in this area. This is my sons device so I'm not sure exactly what he was doing at the time it started this but my guess would be playing MineCraft. Amazon''s wonderful support says it just needs to be replaced but it's out of warranty. My son and I were just about to start an online coding course so I'd like to get this back up and running so we can start that. Any help would be appreciated. After searching the web, you guys seem to be the only ones able to root or fix any software/os issues with these devices.
Thanks,
Doug
Click to expand...
Click to collapse
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Davey126 said:
Your options are limited given the device is largely invisible via tether (even then there would be little recourse as adb is probably disabled). Did you try a factory reset? Amazon's crippled recovery environment can be accessed via power + vol-up from a cold start. Release the power button after the gray Kindle logo appears. If the recovery menu comes up the only option is 'factory reset'. I realize you may not be able to access recovery given the non-responsive power button.
Any chance you son is old/savvy enough to trying rooting the device? The symptoms suggest either a failed automatic update (rare but it does happen) or botched attempt to root via the wrong method. Obviously a spontaneous hardware failure is also possible albeit unlikely.
Do you know what version of Fire OS was running just prior to the boot loop?
Click to expand...
Click to collapse
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
lekofraggle said:
There is still a small chance adb may help even if the device is not recognized by Windows explorer. However, if as Davey said, it is disabled, things are limited.
Again, do you know what version is you were running?
Have you installed adb?
Have you tried recovery?
Sent from my KFTHWI using Tapatalk
Click to expand...
Click to collapse
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Leav320 said:
No, Unless it updated automatically, it was the same version that was on there when it was delivered around 4/14.
No, My son would not have tried rooting this on his own.
I was incorrect when I stated that the system wasn't recognizing the power button. When I try the hold the power button for 40 secs or the Power button + Vol up button to restart, the boot loop gets shorter.
I have installed ADB on my PC but it doesn't see the device (although I'm not sure I'm using it correctly). What command should I be issuing to see if the device is connected. If I use "adb devices" I get the response in the attached screen shot.
If by recovery, you mean the recovery on the device, the power+volume up button doesn't work.
I appreciate all of the help!
Click to expand...
Click to collapse
Given the delivery date and age of device I STRONGLY recommend you reach out to Amazon for a replacement vs trying to resolve on your own. A new version of Fire OS is currently rolling out which MAY have triggered the behavior you are seeing. Bit of a bummer given your son's course plans but a worthwhile delay IMHO.
I agree with Davey.
Sent from my KFTHWI using Tapatalk
Hi,
I have amazon fire hd6.
Yesterday i have rooted using kingroot 4.1. And it was working fine.
I have installed google apps, and it was working for a minute or so.
Than i guess google play had an update and stopped working.
Than i went all stupid, and tried removing google packages from the programs.
The first one was google search and fter removing it the system became unstable so i rebooted and voila stuck at fire logo screen.
Actually, at this stage i can see kindle in device manager as MTP device, and can browse the files from windows. When i connect usb it gives the charging sound so everything seems to work but launcher never cames.
I tried adb but shows no devices, as usb debugging was off on the kindle side.
Is there anything i can do?
Some people are talking about a recovery menu holding power and both volume buttons but i could never get it. Am i doing something wrong?
Any suggestions?
ygulsen said:
Hi,
I have amazon fire hd6.
Yesterday i have rooted using kingroot 4.1. And it was working fine.
I have installed google apps, and it was working for a minute or so.
Than i guess google play had an update and stopped working.
Than i went all stupid, and tried removing google packages from the programs.
The first one was google search and fter removing it the system became unstable so i rebooted and voila stuck at fire logo screen.
Actually, at this stage i can see kindle in device manager as MTP device, and can browse the files from windows. When i connect usb it gives the charging sound so everything seems to work but launcher never cames.
I tried adb but shows no devices, as usb debugging was off on the kindle side.
Is there anything i can do?
Some people are talking about a recovery menu holding power and both volume buttons but i could never get it. Am i doing something wrong?
Any suggestions?
Click to expand...
Click to collapse
I think your problem is nothing too seriously. All you have to do is factory reset through recovery. First turn off your tablet, then hold power + volume up at the same time. When to see amazon logo, quickly release power button. Bam, in recovery.
first check the adb shell and see if you have su access. then check adb logcat to see if it is something you can fix
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
nvm just saw what you said about adb devices... This device is way too easy to brick and we currently have no restore method. I ended up replacing the motherboard on my bricked fire hd6. I bought a fire hd6 with a broken screen on ebay and replaced my device with that motherboard
droidnext said:
I think your problem is nothing too seriously. All you have to do is factory reset through recovery. First turn off your tablet, then hold power + volume up at the same time. When to see amazon logo, quickly release power button. Bam, in recovery.
Click to expand...
Click to collapse
are you sure this is the right procedure for this device?
tried this 100s times but no recovery.
actually i am thinking that this device does not have a recovery thing. As with just 3 buttons i have tried every alternative.
ygulsen said:
are you sure this is the right procedure for this device?
tried this 100s times but no recovery.
actually i am thinking that this device does not have a recovery thing. As with just 3 buttons i have tried every alternative.
Click to expand...
Click to collapse
I just try to help you how to go to recovery. I made 10 out of ten everytime. You just need 2 button, not 3 (power + volume up). Unless you're trolling. Good luck and bye bye
droidnext said:
I just try to help you how to go to recovery. I made 10 out of ten everytime. You just need 2 button, not 3 (power + volume up). Unless you're trolling. Good luck and bye bye
Click to expand...
Click to collapse
you got me wrong mate, i have tried your suggestion and actually thx for that. But after amazon logo there goes the fire logo and nothing happens.
This is for amazon fire 4th gen hd 6 right?
And by 3 buttons, i mean, i have tried every two button alternative and no recovery. The device has only 3 buttons.
Maybe my recovery is also broken?
Thx anyways.
alright guys, so here's the story. just yesterday i bought a brand new lg v10, got it home and the first thing i did was root the device and used ADB to load TWRP following the instructions here on SDA to a T for the ROOT/RECOVERY setup. and it worked. all was fine and dandy, the first time i booted into TWRP via ADB after root i got in, flashed a debloated ROM + xposed and again, everything went fine.. loaded into the OS of the new ROM, went through setup, turned on USB debugging, clicked always allow this computer, installed xposed app yadayadayada. I then, using ADB again, loaded into TWRP. i created a backup there just in case something went wrong with the changes i was about to make and once the backup was complete i loaded back in to the OS. at this point i thought i had done everything right and was confident that if i made system changes that didn't work out i could just flash the phone with TWRP from the backup i made. right? WRONG! ...apparently... so anyways, i made my first change, which was to use a NONROOT app called texdroider or whatever to change my DPI (as i have done with a couple phones previously without much issue) but i didn't take into account that stupid second screen... making the DPI changes system wide, as i'm sure those of you that know this phone are aware, causes the systemUI to crash with an error.. making the OS unusable.. so i tried to load into TWRP by holding the volume down and power button.. but instead it just booted me to the factory recovery.. not TWRP... the phone is unusable within the OS, i can't get the phone to connect to adb to boot into twrp as i had previously, i can't seem to get the phone into download mode, and i can't boot to TWRP and the OS is junk at this point.. but it DOES say on the "LG" screen that the bootloader is unlocked so i'm really hoping i'm not completely out of luck.. but i am not sure what to do at this point. does anyone here know of anything i can try to get into a custom recovery at this point? if i could get into TWRP my SD card in the phone has a backup, the original image, not to mention i could pull the SD card and add anything i need via my pc and then boot back to twrp etc etc and i would have no issue fixing the phone... i really don't understand what i did wrong or why i can't boot to my custom recovery but i'm at a loss.. i'm just looking for a way to force the phone into a custom recovery... or restore the original factory image.. if you have any advice at all i would really appreciate it.
Thanks for reading
**UPDATE** this may or may not make things much easier... but I got download mode working!! so at least there's that, still no custom recovery and i'm currently looking for a KDZ or TOT file to flash via lg flash tool... hopefully that makes things easier..
When you say you got to the factory recovery, what was that, an Android on its side or something asking you to factory reset your device? If it was the factory reset screen, if you select yes and then yes, it will take you to TWRP if you have it installed. If you don't it will factory reset your device.
ngoblirsch said:
**UPDATE** this may or may not make things much easier... but I got download mode working!! so at least there's that, still no custom recovery and i'm currently looking for a KDZ or TOT file to flash via lg flash tool... hopefully that makes things easier..
Click to expand...
Click to collapse
To boot into recovery from power off, you hold volume down & power. When you see the LG logo release and press power while continuing to hold volume down. Then as said above, it come up as a factory reset, select yes each time, and it should boot into twrp, providing you installed it correctly.
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
When you say you got to the factory recovery, what was that, an Android on its side or something asking you to factory reset your device? If it was the factory reset screen, if you select yes and then yes, it will take you to TWRP if you have it installed. If you don't it will factory reset your device.
Click to expand...
Click to collapse
it was a screen asking me to do a factory reset, i click yes, it asks to confirm, i click yes again and then it "successfully" factory resets my phone... it shows the android factory reset symbol that its resetting, then says that its "optimizing apps" and goes through that whole process.. but when it finally loads the "welcome" screen (so i know for a fact that some sort reset has taken place) i get the same "systemui has crashed" error and the OS is unusable and won't connect to my computer.. idk why i can't access TWRP.. i booted to it 3 times before this happened, though never by the hardware buttons on the phone.. everytime i booted to TWRP i had used ADB to boot to TWRP.. what makes me the most sad is that i have a nandroid backup on my SD card... but i can't flash it without recovery.. which i can't install on the phone without getting into the OS..
is there any way to install TWRP or even boot to a temporary TWRP so that i can do so? if i can flash my nandroid i'm saved.. if i can get into a custom recovery i'm saved.. if i can find a .kdz file to flash, i'm saved... if i can get my phone to be recognized by my computer/adb i'm saved.... there simply has to be a way to unbrick this phone...
ZDeuce2 said:
To boot into recovery from power off, you hold volume down & power. When you see the LG logo release and press power while continuing to hold volume down. Then as said above, it come up as a factory reset, select yes each time, and it should boot into twrp, providing you installed it correctly.
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
well i seem to have somehow NOT installed TWRP correctly because it just proceeds to factory reset my phone.. which for some odd reason doesn't reset the DPI... leaving me stranded... is there any way to get ADB to see my device in its present state? my computer makes the device recognition noise when i enter download mode and i can see it in device manager but not my computer or ADB
I've had this phone just over 2 months but I'm not positive, is download mode the same as the bootloader on this device? If so, fastboot commands should work, and you can flash TWRP again, or do 'fastboot boot TWRP_filename' and it will boot TWRP temporarily.
Oh, and the factory reset just wipes your data, but otherwise doesn't restore your system to factory state. That's why your dpi change remained.
YrrchSebor said:
I've had this phone just over 2 months but I'm not positive, is download mode the same as the bootloader on this device? If so, fastboot commands should work, and you can flash TWRP again, or do 'fastboot boot TWRP_filename' and it will boot TWRP temporarily.
Oh, and the factory reset just wipes your data, but otherwise doesn't restore your system to factory state. That's why your dpi change remained.
Click to expand...
Click to collapse
dude.. then what good is a factory reset?!? like seriously... and yeah, i tried that but i can't get adb to connect in download mode.. the device doesn't show up when I type "adb devices" like it did when i first rooted it. ... and i thought i followed the instructions exactly as it was laid out from this link.
http://forum.xda-developers.com/tmobile-lg-v10/general/guide-how-to-root-lg-v10-easy-t3274699
i think somewhere in there i must have missed something and ended up only booting into twrp temporarily.. which is certainly possible since i never boot to twrp during that initial process from the hardware keys or soft keys.. always through adb.. the phone was already plugged in.. typing the command was a couple keys away..
is there anyway to get TWRP on to the phone now? or am i screwed :'(
Well, it is a factory restore for the average user, because the average person isn't modifying their system. But no, I'm sure you're not screwed. If you're in the bootloader you can't use adb, you're already past that step, so you can skip to the fastboot part. What happens when you type fastboot devices? If the phone shows up then you can either fastboot flash or boot TWRP..
YrrchSebor said:
Well, it is a factory restore for the average user, because the average person isn't modifying their system. But no, I'm sure you're not screwed. If you're in the bootloader you can't use adb, you're already past that step, so you can skip to the fastboot part. What happens when you type fastboot devices? If the phone shows up then you can either fastboot flash or boot TWRP..
Click to expand...
Click to collapse
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
ngoblirsch said:
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
Click to expand...
Click to collapse
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
ngoblirsch said:
from what screen should i be attempting this? hold volume up with phone off and plug in to computer to enter download mode? should i try it at the factory reset screen (volume down plus power)? those are the only two screens i seem to have access to.. in download mode my pc/adb just doesn't recognize the phone.. it doesn't show up as a proper device like it did before this whole thing and in that factory reset mode i get nothing.. the download mode seems like its built for LG and runs from different drivers because in device manager it shows up with an error code that it couldn't start the device (this was not the case when i was using adb to unlock the bootloader and then using the bootloader to boot to TWRP..) what am i missing?
and hey, thank you so very much for taking time out of your day to help me. I really do appreciate it.
Click to expand...
Click to collapse
Hold volume down and plug the cable in, already have completed in terminal.....
Sent from my LG-H901 using Tapatalk
YrrchSebor said:
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Click to expand...
Click to collapse
planetbeen said:
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
Click to expand...
Click to collapse
ZDeuce2 said:
Hold volume down and plug the cable in, already have completed in terminal.....
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
@ngoblirsch Along with the information provided in these suggestions and what you have said, you need to reinstall your LG/fastboot drivers on your PC while in fastboot mode
YrrchSebor said:
No problem buddy, and sorry for the confusion. You want to be on the bootloader screen, so here is what you can do: turn the phone off(or remove the battery if you have to, and put it back in), plug the usb cable into the computer only(not phone), hold volume down on phone, plug the usb cable into the phone. That should get you into the bootloader, and then you should be able to fastboot flash or fastboot boot TWRP.
Click to expand...
Click to collapse
OH DEAR GOD THANK YOU!!!!
I spent all damn day yesterday trying to figure out how to get to the bootloader on this phone.. everything i read online said to hold volume down PLUS power while plugging it in and it was NOT working lmao. dude, thank you so much. after i read that comment here it took me about 30 seconds to connect to adb and boot to TWRP. This thread can be listed as RESOLVED!
Thanks again!! can't wait to start tweaking this awesome phone!
planetbeen said:
Waiting for a resolution to this thread!
I'm pulling for you from the cheering section. (otherwise known as afraid to do it myself section!)
I'm pretty sure others have come through this exact situation unharmed (I've pretty much read every thread here.) so it's only a matter of time before you get this figured out.
Here's hoping it's sooner than later.
Sorry I can't offer more besides encouragement!
Sent from my pretty nifty brand new LG V10
Click to expand...
Click to collapse
Well I appreciate the encouragement, it sure seems to have helped! Issue has been resolved. ended up that i just didn't know the hardware key combination to get to the bootloader/fastboot mode without being already connected to adb. nothing that i could find online said to hold volume down while plugging it in to a computer. as soon as i was able to do so i connected to adb and it was a breeze from there; I am now back with an OS AND a customer recovery properly installed on the device!! I will be hanging around these forums for as long as i have this phone so i'm sure i'll bump into you guys! absolutely love the community here on XDA, you guys are freaking awesome!!
ngoblirsch said:
OH DEAR GOD THANK YOU!!!!
I spent all damn day yesterday trying to figure out how to get to the bootloader on this phone.. everything i read online said to hold volume down PLUS power while plugging it in and it was NOT working lmao. dude, thank you so much. after i read that comment here it took me about 30 seconds to connect to adb and boot to TWRP. This thread can be listed as RESOLVED!
Thanks again!! can't wait to start tweaking this awesome phone!
Click to expand...
Click to collapse
Glad you got it fixed, and welcome to the V10 device and forums!