yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 Original Android Development] caribecharlie:
Just installed the newer Ubuntu now, big thanks! as i mentioned, quite new to the linux experience after decades on PCs.

so just follow the guide verbatim? and what is the latest lineage rom available to load after the rooting process?

To sum up

Fire HD 10 7th Gen

OS 5.7.1.0 (659664620)

Ubuntu 20.04 LTS running on VMWare Workstation 17 Player on my windows 8.1 laptop potato
[Fire HD 8 and HD 10 Original Android Development] placeholdername:
Hello, pretty much first time using mobile touch devices(did this for someone), had Fire OS 5.7 "40.6.5.9_user_659664620" on it dated Aug 1 IIRC and it's the latest related to this post, their update page says "5.3" though, probably the original. Had some light Linux experience and used Debian, if you don't have storage and just a 2GB system you could probably get away with a live CD having an Amazon ROM and Lineage. Followed the instructions and didn't have to open the device up. Installed Lineage and GApps afterwards, GApps updated fine. A bit of warning, Amazon messed up their update downloads, if you try to get HD 10 it gives you HD 8, ended up doing a factory reset because I was getting errors using the HD 8 file without realizing it. Their provided links have probably had errors since they updated months ago.

Fire Tablet Software Updates - Amazon Customer Service

Fire tablet devices automatically download software updates when connected to the internet. These free software updates include general improvements and performance enhancements.

www.amazon.com

Thanks to k4y0z, ggow, and all others for their work. Attached some vids showing Amazon's error and how it will look like loading Lineage/GApps on first boot.
[Fire HD 8 and HD 10 Original Android Development] hd10fireroot:
Just wanted to contribute my experience rooting my Fire HD 10 on suez 5.7.1.0. I was up for hours trying everything. I tried the "20165195" exploit via GitHub link, didn't work. I tried the guide on Post 1 of Page 1 in this thread, didn't work. I tried bricking it through recovery mode, didn't work. I was even stupid enough to try Kingoroot, which did not work.

What did work: Look at Post 2 on Page 1 of this thread first. Specifically the guide from @retyre. Clicked on it, saw the picture of the pin to short. This picture, oddly, is one of the only snapshots I can find on the internet that detail what pin to short.

Next, research how to open your device. There's videos on Youtube, but I took a plastic pry tool and gently opened the tablet like an old smartphone. It opened fine. I had some micro screwdrivers with me, specifically my T5 hex head micro bit for dealing with the handful of screws on the motherboard. I disconnected the front camera ribbon (gently) by carefully lifting the release mechanism, and also carefully disconnected the screen ribbon. I left the battery connected after I saw how feeble and dinky the plastic connector was that they chose to connect the battery and the motherboard. Once these ribbons are out and the screws are up, I carefully unlatched the thin speaker wires from their plastic clips to prepare the motherboard to flip over. I then proceeded to flip the motherboard over. I had a piece of wiring (I got my wire from some excess I had laying around from a garage door sensor). I stripped both ends of the cable. I made a tiny little wire hook on one end so it could attach itself to one of the holes in one of the metal plates on the reverse side of the motherboard. I got my script ready with "sudo bootrom-stop.sh". Then I touched the non-hooked end of my wire to the pin on the motherboard and plugged in the microusb. The script began and ran. It said remove short and push enter, so I did just that. It then spend 5 minutes waiting for the data to flash to my device.

It then said reboot to recovery, so I disconnected the USB at this state and put the motherboard back in the proper position, put the ribbons and screws back. I connected the USB again and saw the screen said "hacked recovery mode" in the bottom left hand corner. It was a relief to see this. With this being displayed on the screen and my usb connected, I ran ./fastboot-step.sh now. This installed TWRP and I knew I was golden after that and here I am on Lineage OS now.
[Fire HD 8 and HD 10 Original Android Development] platypoid:
I had some of the same issues you had but I think when you hear the ping , then you flash a different file - I forget now what that was called - maybe fastboot . I also had a boot loop after installing new rom , I unhooked battery , then did rom install again with twrp but this time I did a wipe of system etc that I had neglected to do the first time.
[Fire HD 8 and HD 10 Original Android Development] ShoreHome:
Getting Error: Serial Protocol Mismatch from Line 90 in common.py, running bootrom-step.sh.

