Database Users

[GUIDE] Install NvFlash Flatline (become unbrickable!!)

This Optimized Guide is for NvFlash Flatline only! That is for stock Android Versions: 10.6.1.15.3 - 10.6.1.27.5.
According to this post and this post, it works with the tf300tg as well. Bootloader: 10.6.2.11
Original Thread: http://forum.xda-developers.com/showthread.php?t=2455922
Why install NvFlash?
rayman said:
The AndroidRoot.Mobi Team is proud to present Flatline: Nvflash for TF300T Jellybean!
This release allows generating nvflash blobs for your specific device, making your device unbrickable as long as you have a copy of the blobs.
As a brand new feature, it will also enable wifi and upload a copy of the blob to androidroot's server. Later, a solution will be released to retrieve the blobs from the server if you ever loose them.
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Credit goes to the AndroidRoot.Mobi team:
Bumble-Bee (Apache14), IEF, kmdm, lilstevie & RaYmAn.
Click to expand...
Click to collapse
You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
Guide:
1) Download files
NvFlash for windows.
and the TF300 image, which is a custom recovery for the purpose of flashing the AndroidRoot Bootloader.
Place image in ADB folder, and rename it to: flatline_device.img
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power and vol down button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6) Reboot into recovery which should be CWM at this point. Go Advanced -> Wheelie. Accept the warning.
step 1) Flash AndroidRoot BL
The device will shut down, reboot into Android. Then reboot back into recovery.
step 2) Once back in recovery select go to Advanced ->:”Generate wheelie blobs” Be patient here too.
They can be found in the device at /data/media/AndroidRoot" or /tmp/AndroidRoot
You can use ADB to get them:
Code:
adb pull /data/media/AndroidRoot
or
Code:
adb pull /tmp/AndroidRoot
Alternatively, you can use a root file explorer such as ES File Manager. Be sure to copy all of the files out of the directory. Make sure you have root access before you try to search for the files.
Keep this file safe in multiple places.
7)The next section (Accessing NVFlash) is for creating more essential backups with NVFlash.
step 1) Hold down the volume up key while rebooting and the tablet is plugged in via USB. (This may take a few tries to get into APX mode). If you are successful, the screen will be blank and the device name on the computer will be something along the lines of "NVIDIA APX"
step 2) Take the NvFlash tools zip and extract them to a folder. Shift right click in that folder and select "Open Command window here".
step 3) Copy the blob.bin from the Step # 7 above into the NvFlash folder.
step 4) run the command:
Code:
wheelie --blob blob.bin
8) Next we run some commands to get even more backup files. These should all be run from the same command window in the previous step.
Code:
nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Code:
nvflash --resume --read 14 factory-config.img
Code:
nvflash --resume --read 7 unlock-token.img
These files will be stored in C:\User\AppData\Local\VirtualStore (on the computer)
If they are not there, run a search on your computer for
Code:
*img
9.) Flash any other recovery you want, including TWRP. Be sure it is the correct version for your bootloader.
10.) Store ALL of the img files AND the blob.bin AND all other files in the folder in multiple safe places (email, dropbox, HDD, flash drive, SD card, tape backup, or your favorite plant etc.)
11.) Enjoy the peace of mind that you can now restore your device if you brick it
Hit that thanks button if I helped and also thanks to @bucket81 and of course AndroidRoot.mobi devs @rayman

Recovery
For recovery from a brick when you have already made your NvFlash backups, look here:
As @ebildude123 pointed out, first try
Code:
nvflash -r --download 5 twrp.blob
where the output should be:
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
ebildude123 said:
Then the device proceeded to reboot into android
Click to expand...
Click to collapse
If that does not work, try using the method here:
http://forum.xda-developers.com/showthread.php?t=2590450
Thanks to @lj50036 and @bucket81

Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.

nadorf said:
Hello guys! This nvflash does it work in the Memopad 301T or only TF300T? Both tab works for Tegra 3.
Click to expand...
Click to collapse
If you can flash a Tf300t version of CWM recovery to your ME301 then it could work. I dont have a 301, so i cant test it but i dont think it will because this is bootloader specific and the me301 does not have the same bootloader.

Does this work with TF300TG\L?

spider623 said:
Does this work with TF300TG\L?
Click to expand...
Click to collapse
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.

cmendonc2 said:
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
adb devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery flatline_device.img -i 0x0b05
Blue bar on device will fill. Be patient.
Click to expand...
Click to collapse
Think you mean fastboot devices not adb devices

