Database Develop

[GUIDE] How to get root on the 10.1v

BEFORE YOU BEGIN
As always, mucking with your device at this level is risky. If you follow this process, you do so entirely at your own risk. I accept no responsibility for any detrimental effects resulting from following this process, or for any problems associated with the updated files. Only if you accept these risks should you use these instructions.
PREREQUISITES
Unlocked bootloader (see my guide to do this)
Working fastboot (also see my guide )
Patience
NOTES
I developed and followed this process on Ubuntu Natty, 64bit. I see no reason why it should not work on any other platform, since the only tool used is fastboot and the syntax for fastboot is the same on any platform. if you need to know how to get fastboot working, there are already many guides for that (see my how to unlock your bootloader thread, for example)
BUTTON CONFUSION
When in landscape mode, with the camera at the top, the power button is on the left 'vertical' side of the tab. On the top is the volume rocker. In this orientation:
- The LEFT side of the volume rocker is VOLUME DOWN
- The RIGHT side of the volume rocker is VOLUME UP
This might seem obvious, but to anyone who is used to phones, this is the opposite, since they were designed to be used in Portrait mode.
PREPARE
1) With your Tab in fastboot mode (step 1 of "GETTING ROOT" below), make sure you have a working fastboot implementation:
Code:
fastboot devices
If all is well, you should see your device serial number. If there is a problem, you won't get any response.
2) Downlad View attachment skitzandroid-10-1v-root_0.2.zip and View attachment skitzandroid-stock-recovery.zip
3) Create a folder on your desktop called "root"
Code:
mkdir ~/Desktop/root
for Ubuntu or
Code:
md %userprofile%\desktop\root
for Windows
This will be referred to as the working directory throughout the rest of this guide
4) Copy skitzandroid-10-1v-root.zip to your working directory (DO NOT UNZIP!)
5) Extract the skitzandroid-recovery.img file from skitzandroid-stock-recovery.zip to your working folder. Your working folder should now have 1 IMG file and one ZIP file.
6) This was an afterthought - Make sure fastboot is somewhere in your path (ie can be executed from anywhere). To test, 'cd' to any random folder and type 'fastboot' and make sure it runs.
7) Copy the skitzandroid-10-1v-root.zip file to the root of your sdcard. You can eithe drag/drop, or run:
Code:
adb push skitzandroid-10-1v-root.zip /sdcard/
from your working directory
...now the easy part
GETTING ROOT
1) Power off your Tab and power it back on, while holding the VOLUME DOWN button.
2) When the DOWNLOAD / FASTBOOT icons appear, press VOLUME DOWN again to select FASTBOOT icon (the one with the USB logo) and press VOLUME UP to confirm selection.
3) Confirm you are now in fastboot mode and do a:
Code:
fastboot devices
If all is well, you should see your device serial number.
4) Open a terminal / CMD prompt and CD to your working folder
Code:
cd ~/Desktop/root
for Ubuntu or
Code:
cd %userprofile%\desktop\root
for Windows
5) Run the following command:
Temp Root:
Code:
fastboot boot skitzandroid-recovery.img
..and wait. It might not look like anything is happening but it is.
Permanent Root:
Code:
fastboot flash recovery skitzandroid-recovery.img
6) You should now have a recovery menu. Use the volume rocker (up/down navigates menu options) to select "Install zip from SDCARD" (or something like that - if someone can post the exact menu item wording, I will update the guide). Press (tap!) the POWER button to confirm the menu selection
7) Navigate to the root of your internal storage (/sdcard), select the skitzandroid-10-1v-root.zip file and press (tap!) the POWER button to confirm selection.
8) Once complete, use the Volume rocker to select "REBOOT" from the menu and press (tap!!!) the POWER button to confirm selection.
9) You're done! Press the thanks button on this thread to continue
TESTING
1) Once your Tab boots up, check your apps menu to confirm the existence of SuperUser app.
2) With the Tab attached to your PC via USB cable, do the following:
Code:
adb shell
su
..and watch the screen on your Tab for a SuperUser prompt. If you see this, congratulations!
If you have never rooted a phone/tablet before, go get Titanium Backup Pro and ROM Manager from the market. As soon as the custom ROMs start flowing in, you'll be all set to go.
Edit: How about thanking smaskell who was very patient and persistent in dumping the image from his Google IO 10.1 - for the good of his fellow XDA members. Without his help, this would not be possible.

Note that the above process doesn't flash the recovery, just loads it.
If you want to flash the recovery permanently, all you need to do is follow the guide above and then, in step 5, use this command instead:
Code:
fastboot flash recovery skitzandroid-recovery.img
You will then have a permanent recovery which you can get to by doing:
Code:
adb shell
su
reboot recovery
at any time.
Note that doing just
adb reboot recovery
Click to expand...
Click to collapse
...for some bizarre reason does not boot to recovery. Open up a shell first, as shown above.
I will also give you credit in the guide for having "Balls of Steel" to steal a phrase from PaulObrien
EDIT:
...and the Balls of Steel award goes to *drumroll*
Egan
...for having the balls to flash the recovery. Thanks egan. If I was in a battle, I'd definitely want you in our squad

FAQ
Does it need unlocked bootloader? Yes, see my other guide for this.
Do I need to wipe, or will it wipe my device? No and No.
Can I return my device to factory default config? Yes. This process does not flash the partition unless you follow the process in post 2 which is optional.
Changelog
0.2 - Added busybox (can be flashed over the top of 0.1 without wipe)
0.1 - Initial Relase
Factory Voda Tab Images
Recovery
Boot
System

