Fire HD 6 - 5.3.1.1 - How to root correctly? - Fire HD 6 and 7 Q&A, Help & Troubleshooting

Fire HD 6 - 5.3.1.1 - How to root correctly? - Fire HD 6 and 7 Q&A, Help & Troubleshooting

Hello Fire users
I am not really a newbie but until today I have worked only with Samsung devices.
My daughter got an Fire HD 6 in the christmas days and we started to play around and we have done all updates up to 5.3.1.1. But it's not running perfectly for my wishes. I have read thats it's possible to root the tablet incl. TWRP, xposed framework and go with this up to 5.3.1.1 but it's hard to read out what I have exactly to do because there are many warnings when to do something and when not.
Could you please help what to do exactly? ADB is running and phone is recognizing on Mac and Windows...
Thanks for your help ?

cuki3r3k83bln said:
Hello Fire users
I am not really a newbie but until today I have worked only with Samsung devices.
My daughter got an Fire HD 6 in the christmas days and we started to play around and we have done all updates up to 5.3.1.1. But it's not running perfectly for my wishes. I have read thats it's possible to root the tablet incl. TWRP, xposed framework and go with this up to 5.3.1.1 but it's hard to read out what I have exactly to do because there are many warnings when to do something and when not.
Could you please help what to do exactly? ADB is running and phone is recognizing on Mac and Windows...
Thanks for your help
Click to expand...
Click to collapse
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here

Killa8 said:
From latest news, OS 5.3.1 can't be rooted(directly). You'll need to downgrade to 4.5.3, root, and go back to 5.3.1 as explained here
If you want to feel android experience, you can either install custom launcher and Play Store from here or just totally install Cyanogenmod 11 from here
Click to expand...
Click to collapse
@Killa8, as I mentioned HERE in more detail, the procedure for downgrading to 4.5.3 doesn't appear to be explained in the linked tutorial. Any help would be greatly appreciated! I'm trying to root and install CM on my daughter's tablets as they find Android to be far more intuitive than FireOS. Many thanks!!!

Downgrade to 4.5.3 and root as seen here (skip step 1): https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Jump down to the 2nd post here: https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and install TWRP on your device.
Then go to post 1 where it says "1) boot into TWRP, and, in a single session (!!!!!)" and follow the directions. MAKE SURE YOU USE THE RIGHT BOOTLOADERS!!
Enjoy rooted FireOS 5.3.1

RadRacer said:
Downgrade to 4.5.3 and root as seen here (skip step 1): https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Jump down to the 2nd post here: https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 and install TWRP on your device.
Then go to post 1 where it says "1) boot into TWRP, and, in a single session (!!!!!)" and follow the directions. MAKE SURE YOU USE THE RIGHT BOOTLOADERS!!
Enjoy rooted FireOS 5.3.1
Click to expand...
Click to collapse
Thank you for this! I was having the same issue as the OP and this solved it.:good:

geoyou said:
Thank you for this! I was having the same issue as the OP and this solved it.:good:
Click to expand...
Click to collapse
Can you tell me how you installed TWRP? the 2nd post of the page is confusing to me.
NVM i found a video tutorial