cmendonc2 said:
Im not sure if you can flash a tf300t recovery on a TG or L. If you can, then it should work fine, but if you have to use a separate recovery, then this may not be compatible. You could try modding a tf300tg CWM with the NVflash scripts though, but dont expect any support.
Click to expand...
Click to collapse
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk

spider623 said:
It is for twrp but no idea for cwm
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,

cmendonc2 said:
You could use WinRar to extract the NvFlash scripts from the tf300t image version but i dont really know how you would implement those then,
Click to expand...
Click to collapse
No need, they are the same, only difference is one file that you can put in any rom before flashing to her the radio to work, same for the TL
Sent from my Nexus 4 using Tapatalk

Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?

cravinRiboflavin said:
Just wondering, if I made the blobs for preJB, then upgraded to JB (so now I'm on JB bootloader), should I bother using Flatline? or will my preJB blobs be ok (and make me unbrickable)?
Click to expand...
Click to collapse
Well, when you restore, you restore back to ICS bootloader so you will have to reflash the stock JB zips first. I don't think its worth the hassle if you already have them.

Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot

BrakeZ said:
Hey guys, I want to get some custom ROM to my TFT300. But first I want install this NvFlash Flatline, if anything goes wrong.
But now I´m looking that my android version is already 10.6.1.27.5.-20130902.
But you say in the first post that the Flatline is only for 10.6.1.15.3 - 10.6.1.27.1.
So is it a problem or it should be working anyway?
Thanks a lot
Click to expand...
Click to collapse
Since it is also the latest 4.2 bootloader, it should work fine.

cmendonc2 said:
Since it is also the latest 4.2 bootloader, it should work fine.
Click to expand...
Click to collapse
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.

Matatusku said:
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
Installing CM does not change your bootloader, so if you were running the latest Asus firmware before, you should be fine.
To make sure, you can check the bootloader version on the top-left of the bootloader screen.
Sent from my TF300T using Tapatalk

Matatusku said:
I had 10.6.1.27.5 on my device before i upgraded it to CM11 with Grimlock kernel. I did it with the tool for idiots in a hurry so i did not remember to do this but one guy at Q & A section said this should be easy to do even i have CM11. I am kind of new with these tablets and android so i dont know very much but does that work exactly same way even i have CM11 that i would have Stock rom with 10.6.1.27.5 or is the bootloader changed in the CM11? I have Scanno TWRP. As i said i am very confused about these names and dont know very much but little guidance would be a great help.
I can read the guides and do as they told but im just too scared to do that when i am not 100% sure that everything is compatible and that bootloader thing is very strange because i dont know what bootloader i have in CM11.
Click to expand...
Click to collapse
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.

cmendonc2 said:
No, the bootloader does not change when you flash ROMs. So, you still have the 10.6.1.27.5 bootloader installed on your tablet. When you run the guide, the TWRP you have by scanno will be overwritten and you will have to flash it again at the end once you have made the backups.
Click to expand...
Click to collapse
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)

aminpro715 said:
Would this method work for 10.6.1.14.10? Because I see that this is the latest one and I can't get above that version at this time. Not even on the official site. (TF700T)
Click to expand...
Click to collapse
Well I'm not experienced with tf700t bootloaders, but it says that it is compatible with bootloader version 10.6.1.14.4. That may be the same as 10.6.1.14.10 but you will have to check in the tf700 forum.

Does not work for me in step 4!
hello
I have followed your tutorial on my Asus TF300T Android 4.2.1 build 10.6.1.27.5.
I installed ADB Fastboot, placed flatline_device.img file in the ADB folder.
When I get to step 4 the fastboot devices command displays the serial number of my tablet but the command to flash the image file does nothing !...
My question is: Should the tablet be rooted for this manipulation? or it could be something else?
Thank you for your help

fastboot oem unlock: 'fastboot' is not recognized as an internal or external command

, operable program or batch file.
(update: I'm trying to find a tegra note root guide but I think I'm going to die of old age before I find one that explains the actual steps for 1. finding the tegra note windows drivers 2. how to install them every step explained 3. every step explained how to root this tablet oh god why did I not buy a windows tablet this time ok)
http://forum.xda-developers.com/showthread.php?t=2586432
I tried towelroot but it doesn't do anything after 15 seconds.

