Related
Information: If you're experienced with ADB/Fastboot or Manual Android Rooting, you could read this thread and see if you find something that seems wrong and report to me, thanks!
IntroductionHello there!
I decided to create a new Nexus 7 Rooting Guide, I know that there are some guides already, but I have a few reasons to make this guide.
Unlike many rooting guides, this one doesn't use an automated program (a.k.a Toolkit) and it works for both Nexus 7 Wi-Fi and Nexus 7 3G.
This guide has been tested with a Nexus 7 3G Edition, running Android 4.2.1/4.2.2.
Last Topic Update: Never
Last Minor Topic Update: Check thread edit date!
Requirements:
Nexus 7 (Wi-Fi or 3G Edition)
Android SDK
ADB/Fastboot Drivers
Unlocked Bootloader
If you don't have ADB/Fastboot drivers installed, please check out this thread:
http://forum.xda-developers.com/showthread.php?t=1907796
See Basic Knowledge and Driver Installation parts.
If you have Android SDK and ADB/Fastboot drivers installed and working, you can continue reading.
Make sure you have USB Debugging enabled in your Nexus 7.
Don't forget to unlock the bootloader!
Warning: You're the only one responsible if something bad happens to your device!
Nothing bad is going to happen, but there is always a small risk.
Personally, I recommend having +60% of Battery during ROM Changes (Flashing and etc).
I also recommend you to learn how to do a Factory Image Restore (Flash Stock ROM) before attempting to root...
Rooting your Nexus 7
To root our device, we're simply going to put in our tablet a small program called "SuperSU", you might want to download it now to your PC:
SuperSU v1.04
Basically, we´re going to put SuperSU in /system partition, the file you downloaded is a "Flashable ZIP".
We're going to use TWRP (Team Win Recovery Project) to flash the Flashable ZIP (In this case, SuperSU), after flashing SuperSU you get root privileges!
Now, go to your Android SDK Folder where Fastboot (fastboot.exe) is located (platform-tools), open a command prompt and change directories to your Fastboot location, if you need help just search on Google.
Now, you have CMD (Command Prompt) open with the Android SDK Directory, and we need to reboot your device into Fastboot mode, to do that just type the following:
adb reboot-bootloader
Click to expand...
Click to collapse
You're now in Fastboot Mode (a.k.a Bootloader), type the following to make sure you're in Fastboot Mode:
fastboot devices
Click to expand...
Click to collapse
You should see something like this:
Code:
> fastboot devices
# the following output should be returned
<device serial number> fastboot
Type "fastboot reboot" to reboot the device, then copy the SuperSU.zip you downloaded to your Nexus 7.
I also forgot to tell you to download TWRP, if you have the Nexus 7 Wi-Fi Edition, your board codename is Grouper, if you have the 3G Edition, your board codename is Tilapia.
TWRP for Nexus 7 [grouper]
TWRP for Nexus 7 3G [tilapia]
Copy the correct TWRP Edition to your Nexus 7, then boot into the bootloader.
Temporarily boot TWRP using the following command:
fastboot boot TWRP.img
Click to expand...
Click to collapse
Replace "TWRP.img" with the correct file name.
You can also flash TWRP instead of temporarily booting.
Inside TWRP click "Install" and select the SuperSU ZIP File, then Confirm Flash.
After flashing, reboot your device and you should have SuperSU installed. (Open SuperSU just to test)
Congratulations! You now have a Rooted Device!
To make sure you have rooted, download "Root Checker" from Google Play.
ConclusionAs you can see, this tutorial is a little different from others, I explained what we were going to do and also explained the commands instead of giving you directly the commands.
This tutorial was written to teach the basics of ADB/Fastboot, I hope you rooted your device without problems and learnt/learned something, have a good day!
Feel free to give suggestions or corrections!
This work is licensed under a Creative Commons Attribution-NonCommercial 3.0 Unported License.
Just for newbies wondering what this really means:
1. install and boot into TWRP/CWM recovery means you boot up a 'mini' linux which can do whatever it wants(as root) to any of the partition on the device(including the /system one)
2. the supersu package contains 2 files(an APK and the more importantly 'su') plus some update scripts that (1) would run and copy them to the appropriate places(mainly the 'su' which is the only file that is critical)
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
bftb0 said:
I think you need to mention the bootloader unlock someplace.
Perhaps you can find those specific instructions in another good reference thread; but if not then, at a minimum you should put it in your prerequisites list.
In the narrative as it stands, you casually mention the other thread
[GUIDE] Flashing a Factory Image with fastboot / return to stock
but don't insist that your reader looks at that thread.
But the time for doing the unlock sequence follows the begginers first (fastboot) driver installation, so unless someone reads that thread pretty thoroughly, they will skip it in your description here, and will get stopped out at
Code:
fastboot boot TWRP.img
which needs the privileges of an unlocked bootloader. Since unlocking the bootloader currently entails performing a full-phone wipe, the consequences of that are pretty significant and shouldn't be skipped over.
cheers. Thanks.
Click to expand...
Click to collapse
Hello!
Thanks for your answer, I completely forgot about the "Unlocking Bootloader" part, tomorrow when I get some time I will edit the thread...
Have a good day/night.
Edit: Added "Unlocked Bootloader" to the requisites list and a small note after "Make sure you have USB Debugging enabled in your Nexus 7", tomorrow I may edit the thread again.
Edit 2: I think the essential part is written, and because I'm a little busy, I will leave (temporarily) this thread. You're free to enhance this guide and re-publish it following Creative Commons Attribution-NonCommercial 3.0 Unported License.
I thought there might be a few people who have Macs with questions who'd like to get a quick express guide to getting up and running with Ubuntu Touch on their phone. This isn't that different than flashing your ROM and in fact is the same procedure on linux or windows except the adb and fastboot bins come from somewhere else.
* If you don't already have it, install ADB and Fastboot
http://code.google.com/p/adb-fastboot-install/
* Download the five images files for your device from Ubuntu
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
CODENAMES
Galaxy Nexus - maguro
Nexus 4 - mako
Nexus 7 - grouper
Nexus 10 - manta
quantal-preinstalled-boot-armel+CODENAME.img
quantal-preinstalled-recovery-armel+CODENAME.img
quantal-preinstalled-system-armel+CODENAME.img
quantal-preinstalled-armel+CODENAME.img
All Phones need this main image
quantal-preinstalled-phablet-armhf.img
* Plug in your phone and open a terminal to the folder where you saved the images. Unlock your phone if it's not already.
Code:
fastboot oem unlock
* Power your device down and enter fastboot by holding both volume buttons and the power button until the phone comes on.
* In fastboot, enter the following commands in the terminal:
Be sure to replace CODENAME with your device's code name.
Code:
fastboot flash recovery recovery-quantal-preinstalled-armel+CODENAME.img
fastboot flash system quantal-preinstalled-system-armel+CODENAME.img
fastboot flash boot quantal-preinstalled-boot-armel+CODENAME.img
* Use the volume keys to choose recovery and press the power button
* Enter the following command in the terminal:
Code:
adb sideload quantal-preinstalled-armel+CODENAME.zip
Wait for the sideload to finish.
If you see the message “fixing fs_size in crypto footer”, it’s finished.
From the main menu choose "Advanced" and "Reboot" to recovery.
When the phone has rebooted back to recovery, execute the following command in the terminal:
Code:
adb sideload quantal-preinstalled-phablet-armhf.zip”
When the sideload is finished, restart the device.
Now you're running Ubuntu.
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
TingTingin said:
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
Click to expand...
Click to collapse
There should be no reason why not (Same with Linux)
TingTingin said:
Wouldn't this also work on Windows?
PHONE SLOW CLICK ME?
_____________________________________
"If your doing the right thing then to hell with everyone else -Deadly"
Click to expand...
Click to collapse
yes. they are the same instructions on linux, mac, and windows
Pirateghost said:
yes. they are the same instructions on linux, mac, and windows
Click to expand...
Click to collapse
I did mention that
- Nexus 4 / PA 3 / Franco r83 -
Hmm... I keep getting an error when trying to load the recovery. Weird since the other 2 work. Let me check the MD5Sum. I'm on Windows.
EDIT: Fixed: I just used this link and followed the instructions here. http://liliputing.com/2013/02/how-t...h-on-a-nexus-7-with-windows-mac-or-linux.html I didn't really know what was going on with your instructions. =.3 I'm sorry.
can you show some photo for your operating...i'm very interesting..............
Thank you so much, I did it with linux. Just add a couple of things;
To fastboot mode you just need volum down botton.
I had error with adb sideload (never before flashing android roms), but I solve executing "adb usb" just before adb sideload, in both cases (maybe is a problem with the last recovery...)
I also got the error: closed message
To fix first do ADB Devices to ensure that your system in online then in the recovery screen on your device select 'INSTALL ZIP FROM SIDELOAD' and reexecute the command in terminal
how to use galaxy s3 mini ? it's not fastboot mode
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work. Some even report success after 20 tries.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in the thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Added another instructions from another forumer who think my instructions is not complete:-
1. Install the moto driver and then plug in your device while running normal
2. Run the get_code.bat (from this link)
3. once unlock.code file is created, run "adb reboot bootloader". It will show [Fastboot] with the kf logo.
4. Once bootloader comes up, change driver in device manager for "Other Android" to use the Android -> Mot Adb Composite Driver. It should say "Ready" on the KF
5. Run the stuff from this post (do the bottom steps with fastboot erase first)
6. After you are done in bulk mode, hold the power button for 15 secs to reboot. It will automatically boot into Fastboot
7. When you run the unlock command, use the "unlock.code" file.. not the "0xmmssssssss.unlock" example from that link.
8. Now unplug and hold power again to shut down. Hold VolUp + Power. About 3 secs after you see the KF logo, you can let go of the power button (possibly both buttons) and you get TWRP
From here you can flash CM and gapps (5.1).
Click to expand...
Click to collapse
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
You do not need to be on 4.5.5.2 or any specific version of FireOS for that matter. Is the device rooted?
BatmanDC said:
just wondering is it important to be on os 4.5.5.2 before rooting and unlocking boodloader? I am on OS 13.3.2.1 and I just have no idea what path to do. All I want is to not have OTA and have google play store working
Click to expand...
Click to collapse
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
kkcheong said:
As Davey said, no. The reason I created this thread because 4.5.5.2 is the last OTA. My point is even last OTA can root and unlock bootloader.
Click to expand...
Click to collapse
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
are those instructions as daunting as they sound?
it seems if you kingroot and wipe everything it negates any malware?
barrist said:
...it seems if you kingroot and wipe everything it negates any malware?
Click to expand...
Click to collapse
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Davey126 said:
Correct. KingRoot is a borderline malware but does not appear to harvest personal info during the rooting process and is completely irradiated by a wipe of the system and data partitions.
Click to expand...
Click to collapse
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
barrist said:
Thanks
just picked up a used HDX off Kijiji, so i'm looking forward to tinkering.. can you suggest an initial stable rom to try? the KK based Nexus seems to be the safer one i'm gathering?
Click to expand...
Click to collapse
There are no bad/unstable HDX ROMs. Fire Nexus has the advantage for those needed full Bluetooth and/or LTE support. Otherwise LineageOS 14.1 is a solid choice. Regardless of direction you'll want to unlock the bootloader and wipe the device immediately after rooting if KingRoot is utilized. Also know Amazon devices have their own set of quirks and don't behave like a typical Android gizmo.
Thanks maybe I'll give lineage a shot as I don't really don't need LTE or bt .. just hoping for stable app support and wifi
draxie said:
I'd like to add that you don't even need root to unlock.
Personally, I'd stay away from Kingroot, unless that was the only option.
Thankfully, it is not.
Click to expand...
Click to collapse
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
nice, instructions worked, running lineage 14.1 and no problems so far!
kkcheong said:
Thanks for the awesome info. But noob like me would prefer Kingroot because it give the illusion of zero risk :laugh:
Click to expand...
Click to collapse
No problem.
Given that you wipe 'data' (which I prefer not to, because I'm too lazy to make backups),
you should be fine with KingRoot, it just takes much longer, but that's your choice.
The real risk is making a mistake when flashing aboot and TWRP, which is the same on both paths.
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
xyluss0 said:
I tried to follow all steps but cannot go beyond Step 2c. When I try to flash cubed and aboot, i get "cannot access file : file or directory not present" error. How should I proceed?
Click to expand...
Click to collapse
Have you put both file in the adb directory?
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
xyluss0 said:
Yes I did. Also, I tried to go ahead on the next step and run unlock.bat but I got the error "incorrect unlock code".
Click to expand...
Click to collapse
Please print screen. Did you cd to ADB directory?
Root hdx 7 (3rd Gen.), FireOS 4.5.5.2 with towelroot
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Root fails
kkcheong said:
Finally I got myself to root and unlock bootloader of my Thor Kindles. I've been lurking for few years. Here is the steps:-
1. Install Kingroot from Kingroot website (https://kingroot.net/) and root the phone. I got it first try. But some people are saying they need 8 tries to work.
2. Flash TWRP and Unlock bootloaders. Instruction in https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555. Instruction in this post is better than the first post (OP) in this thread. The step is:-
a) install ADB driver and install Kindle Fire USB driver
b) put get_code.bat and unlock.bat in adb.exe directory. Put aboot and cubed twrp in /sdcard/
b) create unlock.code with get_code.bat
c) flash aboot and cubed twrp with this command in DOS command prompt in adb.exe directory:-
d) make sure check the Android ADB Composite driver is properly install in Device Manager
e) execute unlock.bat
f) reboot, press UP + power to boot into TWRP
g) wipe, then flash your ROM using adb sideload or normal flashing if you already have the rom in your device earlier. Then wipe again.
Tips:-
1. Make sure the driver is Android ADB Composite Driver is properly install or the unlock bootloader (unlock.bat) won't work
2. Installing Rom, press UP+POWER to go into TWRP, download the ROM to PC, then enable ADB side in TWRP, follow up with ADB sideload command in PC. Wipe before and after. :-
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
3. Safe Strap is not supported in 4.5.5.2
4. Copy ROM zip file to /sdcard/ before doing the above to skip the adb sideload step and you can directly flash the rom from TWRP only.
5. Can't boot into 4.5.5.2 after unlock bootloader. I've tried issuing "fastboot -i 0x1949 oem idme bootmode 4000" and then "fastboot -i 0x1949 reboot" command but it does not work.
Click to expand...
Click to collapse
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
achimbub said:
Hi,
I am wondering if the towelroot rooting process is working with the 4.5.5.2 version of the fireOS.
Do you recommend the usage of APK-versions of Kingroot or Towelroot over the use of Windowsversion esp. for Kingroot.
Do i need working internet connection during rooting process with APKs ?
Thx in advance
Achimbub
Click to expand...
Click to collapse
- TowelRoot is ineffective on FireOS v4
- recommend desktop version of KingRoot for 4.5.5.2 (still may not work)
- device does not need an active internet connection with desktop version
---------- Post added at 04:58 AM ---------- Previous post was at 04:55 AM ----------
bobcat131 said:
I am on Fire OS 4.5.5.2 (HDX 8.9 Apollo) and Kingroot can not root(both apk and windows versions). I tried both ten times. What can I do to root this device now?
Click to expand...
Click to collapse
KingOroot is the only other tool that reportedly works on 4.5.5.2. It also has a reputation for screwing up devices. Risky choice.
I don't have experience with the hardmod option, I can't downgrade the firmware because they removed Apply Update From ADB and the mtk-su method doesn't work.
I'm on Fire OS 5.6.8.0 and nothing's worked. How would I downgrade if there's no apply update via adb or is there a root method that works without hardmodding?
SamDungUser said:
I don't have experience with the hardmod option, I can't downgrade the firmware because they removed Apply Update From ADB and the mtk-su method doesn't work.
I'm on Fire OS 5.6.8.0 and nothing's worked. How would I downgrade if there's no apply update via adb or is there a root method that works without hardmodding?
Click to expand...
Click to collapse
Sorry, is not a Fire HD 8 (2016), is just a Fire HD 8 (2017)
AmznUser444 Dev said:
There's no way to do that. You have only to repurpose your Fire tablet:
Digital clock.
Digital picture frame.
Virtual MIDI keyboard.
Home automation panel.
VirtualTablet, a virtual drawing tablet.
Click to expand...
Click to collapse
Sorry I was being an idiot while posting that, I did find a solution to root and install TWRP. If anyone needs step by step instructions i'll reply to you with instructions.
SamDungUser said:
Sorry I was being an idiot while posting that, I did find a solution to root and install TWRP. If anyone needs step by step instructions i'll reply to you with instructions.
Click to expand...
Click to collapse
Instructions please!!
Pabla98 said:
Instructions please!!
Click to expand...
Click to collapse
Thank you for asking for instructions. I'm happy to help.
You will need to download these files
https://forum.xda-developers.com/attachment.php?attachmentid=4845269&stc=1&d=1571151710
https://forum.xda-developers.com/attachments/brick-douglas-zip.4825253/
You'll also need to be running Linux (not terminal emulators)
In most cases use Lubutnu 18.04
If you want to install roms it'll be in Fire HD 8 and HD 10 development with 26 threads (not the 30+ thread)
First: Download and put your files on the desktop and extract brick-douglas.
Open the folder
Go to Tools and open a terminal here.
Enter these commands first:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
Once finished reboot your device to recovery:
Erase data by selecting Wipe Data/Wipe Cache.
Await for it to complete.
Now go to reboot to bootloader and select it.
Now it shall begin.
Execute this command: sudo brick-9820.sh
Wait for it to finish and you should see:
Writing Brick on your tablet
Force it off by Pressing and holding Power + Volume UP and wait for the screen to turn black.
Disconnect the device.
Exit all windows including terminal
Now extract amonet-douglas-v1.2.zip.
Now open amonet again
Now go to Tools > Open Terminal
Now it is time to unlock the bootloader.
Type in: sudo bootrom-step.sh
Press enter
Let it flash, NOTE this will take a while! PLEASE LET IT COMPLETE OR YOU WILL BRICK YOUR DEVICE.
DO NOT LET YOUR DEVICE BOOT INTO FireOS when the process is done.
Next type in: sudo fastboot-step.sh
It will now boot into a hacked fastboot mode and begin the payload to install TWRP. Let this finish or your device maybe bricked.
Once done it will reboot into TWRP and the process is finished!
You have now exploited your device! Now you can flash Magisk to root your device!
AmznUser444 Dev said:
Sorry, is not a Fire HD 8 (2016), is just a Fire HD 8 (2017)
Click to expand...
Click to collapse
Please don't try it with the 2016 (6th gen).
SamDungUser said:
Thank you for asking for instructions. I'm happy to help.
You will need to download these files
https://forum.xda-developers.com/attachment.php?attachmentid=4845269&stc=1&d=1571151710
https://forum.xda-developers.com/attachments/brick-douglas-zip.4825253/
You'll also need to be running Linux (not terminal emulators)
In most cases use Lubutnu 18.04
If you want to install roms it'll be in Fire HD 8 and HD 10 development with 26 threads (not the 30+ thread)
First: Download and put your files on the desktop and extract brick-douglas.
Open the folder
Go to Tools and open a terminal here.
Enter these commands first:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
Once finished reboot your device to recovery:
Erase data by selecting Wipe Data/Wipe Cache.
Await for it to complete.
Now go to reboot to bootloader and select it.
Now it shall begin.
Execute this command: sudo brick-9820.sh
Wait for it to finish and you should see:
Writing Brick on your tablet
Force it off by Pressing and holding Power + Volume UP and wait for the screen to turn black.
Disconnect the device.
Exit all windows including terminal
Now extract amonet-douglas-v1.2.zip.
Now open amonet again
Now go to Tools > Open Terminal
Now it is time to unlock the bootloader.
Type in: sudo bootrom-step.sh
Press enter
Let it flash, NOTE this will take a while! PLEASE LET IT COMPLETE OR YOU WILL BRICK YOUR DEVICE.
DO NOT LET YOUR DEVICE BOOT INTO FireOS when the process is done.
Next type in: sudo fastboot-step.sh
It will now boot into a hacked fastboot mode and begin the payload to install TWRP. Let this finish or your device maybe bricked.
Once done it will reboot into TWRP and the process is finished!
You have now exploited your device! Now you can flash Magisk to root your device!
Click to expand...
Click to collapse
I need help I'm stuck at "USB Transfering..." on my device and "Sending 'brick'" on my Virtual Machine.
IsolatePlz said:
I need help I'm stuck at "USB Transfering..." on my device and "Sending 'brick'" on my Virtual Machine.
Click to expand...
Click to collapse
I found that issue too. Use brick.sh
SamDungUser said:
I found that issue too. Use brick.sh
Click to expand...
Click to collapse
I tried both I had to boot into Ubuntu off of a USB stick to root it.
IsolatePlz said:
I tried both I had to boot into Ubuntu off of a USB stick to root it.
Click to expand...
Click to collapse
Yeah. I experienced problems using virtual machines myself.
you need to brick your device , by short after thes back to stock recovery now can now downgrade
789mod said:
you need to brick your device , by short after thes back to stock recovery now can now downgrade
Click to expand...
Click to collapse
Yes, that's the hardware method that has a higher chance of working.
@SamDungUser are there any chances this trick works on Fire 7 with recent OS? Thanks
neFAST said:
@SamDungUser are there any chances this trick works on Fire 7 with recent OS? Thanks
Click to expand...
Click to collapse
Is your device the KFDOWI Douglas HD 8 2017?
My bad, I did not notice this is the HD 8 subsection. My device is a Fire 7 2019
WIll this work with the Kidle Fire 8 HD (10th Generation)? Happy to try if I can get confirmation this will work with that model...
reubendevries said:
WIll this work with the Kidle Fire 8 HD (10th Generation)? Happy to try if I can get confirmation this will work with that model...
Click to expand...
Click to collapse
NO
SamDungUser said:
Is your device the KFDOWI Douglas HD 8 2017?
Click to expand...
Click to collapse
yeaahh >>> root it from twrp just brick it
789mod said:
yeaahh >>> root it from twrp just brick it
Click to expand...
Click to collapse
Alreday rooted. I joined the Lineage os 15 beta for the HD 8 2017
I was able to root my HD 10 7th gen Suez by using these instructions https://forum.xda-developers.com/t/hd-10-2017-offline-rooting.3734860/
Now that I have a rooted device, I can't seem to figure out how to get rid of Amazon and flash a custom rom
Hello XDA,
I flashed my Fire HD 8 (2018) from FireOS to LineageOS 17 using this guide ( https://forum.xda-developers.com/t/rom-unlocked-karnak-lineage-17-1-17-july-2020.4134829/ ).
Installation went great, TWRP/LineageOS was working fine. Later as I began to setup the tablet I became unsatisfied with the ROM because the camera and proximity sensor were not working properly for me. I then decided it would be better to flash to a previous Lineage ROM to get better performace/support ( https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/ )
At this point is when things went wrong. I tried to overwrite/upgrade TWRP from within TWRP using the IMG file posted in the LineageOS 16 guide with this method - https://www.droidwin.com/update-twrp-recovery-android/ (skip to step 4)
Now whenever I try to boot into Recovery Mode all I see is the Amazon Logo, I cannot get the tablet to boot into TWRP recovery. As bad as that is I can still boot into LineageOS 17 which is a relief. I've tried doing the fastboot recovery method but I get the message "FAILED (remote: 'the command you input is restricted on locked hw')"
At this point I'm stuck and reluctant to try too much more, but I'd still like to try the LineageOS 16 ROM.
G4_PITA said:
Hello XDA,
I flashed my Fire HD 8 (2018) from FireOS to LineageOS 17 using this guide ( https://forum.xda-developers.com/t/rom-unlocked-karnak-lineage-17-1-17-july-2020.4134829/ ).
Installation went great, TWRP/LineageOS was working fine. Later as I began to setup the tablet I became unsatisfied with the ROM because the camera and proximity sensor were not working properly for me. I then decided it would be better to flash to a previous Lineage ROM to get better performace/support ( https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/ )
At this point is when things went wrong. I tried to overwrite/upgrade TWRP from within TWRP using the IMG file posted in the LineageOS 16 guide with this method - https://www.droidwin.com/update-twrp-recovery-android/ (skip to step 4)
Now whenever I try to boot into Recovery Mode all I see is the Amazon Logo, I cannot get the tablet to boot into TWRP recovery. As bad as that is I can still boot into LineageOS 17 which is a relief. I've tried doing the fastboot recovery method but I get the message "FAILED (remote: 'the command you input is restricted on locked hw')"
At this point I'm stuck and reluctant to try too much more, but I'd still like to try the LineageOS 16 ROM.
Click to expand...
Click to collapse
If you're lucky enough you might be rooted. If you are, brick the PL header with ADB (make sure your tablet can access bootrom mode) and re-run amonet.
Rortiz2 said:
If you're lucky enough you might be rooted. If you are, brick the PL header with ADB (make sure your tablet can access bootrom mode) and re-run amonet.
Click to expand...
Click to collapse
Thank you for replying....Unfortunately it looks like I'm not rooted.
I installed the "Root Chcker" app through the Play Store and when I click "verify root" it says "Sorry! Root access is not properly installed on this device".
Any advice on how best to proceed?
G4_PITA said:
Thank you for replying....Unfortunately it looks like I'm not rooted.
I installed the "Root Chcker" app through the Play Store and when I click "verify root" it says "Sorry! Root access is not properly installed on this device".
Any advice on how best to proceed?
Click to expand...
Click to collapse
Well, it's possible that you have a root shell regardless of what the root checker reports. Try running adb root and see what it returns.
Rortiz2 said:
Well, it's possible that you have a root shell regardless of what the root checker reports. Try running adb root and see what it returns.
Click to expand...
Click to collapse
When I run the command "adb root" and command line spits out "adbd is already running as root". So it looks like I'm good here...
When you say 'bootrom mode' are you talking about fastboot? I'm still able enter into fastboot mode, thats when I get the error message listed in the 1st post.
When you say 'brick the PL header with ADB' do you mean to follow this guide? - https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2018-karnak-amonet-3.3963496/
G4_PITA said:
When I run the command "adb root" and command line spits out "adbd is already running as root". So it looks like I'm good here...
When you say 'bootrom mode' are you talking about fastboot? I'm still able enter into fastboot mode, thats when I get the error message listed in the 1st post.
When you say 'brick the PL header with ADB' do you mean to follow this guide? - https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-8-2018-karnak-amonet-3.3963496/
Click to expand...
Click to collapse
bootrom is USBDL mode, the mode that is accessed when the PCB pins are shorted. Anyway, don't worry about that. Just run adb root and then ./fireos-step.sh from the thread you linked and you should be able to access TWRP again.
Rortiz2 said:
bootrom is USBDL mode, the mode that is accessed when the PCB pins are shorted. Anyway, don't worry about that. Just run adb root and then ./fireos-step.sh from the thread you linked and you should be able to access TWRP again.
Click to expand...
Click to collapse
After running 'adb root' it produces the same result as before, 'adbd is already running as root'.
When I run 'sudo ./fireos-step.sh', it then produces "functions.inc: line 39: dos2unix: command not found".
I can't find an immediate answer on how to handle this..
G4_PITA said:
After running 'adb root' it produces the same result as before, 'adbd is already running as root'.
When I run 'sudo ./fireos-step.sh', it then produces "functions.inc: line 39: dos2unix: command not found".
I can't find an immediate answer on how to handle this..
Click to expand...
Click to collapse
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Rortiz2 said:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Click to expand...
Click to collapse
Thank you for the help, that worked.
I'm now having a different issue when running "./fireos-step.sh'". The result it produces is "This is only for the "karnak" - Amazon Fire HD 8 (2018 / 8th gen) - , your device is a "lineage_karnak".
I'm not sure where to find the correct file for "lineage_karnak".
G4_PITA said:
Thank you for the help, that worked.
I'm now having a different issue when running "./fireos-step.sh'". The result it produces is "This is only for the "karnak" - Amazon Fire HD 8 (2018 / 8th gen) - , your device is a "lineage_karnak".
I'm not sure where to find the correct file for "lineage_karnak".
Click to expand...
Click to collapse
Open fireos-step.sh with a text editor and remove the following line:
Code:
check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) - "
Rortiz2 said:
Open fireos-step.sh with a text editor and remove the following line:
Code:
check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) - "
Click to expand...
Click to collapse
I removed "check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) -"" from fireos-step.sh and now I'm getting a root access error shown below
Code:
Testing root access...
/system/bin/sh: su: inaccessible or not found
Trying to use mtk-su to get temp root...
No mtk-su found, you can get it here: https://forum.xda-developers.com/hd8-hd10/orig-development/experimental-software-root-hd-8-hd-10-t3904595
I then downloaded mtk-su and placed it into the working directory hoping it could find the file by itself but that didn't work unfortunately. I thought I had root access already, not sure why it's producing this error.
Rortiz2 said:
Open fireos-step.sh with a text editor and remove the following line:
Code:
check_device "karnak" " - Amazon Fire HD 8 (2018 / 8th gen) - "
Click to expand...
Click to collapse
So I removed the "get root" line from fireos-step.sh and it produces the following result -
Code:
* daemon not running; starting now at tcp:5037
* daemon started successfully
PL version: 5 (5)
LK version: 1 (1)
TZ version: 258 (258)
Flashing PL
bin/preloader.bin: 1 file pushed. 4.5 MB/s (142928 bytes in 0.030s)
/system/bin/sh: su: inaccessible or not found
According to these results It looks I'm not rooted. If this is true why when I run 'adb root' it returns 'adbd is already running as root'?
ttt...still no solution. If anyone can offer some good advice I'd be greatful. Thanks
G4_PITA said:
ttt...still no solution. If anyone can offer some good advice I'd be greatful. Thanks
Click to expand...
Click to collapse
Two things you can do/try...
First one is to use the boot-fastboot script out of the amonet folder, in order to boot into hacked fastboot mode. Just run the boot-fastboot script with sudo and connect the tablet (powered off). Then run fastboot devices, if your device is there. If yes, you can run the fastboot-step if you like, which will flash the old TWRP image. Maybe thats enough to boot into TWRP.
In case that won't help, you can also use hacked fastboot to brick the preloader (like @Rortiz2 suggested), to get into bootrom mode, which will prevent you from open-up the tablet. Follow #2 from the unbrick thread, i.e. unbrick with shorting. You can also use the same guide and use the 'open-up the tablet' thing, to short the special point and re-run amonet from scratch. Good luck.
Sus_i said:
Two things you can do/try...
First one is to use the boot-fastboot script out of the amonet folder, in order to boot into hacked fastboot mode. Just run the boot-fastboot script with sudo and connect the tablet (powered off). Then run fastboot devices, if your device is there. If yes, you can run the fastboot-step if you like, which will flash the old TWRP image. Maybe thats enough to boot into TWRP.
In case that won't help, you can also use hacked fastboot to brick the preloader (like @Rortiz2 suggested), to get into bootrom mode, which will prevent you from open-up the tablet. Follow #2 from the unbrick thread, i.e. unbrick with shorting. You can also use the same guide and use the 'open-up the tablet' thing, to short the special point and re-run amonet from scratch. Good luck.
Click to expand...
Click to collapse
Thanks for your help, when I get a chance I'll try this and report the results.
Sus_i said:
Two things you can do/try...
First one is to use the boot-fastboot script out of the amonet folder, in order to boot into hacked fastboot mode. Just run the boot-fastboot script with sudo and connect the tablet (powered off). Then run fastboot devices, if your device is there. If yes, you can run the fastboot-step if you like, which will flash the old TWRP image. Maybe thats enough to boot into TWRP.
In case that won't help, you can also use hacked fastboot to brick the preloader (like @Rortiz2 suggested), to get into bootrom mode, which will prevent you from open-up the tablet. Follow #2 from the unbrick thread, i.e. unbrick with shorting. You can also use the same guide and use the 'open-up the tablet' thing, to short the special point and re-run amonet from scratch. Good luck.
Click to expand...
Click to collapse
Finally got TWRP back!! The solution was so intuitive I feel ridiculous for not trying it first.
So I took the advice of Sus_i and ran the two files out of the karnak's amonet folder; bootrom-step.sh & fastboot-step.sh. This is exactly what I did initially to root the tablet and install LineageOS in the first place!! I posted a link to the solution in the first post of this thread!! For anyone wanting more info on the steps I took there's a video tutorial which shows what's required to get TWRP working again -
This video tutorial also shows how to install LineageOS onto a Fire HD 8 Tablet. I overwrote LineageOS 17 with LineageOS 16 Karnak. The camera is working in this version of Lineage but the proximity sensor is still lacking.
A big THANK YOU to users - Sus_i & Rortiz2 for helping me out, I'm very thankful for your knowledge and generosity.