I've seen too many threads mentioning 5.3.1 and implying that 5.3.1.1 is the same.
Even if that is the case, all the tutorials I have read left me scratching my head at various points. So here is a walkthrough of what I just went through to root my Kindle fire HD 6
It's now running 5.3.1.0 and will stay there for the time being (unless I can get solid answers on 5.3.1.1).
I started with this tutorial thread but I found it easy to make mistakes and I ended up bricking my device (fortunately the unbrick iso is very good and the tutorial video is excellent).
So here is my procedure. Doing this on Windows is probably less involved thanks to the bat file in one of the steps.
Start by getting the stuff you will need together.
You will need ROMs from here.
Specifically, the 4.5.3 and 5.3.1.0 ROMs.
The 4.5.3 file name is update-kindle-20.4.5.3_user_453011120.bin
The 5.3.1.0 file name is update-kindle-20.5.5.2_user_552153420.bin
Note: The version number on that second file makes no sense to me, and I made a mistake trying to flash the wrong one in TWRP. Here is the correct name for reference. You might change the file names to reflect the version number.
Go ahead and change the extension of the 5.3.1.0 bin file to zip instead. TWRP will need it this way.
Download the stock recovery image. There is a link at the bottom of the second post in the tutorial thread I linked above. Or you can just click here.
Grab the WindowsAutoTWRP_v03.zip from the tutorial thread (or click here).
It has the Windows ADB executable and drivers in it so it will save you some hassle on a Windows machine.
For Macs, I found a video from RootJunkie.com that linked to tools at http://rootjunkysdl.com/files/?dir=Adb%20Fastboot%20Files. I was able to do everything from my Mac with these.
As a side note, the video I found these on was https://www.youtube.com/watch?v=iv0VcNM8IAw, but it's not important to watch.
It will help to gather zips and APK files you will need right now as well.
Get a copy of ES file explorer, Kingroot (I used the APK, but if you have a windows system, it might be easier to use the Windows version instead), and an android launcher of some sort.
For additional images, you will need the following:
From the tutorial thread: make_space_v02.zip
Supersu.zip linked at https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Xposed which if you follow the link from the tutorial through the forum thread should lead you here: http://dl-xda.xposed.info/framework/sdk22/arm/. I grabbed xposed-v87-sdk22-arm.zip
flash Pico (Uni) GAPPS for 5.1 which again, if you follow all the links, will take you here: https://basketbuild.com/filedl/devs?dev=osm0sis&dl=osm0sis/gapps/tk_gapps-modular-pico%28uni%29-5.1.1-20150920-signed.zip.
Make sure you have all the files gathered in one place, it's really helpful.
If you are using a Mac, you will also need Android File Transfer at https://www.android.com/filetransfer/.
Something optional that might help is a USB OTG cable or one of those USB drives that support USB OTG with its own micro USB connector. It's not necessary but it might help if you need to get files to your tablet in TWRP.
At this point, I'm going to go into Mac instruction mode. If you know that the Windows command prompt is sort of like the terminal application on OS X, that you don't use ./ path specifies on windows, etc, you should be able to come up with some
Once you have everything in place, shut down your Kindle Fire 6.
On your computer, open a terminal window and get to where you unzipped your ADB tools.
The simple way is to type cd followed by a space then drag the folder with your tools from finder to the terminal widow so you get something like cd /users/me/abd
The actual path will be dependent on your system.
This terminal window should remain open for the entire process. It will make life easier.
Hold volume up and turn the Kindle Fire on. You should enter recovery.
Back at your computer type ./adb devices
Your kindle should show up there. When it does, go back to your tablet and select "apply update from ADB".
Then, from the terminal, enter ./adb sideload 4.5.3 file name is update-kindle-20.4.5.3_user_453011120.bin
If you just type ./adb sideload then drag the file into the terminal window, it will fill the name and path out for you.
Note that this all seems kind of like the video I linked above but we are downgrading to 4.3.5 instead as the tutorial thread says we should.
Once that's done, you end up back at the recovery screen. I went ahead and did a wipe data/factory reset. I don't know if this is necessary though.
When you get into 4.5.3, you need to shut down wifi if you are not prompted through new device setup.
If you are prompted, just skip it.
You may need to enable debugging. Go to setting, device options, find the serial number field and tap it 7 times.
Open the now revealed developer console and toggle "enable ADB" so it's on.
Install the APKs you downloaded earlier.
Use ./adb install <name of ES file explorer apk>
If you're on Windows, you can go ahead and run the Windows root util.
If you are on a Mac, install the Kingroot APK using the ./adb install command.
If you go the APK route, Kingroot requires a wifi connection. This will expose you to Amazon's OTA updates. You will need to watch your Kindle carefully at this point.
The download with probably download but as long as you don't let it sleep, it should not reboot and install.
Kingroot may take a couple of tries to get root.
As soon as it does, turn off wifi!
After that, open ES file explorer, give it root permissions, then navigate to the root folder, then to cache. Look for a bin file there. If there is nothing, you didn't get the OTA update pushed to you. If you did, delete it. See post 5 in this thread: https://forum.xda-developers.com/kindle-fire-hdx/help/deleting-downloaded-update-t3100573
To prevent any OTA relapses until we can go further, use ES file explorer to rename /system/etc/security/otacerts.zip. I replaces the first o and last p with _ characters.
It should be safe to turn on wifi at this point.
If you deleted a bin file in /cache, you aren't out of the woods yet. The Kindle could still reboot on you and it will give you the red ! but I found booting into recovery then just rebooting the Kindle caused it to work itself out after a couple tries.
We should be good to go for TWRP at this point.
In the terminal type ./adb shell
When the shell opens type su
Grant the shell permissions on the Kindle
Type exit twice.
On a Mac, we cannot run the bat file included in the WindowsAutoTWRP_v03.zip file.
But here are the commands to enter manually:
./adb devices
./adb install gscript-android.apk
./adb shell "mkdir /sdcard/gscript"
./adb push gscript /sdcard/gscript/
./adb shell "cp /sdcard/gscript/flash_453_stay.sh /data/local/tmp/"
./adb shell "ls /data/local/tmp/"
./adb shell "su -c 'chmod 777 /data/local/tmp/flash_453_stay.sh'"
./adb shell "su -c 'sh /data/local/tmp/flash_453_stay.sh'"
Once complete open ES file explorer again
DELETE sdcard/gscripts/s5.4.1_113_stock_recovery_uboot.zip!!!!!!!
It's too easy to mistakenly flash this in TWRP and it WILL brick your kindle.
We will now copy those zip files we downloaded earlier onto the Kindle.
I used the Android file transfer unity to put them in the scripts folder but copying them to Downloads on the Kindle might be easier.
If you are a command line type of person, you can also use the adb push command.
You want to copy over the following:
The 5.3.1.0 file name is update-kindle-20.5.5.2_user_552153420.bin
5.5.2_1534_stock_recovery_uboot.zip
UPDATE-SuperSU-v2.46.zip (or whatever the current version you downloaded is)
make_space_v02.zip
xposed-v87-sdk22-arm.zip (or whatever the version you downloaded is. The version could have changed after I wrote this.)
tk_gapps-modular-pico(uni)-5.1.1-20150920-signed.zip (again, based on what version was available when you downloaded it)
It might be a good time to sideload that extra launcher you downloaded earlier. I didn't need it, but you might.
Again the command is ./adb install <apk file name>
In the terminal, type ./adb reboot recovery.
You *should* end up in TWRP.
These next steps are important to do in one go. Don't exit TWRP until you have installed all the zip files you copied over.
The order in the tutorial thread is the 5.3.1.0 system image, the recovery image, the make_space zip, the Supersu zip, the xposed zip, and the tk_gapps-modular-pico(uni)... zip.
Do all this from the Install menu in TWRP. I did not try to queue up all the zip files at once, I don't know if that would work.
If you forgot to copy a file, TWRP should allow you to copy files via a USB cable to your tablet.
If you do this on a Mac and Android file transfer craps out on you as it did with me, that is where the USB OTG cable comes in handy. But lets hope you copied everything or that the USB connection doesn't crap out on you.
Select the wipe menu, then advanced wipe. Check the cache and dalvik cache. Once done use the back arrow and swath the "swipe to factory reset" slider.
If you are brave, you can just reset and wait through the fire logo.
If you are trying to follow along with the tutorial I linked, reboot while holding volume up to see what recovery you land in. If it's not TWRP, proceed.
When you finally get to Android, you can use ES file explorer as one way to check for root privileges. I'm sure there are others.
I'm no expert, but if you run not problems with the Kindle Fire HD 6 (4th gen) and you started with 5.3.1.1, I can tell you some of the pitfalls I ran into and how I got out of them.

Excellent guide, thanks elementcarbon12!
I'm a total new comer to rooting and getting my hands dirty with android (although I am a long time linux user), and i made it work, and now have a fire hd 6 that I can sort the way I want it!
I did encounter a few problems though, first, I did not do a factory reset /data wipe after the downgrade and ended up in a boot loop. This was easily sorted by using the "adb reboot recovery" command, doing the data wipe/reset and then holding down power for 20 sec.
Everything was smooth sailing again until the reboot out of TWRP after installing the ZIP files. I did the wimps reboot to recovery to make sure I didn't get TWRP, which I didn't, so rebooted to get into android, however I entered a boot loop again. This time a simple hold the power for 20 sec and then turn on worked and the system started it's 'optimization'.
Upon completion, i still had root, although ES and my chosen launcher had gone, so had to reinstall them. No problems there though.
So thank you very much for collection all of the information and links from other pages into this one easy to follow post!

hi guys i have a question I'm on cm11 on fire hd 6 i also have a android backup of 4.5.3 my question is I'm note sure what boot loader i have at one point it did have 5xxx on it but not sure what version can i just side load 5.4.0 and be okay since the stock rom was put back to 4.5.3 thats how i installed cm11 or does it need boot loader from a 5xxx rom

Related

ClockWork Mod recovery wont install on prime!!!

Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)

hahmoode said:
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
Click to expand...
Click to collapse
On an unlocked device I don't think there can be aproblem to install a recovery.
All methods (terminal one or apps like Rom Manager and Goo) are in fact the same, copying the img or blob file in the flash partition, and the real flash occurs at next boot.

