Just a background:
This is not my device
This is a stock OS/nonrooted device
I have done some development on Android, so am somewhat experienced
I am helping a friend who just wants it to work again
Kindle Fire HDX 7" model # C9R6QM
What's going on:
Device is stuck on light gray "kindle fire" boot logo.
Device is not showing in device manager on Windows 7 PRO
Device is not showing in adb "adb devices command"
Device seems charged, has been left with cord in for longer than several hours
Tried several different cords to rule out faulty equipment
Tried multiple USB ports including 2.0, 3.0, front and rear ports, even a powered USB hub
Tried hard reset multiple times using power button
Tried power and vol up to go into a recovery, nothing happens.
"fastboot devices" command shows only "waiting for devices"
Help! I just need to get this thing up and running again, no matter the cost to data. Only thing I haven't tried is the bootloop utilities yet, as I am on a work pc and do not have access to download them atm. Will try these later if I need to.
Thanks in advance, and ask any questions if you need more info.
-Tripp
UPDATE 1: Upon further playing with device, I have finally gained access to the "Fire System Recovery" page seen here.
Well I guess since I am a new user still I cannot post the photo, but it is kindlefire recover page with a bunch of E: failed and E:cant mount stuff underneath. If I need to spell it all out I will.
Unfortunatly, neither "reboot your kindle" or "reset to factory defaults" does any good for me. Rebooting just causes it to bootlogo screen again, and Reset to FD fails, getting some weird oldschool tv effect on the screen until it reboots again into recovery and gives me the same two options.
ADB, windows, and fastboot still do not detect the device while in recovery.
Any ideas?
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
EncryptedCurse said:
Doesn't sound like you have many options. Only other thing I can think of would be to try booting into Linux (i.e. Ubuntu) and see if you can get anything to work from there.
Anyways — since you claim this is a stock device — have you tried contacting Amazon for a replacement?
Click to expand...
Click to collapse
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
trippvail said:
I wish it was that easy. Device is way out of warranty. Was purchased just after it came out in 2013. I have not tried booting into linux, but can run a USB boot when I get home on my machine to attempt it. Will report back after. Thanks.
Click to expand...
Click to collapse
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Davey126 said:
No surprise about ADB and not showing in Windows as the former was probably never enabled and the boot never gets far enough for the latter. Curious if you seen anything in device manager.
Unfortunately, you don't have a lot of options given the device is stock and fastboot is next to useless on a HDX with a locked bootloader (special cables don't work). If the previous poster's suggestion yields no progress I would reach out to Amazon. Even though the device is well out of warranty they may offer a deal given it failed spontaneously. Yeah, it likely be a refurb with some coin added in but a working unit is better than a brick if the price is right.
Click to expand...
Click to collapse
Damn was hoping there was a fix. I am sure that adb was never enabled as they are not tech savvy. Nothing shows in device manager when it is plugged in, ever. No changes.
Update 2:
So I popped in my Ubuntu drive and booted up. After installing adb and fastboot just in case, I tried accessing the kindle in both boot logo and recovery modes. No luck.
Ubuntu doesn't even see it there...
I know I'm not going crazy but it seems like I'm missing something somewhere. I have been through multiple brickings of our developer phones and brought them back to life but they always had adb enabled. Seems like there has to be a work around.
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
trippvail said:
Quick question, would I be able to use a factory cable, or a homemade one at least, to force it into fastboot mode while it's stuck on boot like this?
And if I could get it into fastboot, would I be able to do anything to fix my situation?
Click to expand...
Click to collapse
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Davey126 said:
Don't waste your time; traditional fastboot cables are useless on an HDX. One reason this generation of Kindle is exceptionally difficult to recover. The only time your really have control is with an unlocked bootloader. Otherwise the fastboot environment is crippled. Obviously Amazon has a hardware recovery method but no one has discovered it in the nearly 2 years since initial release.
Sorry to be the barer of bad news. It would be much more satisfying communicating a potential solution ...
Click to expand...
Click to collapse
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
trippvail said:
lol thanks anyways. I just can't believe there is nothing I can do. Seems like if taken one step at a time, however lenghty the process may be, I would be able to get it fixed. Like if I can get into fastboot, even if crippled, I could repair the bootloader, or install a new recovery, or even wipe every partition and start over, or something. And then from there just add on little by little till it works again. I guess locking this device up like Amazon has will allow them to be the only ones to fully work on them. What a shame.
Click to expand...
Click to collapse
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Davey126 said:
Yup - in a phrase it sucks. You can enter fastboot via power + vol- (volume down) but no useful commands can be issued unless the bootloader is unlocked. To do that you first need to install a vulnerable bootloader (typically accomplished via a Fire OS rollback), build an unlock code from your serial and manfID (obtained via ADB), sign the code string using a 'special' program and then attempt to unlock from fastboot. You can't even get to the first step no less securing the various details needed to complete the magic.
From a stickily business perspective Amazon is doing the right thing as a 'hacked' Kindle likely won't be used in the manner intended which involves full immersion into the Amazon ecosystem. Yeah, it ticks off a community of Android die-hards who vow never to purchase another Amazon device but in reality we represent a minute fraction of total sales. Apple nerds have been rattling the boycott saber for years. Has worked well - Apple just reported $58B USD sales for 1Q15. Apple probably could have made another 12 cents if they allowed all their devices to be unlocked and loaded with non iOS components (not adjusting for lost revenue from uncaptive app/media sales).
Click to expand...
Click to collapse
Ya I can understand that. I'm actually using an iPhone right now, jailbroken of course lol. But I understand why Amazon did it. Too bad a tablet has to die because of it though. I love the open Android systems but I like apples hardware better. Haven't found an android phone I like better yet. To each his own, right?
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
draxie said:
You may have said this before (I didn't read too carefully),
but I'm wondering if you had tried the HW buttons to get
into fastboot mode (power off, hold both volume buttons
while powering on). I have a theory that 'fastboot update'
actually works, but never had the need (or the extra time)
to test this.
Do you know what version of FireOS was installed?
Click to expand...
Click to collapse
I don't and neither does the owner. I would assume the latest if it auto updates, although that may be what bricked it if it didn't have the power to complete the update. Can't confirm any of that though.
I will try both volume buttons in a bit when I get off work. I did the vol up with power to get into recovery, but that did nothing for me as recovery failed every time and rebooting just takes me back to the gray kf logo.
Ok so I tried the vol up and down while powering it on and it just took me to recovery. Same E:failed to mount and E:can't mount/can't open messages below the recovery options in yellow. So I guess I'm screwed then.
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
draxie said:
Hmm... This sounds kind of weird _to me_ considering that fastboot is the interface
to the bootloader, which loads either the boot or the recovery image. Since you do
seem to be able to boot to recovery (albeit with errors), I'd sort of expect aboot (i.e.
thebootloader) to be reasonably intact. And, in that case, you should be able to get
to fastboot; at least, in my book...
I suppose you must have tried this more than once, but I'd still recommend to give it
another chance. Power off the Kindle. Hold both volume buttons firmly. Push the power
button. And, keep holding all three until the fastboot prompt slides in. (The grey logo
should show up first, even in this case; quickly followed by the [fastboot] text.)
If this just doesn't seem to work, you could also try holding just the power button *really*
long (something like 40 seconds, I believe), which is supposed to trigger some form of low
level reset (possibly the same as factory reset; so, if data on the device matters, you should
think twice before going down this road). Then, see if this helped with getting into fastboot...
Other than that, I'm not quite sure what else to do than pray the thing apart and look for
debug pins.... :crying:
Click to expand...
Click to collapse
I will be trying your methods draxie when I get home and back with the device today if what I am doing now doesn't work. I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
At this point recovering anything from the device is nothing to me, or the owner, as there was nothing important on it. I was hoping to not take the hardware route, but I have the tools, the time, and the hands to do it if necessary. All I need is the knowledge from someone as to what the hell I'm looking for in there.
Just to confirm, after the gray logo of KindleFire comes up, should I be seeing anything else come up while holding buttons for fastboot? <<Just re-read your post and realized it answered this question>>These things are so much easier to use when rooted and TWRP or CWM recoveries are installed. Android makers all over should take note and use the knowledge of the open source community to improve their own devices.
Below is a photo of the recovery screen I see now that I can finally post photos.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
trippvail said:
I was following another dev's advice to let the device die and charge it from there to perform a reset as well. It is not dead yet and has been on boot screen all night. Not sure what it is going to do but I am new to these Kindle Fire related things so I am not going to ask questions.
Click to expand...
Click to collapse
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
draxie said:
That sounds like a more surefire way to get any "stuck bits" cleared.
This would be similar to how some laptop manufacturers instruct you
to disconnect power, remove batteries, and let the thing sit for 5-10
minutes as a last resort, e.g. with boot failures. Which reminds me,
it may be a good idea to let the Kindle sit there dead for a while
before connecting a charger...
I was hoping that holding the power button "long enough" might get
you there faster; but that may just be wishful thinking based on a post
I read somewhere in these forums.
Click to expand...
Click to collapse
Lol thanks. I am sure it will be dead for awhile before I get home, if it's not dead already. But if for some reason it's still alive I will make sure to let it sit for an extra 30 minutes after it goes down.
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
jwcdis said:
My kindle unit is in the same boat as that unit above, no fastboot, no ADB, I had TWRP but i formatted it thinking it would only format the OS image.
The only thing I can get is a QHSUSB_BULK driver that doesn't completely install. Am I in a position where I can get fastboot or ADB access?
Click to expand...
Click to collapse
If the bootloader remains locked with no access via tether (or wireless ADB) you are pretty much done. You can attempt the cold start remedy suggested in earlier posts. Long shot at best. Note the device should sit idle for several days after appearing to be depleted as internal circuitry prevents the battery from going completely dead. Even then some charge will remain which is necessary to respond to the power button and protect the battery from permanent damage. Removable primary and backup batteries are the only surefire way to insure a true cold start.
Related
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Edit: I was told that my lack of drivers were the problem - I thought I didn't need them on a 32 bit system. I did. Recovery reboot solved for me!
If you cannot enter Recovery Mode with Vol Up+Vol Down+Power, your phone is defective and T-Mo will exchange it.
You're serious? It really is that simple?
So, I call them up, tell them I have a hardware locked phone and I cannot boot into recovery mode, and they'll set me up?
I'm thinking I had to go learn odin and start getting less a'scared of command lines.
FenixGryph said:
Hey everyone - my first post here.
Anyway, I read and read and read about my new Vibrant to see just what I could do with it without screwing it up and bricking it and I find out my device is hardware locked.
After reading [GUIDE] / [THINK TANK] - Accessing downloader & recovery w/ locked hardware access (I cannot post a link just now, apparently) from start to finish, I am more confused than not. I cannot do anything but stay in a boot loop (by holding buttons down) or boot up the phone like normal. No recovery or download mode has so far been possible.
So, can I root my phone? Should I just attempt to exchange it? Should I wait for a work-around? Or is there information I'm missing somewhere?
Thanks, all. This community is insanely helpful and cordial, without you guys I'd never have gotten my dream working properly.
Click to expand...
Click to collapse
Here's my advice in a step-by-step:
-Install the AndroidSDK (And make sure it is named that) Found here - http://developer.android.com/sdk/index.html
-Move the folder to Computer> Local Disk ( C: )
-Run the .exe
-Go to Settings, click on Miscellaneous, and check Force https
-Click on Available Packages and install (And then minimize)
-Click Start and search cmd (Also known as Command Prompt)
-Type cd\ (And then press enter)
-Type AndroidSDK\Tools\adb reboot download (And then press enter)
**Make sure your phone is plugged into the computer with USB Debugging turned on.
Your phone will reboot and be in Download Mode. Hope this helps.
Hardware Locked, huh? really? on the vibrant?
Can someone explain what hardware locked vibrant is. Is this some term you guys made up. I can not for the life of me, figure out, why in the world Samsung would ship some phones hardware locked and others not.
Makes no sense, someone explain, seems like this is a made up term which does not apply to Vibrant.
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
sabooher said:
Either Samsung is being completely ignorant to this issue or they have the worst quality control. I am beginning to think it's both. Simply google searching brings up lots of results on this issue.
My first Vibrant (USB port eventually broke) 3 button recovery worked fine; dated July 15. The replacement after that did not work, nor did the one after that. Those were both made on Aug 16. I finally got a refund under buyer's remorse and waited another week. Got my fourth Vibrant today, made 09/01 and yes it does work with 3 button recovery.
Keep in mind none of my Vibrants were refurbished units. They were all brand new. I think Samsung has a serious flaw on their hands. I'm concerned about keeping this phone even but I added the insurance on it just in case.
Click to expand...
Click to collapse
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Oniyuri said:
By "hardware locked" they mean that you cannot access the phone's recovery or dl mode using the 3 button method.
this has apparently started with the 08/**/2010 batches. beforehand this phone was deemed "unbrickable" but it's now actually possible with the newer shipments so ppl have got to be a lot careful trying to mod their phones now.
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
Well just my 2 cents on the topic, entering recovery mode required following strict steps, miss 1 single step, and you won't get into recovery.
now as far as download mode goes, I have been able to get into it once. This was by accident, I was randomly doing various sequences of volume rocker and power, it went into download mode. Now since then, I have no clue what sequence I used, but I have never been able to get into download mode ever again.
Additionally, my phone is dated 7/2010, so the 8/2010 batch theory doesn't hold since I can not get into download mode either now.
To get into Recovery Mode, follow these steps.
Okay, I'm reading lots of people having trouble getting into recovery mode, thinking their phone is broken or busted. Chances are you are not holding down the power button log enough, or you are letting go of something too quick.
FOLLOW THESE DIRECTIONS STEP BY STEP.
1) START with your phone off
2) Press volume up AND volume down at same time, keep them pressed in the entire time, do NOT let go. I prefer to hold my phone in landscape, this gives me better control with my fingers.
3) WHILE holding down volume up and volume down, press and hold power button, DO NOT LET GO OF ANYTHING. You should be holding down volume up, volume down, and power, DON'T LET GO! HOLD ON... and proceed to next steps, dont let go!
4) PHONE will start, you will see the white Vibrant logo. STILL DON'T LET GO, volume down, volume up, and power all pressed.
5) White Vibrant logo disappears, still dont let go!
6) White Vibrant logo re-appears again for the second time. Right when you see the white vibrant logo pop up a second time, let go of ONLY the power button, keep holding down volume down and volume up.
7) Phone enters recovery mode, you can let go the volume rocker.
hope this helps, it worked for me, hopefully it works for you also.
now can someone post sure fire method into getting into download without needing to connect the phone to your computer and using odin?
Oniyuri said:
I think that's the first phone dated after 08/** that i've heard of actually having the 3 btn modes work. My bf has a vibrant and I've been holding off purchasing one myself since hearing about the hardware locked ones. i've been literally scouring ebay for a phone that was a part of the July batch.
well, this gives me a little hope.
Click to expand...
Click to collapse
Hate to break it to you, my phone is made in July, and it WILL NOT go into download mode, I do however get into recovery mode.
That phone date batch theory doesn't hold true, so you can stop searching for july phones.
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.[/QUOTE]
where did you read this, please provide the link
Click to expand...
Click to collapse
Samsung Mobile USA support is worthless. I called three times and finally got someone in "premier support" who didn't know anything. He actually went as far as to tell me a simple data wipe would resolve this problem, ha! I then got a hold of someone at Samsung Telecom corporate office who said he'd look into it and never called me back. No surprise there either. I think it's kind of sad that people are having to resort to Facebook wall comments to get a company to start backing it's products.
Thanks to sabooher, I was able to get into download mode with no problems, I hope this works for you, and thank you again sabooher.
okay, start off with your phone turned off
hold down both volume down and volume up at the same time, do not touch the power button
now, get your usb cable, have one end into your computer, the other end put into your vibrant, while you are still holding down the volume up and volume down at same time. dont touch power button
your phone hopefully will now go into download mode!
SamsungVibrant said:
FOLLOW THESE DIRECTIONS STEP BY STEP.
Click to expand...
Click to collapse
Nope, no good.
jonathan3579 said:
Here's my advice in a step-by-step:
Click to expand...
Click to collapse
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
SamsungVibrant said:
Oniyuri said:
on a side note: i've read that Samsung Mobile Canada has admitted that the hardware locked phones are in actuality a defect. hopefully Samsung Mobile USA will come to the same conclusion.
Click to expand...
Click to collapse
where did you read this, please provide the link
Click to expand...
Click to collapse
Sure, it's all over their facebook page. I've read tons of android sites so I can't quote the site that led me to this page but I've been following the Samsung Mobile Canada FB page over the last few days about it. Suffice it to say: the Bell customers are really not pleased with the 3 btn issue: Samsung Mobile Canada
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
maybe you don't have the correct drivers installed, try the ones from this thread --> http://forum.xda-developers.com/showthread.php?t=728929
Well here's my take on things. I got my phone (July 11th build date) directly from T-Mobile corporate. Came via FEDEX on launch day. Long story, suffice to say I had Behold II and complained to the right people at the right time and got swapped a Vibrant to basically shut me up.
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
masterotaku said:
Entering download mode seems to be very timing specific even for this original batch phone. There is only one way I can reliably get download mode 100% of the time...
- Pull battery
- plug in to USB cable connected to PC
- hold down VOL DOWN + VOL UP (DO NOT HOLD DOWN POWER)
- Insert battery
Alternately I can get into download mode using VOL DOWN+ VOL UP + POWER, but I have to be very careful to catch the right moment after the Vibrant logo appears the 2nd time to release power to get download mode.
When I ODIN, I use the first method always now.
Click to expand...
Click to collapse
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
crazycaveman said:
That's odd. I've never had a problem getting into download mode; in fact, I was confused the first time it happened cuz I didn't mean to! All I have to do is make sure the USB cable is plugged in and then hold all 3 buttons when I turn it on and into download mode it goes.
Click to expand...
Click to collapse
I tend to have bad luck with Odin too. I've seen the "ohsh*t" icon many times...
(note: the "ohsh*t" icon is what I call the phone/caution symbol/pc icon I tend to see quite often)
When that happens the ONLY way I can get back to download mode is the battery-insert method.
FenixGryph said:
Nope, no good.
Had the sdk already, so that was no problem. With usb debugging on, I had the same problem I've always had with adb - error: device not found.
Click to expand...
Click to collapse
It definitely sounds like you don't have the correct drivers installed. My drivers were downloaded through the installation of Kies, however, is your computer online while you are attempting this? I can only speak for my computer which is running Windows 7, but it automatically downloads any updated/new drivers necessary when connected online.
woot!
Ha ha!! The drivers were the problem. I was under the impression I only had to install the samsung drivers if I was on a 64 bit system.
I'm looking at my recovery menu now and am very happy! Wish I had time to do the stuff I wanted to do the vibrant before work, but I gotta make a couple of bucks before I get this guy set up just how I want.
See? I knew XDA was the place to be. Many thanks Oniyuri and jonathan3579!
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Don Karnage said:
Hello guys!
I think i turned my Fire HDX 7" into a fancy cutting board.
I just hope there is still... well... hope.
About 2 month ago I stumbled across an app that "can boot your device in one click". Didn't work out, thought it did nothing but i think it's the root of my problem.
On the weekend i wanted to rest to factory settings. After that i'm stuck in a bootloop.
Kindle logo followed by "Fire is updating.. please wait" aaand reboot
Pressing the power button and volume up gives me the "reset/reboot" menu.
I soldered together a factory cable but it didn't enter fastboot. Showed up as "QHSUSB_BULK". and a "bricked" feeling (no reactions, blackscreen). Pressing power for a long time returned it to the bootloop.
Any help is appreciated and if things work out you just might earn a beer if you ever visite Germany/Munich.
Greeting
Click to expand...
Click to collapse
Sorry for your troubles. Fastboot (aka factory) cables are useless on an HDX. If you can't 'see' your device via a standard usb cable or it shows up as "QHSUSB_BULK" then you're done. If the device was purchased within the past 12 months there is a good chance Amazon will exchange it for a refurb. Just say it died during an update (apparently true). No need to mention the prior root attempt which may or may not be related. Call and be nice to the rep; ultimately it's their decision.
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Don Karnage said:
Well, this explains a lot.
First of all thank you!
With a normal usb-cable iz shows up as "Anroid" and "MTB-USB-Device"
Contacting amazon will be the next thing for me i guess.
Click to expand...
Click to collapse
Those are encouraging signs. Do you recall enabling adb? If so there may be a way to revive your device via tether but the the commands/techniques are a little beyond me (others can probably help). Most require root access which you likely don't have. Best guess is the root exploit you tried was partially successful and may have altered some files needed to process ota updates. A factory reset emulates portions of that process likely resulting in the boot loop. If the offending 'update' file(s) can be renamed you might be able to boot successfully.
Don have you ever used ADB? If so this might possibly save you
http://forum.xda-developers.com/kindle-fire-hdx/general/unbrick-solutions-t3059733
So, I've had my Kindle Fire HDX 7' for a while now, and it's been running great. But amazon updated it from 4.5.3 to 4.5.4 and then it wouldn't boot. It would say: Fire is Upgrading, please wait... Then it would prompt me to choose the default kindle launcher, nova launcher, or the setup wizard. Which ever one I chose, it would close the window, but then come back to the same place. I contacted amazon support, and they said to boot into recovery (power+volume up) and factory reset, which I did. And now what happens is it says Fire is Upgrading please wait... then says that it is starting applications. But it stays there, and nothing happens. Anybody know a way I can fix this?
A very long shot, but try holding down the power button for 2 minutes.
lekofraggle said:
A very long shot, but try holding down the power button for 2 minutes.
Click to expand...
Click to collapse
Nope, that just force rebooted it a bunch of times
ftf841 said:
So, I've had my Kindle Fire HDX 7' for a while now, and it's been running great. But amazon updated it from 4.5.3 to 4.5.4 and then it wouldn't boot. It would say: Fire is Upgrading, please wait... Then it would prompt me to choose the default kindle launcher, nova launcher, or the setup wizard. Which ever one I chose, it would close the window, but then come back to the same place. I contacted amazon support, and they said to boot into recovery (power+volume up) and factory reset, which I did. And now what happens is it says Fire is Upgrading please wait... then says that it is starting applications. But it stays there, and nothing happens. Anybody know a way I can fix this?
Click to expand...
Click to collapse
You mentioned Nova which suggests device was rooted. Once rooted you have to block OTA. Not a lot of options unless root was retained through the update (unlikely) and you have adb enabled. I would work with Amazon given the 4.5.4 update hosed your device. Might get a discount on a replacement. Probably best not to mention root, Nova or any other customizations.
Davey126 said:
You mentioned Nova which suggests device was rooted. Once rooted you have to block OTA. Not a lot of options unless root was retained through the update (unlikely) and you have adb enabled. I would work with Amazon given the 4.5.4 update hosed your device. Might get a discount on a replacement. Probably best not to mention root, Nova or any other customizations.
Click to expand...
Click to collapse
When I contacted them, I didn't mention anything about those. However, it had been past a year, and so the warranty was out, and they said they couldn't do anything about it. I get a 20 dollar discount though
ftf841 said:
When I contacted them, I didn't mention anything about those. However, it had been past a year, and so the warranty was out, and they said they couldn't do anything about it. I get a 20 dollar discount though
Click to expand...
Click to collapse
If I were to guess is your Kindle is trying to start the native launcher but is encountering a conflict with Nova. On most devices this would be fairly easy to fix. Recent Kindles are locked down by Amazon. A next-to-use useless recovery environment compounds the problem. So far no one has figured out how to crack this nut on an unrooted device running Fire v4.
Press your case with Amazon. If you are regular customer a supervisor may be willing to make an exception or offer a larger discount. Your argument is based on an unwanted/unrequested/unnecessary amazon update that went bad. Just minding your own business and blamo ... an OTA out of the blue turned your world upside down. Or something like that ....
Davey126 said:
If I were to guess is your Kindle is trying to start the native launcher but is encountering a conflict with Nova. On most devices this would be fairly easy to fix. Recent Kindles are locked down by Amazon. A next-to-use useless recovery environment compounds the problem. So far no one has figured out how to crack this nut on an unrooted device running Fire v4.
Press your case with Amazon. If you are regular customer a supervisor may be willing to make an exception or offer a larger discount. Your argument is based on an unwanted/unrequested/unnecessary amazon update that went bad. Just minding your own business and blamo ... an OTA out of the blue turned your world upside down. Or something like that ....
Click to expand...
Click to collapse
If Nova was conflicting, the factory reset should've fixed it. Something I forgot to mention, is if I shut it down after it prompts me which launcher to choose, it goes through the same process all over again, with the updating, leading me to believe it's something deeper than just the launchers conflicting.
ftf841 said:
If Nova was conflicting, the factory reset should've fixed it. Something I forgot to mention, is if I shut it down after it prompts me which launcher to choose, it goes through the same process all over again, with the updating, leading me to believe it's something deeper than just the launchers conflicting.
Click to expand...
Click to collapse
A factory reset on a Kindle isn't what you think. It restores some files but does not perform a comprehensive refresh. A reasonable (albeit imperfect) comparison is system restore in Windows. Addresses some issues but is by no means comprehensive. Unlike Windows you don't have access to low level files without root and usually can't fix a start-up problem even if you know the source. What you really want is a true 'reset' or 'restore'; those options aren't available in the stock recovery.
I'm not saying it's 100% unresolvable. But few users exit the dreaded 'setup loop' w/o root access. Don't mean to be negative but also do not want to raise false hopes. There are a few clever (and very talented!) individuals who monitors these forums. Let this post sit for awhile and see who chimes in.
Davey126 said:
A factory reset on a Kindle isn't what you think. It restores some files but does not perform a comprehensive refresh. A reasonable (albeit imperfect) comparison is system restore in Windows. Addresses some issues but is by no means comprehensive. Unlike Windows you don't have access to low level files without root and usually can't fix a start-up problem even if you know the source. What you really want is a true 'reset' or 'restore'; those options aren't available in the stock recovery.
I'm not saying it's 100% unresolvable. But few users exit the dreaded 'setup loop' w/o root access. Don't mean to be negative but also do not want to raise false hopes. There are a few clever (and very talented!) individuals who monitors these forums. Let this post sit for awhile and see who chimes in.
Click to expand...
Click to collapse
Well, thanks anyways
Holding the power button is a way of clearing the cache. It seems like it is just rebooting, but if you do not have a true recovery (which you don't, it is a long shot which has worked for many. If you gave up after a few rounds, stick to it). If that does not work, try pressing poker once and Now, instead of choosing your launcher, enforcing the Kindle to give you the notification bar. Try holding power for just a second and clicking cancel and swiping down from the top. If youngest into settings, you may be able to try the update again. That may reset whatever broke, but Davey is correct, if you indeed were rooted, this is looking bad. If you were not, and you just downloaded nova, there is still a bit of hope.
lekofraggle said:
Holding the power button is a way of clearing the cache. It seems like it is just rebooting, but if you do not have a true recovery (which you don't, it is a long shot which has worked for many. If you gave up after a few rounds, stick to it). If that does not work, try pressing poker once and Now, instead of choosing your launcher, enforcing the Kindle to give you the notification bar. Try holding power for just a second and clicking cancel and swiping down from the top. If youngest into settings, you may be able to try the update again. That may reset whatever broke, but Davey is correct, if you indeed were rooted, this is looking bad. If you were not, and you just downloaded nova, there is still a bit of hope.
Click to expand...
Click to collapse
Well, Amazon told me to boot to recovery and factory reset and that may have screwed me over, because now it doesn't show the nova or kindle launcher, in place of that it says, starting applications, but nothing happens after that. I'll try holding the power button, because I did give up after 3 reboots.
The factory reset could have been a mistake, but I would assume they would have taken you through the power button piece first. Hmm. But, you did try their advice, and it got worse, so perhaps they will hand you a shiny referb. in return. If they do, check it for structural damage. I needed a return, because one of their updates messed my original one up (the kindle app and clipboard would not load), and they sent one with an old boot loader, but it had a cracked bezel. I did eventually get one that worked well, but it took a few rounds. They all had software or hardware issues. Through it all, tech support was stellar.
ftf841 said:
Well, Amazon told me to boot to recovery and factory reset and that may have screwed me over, because now it doesn't show the nova or kindle launcher, in place of that it says, starting applications, but nothing happens after that. I'll try holding the power button, because I did give up after 3 reboots.
Click to expand...
Click to collapse
lekofraggle said:
The factory reset could have been a mistake, but I would assume they would have taken you through the power button piece first. Hmm. But, you did try their advice, and it got worse, so perhaps they will hand you a shiny referb. in return. If they do, check it for structural damage. I needed a return, because one of their updates messed my original one up (the kindle app and clipboard would not load), and they sent one with an old boot loader, but it had a cracked bezel. I did eventually get one that worked well, but it took a few rounds. They all had software or hardware issues. Through it all, tech support was stellar.
Click to expand...
Click to collapse
I think you have a pretty good argument for your next Amazon engagement given the advise given actually made things worse. Obviously demeanor is important; treat everyone with respect and (gently) ask to speak with a supervisor if things grind to a halt. Reputation and customer satisfaction are important to Amazon but you have to be persistent.
Btw - lekofraggle is one of those clever/talented individuals I referenced earlier. Thought s/he might stop by. As always, great to hear multiple perspectives! Good luck.
You must have been in Warranty Leo. I tried so many times. The most helpful tech managed to get me a hundred bucks off, but this was several hours on the phone... He said that a few other people had the same hard brick that I had(never mentioned root) but... no warranty. @op good luck trying to fix this. Amazon is worse than Verizon imo because there is practically no way to fix this damned thing.
I was under warranty. That is too bad because not only is there no way to fix this, there was no way (that they know or want you to be privy to) to prevent it. That is wrong imo.
I'm having the same situation. My kindle was working fine before the night, and the Amazon auto upgrade bricked my Kindle. I contacted Amazon for help. During the conversation they changed 5 agents including one who claimed himself "one of the leaders". Most of them didn't seem to know what happened and how to fix it. Two of them mentioned that I need to factory reset my tablet, but none of them show me how to get into the recovery mode. After 4 hours of conversation they told me my kindle cannot be fixed and the only choice I have is to replace my kindle. And then they said since I've own my kindle for more than one year, the warranty is expired, as a result they cannot replace the kindle for me but they can offer me a discount if I buy another one from them. I was annoyed because what broke my Kindle is Amazon's update, not me. To me, they literally sold me a kindle and broke it after the warranty expired, and then try to sell me another one. They ended up giving me a $50 gift card for whatever sold and shipped by Amazon.
After the conversation I found the way to get into the recovery mode. And I hit the factory reset button. After the reset progress is complete my kindle is still stuck at "starting application", sometimes it passes "starting application" and the screen start flashing... as if the tablet is going to explode....I doubt maybe it is the factory reset file's problem, but it is too late for me to get into the storage using ADB since I don't have debugging mode activated after factory reset.
You may still have adv after factory reset. It only resets some settings. And deletes portions of the /data partition. It does not delete anything from the sd card or much from the /system partitions (which is why it does not help too much if there was a botched install or you messed something up with root powers.
That said, it does remove root, so adb is limited.
Brad D said:
I'm having the same situation. My kindle was working fine before the night, and the Amazon auto upgrade bricked my Kindle. I contacted Amazon for help. During the conversation they changed 5 agents including one who claimed himself "one of the leaders". Most of them didn't seem to know what happened and how to fix it. Two of them mentioned that I need to factory reset my tablet, but none of them show me how to get into the recovery mode. After 4 hours of conversation they told me my kindle cannot be fixed and the only choice I have is to replace my kindle. And then they said since I've own my kindle for more than one year, the warranty is expired, as a result they cannot replace the kindle for me but they can offer me a discount if I buy another one from them. I was annoyed because what broke my Kindle is Amazon's update, not me. To me, they literally sold me a kindle and broke it after the warranty expired, and then try to sell me another one. They ended up giving me a $50 gift card for whatever sold and shipped by Amazon.
After the conversation I found the way to get into the recovery mode. And I hit the factory reset button. After the reset progress is complete my kindle is still stuck at "starting application", sometimes it passes "starting application" and the screen start flashing... as if the tablet is going to explode....I doubt maybe it is the factory reset file's problem, but it is too late for me to get into the storage using ADB since I don't have debugging mode activated after factory reset.
Click to expand...
Click to collapse
If you rooted your Kindle then over-the-air (OTA) updates must also be blocked. That's the case for many devices as the update package expects a device is in a specific condition which may no longer be true after rooting. If the device has never been rooted or otherwise modified an an 'unsupported' manner (including side loading applications; read the disclaimer) then I agree you have a strong case against Amazon and should reengage with the understanding that you will take stronger action if they do not provide a better resolution. Worth a shot unless you are satisfied with the $50 or have something to 'hide'.
Davey126 said:
If you rooted your Kindle then over-the-air (OTA) updates must also be blocked. That's the case for many devices as the update package expects a device is in a specific condition which may no longer be true after rooting. If the device has never been rooted or otherwise modified an an 'unsupported' manner (including side loading applications; read the disclaimer) then I agree you have a strong case against Amazon and should reengage with the understanding that you will take stronger action if they do not provide a better resolution. Worth a shot unless you are satisfied with the $50 or have something to 'hide'.
Click to expand...
Click to collapse
I didn't have my kindle rooted, while I did install some applications from 1 mobile market. I even asked them to take my kindle back for further inspection, while they simply refused my suggestion and insisted their solution, which is either I return the kindle for the discount for a new purchase, or the $50 gift card. I figured that it may cost me more to take further action as I'm just one foreign customer and I don't see many who met the same situation in here.
Let me start by saying I am a newbie. I haven't done any modifications or anything of that sort to the device. I have a Fire HDX 7" that is about 18 months old. Things were going great and then my reader started acting up. The device wasn't completely turning pages, and then locked up all together. I plugged it in to charge, powered down and left it to charge overnight. Turned it back on and was greeted by a screen that says:
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.
Volume up/down to move highlight;
power button to select.
Reboot your Kindle
Reset to Factory Defaults
So I chose the Factory Default. It doesn't seem to be completing the erase procedure, it won't boot. I tried customer service and they were less than helpful, offering me a $20 discount on a refurbished unit.
I expected more than 18 months out of this device. Anything I can do?
Did you make any modifications to the system? (i.e. root, Safestrap)
EncryptedCurse said:
Did you make any modifications to the system? (i.e. root, Safestrap)
Click to expand...
Click to collapse
Nope. Didn't do anything to the device.
VilleDJ said:
Let me start by saying I am a newbie. I haven't done any modifications or anything of that sort to the device. I have a Fire HDX 7" that is about 18 months old. Things were going great and then my reader started acting up. The device wasn't completely turning pages, and then locked up all together. I plugged it in to charge, powered down and left it to charge overnight. Turned it back on and was greeted by a screen that says:
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.
Volume up/down to move highlight;
power button to select.
Reboot your Kindle
Reset to Factory Defaults
So I chose the Factory Default. It doesn't seem to be completing the erase procedure, it won't boot. I tried customer service and they were less than helpful, offering me a $20 discount on a refurbished unit.
I expected more than 18 months out of this device. Anything I can do?
Click to expand...
Click to collapse
Unfortunately, if the device is 'stock' little can be done to recover from the situation you are in. Hard to tell what happened; sounds like a hardware failure but can't rule out software or malware. Sorry the news isn't better.
Did your battery die in the tablet before during this time? Might of been a failed ota.