yashsingh1/xdaforums huggingface dataset:
[7" Kindle Fire HD Android Development] Droidriven:
Ok

So, everything was fine, then you wiped system and then all this started because of that?

Restoring a nandroid backup or flashing a ROM via TWRP isn't working and adb/fastboot won't do anything even though you are booted into TWRP and should TWRP natively connect to both with no issues?

Are you certain the full USB drivers are installed?

Or do you only have the drivers that auto install when you first connect the device?

Did you have USB debugging turned on before this happened?

Terminal in TWRP is doing nothing even though TWRP natively has access to everything and can do whatever it wants to any part of the device? Very strange.
[7" Kindle Fire HD Android Development] Dishe:
Sort of- the power thing (unable to maintain sleep mode and failure to boot / dying if plugged in unless system is booted) started first, which led me erasing the sys partition. I erased sys foolishly thinking if it was a software issue, maybe I wanted to completely wipe out all traces of it and start over with a different rom. I forgot that this would make my system unbootable and I should have first checked to make sure there's a way to load something on to it.

As for drivers- this is the same PC used to initially install twrp and beanstalk rom. It was years ago, but pretty sure I must have installed proper drivers for it to work.

As for USB debugging- I don't recall. I'd guess so, but not sure I had any reason to check post custom Rom installation. I'd assume it came enabled.

Terminal command in twrp works, I'm able to type reboot bootloader and it reboots... But nothing comes on. It seems like it's dead after that. I tried plugging it in just in case it was active but not showing me anything in screen, but I feel like if it weren't shut off already, plugging in the charging curcuit would have. Just like while it is booting and I plug it in, it shuts off instantly, it might be doing that here too.

Is this weird or what?
[7" Kindle Fire HD Android Development] Droidriven:
If it is responding when plugging into PC, regardless of results, means some kind of connection is being made, whether it be a recognized connection or not.

If it isn't at least popping up and disappearing in device manager as some kind of device when connecting(recognized or not) but before it shuts off then its only responding to charge, as you somewhat surmised previously.

If you didn't turn USB debugging on yourself then it wasn't on, its never on by default that I know of. Without it turned on, adb and fastboot aren't gonna do anything anyway, that I know of.

Try using the terminal in TWRP and enable USB debugging by this command:

/data/property/persist.service.adb.enable

The path may not be correct, I don't have my Tate on hand to verify the path but what I posted is the general path. It may be different so you may need to verify that first. It may not even work because of the system wipe that you did, but its worth trying just in case that is blocking you.

There has to be way to push a copy of the system .img via adb with dd command or fastboot flashing. Unless the issue is a mix of having a faulty USB port, which is preventing you from replacing the system that you wiped and the previous behaviour being caused by a bug in your ROM. I know that when my Tate is plugged in, the touchscreen acts freaky and has been fickle about making a connection to charge when powered off and left that way for a while until the battery loses all charge. This didn't start until after flashing Lollipop and it's been that way on ROMs I've tried since then, it may be something that was/is in CM/LOS that no one has bothered to fix.
[7" Kindle Fire HD Android Development] Dishe:
I appreciate you not giving up on me. Makes me want to try again.

I checked the path in file manager on twrp, but data is wiped, and contains only one folder, called Media. Inside there is o/twrp and inside that is a single file, .twrps.

If I try mounting USB storage, and click the button to reveal command line responses I can see it says E:Unable to find storage partition to mount to USB.

Is that normal?
[7" Kindle Fire HD Android Development] Droidriven:
If Tate had an external SD card slot or was OTG capable, I could probably make recovering easier. Unfortunately, I think we may be at the end of the road where androids go to die.
[7" Kindle Fire HD Android Development] jjkrause1:
For me, it isn't related to sleep or whether the cable is plugged in. It's completely random. It usually happens while being used, but not necessarily under heavy use.

I just tried this, to no avail.

I'm starting to wonder if it's an eMMC (sdcard) failure. I got the "Encryption unsuccsessful... Reset phone" error around the time this first started happening, which was what led me to do the full wipe. Could that be a sign of eMMC failure?
[7" Kindle Fire HD Android Development] chris8189:
Thanks so much for this advice. I was also having problems with not getting past the initial set up screen. I have now managed to successfully upgrade to the latest CrDroid version 7.1.2-20171217-tate-v3.8.4. I then did as advised and went back into TWRP and flashed GApps. Rebooted and everything now working. This has transformed my dad's 2012 Kindle Fire and brought it into the present day! He's over the moon with it now running (near) stock Android. He's always hated the Kindle OS, but now loves using his tablet.

Thanks to everyone on this thread for their help and advice, and also to the devs which continue to work hard to put life back into these devices.

Chris
[7" Kindle Fire HD Android Development] jjkrause1:
crDroid fixed mine too! No more reboots.

There's no camera, and Plex will only work if I set the home-streaming quality to 720 HD (2 mpbs) or less, but that's not a deal-breaker since my 2 year old uses this tablet. YouTube Kids and the Teletubbies app work flawlessly :)

Thanks for the suggestion!
[7" Kindle Fire HD Android Development] Devo7v:
So I made a mistake. After 2 years of not using my Kindle, I decided to flash crDroid today and everything was working great. Not remembering how I originally installed TWRP, I decided to flash Magisk, obviously this was the mistake. Magisk overwrote my boot img which removed boot 2. Now I'm stuck at the orange Kindle fire logo since boot 2 is gone and I'm not sure how to proceed. Does anybody have any advise?
[7" Kindle Fire HD Android Development] mikeataol:
Do you have a fastboot cable?

pretty easy with one, I've never succeeded without one
[7" Kindle Fire HD Android Development] Devo7v:
I don't, I guess I'll have to see if I can get into fastboot without it, otherwise it's probably not worth it to purchase one.
[7" Kindle Fire HD Android Development] Corduroysack:
I had exactly the same problem and got a fastboot cable off ebay from China (under £5) and couldn't get it working so for 6 months a had a brick.

I read loads of threads and started using adb commands on another device I had (plus I'd learnt how to properly install my drivers on Windows 10) and decided to have another go at. Luckily before I'd flashed anything I'd backed up my kindle partitions.

Finally got the fastboot cable working (user error before) so I pushed my back up I'd made onto the kindle and it worked. Fastboot cable is a must. Did you backup before doing any thing?
[7" Kindle Fire HD Android Development] Devo7v:
I have a fastboot cable coming tomorrow so I'll be about to start trying things. I'm pretty sure I have a back up, but it's been a couple years so I could be wrong. Is there any reason I need to reflash a backup? From what I can tell I just overwrote the boot img so I should just be able to reflash everything in Step 5 of the boot 2 thread, but again I could be wrong. I'll give it a shot and let you know how it goes.
[7" Kindle Fire HD Android Development] Corduroysack:
I was just so relieved I'd got it responding I decided to go back to stock then the following day I flashed a custom rom on it again lol. Maybe you could just flash twrp again to fix it, yeah report back on what you did interested to see if I took the long route ☺️
[7" Kindle Fire HD Android Development] cw-kid:
Hello

I need some advice please.

I have an Amazon Fire 7 5th Gen with CM 12.1 on it currently. I followed a Youtube video, which I cannot find now.

I used the Flash Fire app to do it and it doesn't currently have the TWRP recovery installed, as when I go to the boot loader it says "Amazon System Recovery <3e>"

SuperSu is also installed and showing in the app drawer.

I am not sure how to install TWRP.

Can I just use Flash Fire app again to upgrade it from CM 12.1 to CM13 Marshmallow or CM14.1 Nougat etc ?

Can someone point me in the right direction!

Thank you.
[7" Kindle Fire HD Android Development] Devo7v:
Success. It took me longer to download the files than it did to restore the tablet. The links in the OP take you to DevHost which as far as I could tell was full of spam, so I was able to find another link that had all the files I needed and the md5 matched. Here's a link to all the files needed for this: https://androidfilehost.com/?w=files&flid=34232.

I had to buy a fastboot cable to get the tablet into fastboot mode, then the only thing I did was step 5 in the bootloader thread:

Once I did this boot 2 was working again, but I was worried about the disclaimer about not flashing the freedom-boot.img with a custom ROM so I reflashed crDroid again and booted up. It booted successfully and everything was as I had left it, apps and data untouched. So I'm wondering if I could have just flashed the freedom-boot.img, then crDroid and be done. Either way everything is working perfectly although pretty slow because of the 6 year old hardware.
[7" Kindle Fire HD Android Development] Corduroysack:
Excellent news mate its such a relief when it works again :D :D
[7" Kindle Fire HD Android Development] andr01dfr3ak:
This ROM works well on my device, and just like stock ROM, I do not expect it to be fast.

Currently, I am trying to build this ROM so I can get the latest security patches and any other enhancements the LineageOS community has made, but as always, I get the error that can be found in the image below.

What do I do about this? I already have the proprietary files set up (cloned from KFire-Android on the cm-14.1 branch), and I am currently using transi's device trees (since the official CM and LOS ones are on cm-12.1, and basically dead). If I can't build this, I can't go build lineage-15.1 yet.

EDIT: The file that was supposed to be attached here is now below this post. You'll figure out why.
[7" Kindle Fire HD Android Development] andr01dfr3ak:
I actually forgot to send the file needed. That's really sad.
[7" Kindle Fire HD Android Development] transi1:
new build lineage-14.1-20180326-UNOFFICIAL-tate.zip

http://www.mediafire.com/folder/u7sb7p10ik7v0/tate
[7" Kindle Fire HD Android Development] andr01dfr3ak:
I always enjoy these builds, even if they're still on Nougat. Good job on building these.

At this point, you should become a maintainer for this device, since these builds basically work well (apart from Bluetooth and stuff).
[7" Kindle Fire HD Android Development] u2berggeist:
Possibly a noob question, but I've been trying to find a ROM that can adjust the back light. For some reason, the built in slider and other things doesn't do that. Going into battery saver mode on some of your ROMs seems to dim the backlight, but nothing else does.

Note that this happens with `cm-13.0-20160508-UNOFFICIAL-tate`, `cm-14.1-20161122-UNOFFICIAL-tate` , and`lineage-14.1-20180326-UNOFFICIAL-tate`.

Is there something I'm missing? Is this just a general accepeted thing with ROMs? Or is there a utility that I'm supposed to install that I haven't?

Thanks,
[7" Kindle Fire HD Android Development] mikeataol:
you should check all the settings related to the display

I turn off "Adaptive Brightness" and "LiveDisplay" options, and the slider has always worked for me, including on this 14.1-20180326
[7" Kindle Fire HD Android Development] u2berggeist:
That worked for me! Thanks.

On my Pixel, it does adaptive brightness, LiveDisplay (or whatever the blue shift thing is officially called), and the slider at the same time. Weird that it doesn't allow it here.
[7" Kindle Fire HD Android Development] andr01dfr3ak:
At any point in time, will there be TWRP 3.2.0 for this device? I have a completed build of LineageOS 15.1 ready (that is not a joke) and that build requires an up-to-date version of TWRP for it to work.
[7" Kindle Fire HD Android Development] mikeataol:
Edit: oops wrong thread
[7" Kindle Fire HD Android Development] monster1612:
What happens if you flash it on the latest 3.x port? Does it complete successfully?
[7" Kindle Fire HD Android Development] andr01dfr3ak:
TWRP does compile successfully, but the recovery image is larger than the partition on the device itself. I'm already having difficulties shrinking the size of TWRP so I can actually flash it onto the device.
[7" Kindle Fire HD Android Development] monster1612:
Try building TWRP against r3t3ch's device-specific repos in the cm-14.0 branches. They have some patches to fix the temperature display in TWRP, and I think they should compile as is.

I'd asked specifically about flashing your lineage 15.1 against the latest compiled TWRP, but I think just compiling 3.2 would make sense anyway. Do you have any source on GitHub? (I'd be interested in running a build for the 8.9" if possible.)
[7" Kindle Fire HD Android Development] javedgh:
usb otg works on this tablet i have also but usb otd not works any idia how use usb otb this amazon tate
[7" Kindle Fire HD Android Development] Droidriven:
Tate does not support OTG that I know of.
[7" Kindle Fire HD Android Development] Duncan Idaho:
So, I have a question, or more of an inquiry, I downloaded, this version and I installed the GAPPS for 7.1.2 but the issue was, that it never went pass the CR DROID stuff, my kindle is a kindle fire HD 7" 2nd gen. I am honestly puzzled why it failed.
[7" Kindle Fire HD Android Development] Duncan Idaho:
I come with a 2nd question, assuming I manage to get this working, will FGO run on this rom?
[7" Kindle Fire HD Android Development] Droidriven:
That is because that ROM is for the Tate, 1st gen(2012) kindle fire hd 7.

It is not for 2nd gen. You've probably bricked your device. If you created a nandroid backup in recovery before flashing the ROM and you can still boot into recovery, restore that backup.

If you didn't create a nandroid backup before flashing, try finding your stock firmware that has been converted into a flashable zip that can be flashed using a custom recovery(not the same thing as your stock firmware that is flashed via fastboot, that firmware file won't work).

If there is no stock flashable zip that can be flashed in recovery, you'll probably have to flash a copy of your stock firmware via fastboot.
[7" Kindle Fire HD Android Development] Duncan Idaho:
But mine is a Tate.

A website had a copy of it and I've been able to flash a variety of tate roms on it.

But atm I am searching ofr a rom that can let me play Fate/grand order, seems every cyanogen or variant such as slim comes pre rooted and even removing the bin stuff makes it impossible to play, it keeps giving me Error 60. Or is it that DW was in a dickish mood and decided to ban all custom roms?
[7" Kindle Fire HD Android Development] Droidriven:
The way to remove root is to open the SuperSU app, then open its app settings, in its settings, it will have an option to "cleanup for unroot and uninstall". This will remove root and the SuperSU app, then you boot to recovery and use the Wipe>advanced wipe option to wipe cache and dalvik cache, then reboot.
[7" Kindle Fire HD Android Development] Duncan Idaho:
Doesn't works. I tested it but FGO keeps saying Error 60.

To be exact Super SU never went beyond the step of "uninstalling please wait" for about 3 hours, and I used this tutorial the ES filer explorer option and it didn't work either. I admit I haven't wiped the caches.

EDIT: No even wiping the caches still makes FGO give out error 60. I am wondering if DW banned all Custom roms, or just cyano/linos, etc.
[7" Kindle Fire HD Android Development] Droidriven:
You should be able to remove root regardless of what ROM you have or what else is installed. You may have corrupted root in the processes that you've tried, if this is so, that's probably why its acting weird.

Does the device still have full root? Use the root checker app. Try flashing the latest version of SuperSU.zip in TWRP then factory rest, wipe cache and wipe dalvik cache, this should fix root if it's corrupted. Then try removing SuperSU the way I originally described.

Does the device have the latest version of SuperSU installed? Are the su binaries still in /system/bin or /system/xbin.

Did you have root explorer enabled in ES File Explorer? Did you use the Mount R/W option to set /system to rw?

Since you're trying to use custom ROMs you should have a setting for root access in developer options. Go to system settings>Developer options>root access and set it to "apps and adb"

Check your SELinux policy to see if it set to "enforcing" or "permissive"? You might need to find a way to set it to "permissive" to allow your changes to save.

Try booting into TWRP and connecting to adb then use adb to remove root, the su binaries and the SuperSU app.

Or you can try using the terminal emulator that is built into TWRP to remove it. The commands are the same as "adb shell" commands but with the "adb shell" part removed from the commands.
[7" Kindle Fire HD Android Development] Duncan Idaho:
Tried it on Slim, didn't work, downgraded to cyano 11, used the method on the website I linked you to.

No, it doesn't has root, I'll have to look for a superSU.zip just in case.

As I mentioned I used ES file Explorer to remove those manually.

No, after I used ES explorer to remove the two binaries I can't use ES file explorer with the root option.

I had it like this and I'd like to remove it.

Its on permissive and my changes did save. But FGO still reads the device as rooted, even when it is not rooted.

Any links for this if you would be so kind?
[7" Kindle Fire HD Android Development] Droidriven:
[/QUOTE]Very strange, I think you might have to start over from scratch.
[7" Kindle Fire HD Android Development] Duncan Idaho:
Very strange, I think you might have to start over from scratch.

I just flashed Paranoid Android and the issue is the same, Super SU claims its binary is occupied, then when I ask for full unroot with root access for APP's and ADB its just stuck there saying "uninstalling, please wait" This is a Fresh install of paranoid android.

I'll be trying the ES file explorer method and see if that works.

Also the SELinux status is set to permissive.

Ok this is interesting, super SU isn't just a couple of binaries, it seems there are a dozen or so files, all related to super SU.

Ok, root checker claims that even with root access under dev options set to app and adb the device is rooted. Installing gmail just in case I get an error.

Error 60, in spite of my device being unrooted.
[7" Kindle Fire HD Android Development] ipdev:
If you are looking to un-root.

https://xdaforums.com/showpost.php?p=63615067

Edit:

You might want to look into ES. Most have stopped using it.;)
[7" Kindle Fire HD Android Development] Droidriven:
I actually meant that you might have to flash stock and start over with flashing TWRP then your ROM. Then do the unroot correctly using SuperSU settings.

Or, try extracting your ROM zip on PC, remove all the root stuff, zip the ROM, flash the ROM.

Or try this:

Did you do a "clean install" of PA?

To do a clean install:

Boot to TWRP, select "Wipe" then select "advanced wipe", select:

system

data

cache

dalvik cache

Swipe to wipe

Then go back to home in TWRP, select "install" then flash your ROM.
[7" Kindle Fire HD Android Development] Duncan Idaho:
That can be done? Because whenever I install the firmware, 7.2.3 it never touches the bootloader.

So this is possible? all I found on it was SU and busybox inside xbin. I am going to try this for certain.

What I did was factory reset then wipe caches, flash PA, flash Gapps, wipe caches.

Edit, seems that removing su and busybox makes the installer fail, any ideas how do I fix this?

Edit I am dumb, managed to make a working zip.

Hmm, TWRP claims I am not rooted, but even without busy box and super SU it still pops #superuser and the options inside settings>developer options,
[7" Kindle Fire HD Android Development] Droidriven:
So you're good now?
[7" Kindle Fire HD Android Development] Duncan Idaho:
No, error 60. Where else aside bin, xbin and apk would SU hide?

The Flashable zip also doesn't works, FGO still claims the device is rooted.

TWRP shows a SuperSU in root, curious.
[7" Kindle Fire HD Android Development] Droidriven:
When you zipped the ROM, what program did you use to compress it? Did you choose the highest compression level?

When you flash the ROM, do a clean install as instructed earlier, I mean specifically a clean install, not just the normal wipes and flash. Try with the unmodified ROM zip that you originally tried.

Boot to recovery, select "Wipe" then select "advanced wipe" then select these options:

system

data

cache

dalvik cache

Then swipe to wipe then install the unmodified ROM and Gapps. This should remove everything from before that might still be lurking in system(factory reset and wiping cache doesn't touch system, that's probably why you're still having issues even after flashing the ROM multiple times, you haven't wiped the system partition), after booting the ROM, don't install any apps yet. Now, use the script that you were given in the link earlier by the other member a few posts up, it should simplify removing root. After running the script, then install your extra apps and see if it still acts weird.
[7" Kindle Fire HD Android Development] Duncan Idaho:
Windows 7 default compressing option.

Here is what I did, I did a clean install with the modded files, all I did was to take from xbin SU and Busybox, nothing else. I searched for SU, Super, etc. and the files aren't being shown at all.

The clean install came after you instructed me how to do the clean install.

I did this. I wiped everything BUT the internal storage.

I have wiped system but it isn't erasing the thing. But Ill try it this way.

It isn't lodged on system, its lodged on /

instead of being /system/supersu

is /supersu.

Can I erase this via ADB or fasboot commands?

Edit I am a blasted idiot, TWRP can erase it, which I just did. Let's see what happens.
[7" Kindle Fire HD Android Development] Droidriven:
I had already mentioned some of the other tools in TWRP, one of them had to work.

It's still strange that a clean wipe and install and then using SuperSU settings to unroot is still giving issues. But, there is still the script from the post above from the other member that replied to you, it is commonly used, though I have never had to use it. But that's only because of device and Android version differences.
[7" Kindle Fire HD Android Development] Duncan Idaho:
I installed the zip without the supersu and I had previously erased it (and yes I did a clean install) seems the PA rom as well others are designed to somehow copy these files to / on boot because the folder is back.

So following your suggestion, I did not install anything, I chose to use the unroot zip and I am booting back into twrp, I go to file manager. Super SU is back.

WTF.
[7" Kindle Fire HD Android Development] Droidriven:
It's becoming a maze, at this point, I think I would need the device in front of me to figure it out. I've never had this issue, it isn't making sense snymore. I'm trying to help without leading you a direction that makes things worse. I can't seem to put my finger on it.