hahmoode said:
Does anyone else have the issue where the Clockwork mod wont install. I have tried using rom manager, and did the terminal and pushing the blob file through but it just refuses to install. All the transformer does is give me a logo. The next step i tried is using the Goo manager to install the recovery but same thing, it refuses to boot to it or install technically!!
PLEASE HELP! does anyone know what im doing wrong or if there is a way to fix this?
(if this is the wrong forum for this please inform me immediately.)
Click to expand...
Click to collapse
yes should be in Q & A
1. YOU ARE NOT RUNNING ASUS SOFTWARE ANYMORE. THAT IS WHY ASUS PROVIDED A WARNING WHEN YOU UNLOCK. YOU SHOULD EXPECT ISSUES WITH ROMS, IT IS BOUND TO HAPPEN.
2. The full wipe of the internal SD is for a fresh start. Its basically the same as re-installing windows, Kiss all your stuff goodbye unless you back it up beforehand. Don't cry to use that you lost your stuff because you decided to rush and not read the menu and select the correct choice.
3. Team Wookie are normal people with normal jobs and somewhat normal families that in turn this things take priority first, NOT YOUR PRIME. If issues arise we will work best with you as long as you are respectful and not a prick towards the team demanding stuff. We will address these issues on our clock, not yours.
4. Any future things you would like to see in future editions of this ROM please send me a PM and I will forward the information on to the rest of the team to discuss if it is possible. Keep in mind that we will not include paid apps in this rom because we will not rob out of other developers pockets for their hard work and also dropping the soap in prison leads to bad things that we want to avoid. JUST BECAUSE A REQUEST IS MADE IT DOES NOT GUARENTEE THAT IT WILL BE HONORED OR IN THE NEXT VERSION WHENEVER IT COMES OUT.
5. Team Wookie greatly appreciates all it's followers and feedback so don't ever think that your not appreciated, at least when it comes to a rom on a tablet level, the rest of your real world life is on you.
6. RESEARCH RESEARCH RESEARCH. We know there are a lot of posts now, 178ish pages and growing, please search through these pages to see if a solution has been found to your problem first before posting.
7. This is not the forum to ask how do I root my tablet or flash a rom. There are plenty of other threads on XDA and videos on youtube that explain how to do it with the current version software that you have.
This has been a public service announcement from Team Wookie, Long live the rebellion.
---------- Post added at 09:14 AM ---------- Previous post was at 09:06 AM ----------
Download goo manager from the play store and in the upper right hand corner select recovery. It will ask for superuser permissions then let it do its thing. However it will not show a progress bar or anything but rather just go back to the main menu. Just wait a few minutes and you will ge a pop up saying it is now installed.
---------- Post added at 09:17 AM ---------- Previous post was at 09:14 AM ----------
This is not an issue because the rom is designed to work this way and I have flashed it this way many times. I have a video coming up shortly showing the whole install from twrp to desktop, im just editing it now. If anyone is feeling scared about doing this before you flash get the adb software package and try to push a test file to your tablet ( i just made a test.txt file) and see if it actually works. If the poop hits the fan then you know you can always push the zip file back because you confirmed ADB working with your computer and tablet.
For those having ADB issues follow this guide I made up. the best thing to do is to try to push a test file before you flash is you are going to super wipe and if you are really that nervous about it. This is based off of windows 7 64 bit but should be the same for windows 7 32 bit. I can confirm this works. Regardless ADB is good to have if you run any Android devices, not just this ROM so in case poop ever hits the fan here ya go:
This solved it for Winblows 7 64 bit. For others having the same problem on Winblows 7 64 bit (should be the same for 32 bit miuns the X86 Directory)
1. Go into settings on the prime and make sure USB debugging has a check in it in under SYSTEM > Developer options > USB Debugging
2. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers. If you see at the top of device manager ASUS Android devices and when you expand it you see ASUS Android Composite ADB Interface you already have the ADB drivers installed and can skip down to #6
3. Go to ASUS website and download the USB drivers for the TF201. Download Vipermod Primetime 4.6 here for the ADB drivers http://goo.im/devs/viperboy/Prime/vi...eTime_v4.6.zip then extract the zip file to a normal file. You only need the drivers from the tool.
4. Plug your prime into your Winblows 7 laptop and let it install its drivers. Open up device manager by going to Start > Control Panel > Hardware and Sound > and click on device manager under devices and printers.
5. You should see the prime listed under portable devices. Uninstall the driver then update the driver manually. Browse to the folder you created from the Vipermod primetime zip. Make sure there is a check in check sub folders. Winblows should detect the drivers and then convert the prime to a ASUS Android Device.
6. Go into settings on the prime and make sure there is no check in Launch ASUS Sync under PERSONAL > Accounts & Sync > Launch ASUS Sync
7. Press Control, Shift, Escape at the same time and make sure there are no instances of ASUS Sync or Splashtop runnung in services in Winblows 7.
8. Download and Install the latest Android SDK. I installed all the libraries and such just to be on the safe side. http://developer.android.com/sdk/index.html
9. DISCONNECT YOUR PRIME FROM THE USB AND REBOOT YOUR PRIME AND YOUR WINBLOWS LAPTOP. After both devices reboot plug in your tablet into your Winblows laptop.
10. Navigate to C:\Program Files (x86)\Android\android-sdk\platform-tools and click on the ADB file. A command prompt will open and spool up a bunch of stuff then close. All the stuff spooling I am assuming was the ADB server starting.
11. Hold down shift then right click inside platform-tools folder and select open command prompt here. You should be in a command prompt window showing the directory C:\Program Files (x86)\Android\android-sdk\platform-tools
12. type adb devices. You should see your primes serial number pop up.
13. make a test file in the platform-tools directory, i just used a simple text file to test then type:
adb push test.txt /sdcard/
It would be easier to just put the Rom you are going to flash in this directory so when it is time to push the rom it would be:
adb push nameofrom.zip /sdcard/
If SDCARD not recognized try:
adb push nameofrom.zip /system/media/
14. browse to your sdcard and you should see your file there. If you are already in the sdcard folder window on your prime, leave the folder then come back and it should be there.
15. You should be able to push files now after superwiping. You may need to push to /system/media/ if /sdcard/ is not found. Make sure you have all the / in the directory structure when pushing.
16. From inside recovery select install zip from sdcard and browse to the folder you pushed it to then flash awa
Sent from my Transformer Prime TF201 using xda app-developers app

So with those steps it still hasn't installed recovery! So the thing is that i have full root, and my prime is unlocked, but it just WONT install recovery using any app or manually! Is there a idea on why my prime wont let me?
(Thanks for that long answer btw i tried a lot of it but stil no dice )

Have you tried twrp? The link is HERE. I found its more reliable on the prime. Just my opinion.

fredgar75 said:
Have you tried twrp? The link is HERE. I found its more reliable on the prime. Just my opinion.
Click to expand...
Click to collapse
I will deff try it when i get home from work thank you i will let you know later! (THANKS SO MUCH FOR SOME MORE ADVICE ON THIS)

Ok just to be sure. You did unlock through asus? And you are rooted I know you said you have but just want to make sure. The only reason you wouldnt be able to flash a recovery is if your not unlocked. Just trying to rule out the obvious.

Simple steps:
1-Unlock prime
2-Download the ROM of your choice.
3-Download Goo Manager from the Play Store. Open it and hit menu - Install OpenRecoveryScript. The app will ask for su perms and may exit back to the main screen. Hit the install button again and the app will download the recovery, flash it and reboot. You'll see the flashing process and your tablet will reboot again. At this point you can hold vol down, then up to enter recovery.
4-Flash ROM
5-Profit!!
Doesn't get any easier, takes about 10 minutes for everything.

