I'm no spring chicken when it comes to HDX flashing. I've put cyanogenmod and nexus HDX on this thing a few times but now i'm pretty sure i've killed it.
I decided to upgrade to the latest Nexus HDX build and put it in safestrap and everything, then while it started loading up, i got into the dreaded bootload loop. Any help would be great, i haven't tried the adb method that was here about a year ago as the ADB commands refuse to work as it keeps saying "device not connected" in spite of ADB drivers being installed.
HELP!
godsburden said:
I'm no spring chicken when it comes to HDX flashing. I've put cyanogenmod and nexus HDX on this thing a few times but now i'm pretty sure i've killed it.
I decided to upgrade to the latest Nexus HDX build and put it in safestrap and everything, then while it started loading up, i got into the dreaded bootload loop. Any help would be great, i haven't tried the adb method that was here about a year ago as the ADB commands refuse to work as it keeps saying "device not connected" in spite of ADB drivers being installed.
HELP!
Click to expand...
Click to collapse
Slow please. Give a little more info.
Which Safestrap Version do you use? What CM ROM did you flash? Did you create secondary slots in Safestrap, or did you Flash CM and/or Nexus to the stock slot? Did you backup your Fire OS before you flashed any ROM?
ADB connetion from PC to HDX in Safestrap is highly problematic, there could be a chance using e.g. Linux though.
I was using 3.75, upgrades to 4.0.1 didn't work and I'd flashed cyanogen mod, stock, and nexus several times before without a hiccup.
I can pull the "factory reset" menu up with the orange fire letters but nothing will load past the silver letters.
I haven't used fire os for maybe a year now. I've been running nexus for 6 months or so.
Can you still boot into Safestrap?
EncryptedCurse said:
Can you still boot into Safestrap?
Click to expand...
Click to collapse
Nope, just keeps flashing to and looping silver kindle fire logo. I fear for the worst
godsburden said:
Nope, just keeps flashing to and looping silver kindle fire logo. I fear for the worst
Click to expand...
Click to collapse
You mentioned Safestrap 3.7.5 & 4.0.1. Sounds like you attempted a SS upgrade without upgrading to FireOS 4.5.2 first. If so you're done.
Related
Hi all,
I had rooted my nook tablet using snowball mod about a week ago and I loaded CWM on to the emmc using indirect's one-click recovery flash app. It was all working fine.
I wanted to return to stock and so put the 1.4.0 zip on my sdcard and rebooted. But it went straight to CWM. So I remembered i had to restore the stock recovery and rebooted and flashed stock recovery. only this time, I used the updated version of the one-click app (the updated version of 26th Jan) and hit reboot to recovery. This caused my NT to be in a boot loop ever since.
I have tried the 8 failed reboot method to initiate a factory reset but it didn't work. I also tried using the Nook Recovery Fix but i can't get to install the drivers since if I connect the NT to my computer, it keeps rebooting over and over again and I can't get to show for longer than 2 secs in device manager to install the drivers for Windows. (I was using it on Ubuntu till now).
My NT just turns on, the black screen n logo shows (The "With adobe reader" screen) however it doesn't go any farther than that. It just shuts down. The white nook screen does not even show. It's like it's going through multiple failed reboots without me holding down any buttons. Any help from you guys is greatly appreciated. Thanks.
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Data Injures said:
You have to make a bootable SD with CWM on it so that the computer can actually catch the Nook long enough to do anything. Also, I'm pretty sure the B&N drivers restrict what you can do, but I'm not really sure what's gonna happen if you connect for the first time in CWM. I say use the Nook and Zergy method for the drivers (the first part, runmefirst.bat)
After that, try the Nook Recovery. It should work. I'm not positive on this, but from what I've read, that's what you do.
CWM SD:
http://forum.xda-developers.com/showthread.php?t=1446987
Really though, no promises. Good luck. Lemme know how it turns out.
Click to expand...
Click to collapse
Thanks a lot for your suggestion! I just spent a half hour on the phone with B&N customer service and they agreed to ship out a replacement device. The rep said it was a hardware failure that was causing it to act like that. I was a bit surprised at that. I'm not sure she knew what she was talking about. Anyway I had bought mine off craigslist. And now I'm getting a new device so I guess I can't complain. But I'll try later tonight to restore this one using the bootable CWM you linked to. Thanks again.
Follow Up
Just thought of posting a follow up. The bootable CWM method worked. I was able to fix the recovery. Most certainly not a HW problem like the tech claimed. It's working fine now.
I'm glad to hear that! Now if I have the same problem in the feature I can just follow my own advice. Lol
Sent from my DROIDX using XDA App
So I have basically the same problem. My girlfreinds nook was rooted but the OTA update stopped the root from being effective. I tried the sd card revert to 1.4.0 and I hade the problem with the "n" butting not working. When i tried the 8x reset the nook went into an endless boot loop where I see the back screen and the next white screen flashes for like 2 seconds and then reboots. I tried to make the CWM SD card but it still just reboots. My question is that since i never had the CWM mod installed am I pretty much hosed or am I doing something wrong?
What are you using to make the CWM SD card? I strongly recommend using GParted either from a Linux live image or there is a GParted live image you could use. When it works correctly, the bootable SD card that should stop the boot loop.
But why did the boot loop problem occur in the first place ?
sailerph said:
But why did the boot loop problem occur in the first place ?
Click to expand...
Click to collapse
From what I know of, if you install stock recovery and hit the reboot to recovery button, it initiates the stock recovery which then causes the error. Though I don't know the reason behind nor what's causing the problem, just relaying what I have read around the forums.
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Denmmurray said:
From what I understand when you flash CWM it's recovery replaces the stock recovery so when you try to install the stock recovery, which you should not do, it is trying to pull from something that's no longer there. I learned this lesson the hard way.
Click to expand...
Click to collapse
Hm I actually unrooted my nook a couple of times to play with it. I reinstalled the stock recovery from the app on multiple occasions, but instead of clicking reboot to recovery, I ran the one click unroot and never ran into any trouble.
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
The ROM may not have Loki support...if you are using the older twrp version it may not auto lokify the ROM...try updating your recovery and give it another go
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would recommend trying out Philz ( cwm ) recovery possibly. There have been random issues like yours reported and usually updating the recovery or just trying a different ROM all together gets better results.
You shouldn't need to go back to stock mdk for anything since you're already rooted and have a custom recovery.
Sent from my SCH-I545 using Tapatalk
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
FranklinPIerce said:
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
Click to expand...
Click to collapse
Let me suggest trying liquid smooth 4.4
Awesome ROM to try.
Sent from my SCH-I545 using Tapatalk
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would try their suggestions. For future reference though, you can use heimdall instead of Odin on Linux. I love it I think its better than odin
Sent from my unknown using Tapatalk
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
FranklinPIerce said:
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
Click to expand...
Click to collapse
That's odd that flashing Philz didn't work for you. Its a pain I know but probably if you had wiped the phone with stock mdk then tried again it woukd have worked I bet. I had to do that with this phone when i got it. It came with twrp, but was acting real funny not always getting into recovery or just hanging up on reboot. But you have a working twrp so that's good too.
I don't believe liquid has the built in app permissions you're talking about but maybe I missed it. I don't really mess with permissions. Liquid has everything else though and then some!
I know some Roms were having problems with unified builds. I know liquid does not at this point. Maybe it'd be worth trying just so you're not on stock lol you may want to look into the Loki doki zip that you flash after flashing the ROM. I've seen some people on here using that when they were getting the same error you were. Just an idea.
Good luck man!
Sent from my SCH-I545 using Tapatalk
Del
Ikolocol said:
Hello,
in may this year i bought my HDX7. I did not like fire os so i decided to install a custom rom (HDX Nexus v2.0.5 http://forum.xda-developers.com/kindle-fire-hdx/development/apollo-nexus-v1-1-t2835838). I followed this guide http://forum.xda-developers.com/kin...tut-kindle-rooted-otaed-safestrapped-t2954893 and everything went smoothly. I was rooted, safestraped (3.75). I've made second partiton for custom rom and installed it. It worked! Since then i did not change ANYTHING in my device but one day (week ago?) when i was watching a Twitch stream, tablet froze. I shut it down by holding power button. So the problem is it bootloops now between grey kindle fire logo and safestrap: dissabled screen. I guess im soft bricked? I tried this http://forum.xda-developers.com/showthread.php?t=2793253 but no results. Adb, fastboot and safestrap seems to be working. Where should i start?
I do not have backup/recovery file since i did nothing with stock partition.
Last known OS: FireOS 13.3.2.4 and HDX Nexus v2.0.5
Safestrap: 3.75
Thanks for your time.
Click to expand...
Click to collapse
Since the device is still under warranty contact Amazon regarding a replacement. They most likely won't check that you rooted, installed Safestrap & Nexus, etc. This is the fastest and really only way to get you out of this problem.
Can actually boot into the Safestrap interface?
I'd just try reflashing the same ROM.
del
Ikolocol said:
i cant flash stock rom because:
Installing '/sdcard/update-kindle-13.3.2.4_user_324002120.zip' . . .
Skipping MD5 check: no MD5 file found
Skip modem update
Updating partition details. . .
and i cant find option to disable md5 verification. so yeah.
im thinking about flashing ggow's hdx roms (http://forum.xda-developers.com/kin.../hdx-stock-images-pre-rooted-updates-t2911954) but i dont see v. 13.3.2.4. Is flashing 13.3.2.6 even safe?
Click to expand...
Click to collapse
You can NOT flash a pure 'stock' rom in Safestrap v3. Feel lucky it failed as doing so probably would have hard-bricked your device. I still feel there is a hardware problem but suppose it is best to rule out potential software issues. Thoughts:
- if you have room on your device try backing up your current secondary slot in Safestrap v3
- try flashing Nexus v2.0.5 over existing contents of secondary slot (dirty flash)
- if that fails try deleting/recreating secondary slot and then flash v2.0.5 again
- if issue persists switch to stock slot and flash SS safe variant of FireOS 3.2.6 (ok as prior version was 3.2.4)
- last option is to flash Nexus v2.0.5 to stock slot
Do NOT perform a 'factory reset' from the Kindle recovery menu accessed via power+vol-up. This will not help and will likely result in a fatal bootloop. Good luck.
del
I have followed the latest guide from Hashcode on xda developers. Everything works according to my feedback from the tablet and what his guide says is supposed to happen. Fastboot worked great, i moved the files over as instructed. My tablet loads into TWRP, I move the files over with adb push from cmd prompt and then when I try to flash the two .zip files it does nothing.
It reports a successful flash of both the cm and gapps. Then I reboot as the guide says, and the Kindle blue logo comes up and sits there. I've left it sitting for 30 minutes to ensure it is not loading slowly. Any ideas on how to get this thing booting up properly?
I've attempted a lot of searches on here as I generally lurk, been around since 2013 10.1 cm using it on my KFire HD. Really want to get rid of the old cm build, but it just won't boot up after a successful flash.
Any help is appreciated!
Dugite said:
I have followed the latest guide from Hashcode on xda developers. Everything works according to my feedback from the tablet and what his guide says is supposed to happen. Fastboot worked great, i moved the files over as instructed. My tablet loads into TWRP, I move the files over with adb push from cmd prompt and then when I try to flash the two .zip files it does nothing.
It reports a successful flash of both the cm and gapps. Then I reboot as the guide says, and the Kindle blue logo comes up and sits there. I've left it sitting for 30 minutes to ensure it is not loading slowly. Any ideas on how to get this thing booting up properly?
I've attempted a lot of searches on here as I generally lurk, been around since 2013 10.1 cm using it on my KFire HD. Really want to get rid of the old cm build, but it just won't boot up after a successful flash.
Any help is appreciated!
Click to expand...
Click to collapse
full file names?
twrp version?
there is no 8.9 first gen
volume buttons on the side or back?
0, 1, or 2 cameras? front and/or back?
Sent from my KFFOWI using Tapatalk
Sounds like you're on the wrong forum.
http://forum.xda-developers.com/kindle-fire-hd
I have a Kindle Fire HDX 7, rooted it, installed safestrap, then CM 11 in stock slot..
Running great for agres, but suddenly some CM 11 nightly updates appear, then start to download and update.
Update doesn't work, but the tablet will go into TWRP recovery that is part of Safestrap. But it says no OS installed, so it won't boot.
It did say safes-strap disabled, but last time I turned it on it said safe-strap enabled. Still wouldn't boot, though.
Factory reset didn't help.
The tablet isn't recognized by windows, so unless I can find a way to get a new rom onto the tablet, I can't flash a new rom, so I have a brick.
This is why I don't like tablets with no SD card slot. If I had an SD card slot, no problem.
Does the mount option in TWRP do anything?
Thanks for your help.
Nagoyablue73 said:
I have a Kindle Fire HDX 7, rooted it, installed safestrap, then CM 11 in stock slot..
Running great for agres, but suddenly some CM 11 nightly updates appear, then start to download and update.
Update doesn't work, but the tablet will go into TWRP recovery that is part of Safestrap. But it says no OS installed, so it won't boot.
It did say safes-strap disabled, but last time I turned it on it said safe-strap enabled. Still wouldn't boot, though.
Factory reset didn't help.
The tablet isn't recognized by windows, so unless I can find a way to get a new rom onto the tablet, I can't flash a new rom, so I have a brick.
This is why I don't like tablets with no SD card slot. If I had an SD card slot, no problem.
Does the mount option in TWRP do anything?
Thanks for your help.
Click to expand...
Click to collapse
Unfortunately there is no way to move files onto this device (specifically 3rd gen HDX running Safestrap v4) without a functioning rom. Best bet is to use the File Manager in Safestrap recovery to search the device for the CM11 zip that was originally used to populate the Stock slot. If found you might be able to use that to recover the device (install to the STOCK slot).
You mentioned a factory reset. If performed from the stock recovery menu (outside Safestrap) the device is likely toast.
Nagoyablue73 said:
I have a Kindle Fire HDX 7, rooted it, installed safestrap, then CM 11 in stock slot..
Running great for agres, but suddenly some CM 11 nightly updates appear, then start to download and update.
Update doesn't work, but the tablet will go into TWRP recovery that is part of Safestrap. But it says no OS installed, so it won't boot.
It did say safes-strap disabled, but last time I turned it on it said safe-strap enabled. Still wouldn't boot, though.
Factory reset didn't help.
The tablet isn't recognized by windows, so unless I can find a way to get a new rom onto the tablet, I can't flash a new rom, so I have a brick.
This is why I don't like tablets with no SD card slot. If I had an SD card slot, no problem.
Does the mount option in TWRP do anything?
Thanks for your help.
Click to expand...
Click to collapse
I had the same issue myself (I had actually formatted the system partition and the sd card without thinking), you might try another USB port and/or another cable, even another computer if you can get access to one.
after trying to get ADB to see my tablet for 3 hours I finally moved to another USB port and it worked right away.
once it saw the tablet it only took a few moments to sideload another rom.
on a side note when it happened to me I was on an unlocked bootloader and was not using safestrap so I cant recall if the ADB sideload feature is even available in safestrap... but if so its what worked for me.
firefly6240 said:
I had the same issue myself (I had actually formatted the system partition and the sd card without thinking), you might try another USB port and/or another cable, even another computer if you can get access to one.
after trying to get ADB to see my tablet for 3 hours I finally moved to another USB port and it worked right away.
once it saw the tablet it only took a few moments to sideload another rom.
on a side note when it happened to me I was on an unlocked bootloader and was not using safestrap so I cant recall if the ADB sideload feature is even available in safestrap... but if so its what worked for me.
Click to expand...
Click to collapse
Unfortunately, Safestrap v4 has no native support for adb. There is no way to push a file to the device without a functioning rom.
Davey126 said:
Unfortunately, Safestrap v4 has no native support for adb. There is no way to push a file to the device without a functioning rom.
Click to expand...
Click to collapse
It's a moot point now, as the battery is dead, and the tablet won't charge, or won't turn on if it is charged. Looks like it's completely dead. Any one need a hdx 7 for spares?
Nagoyablue73 said:
It's a moot point now, as the battery is dead, and the tablet won't charge, or won't turn on if it is charged. Looks like it's completely dead. Any one need a hdx 7 for spares?
Click to expand...
Click to collapse
It might turn on with a long press of the power button (20-30 sec) but that will just get you to Safestrap v4 recovery. Beyond that there isn't much hope; factory reset may have killed it (resetting is a no-no with Safestrap installed). Sorry for your loss.
Nagoyablue73 said:
It's a moot point now, as the battery is dead, and the tablet won't charge, or won't turn on if it is charged. Looks like it's completely dead. Any one need a hdx 7 for spares?
Click to expand...
Click to collapse
Davey126 said:
It might turn on with a long press of the power button (20-30 sec) but that will just get you to Safestrap v4 recovery. Beyond that there isn't much hope; factory reset may have killed it (resetting is a no-no with Safestrap installed). Sorry for your loss.
Click to expand...
Click to collapse
If you still have this device *and* it can boot into Safestrap recovery there may be hope. See this thread for new findings courtesy @skoop99.
Davey126 said:
If you still have this device *and* it can boot into Safestrap recovery there may be hope. See this thread for new findings courtesy @skoop99.
Click to expand...
Click to collapse
Thanks for the heads up! (Runs to get kindle HDX 7 out of the bin).
It does indeed power up and boot into safestrap.