Kindle Fire HDX 7, safestrap, recovery but no OS installed... - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

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.

Related

[Q] Nook Tablet Boot Loop

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.

Stuck on B&N software with custom touchscreen firmware

I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Thank you
asawi said:
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
That should work excellently, thank you very much.
Nookuser19 said:
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Click to expand...
Click to collapse
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
topdawg7793 said:
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
Click to expand...
Click to collapse
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
asawi said:
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
Click to expand...
Click to collapse
Just used a 4gb class4 through a memory stick reader. It's working beautifully now, except I need to repartition it.
Interesting bug though, the home button won't take it out of sleep any more. Only the power button..?

Nook BNTV250 touchscreen on CM 10.1 suddenly stopped responding

Here is what I did, on a new Nook Color (I guess mine is Nook Tablet) 16GB, I used MicroSD image with cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img to boot into CWM
Did factory wipe and Dalvik wipe.
Installed cm-10.1.3-acclaim.zip
Did another quick factory wipe
Installed gapps-jb-20130812-signed.zip
Everything was perfect, booted just fine, went through set up process but at setting up google account, I went to get my password from my PC, when I got back screen was not responding. Auto rotation, volume rocker, buttons all work very fast and smoothly, but I cannot touch/tab on anything.
hydeah said:
Here is what I did, on a new Nook Color 16GB, I used MicroSD image with cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img to boot into CWM
...
Auto rotation, volume rocker, buttons all work very fast and smoothly, but I cannot touch/tab on anything.
Click to expand...
Click to collapse
The ROM build cm-10-20121231-NOOKTABLET-acclaim-HD-SDC which you use is for the Nook Tablet, not for the Nook Color.
digixmax said:
The ROM build cm-10-20121231-NOOKTABLET-acclaim-HD-SDC which you use is for the Nook Tablet, not for the Nook Color.
Click to expand...
Click to collapse
I did not do anything with the ROM on it, I simply used it to boot into CWM without having to go through partitioning the SD, etc.
PS: When I was testing above "live SD card" CM10 loaded fine and was working, a little slow but I blame the slow SD card for that..
(I booted to cwm, removed the SD card with HD-SDC and then inserted another SD with cm-10.1.3-acclaim used the CWM to install)
Everything looked like they worked just fine until suddenly touch screen stopped working. I have BNTV250. Did I just totally mess this up!
I fixed the title on 1st post, maybe I posted this in wrong section?
Have you tried rebooting with no sd-card inserted?
Press and hold power so the device shuts off completly and then restart.
Thanks Moscow for moving the thread for me.
asawi said:
Have you tried rebooting with no sd-card inserted?
Press and hold power so the device shuts off completly and then restart.
Click to expand...
Click to collapse
Asawi, no, that doesn't help. I already removed the SD card (since I flashed to 10.1, it boots into 10.1)
When I press and hold power and I keep holding with n button, it then asks me if I want to format to factory settings (I guess this is nook's own formatting tool)
Also, when I try to go into internal recovery (with no SD card) it crashes.
Is there anything I can do to just try again? Can I simply flash another copy of 10.1, maybe an earlier version or even a newer version like 10.2 over this?
I was so disappointed last night, I thought about this all night, couldn't go to sleep!
You can certainly flash the ROM and gApps again an see if that helps.
asawi said:
You can certainly flash the ROM and gApps again an see if that helps.
Click to expand...
Click to collapse
Thanks.
The ROM and gApps I listed above match each other, right?
cm-10.1.3-acclaim.zip (http://get.cm/?device=acclaim)
gapps-jb-20130812-signed.zip (http://goo.im/gapps/gapps-jb-20130812-signed.zip via http://wiki.cyanogenmod.org/w/Gapps)
btw, thanks for replying, in fact I followed your instructions to install 10.1, and here you are. :good:
Before installing cm and gapps, my nook was completely stock, I guess I really did not need to do anything before installing CM, right? Did I need to root it with a custom update.zip or something like that, or is that not necessary at all? Just boot into cwm and install rom+gapps, that's it?
Edit: Re-installed CM10.1 and Gapps, still have the unresponsive touchscreen..
I have to admit I don't know what ROMs and gApps match now. I've stayed om Succulent's CM10 on my devices becasue I've been so happy with it feel no need to upgrade. You have to check the info surronding your ROM what gApps goes with it.
Edit: It looks like you have matching ROM and gApps.
asawi said:
I have to admit I don't know what ROMs and gApps match now. I've stayed om Succulent's CM10 on my devices becasue I've been so happy with it feel no need to upgrade. You have to check the onfo surronding your ROM what gApps goes with it.
Edit: It looks like you have matching ROM and gApps.
Click to expand...
Click to collapse
Thanks for checking, I just re-installed them, still touchscreen won't respond to taps.
I can just go with what you have if it works fine. Tell me how to get them on my Nook and I will, I don't care about version of Android, just need a stable android on this device so I can buy some sesame street, disney, etc stuff for the kids since Nook OS was laggy and limited. Can I just wipe all this stuff off the nook and start over?
Is there anyway to check if touchscreen problem is physical or software issue?
What's happening to you is really odd, and it could be hardware related. Unless somehow the touchscreen drivers got corrupted during install (and that really shouldn't have happened...)
I doubt going with another ROM will help, but this is what I run:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
There is a link to the matching gApps on that page.
asawi said:
What's happening to you is really odd, and it could be hardware related. Unless somehow the touchscreen drivers got corrupted during install (and that really shouldn't have happened...)
I doubt going with another ROM will help, but this is what I run:
http://iamafanof.wordpress.com/2012/11/03/cm10-0-jelly-bean-for-nook-tablet-uploading/
There is a link to the matching gApps on that page.
Click to expand...
Click to collapse
Thanks, do I need to wipe anything to get rid of 10.1 before I install this?
I will follow this:
Download the updated CM10 12/25 ROM (cm-10-20121225-acclaim-HD-SDC.zip (GCC 4.6) (http://tinyurl.com/au32v2l) and also download the GApps file (http://goo.im/gapps/gapps-jb-20121011-signed.zip)
Do the usual wipes. Factory reset, cache, Dalvik
No go, I went down to CM10 ROM above, no luck, touchscreen is still not functioning.
I am going to use recovery by following these instructions to return this to stock OS and then take it back, this is ridiculous.
I can just use this, right: http://forum.xda-developers.com/showthread.php?t=1663836
Yes, that repart.img should work. I have used it on numeroud Tablets and it has never failed me.
Nook is going back, recovered using repart, worked very well, I don't see a trace of cwm.
Touchscreen has some issues, that's for sure, thanks for all your help.
hydeah said:
...
When I press and hold power and I keep holding with n button, it then asks me if I want to format to factory settings (I guess this is nook's own formatting tool)
Also, when I try to go into internal recovery (with no SD card) it crashes.
...
Click to expand...
Click to collapse
Sounds like you still have stock recovery.

Made a mistake. Need some direction.

I'll just get to the point.
I rooted the HDX using the towelroot app. Installed SuperSU, verified root access., all was successful thus far. At this point I installed Safestrap recovery, using the. apk.
Here's the problem. I thought I transferred the ROM and gapps package to the internal SD card. Could have sworn I did. Well I didn't. My second mistake was wiping all on the stock ROM slot once in Safestrap thinking I had the new ROM on the internal SD. Well I realized I didn't, had to leave the HDX in safestrap for a while and came back to the battery dead. Now it does not boot past the stock recovery where my options consist of reboot system or perform stock recovery. Stock recovery does nothing which is expected after my slip up.
What I'm wondering is if I can somehow flash the recovery back to my device via ADB? Or maybe the stock ROM? If not, do I have any other options.
Disclaimer: yes, I made a stupid mistake, I admit it. Please keep the flaming to a minimum.
yes you did.
mangomango said:
I'll just get to the point.
I rooted the HDX using the towelroot app. Installed SuperSU, verified root access., all was successful thus far. At this point I installed Safestrap recovery, using the. apk.
Here's the problem. I thought I transferred the ROM and gapps package to the internal SD card. Could have sworn I did. Well I didn't. My second mistake was wiping all on the stock ROM slot once in Safestrap thinking I had the new ROM on the internal SD. Well I realized I didn't, had to leave the HDX in safestrap for a while and came back to the battery dead. Now it does not boot past the stock recovery where my options consist of reboot system or perform stock recovery. Stock recovery does nothing which is expected after my slip up.
What I'm wondering is if I can somehow flash the recovery back to my device via ADB? Or maybe the stock ROM? If not, do I have any other options.
Disclaimer: yes, I made a stupid mistake, I admit it. Please keep the flaming to a minimum.
Click to expand...
Click to collapse
If you cannot get into safestrap . You're simple no flaming answer is ,NO .
http://forum.xda-developers.com/showthread.php?t=2795602 post 37 ?
Good find. I'll check it out. Thank you.

Completely bricked help!!!

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.

Categories

Resources