Database Users

Multi-platform 1-Click bootloader unlock for *ANY* 3rd Gen HDX (with VirtualBox)

UPDATE 2022-03-05: Network Access Snafu
During the last week or so, a server-side issue caused 1-Click to fail
either silently or with a "1-Click needs network access!" message
on startup. If you experienced the above, please try again!
Changed:
VirtualBox 6.1.x support (tested with 6.1.16)
works fine on Linux with Firefox and USB2 ports
tends to be flaky on MacOS with Safari; PLEASE use Firefox or Chrome!!
may need to connect via a USB2 hub or try different ports and cables
More accurate state assessment (i.e. rooted/unlocked/etc)
More aggressive planning logic
always look for ROM/GAPPS/SU in internal storage
may end up offering choices that make very little sense
Assorted fixes and improvements
hopefully fewer new bugs were introduced than old ones fixed
Unchanged:
No prerequisites on the device side
no root needed
full stock is OK
stuck in fastboot is fine
heck, it even works with _some_ soft-bricks
Does NOT work on Windows
1-Click is a virtual machine and a script that starts the VM in VirtualBox.
Unfortunately, VirtualBox on Windows fails to pass certain USB devices
including the HDX in bulk mode from Windows to the VM.
Network access required to grab the right aboot + TWRP for your device
Optional TWRP magic to auto-install ROM.zip, GAPPS.zip, and SU.zip from internal storage
PM me for a personal link and please state your regular HOST operating system.
Gotchas:
Requests without HOST OS information will be ignored.
Naturally, the same applies to requests with a Windows HOST OS.
Running 1-Click inside another VM is almost guaranteed NOT to work.
Link requests should be sent at the earliest 2 weeks after join date.
Freshly joined members are encouraged to spend some time
familiarizing themselves with the details of working with this device
by studying the relevant threads in this forum.
If you send a request be sure to monitor your account for replies!
A response should arrive within a week (or so), but the link is only valid for 2 days.
Don't miss your chance!

draxie said:
Title says it all..
(Well, almost: you need a vulnerable bootloader,
i.e. 3.2.3.2 or earlier, that foolishly accepts forged
signatures...)
Download and unpack the attached zip file.
Run the right '1-Click' script for your platform
(that is, '1-Click.bat' for Windows users,
and '1-Click' on OS X and Linux).
Simply clicking on the script works in Windows and OS X.
On these more "one-size fits all" operating systems, the scripts
-modulo network connectivity- will also download and install
VirtualBox, if it's not already installed.
Linux users need either VirtualBox or QEMU installed.
There are simply too many variants to automate this
for all the different distros. Sorry...
On some Linux variants, instead of launching the script
the click action opens the script in editor... YMMV
This may, in fact, be very useful, since on some of the same
Linux variants the script has to be run as root to avoid
automounters taking precedence; in which case, you're
well advised to make sure you read and understand what
the script is doing before you run it as root, because I take no
-that is: ZERO- responsibility for any damage that may result.
I personally tested the scripts on
Linux: Mint 17.2 (both 32-bit and 64-bit versions)
OS X: Mountain Lion, Yosemite, El Capitan
Windows: 7, 8.1, 10
The 1-Click VM runs a minimal Linux system with adb/fastboot
and a pure C "cuber" using OpenSSL's BigNum library.
No need to download adb/fastboot, python, or worry about
drivers on your host system.
Good luck!
Click to expand...
Click to collapse
Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).

Any takers?
Davey126 said:
Very cool! Will be interesting to try this out (have to wait for a someone with an eligible device that is willing to give it a whirl).
Click to expand...
Click to collapse
BTW, this works with already unlocked devices also,
if anyone is willing to do some independent testing.
This is how I tested also... should be completely harmless.