You either need to install Fastboot and ADB look in dev are for links or your not in the directory where the adb and fastboot executables are.
This is why your getting this error. Also i have tried towelroot and it froze my tegranote right out i have to reflash the device again to get it working or more over just the /System partition.
If you have gone though the OTA updates and have hit past 4.3 then you can simply use the SuperTool to restore your tablet which has everything in there for you including the fastboot and adb.
Just make sure you wasn't on 4.2.2 before using this methord.
Also you haven't said which brand of tablet you have either.
By looks of the link you posted your after installing root via either CWM or TWRP (I suggest using TWRP!)
if thats the case.
Install fastboot and adb files some where and also the recovery image of choice then do the fastboot flash recovery (name of recovery .img file ) then download the SuperSU zip and flash that in your chosen recovery you will then be rooted!.

kingroot v3.5 or older
If you want to root without PC on TN7 use kingroot and if you having trouble installing fastboot send me an email

[RECOVERY][YotaPhone2][Lollipop][ROOT]Modified YotaPhone 2 Stock Recovery for ROOT

YotaPhone 2 ROOT with modified stock recovery​
NOTE:
Check out the more functional TWRP recovery for YotaPhone 2.
Since not much dev work is happening on the YotaPhone 2, I though I'd kick off by publishing a recovery image that will hopefully allow you to root your YotaPhone 2 device with lollipop, and e.g. make partition backups.
First off: Disclaimer!
I am not responsible for damaged or bricked devices. If you follow instructions in this post, then YOU are making the choice to tinker with your device, and you are likely to void your warranty by doing so. You might even damage or brick your device, so ask yourself if the benefits outweigh the risks, because after proceeding you are pretty much on your own.
What is it?
It's a slightly modified stock recovery that allows to install packages signed with testkeys, plus adb root access and busybox for e.g. shell. That's it.
What can you do with it?
- adb root & shell access (e.g. to manually backup partitions or modify system files)
- install update zips signed with testkeys (e.g. SuperSU) in addition to original Yota Devices software
- root your device
What can it NOT do?
- probably can NOT install unsigned zips (must be signed by YD (like fota update zips), OR signed with standard testkeys)
- no fancy features, just boring AOSP stock recovery as included in stock firmware
- installing of apks/zips only through adb sideload, not from (emulated) SD card
What do you need?
- YotaPhone 2 (YD201) with Lollipop 5.0, I used firmware 1.39 YMMV with other versions
- Some technical confidence
- USB cable with a PC or laptop on one end
Steps overview:
1) First read the whole post to understand what's going to happen
2) backup (sync stuff, copy photos off, use a backup app etc, use search if unsure how to)
3) Unlock the bootloader
4) Install adb and fastboot if not yet installed. (For Windows look e.g. here, for linux the fastest is probably to install Android SDK with platform tools, see here If this is not enough info to get you started, please use xda search!)
5) Download recovery image: yd201_reco_139_testkeys_v01.img
6) boot the recovery image
7) root the device by sideloading SuperSU,
Unlocking bootloader:
Warning 1: It is currently not known how to re-lock the bootloader. (fastboot oem lock just hangs). This means you cannot completely undo the next step as of yet. This might have consequences for sending the device in for repairs, if they check for this, and deem it a (warranty) problem.
Warning 2: on some devices unlocking the bootloader wipes the device clean to factory defaults. I didn't see this happening on my YD201, but be warned, backup first!
On Linux:
Code:
sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s
On Windows:
Code:
C:\android-sdk-windows\platform-tools>fastboot oem unlock
...
OKAY [ 0.002s]
finished. total time: 0.002s
Maybe Windows will install some extra drivers in the process.
BOOT the recovery image:
a) First: put the device in fastboot/download mode:
method 1: Power off with USB cable disconnected, then hold volume down key while inserting USB cable (which should already be in your PC on the other end).
method 2: do a
Code:
adb reboot bootloader
You should see a black screen with a tiny white: downloading...
b) boot the recovery image:
On linux:
Code:
sdk/platform-tools$ sudo ./fastboot devices
Should show a connected device in fastboot mode, then proceed:
Code:
sdk/platform-tools$ sudo ./fastboot boot <path>/<to>/yd201_reco_139_testkeys_v01.img
Where <path>/<to>/yd201_reco_139_testkeys_v01.img is the path you downloaded the image file to (e.g. ~/Download/yd201_reco_139_testkeys_v01.img)
On Windows:
copy the yd201_reco_139_testkeys_v01.img file to the folder with fastboot.exe (here assuming C:\android-sdk-windows\platform-tools, and D:\downloads as download location for the img)
* snippet below is fabricated, but you get the idea
Code:
D:\>C:
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>fastboot.exe devices
Should show a connected device in fastboot mode, then proceed:
Code:
C:\android-sdk-windows\platform-tools>copy D:\downloads\yd201_reco_139_testkeys_v01.img . [i]note the dot at the end[/i
C:\android-sdk-windows\platform-tools>fastboot.exe boot yd201_reco_139_testkeys_v01.img
Hopefully you see the screen go completely black after a few seconds, and recovery menu will appear. Like stock recovery, it will show an error (E:Cannot load volume /misc) but you can ignore that, along with the 'error' triangle icon that goes with it.
If booting fails with a signature error, the bootloader is probably not properly unlocked, try again.
Note that this recovery image could be flashed too (I haven't actually tried to flash yet), but if you're cautious (as we are in this post) you can just boot it every time you need it.
SuperSU flashing:
1) download Chainfire's SuperSU flashable zip from this page, filename is:UPDATE-SuperSU-v2.46.zip
2) Assuming you're still in custom recovery, otherwise boot into custom recovery again as outlined above
3) choose "apply update from ADB" from the menu (choose with volume up/down keys, confirm with power key). Recovery now waits for a file.
4) on the connected PC:
on Linux:
Code:
sdk/platform-tools$ adb sideload <path>/<to>/UPDATE-SuperSU-v2.46.zip
on Windows:
Code:
D:\>C:
C:\>cd C:\android-sdk-windows\platform-tools
C:\android-sdk-windows\platform-tools>copy D:\downloads\UPDATE-SuperSU-v2.46.zip .
C:\android-sdk-windows\platform-tools>adb.exe sideload UPDATE-SuperSU-v2.46.zip
5) on the phone you should see SuperSU installing.
6) reboot when done
7) if SuperSU app is not visible in launcher, download & install SuperSU from playstore.
To verify if rooting worked, start SuperSU. If that looks OK, start an app that requires root (like e.g. betterbatterystats) or use a simple checkroot app from the store. Reboot and check again if it persisted.
NOTE: you could also FLASH this image, replacing the stock recovery on the recovery partition permanently (until you flash again). Above we're just BOOTing it once, next time entering recovery in the standard way will just load the stock recovery from the recovery partition). You would use fastboot flash instead of fastboot boot above. Flashing is UNTESTED.
Problems & FAQ
Q: It doesn't work!!1!
A: Please provide plenty of detail about error messages, which step, what versions etc. Without providing any detail you'll look silly.
Q: I don't know how to <backup/adb/download/reboot/flash>
A: Please use the search button, xda forums have lots of info
Q: How can I tell if I'm in stock recovery or modded stock recovery? They look the same!
A: The Droid error icon with the triangle in the centre of the modded recovery screen has some white text (yd201_cr0.1), the stock one doesn't.
Future development
I hope that there are some devs out there willing to work on the YotaPhone 2 in the near future. I'll try to tinker a bit every now and then, but I cannot promise anything as I'm no expert. To enable proper development of custom ROMs and better recoveries (e.g. TWRP) it would be great if Yota Devices released their Kernel sourcecode for the kernel they use in their YotaPhone 2 ROMs. I know they have been asked to release sources before (and they should in order to comply with the GPL license), but so far without response.
Good news is that You Can Help! Please stimulate Yota to publish Kernel sourcecode for YotaPhone 2 through their support page (hint: choose 'sales' as category, otherwise you'll have to enter lots of details. Be polite!).
Info::
Mod by: SteadyQuad
Version: 0.1 based on YD stock recovery 5.0 1.39 EU
Thanks to: Yota Devices for a great device, Jeopardy for testing and suggestions, Chainfire for SuperSU
Created: 2015-06-10
Last Updated: 2015-06-20 (added warning about current inability to re-lock bootloader)

As SteadyQuad already mentioned, I can confirm that this method works.
Bye bye Google Newsstand! Goodbye Google Books!
(When uninstalling system apps Lollipop handles a bit differently from Kitkat, and I had to always restart the device after deleting.)
Thank you very much for your effort SteadyQuad.

Allelujah!
Thanks SteadyQuad for this great job! It works like a charm!
:good:
Anybody tried to install xposed module on rooted Yotaphone2? (alpha 4 modules)?
I think it little bit risky that's why I'm asking...
Or maybe somebody know how to make a full backup Yotaphone (like in CWM)?
Thanks in advance again for a really great job!

zencooler said:
Allelujah!
Thanks SteadyQuad for this great job! It works like a charm!
:good:
Anybody tried to install xposed module on rooted Yotaphone2? (alpha 4 modules)?
I think it little bit risky that's why I'm asking...
Or maybe somebody know how to make a full backup Yotaphone (like in CWM)?
Thanks in advance again for a really great job!
Click to expand...
Click to collapse
I haven't tried testing xposed yet, but am planning to sooner or later.
Running that custom recovery we do have root level access to everything, so it should be possible to create a backup from there with the help of a computer. Have to look into this.

the recovery download doesn't work.
EDIT : it worked on laptop
How about somebody can compile a TWRP recovery because Yotaphone has posted there SDK ?
So we can make Nandroid backup.

a question : if you can modify stock recovery,
can't you compile from TWRP source and yotaphone SDK a TWRP recovery for the yotaphone 2 users ?
just my 2 cents, i evenly willing to pay for it

Gojira-r32 said:
a question : if you can modify stock recovery,
can't you compile from TWRP source and yotaphone SDK a TWRP recovery for the yotaphone 2 users ?
just my 2 cents, i evenly willing to pay for it
Click to expand...
Click to collapse
I think if we all contribute to twrp and request them they might make us one
Sent from my YD201 using Tapatalk

Can the bootloader be re locked And can the root be removed for warranty purposes
Sent from my YD201 using Tapatalk

Yes
Fastboot oem lock

Gojira-r32 said:
Yes
Fastboot oem lock
Click to expand...
Click to collapse
If the recovery image is modified don't we flash back to stock before oem lock
Sent from my YD201 using Tapatalk

Good work. A pity Xposed framework isn't compatible yet.
Sent from my YD201 using XDA Free mobile app

dai75 said:
Good work. A pity Xposed framework isn't compatible yet.
Sent from my YD201 using XDA Free mobile app
Click to expand...
Click to collapse
Xposed framework isn't FULLY compatible, but many features already work. See SteadyQuad's thread here

adamo86 said:
Can the bootloader be re locked And can the root be removed for warranty purposes
Sent from my YD201 using Tapatalk
Click to expand...
Click to collapse
I haven't been able to re-lock it when I last tried (fastboot oem lock just hung). If anyone did succeed to lock, let us know! (Gojira-r32: did you actually execute the fastboot oem lock?)

I also failed to lock it back . I wanted to install the new update 1.44 that arrive in France but it failed at the recovery stage. E:Error in cache/update/yota....zip (status 7)
I did a wipe cache partition but not a wipe data as I don't want to lose all my settings. Anyone achieved to install the new Yota update version? And then root?

I just updated to latest update in UK. But I tried Kingo no success still.
Sent from my YD201 using Tapatalk

and the first post with flashing S%U tru modified recovery ?
is this firmware somewhere to download?
still not yet on yota FTP

Has anyone the stock recovery image? Maybe I'll achieve to get the OTA update after unrooting my YD201 with the original stock recovery firmware.

i am doing that right now, unroot, flash stock recovery, i have the OTA 1.1.44 pulled out of phone after download and will try to flash it

stock recovery, boot, sustem img, unrooted, everything tried
also got other build, fixed that.
now yotaphone is completly stock and get :
error in update zip "status 7"
so i think this update is no good, some faults in it, that's why we can't flash it yet, also chaged some things in OTA and resigned it etc... no good

Gojira-r32 said:
stock recovery, boot, sustem img, unrooted, everything tried
also got other build, fixed that.
now yotaphone is completly stock and get :
error in update zip "status 7"
so i think this update is no good, some faults in it, that's why we can't flash it yet, also chaged some things in OTA and resigned it etc... no good
Click to expand...
Click to collapse
Did you try to flash the OTA update via adb sideload in the modified recovery? I'm having the same problem.
Edit: I just tried to flash the update via adb sideload - no joy. I got the following error:
Package expects build fingerprint of YotaPhone/yotaphone2/yotaphone2:5.0/LRX21M/5.0.0-EU1.1.39:user/release-keys or Yotaphone/yotaphone2/yotaphone2:5.0/LRX21M/5.0.0-EU1.1.44:user/release-keys; this device has Yotaphone/yotaphone2/yotaphone:5.0/LRX21M/5.0
E:Error in /sideload/package.zip
(Status 7)
I also tried resigning the package with testkeys, but that didn't work either. Same error. So something has changed in the rooting process, because some people in the forum have managed to update normally, presumably on their nonrooted devices.

Thor & 4.5.5.2 : Easy to root and Unlock Bootloader

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.

(Solved) TWRP Recovery mess

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.