I used the multi root tool, viper mods tool I think it was, from a long time ago that was designed for rooting the .15 firmware, even though I was on .21 or .28 and I didn't use it to root, I only used the option to install recovery, which installs the latest TWRP recovery when I had a similar issue.
It worked great, I just ran the program on the computer and told it to install recovery.
Sent from my ADR6425LVW using xda premium

[Q] Help with Asus TF201

Hi to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
I wanted to get rid of some apps that I dont use at all e.g Amazon Kindle but found out with research that I can do that. Also tried to use apps like Titanium Backup again I couldnt. I am new to the Tablet world this is my first. So I did some research and terms of root, unlock etc came up. So I know the difference between them. In order not to lose my warranty and since I just want to be able to delete certain unwanted apps and add other apps, I just want to for now root my TF201.
Did more research but I still cant get an answer or get some of the methods to work for me.
Below is the specs for my Asus TF201
1. So I have JB (Android Version 4.1.1), dont know if it came with it or got updated like I said I didnt mess with the tablet alot
2. Build #: JRO03C.US_epad-10.4.2.17-20121018
I plugged in the USB to my Windows XP laptop for the first time today and ofcourse I am missing the drivers. I went to ASUS website and couldnt figure what I need.
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB

ramez75 said:
Hi to All,
Well I got an ASUS TF201 March 2012 and I never messed with it much, just net surfing and watching movies and listening to music....
*SNIP*
1. Does anyone have the ASUS Sync that I need on my laptop
2. Also does anyone have the drivers that I need on my laptop so my ASUS is recognized. I installed some drivers from the xda forum to use the DebugFS Root but got a message that I need to install the latest drivers. Does anyone have them or can tell share a link for me to get them.
All I want basically is to have the current drivers on my laptop and the ASUS Sync thing and be able to ROOT my tablet. Most of the threads I read are for the Android Version ICS 4.0.
Any help on this is greatly appreciated
Thanks
RB
Click to expand...
Click to collapse
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
TWRP Page
On that page are instructions including a download link for JB BOOTLOADER ONLY! MAKE SURE YOU GET THE RIGHT TWRP FILE FOR YOUR DEVICE. THE ICS ONE IF YOU ARE ON ICS, OR THE JB ONE IF YOU ARE ON JB:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
Download bin4ry's root tool to get the ADB file
When that is downloaded you can compare the MD5 hash because its a good idea to do that. You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it saysthe files MD5 hash is on the download web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Copy the unlocker APK to the SD card. Run a file explorer on our tables and browse to the SD card (/Removable/MicroSD). Tap the APK to install. Once installed run the Icon for the unlocker and follow directions. There are several warnings etc.. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
if you don't get the command window here option then you will have to open a command prompt. open the run dialog and type CMD and hit enter. This will get a dos command windows. Use the change directory (CD) command to change the current folder in the DOS window to where your fastboot file and TWRP.blob are.
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed.
To test root with ADB:
Your tab must be plugged in to the USB port of the computer of course.
If you installed the SDK tools it is there or use the one from bin4ry's root tool as follows:
Unzip the downloaded root tool from bin4ry mentioned above. Use the command windows to change directory of the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the command sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Edits:
I have editted this based on questions below to make it more complete..

First Thank yo uso much for taking the time and sharing the good info. Ofcourse there is alot of foreign terminology you have used and I will need to read you reply a number of time till it soaks in and I am sure I will have follow-up questions.
So it seems the only way I can get to root my TF201 (running JB) is to unlock it which means losing the warranty. Well if thats the only route then so be it....
I guess first thing is to successfully unlock the TF201
hx4700 Killer said:
Asus Suite including Sync:
http://support.asus.com/Download.as...ite_v1_0_41.zip#ASUS_Pad_PC_Suite_v1_0_41.zip
I just went through the unlock part yesterday so fresh in the mind it ASSUMES AN SD CARD IS INSTALLED and WINDOWS OS!
Asus Unlock Tool:
http://support.asus.com/Download.as...ck_Device_App_V6.apk#UnLock_Device_App_V6.apk
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Then I downloaded Ultimate Backup Tool from here:
http://goo.gl/iOUwe
Unzip it so you have fastboot.exe
Rename the TWRP you downloaded to TWRP.blob and copy it to where you have fastboot unzipped.
Finally download SuperSU zip file from:
http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip
Now we need to unlock the device. Run the unlocker tool you downloaded. For here its fuzzy for me because I found the APK file I got from the Asus download and copied it over to my tablets SD card via USB. Then I used the built in file browser to find it on my SD card and ran it. By whatever means you will need to run the unlocker tool on your tablet to unlock. You will need wifi connected and it will unlock your device and VOID YOUR WARRANTY!.
The unlock will take a few minutes. When it is successfull you will see a notice on device boot up that says the device is unlocked.
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
Let it runs its course. When done I had a black screen with ASUS in the middle and a blue-ish bar across the bottom that was filled. I had to hold power until it rebooted.
Once I confirmed my Stock OS loaded I copied the Super SU zip file we downloaded above over to the device via the USB cable to the root of my SD card. Once the copy complets shutdown the device again.
Once off, power it on and press and hold both the power buttons and volume down again. When the menu appears you should already have RCK (recovery) hightlighted so press volume up to load TWRP recovery.
Once TWRP loads the top left option is "Install" tap that.
You will see a few choices, select the radio button to install from SD card (external source it may say). Tap the super su zip file: Superuser-3.1.3-arm-signed.zip to choose it.
Slide the slider at the bottom to the right.
This will flash superSU to your device. When done, reboot (should only take a few seconds).
When you boot up SuperSU is installed. ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse

Yes, unlock it. There is no root method for tf201 on JB outside of unlock. An exploit may come up some day but nothing soon I would wager.
I tried to organize it by Al the stuff you need to download first. Then steps to use what you downloaded. It you follow it precisely things would become clearer.

Hi,
Ok I was going through the instructions and downloading all the necessary files and I ran into an issue with downloading the TWRP for JB. Well the link you have allows me to download either the *.img or the *.blob extensions. So I went ahead and downloaded the *.blob extension. I did the MD5 as you recommended and visually checked it with the image on the website and they dont match. I got the below
"b6bae17dac81a126d5d3ad8e27fd5007" which is entirely different than the one on the webpage. I also tried the *.img and no luck there. So I stopped. What do I do now where can I get the TWRP
Thanks
hx4700 Killer said:
Get TWRP for TF201Jellybean:
http://teamw.in/project/twrp2/93
On that page are instructions including a download link for JB BOOTLOADER ONLY!:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
When that is downloaded you can compare the MD( its a good idea to do that). You can find something like winMD 5 generator:
http://www.winmd5.com/download/winmd5free.zip
Use it to generate an MD5 hash of the TWRP download to what it says on the web page. If I remember correctly I had to manually type in the MD5 hash from the page because it was an image I couldnt just copy. Or you can just visually verify with the one generated by winmd5.
Click to expand...
Click to collapse