Ran this against my HDX 7
Puttytel reported an 'error reading from serial device', but after it had initiated device shutdown so just a gui annoyance (I'm on windows, so commonplace.) It seemed to work, but I haven't verified yet..
> fastboot -i 0x1949 oem device-info
kindle fire [fastboot]
oem device-info...Device tampered: false
Ok.
I'll do some more testing later.

codeshane said:
Puttytel reported an 'error reading from serial device', but after it had initiated device shutdown so just a gui annoyance (I'm on windows, so commonplace.) It seemed to work, but I haven't verified yet..
> fastboot -i 0x1949 oem device-info
kindle fire [fastboot]
oem device-info...Device tampered: false
Ok.
I'll do some more testing later.
Click to expand...
Click to collapse
Thanks for reporting back!
The puttytel message is normal: the serial port it's talking to
disappears when the VM shuts down.
If/when you test again do check your Kindle after the fastboot prompt
appears but **before** you hit [Enter] in the puttytel window!
You should see "Unlock code correct" in green,
if the unlock worked...
Other than that, since you seem to have fastboot working, you can use
Code:
fastboot -i 0x1949 oem idme ?
to see if your device is unlocked (see here for a list of commands).

draxie said:
Other than that, since you seem to have fastboot working, you can use
Code:
fastboot -i 0x1949 oem idme ?
to see if your device is unlocked (see here for a list of commands).
Click to expand...
Click to collapse
C:\>fastboot -i 0x1949 oem idme ?
...
(bootloader) board_id: 0c0400
(bootloader) serial: xxxxxxxxxxxxxxxx
(bootloader) mac_addr: 00BB3Axxxxxx
(bootloader) bt_mac_addr: 00BB3Axxxxxx
(bootloader) productid: 0
(bootloader) productid2: 0
(bootloader) bootmode: 1
(bootloader) postmode: 0
(bootloader) bootcount: 203
(bootloader) panelcal:
(bootloader) time_offset: 0
(bootloader) signature:
(bootloader) idme done
OKAY [ 0.359s]
finished. total time: 0.361s
I feel rusty, haven't done any android dev in two years.. never tried to unlock a bootloader beyond 'fastboot oem unlock' before, but I really don't want them re-locking this one (they've taken root from me twice before.) I verified I have root still, but some apps are reporting that I don't. lame. more tests when I have some time, thanks for your time and effort!
Update:
Successfully flashed twrp recovery image recovery-twrp-recovery-2-8-1-0-apollo-t2991155
Happily considering ROMs to blow-away Amazon's 'os' with

codeshane said:
C:\>fastboot -i 0x1949 oem idme ?
...
(bootloader) board_id: 0c0400
(bootloader) serial: xxxxxxxxxxxxxxxx
(bootloader) mac_addr: 00BB3Axxxxxx
(bootloader) bt_mac_addr: 00BB3Axxxxxx
(bootloader) productid: 0
(bootloader) productid2: 0
(bootloader) bootmode: 1
(bootloader) postmode: 0
(bootloader) bootcount: 203
(bootloader) panelcal:
(bootloader) time_offset: 0
(bootloader) signature:
(bootloader) idme done
OKAY [ 0.359s]
finished. total time: 0.361s
Click to expand...
Click to collapse
codeshane said:
I feel rusty, haven't done any android dev in two years.. never tried to unlock a bootloader beyond 'fastboot oem unlock' before, but I really don't want them re-locking this one (they've taken root from me twice before.) I verified I have root still, but some apps are reporting that I don't. lame. more tests when I have some time, thanks for your time and effort!
Update:
Successfully flashed twrp recovery image recovery-twrp-recovery-2-8-1-0-apollo-t2991155
Happily considering ROMs to blow-away Amazon's 'os' with
Click to expand...
Click to collapse
Thoughts:
- take a backup of your current rom before flashing; leave it on the device until the new rom is stable (simplifies recovery)
- if you get a response from 'fastboot -i 0x1949 oem idme' your bootloader is unlocked!
- once you overwrite FireOS there is no chance of loosing root due to Amazon actions. OTA capability is baked into FireOS - not the device firmware.
- If you like AOSP go with Nexus v4. Any of the other HDX roms (CM11, CM12, SlimLP) are also fine choices. Each has a few minor quirks but no major 'gotchas'.

Sorry for the delay, wrote back a while ago but I guess it didn't post (cellular, pfft.)
Went for the Nexus v4 rom, which is running great so far. Thanks again for such a brilliantly simple unlock utility!

I have a few questions.
1. How can I tell I have a vulnerable bootloader?
I've been on Safestrap 3.7 and one of the early 4.2.2 Android Roms since the December after the HDX's release. My stock slot Fire OS hasn't been updated either. So am I on a vulnerable bootloader? How do I check?
2. Where do I start with this?
Is there anything I need to remove? Do I need to be on the stock Fire OS slot? Or do I simply run it as you stated.
3. After the unlock where do I go from there?
I'm so out of the loop I don't know what's the ideal stable rom to use .
Thanks, I'd appreciate any help .

zXiC said:
I have a few questions.
1. How can I tell I have a vulnerable bootloader?
I've been on Safestrap 3.7 and one of the early 4.2.2 Android Roms since the December after the HDX's release. My stock slot Fire OS hasn't been updated either. So am I on a vulnerable bootloader? How do I check?
2. Where do I start with this?
Is there anything I need to remove? Do I need to be on the stock Fire OS slot? Or do I simply run it as you stated.
3. After the unlock where do I go from there?
I'm so out of the loop I don't know what's the ideal stable rom to use .
Thanks, I'd appreciate any help .
Click to expand...
Click to collapse
Check your FireOS version in the stock slot. If 3.2.6 or below you can unlock the bootloader. The rollback procedure depends on the current version of FireOS. Report back and we'll go from there.

Just a little add-on to @Davey126's info:
3.2.3.2 and lower can unlock, 3.2.4 - 3.2.6 must downgrade first.
Once on 3.2.8 or higher you can NOT downgrade anymore due to rollback protection by Amazon, attempting would brick the device! So if you're on 3.2.6 or lower do NOT update!

Cl4ncy said:
Just a little add-on to @Davey126's info:
3.2.3.2 and lower can unlock, 3.2.4 - 3.2.6 must downgrade first.
Once on 3.2.8 or higher you can NOT downgrade anymore due to rollback protection by Amazon, attempting would brick the device! So if you're on 3.2.6 or lower do NOT update!
Click to expand...
Click to collapse
Just a quick comment: since there are no known adverse affects of a failed unlock,
you could just try unlocking to see if your bootloader is 3.2.3.2 or earlier..
If the unlock fails, you could move on to figuring out if downgrading is an option.

draxie said:
Just a quick comment: since there are no known adverse affects of a failed unlock,
you could just try unlocking to see if your bootloader is 3.2.3.2 or earlier..
If the unlock fails, you could move on to figuring out if downgrading is an option.
Click to expand...
Click to collapse
True!! But for for the 'typical' Kindle user (I know...sterotypes) working with a Windows host the effort to unlock far exceeds that of simply checking the FireOS version if still installed.

Hi, can any help why it keep telling me my kindle device is not connected? i using windowX86 and sure open the adb on kindle. thank you!

More accuracy please! (-;
fuxkamazon said:
Hi, can any help why it keep telling me my kindle device is not connected? i using windowX86 and sure open the adb on kindle. thank you!
Click to expand...
Click to collapse
Hi there,
I'm convinced that I can help you,
but I would need a more accurate
trouble report...
In the meantime, I'll try to give some background
and possible causes and remedies to what I think
might be your problem.
1-Click relies on VirtualBox's USB filter mechanism
to pass through any USB device with Amazon' s
vendorId (0x1949) to the 1-Click VM.
This may not always work.
The most common reasons are as follows:
No device is connected.
I presume this does *not* apply...
The device is in use.
This could happen easily, e.g. if you were browsing files on your Kindle.
Apart from possible privilege issues (see next bullet),
these kind of issues are usually solved by simply disconnecting
and reconnecting your device while the VM is running.
This is the most common/likely case, which 1-Click also tells you about..
Have you tried this? (Your report is not very clear on this.)
Possible lack of privilege.
I've only encountered this on Linux (as described in the first post),
but, then again, on all the Windows boxes I tested on, my user is
in the Administrators group; so, this may still apply there.
BTW, I'm guessing that you are on some 32-bit version of Windows,
although I must admit that the "windowX86" moniker in your post
doesn' t make this crystal clear.
Global USB filter rules in VirtualBox may override the rule used by 1-Click.
This only applies if VirtualBox had already been installed
and configured with global USB filter rules before 1-Click.
There may be other reasons, but the above should cover
the most obvious/common cases.

ty for you quick reply. i dun know what info i can provide but ill try. im now using this bl unlock on safestrap3.75 stock rom without opening or browsing any documents. yet, it show the samething i did last couple times. Here is,
Welcome to 1-Click
mount: proc mounted on /proc.
mount: sys mounted on /sys.
mount: dev mounted on /dev.
* daemon not run[ 1.269523] random: adb urandom read with 6 bits of entropy available
ning. starting it now on port 5037 *
* daemon started successfully *
Please make sure ADB is enabled on your Kindle
and connect the device to your computer
In case you don't already know, ADB is enabled by turning on the
'Settings/Device[ Options]/Developer Options/Enable ADB' option.
If 'Developer Options' is missing in 'Settings/Device[ Options]',
tapping 'Settings/Device[ Options]/Serial Number' seven times
will enable it..
Hit [Enter] to continue
No device appears to be connected..
You may need to disconnect and reconnect your device
Hit [Enter] to continue[ 27.214445] random: nonblocking pool is initialized
so hope you can find whats going wrong. ty!
draxie said:
Hi there,
I'm convinced that I can help you,
but I would need a more accurate
trouble report...
In the meantime, I'll try to give some background
and possible causes and remedies to what I think
might be your problem.
1-Click relies on VirtualBox's USB filter mechanism
to pass through any USB device with Amazon' s
vendorId (0x1949) to the 1-Click VM.
This may not always work.
The most common reasons are as follows:
No device is connected.
I presume this does *not* apply...
The device is in use.
This could happen easily, e.g. if you were browsing files on your Kindle.
Apart from possible privilege issues (see next bullet),
these kind of issues are usually solved by simply disconnecting
and reconnecting your device while the VM is running.
This is the most common/likely case, which 1-Click also tells you about..
Have you tried this? (Your report is not very clear on this.)
Possible lack of privilege.
I've only encountered this on Linux (as described in the first post),
but, then again, on all the Windows boxes I tested on, my user is
in the Administrators group; so, this may still apply there.
BTW, I'm guessing that you are on some 32-bit version of Windows,
although I must admit that the "windowX86" moniker in your post
doesn' t make this crystal clear.
Global USB filter rules in VirtualBox may override the rule used by 1-Click.
This only applies if VirtualBox had already been installed
and configured with global USB filter rules before 1-Click.
There may be other reasons, but the above should cover
the most obvious/common cases.
Click to expand...
Click to collapse

fuxkamazon said:
ty for you quick reply. i dun know what info i can provide but ill try. im now using this bl unlock on safestrap3.75 stock rom without opening or browsing any documents. yet, it show the samething i did last couple times. Here is,
Welcome to 1-Click
mount: proc mounted on /proc.
mount: sys mounted on /sys.
mount: dev mounted on /dev.
* daemon not run[ 1.269523] random: adb urandom read with 6 bits of entropy available
ning. starting it now on port 5037 *
* daemon started successfully *
Please make sure ADB is enabled on your Kindle
and connect the device to your computer
In case you don't already know, ADB is enabled by turning on the
'Settings/Device[ Options]/Developer Options/Enable ADB' option.
If 'Developer Options' is missing in 'Settings/Device[ Options]',
tapping 'Settings/Device[ Options]/Serial Number' seven times
will enable it..
Hit [Enter] to continue
No device appears to be connected..
You may need to disconnect and reconnect your device
Hit [Enter] to continue[ 27.214445] random: nonblocking pool is initialized
so hope you can find whats going wrong. ty!
Click to expand...
Click to collapse
This looks fine. The question is what you did next..
Have you tried disconnecting and reconnecting your Kindle
as the message above suggests?
(BTW, since this was the only direct question in my previous post,
I sort of expected you to answer that, but now you get another chance. )

just tried this. i had rooted my kindle when root first came out without safestrap as i didnt like all the restrictions of safestrap. i installed twrp much later and then cm 11 for twrp without an unlocked BL. tried this one click and had to disconnect and reconnect the tablet at one point, no biggie. at another it sat there with no instructions till i hit enter, but it did complete and said it was successful. so ty very much. at some point soon ill try a rom that requires an unlocked BL and see that my BL is really unlocked. great program if it really did work. will donate soon

I'm using Thor with stock 13.3.2.4 block OTA update and safetrap 3.75. So can i use this tool to unlock BL right away or i've downgraded 13.1.0.0 then unlock?

nickytun said:
I'm using Thor with stock 13.3.2.4 block OTA update and safetrap 3.75. So can i use this tool to unlock BL right away or i've downgraded 13.1.0.0 then unlock?
Click to expand...
Click to collapse
You can NOT unlock versions above 3.2.3.2, so you must downgrade first.
Good News is you can downgrade to 3.1.0 using the downgrade images provided by @ggow. Check page 2 here (page 1 is about 3.2.5/3.2.6 users who can NOT use these images!). Then flash TWRP, update the bootloader to 3.2.3.2, unlock the bootloader, then use ROM of your choice.
Read the info, ask if you've any questions before you brick your HDX! Note that factory reset in Safestrap means the standard wipe only (wipes data, cache & dalvik only)! Do NOT go into advanced wipe, do NOT wipe System!
Be sure to make backups of your current system (even if you don't need it anymore), remove the secondary slot(s) in Safestrap to get back the storage used by it (if you created any), and after installation of TWRP create a backup of your Fire OS before you flash any custom ROM.

[GUIDE/TUTORIAL/HOWTO] HTC One M7 Stock to Android 11 / LineageOS 18.1

[GUIDE/TUTORIAL/HOWTO] HTC One M7 Stock to Android 11 / LineageOS 18.1
[GUIDE/TUTORIAL/HOWTO] HTC One M7 any version (m7, m7ul, m7spr, m7vzw) stock to Android 11 R / LineageOS 18.1
This detailed step-by-step guide helps you transform your HTC One M7 (any version) to a powerful one with Android 11.
Make sure you have the One M7 model, in Android, go to Settings > About phone and check the model.
CHANGELOG
v8. Upgrade to Android 11, improve readability, update pack
v7. Updated pack with MagiskManager 8.0.7 and Magisk 21.4
v6. Infos in case of Simlock
v5. Moved to Android 10 thanks to @tarkzim, updated pack with Magisk 20.4
v4. Moving to Android 9. I was wrong in v3 ;- Thx @tarkzim), good for all M7 versions
v3. Reverted back to Android 7.1. No stable ROM for Android 8 or 9 (and will never be)
v2. Tutorial updated for Android 8.1 Oreo, updated pack with TWRP 3.3.1-0
v1. Initial release
1) DOWNLOAD
- djibe HTC One M7 pack (44.3 Mo) v2 : http://bit.ly/djibe-onem7-v1
(includes HTC drivers, recovery TWRP 3.6.1_9-0 for all m7 by Xeno1, Magisk Root 23 adb & fastboot.exe).
Unzip the djibe folder from the zip on root folder of C: drive.
- ROM Unofficial Lineage OS 18.1 for M7: https://forum.xda-developers.com/t/rom-11-0-unofficial-m7-all-lineageos-18-1-stable.4454219/
Download latest build for M7 here: https://androidfilehost.com/?w=files&flid=334598&sort_by=date&sort_dir=DESC
+ BitGApps ARM 11 v1.4+: https://github.com/BiTGApps/BiTGApps-Release/releases/
+ Charge phone to 100 %
WARNING. This tutorial uses Microsoft Windows.
WARNING. Warranty is now void.
WARNING. Read carefully the sentences starting with ###.
2) BACKUP DATA AND INSTALL DRIVERS
Disable Antivirus.
Install drivers from my pack:
right click on HTCDriver.exe -> click on Run as administrator and continue the setup.
Then install HTC_BMP_USB_Driver_x64.msi (or *_x86 if you have a 32bits Windows edition).
### Install doesn't work ? Try these drivers for Win10 : https://htcusbdriver.com/download/htc-usb-driver-v4-02-0-001
Now go to my folder flash, and right click the adb 15seconds installer > Run as administrator.
During install, every time the command asks you a confirmation, enter Y and confirm with Enter.
Connect HTC One (while phone on) to PC, let drivers install.
In Windows explorer, HTC One should be available.
### If not make sure phone connection is in File transfer mode (see Android notifications).
Collect all personal photos, videos, etc ... and copy these on PC.
Use an app like Backupyourmobile to backup texts, contacts, etc.
Check that backup is located on microSD card.
Then copy the backup on your PC.
Disconnect phone.
### If your phone is Simlocked/carrier locked/Network locked, don't go further.
Visit official website of your network carrier (or call their support) to retrieve your desimlock code.
Ask them for details on how to remove simlock.
How do I know my phone is simlocked ? When you insert a SIM card from another operator, network is not accessible.
Only a stock ROM can remove simlock.
To go back from custom ROM to stock in 1 zipfile flash, follow this tutorial: https://tcg96.github.io/m7gurureset
3) UNLOCK BOOTLOADER
In Android, go to Settings > About > Software information > More.
Tap 7 times on Build number. It unlocks Developer options.
Go back to the About menu, you can see the new Developer options menu.
Tap on it, accept the warning.
Toggle on the USB debugging option.
Connect phone, a message appears on phone : Allow USB debugging?
check Always allow and confirm by tapping on OK.
Now, open a Windows command on my "flash" folder (hold Shift + right click on folder -> Open a windows command here).
### Then navigate to my flash folder (if it is on desktop) with this command :
Code:
cd /d C:\djibe\flash
Enter command :
Code:
adb devices
, confirm by pressing Enter.
Command returns :
Code:
List of devices attached
HT35****** device
### If no device is found, uninstall and reinstall properly the drivers while antivirus is off.
### Or start fresh on another PC.
Now type :
Code:
adb reboot bootloader
Authorize ADB commands on phone.
Phone restarts in Fastboot mode. Wait till phone screen is blank in fastboot mode.
Type :
Code:
fastboot devices
Command returns :
Code:
HT35**** fastboot
Type :
Code:
fastboot oem get_identifier_token
, confirm by pressing Enter.
Command returns multiple lines.
Select with your mouse all the lines from
Code:
<<<< Identifier Token Start >>>>
(included)
to the line
Code:
<<<<< Identifier token end >>>>>
(included).
Now on keyboard copy (Ctrl + C combo), then open Notepad.
In Notepad, paste those lines (Ctrl + V combo).
Now manually remove all the (bootloader) strings from each line.
Your notepad should now look like this :
<<<< Identifier Token Start >>>>
37A5DBF4FE5F0D9F4425E54AA91AFDBF
2A20E9C67C3BB4FAE60263F76BDEC6AC
847BF9FFB11DAEA4AB88AC8710435449
9BC12E93DF4C54FFE3D064C4C810C49A
2CDAF2E0CD3A164FED4A568CB0FD2AC6
C01AA991733D949C00987062D691DE91
8AA1C97CEBC3ACE83FECE75A1D03CE72
62414C7DC36A73AFCBF433E1EBE2EDC7
E272F73309632D3EF8C86E472B65E8EF
37E46B52FE3F94FC69D1854CA3DE6F48
C3E10001B233A70B1EAF35134F51FCC6
353E0CC98534E6E60A241A7063D0BE2F
A5B752E75C1C47E6F739BDBE67D024DA
3292A14278247557632639802722A86C
E61424F7666AE085AA9905096FEED1AD
5ECBBD867544E95ABDDA277690B8CB55
<<<<< Identifier Token End >>>>>
Now visit this website : https://www.htcdev.com/bootloader/
Register on the site. Confirm registration with your email.
In the select menu, chose HTC One (M7), click Begin unlock Bootloader button.
Agree to legal terms.
Next page, go to the bottom and click continue to step 5.
In the bottom of this page, in the lower textarea "My Device Identifier Token",
copy and paste the multiple lines you just edited (my example is just above).
Click Submit.
HTC tells you : Token Submitted Successfully.
Open your mailbox (associated to your HTC account).
Copy the Unlock_code.bin file attached to email in my "flash" folder you unzipped.
In Windows command, type :
Code:
fastboot flash unlocktoken Unlock_code.bin
, confirm with Enter.
Command should return :
Code:
unlock token check successfully
Back to phone, press Volume+ to select "Yes, unlock bootloader", then Power button to confirm flash.
Now wait while phone is going to Factory reset.
Don't let Android restart by holding both Power + Volume- to enter bootloader immediately.
FASTBOOT menu is overlined in red.
4) FLASH TWRP RECOVERY
Using the same Windows command prompt, enter :
Code:
fastboot devices
to make sure phone is still available.
Then
Code:
fastboot flash recovery twrp-3.6.1_9-0-m7univ.img
Command returns :
Code:
finished. total time: x.xxxxs
##€ If it fails, tries with a Windows Powershell shell.
Now on phone, press Volume- to select Bootloader, confirm with Power button.
You are back to the booloader screen (UNLOCKED is written on top line), press Volume- to navigate to RECOVERY, and confirm with Power button.
Phone reboots in TWRP recovery.
5) WIPE PARTITIONS
In TWRP, check Never show this screen and Swipe to Allow Modifications.
You land on TWRP Home screen.
Go to Wipe > Advanced wipe.
Select Dalvik, Cache, System, Data, Internal Storage then Swipe to Wipe, go back to Wipe menu.
6) FLASH ROM, GAPPS AND ROOT (OPTIONNAL)
We first have to get our zips on the phone.
Still on TWRP Home screen, tap on Mount > deselect all partitions except Data, then connect phone to PC.
In Windows Explorer, you can see MTP Device, copy the zips of ROM, GApps, Magisk + Magisk Manager right in the Internal Storage folder.
Tap on Disable MTP once copy is finished.
Then back to Home screen, tap on Install > choose lineage*.zip,
(if you don't see the files, tap on Select Storage and make sure Micro SDCard is active)
then Add more Zips -> Magisk*.zip,
then Add more Zips -> bitgapps*.zip,
then Swipe to confirm Flash.
Wait for operation to end (can be long).
When completed successfully, tap on Reboot.
Tap on Do not install when TWRP asks for the app install.
Wait during long first boot.
Setup Android.
7) You can use Backupyourmobile to restore data,
use GPS Status & Toolbox app to enhance GPS fix.
That's it.
Enjoy,
djibe
THANKS --------------
Teams of : TWRP, LineageOS team, tarkzim, zsoerenm, alray, ., Flyhalf205, icxj1, R1ghtC, gimmeitorilltell, All M7/MSM8960 contributors.

