I know this has probably been covered to death in various posts here but I have tried a lot of what is written here and haven't been able to fix my hdx. I am currently stuck in a fastboot loop. Though sometimes it boots into bulk mode, which is strange, but I can get it back into fastboot eventually. Anyone out there able to walk me through steps to figure out what I did and get it back to working, preferably with TWRP and Lineage OS installed. I will just take getting back in to Fire OS atm sine this is giving me a headache. Anyway, I am using a win 10 machine and have fastboot ready on the KF right now. I am going to leave it this way for the time being. I originally used this https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240 to go about getting this to where I could install a custom ROM but missed the adb composite drivers before I ran the unlock.bat. I have since gotten that straightened out and even ran the unlock.bat and it succeeded. I have reflashed recovery.img and a boot.img though it isn't the right one. (I was desperate and tried some dumb stuff and flashed the boot.img from my lineage os zip via fastboot)(yeah I know, stupid, but like I said, desperate)
Enough rambling for now. Anyway think they can help me with this issue? @draxie maybe? or @Davey126.
Please and thank you!
FumundaSaq said:
I know this has probably been covered to death in various posts here but I have tried a lot of what is written here and haven't been able to fix my hdx. I am currently stuck in a fastboot loop. Though sometimes it boots into bulk mode, which is strange, but I can get it back into fastboot eventually. Anyone out there able to walk me through steps to figure out what I did and get it back to working, preferably with TWRP and Lineage OS installed. I will just take getting back in to Fire OS atm sine this is giving me a headache. Anyway, I am using a win 10 machine and have fastboot ready on the KF right now. I am going to leave it this way for the time being. I originally used this https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240 to go about getting this to where I could install a custom ROM but missed the adb composite drivers before I ran the unlock.bat. I have since gotten that straightened out and even ran the unlock.bat and it succeeded. I have reflashed recovery.img and a boot.img though it isn't the right one. (I was desperate and tried some dumb stuff and flashed the boot.img from my lineage os zip via fastboot)(yeah I know, stupid, but like I said, desperate)
Enough rambling for now. Anyway think they can help me with this issue? @draxie maybe? or @Davey126.
Please and thank you!
Click to expand...
Click to collapse
Above my pay-grade upon learning you flashed the LineageOS boot.img. Most likely will need to fix this (if repairable) from bulk mode. I believe @draxie is the only one with sufficient knowledge to take this on; also know he's usually quite busy.
Davey126 said:
Above my pay-grade upon learning you flashed the LineageOS boot.img. Most likely will need to fix this (if repairable) from bulk mode. I believe @draxie is the only one with sufficient knowledge to take this on; also know he's usually quite busy.
Click to expand...
Click to collapse
Thanks anyway. I know i screwed it up pretty badly but hoping since i can still get into fastboot and bulk mode that maybe it's still salvageable. Not holding my breath at this point. Thanks again
You should be fine
FumundaSaq said:
Thanks anyway. I know i screwed it up pretty badly but hoping since i can still get into fastboot and bulk mode that maybe it's still salvageable. Not holding my breath at this point. Thanks again
Click to expand...
Click to collapse
As long as your HDX responds to fastboot commands as expected,
your desired outcome should be achievable. Now, since you got
desperate and did a bunch of random stuff, let's start with checking
if that HDX is unlocked. (I suspect it isn't, otherwise that boot.img
from Lineage should just work.)
Code:
fastboot -i 0x1949 oem idme \?
Next, if it were still locked, do you have the unlock code?
If so, try to unlock, and if that works, see if that fixes booting.
Code:
fastboot -i 0x1949 flash unlock unlock.code
If the unlock fails or you're still having problems after a successful
unlock, I'd need to get some clarity regarding that bulk mode you
mention. Since it's -apperently- entered spontaneously (is it?) and
appears to be recoverable without too much effort(correct?), I'd
expect this to be the Sahara-style serial communication bulk mode,
and not the one that exposes all partitions to the host OS (you'd know,
since the latter generates a ton of dialogs asking to format those).
What cable (or cables) are you using? That serial bulk mode can be
consistently entered with a fastboot cable, but I find the kind of
intermittent triggering you describe rather strange...
Ok. First of, thanks @draxie for helping. Second i am including the pic i took of the txt on hdx screen after input of both commands. I honestly don't know what i am looking for so i will let you see it and tell me.
As for the bulk mode, it is the mode that produces the 8 or 9 drives in Windows(and Linux). The intermittent part is that sometimes it isn't recognized correctly by Windows. Sometimes it is recognized as the qloader 9008 like it should be. Sometimes Windows says it is an unrecognized usb device.
Hopefully that makes sense.
FumundaSaq said:
Ok. First of, thanks @draxie for helping. Second i am including the pic i took of the txt on hdx screen after input of both commands. I honestly don't know what i am looking for so i will let you see it and tell me.
As for the bulk mode, it is the mode that produces the 8 or 9 drives in Windows(and Linux). The intermittent part is that sometimes it isn't recognized correctly by Windows. Sometimes it is recognized as the qloader 9008 like it should be. Sometimes Windows says it is an unrecognized usb device.
Hopefully that makes sense.
Click to expand...
Click to collapse
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
draxie said:
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
Click to expand...
Click to collapse
@draxie - keep in mind he can boot a suitable twrp image from fastboot if the bootloader is unlocked. Might provide an expedited path to a bootable system partition.
draxie said:
Well, that makes only partial sense to me,
since getting into that bulk mode normally
requires active effort, which does not quite
match my interpretation of what you wrote
(i.e. "sometimes boots into", which sounds
unprovoked/spontaneous to me).
BUT, that's the better scenario; so, let's
just celebrate briefly and move on.
The image indicates that the bootloader is
now unlocked. I think it may have already
been unlocked before, but I'm not sure.
And, frankly, it doesn't really matter now.
What I gather from your original post,
you end up back in fastboot when you
reboot. Is that still the case?
What happens if you hold Volume-Up
and Power to reboot? No TWRP?
Click to expand...
Click to collapse
Holding volume up and power just gets me back into fastboot. As for the sometimes boots into bulk mode, i didn't really mean spontaneous just that there are times when i tried to force it into bulk mode that Windows sar it only as unrecognized usb device and other times Windows sees it correctly. It only attempted bulk mode when i tried to put it there. Sorry for the misunderstanding. I'm new to this bulk mode thing.
If i remember, i put it into bulk mode using the commands
Fastboot -i 0x1949 erase aboot
Fastboot -i 0x1949 reboot
I probably messed up something doing that so feel free to berate me for that
I will follow whatever instructions you have. I really appreciate the help.
@draxie Just tested the volume up + power again and booted into twrp! Not sure why it never did before. Maybe I am just an idiot or didn't wait long enough. I did reboot with vol up and power but got a grey kindle logo and then nothing. Connected it to my pc and tried adb devices and there was one. The SN was strange, it read 0123456789abcd which obviously isn't correct. But I sent the command adb reboot recovery and then let it shut off, held the vol up and power and now I'm in twrp!
I sideloaded Lineage os and gapps now. It is working! Thanks for the help!!! Not sure what I was doing wrong before but I appreciate your guidance. Thanks to both @draxie and @Davey126 for bearing with me. You guys have the patience of Saints!
FumundaSaq said:
I sideloaded Lineage os and gapps now. It is working! Thanks for the help!!! Not sure what I was doing wrong before but I appreciate your guidance. Thanks to both @draxie and @Davey126 for bearing with me. You guys have the patience of Saints!
Click to expand...
Click to collapse
I'm still confused by your story, but I'm glad it worked in the end.
draxie said:
I'm still confused by your story, but I'm glad it worked in the end.
Click to expand...
Click to collapse
I realize that you probably are. For all I know it would have worked to begin with. I don't know what happened. I'm just strange that way.
If you have a specific question I would be glad to try to answer it.
FumundaSaq said:
Holding volume up and power just gets me back into fastboot. As for the sometimes boots into bulk mode, i didn't really mean spontaneous just that there are times when i tried to force it into bulk mode that Windows sar it only as unrecognized usb device and other times Windows sees it correctly. It only attempted bulk mode when i tried to put it there. Sorry for the misunderstanding. I'm new to this bulk mode thing.
If i remember, i put it into bulk mode using the commands
Fastboot -i 0x1949 erase aboot
Fastboot -i 0x1949 reboot
I probably messed up something doing that so feel free to berate me for that
I will follow whatever instructions you have. I really appreciate the help.
@draxie Just tested the volume up + power again and booted into twrp! Not sure why it never did before. Maybe I am just an idiot or didn't wait long enough. I did reboot with vol up and power but got a grey kindle logo and then nothing. Connected it to my pc and tried adb devices and there was one. The SN was strange, it read 0123456789abcd which obviously isn't correct. But I sent the command adb reboot recovery and then let it shut off, held the vol up and power and now I'm in twrp!
Click to expand...
Click to collapse
I, too, am stuck in fastboot mode after I seemingly flashed TWRP and aboot. Could you elaborate what you did to fix the issue? I held power button + Vol UP and no TWRP mode, just goes back to fastboot...I think my issue is I forgot to run get_code.bat before erasing aboot, and now I can't unlock nor boot into the stock ROM. Is there anyway to unlock through just fastboot or even restore the stock ROM? I don't mind reloading and going through the process all over again.
This was the thread I was following: https://forum.xda-developers.com/ki...loader-firmware-t3463982/page106#post76073370
Praxxer1 said:
I, too, am stuck in fastboot mode after I seemingly flashed TWRP and aboot. Could you elaborate what you did to fix the issue? I held power button + Vol UP and no TWRP mode, just goes back to fastboot...I think my issue is I forgot to run get_code.bat before erasing aboot, and now I can't unlock nor boot into the stock ROM. Is there anyway to unlock through just fastboot or even restore the stock ROM? I don't mind reloading and going through the process all over again.
This was the thread I was following: https://forum.xda-developers.com/ki...loader-firmware-t3463982/page106#post76073370
Click to expand...
Click to collapse
Cross post - answered in other thread.
Related
Hey Guys, could sure use your help... i updated my 10.1 le yesterday and that went thru fine. Later on i was playing and watching youtube and it sent my tablet into a boot loop and i cant seem to fix it. any help would be appreciated thanks in advance.
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
LovellKid said:
Mine did the same thing when i was streaming music. Not even Odin brought it back. I used adb to reboot into stock 3e recovery and wipe data/factory reset it, then used Odin to grt back to 3.0.1. Then i just redownloaded the 3.1 update. Hope that helps
Click to expand...
Click to collapse
right now im having problems with adb listing the devices. adb is installed. it keeps saying that i need some APX drivers???
Drivers are here:
http://www.samsung.com/us/support/owners/product/GT-P7510UWYXAR
I had the same problem. This is what i did. Since I had already rooted my tablet, I already had in my laptop ADB and the driver for the tablet. If you don't have these 2 things, I suggest you go to the development section of this forum, look for the insrltructions on how to root, and download what you need.
I connected my tablet then went into cmd mode (DOS MODE), then typed adb reboot recovery. From there the tablet rebooted into recovery. I then wiped data and cache. Then I rebooted and it went fine, no more bootloop. In settings I noticed that it had reverted back to 3.0.1 so I just did update again. Since then my tablet has been smooth as butter.
Sent from my GT-P7510 using XDA Premium App
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
kdietze3 said:
For those not too comfortable with ADB, I just installed PDAnet (for the fastboot drivers) and after booting to fastboot (holding power and the volume down button and selecting the USB symbol) I used the "fastboot -w" command in CMD.exe to wipe the device.
Its rather strange that a lot of people are having problems. Mine started after getting an error turning on the WIFI chip. Thank god for Titanium Backup's option to sync with Dropbox. Hope this helps.
Click to expand...
Click to collapse
THANK YOU!! Your suggestion of installing PDAnet saved me! I was having a hell of a time trying to get the right drivers so my computer would recognize the tablet has an adb device. After installing PDAnet, it was a cinch. Then I reflashed everything, wiped userdata and cache, and rebooted (I followed the instructions found here: http://forum.xda-developers.com/showpost.php?p=14600617&postcount=111) Now my tab is working again and I was getting ready to ship it off to Samsung so they could re-flash it for me.
Follow this steps
The steps are this:
http://forum.xda-developers.com/showpost.php?p=15084897&postcount=123
Obviously I have installed adroid-sdk and download fastboot from HTC page.
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
engljeff said:
I'm one of the lucky ones who has had their I/O tab stuck in a boot loop on 3.1, and after trying the steps below, I am not getting it to work. I know I must be making a stupid mistake somewhere along the line, but essentially,
I downloaded the new image, boot, and recovery files into a directory on my hard drive;
I installed PDAnet;
I entered into fastboot on my GTab and plugged it into my PC;
I can tell that fastboot is now listed as a device (I suspect this means that the drivers are installed correctly and that it is recognizing a fastboot device);
Now when I try to run the fastboot commands suggested, I get 'fastboot' is not recognized as an internal or external command...
Stupid question, but I am supposed to run this command from cmd.exe, right? Any ideas what I am doing wrong so that the fastboot commands are not recognizable? I may need a dumbed down instruction set if there are steps I am missing somewhere...
Click to expand...
Click to collapse
Edit:
After trying just about everything, I have concluded there are two hurdles I still cannot pass. First, if I fastboot my device, and select the USB icon, my device is appearing in my windows device list. However, I cannot run any fastboot commands in cmd.exe window. Not sure why or what else is needed. Second, I successfully installed SDK and tried to enter recovery mode through ADB, but I cannot find the magic trick to have my device appear in ADB. ODINing back to stock did not make a difference. If I can get past either of these hurdles I am confident I can progress, so any suggestions are appreciated.
fastboot commands never seem to work for me. Always says waiting for device.
ericc191 said:
fastboot commands never seem to work for me. Always says waiting for device.
Click to expand...
Click to collapse
Which makes me wonder if I am doing something wrong. I can't even get fastbook command to be recognized. It's as if there is some fastboot software needed so that my pc knows what to do when I type fastboot. I hoped SDK was enough, took a stab with a fastboot.exe from htc I found on another forum, neither worked. How did you get your pc to look for your device from fastboot in the first place?
Sent from my SGH-T959 using XDA App
Hi .. I have the same problems before
I found out that the new ADB has moved the directory to "platform-tools"
This renders the fastboot useless "winapiadb.dll"(or something) file not found pop up window
I got that ridiculous bootloop issue right in the middle of the flight! thought I bought a $$$ junk lol
use the fastboot -w option to recover .. but it resets the whole tablet back to OE (original everything)
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Clyde_Frog said:
Hey guys,
So I have one of the Limited Edition Google IO Galaxy Tab 10.1's and I can't find a more updated thread than this. It seems this problem is isolated or mostly isolated to the Limited Edition tabs?
Anyways, I've read through the thread (as well as many other resources) and I just don't understand what I'm supposed to do to defeat the boot loop problem.
For me, pressing the Power and Volume up button (or Power and Volume down button) doesn't do a thing. The tablet does not respond at all. The only thing other than the boot loop is that I can get it into "upload mode" whatever that is.
This thread doesn't mention upload mode, so I don't know how to proceed. I can't seem to find anything in the manual about this sort of hard reset, nor can I find any information anywhere else.
Also, I've read this thread, and I do not have any familiarity with what the following software projects are: Odin, PDAnet, and APX Drivers. I also have not used the android SDK.
Also, in the third post chris eckman posted a link to some sort of Galaxy Tab drivers on samsung's site, which is now a broken link.
Anyways, while I'm a noob to the XDA community, I am a computer engineer, and I'm confident I won't have any trouble recovering this device. There's just so much conflicting information and alternatives methods that I'm not sure how to proceed.
It seems like a tutorial might exist out there that I have not yet found?
Click to expand...
Click to collapse
Ok, well if you are running a "stock" IO bootloader, then you should have fastboot and download modes accessible to you by using the volume down and power button combo.
Have you ever gotten to this menu before? If not, then you just aren't doing it right. Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear. If you have an IO bootloader, then you are going to go into fastboot mode, and then use fastboot to get your recovery booted. Once you get CWM booted, you can flash a stock ROM, load up stock recovery and wipe this sucker back to factory, and then fastboot your CWM recovery and install Task650's latest rom and be bootloop free. Let me know if you need further help.
Alright, first things first. Yes, this tablet is 100% stock, and I've done one major Android update, but it was not the one that broke everyone's wireless.
----------
So going step by step:
you should have fastboot and download modes accessible to you by using the volume down and power button combo. Have you ever gotten to this menu before?
So, I did once get to what I believe was the "fastboot" menu. I had four options available to me, the first one was something like "repair boot process" which I selected, because I was having a boot problem. It did nothing, and now I cannot get back to that menu.
I did get to the USB upload screen once by accident, when I was trying to get back to the boot menu, but not knowing what to do at that point. I had to shut it off.
Let go of the power button part of this combo once the samsung logo appears, and then you should see two icons appear.
Which Samsung logo? If I press both the power button and volume up or down, I get nothing. Nothing happens. If I press the power button first and then two seconds later start holding down the volume button, then eventually I get the blue swirly samsung screen. At the end of that, the samsung logo is clear. But waiting a bit longer, after about 30 seconds of blank screen, a pulsing white Samsung logo comes up, and I've never known which samsung logo to stop holding the power button. I believe I've tried every combination imaginable, and none of them work.
If you have an IO bootloader Do you mean Google I/O Stock bootloader? If not, I have no idea what this is in reference to.
Once you get CWM booted No idea what that is.
you can flash a stock ROM Where do I get that?
-------------
My bootloop might be different from everyone else's. Everyone else says "shut off the device, and then turn it on with the volume down/up held down. The problem with mine is that it NEVER shuts off! So, I can only do about 2 tests per day, because the only way I can shut it off is to let the battery run dead.
Mine switches from boot loop, and if I force that off, by holding down the power button for 10-15 seconds, then it immediately boots back up into "going into upload mode, cause unknown" If I force that screen off, it boots into the boot loop, so I can never boot from a "powered off" mode, again, unless I let the battery run dead.
I've tried every button pressing boot sequence I can think of with no luck. Can't I just upload something to the device in "upload mode" ? I don't need any data off this device, I just want it to be reset back to day 1, so that I can turn it on and use it.
Thanks so much for your help. As you might imagine, this is a very frustrating problem.
bootloop
can someone please help me ,i have a samsung galaxy tab 2 10.1 ,and its on boot loop ,always showing smsung galaxy tab 2 logo,i've tried restoring factory settings ,,didn't work ,i tried to install receovery from internal sd card says not found ,some one pleeaaase send me the steps of what to do
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
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
jhajj33 said:
Hi everyone,
While trying to return to stock using the LG Flash Tool .tot method, my phone got disconnected from my PC during the firmware update. Now, I just get the LG screen in a boot loop without the ability to get into download mode or recovery. I've looked around for a good half hour and couldn't find a thread describing a similar problem, so if it's a noob question, my bad. I have insurance for physical damage, so it might accidentally get run over at some point today. Any last ditch efforts available before it happens?
Appreciate any and all input!
Click to expand...
Click to collapse
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
It's Vol Up (and hold it) + plug into the computer to get to Download Mode, but if the OP was already in a flash process that got interrupted it's entirely possible the phone won't go back into Download Mode again. It should be able to get back into that mode given how it works but, it's all relative given how far along the process was the first time when it was interrupted.
Pull the battery for 30 seconds, re-insert it, then hold Vol Up + plug it into the computer and see what happens. If it will absolutely not jump back into Download Mode then yep, it's pretty much hosed and would need LG to do something to resolve it.
Good luck...
jhajj33 said:
I have insurance for physical damage, so it might accidentally get run over at some point today.
Click to expand...
Click to collapse
Thanks for that good laugh, almost spit out my coffee with that one.
engine95 said:
If you pull the battery, then put it back in, it should be off.
Then press and hold vol dn while plugging it in it should go into DL mode. Flashtool should work then.
It might be vol up. I can't remember off hand.
Click to expand...
Click to collapse
That was the first thing I tried doing, it completely ignores my button presses no matter what I do. Held uo/down while plugging it in, , tried power+up, power+down to get into recovery mode, nothing. Just keeps showing the splash screen over and over again. This isn't my first, or even 10th rodeo as far as restoring phones back to stock, but I've never seen something like this before. Starting to think it's a lost cause.
When it is at the LG screen try running:
fastboot reboot-bootloader hopfuly that will boot you into download mode. The next thing you can try is to download the twrp image and then run this command: fastboot flash boot <namehere>. I know its not the same device but I did the same thing ony kindle fire and that boot command worked. It just booted me into twrp and I flashed a new rom.
Hi. My sons HDX is stuck in fastboot mode. Amazon support only offered him a discount to replace it. I thought maybe I could do something to wake it up or reflash it but from what I'm reading this is a difficult device. I have been able to get it to respond to the fastboot reboot command in linux but nothing else. This device has never been rooted/flashed/modded and I don't know how it got this way. Is there anything I can do at this point besides throw it away?
Thanks.
when you are at the fastboot screen...
press the power button for 10-20 sec. and it will shut down...
than try to power it on again.... (try it with unplugged usb)
maybe this helps...
If possible, I would unlock the bootloader and then try this guide: http://forum.xda-developers.com/showpost.php?p=22077057&postcount=11
This device has never been rooted/flashed/modded and I don't know how it got this way.
Click to expand...
Click to collapse
Just thought this means the HDX is on 4.5.2(3)
thanks for the responses. I have tried rebooting the device many times with or without usb plugged in. I've held the power button for 25 seconds until it starts rebooting again. It always boots to a gray kindle fire logo and says fastboot. I've tried the fastboot -i 0x1949 oem idme bootmode 4000 command but it says the hw is locked. From what Ive read, the bootloader cant be unlocked right?
ianedward said:
From what Ive read, the bootloader cant be unlocked right?
Click to expand...
Click to collapse
Do you recall the firmware level (eg: 3.2.6; 4.5.2)?
Edit: After shutting down (completely off) have you tried power+volume up to access Amazon's crippled recovery? From there you might be able to initiate a factory reset.
i have tried to power it on with different button combinations. I can only get to the same fastboot screen.
oh and I have no idea what firmware it was on.
ianedward said:
i have tried to power it on with different button combinations. I can only get to the same fastboot screen.
oh and I have no idea what firmware it was on.
Click to expand...
Click to collapse
Yeah, it was a long shot. At this point you may be hosed unless someone knows of a way to recover in fastboot given the state of your device (locked, unrooted, version unknown). Might want to try Amazon again. A different rep may be more accommodating. Sorry, mate.
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!