hx4700killer
I did some googling and found the below link
http://forum.xda-developers.com/showthread.php?t=1510737
the link has "Direct apk link (dropbox)"....Is this what you referred too? I downloaded the file, should I move it to the SD card and run it from within the tablet?. Is there a way to run an apk file.
Also
I downloaded Android SDK on my laptop. I run the eclipse.exe as per the instructions on the website but nothing happens
Thank you
RB

Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.

The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app

ramez75 said:
The link from ASUS has a zip file. So i did download it and extract it to the SD card. Moved the SD card to the tablet but there is no apk file.....Also do i use the twrp file even if the md5 didnt match.
Thanks
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
The second link that says it is for the unlock tool is the APK.

Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
hx4700 Killer said:
Download the APK from the link I gave above. It comes straight from ASUS. I had gotten it 2 months ago and I guess I thougth I had run an installer and copied the APK from there but it is in fact just an APK to download directly.
When you copy it to the SD card nothing is needed to run it. Just tap on the file in a file explorer on the tablet and it will install itself. once installed run the installed unlock app and follow the directions.
Click to expand...
Click to collapse

ramez75 said:
Ok the unlock worked successfully. So my TF201 is unlocked.
Following the rest of your post, next thing on the hit parade is to have the correct TWRP for JB (Open_recovery_TWRP.blob). At this point the MD5sum using WinMD doesnt match the image on the website. Do I still go ahead and use it or will it cause issue....
Ofcourse I dont understand what is the use of the MD5sum number
Thanks
Click to expand...
Click to collapse
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.

Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
hx4700 Killer said:
The MD5 is confirmation that what you downloaded matches what was uploaded to the server. It runs an algorithm against the file contents and generates that long number. When you compare the number to what is on the server page they should match.
If they don't match then HELL NO do not flash it or you will have a bricked device. Redownload it and don't flash anything unless the MD5 matches.
I totally missed that you posted this above or I would have told you sooner.
Click to expand...
Click to collapse

ramez75 said:
Thanks, well then i cant use that link i cant get the MD5 to match. I will google and see if I can find a twrp file that will work for me
Click to expand...
Click to collapse
This is the MD5 hash that you should get:
19d93f4ec4685b8124468684eb2913fc
This is the exact download link I used for my TF201 running the most recent JB Update:
http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.3.1.0-tf201-jb.blob
The file you get is: openrecovery-twrp-2.3.1.0-tf201-JB.blob which is the one I say to rename to twrp.blob
I would NOT flash anything not from the source on this one. If its wrong your device is trash.

Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
hx4700 Killer said:
Once unlocked, power it off. Once off power it onby holding BOTH volume down and power buttons. When you see the menu appear the first option is RCK. press Volume Down to change the cursor to be over the USB logo (two presses of the button) and press volume up. This puts your device in fastboot mode
Back on your computer you should hopefully see a successfull driver install. I got drivers from downloading and installing the Android SDK so you may or may not need to do that. Android SDK
If all is prepared and you are in fastboot with drivers loaded:
On your computer hold shift and right click on the folder where fastboot and the twrp.blob file are and you will see a context menu. Click on "Open Command Window Here"
In the command window paste:
fastboot -i 0x0b05 flash recovery twrp.blob
and hit enter
...
Click to expand...
Click to collapse

Yes, just open CMD and "cd" your way to the directory. Just make sure you end up inside the directory (ie. "...\UBTv1.3.2>")
ramez75 said:
Hi again,
Ok so i got the correct TWRP.blob and I changed its name and put it in the folder with fastboot.exe. i plugged in my tf201 to my laptop followed the power volume sequence. I held the shift and right clicked on the folder but i didnt see "Open command window here". So how do i got about that. Do i use the "cmd" in the run from start to open the black dos screen and change directory (cd..) till i get to the folder that has the fastboot.exe
Thanks
Click to expand...
Click to collapse

Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
hx4700 Killer said:
ADB will now yield Root when you type: SU root and hit enter (grant root privs in the popup)etc...
Click to expand...
Click to collapse

ramez75 said:
Followed all the instructions and seemed all were successfull. I see a Superuse icon created. What do you mean by ADB? and what will yield root when I type?, where do I type?. I dont understand the last sentence, please can you empahsize on it
Thanks again
Click to expand...
Click to collapse
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.

By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
hx4700 Killer said:
Lol, guess I didnt include one of those in the downloads. After flashing TWRP I assume you "Installed" the superuser zip? This is what roots the device.
I got ADB from several sources but this "root method" http://forum.xda-developers.com/showthread.php?t=1886460 from bin4ry is what I have been using: (And no, it doesnt work for the prime because the exploit he uses to run the device in emulator mode doesnt work for us)
http://ul.to/xdevcthz
Your tab must be plugged in to the USB port of the computer of course.
Download the ZIP file and decompress. Use CMD to change directory to the unzipped folder and further in to the "STUFF" folder. type:
adb shell
<hit enter>
after a few seconds you should see a $ prompt and your are in to the console of your tablet.
Type:
su root
<hit enter>
Superuser will prompt you to grant root permissions and I set the setting so it doesnt prompt me every time.
Your prompt will change to # and thats it, you are root.
I don't seem to have the sudo on my tab so every time in a terminal I want root I will type that su root to get the # prompt.
Any apps that need root can now ask for it, you will get that same "Grant" prompt and do so if that is what you want.
Adding:
i just remembered that you said you downloaded the android SDK. ADB is in amongst those files as well.
Click to expand...
Click to collapse

ramez75 said:
By the i still didnt follow the below instructions but it seems i am already rooted because i was able to download titanium backup. So what will the below steps give me more.
Also how do i get rid of apps like Amazon kindle??.....
Below you say that you used the method from binary but you also say it doesnt wok with the prime. So i presume tf201 is the prime, so i still follow the below right
Click to expand...
Click to collapse
What I meant was I use ADB from that root method from bin4ry. He includes ADB.EXE and needed DLL files so its a quick one stop shop for ADB.
Does the adb shell command give you anything? No its just proves root is available. Rootcheckers can also do it. ADB is just a way in to your device from a desktop machine.
I have never removed an APP but I believe removing its APK file from /system/app folder allows it to be removed or does remove it. ( i would save it somewhere in case you need/want it back)

Thank you for an easy to follow way to root a 4.1.1 JB OTA TF-201. It worked exactly as you described.
You may want to let some of the noob users know what in each zip file they need. It really helps if all the files you download are in one location unless you are familiar the windows command line.

I made a script that roots and updates your watch to 5.0.1 in a click.

This version is Mac only sorry, will update for PC this week.
Directions:
1.) Download from https://www.dropbox.com/s/4zd9rz3akcr8zht/lollipop.zip?dl=0[1][1] to your desktop. (file size 124 mb), and extract it the zip.
2.) Open up terminal, and type navigate to the file via cd/Desktop/lollipop .That code only works if the extracted file is actually called lollipop and is in your desktop.
3.) Type sh runMe.sh into the terminal and just follow on screen instructions.
Short version of what it does: Used adb to unlock bootloader, Roots it, Copies over 5.0.1, Writes to cache, and reboots. Then optional install of TWRP recovery.
This code isn't specific to the G Watch, to make it work for your phone, just add two files...
Replace:
update.zip with your factory image of lolipop
LGGW-rootboot.img with temporary boot image for your device to give it root, can find this on forums like XDA TWRP (optional) custom recovery
Be sure to keep the file names the same, as that is what the script looks for! I'm too lazy now, but only 2 things need to be done to make it work for PC...
1.) Get the adb drivers and fastboot, and put it in the lollipop folder, make sure you keep the names the same as the ones in there now.
2.) On the script called runMe and called, everywhere it says ./fastboot or ./adb-mac, get rid of the ./ part, so it would just say fastboot or adbmac