Just my 2 cents
Just my 2 cents if it can help
djibe89 said:
- a microSD card (FAT32 format). Copy the zips of ROM, GApps, addonsu and deviceid*.apk (both in my pack) on the root folder of microSD, then insert it in phone.
Click to expand...
Click to collapse
The M7 is not equipped with a mircoSD card slot, only a virtual /sdcard (symlink to /data/media/0) ... So they'll either have to adb sideload or adb push the files to internal memory which is pointless at this stage since it will be wiped during bootloader unlock. Or drag n drop the files using mtp from twrp once it's installed on the phone.
3 ) UNLOCK BOOTLOADER
[...]
Now wait while phone is going to Factory reset.
Setup Android again on next boot.
4 ) FLASH RECOVERY
Now re-enable USB debugging in Android.
Using the same Windows command prompt, type
Code:
adb reboot bootloader
again.
Click to expand...
Click to collapse
You could save a lot of time just force rebooting to bootloader (power + vol down) right after BL unlock/factory reset are completed so you don't have to setup the system you're going to wipe 2 steps later. USB debug anyway isn't required to fastboot flash recovery so it's not like booting back in system is mandatory before flashing recovery.
:good:

@alray : Thank you so much for help.
I'm lazy with baby waking up every night and did some awful copy-paste.
I correct all these right now.
Thanks.

I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.

saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
Because you are a senior member you know where to download everything.
But everyone is not like you.
So I tried to compile a ready-to-go pack for the newcomers, like I did for many devices by know.
This allows noobs to profit from custom ROMs and don't keep it esoteric.
Like you say, many downloads are just hacks, so I tried to bundle lowest size safe files.

saturday_night said:
I would highly recommend to use the official downloads of twrp, HTC drivers, roms and so on, you uploaded these files to your google drive and there is stuff in it nobody will ever need. And nobody knows if those files are in original condition. Strange thats the third time this year someone tries to get users to use their stuff (for a five years old device) there are already a lot of guides out there and several thousand people did it several thousand times without problems. Also you wrote that this would be official lineage but its unofficial, and for that there is already a thread here. The other two threads got deleted by mods because they tried to get users to use files from unknown suspects sources. Use android file host and maybe tell in los thread where those files are stored, whats the source and who made it.
Click to expand...
Click to collapse
For the official LOS ROM, tell LOS to store official builds. As they don't do it anymore, we must rely on personnal builds.
A lot of guides out there ? Made extensive search for cracking this phone, never found a step by step one.
Five year old device ? Still so good once unleashed. Custom ROMs are for these devices isn't it ?

@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .

.:B:. said:
@djibe89 Might be useful to point out in your opening post that the 20180420 build has DT2W enabled, but I'd like feedback from people with a functional battery if it makes their device reboot or not, similar to issues reported in the original kernel thread. I suspect my battery is on its way out. The 20180416 build is completely stock upstream LineageOS, no DT2W.
Thanks for the credit .
Click to expand...
Click to collapse
Thanks for your explanations.

Any trouble following this tutorial guys ? How to enhence it ?

802D device supported?

M.Z.F said:
802D device supported?
Click to expand...
Click to collapse
Hi, no idea, does your model has another model name/code ?

djibe89 said:
Hi, no idea, does your model has another model name/code ?
Click to expand...
Click to collapse
Model name & code like?
PRI Version= 4.22_001
PRL Version = 10012

Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you

I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg

Rafay106 said:
I have tried all the custom roms mentioned above i.e. lineage os , Xenonhd and slim7. But non of them installed. It always shows error either this is not for your device , this device is cdwg or unable to mount. Please give me a link for custom rom for my device that is htc one 802d cdwg
Click to expand...
Click to collapse
All the custom roms mentioned above are NOT for your phone variant.There were almost no development for the 802 branch at the peak of it's popularity and I didn't see anything new for this variant in the past 2 years or so. I wouldn't expect a 7.1 roms for this variant...
Maybe you'll have better luck searching on Asian forums