Awesome news! Thanks to everyone who worked on this - I can't wait!

Great, great job you guys! This thing needs root so it can grow

Thanks a lot bcmobile and smaskell! Ill give it a go around launch.
Sent from my LG-P990 using XDA Premium App

Thank you guys, it's working great on my 10.1v

I'm pretty sure I know the answer to this already - but is there anyway of getting temp root on these devices so I can backup all my apps and data (properly) before unlocking / flashing recovery / rooting??

This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition

Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..

gjroeleveld said:
Thanks a lot. Works like a charm
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Would this be enough to have a proper "original" image? (With the small addition of root offcourse)
(Did a dd of dd if=/dev/block/mmcblk0p1 of=/sdcard/efs.img too, just to have a backup
Will see if I can make a full nandroid back-up now
Before flashing any recovery images etc..
Click to expand...
Click to collapse
That's all the backup I have done so I hope so
Just uploading a new version of the update zip (v0.2) which includes busybox

bcmobile said:
This wont make any changes to the partitions. You could undo the whole process by just deleting a few files.
The process in my second post would actually flash the image, and would be permanent if you had no 'factory' recovery image to flash back.
The 'standard' process in post 1 is normally used for testing and doesn't overwrite the recovery partition
Click to expand...
Click to collapse
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..

gjroeleveld said:
Now to make a full "original" fastboot flashable restore fileset:
Boot: dd if=/dev/block/mmcblk0p5 of=/sdcard/boot.img
System: dd if=/dev/block/mmcblk0p4 of=/sdcard/system.img
Click to expand...
Click to collapse
Sorry for the ignorance, but are these fastboot or a adb commands?

Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Regards
EDIT:
black beard said:
Sorry for the ignorance, but are these fastboot or a adb commands?
Click to expand...
Click to collapse
These are adb commands you need to do with su!

black beard said:
Sorry, I realise that applying the root won't wipe anything, but unlocking the bootloader comes with a nice factory reset if I'm not mistaken..
Click to expand...
Click to collapse
That is part of the recovery image, not the unlocked bootloader.
You can always put back a stock image using fastboot which is one of the really nice things about fastboot unlocking vs bootloader exploits. "fastboot oem unlock" can then be undone by "fastboot oem lock" and nobody would know the diff.

seraphimserapis said:
Good work!
You should mention that you can't unlock and flash the Root-Update in one step.
The recovery complains then that /data/media is missing
Click to expand...
Click to collapse
Thanks!
Yeah, oem unlock doesn't actually do anything until the next boot

Egan said:
Thanks a lot bcmobile and smaskell! Ill give it a go around lunch.
Sent from my LG-P990 using XDA Premium App
Click to expand...
Click to collapse
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .

Egan said:
Works like a charm! Now lets backup the original recovery and then flash the stock recovery .
Click to expand...
Click to collapse
Are you going to flash it?
You will earn the official "Balls of steel" badge

Thanks,
Also remember to enable USB debugging after you have done the unlocked bootloader, took me 5 min to to realize why adb did not want to work, 5 scary min after the reboot.

I've tried to make a proper nandroid backup but haven't been able too.
Tried with romdump 0.72 but that crashes :-(
Most tutorials use Rom Manager, but that needs some work from @koush before we can use it.
I'll google on
Sent from my GT-I9000 using XDA Premium App

[BOOTLOADER] 2nd-Bootloader/Recovery unlock process for KFire 2 [TWRP 2.6.3.0]

Introducing: Kindle Fire 2nd-bootloader + TWRP 2.6.3.0 for the Kindle Fire 2nd GEN
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
*** READ CAREFULLY BEFORE DOING ANYTHING ***
*** Kindle Fire 1st-gen ROMs/KERNELS are *NOT* compatible with the Kindle Fire 2. Please only flash ROMs/KERNELS that are made for the Kindle Fire 2. ***
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T FIND THE ANSWER **
** WHEN MOVING FROM AMAZON OS TO CM10.1 IN TWRP: "WIPE" -> "SYSTEM" AND "FACTORY RESET" TO CLEAR SYSTEM/DATA/CACHE. YOUR APPS FROM AMAZON ICS AREN'T COMPATIBLE. IF NOT YOU'LL LOOP ON THE CM10.1 BOOT ANIMATION **
[03/27] NEW support thread for OFFICIAL CM on the Otter2 (Kindle Fire 2):
http://forum.xda-developers.com/showthread.php?t=2209995
** YOU SHOULD HAVE A WORKING FASTBOOT CABLE + FASTBOOT DRIVERS/ACCESS ON YOUR PC. **
Q: How do I know if my fastboot works?
A: Plug the cable into your device and then the computer. Reboot the Kindle. It *SHOULD* show a Fastboot screen. Once at the screen use this command on your computer:
fastboot -i 0x1949 devices
You should see something like this:
0123456789ABCDEF
Here's 1 website you can purchase a FASTBOOT adapter from (works with your normal USB cable)
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
** I don't make any commission or fee from the sales of these devices, I just know they have them on stock most of the time and ship in a reasonable time frame unlike the Chinese variants found on ebay.
If you do NOT see this, then make sure you have the SDK installed correctly and you have the right setup for fastboot on your PC before proceeding.
*** BE SURE YOU HAVE A GOOD CHARGE ON THE DEVICE ***
INITIAL SETUP INSTRUCTIONS (1st TIME ONLY) FOR 2ND-BOOTLOADER + TeamWinRecoveryProject INSTALL:
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb pull /dev/block/mmcblk0boot0
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/boot
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
adb pull /dev/block/platform/omap/omap_hsmmc.1/by-name/system # This will take a few minutes
Take those files and put them somewhere safe.
STEP 2: Download the files you will need to install 2nd-bootloader, TWRP and CM10.1:
Stack override file:
http://goo.im/devs/Hashcode/otter2/stack
[12/09] otter2-freedom-boot-10.4.6.img (USED ONLY THE FIRST TIME -- .zip files will have their own boot.img's from now on):
http://goo.im/devs/Hashcode/otter2/otter2-freedom-boot-10.4.6.img
md5sum: 80f9b9ba80910de361463560f86f315a
[09/03] TeamWin Recovery 2.6.3.0:
http://goo.im/devs/Hashcode/otter2/otter2-twrp-2.6.3.0-recovery.img
md5sum: a66a8cbab92fd5daaa85f6303e9cc0c3
older 10.2.4 bootloader file and flash to your device via fastboot:
http://goo.im/devs/Hashcode/otter2/otter2-u-boot-prod-10.2.4.bin
md5sum 5b03a7b428325de8d360ec201a745498
(You SHOULD check the MD5SUM before using fastboot -- downloads CAN be corrupted)
CM-10.1/CM-10.2 for the Kindle Fire 2 (choose the latest version from):
http://www.get.cm/?device=otter2
Google Apps from: http://goo.im/gapps (choose the version: CM10.1 or CM10.2)
Place the ROM and the gapps .zip on your device in the /sdcard area
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS -- May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to permissions changes
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
[ Connect fastboot cable, and reboot the device so that "Fastboot" is showing ]
STEP 4.
Flash the OLD bootloader, new otter2-freedom-boot.img and TWRP recovery.[/B]
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CM10.1 -- IT'S FOR STOCK AMAZON OS ONLY / FIRST INSTALL ONLY*
Code:
fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
fastboot -i 0x1949 flash boot otter2-freedom-boot-10.4.6.img
fastboot -i 0x1949 flash recovery otter2-twrp-2.6.3.0-recovery.img
fastboot -i 0x1949 reboot
** If everything was done correctly you will at this point see the bootmenu with a BLUE logo during the reboot. **
TO ENTER RECOVERY:
During the blue logo screen press the power button to cycle through options and select "Recovery" to enter TWRP.
Once in TWRP you can Install" the CM-10.1/CM-10.2 by selecting "Install" and then browsing the device and selecting it, then "Add Zip" and select the Gapps .zip as well.
Use the slider to start the install.
FLASHING BACK TO STOCK:
** FIND THE FILES WE BACKED UP IN STEP #1 OR DOWNLOAD NEW ONES FROM THE RECOVERY THREAD HERE: **
http://forum.xda-developers.com/showthread.php?t=2035047
Once you have these files (we'll name them boot.img/recovery.img and system.img for the purpose of these instructions, but they could be different on your system).
Plug in your fastboot cable and reboot so that you see the fastboot screen and enter the following commands:
Code:
fastboot -i 0x1949 flash boot [B]boot.img[/B]
fastboot -i 0x1949 flash recovery [B]recovery.img[/B]
fastboot -i 0x1949 flash system [B]system.img[/B] # This one will take a few minutes
fastboot -i 0x1949 reboot
Enjoy
THANKS TO:
fattire for finding the original bootloader exploit
TESTERS: powerpoint45 and FMKilo

Changelog: updated 2013-07-08
freedom boot.img (for use w/ stock Amazon OS + 2nd-bootloader):
[07/08] Updated w/ kernel from 10.4.3 release
TeamWin Recovery (TWRP) 2.6.0.0
[07/08] USB Vendor ID / Product ID in recovery now matches stock Amazon OS
[07/08] Based on 10.4.3 stock kernel
[07/08] Fixed recovery bootloop issue
[07/08] TWRP 2.6.0.0 update

one more reserved space

no chance to flash without fastboot cable? cause when i do
su
reboot bootloader
the fire boots into fastboot...does this work too?

Hondologe said:
no chance to flash without fastboot cable? cause when i do
su
reboot bootloader
the fire boots into fastboot...does this work too?
Click to expand...
Click to collapse
Yes, this would work, however if something goes wrong (and it frequently can during early development) you will have NO WAY of recovering the device without a fastboot cable. So I don't recommend this method currently.
Also, these instructions are BRAND NEW, and I understand if you really want to get this setup, but please let some users w/ fastboot cables run through the instructions to make sure I didn't typo something, etc.

Good work man! Can't wait for my fastboot cable so I can try this out.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

mindmajick said:
Good work man! Can't wait for my fastboot cable so I can try this out.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I`m gonna try it later WITHoUT FB cable . If it fails i just have to wait a couple of days, so its worth it if i get CM onto my kindle
BTW If it fails, im gonna blame it on you (Just kidding...)

Thanks hash code!!! Is this ROM the updated one so Apollo won't force close?

powerpoint45 said:
Thanks hash code!!! Is this ROM the updated one so Apollo won't force close?
Click to expand...
Click to collapse
I did make the /storage/usb0 changes in this ROM. No telling if it'll fix the Apollo FCs till we get it tested.

Hashcode said:
I did make the /storage/usb0 changes in this ROM. No telling if it'll fix the Apollo FCs till we get it tested.
Click to expand...
Click to collapse
OK cool! Looking forward to build custom ROM. Downloading latest ROM now... I think Darwin's upload failed ): not showing up as right file size on goo.im. will check md5 at home
Edit:no FC yet

i just ordered my factory cable... thanks hashcode and powerpoint45!

powerpoint45 said:
OK cool! Looking forward to build custom ROM. Downloading latest ROM now... I think Darwin's upload failed ): not showing up as right file size on goo.im. will check md5 at home
Edit:no FC yet
Click to expand...
Click to collapse
Goo doesn't always update the file size on the webpage during large uploads. Have him double-check the md5sum.

Hashcode said:
Goo doesn't always update the file size on the webpage during large uploads. Have him double-check the md5sum.
Click to expand...
Click to collapse
OK. I will when I get home so I can check md5. Any ideas to fix ducati?

powerpoint45 said:
OK. I will when I get home so I can check md5. Any ideas to fix ducati?
Click to expand...
Click to collapse
If someone has the time to do a video guide for this that would be great.

Congrats!
(that's all I got)

Congrats and thanks again to you and all involved!
Just soldered my own factory cable this evening from a spare micro-usb cable, and I could start my kindle in fastboot mode
Too late now so I'll take a deeper look and try to flash tomorrow evening and give some feedback - also have to find this damn fastboot command, wouldn't shop up in my terminal?!

Jowyn said:
Congrats and thanks again to you and all involved!
Just soldered my own factory cable this evening from a spare micro-usb cable, and I could start my kindle in fastboot mode
Too late now so I'll take a deeper look and try to flash tomorrow evening and give some feedback - also have to find this damn fastboot command, wouldn't shop up in my terminal?!
Click to expand...
Click to collapse
You will probably need to install the Android SDK to get the fastboot command.

Hashcode said:
You will probably need to install the Android SDK to get the fastboot command.
Click to expand...
Click to collapse
And all the image files that need to be flashed via fastboot need to reside where fastboot.exe is just to clarify.

Hashcode said:
You will probably need to install the Android SDK to get the fastboot command.
Click to expand...
Click to collapse
If you follow the noob guide on rooting the kindle fire 2 it tells you to download two files, inside of either of those two files is adb and fastboot as well as all the needed drivers, if you place the files needed to do this process inside of either of those folders holding down control while right clicking inside of the folder ( making sure nothing is highlighte) select open command prompt here, that way you should be able to do this process without the sdk
Let me know how it turns out and hopefully that will save some people the headache of getting their environmental variables set up correctly ( my computer likes to play stupid )

and nobody mentioned me.. come on, I thought I was listed in credits as moral support, and kid who flashed without a fbcable.. I know how to do it, and you could too if you just read up enough on idme and bootmodes..
No more from me, I don't want to be the one who is in trouble for bricked non factory cable owning users..

[SOLVED] Please Help Me Help Myself

I finally decided to root my daughters KFHD. I said, "Dont worry once Im done and install a custom ROM itll be 10x better than before." She reluctantly said okay only because shes seen me do the same thing to every phone and tablet Ive ever had. I knew from looking around and doing research here on XDA that there was a good chance something could go wrong and I could end up bricking her kindle. Ill cut to the chase.....Something went wrong with the install of the 2nd bootloader/recovery. I ended up with the lovely RSOD. So I proceded to make a fastboot/factory cable. Now Ive gotten rid of the RSOD but the kindle is stuck in bootloop and eventually itll go into the stock recovery saying blah blah blah kindle wont boot. Ive tried the factory reset option to no avail. One thing I find odd is this is the 2nd type of bootloop Ive seen, the 1st one would show the kindle logo for only a few seconds then it would do like the CRT animation does and bootloop from there, now tho, it actually shows the entire bootanimation, I know this because I can see the gradient color change that goes across the kindle fire logo. At this point Ive flashed everything from hashcodes thread, the 7.2.3 bootloader with the freedom 7.4.6 img and the twrp recovery several times. Ive flashed 2.7 and 2.3 recoveries along with a 7.2.3 boot img and 7.2.3 system img together with no luck. So heres where I need someone from within this wonderful open source community to help meh. Gimme a quick rundown of the kindle boot process with the 2nd bootloader including what boots when and where it boots from. Also when using fastboot whats the correct order to flash what? Should I only be trying to flash a recovery now? I shouldnt need to reflash the bootloader right? what about the boot and system img's do I flash those? This is where I need the help. Thanx in advance for taking the time to read my short novel and for helping me. Oh ya Im on linux so i havent been able to use any of the tools that are available for Winblows.

OK, from what I know you didn't install the stack override in the system partition. That's why its bootlooping.
Sent from my GT-i9100 running CM11

Thank you for the reply....after all the reading I've done I was kinda thinking that may be my problem. Is it possible that I did originally push it to my sdcard, then sometime in between then and now I erased it with the fastboot erase data command? There is no way to push anything to sdcard with fastboot, right?

Well from what I can tell the tablet is burnt. I will post pics after I smash it with a hammer and run it over with my car.

Burnt? Nononoo. Don't waste a device that is still "working". It is just bootlooping. Send it to a dev instead of breaking a good device.

No need to do that lol. Get yourself a fastboot cable and use the SRT or KFFA to restore system
Sent from my GT-i9100 running CM11

I made a fastboot already. Correct me if I'm wrong but both tools are only for windows ,right? And if the tools could do it then why couldn't I just do it from the command line in my Linux OS. The GUI tools for windows are essentially scripts that automatically run the commands for a person instead of the user manually typing them. From what I gathered I need to adb push stack /sdcard/ but all I have is fastboot commands. FWIW I downloaded the stock 7.2.3 Amazon OS tried to flash that....nothing. Tried unzipping it to flash imgs inside and nothing. tried various recoverys with no luck. Thanx for the reply's, I appreciate it a lot.

DowneyJM said:
I made a fastboot already. Correct me if I'm wrong but both tools are only for windows ,right? And if the tools could do it then why couldn't I just do it from the command line in my Linux OS. The GUI tools for windows are essentially scripts that automatically run the commands for a person instead of the user manually typing them. From what I gathered I need to adb push stack /sdcard/ but all I have is fastboot commands. FWIW I downloaded the stock 7.2.3 Amazon OS tried to flash that....nothing. Tried unzipping it to flash imgs inside and nothing. tried various recoverys with no luck. Thanx for the reply's, I appreciate it a lot.
Click to expand...
Click to collapse
Yes,you can execute the commands via Linux as well. Ill write you a guid as soon as I get to my PC. And don't give up yet

SafinWasi said:
Yes,you can execute the commands via Linux as well. Ill write you a guid as soon as I get to my PC. And don't give up yet
Click to expand...
Click to collapse
Thank you for taking the time to help me I really appreciate it.

DowneyJM said:
Thank you for taking the time to help me I really appreciate it.
Click to expand...
Click to collapse
Ok,let's get started. Download SRT from http://forum.xda-developers.com/showthread.php?p=33156486. You have to download version 7.2.3. Then,extract the zip to a folder. I'll use ~/SRT for this guide. Next,cd into the SRT folder and cd again to the images folder. At this point,you must have adb and fastboot configured. If not,run the following commands:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
Note:I'm running Linux Mint,so these should work on any Debian based distro. Open a command line in the images folder and test by running adb or fastboot. If it shows a lot of text,it's running properly.
Next,enter this command on the prompt:
Code:
fastboot -i 0x1949 getvar product
It'll show "waiting for device". Next,plug in the Kindle WITH factory cable. It should boot into fastboot. If it doesn't,your cable is damaged. Buy a new one.
Next,run the following commands one after another. Beware,the system command will take A LONG time so don't worry.
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
After this,use this command to get out of fastboot:
Code:
fastboot -i 0x1949 reboot
NOTE:You have to unplug the cable immediately after entering the command or else it'll boot into fastboot again
All done! Your tablet is restored! If you need help flashing the 2nd bootoloader and recovery,I'll be glad to help

SafinWasi said:
Ok,let's get started. Download SRT from http://forum.xda-developers.com/showthread.php?p=33156486. You have to download version 7.2.3. Then,extract the zip to a folder. I'll use ~/SRT for this guide. Next,cd into the SRT folder and cd again to the images folder. At this point,you must have adb and fastboot configured. If not,run the following commands:
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
Note:I'm running Linux Mint,so these should work on any Debian based distro. Open a command line in the images folder and test by running adb or fastboot. If it shows a lot of text,it's running properly.
Next,enter this command on the prompt:
Code:
fastboot -i 0x1949 getvar product
It'll show "waiting for device". Next,plug in the Kindle WITH factory cable. It should boot into fastboot. If it doesn't,your cable is damaged. Buy a new one.
Next,run the following commands one after another. Beware,the system command will take A LONG time so don't worry.
Code:
fastboot -i 0x1949 erase cache
fastboot -i 0x1949 erase userdata
fastboot -i 0x1949 flash boot boot.img
fastboot -i 0x1949 flash recovery recovery.img
fastboot -i 0x1949 flash system system.img
After this,use this command to get out of fastboot:
Code:
fastboot -i 0x1949 reboot
NOTE:You have to unplug the cable immediately after entering the command or else it'll boot into fastboot again
All done! Your tablet is restored! If you need help flashing the 2nd bootoloader and recovery,I'll be glad to help
Click to expand...
Click to collapse
That did it!!! :highfive::highfive::highfive: Thank you!!! I thought i had already tried flashing all the img's from 7.2.3 together but obviously I didnt. I think i got to worked up and frustrated and forgot my #1 rule "KISS" If you feel up to it I'd appreciate a rundown on the 2nd bootloader and recovery process. Thanks again.

DowneyJM said:
That did it!!! :highfive::highfive::highfive: Thank you!!! I thought i had already tried flashing all the img's from 7.2.3 together but obviously I didnt. I think i got to worked up and frustrated and forgot my #1 rule "KISS" If you feel up to it I'd appreciate a rundown on the 2nd bootloader and recovery process. Thanks again.
Click to expand...
Click to collapse
No problem mate! Trust me,once we're done with it,both you and your daughter are gonna LOVE it.
OK,basically when the tablet turns on,it runs a binary called the u boot. Now this is Amazon stuff and can't be tampered with. But we have the source code due to GPL and what we do know is that a part in the code allows us to flash unsigned third party kernels,therefore a 2nd bootloader. But it can't just be any boot image,it must be patched with the Amazon u boot AND the stack override. Not only that,you must also have installed the stack override in a specific byte address of the system partition. Once we've done that, we can safely flash a recovery and thus,get the ability to install custom ROMs. Oh,another thing. Amazon patched the u boot on versions higher than 7.2.3,so the stack will cause it to crash and show the Red Screen if it's not 7.2.3
Sent from my GT-i9100 running CM11

Kindle Fire HD Stuck on flash logo screen

I wanted to install Gapps to my Kindle since many of the apps including the web browser are coming up as unsupported. I have rooted my Kindle Fire HD 8.9 and installed TWRP. When I rebooted my kindle to enter the recover mode, it got stuck at logo screen.
At first, when it was logo was flashing if I plugged it in, ubuntu give an error message "unable to mount Jem PVT Prod 04". I discovered that holding the volume up button made the screen go blank but not off. You can plug the kindle in and Ubuntu will recognize the kindle and allow you to access the internal storage.
How can I fix and reboot the Kindle from Ubuntu?
I researched tons of solutions but most of them require Windows which I don't run or I tried the instruction and they don't work or our incomplete.

I received a fastboot cable from Amazon today. I'll see how it works. Any advice would be appreciated.

Okay, I fixed the problem with the Fastboot Cable. Here's the steps that I did to fix it. It was loading Twrp or the bootloader so I reinstall them. I have Android SDK on my computer and my Kindle is rooted.
Step 1.
The correct twrp was difficult to find. This forum offered a site to go to but I found the site was corrupted and the website was trying to download a virus.
I found the twrp and bootload file here.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet/
I placed the files in my android/sdk/platform-tools. (kfhd8-freedom-boot-8.4.3.img & kfhd8-twrp-2.6.0.0-recovery.img)
I typed into terminal "fastboot -i 0x1949 getvar product" without parenthesis. At the waiting for device command, I plugged in the Kindle with the Fastboot cable and held the Volume up button to go into fastboot mode.
I opened the android/sdk/platform-tools and right click the mouse and hit open in terminal
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.3.img
fastboot -i 0x1949 flash recovery kfhd8-twrp-2.6.0.0-recovery.img
fastboot -i 0x1949 reboot
From the reboot, hit the volume up to get into twrp.
At this point, I still could go into the kindle so I thought the operating system may be corrupted.
Step 2
In twrp, I backed up the system. and rebooted into twrp.
In twrp, I hit wipe and rebooted back into twrp.
I downloaded CyanogenMod and Gapps to my platform-tools folder again.
rootkindlefire.com/kindle-fire-root/how-to-root-convert-kindle-fire-hd-8-9-into-pure-android-tablet
Step 3
I couldn't access the internal drive so I used ADB to put the files on my kindle.
Here's a video of the instructions I used.
youtu.be/NaK5OxUeDKM
Open the support document for Ubuntu instructions.
First, open terminal in the Platform Tools file and type ADB Devices. When I pushed the two files, his instructions say to use command sudo ./adb-linux push filename /sdcard/. This didn't work. I used "./adb push [filename /sdcard/." without the quotes and it worked.
Step 4
Enter twrp and install the CyanogenMod and Gapps. Reboot
This got my operating system up and running perfectly.
Now bad for a complete Noob.

[UNLOCK][ROOT][TWRP][UNBRICK] FireTV 2 (sloane)

Read this whole guide before starting.
This is for the 2nd gen Fire TV (sloane)
Current relase: amonet-sloane-v1.1
NOTE: This process does not require you to open your device if you're already rooted or you have TWRP.
NOTE: If something goes horribly wrong and your device gets bricked, you'll have to open it and unbrick it through bootrom (post 2).
NOTE: This process will modify the partition-table (GPT) of your device.
NOTE: Your device will be reset to factory defaults (including internal storage) during this process.
NOTE: Flashing prerooted ROM will disable unlocked TWRP. It's recommended to flash an stock update.bin until that gets sorted out.
To update to the current release if you are already unlocked, just flash the zip in TWRP.
What you need:
A Linux installation or live-system
A a-a cable
1. Download the attached zip-file "amonet-sloane-v1.1zip".
2. Copy the zip-file to the internal storage of the box or copy the zip-file to an external SD/USB storage and connect it to the box.
3. Reboot the FireTV to rbox's TWRP recovery and flash the zip-file.
NOTE: If you are on firmware 5.2.7.3 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
If you chose the brick option, you need to continue with bootrom-step-minimal.sh:
NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip once you're in TWRP.
Once the zip-file finished flashing, disconnect the device and run:
Code:
sudo ./bootrom-step-minimal.sh
Then plug the device back in.
The device will reboot to hacked fastboot mode (Static Amazon White Logo + white blinking LED).
Then run:
Code:
sudo ./fastboot-step.sh
After that, the device will reboot to unlocked TWRP. Then go to Wipe > Format Data and type "YES".
You can now install Magisk from there.
Important information
NOTE: This has nothing to do with the unlock process.
You have 10 seconds to force TWRP to keep ADB over USB active by using
Code:
adb wait-for-recovery && adb shell setprop twrp.usb.mode 0
In the new partitioning scheme your boot/recovery-images will be in boot_x/recovery_x respectively, while boot/recovery will hold the exploit.
TWRP takes care of remapping these for you, so installing zips/images from TWRP will work as expected.
Don't flash boot/recovery images from FireOS (FlashFire, MagiskManager etc.) (If you do anyway, make sure you flash them to boot_x/recovery_x)
Should you accidentally overwrite the wrong boot, but your TWRP is still working, rebooting into TWRP will fix that automatically.
TWRP will prevent updates from overwriting LK/Preloader/TZ, so generally installing an update should work without issues (only full updates, incremental updates won't work).
For ROM developers there is still an option to overwrite these, which should only be done after thorough testing and if needed (LK should never be updated).
It is still advised to disable OTA.
Very special thanks to @k4y0z and @t0x1cSH for making all this possible by porting the LK exploit to sloane and implementing the RPMB-key derivation for sloane.
Special thanks also to @xyz` for making all this possible and releasing the original amonet exploit for karnak.
Special thanks also to @retyre for porting the bootrom-exploit to mt8173.
Special thanks also to @Sus_i and @DanielF50 for testing.
Special thanks also to @diplomatic for his wonderfull mtk-su, allowing you to unlock without opening the device.

Unbricking / Unlocking with non-rooted Firmware
Prepare the environment, disable modemmanager and install the required packages:
Code:
sudo apt update
sudo add-apt-repository universe
sudo apt install python3 python3-serial adb fastboot dos2unix
Code:
sudo systemctl stop ModemManager
sudo systemctl disable ModemManager
NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip linked in the first post (OP).
If FireOS is still accessible there are other means of recovery, don't continue.
If your device shows one of the following symptoms:
It doesn't show any life (screen stays dark)
You see the white amazon logo, but cannot access FireOS.
If you have a Type 1 brick, you may not have to open the device, if your device comes up in bootrom-mode (See Checking USB connection below).
Unplug the device from the wall
Start bootrom-step.sh
Plug in the power source and then the USB
NOTE: If you have issues running the scripts, you might have to run them using sudo.
Also try using different USB-ports (preferably USB-2.0-ports)
1. Extract the attached zip-file "amonet-sloane-v1.1.zip" and open a terminal in that directory.
2. Start the script:
Code:
sudo ./bootrom-step.sh
It should now say Waiting for bootrom.
3. Connect the USB A-A cable, short the board according to the picture (DAT0 with GND), and connect the power supply.
4. When the script asks you to remove the short, remove the short and press enter.
5. Wait for the script to finish.
If it stalls at some point, stop it and restart the process from step 2.
6. Your device should now reboot into unlocked fastboot state.
7. Run
Code:
sudo ./fastboot-step.sh
8. Wait for the device to reboot into TWRP.
9. Format data and use TWRP to flash a custom ROM, Magisk or SuperSU.
Checking USB connection
In lsusb the boot-rom shows up as:
Code:
Bus 002 Device 013: ID 0e8d:0003 MediaTek Inc. MT6227 phone
If it shows up as:
Code:
Bus 002 Device 014: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
instead, you are in preloader-mode, try again.
dmesg lists the correct device as:
Code:
[ 6383.962057] usb 2-2: New USB device found, idVendor=0e8d, idProduct=0003, bcdDevice= 1.00

Unlocking with ADB + root
NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
1. Extract the attached zip-file "amonet-sloane-v1.0.1.zip" and open a terminal in that directory.
NOTE: If you are already rooted, continue with the next step, otherwise get mtk-su by @diplomatic from here and place (the unpacked binary) into amonet/bin folder
2. Enable ADB in Developer Settings.
3. Start the script:
Code:
sudo ./step-1.sh
Your device will now reboot into recovery and perform a factory reset.
NOTE: If you are on firmware 5.2.7.3 or newer, a downgrade is necessary, this requires bricking the device temporarily. (The screen won't come on at all)
If you chose the brick option, you need to continue with bootrom-step-minimal.sh:
NOTE: Please refer to the #2 post on how to prepare your environment before proceeding.
NOTE: If you use this method to unlock the device you don't need to flash the unlock-zip once you're in TWRP.
Once the zip-file finished flashing, disconnect the device and run:
Code:
sudo ./bootrom-step-minimal.sh
Then plug the device back in.
The device will reboot to hacked fastboot mode (Static Amazon White Logo + white blinking LED).
Then run:
Code:
sudo ./fastboot-step.sh
After that, the device will reboot to unlocked TWRP. Then go to Wipe > Format Data and type "YES".
If you used this method (brick), you're done with the unlock. Skip the step 4.
NOTE: Make sure you re-enable ADB after Factory Reset.
4. Start the script:
Code:
sudo ./step-2.sh
The exploit will now be flashed and your device will reboot into TWRP.
You can now install Magisk from there.

There are three options for interacting with TWRP:
A mouse/keyboard via USB
ADB over ethernet/USB
TWRP commandline via adb: https://twrp.me/faq/openrecoveryscript.html
Via /cache/recovery/command
Example for /cache/recovery/command:
Code:
echo "--update_package=/path/to/zipfile" > /cache/recovery/command
echo "--wipe_cache" >> /cache/recovery/command
reboot recovery
If you somehow end in a bootloop you can boot into hacked fastboot or recovery using.
Code:
sudo ./boot-fastboot.sh
Code:
sudo ./boot-recovery.sh
NOTE: This will only work if the boot-exploit is still there.
Source Code:
https://github.com/chaosmaster/amonet-sloane
https://github.com/R0rt1z2/android_device_amazon_sloane
https://github.com/chaosmaster/android_bootable_recovery

Reserved

Nice to see this released - it's been a while in the making... just glad that me and my multiple sloanes could be of service to the community
edit: obviously Magisk works with a full unlock, but as Rortiz2 states above this must be flashed to boot_x - I would advise you pull your ROM's boot.img, patch it with MagiskManager & then flash this manually via hacked fastboot, otherwise it won't work & you'll probably brick your device again.

DanielF50 said:
Nice to see this released - it's been a while in the making... just glad that me and my multiple sloanes could be of service to the community
Click to expand...
Click to collapse
Yeah I'll second that, It works perfect and flawlessly. Be sure to follow the guide to the letter ..... .... It's good to see development continue to make progress on what I would say is the best amazon device of them all.
Well done. All your hardwork is greatly appreciated. @k4y0z , @Rortiz2 , @t0x1cSH, @Sus_i , @retyre , @diplomatic @DanielF50 without you guys continued attention and testing of these sticks/boxes we would be stuck with plain old boring devices.
Cheers again
regards

DanielF50 said:
I would advise you pull your ROM's boot.img, patch it with MagiskManager & then flash this manually via hacked fastboot, otherwise it won't work & you'll probably brick your device again.
Click to expand...
Click to collapse
Don't worry, magisk flashing in TWRP works (now).

Time to pull the Sloanes out of the drawer!

Ok, so I ran into some issues. I flashed the zip in the pre-rooted TWRP. No errors and reboots into unlocked TWRP. From unlocked TWRP i format data and type yes, then reboot. Now i am at the black amazon fire logo and nothing happens. I think i missed or didnt understand the downgrading part to older than 5.2.7.3. So, i think i have to do the shorting method now? Also, does anyone know where i can find a old version <5.2.7.3 .bin to flash? Is there anyway to get back into unlocked TWRP now?

http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.7.0-rooted_r1.zip
http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.6.7-rooted_r1.zip
All here, scroll down
Fire TV & Fire TV Stick Downloads: APKs von Apps & Games
Fire TV Downloads Sammlung von Android Apps (APK-Dateien), die man herunterladen und auf dem Amazon Fire TV und Fire TV Stick 4k installieren kann.
aftvhacks.de

0815hoffi said:
http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.7.0-rooted_r1.zip
http://aftvhacks.de/downloads/rooting/fire-tv-2/sloane-5.2.6.7-rooted_r1.zip
All here, scroll down
Fire TV & Fire TV Stick Downloads: APKs von Apps & Games
Fire TV Downloads Sammlung von Android Apps (APK-Dateien), die man herunterladen und auf dem Amazon Fire TV und Fire TV Stick 4k installieren kann.
aftvhacks.de
Click to expand...
Click to collapse
Thanks, great resource. I am looking for stock though...
" NOTE: Flashing prerooted ROM will disable unlocked TWRP. It's recommended to flash an stock update.bin until that gets sorted out. "

Michajin said:
Ok, so I ran into some issues. I flashed the zip in the pre-rooted TWRP. No errors and reboots into unlocked TWRP. From unlocked TWRP i format data and type yes, then reboot. Now i am at the black amazon fire logo and nothing happens. I think i missed or didnt understand the downgrading part to older than 5.2.7.3. So, i think i have to do the shorting method now? Also, does anyone know where i can find a old version <5.2.7.3 .bin to flash? Is there anyway to get back into unlocked TWRP now?
Click to expand...
Click to collapse
If the zip flashed fine forget about the downgrading part. Are you able to boot unlocked TWRP using boot-recovery.sh?
Here's an stock update.bin: https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.4.8_user_648594820.bin

Rortiz2 said:
If the zip flashed fine forget about the downgrading part. Are you able to boot unlocked TWRP using boot-recovery.sh?
Here's an stock update.bin: https://d1s31zyz7dcc2d.cloudfront.n...indle-full_sloane-36.6.4.8_user_648594820.bin
Click to expand...
Click to collapse
yes, boot-recovery works perfect. That is exactly what I needed thanks!

In case someone needs some newer 'full OTA update' packages of the stock rom, only for sloane:
Fire OS 5.2.7.3 (652614020).
https://d1s31zyz7dcc2d.cloudfront.net/7af0a9a31621db60bf48d23e680751d3/update-kindle-full_sloane-36.6.5.2_user_652614020.bin
Fire OS 5.2.7.4 (656638420).
https://d1s31zyz7dcc2d.cloudfront.net/7758ad70f668023cc93ddee2655c6226/update-kindle-full_sloane-36.6.5.6_user_656638420.bin
Fire OS 5.2.7.6 (659654620).
https://d1s31zyz7dcc2d.cloudfront.net/c5b513d2116f5ad2942426ab79bb437b/update-kindle-full_sloane-36.6.5.9_user_659654620.bin
5.2.7.6 is the latest OS (as of today).
Don't forget to rename the file, i.e. .bin to .zip.

Sus_i said:
Don't worry, magisk flashing in TWRP works (now).
Click to expand...
Click to collapse
Oh, awesome news!

Hey guys, So do users of the new unlocked twrp to only use the clean update.bin files provided by @Sus_i and not the rbox prerooted stock (supersu) roms? Just to clarify for the sake of Magisk clashing with Supersu prerooted firmware incase it throws some nasty surprises.
Regards

Next OTA update incoming...
Full OTA update package (latest stock) for sloane:
Fire OS 5.2.7.7 (662663720).
https://d1s31zyz7dcc2d.cloudfront.net/b9f7c8f9a8a4ba1f34da8ce7a8077474/update-kindle-full_sloane-36.6.6.2_user_662663720.bin

Sus_i said:
Next OTA update incoming...
Full OTA update package (latest stock) for sloane:
Fire OS 5.2.7.7 (662663720).
https://d1s31zyz7dcc2d.cloudfront.net/b9f7c8f9a8a4ba1f34da8ce7a8077474/update-kindle-full_sloane-36.6.6.2_user_662663720.bin
Click to expand...
Click to collapse
5.2.7.7 yipeee
Seconds later bootloader is locked lol
I'm currently on 5.2.7.4 I think I'll stay there. This is the os before big A started messing with adb and accessibility (launchers) you can just disable launcher and firehomestarter apk provided there is a settings apk installed (hoffis is great).

lol