works wirh 4.4W1?
solved, found ota to 4.4w.2

starbase64 said:
works wirh 4.4W1?
solved, found ota to 4.4w.2
Click to expand...
Click to collapse
Yea! It upgrades any version, be i t 4.4 or 4.4.1

Oh, the irony, using android devices on a mac . Can't wait for the windows version though, thanks for your work, man

This worked like a charm for me! I was up and running within 5 minutes -- with no previous ADB experience in my life. I recommend anyone with a mac available to use this if you want to avoid all of the manual work. Thanks again, pal.

Any progress on PC version?

[HELP NEEDED] No launcher, stuck in settings with no buttons HDX 7 3rd Gen

Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!

Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.

Davey126 said:
Appears you have done your homework and have tried most of the solutions I might have suggested. FireOS is intolerant of component name/permission changes (aside from one file dealing with OTA). Best option is to contact Amazon for a one time courtesy exchange if still in warranty.
As a last ditch effort you could try installing Safestrap v4 via adb. If you can get the recovery component installed (requires launching the installed Safestrap app) you *might* be able to flash another rom or repair FireOS. Long shot at best that could leave you with a brick. If you go this path know a factory reset/restore from the native recovery menu *will* brick the device (so don't do that).
Sorry for the bleak prognosis.
Click to expand...
Click to collapse
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?

Mcfinnipoop said:
Thanks man. Yeah, I'm not new to the whole rooting/linux thing, however KINDLE FIRE OS IS The most garbage version of Android I've ever dealt with. I read numerous warnings about bricking, but decided to try anyways.
I tried many more things last night and actually had some luck with pushing commands through ADB to start ES File Explorer from the settings screen, I was able to open apps through ES and manged to get a lot done, however I couldn't get the softkeys/ui keys to appear no matter what I did.
I could power the screen down and it would open back up to ES or whatever App I had opened before "locking" the screen, but Once again I hit a Wall. I checked it this morning, and somehow I got stuck at a black screen when I hit the power button, and now Im stuck in recovery with no option to fastboot.
The Fire is recognized as "Fire" in Device Manager, however I can't seem to get it recognized in ADB to use a Recovery tool or push the Stock OTA rom to the system.
Is there any way of accessing ADB, or enabling USB via Recovery screen?
OR is there a tool similar to ODIN I can use to rebuild, fix up my current OS using adb or usb as mentioned above?
Click to expand...
Click to collapse
Sorry - afraid I can't be of much help. The latest situation is not uncommon after a reboot on a borked device. There is no way to enable adb via stock recovery; would be a security risk even if available. Amazon devices are unique beasts; many common recovery tools/techniques don't work due to component selection and a restrictive bootloader. Even if you did regain limited control pushing an OTA image via ADB would not cause it to be processed as you would need a higher version of FireOS than what's already on your device (4.5.5.1); none exist at present aside from v5. With one exception lower (rollback) versions are summarily dismissed.

Mcfinnipoop said:
Kindle Fire HDX 7" 3rd Generation
Fire OS 4.5.5
Rooted Stock ROM
So here's where I'm at:
I'm stuck in the Settings screen, still have root access, but have no on screen buttons to get out or even open up a home replacement.
Here's every step I can think of since Rooting & junk using several XDA Forums
-Rooted w/ KingRoot
-Installed Gapps w/ no problems
-Changed Names(Not Delete) of the System files using ES File Explorer
-com.amazon.otaverifier
-com.amazon.settings.systemupdates &
-com.amazon.device.software.ota) using ES File Explorer
-Froze Ads app (com.amazon.kindle.kso)
THEN My Battery died last night, Recharged at work this morning and got stuck in boot loop. I should have stopped right there and come to the forums, but like an idiot, I hit reset to factory, foolishly thinkin "hey, that KingRoot was easy enough, I'll root it by lunch time and be good to go"...
I have attempted everything I can think of and can't seem find a solution anywhere, but here's the basics of what I've done so far to try and fix...
1) Installed Nova Launcher in ADB to bypass the Kindle launcher loop but I have NO BUTTONS on my screen to bring up the app selector for "Default Launcher".
2) Used ADB Command to force a Home Key Press with no luck, which leads me to believe the Launcher App isn't running at all?
3) Attempted to Install missing Amazon .apks, and run them using ADB
4) Installing new Launcher, attempt to Force run through command to start Launcher/Home. No luck
5)The last attempt at fixing this thing was using THIS Tutorial to get back to a Stock Fire OS, so I could just start from scratch, but clearly, I have changed the names of the apps letting me do so, as well as had failure to write/copy to my Kindle because it said "permission denied", which I don't understand having root access otherwise...
KingRoot is still installed after Factory Reset as well, so it's still rooted?
I apologize, that's a lot of info, but I figured the most details I can throw out there from the start, might help pinpoint or help find a solution. And Yes, I have scoured XDA for hours for fixes with no results.
Thanks ahead of time everyone!
Click to expand...
Click to collapse
ok this may sound silly but there were 2 things i did to fix a friends kindle stuck on the settings screen as u describe, I went to applications and under that went to the default silk web browser then to most visited , and yahoo link which allowed me to get to the internet and download and install custom notification apk can be found here https://globalapk.co/apk/1/9085-custom-notification-ex-v221 from there it opened and i was able to place the alternate launcher i had adb installed as a shortcut in notification area which allowed me to navigate, and open the alternate launcher and had some control on device, I also think that simply going to an apk site you trust and installing an alternate launcher like that should also work it should pop right up after install depending on how bad your situation is or what was done with the specific kindle, just thought id give some suggestions for alternate way to perhaps fix it gain control over system again it may not work though, hope that helps.

Hopefully this will work
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.

trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
This is a nice write-up that will likely help someone in a similar situation. Thanks for posting