skovatov said:
Getting this message: Updater process ended with ERROR: 7 Error installing zip file '/sdcard/lineage-14.1-20180520-UNOFFICIAL-m7.zip'
any help would be appreciated, thank you
Click to expand...
Click to collapse
Here you have answer:
https://forum.xda-developers.com/showthread.php?t=2522762
---------- Post added at 05:30 PM ---------- Previous post was at 05:20 PM ----------
Hi.
After installing Android 7.1 Google Pay stop working on my phone. I have torn on NFC communication but terminal don't read my card from app. I don't turn on access to root. Any aidia how to solve this issue?

I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.

Bazooka said:
I have an M7 that I would like to update Android on however the above is a bit over my head. I have seen other sites and video showing this to only take a few minutes and not requiring a PC. Am I missing something? I just don't quite understand the process of it all.
Click to expand...
Click to collapse
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?

alray said:
Flashing without a PC can be done but not recommended. If something goes wrong (and thrust me, it happens pretty often) you'll be stuck with a bootlooping phone.
The guide at post #1 is all you need, what part exactly do you have problem understanding?
Click to expand...
Click to collapse
Thanks for that. I tried to go through it nice and slow making sure I understood each step. I got to where I needed to open a command window on the "flash" folder to which I must have powershell(?) installed as it gave me that option. After inputting 'adb devices' it listed a device but stated it was offline. This is where I am stuck as the steps after this do not work.

drivers win10
Hi, I have a basic ask. Do you know where to get Win 10 drivers? I can't run the installer HTCDriver_4.2.0.001 on my Windows 10 (version 1803).
It gives me the error: The driver installer is not supported for your operating system. Thanks for your help.

Customizing the Fire TV Stick 4K (mantis) - Debloat - Replace launcher and Testing