Started with and Fire HD 10 - 7 running 5.7.1.0. Sideloaded 5.6.0.0 and it bricked. Stuck in Preloader, no screen. Running Ubuntu on a laptop. Stopped and uninstalled ModemManager. I am prepared to pop the case if needed. Would hate to do that if I get the same error. Anyone seen this? Thanks.
[Fire HD 8 and HD 10 Original Android Development] platypoid:
Opening it up and shorting the pin let mine get the install at the waiting for bootrom stage after it was bricked.
[Fire HD 8 and HD 10 Original Android Development] ed1ks:
Thank you!
[Fire HD 8 and HD 10 Original Android Development] CanKiller:
Firewarenot supported, Im running 5.7.1.0, is downgrade firmware possible?
[Fire HD 8 and HD 10 Original Android Development] A Cool User:
IDK much about this, but see the note on the first page:
[Fire HD 8 and HD 10 Original Android Development] zaooza:
Just tried to follow the instructions from op post on the latest stock with no luck (with temporary brick step). After that successfully rooted the stock with Matrix method, then resumed from step-2.sh. The script flashed everything successfully, however it completely bricked my suez :(
[Fire HD 8 and HD 10 Original Android Development] A Cool User:
Well, you can try opening the back of the tablet and shorting the point to unbrick. Or just have a paperweight...
[Fire HD 8 and HD 10 Original Android Development] zaooza:
Unfortunately it didn't work. Opened the tablet, shorted testpoints, the unbrick script failed with "RuntimeError: bad gpt" error

UPD: bingo! Connected the battery to the unscrewed board with grounded test point and scripts "bootrom-step-minimal.sh" and "fastboot-step.sh" did the job. Was able to flash twrp.
[Fire HD 8 and HD 10 Original Android Development] pberhane:
Help Needed! I have Fire HD 2017 (7th Gen) Suez, I managed to unlock the boot loader and got TWRP working. It allows me to load LineageOS 12.1 fine. Because Lineage OS keeps crushing, I wanted to put the original Fire OS 5.3.6.4 (I believe) but when I sideload the 'update-kindle-40.6.3.6_user_636558520.bin file it hangs on forever at 25% and comes with " adb: failed to read command: No error" I tried different bin files but same thing. Can you please help me put the Fire OS (Factory one) into my Suez Fire HD 10? Thanks
[Fire HD 8 and HD 10 Original Android Development] K-Mac:
I am not new to rooting/flashing but had a few questions. After rereading the instructions, I see that a downgrade would be necessary for me (I am on 5.6.9.0) but I didn't see where/how to do that or the firmware downloads for that.

I am assuming that after that first step, running "sudo ./step-1.sh", my device would be bricked and i need to do the stuff hidden in the hidden content area that ends with "sudo ./fastboot-step.sh"

Is this correct? If so, how do I load the firmware?

Lastly, is it still worth it to do this? with the end goal of going to something like lineage? I see a bunch of discontinued versions, what is the latest version supported on the 7th gen? I again assume based on titles is version 16 because of the suez on it. I have been looking but it there is a lot to try and sort through. Any help is appreciated!
[Fire HD 8 and HD 10 Original Android Development] platypoid:
The first post tells how to do the downgrade. You may have to open it up and short some pads to get it out of brick.
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
Have done this yourself on 5.7.1.0 ? I got a device like that, and can follow the exact instructions, from page #1, LOL. But it might be that I'd have to open it after bricking.

P.S. I checked everything carefully. There is no way to root now other than to open the case, and short the points. The old approach relied on getting root and bricking the preloader, but that does not work anymore. No root, so need to open the case for sure!
[Fire HD 8 and HD 10 Original Android Development] odiad:
Hi. I tried to flash TRWP, was on latest firmware, so I used the step with brick, etc., but when tablet should boot to TWRP it didn't work and now I have bootloops. After start it hangs a bit on amazon logo, and then it starts again.

I am not able to come into bootloader/recovery mode. So e.g. press any volume button and plug in USB cable doesn't work.

Is there any way to be able to flash ? Any instruction how to solve the problems?

Greetings Odiad
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
Tried to short again, and make sure you see the message "now remove short".
[Fire HD 8 and HD 10 Original Android Development] odiad:
Hi bibikalka, I didn't understand what you mean. So you mean after flashing the reboot process?

At the moment I can't try anything because I have that bootloop and I can't flash. Wenn I start on computer in terminal-app any sh-file it doesn't work. The tablet is not recognized by computer. The tablet just starts again and again in that loop
[Fire HD 8 and HD 10 Original Android Development] bibikalka:
So you need to flip the motherboard again, and short that contact, and do bootrom-step from scratch. If you do everything correctly, you'll boot into TWRP, without bootlooping.
[Fire HD 8 and HD 10 Original Android Development] austanss:
I am following the guide by @retyre to unbrick after a downgrade. I am using that guide's ./bootrom.sh because I did not use step-1.sh first, I sideloaded a stock downgrade from stock without unlock or root.

I'm unbricking a "suez" model HD 10 that had 5.7.1.0 installed on it previously. I sideloaded 5.6.3.0 which obviously caused the anti-rollback brick. I followed all the instructions. I am getting a "Serial protocol mismatched" error when I run the script. When I connect the device supposedly holding the short, it shows in LSUSB as preloader. It is not in bootrom mode. I am using a multimeter and it picks up voltage running across the short. I am shorting it by holding the positive end of the meter to the pin and the negative end of the meter to the SD card metal casing. For sanity I saw and made sure: the meter does not pick up that voltage when touching the green filler of the board. Thus I believe that it is actually shorted. It comes up in LSUSB as `Preloader` so its not in bootrom mode. It never shows up in LSUSB as the correct name that would indicate bootrom, nor does it arrive in dmesg. I heard that a USB port that is not USB 2.0 can cause issues with the communication. I have modemmanager disabled and uninstalled. My laptop's USB ports are superspeed USB 3.2. I'm not sure if that makes a definitive difference. Just trying to restore life to my bricked device here.
[Fire HD 8 and HD 10 Original Android Development] lovaduck:
Hi! I would place an old usb 2.0 hub in between, maybe that would downgrade the port enough to work. Worth a try!
[Fire HD 8 and HD 10 Original Android Development] riverstyxxx:
Hitting roadblocks at every attempt. Ubuntu keeps spitting out "Failed critical init step 4, this firmware cannot be supported" until I close the terminal. Firmware is too high but it's not clear how to use bootrom-step-minimal, where to confirm anything, so I just ran it and it says "waiting for bootrom", inserting the tablet into usb does nothing.

I've been all over these forums and have not found one link to a downgraded firmware version.
[Fire HD 8 and HD 10 Original Android Development] nedgepepsi:
Hello. Is the link down? I'm getting a 404.
[Fire HD 8 and HD 10 Original Android Development] riverstyxxx:
I was able to install it, took forever and I wouldn't go through it again if I didn't have to. Not exactly sure how I did it, but one of the error messages that popped up led me to somebody's suggestion to install kingo root, run it twice, then run step 1. It'll brick, open the thing up, solder the points then cut the wire when it says to. Then re-run step 1 and..a few other things. It's kind of a blur, but there'll be a part that says to remove the wire, ignore it then ignore the warning and it'll flash the new bootloader. Hope this helps, I need an aspirin.
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
Still No Go

Did all of your suggestions with new 5.6.3.0 I got directly from Amazon. Rebooted, enabled Developer Options, enabled ADB, shut down tablet, unplugged USB, started HD 10, started Ubuntu session, tested that I had access through ADB, ran step 1, got error, shut everything down again, deleted previous GPT files in amonet, restarted and tested everything, ran step 1 and got same result. The output from this run is attached.
[Fire HD 8 and HD 10 Original Android Development] jeepers007:
I ran this successfully in Virtualbox Unbuntu 18.04, but only after I change the USB controller setting in Virtualbox on the Unbuntu virtual machine to USB3 (I am plugged into a USB3 physical port on my old Dell). May not be your issue, but might help.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
With a corrupted GPT the error from the script should look differently.

Something like

"What's wrong with your GPT".

The error he's getting means, that it doesn't even read out anything from EMMC (corrupted or not).

This is either either because there is still a short at that point, or there is some hardware-damage, which causes it not to be able to access the EMMC.

That's why I am asking if it goes straight into bootrom without shorting anything.

If it goes into preloader, then EMMC can still be accessed.

I assume you mean boot1/idme-region which stores the device-specific information.

That could also be accessed via bootrom, but only if reading out EMMC works generally.

Yeah, you need to run step-2.sh.
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
I left it to 'charge' overnight. Got home, made sure it was powered off and plugged it into the Linux box. Waited a minute or so and ran lsusb. The tablet goes into preloader mode.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
OK, that's good.

lsusb shows this, yes?

Bus 002 Device 014: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

Then try again with the unbrick-scripts.

Make sure the battery is disconnected.

Make sure to remove the short when prompted. (You may wait a moment before pressing Enter)

Make sure modem-manager is disabled

Make sure you run the script as root.

Make sure to try different USB-ports

Try adjusting the TIMEOUT in common.py to a larger value.

It should at least go past "Check GPT"
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
That did it. This time it booted into TWRP !
[Fire HD 8 and HD 10 Original Android Development] DragonFire1024:
Yes that's exactly what lsusb shows. What line is the time out in? I recall a post about that. Forget where it is though.
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
It's in line 11

TIMEOUT = 5

the common.py I sent you earlier actually already increased it from 5 to 10, but you can try increasing it even further.
[Fire HD 8 and HD 10 Original Android Development] slicer2k:
Do i need a permanent root or just the temporarily one???
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
Root Access

After completing this method, I've noticed that some sideload packages install with root access and others that use it do not. How do I ensure that app packages that need root access are installed with it ?

Do I still need to install SuperSU to get root access through a Command Window in ADB shell ? I've also noticed that I can't get [MENTION=8132642]diplomatic[/MENTION]'s temporary root method to work any more. Is this normal or do I need to go through your process again ?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
I'm not sure I understand your question.

Did you install Magisk and MagiskManager APK?

No, SuperSU and Magisk are mutually exclusive.

mtk-su should work just like before, but with Magisk you don't need it.
[Fire HD 8 and HD 10 Original Android Development] OldFeller:
Thank you for all the work you did developing this method and for all the help you so willingly provide. :good::good::good:
[Fire HD 8 and HD 10 Original Android Development] runderekrun:
Thanks [MENTION=7104332]k4y0z[/MENTION] . Was super easy to get my tablet rooted.

What is some stuff I can do with root now? I got the amazon launcher disabled and use Nova as my launcher. I converted it to a system app for google now functionality. I used the "non root" method to kill the ads but they keep coming back. Is there a root way to handle them? I would love to disable the lock screen but of course Amazon doesn't have an option for this because they have ads on theirs.
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
There's an AIO tool you can download that does a lot of stuff for you, though if I were you I'd not debloat anything with it, 'cause that may cause some issues for you. I'd recommend just using it for the ads-killing option.

[MENTION=7104332]k4y0z[/MENTION], what's the latest FireOS update I can flash to stock before doing this? This one? "update-kindle-40.6.2.6_user_626533320.bin"?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Yes, that's the current Firmware (5.6.3.0 mislabeled as 5.3.6.4)

https://www.amazon.com/gp/help/customer/display.html?nodeId=202194760
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
Alright, how do I flash this? Copy to my device, boot into recovery, and flash it?
[Fire HD 8 and HD 10 Original Android Development] k4y0z:
Just sideload from recovery...
[Fire HD 8 and HD 10 Original Android Development] SingleMalt69:
Just to help out with a few more details:

1. From the tablet, in TWRP tap on Advanced then tap on ADB Sideload

2. From a shell on your computer execute "adb sideload update-kindle-40.6.2.6_user_626533320.bin"
[Fire HD 8 and HD 10 Original Android Development] ffstudios:
Hey guys, need some help here. I have TWRP and root and everything and it was running great. I pushed that modified framework-res.apk to enable the Advanced Power Menu and now my Kindle is all borked. The keyboard no longer launches. I can not install or uninstall APKs from the file system. I cannot launch abdb Insecure whatsoever in order to undo the framework-res.apk mod

I enter TWRP on the Kindle, I open ADB, I can see the Kindle in recovery mode from adb devices, I run "fastboot flash recovery bin/recovery.img" and then it just says "Waiting For Device". Am I missing something here? What the heck do I have to do to get rid of all this garbage and start from square one again? I evidently should not flash stock images from TWRP, I know that from the OP, but I'm really confused as to what I need to do now because a full factory reset does not undo the framework-res.apk mod.

EDIT: Sorry, I just read the last page. I can sideload the stock Fire OS image from ADB in TWRP safely?
[Fire HD 8 and HD 10 Original Android Development] GuyInDogSuit:
So I already need to have TWRP on there? I thought I needed to update BEFORE unlocking the tablet.
[iPAQ rw6828, XDA Atom Software Upgrading] nicale19:
hi to all!

i ve flashed my atom life to pedviet rom..but now i ve noticed that my atom has a little problem to speaker, so i would like to send it back

where can i found original mwg rom and hpw replace it??

thank u!
[iPAQ rw6828, XDA Atom Software Upgrading] devalian:
MWG website should have it.. i get my O2 Atom Life WM6 rom at MWG website..
[iPAQ rw6828, XDA Atom Software Upgrading] ednap_ina:
is it ok to replace O2 Atom Life ROM with MWG ROM? is there any conflict? such as radio, wifii, or other application? thanks for sharing:confused::confused:
[Greenify] heynando:
Even touches on the screen don't get registered in that period, songs stop playing, videos stutter, typing freezes, the entire system halts for 3 seconds whenever Greenify hibernates any application. Is this normal?

Android 8.0, stock ROM Moto z2 play, no Xposed, Magisk only
[Greenify] 550D:
Nope. That's not normal...

sent using taptalk
[Greenify] DB126:
Definitely not normal; no one would put up with that crap. Something specific to your system/config.
[Greenify] heynando:
Could you help me diagnose the issue by analysing this logcat? This particular recorded session depicts multiple system halts, It freezes every time an app gets updated, since several of them are updated one by one, the system also halts one by one.

My hope is that it's something relatively simple to fix or maybe just a bad combo of apps conflicting with each other, instead of having to do a complete wipe of data partition.
[Greenify] ChingghisKhan:
I am having this problem when MacroDroid is enabled.
[MTCD Android Head Units General] eiadah:
I have an Android rockchip px3 screen. I do not work and I do not accept to enter the recovery mode only when I press the WST button and I can not install any system:(:crying:
[Nokia 8 Questions & Answers] axtroz:
Hi,

I upgraded my Nokia 8 to Pie a while ago and now I had to reinstall windows.

Now when I connect the phone to my computer I get the CD drive that should contain the driver but when I try to open it I get a "Please insert a disk into CD-ROM drive F:".

So... how to get the driver from the phone in this case? I tried uninstalling and reinstalling the CD device, tried reassigning a drive letter to no avail. This was working just fine prior the Pie update. Any help much appreciated.

Thanks!
[Nokia 8 Questions & Answers] Hem981:
What i tried was remove all usb root hubs from device manager on windows and then scan for hardware changes. Everything was back to normal. But since you just reinstalled windows, i don't know if it'll work. But no harm in trying, right?

Also, try searching for drivers from windows update. Check device manager to try and update the mtp drivers manually from windows update.

Or you could just connect it to some windows 7 pc, copy all drivers and install it in your windows 10 one.
[Nokia 8 Questions & Answers] axtroz:
Whatever I did, it showed up only as an empty drive. I ended up crawling the filesystem via `adb` and pulled the iso from the phone. It's still there, it just doesn't mount the contents. So I extracted it and put it in Gdrive for future reference. Whoever is interested, can find it here.
[Nokia 8 Questions & Answers] Hem981:
Try one more thing: enable developer options by clicking on the build no in about phone a number of times. Go to developer options>default usb configuration. Try meddling with those settings.
[Samsung Galaxy S7 Questions and Answers] Flyingpiglet:
I flashed the lastest "THE GALAXY PROJECT" ROM and ever since I can't use TWRP anymore since my storage is "0MB".

It's not asking for a decryption password when I boot to recovery and when I try to decrypt in TWRP Terminal it says "Failed to decrypt data".

I've searched everywhere but can't find a answer to this problem.

Can anyone help me out?
[Samsung Galaxy S7 Questions and Answers] cooltt:
Yeah they decided to encrypt the storage as default, you need TWRP with quota support so download this guys TWRP and flash it, it works great. https://xdaforums.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770/page137 Not the first post, the second one Lucas Tech.

the .img file can be flashed with TWRP on your device or the .tar can be flashed with Odin.