You can help me?
trinityschild said:
Not sure you have this working yet but I had the same issue, spend most of Saturday trying to fix it, and finally did.
Hopefully the below will help
First need to download cm 11 and gapps on you pc
If you have 7” inch you need the Thor things
Cm 11: Thor ROM http://click.xda-developers.com/api...Amazon Kindle Fire HDX 7" & 8.9"&txt=Thor ROM
Gapps: http://opengapps.org (remember take the 4.4 apps)
Check md 5 hashes on both files
I renamed my files cm-11.zip and gapps.zip
The copied them into my adb folder and
adb push gapps.zip /sdcard/Download
adb push cm-11.zip /sdcard/Download
Once this is done we need to launch silk via adb so
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
We then need to get SuperSU installed I went too
http://www.apkmirror.com/wp-content/themes/APKMirror/download.php?id=64309
Download and then you should get the dialog to install, you should get the pop-up to open once it installs do this. You should get the kingroot pop-up to give it root access obviously click grant/yes.
Once this is done, go to settings menu on the Kindle (which you should still be able to get too. ) then apps, all apps, then uninstall kingroot.
Now we need to get to silk again so on your PC
adb shell am start -n com.amazon.cloud9/.browsing.BrowserActivity
Next we need to get safestrap
Link to the Thor apk
http://click.xda-developers.com/api...dle Fire HDX 7" & 8.9"&txt=Safestrap for THOR
Do the same as SuperSU install, then open through the pop-up
Accept the root pop up
Then click on install recovery, then reboot to recovery
Now fingers crossed it should reboot into safestrap recovery.
Do the normal ROM install (wipe, install cm-11.zip from the /sdcard/Download, same with gapps, wipe cache/dalvik)
Then reboot and keep everything crossed and it should boot to cm-11.
Sorry about the poor write up as I have Ms and today is not a good day.
Really hope this helps and works. Cm-11 is buttery smooth on the hdx.
Click to expand...
Click to collapse
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you

Hello Mcfinnipoop,
I encountered the same problem as you, have you resolved the problem yet? I would appreciate it if you could tell me how to fix it.
Thanks!
VoadekS said:
I try to do what you write in this tutorial. But when i reboot in recovery after i installed the safetrap, my kindle go reboot, and display kindle fire for a long, and nothing happen.
Another problem, when i instal de supersu, after i try to remove kingroot and not work, i have only force stop, clear data and clear cache allowed to press.
Thank you
Click to expand...
Click to collapse

[NEWBIE GUIDE] How to Unlock Bootloader/Root and install Addons FireStick 4k

None of this is my work and all recognition goes to the awesome developers that made this possible, I will link their guides in here with some minor notes for newbies like me that may had some issues trying to unlock and root the Fire Stick (FS) 4K
DISCLAIMER: BE WARNED THAT YOU HAVE TO OPEN YOUR FIRE STICK AND IT WILL VOID YOUR WARRANTY, THIS IS NOT FOR THE FAINT OF HEART AND NEITHER THE DEVELOPERS OR MYSELF ARE RESPONSIBLE IF YOU BRICK YOUR DEVICE OR VOID YOUR WARRANTY
Ok, now let's begin:
UPDATE: Per Sus_i, this makes perfect sense:
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."
First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting
In order to unlock the bootloader follow "THIS GUIDE"
I made a quick video on how to open your device and how to Short it using Aluminum Foil:
https://www.youtube.com/watch?v=h4I6ifBLWJ4
Process is pretty self explanitory, make a USB ISO from the image provided on that thread, boot into it and open terminal, make sure you put the file he provides on a RW location, my mistake was that I put it inside a RO folder and it would not load the script, so I mounted the kamakiri-mantis-v1.2.zip unto the /mnt directory of the usb and I was able to run the script successfully, make sure to run the commands quickly as the first time that I it finished the ./bootrom-step.sh script and I left it sitting for 10 minutes to grab a bite, I couldn't run the second script and had to start all over. After the second ./fastboot-step.sh script, your device will be on the TWRP recovery, now on the same terminal page or a new one enter these commands:
Code:
adb devices
adb shell
exit
You should see your device's serial number from the first command with "device" to the right of it and the second command will basically put you inside the device's directory assuming you have established a successful connection. The last command just put you back to your starting point, now open the firefox browser on the FireOS USB and navigate to the URL below
Download the Pre-Rooted Image from "HERE" This image contains Magisk already so you don't have to worry about installing it separately, the image is larger than the available partition on this USB so this is a good time to either get a second USB or if you want to download the file to your local hdd and pull them from there its up to you, then run these commands:
Code:
adb push <your download location you decided earlier here>/mantis-6.2.6.8-rooted_r1.zip / sdcard/
adb reboot recovery
adb shell
twrp install /sdcard/mantis-6.2.6.8-rooted_r1.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
This basically installs the pre-rooted image to your device, after the last command, you should see on your monitor the Fire Stick Reboot and boot to the Amazon GUI Splash Screen, now very important if you followed my previous instructions of deregistering your device before performing all these steps, it should bring you up to the Amazon Initial Setup Screen, now what you want to do is do the following commands before continuing on terminal:
Code:
adb devices *you should see something your screen where the FS is connected to, click accept or enter can't remember*
Now it should show you in terminal your serial number and "device" next to it, meaning you can run adb commands in which you will run the following to disable OTA updates:
Code:
adb shell
su *after this command you should see something again on your screen, click the check the box "Always Remember" and click ok" *
if "su" was successful, you should see something like this:
mantis:/ $ su
mantis:/ # *the hash means you're running as root, if you don't have a "#" you are not running as root"
Than continue with these commands and should get the following results:
pm disable com.amazon.tv.forcedotaupdater.v2
***Package com.amazon.tv.forcedotaupdater.v2 new state: disabled***
pm disable com.amazon.device.software.ota
***Package om.amazon.device.software.ota new state: disabled***
pm disable com.amazon.device.software.ota.override
***Package com.amazon.device.software.ota.override new state: disabled***
After running all these commands exit adb and continue with the normal Amazon Setup including adding your amazon account. After you get to the screen where you can see all the apps, open a new web page browser in firefox and download "This Add-On" , this one is less than 200MB so it should fit on the Fire OS USB, so I would download it and copy it to /mnt for ease of access, go back to terminal and type this:
Code:
adb devices
adb push <your download location you decided earlier here>/AFTV-MM-1.7-6.2.6.8.zip/ sdcard/
adb reboot recovery *it will boot into TWRP*
adb shell
twrp install /sdcard/AFTV-MM-1.7-6.2.6.8.zip
twrp wipe cache
twrp wipe dalvik
reboot -p
Your device will reboot and if everything went smoothly, you should have a rooted amazon fire stick 4k, Congrats :good:

Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Edit: S̵i̵n̵c̵e̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵ ̵c̵a̵n̵'̵t̵ ̵b̵e̵ ̵p̵a̵t̵c̵h̵e̵d̵,̵ ̵i̵t̵'̵s̵ ̵i̵n̵ ̵m̵y̵ ̵o̵p̵i̵n̵i̵o̵n̵ ̵t̵h̵e̵ ̵b̵e̵s̵t̵ ̵t̵o̵ ̵d̵o̵ ̵t̵h̵e̵ ̵s̵e̵t̵u̵p̵ ̵a̵t̵ ̵t̵h̵e̵ ̵b̵e̵g̵i̵n̵n̵i̵n̵g̵,̵ ̵p̵a̵i̵r̵ ̵t̵h̵e̵ ̵r̵e̵m̵o̵t̵e̵,̵ ̵t̵h̵e̵n̵ ̵u̵p̵d̵a̵t̵e̵ ̵t̵o̵ ̵t̵h̵e̵ ̵l̵a̵t̵e̵s̵t̵ ̵o̵v̵e̵r̵ ̵f̵i̵r̵e̵O̵S̵.̵ ̵T̵h̵a̵t̵ ̵w̵a̵y̵ ̵y̵o̵u̵ ̵a̵v̵o̵i̵d̵ ̵a̵ ̵p̵e̵n̵d̵i̵n̵g̵ ̵u̵p̵d̵a̵t̵e̵ ̵n̵a̵g̵ ̵s̵e̵t̵u̵p̵ ̵s̵c̵r̵e̵e̵n̵ ̵a̵f̵t̵e̵r̵ ̵d̵o̵i̵n̵g̵ ̵t̵h̵e̵ ̵e̵x̵p̵l̵o̵i̵t̵.̵ ̵T̵h̵e̵n̵ ̵e̵n̵a̵b̵l̵e̵ ̵A̵D̵B̵ ̵a̵n̵d̵ ̵u̵n̵k̵n̵o̵w̵n̵ ̵s̵o̵u̵r̵c̵e̵s̵.̵ ̵ After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Edit: Update: meanwhile, the fix for the mentioned 'contact manufacturer' error is known...
Take a look here and here.
Edit/Update: Due to efuses (blocking the bootrom access), it isn't recommended to do any update infront of the unlock...