EDIT (12/08/22): Parts of this guide may be out of date, it hasn't been updated since December 2019.
TL; DR Version in the second post, it's also a short overall summary. Might be best to have a look so you don't get overwhelmed by this first post.
Just thought I would share my experience with the 4K. Just as an FYI this is my first firestick and I've only had it for about a week but I've been playing with it quite a bit.
Personally I'm interested in removing all amazon related products/apps/services etc. With the exception of the store as I would like to get some of my apps through it.
Making it as lean and fast as possible.
Getting as close to AndroidTV as possible without losing any functionally and keeping stability.
I'm primarily interested in Plex and/or Kodi (with no addon apps, just vanilla kodi).
Having root. I like to have the ability to do anything, and I personally found rooting the stick easy so I found no reason not to do it. With that in mind everything I did I had root. I have no idea if any of these steps work without root.
Pre info
I chose to not flash the Prerooted Stock Image due to the comment Sus_i made here. I updated, then rooted.
EDIT (12/08/22): Updating before rooting is no longer recommended.
Step1
Plug it in, run through the setup and let it update. Go to settings -> My Fire TV -> Developer Options and enable ADB Debugging and Apps from Unknown Sources.
Step 2
Root it!
Guide here
This guide/post was helpful also. There is a good video of them opening up the firestick to access the necessary point to short/ground to allow the root script to work. Just be careful with what you use. I just used a small copper wire.
After getting root. Put it back in the case. and plug it in to your tv.
Step 3
Running commands with adb
Get and install adblink, link here
Information on how to use it is on the site. You will need to get the IP address of the firestick. Go to setting -> device -> network -> about
open adblink
click adb shell
type
Code:
reboot recovery
then enter
You'll now be in TWRP
Step 4
Install Magisk
Get the latest stable magisk zip from here
No need for the Magisk Manager apk, that will get installed with the above zip.
Put the zip in the same folder that the adblink.exe is in. (you can find that by clicking adb shell in adb link and then typing exit, then enter. It will show you where you should put the zip file)
Open adblink if you closed it (just leave it open)
click adb shell
which should show the bellow on screen
Code:
mantis:/$
type exit
then paste the following (replace the "Magisk-v20.1.zip" with the correct name of the magisk zip you downloaded)
Code:
adb push Magisk-v20.1.zip /sdcard/
then type
Code:
adb shell
echo "--update_package=/sdcard/Magisk-v20.1.zip" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
It will reboot and install magisk, then reboot to the launcher.
You can now check if you like if magisk is installed correctly and if you have root (you should)
Step 5
Install [Magisk][Module] FireTV 4K Stick Add-Ons
This gets rid of the amazon launcher and does a few other things, including installing xposed framework.
Follow the instructions in that thread. But here's some additional info. Which is just a copy of how we installed magisk.
Download and put the zip in the same folder that the adblink.exe is in.
Open adblink if you closed it (just leave it open)
click adb shell
which should show the bellow on screen
Code:
mantis:/$
type exit
then paste the following (replace the "AFTV-MM-1.9.zip" with the correct name of the AFTV-MM .zip you downloaded)
Code:
adb push AFTV-MM-1.9.zipp /sdcard/
then type
Code:
adb shell
echo "--update_package=/sdcard/AFTV-MM-1.9.zip" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
It will reboot and install AFTV-MM, then reboot to the launcher. It does some things automatically on first boot and may reboot on it's own just let it do it's thing. Some additional commands need to be run via ADB, go to the thread and follow the instructions there: [Magisk][Module] FireTV 4K Stick Add-Ons
Step 6
Remove amazon bloat. *More info below*
Now I've seen a few lists here and there and tried to guess which things to disable on my own until I found these scripts.
Now these scripts weren't made for the 4k (mantis) firestick as you can see from the compatibility list. But I assumed the packages installed would be close so I'm guessing this isn't a bad starting point. But just remember this clearly wasn't meant for this device.
Download the script from here All credit for the original script goes to esc0rtd3w.
and put it in your adblink folder.
Open adblink if you closed it (just leave it open)
click adb shell
which should show the bellow on screen
Code:
mantis:/$
type exit
Code:
adb push bloat-disable.sh /sdcard/
then type
Code:
adb shell
su
cp /sdcard/bloat-disable.sh /data/local/tmp/
chmod 755 /data/local/tmp/bloat-disable.sh
sh /data/local/tmp/bloat-disable.sh
The script will then disable all the bloat. If you would like to enable all the bloat then use this script, download it and follow the same instruction from above. If you just need to enable a single app/service then you can run:
Code:
adb shell
su
pm enable com.amazon.dcp
replacing "com.amazon.dcp" with the app you want to enable.
Step 7
If you want Kodi as the launcher
You can get a modified apk here The thread where this came from originally is here Discussion of an update here
Side load the apk with adblink. Should be self explanatory, click install apk. Once installed open LauncherHijack and select Kodi as the launcher.
Step 8
Setting Kodi (or any other launcher) as the launcher
Install Launcher Hijack (Clone Mod), get the apk here
Follow the instructions here to install it and get it working. By now you should be getting comfortable with abdlink, use it to install the apks and run the adb shell commands.
Other apps to install
Smart Youtube TV (no ads)
OpenVPN install if you want or need it. In my case I need to slightly deviate from the guide. I simply didn't need to create the login.conf file. I Just copied opvn config over and then in settings chose "Certificates" for type and insert the password in "private key password".
That's it for now. I'm curious what other modifications can be done on the 4K (mantis). I'm thinking about/planning on trying a few I've seen around. I think as long as I can get back to TWRP then worse case I should be able to flash the stock ROM to recover. Would be interested to hear what other people may have pulled off.
*Step 6 more info*
This script will remove all packages that esc0rtd3w deemed safe to remove as of Fire OS 5.2.7.2 on the FireStick2. It will leave the amazon launcher enabled and allow use of the amazon app store. The amazon app store can also be disabled but disabling the amazon launcher breaks access to the settings.
My slightly edited version of his script
esc0rtd3w firestick-loader github. All credit for the script goes to him.
List of services/packages that are new for Fire OS 6.2.6.8
If anyone can inform me of the packages/services that can be safely disabled, please let me know and I can include them in the script. For now they are left untouched/enabled.
Info I found and used for this post
[UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 4K (mantis)
[Magisk][Module] FireTV 4K Stick Add-Ons
[FireTVStick4k] Updated Info November 2019
[NEWBIE GUIDE] How to Unlock Bootloader/Root and install Addons FireStick 4k
FireTV4k Stick: Achieving Root With Magisk
[LAUNCHER] XBMC/Kodi for Fire TV (Root)
Updated Kodi 18.5 version by the developer elmerohuesoWhich is posted here
Install OpenVPN on fireTV (no root required)
Running scripts on the Firestick, in this case the disable-bloat.sh script

This assumes you have an understanding of how to use adb and if more detail of any of the following steps is necessary then follow the steps in the first post.
Step 1
Plug it in, run through the setup and let it update. Enable ADB and Unknown Sources.
Step 2
Root it!
Guide here
Step 3
Get adb installed
Step 4
Install Magisk
Step 5
Install [Magisk][Module] FireTV 4K Stick Add-Ons
Step 6
Remove amazon bloat.
Download the script from here
Run on firestick via ADB
Step 7
If you want Kodi as the launcher, See the first post.
Step 8
Setting Kodi (or any other launcher) as the launcher, See the first post.
Step 9
Install other apps
OpenVPN install Seeing first post for more info
Smart Youtube TV (no ads)
Step 10
Other Tweaks
Stop firestick from going to sleep/returning to the home screen.

Things that don't work or I'm interested in trying to get working.
-Can't "install" apps from amazon. The app store is there and can install from "the cloud" but can't search for new apps. Likely due to something being disabled., just not sure what. I assume installing from amazon web into the cloud or something like that could be a work around. Might be that the only way to search for apps is with the default launcher?
-Voice search doesn't work. Looks like some people have kind of gotten it to work but I have not.
-Chromecast support.
Both would likely have a better chance if google play services/store could be installed. I see there was some effort put forth in trying to do that on previous firetvstick models so I may try some of the info that is out there. Seeing as we now have root its a lot more possible.....I assume.

reserved 1

reserved 2

I keep meaning to test nanodroid with microg & the patched play store. I've not done it yet as I was afraid patching the system would screw everything up & I had so much difficulty getting bootloader patched to begin with. It may not be necessary to patch system, I recall using an xposed module for spoofing some time ago on an old phone so that could be a possibility.
It might not work, but there's probably less that can go wrong as there's less "deep" system integration than using official gapps. Just an idea if you fancy trying it.

Booting between FireOS and TWRP
Below are the first steps in rooting the firestick 4k:
Once it reboot’s into TWRP do you now have root privs?
Can you stop here and not install a “pre-rooted image”?
Can I now boot between FireOS and TWRP if so How?
Thank You,
1.Boot the ISO
2.Download and extract the exploit package.
3.Open a terminal in the kamakiri directory
Run
Code:
4. ./bootrom-step.sh
Short one of the points in the attached photo to ground (the cage of the shielding).
Ideally you want to use DAT0, since that is tiny it might be easier to short the point marked CLK instead.
It is very important that you use a piece of soft wire or aluminum foil or something similar for shorting. Don't use tweezers as that makes it incredibly easy to knock of the capacitor off the PCB and kill the board!
5. Connect the stick to your computer (while keeping it shorted)Both USB and HDMI ???
6. The script should tell you to release the short and hit enter
Once finished run
Code:
7. ./fastboot-step.sh
Your device will now reboot into TWRP

RPM99 said:
Below are the first steps in rooting the firestick 4k:
Once it reboot’s into TWRP do you now have root privs? (Yes, but you need to install magisk to manage su)
Can you stop here and not install a “pre-rooted image”? (Yes, you don't need to install the image)
Can I now boot between FireOS and TWRP if so How? (adb commands or the reboot menu if you have the magisk module installed. For adb, insure you have adb debugging turned on, then log into the firestick (that's all in the guide) and run "reboot recovery")
Thank You,
1.Boot the ISO
2.Download and extract the exploit package.
3.Open a terminal in the kamakiri directory
Run
Code:
4. ./bootrom-step.sh
Short one of the points in the attached photo to ground (the cage of the shielding).
Ideally you want to use DAT0, since that is tiny it might be easier to short the point marked CLK instead.
It is very important that you use a piece of soft wire or aluminum foil or something similar for shorting. Don't use tweezers as that makes it incredibly easy to knock of the capacitor off the PCB and kill the board!
5. Connect the stick to your computer (while keeping it shorted)Both USB and HDMI ??? (hdmi isn't needed, just usb)
6. The script should tell you to release the short and hit enter
Once finished run
Code:
7. ./fastboot-step.sh
Your device will now reboot into TWRP
Click to expand...
Click to collapse
I replied inline in brackets. On mobile so a pain to in another way.

Thanks for the clarification
bnevets27 said:
I replied inline in brackets. On mobile so a pain to in another way.
Click to expand...
Click to collapse
Hi,
Inline with great answers is just fine, thank you.
I will investigate magisk, I didn't realize that's what it is for.
And "reboot recovery" at the adb command line will put me back in TWRP mode - This was great info!!
I ordered a new firestick to try this on, it will be here next week so I have some time to read up.
Thanks again,
Steve

More questions if you can please
RPM99 said:
Hi,
Inline with great answers is just fine, thank you.
I will investigate magisk, I didn't realize that's what it is for.
And "reboot recovery" at the adb command line will put me back in TWRP mode - This was great info!!
I ordered a new firestick to try this on, it will be here next week so I have some time to read up.
Thanks again,
Steve
Click to expand...
Click to collapse
When you short to ground and then plug into usb to boot firestick is that considered bootloader mode?
At what point is the greatest risk of bricking the firestick?
Thanks,
Steve

RPM99 said:
When you short to ground and then plug into usb to boot firestick is that considered bootloader mode?
At what point is the greatest risk of bricking the firestick?
Thanks,
Steve
Click to expand...
Click to collapse
I guess that would probably be technically correct.
Only time there's a chance of bricking, usually for flash anything, is during the writing process. Or a corrupt file.
I've done a hand full and haven't had any issues. Just take normal precautions like do what you can to prevent a power outage during the flash and once it's plugged in and flashing don't touch anything till its finished.
Personally I plugged in the mirco USB into the firestick first, then lined up the USB into the computer but didn't push it in. Held a small solid copper wire against the rf shield (the metal that surrounds the chip) and touched the side of what I think is a capacitor (you can't get to clk without taking the surrounding metal piece off). It's the "other" point they mention you can use. While doing that with one hand I plug in the USB to the computer. Remember the script has to be run first, waiting to see the stick before you plug it in.
If you miss time it or don't make the connection, the script just won't tell you to remove the short and press enter, so you'll just have to try again.

bnevets27 said:
...
Both would likely have a better chance if google play services/store could be installed. I see there was some effort put forth in trying to do that on previous firetvstick models so I may try some of the info that is out there. Seeing as we now have root its a lot more possible.....I assume.
Click to expand...
Click to collapse
Did you try https://forum.xda-developers.com/fire-tv/development/magisk-gapps-fireos-6-t4019095 ?

Kramar111 said:
Did you try https://forum.xda-developers.com/fire-tv/development/magisk-gapps-fireos-6-t4019095 ?
Click to expand...
Click to collapse
I haven't no. I might have missed that one. I've been pretty happy the the end result of using his module in this thread. And after updating to the latest version, voice search is working for me.
I have some other projects at the moment so I'm not working on this but I'll come back to later on.

bnevets27 said:
I haven't no. I might have missed that one. I've been pretty happy the the end result of using his module in this thread. And after updating to the latest version, voice search is working for me.
I have some other projects at the moment so I'm not working on this but I'll come back to later on.
Click to expand...
Click to collapse
When you say voice search is working, does that mean you can click the little mic icon at the top left of the Android TV launcher and it will search? Does it work well? Thanks

gogorman said:
When you say voice search is working, does that mean you can click the little mic icon at the top left of the Android TV launcher and it will search? Does it work well? Thanks
Click to expand...
Click to collapse
Yeah you have to click the mic on screen then the mic on the remote. Seems to work pretty well but haven't used it much more then just to see if it worked.

bnevets27 said:
Step 2
Root it!
Guide here
Click to expand...
Click to collapse
This exploit does not give you root. This unlocks the bootloader and then installs TWRP recovery.
.... I just used a small copper wire.
Click to expand...
Click to collapse
I used a Reese's candy wrapper! I just rolled it between my fingers and wedged it under the metal "cover," touching the CLK and DATA points. Then plugged it in to the USB port.
Step 4
Install Magisk
Click to expand...
Click to collapse
This is what gives you ROOT access.
Took me a while, reading through all the threads, to figure out which exploit does what.
Step 5
Install [Magisk][Module] FireTV 4K Stick Add-Ons
Click to expand...
Click to collapse
This module is great. It also disables Amazon firmware updates. There are a bunch of other tips in that thread too.
Thanks for the tips and tricks!

When trying to run the disable script I get i get an error at the last command. /data/local/tmp/bloat-disable.sh[7]: syntax error: 'newline' unexpected.When running command " sh /data/local/tmp/bloat-disable.sh "

Can you create a bloat-disable script dedicated to fire stick 4k (mantis) ? that would be beneficial for everyone.

[Discontinued] Linux on the Acer Iconia Tab A500, 2022 edition

UPDATE: I discontinued work for this tablet model, due to the lack of NEON support for the Nvidia Tegra 2 CPU used in this model. Any existing work I uploaded will remain online, but I won't be uploading anything new. I'm also considering selling my tablet to anyone interested.
I have become successful with getting postmarketOS to run on this tablet for the past 2 months, running mainline Linux (5.8.0 as of this writing). This allows us to use this tablet model for a little longer, without getting stuck on older Linux kernel versions.
postmarketOS is an experimental, touch-optimized and pre-configured Alpine Linux. It can be installed on smartphones and other devices.
About postmarketOS, from their homepage:
We are sick of not receiving updates shortly after buying new phones. Sick of the walled gardens deeply integrated into Android and iOS. That's why we are developing a sustainable, privacy and security focused free software mobile OS that is modeled after traditional Linux distributions. With privilege separation in mind. Let's keep our devices useful and safe until they physically break!
Click to expand...
Click to collapse
Wiki page for this tablet: https://wiki.postmarketos.org/wiki/Acer_Iconia_Tab_A500_(acer-picasso)
Most features should work, except for the camera and 3D acceleration. Wi-Fi and Bluetooth work only if the non-free firmware is chosen to be installed.
How to install:
Follow the installation guide at https://wiki.postmarketos.org/wiki/Installation_guide, where theses specifics have to be specified when requested (this device is now in upstream pmaports):
Vendor: acer
Device code-name: picasso
Install non-free Wi-Fi + Bluetooth firmware: y
Only the mainline kernel is available for installation now, as downstream kernels no longer successfully compile. The user interface may be freely selected, as long as it is not one that requires 3D acceleration. To use KDE Plasma 5, add these lines to /etc/security/pam_env.conf:
Code:
QT_IM_MODULE=qtvirtualkeyboard
QT_QUICK_BACKEND=software
LIBGL_ALWAYS_SOFTWARE=1
Next, run the following commands in succession, after each one finishes, assuming the working directory contains the pmbootstrap.py script:
Code:
> ./pmbootstrap.py build device-acer-picasso
> ./pmbootstrap.py build firmware-acer-picasso
> ./pmbootstrap.py build linux-postmarketos-grate
From here on out, the generated chroot can be either installed to the eMMC, or a microSD card that must be inserted at or before boot time (the latter method allows for dual-booting Android already installed to the eMMC, although it can be directly accessed from the Linux system). The boot partition always has to be flashed to the eMMC in fastboot mode, as it is not possible to boot directly off of a microSD card.
If installing to the eMMC, run
Code:
> ./pmbootstrap.py install
> ./pmbootstrap.py flasher flash_kernel --partition secboot
> ./pmbootstrap.py flasher flash_rootfs
(optional) > ./pmbootstrap.py flasher boot
If installing to a microSD card, run
Code:
> ./pmbootstrap.py install --sdcard [path to the device for installation]
> ./pmbootstrap.py flasher flash_kernel --partition secboot
Depending on what user interface was chosen earlier in the installation process, there may not be enough packages installed to get a fully-loaded GUI. Besides the built-in Wi-Fi, it is also possible to use a USB ethernet adapter, or connect to another computer with a micro-USB cable and get RNDIS access that enables using SSH to the tablet.

Using another distro in place of postmarketOS
Advanced: Using another distro in place of postmarketOS
It is possible, if using the microSD card method, to use a different distro instead of postmarketOS, for those who want more software OOTB. I use the Ubuntu MATE rootfs from https://ubuntu-mate.org/ports/raspberry-pi/ as my daily driver, but other distros may take more effort to get working. Glibc limitations no longer apply, as the kernel version is no longer stuck at 3.1.0 (unlike with my earlier attempts). Carefully follow the instructions listed below, or the resulting system will become unbootable:
Use losetup or GNOME Disks (Utility) to mount the image in read-write mode.
Run GParted with the loop image and the target microSD card as the arguments.
Copy only the larger rootfs partition to the microSD card. Resize as necessary to get it to fit on the target microSD card.
Make sure on the target microSD card the boot partition is named 'pmOS_boot' and the rootfs 'pmOS_root'. The initramfs is hard-coded to search for partitions with these names by default for microSD cards. The loop image is not needed after this point, and can be safely detached.
On the copied rootfs, edit /etc/fstab to reflect the partition layout. To get access to Wi-Fi and Bluetooth, copy the kernel modules and firmware from the pmOS rootfs on the host system to the microSD rootfs.
Let me know if something wasn't understood from my instructions, or more clarification is needed. The instructions here can be somewhat overwhelming for those who have less Linux experience, but at least we're not forced to stay on old distro versions anymore.

Premade Linux images
I finally have managed to create a premade image to make the installation process easier for other people, especially for those who don't want to go through the hassle of compiling software. Every image I make can be found at https://drive.google.com/drive/folders/1pMqaS5GaM6N9TAKlNGQZWCG8UTiRn4pK?usp=sharing.
For all images:
Kernel version: 5.15.0-rc4
Includes all compiled kernel modules from postmarketOS builds, plus nonfree firmware enabled.
The postmarketOS splash screen will appear, although the underlying OS differs based the image used.
Images available:
Ubuntu MATE 20.04.1 (ubuntu-mate-20.04.1-desktop-armhf+acer-picasso.img.xz) (size: 1.3 GiB):
Based on 'ubuntu-mate-20.04.1-desktop-armhf+raspi.img.xz', available from https://ubuntu-mate.org/ports/raspberry-pi/
Underlying OS is Ubuntu 20.04.1, which is supported for 5 years until April 2025. However, Ubuntu MATE officially has support only until April 2023.
Requires at least an 8 GB or greater size microSD card (the image is 5.6 GiB decompressed).
The setup screen will open upon the first successful boot, where a username and password have to be set.
Most extra packages for the Raspberry Pi family of computers have been removed, including the kernels.
The battery icon in MATE cannot be enabled graphically, as the preferences window has been patched to permanently hide such an option (as the Raspberry Pis lack native battery support); instead run the command
Code:
gsettings set org.mate.power-manager icon-policy 'always'
to manually enable it.
The PPA at https://launchpad.net/~grate-driver/+archive/ubuntu/ppa is pre-configured to be accessed. Most packages from this repository, including the opentegra driver, come preinstalled. They currently are enough to get 2D acceleration working, but not for 3D acceleration.
Except for what has been mentioned above, any packages shipped may have to be updated once an internet connection is established.
Arch Linux ARM (ArchLinuxARM-armv7-latest+acer-picasso.img.xz) (size: 576.6 MiB):
Based on 'ArchLinuxARM-armv7-latest.tar.gz', available from https://archlinuxarm.org/about/downloads
Rolling release distro often with the latest versions of most packages. More recent software can be acquired at a small expense of instability.
Requires at least an 2 GB or greater size microSD card (the image is 1.9 GiB decompressed). Larger size is recommended for installing more packages.
To login into system:
Login as the default user alarm with the password alarm.
The default root password is root.
Initially command-line only; contains no desktop environment installed.
Use any image writing program with these images. If such a program does not support XZ compression, the image needs to be extracted instead, and that has to be used.
I hope the images will proves useful to some people. Let me know if any issue pops up during usage of this image!

hey Worldblender,
I have flashed the premade file you shared to an sdcard but I'm unsure as to how to boot into it?

tehno said:
hey Worldblender,
I have flashed the premade file you shared to an sdcard but I'm unsure as to how to boot into it?
Click to expand...
Click to collapse
The instructions were written assuming that the user has already flashed the custom bootloader as described here: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271. Sorry for not making this clear anywhere, but that custom bootloader, along with flashing the boot image found in the first partition named "pmOS_boot" to either boot or secboot using fastboot, should get you set up to boot the SD card image.

Hi Worldblender,
Nice to see you work on this legacy device.
I definitely don't want to use android or can use it anymore on this tablet.
Nice to see some linux flavor being ported to it.
I had a look a the dedicated page on postmarketos.
Can you confirm the only GUI availbale as for now is the one called "Weston" ?
Or is MATE also working (from the screenshot) ?
Weston seem very basic, MATE more friendly.
How about performance ?
I'm considering reusing it to display a grafana dashboard in firefox for instance, maybe more if performance isn't too bad.

Worldblender said:
The instructions were written assuming that the user has already flashed the custom bootloader as described here: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271. Sorry for not making this clear anywhere, but that custom bootloader, along with flashing the boot image found in the first partition named "pmOS_boot" to either boot or secboot using fastboot, should get you set up to boot the SD card image.
Click to expand...
Click to collapse
Thank you Worldblender for your work in writing up instructions and compiling the image too.
However, I'm still a bit lost as to what to do with your Ubuntu Mate image.
I've gotten the TWRP bootloader installed onto my Acer A500 tablet, but whether I use Rufus to expand your image onto an SD card, or just copy the compressed image onto the SD card, the [ Install ] does not see any images inside of the drive. Am I supposed to decompress your image in Windows and use the 0.img and 1.img in place of the nvflash's boot.img and recovery.img?
While I can see the two partitions in Ubuntu, I'm equally lost as to what to do with them, and how to get it onto the tablet.

coluwyvurne said:
Thank you Worldblender for your work in writing up instructions and compiling the image too.
However, I'm still a bit lost as to what to do with your Ubuntu Mate image.
I've gotten the TWRP bootloader installed onto my Acer A500 tablet, but whether I use Rufus to expand your image onto an SD card, or just copy the compressed image onto the SD card, the [ Install ] does not see any images inside of the drive. Am I supposed to decompress your image in Windows and use the 0.img and 1.img in place of the nvflash's boot.img and recovery.img?
While I can see the two partitions in Ubuntu, I'm equally lost as to what to do with them, and how to get it onto the tablet.
Click to expand...
Click to collapse
Wait for me to give out an update to the image, as there likely has been a new kernel version released that I would like to have updated first.
TWRP will not be used at all for this installation process, as the image is too big to flash with fastboot. Just flash the image to a microSD card, as the boot image that will be flashed will automatically pick it up shortly after booting. The only thing that does have to be flashed is the boot.img, which can be found in the first partition, and you will be only using fastboot for this process, not anything else.

I released a new version of the premade Ubuntu MATE image just now, named 'ubuntu-mate-20.04.1-desktop-armhf+acer-picasso.img.xz'. The following changes have been made since the last image:
Kernel version upgraded to 5.10.1-rc1
Based on Ubuntu MATE 20.04.1
Everything that changed since the beta1 image
Other than these changes, there are no other differences that can be noticed right away.
Direct link: https://drive.google.com/file/d/1mr-7e29KJYeagJju0Yo1qUpT2YRb61AR/view?usp=sharing

Many thanks for your work. I've entered today this forum just curious about something new and found this!
Second life for this old machine!
For those with problems installing, I've flashed precompiled image using balenaEtcher into the sdcard.
Then, extracted .xz image, extracted .img, then extracted 0.img and copied boot file from there. After that, renamed the file to boot.img and flashed it with fastboot.
As I've the old modified skrillex bootloader, the command is fastboot flash secboot boot.img.
It boots and works well for now!

Worldblender said:
[*] Add the PPA at https://launchpad.net/~grate-driver/+archive/ubuntu/ppa to get access to updated video drivers. They currently are enough to get 2D acceleration working, but not for 3D acceleration.
Click to expand...
Click to collapse
@Worldblender
Hi, i apt updated after adding grate-driver ppa, it seems it broken xorg because X don't start anymore
Can you detail how to proceed ?

pheex79 said:
@Worldblender
Hi, i apt updated after adding grate-driver ppa, it seems it broken xorg because X don't start anymore
Can you detail how to proceed ?
Click to expand...
Click to collapse
Can you still switch to a virtual terminal with Ctrl-Alt-[F1-F7]? You will need a USB keyboard to do this. Then try, after logging in with your username and password:
Code:
systemctl stop lightdm
startx
If startx does not bring something up, could you try running journalctl, and show me any log entries relating to lightdm?
If that still fails, you can try (if ppa-purge is not installed, install that first)
Code:
ppa-purge ppa:grate-driver/ppa

@Worldblender
one binary missing but i think this error is present before adding ppa
"/sbin/prime-switch: 22: /usr/bin/gpu-manager: not found"
Xorg log:
Require OpenGL version 2.1 or later
modeset(0): Failed to initialize glamor at ScreenInit() time

pheex79 said:
@Worldblender
one binary missing but i think this error is present before adding ppa
"/sbin/prime-switch: 22: /usr/bin/gpu-manager: not found"
Xorg log:
Require OpenGL version 2.1 or later
modeset(0): Failed to initialize glamor at ScreenInit() time
Click to expand...
Click to collapse
I never received such an error, but the specific package you must install is xserver-xorg-video-opentegra. No other Nvidia driver is going to work.

Worldblender said:
I never received such an error, but the specific package you must install is xserver-xorg-video-opentegra. No other Nvidia driver is going to work.
Click to expand...
Click to collapse
It works ! Thank you
xserver-xorg-video-opentegra was not installed
when adding ppa grate i only did an "apt upgrade" cmd i thought all grate items were installed (a few are installed when upgrading apt)

Nice work thank you so much.
Is there any chance for Manjaro arm? Or is it limited to debian based distros?

Note that after following the instructions for installing the Ubuntu MATE image from @Worldblender from a starting point of just the stock image, I have Ubuntu MATE installed on the external SD card and no OS installed on the eMMC because it was wiped during the bootloader replacement. Reading back through the posts suggests this is by design.

@Worldblender, so I'm very new at rooting devices, and have a little experience with Ubuntu but feel pretty lost. Any chance you could hook me up with a step by step install of the Nov2 image (unless you've put together another new version) from a stock(not rooted or anything) A500? I apologize if I overlooked something.
Edit: I got it working after doing this thing called reading, I definitely overlooked some things after reading closer. For someone else that might find themselves in my shoes here's what I did.
I followed this link: https://forum.xda-developers.com/iconia-a500/a500-2019-2020-t4039271 to get the bootloader installed
and then followed @whylly 's instructions:
whylly said:
For those with problems installing, I've flashed precompiled image using balenaEtcher into the sdcard.
Then, extracted .xz image, extracted .img, then extracted 0.img and copied boot file from there. After that, renamed the file to boot.img and flashed it with fastboot.
As I've the old modified skrillex bootloader, the command is fastboot flash secboot boot.img.
Click to expand...
Click to collapse

Hi there ! I have an iconia a500, rooted with lightspeed 4.8. Can I install this and then make it switch to Khali linux ? My ultimate objective is to get Khali on this tablet. I've worked my way down from ver 2.5x linuxdeploy all the way down to 2.0 lol So I'm thinking maybe if I apply your OS it will update the Kernal from 4.0.3 to 5 yes ? (That's a big jump for linuxdeploy) then I can apt-get khalifull ? Am I off base would this work ? Unless you have an image already of course in which case pleaaaaaaaaaaaaaase I'll pay for the bloody thing if I have to I've been pulling my hair out for days. Tried frikkin everything.
Unless anybody has a better method of course in which case feel free to suggest. If I have to make the image from scratch so be it
EDIT: UGhhhhhh after days of troubleshooting, I got to linuxdeploy2.0-1.16 installed kali (the native one on the app not from the repository as that gives kernel too old once you get the install working). Managed to term in and tried to start lxde, failed because lxde doesn't exist (sigh) tried to apt-get... kernel too old. game over sigh
Unless someone has a workaround I don't think it's possible to get Khali on a500.

Sound work?

Fire hd 8 7th gen root

I tried all rooting methods for fire hd 8 7th gen but didnt succeed... the apply update in the recovery is also not there... can anyone help me?
im new...

Darklord071 said:
I tried all rooting methods for fire hd 8 7th gen but didnt succeed... the apply update in the recovery is also not there... can anyone help me?
im new...
Click to expand...
Click to collapse
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?

Letitride said:
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?
Click to expand...
Click to collapse
Thanks for the welcome.. i tried using linux and windows... the fire tab is running fire os 5.6.6.0..
i know adb commands..and i disabled ads using fire toolkit.
and i use debian linux.
Thanks in advance!!

Letitride said:
Welcome to XDA ... as a newbie
It would help, I think, for you to let us a little more about your device status - i.e. running Fire OS 5.6.4.0 (or newer/newest one) ? Have you managed to disabled Ads using one of the methods ? Have you used the "Android Toolkits V8.2 being the newest" - not that it will help you learn about ADB commands ?
What about using Linux OS and using that approach to unlock/root & sideload ?
Click to expand...
Click to collapse
btw do u have the drivers for 32bit arch linux?
thx

Darklord071 said:
btw do u have the drivers for 32bit arch linux?
thx
Click to expand...
Click to collapse
Fire OS 5.6.6.0 is the newest one and my understanding is that version/release is a PITA as the "exploit" to unlock & inject the Fastboot mod is a problem .... sorry about that, maybe another XDA'er familiar with that can help walk you thru on their efforts & success (or not) i.e. whether they managed to roll it back.
I used LMDE-4 Cinnamon 64bit (d/l via Linux Mint) and it works fine on my good old Dell 380 desktop on USB stick ... don't believe one can get anything done if I stay on Windows 10 Pro. Copy or download all the possible files you need to the USB/thumb drive ahead or while connected in LInux ... go slow & a nice cup of coffee is always good to watch & sip. If you have even older hardware (just retired my 15 years old Dell Optiplex 620 MT which has been a home server) - LMDE-3 Cinnaman 32 or 64 bits (LTS) should do. Sorry, I don't have a link to any 32 bits ... just go search for it while connected.
If and when you managed to modify the HD8 and get back into Bootloader & Recovery, do not restart the device until you are certain that TWRP is up & running (whether you install & run Magisk or not, doesn't matter) Then, sideload & flash either LIneage 12 OS or the "stock" HD8 rom in this XDA thread/link - https://forum.xda-developers.com/hd...rmware-amazon-fire-hd-8-2017-douglas-t3972921
Even if you cannot do some/all of the above, the latest V8.2 Toolbox itself is pretty good - ads blocked & OTA stopped/disabled, able to install Google Apps & Play Store, etc. and Nova Laucher (I recommend & use it myself on the FD8) ... it is more responsive than Lineage (being in "beta" status) - install some apps & run it, let it update & settle down for a day or two.
Be sure to read & follow all the steps, disable WiFi & turn on Developer's Mode, enabled USB debug, etc. - then resume & do the setup after using the Toolbox.
Not bad for a $60 device that's 3+ years old, I got Youtube Vance running, Adaway installed & FB/Messenger/IG "Lite" working - use it to watch videos on a 64 GB mSD card offline, and check email & run news app ... when not using it as a security cam monitor linked to our Xiaomi & Wyze wifi cams.
Just don't feel like trading up for a $10 Amazon gift card & get the newest HD8 with 20% discount - if and it's on sale on 2020 Prime Day, I might just grab another one to play.
What do you wish, hope & expect the HD8 to do by rooting it ??

Letitride said:
Fire OS 5.6.6.0 is the newest one and my understanding is that version/release is a PITA as the "exploit" to unlock & inject the Fastboot mod is a problem .... sorry about that, maybe another XDA'er familiar with that can help walk you thru on their efforts & success (or not) i.e. whether they managed to roll it back.
I used LMDE-4 Cinnamon 64bit (d/l via Linux Mint) and it works fine on my good old Dell 380 desktop on USB stick ... don't believe one can get anything done if I stay on Windows 10 Pro. Copy or download all the possible files you need to the USB/thumb drive ahead or while connected in LInux ... go slow & a nice cup of coffee is always good to watch & sip. If you have even older hardware (just retired my 15 years old Dell Optiplex 620 MT which has been a home server) - LMDE-3 Cinnaman 32 or 64 bits (LTS) should do. Sorry, I don't have a link to any 32 bits ... just go search for it while connected.
If and when you managed to modify the HD8 and get back into Bootloader & Recovery, do not restart the device until you are certain that TWRP is up & running (whether you install & run Magisk or not, doesn't matter) Then, sideload & flash either LIneage 12 OS or the "stock" HD8 rom in this XDA thread/link - https://forum.xda-developers.com/hd...rmware-amazon-fire-hd-8-2017-douglas-t3972921
Even if you cannot do some/all of the above, the latest V8.2 Toolbox itself is pretty good - ads blocked & OTA stopped/disabled, able to install Google Apps & Play Store, etc. and Nova Laucher (I recommend & use it myself on the FD8) ... it is more responsive than Lineage (being in "beta" status) - install some apps & run it, let it update & settle down for a day or two.
Be sure to read & follow all the steps, disable WiFi & turn on Developer's Mode, enabled USB debug, etc. - then resume & do the setup after using the Toolbox.
Not bad for a $60 device that's 3+ years old, I got Youtube Vance running, Adaway installed & FB/Messenger/IG "Lite" working - use it to watch videos on a 64 GB mSD card offline, and check email & run news app ... when not using it as a security cam monitor linked to our Xiaomi & Wyze wifi cams.
Just don't feel like trading up for a $10 Amazon gift card & get the newest HD8 with 20% discount - if and it's on sale on 2020 Prime Day, I might just grab another one to play.
What do you wish, hope & expect the HD8 to do by rooting it ??
Click to expand...
Click to collapse
I wanna install custom roms to get a better experience... Thanks a lot ??.

Darklord071 said:
I wanna install custom roms to get a better experience... Thanks a lot .
Click to expand...
Click to collapse
There isn't much custom rom development going on with a years old Fire HD tablet, unless you are prepared to work on LOS's V12 beta (newest release) - which I tried briefly, which I am hoping to go back to when status is "stable". I am perfectly happy to go back to use the tablet as an always-on mini monitor for our home security cams.
Have you managed to root yours yet ??
Just FYI and as a sideload, I've been watching prices for the newest HD8 2020 (Gen 10) priced at $89.99 - with Prime Day around the corner. Well, I hit the Enter key today upon getting an alert that it's on sale at QVC for $59.99 with free standard shipping. Wiki codes & whatever - able to use a "New" code to get an additional $15 off, hence - ordered it, just a click over $50 shipped, taxes included - AND, it's bundled with a coupon for free case redemption (that's anywhere from $15 to $25) and other goodies. I should get mine by next weekend - going to have fun with the Toolbars Kit & see how far I can run with it, and see if the smart XDA'ers will find a way to root it - got another inexpensive tablet to play & watch YouTube Vanced, etc.

This post was a Mistake

Letitride said:
There isn't much custom rom development going on with a years old Fire HD tablet, unless you are prepared to work on LOS's V12 beta (newest release) - which I tried briefly, which I am hoping to go back to when status is "stable". I am perfectly happy to go back to use the tablet as an always-on mini monitor for our home security cams.
Have you managed to root yours yet ??
Just FYI and as a sideload, I've been watching prices for the newest HD8 2020 (Gen 10) priced at $89.99 - with Prime Day around the corner. Well, I hit the Enter key today upon getting an alert that it's on sale at QVC for $59.99 with free standard shipping. Wiki codes & whatever - able to use a "New" code to get an additional $15 off, hence - ordered it, just a click over $50 shipped, taxes included - AND, it's bundled with a coupon for free case redemption (that's anywhere from $15 to $25) and other goodies. I should get mine by next weekend - going to have fun with the Toolbars Kit & see how far I can run with it, and see if the smart XDA'ers will find a way to root it - got another inexpensive tablet to play & watch YouTube Vanced, etc.
Click to expand...
Click to collapse
I haven't rooted mine yet... I used the raspberry pi before??.. so I am gonna use a laptop soon... I'm only 14 yrs old???. I wanna also be a software developer when I grow up.. and my laptop is in the us and can't be delivered to me cuz of the pandemic.... Thanks a lot and I posted this question in reddit and some nice guy gave me the link for directions.. these are the instructions posted by a fellow xda'er..
Yesterday i managed to root updated FireOS and install Lineage 12.1, so, here's my story
Version 5.6.6.0 build 654620620,
on Linux KDE Neon.
Installed python3, PySerial, adb, fastboot dos2unix as described in this and other posts.
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Downloaded the following attachments from the first post : amonet-douglas-v1.2.zip and brick-douglas.zip
Extract both files to the same folder
Enable Developer options and enable ADB (inside debugging options) on Amazon tablet
Plug in the tablet (has to be turned on)
Now comes the commands execution part. So, open the terminal in Linux (lines that start with // are comments and should not be run from command line - if you copy paste)
Code:
sudo systemctl stop ModemManager && sudo systemctl disable ModemManager
Code:
adb devices
// there should be an item listed
// to be sure, you can unplug and run it again, if it's empty,
// ou know tablet can connect, so plug in the tablet back
Code:
adb reboot bootloader
// reboots the tablet and awaits commands
Code:
sudo ./brick.sh
// type YES, hit enter
// it will take a couple of minutes (around 3-5min in my case)
// watch the tablet for success message, it should be displayed there if everything works
// but also, watch your terminal...if it gives you error message similiar to:
// ==> [I][U]failed with error message that it can't write somewhere[/U][/I]
// you have to try with brick-9820 script
Code:
sudo ./brick-9820.sh
// it will take a couple of minutes, similar to above step
NOTE : after either of the above commands (which one succeeds) POWER OFF THE TABLET and DO NOT try to turn it back on. It should stay powered off!!
Code:
sudo ./bootrom-step.sh
// this will take some time (in my case around 5-10 minutes)
// will give you message similar to "awaiting device connection" and nothing else...
// although nothing seems to happen, just wait a bit and watch the terminal, it will soon start displaying the process
// it should then reboot the tablet, but in my case, that did not happen, so i had to do it manually...
// NOTE that althought tablet seems to be "off", it isn't, so press power btn and hold for 5 sec to turn it off
// after that click and hold volume up button (when in portrait mode it is the right one, the one closest to power btn)
// and immediately after that press and hold the power btn until amazon logo shows itself
// it should then show in bottom left corner HACKED FASTBOOT after a few seconds
Code:
sudo fastboot devices
// there should be a device listed
// if not, you should run (in the extracted directory that you are in):
./bin/fastboot devices
// if sudo fastboot devices does not show your device but ./bin/fastboot works, you have to edit the fastboot-step.sh file and change the fastboot commands to ./bin/fastboot
Code:
sudo ./fastboot-step.sh
// takes a couple of minutes (1-3 min in my case)
// reboots the device
after that you should be in TWRP
NOTE when in TWRP:
DO NOT RESTART tablet before the following
(or amazon fire os will overwrite TWRP and you will be reset to factory default with fireOS, losing everything you've done and starting from scratch...
when it happened to me, the brick-9820.sh didn't work anymore and had to use brick.sh script)
-allow modifications
-format data,system,cache partitions, go to wipe->advanced wipe-> repair/format (something like that), select each of the 3 partitions aformentioned and format to ext4
-if you've done it correctly, there should not be any red warnings
-after that go to wipe, select all partitions and wipe them (just to be sure)
-tablet should be connected and TWRP should be left on
on PC
-download Lineage 12.1 ROM from https://forum.xda-developers.com/hd8-hd10/general/discussion-root-progress-fire-hd-8-t3743024
-download opengapps from https://opengapps.org/
- put them inside amonet-douglas-v1.2 folder where you've extracted the prior ZIP files (just to be clear, you can put them anywhere, but i like to keep it all inside the working directory)
-go to terminal
Code:
adb push lineage-12.1-20200614-UNOFFICIAL-douglas.zip /sdcard
adb push open_gapps-arm64-5.1-nano-20200624.zip /sdcard
now the files are on the tablet
- in TWRP go to INSTALL, go to /sdcard folder if not in it
- first install Lineage ROM from zip
- then install GApps from zip
hope it works!
I'm glad i've finally rooted it, thank you all for the great content here!

Darklord071 said:
I haven't rooted mine yet... I used the raspberry pi before.. so I am gonna use a laptop soon... I'm only 14 yrs old. I wanna also be a software developer when I grow up.. and my laptop is in the us and can't be delivered to me cuz of the pandemic.... Thanks a lot and I posted this question in reddit and some nice guy gave me the link for directions.. these are the instructions posted by a fellow xda'er..
Yesterday i managed to root updated FireOS and install Lineage 12.1, so, here's my story
Version 5.6.6.0 build 654620620,
on Linux KDE Neon.
Installed python3, PySerial, adb, fastboot dos2unix as described in this and other posts.
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Downloaded the following attachments from the first post : amonet-douglas-v1.2.zip and brick-douglas.zip
Extract both files to the same folder
Enable Developer options and enable ADB (inside debugging options) on Amazon tablet
Plug in the tablet (has to be turned on)
Now comes the commands execution part. So, open the terminal in Linux (lines that start with // are comments and should not be run from command line - if you copy paste)
Code:
sudo systemctl stop ModemManager && sudo systemctl disable ModemManager
Code:
adb devices
// there should be an item listed
// to be sure, you can unplug and run it again, if it's empty,
// ou know tablet can connect, so plug in the tablet back
Code:
adb reboot bootloader
// reboots the tablet and awaits commands
Code:
sudo ./brick.sh
// type YES, hit enter
// it will take a couple of minutes (around 3-5min in my case)
// watch the tablet for success message, it should be displayed there if everything works
// but also, watch your terminal...if it gives you error message similiar to:
// ==> [I][U]failed with error message that it can't write somewhere[/U][/I]
// you have to try with brick-9820 script
Code:
sudo ./brick-9820.sh
// it will take a couple of minutes, similar to above step
NOTE : after either of the above commands (which one succeeds) POWER OFF THE TABLET and DO NOT try to turn it back on. It should stay powered off!!
Code:
sudo ./bootrom-step.sh
// this will take some time (in my case around 5-10 minutes)
// will give you message similar to "awaiting device connection" and nothing else...
// although nothing seems to happen, just wait a bit and watch the terminal, it will soon start displaying the process
// it should then reboot the tablet, but in my case, that did not happen, so i had to do it manually...
// NOTE that althought tablet seems to be "off", it isn't, so press power btn and hold for 5 sec to turn it off
// after that click and hold volume up button (when in portrait mode it is the right one, the one closest to power btn)
// and immediately after that press and hold the power btn until amazon logo shows itself
// it should then show in bottom left corner HACKED FASTBOOT after a few seconds
Code:
sudo fastboot devices
// there should be a device listed
// if not, you should run (in the extracted directory that you are in):
./bin/fastboot devices
// if sudo fastboot devices does not show your device but ./bin/fastboot works, you have to edit the fastboot-step.sh file and change the fastboot commands to ./bin/fastboot
Code:
sudo ./fastboot-step.sh
// takes a couple of minutes (1-3 min in my case)
// reboots the device
after that you should be in TWRP
NOTE when in TWRP:
DO NOT RESTART tablet before the following
(or amazon fire os will overwrite TWRP and you will be reset to factory default with fireOS, losing everything you've done and starting from scratch...
when it happened to me, the brick-9820.sh didn't work anymore and had to use brick.sh script)
-allow modifications
-format data,system,cache partitions, go to wipe->advanced wipe-> repair/format (something like that), select each of the 3 partitions aformentioned and format to ext4
-if you've done it correctly, there should not be any red warnings
-after that go to wipe, select all partitions and wipe them (just to be sure)
-tablet should be connected and TWRP should be left on
on PC
-download Lineage 12.1 ROM from https://forum.xda-developers.com/hd8-hd10/general/discussion-root-progress-fire-hd-8-t3743024
-download opengapps from https://opengapps.org/
- put them inside amonet-douglas-v1.2 folder where you've extracted the prior ZIP files (just to be clear, you can put them anywhere, but i like to keep it all inside the working directory)
-go to terminal
Code:
adb push lineage-12.1-20200614-UNOFFICIAL-douglas.zip /sdcard
adb push open_gapps-arm64-5.1-nano-20200624.zip /sdcard
now the files are on the tablet
- in TWRP go to INSTALL, go to /sdcard folder if not in it
- first install Lineage ROM from zip
- then install GApps from zip
hope it works!
I'm glad i've finally rooted it, thank you all for the great content here!
Click to expand...
Click to collapse
Dude! Thank you so much for sharing this, I've spent hours looking for a solution and I'll certainly give this a go when I next get the opportunity. Literally I exhausted all my efforts to the point where I posted a question a couple of days ago (https://forum.xda-developers.com/showpost.php?p=83638279&postcount=584). Fingers crossed your very helpful reply will help me see an end to this painful process!

lmao
andyboot said:
Dude! Thank you so much for sharing this, I've spent hours looking for a solution and I'll certainly give this a go when I next get the opportunity. Literally I exhausted all my efforts to the point where I posted a question a couple of days ago (https://forum.xda-developers.com/showpost.php?p=83638279&postcount=584). Fingers crossed your very helpful reply will help me see an end to this painful process!
Click to expand...
Click to collapse
LMAO. No problem
btw it worked for other ppl so, it will definitely work for you!

Darklord071 said:
LMAO. No problem
btw it worked for other ppl so, it will definitely work for you!
Click to expand...
Click to collapse
Quick update, worked like a charm! Thanks once again!

WORKED!!
andyboot said:
Quick update, worked like a charm! Thanks once again!
Click to expand...
Click to collapse
tried it yesterday.. IT WORKED!!!

Just wanted to add another confirmation that these steps worked. Its hard finding the correct info for such an old device and so much out of date guides, but this worked like a charm.

thetakerfan said:
Just wanted to add another confirmation that these steps worked. Its hard finding the correct info for such an old device and so much out of date guides, but this worked like a charm.
Click to expand...
Click to collapse
Hit the thanks button if you want to!

Thanks Darklord071. Worked like a charm.
I guess LineageOS 12.1 is the best we can get huh? it's showing Android 5.1.1.
Some apps are not compatible with those old Android versions. Oh well.