Sus_i said:
Nice guide
Here are a few thoughts from me...
It's important to use the latest kamakiri. The mentioned prerooted 6.2.6.5 is probably a downgrade. A few sticks needs an update of the TZ in order to play prime video. The TZ update is only in the v1.2 Kamakiri or in the 6.2.6.6 prerooted.
Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen).
Click to expand...
Click to collapse
Ops Typo let me edit it, I meant to put 6.2.6.8 on the command lol, and aaaa I see I didn't know the exploit couldn't be patched great info, so than yes I will revise my instructions thank so much
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?

nandroidint said:
UPDATE: I just checked my FS and I'm on 6.2.6.8v1 and didn't receive contact the manufacturer, is it because I sideloaded the manager app after?
Click to expand...
Click to collapse
No. If I remember correct, it has something to do with flashing, i.e. the vendor partition wasn't flashed propperly.
Maybe you flashed not the prerooted!? With the Kamakiri TWRP version is flashing full ota update packages (renamed to zip) also possible... and in the prerooted thread is such a full 6.2.6.8 ota linked.
Edit: Could be that this error is prime video related, idk. rbox said he looks into it soon...
Just for clarification: The prerooted rom is a perfect thing since years.
My suggestion 'avoid any rom flashing' from my last post is just an attempt to keep it simple for beginners.
By the way, if the stick gets all updates in front of the unlock, it makes no sense to update it after the unlock again (unless addon.d support is needed).
I hope that has become clear I very much appreciate all the prerooted stuff

thanx for the tut nandroidint this is exactly what I needed, I wasn't sure how to do the shorting so the video helped out a lot now I'm ready to do this. But I'm sorta a noob when it comes to android so I got few questions tho, 1) what are the main benefits in rooting the fIrestick 4K 2) are there different roms to install? 3) are there root only .apks? 4)also one main thing I would like to be able to do is spoofing the Mac address any idea if that's possible?
5)Oh and lastly what OTB cable do you recommend? sorry for all the questions ?

'std::bad_alloc'
After running the adb push of the manthis.zip Im getting terminate called after throwing an instance of 'std::bad_alloc'.... What Im I doing wrong?

i gave root can i remove amazon services
i dont want google launcher jsut remove services

Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable ?
Can I please get some support guys ? previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.

Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?

davinci2798 said:
Hello, after root i got massage on screen
: android system
There is na internal problem with Your device. Contact Your manufacturer for detalis.
And when im trying to register in Amazon it bringing me back to pairing screen, farest i can go it is wifi connection.
Did i brick my Stick?
Click to expand...
Click to collapse
Did you deregister before rooting like the tut says? This is why I’ve been hesitant on rooting because of the lack of support on this forum

Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.

itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.

tsynik said:
You can use adoptable storage on 4K stick with Add-Ons installed and activated AFTV-XM Xposed Module. It brings adoptable storage support to Settings UI.
Click to expand...
Click to collapse
Nice! That’s awesome thanx for the info and reply.

davinci2798 said:
Yep, it was new Stick, out from box. Not registered at all. I managed massage, but still comminng to pairing screen.
Click to expand...
Click to collapse
Hey so have you figured out what was the problem yet? If so could u explain how you managed to fix it? I’m going to root sometime this week and would hate to run into this issue.

USB drive for storage
itsyaboy said:
Sooo there’s no way to expand the storage? Even after rooted? Just bought an otg cable
Can I please get some support guys previous questions I don’t need answered I found someone on twitter who explained a few things but can someone please answer this.
Click to expand...
Click to collapse
Yes, You can use a USB drive for App loading and Movie storage.
See Troypoint.com for good video.
I suggest a single USB OTG Cable and a USB HUB for your drive.
Then you can add a Keyboard and Mouse which make it MUCH easier to type commands.
Good Luck

How might one do this on a Mac?
Thanks

gogorman said:
How might one do this on a Mac?
Thanks
Click to expand...
Click to collapse
Do what? The only thing u can do on the MacOS is to create the bootable iso usb, you can follow these steps to do so https://www.google.com/amp/s/www.le...-on-an-apple-mac-os-x-from-an-iso?hs_amp=true
After your create the bootable usb just reboot and hold down option and select the bootable usb, once in open up Firefox and download the kamakiri-mantis-v1 and open a terminal window and change the directory to where u have the kamakiri folder, in terminal type cd then just drop in the kamakiri and hit enter. From there u can just follow the tut, FYI the bootable usb you create is a Linux OS so that’s how you can do it on a Mac, you just can’t do the rooting on MacOS, just clarifying Incase that was your question.

Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk

Step by step instructions would be great?
chinkster said:
Sorry I haven't rooted phones in a while and am trying to root my fire stick 4k. Can we get some pictures tutorial pretty please
Sent from my ONEPLUS A5010 using Tapatalk
Click to expand...
Click to collapse
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...

RPM99 said:
I would love that too, I have rooted with Unix before but that was on a Drone(Solo).
I understand about creating a bootable USB drive and booting my PC/Mac by changing the bios to boot first off the USB as step 1.
Step 2 is loading software onto the USB while booted under Unix/Linux???
Step 3 How do you then connect to the firestick?
When do you plug the firestick into the tv and when do you short out the jumper??
I know to some of you these sound very basic but it would be helpful for those of us just learning this environment.
Thanks in advance...
Click to expand...
Click to collapse
The link he provided explains all that https://forum.xda-developers.com/fire-tv/orig-development/unlock-fire-tv-stick-4k-mantis-t3978459 all except for when to connect to the tv, but I assume it’s after running the kamakiri script, btw it’s not software, you just download the kamakiri mantis while in the Linux usb os, open a terminal and change the directory of the terminal to the kamakiri folder in order to run the ./bootrom-step.sh and ./fastboot-step.sh commands
Edit: just follow the main guide from the link above then read this guide after, that’s the best way to understand it.

Better Mobile App

welcome