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
Related
Welp, after spending over 26 honest-to-God hours researching a "cure" for this, I am still without a solution. I hope a kind soul will be able to guide me to the light, because I have been unable to find it on my own.
I am going to try to be as through as possible, if for nothing else than doing a mental checklist to see if I missed some obvious step along the journey. Also, maybe a keen observer will be able to spot what I'm doing wrong.
So,
My Asus Prime is bricked. I'm stuck on scenario 3 (according to this post:http://forum.xda-developers.com/showthread.php?t=1514088&)
In chronological order, here's what happened:
1. I'm running Virtuous Prime 1.0
2. I flash ClockworkMod Recovery Touch v5.8.1.8
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
5. I flashed a new ROM, then hit 'reboot system now'
6. I'm stuck at the Asus logo screen; Android won't boot.
I am able to access recovery and activate Fastboot mode; definitely scenario 3.
Then, also in chronological order:
1. I restarted the tablet, pressed the up volume key and accessed the other menu with 3 options
2. I hit the 'wipe data' option
3. Try to boot Android
4. Still stuck at the 3 option screen
From what I read, this situation is likely the result of clockworkMod Recovery flashing a bad kernel. Supposedly, it can fixed by flashing a 'good' kernel via fastboot, which requires both a "stock kernel" and a more recent clockwork mod recovery image.
I downloaded the SDK package and downloaded pretty much everything, including the USB drivers. I downloaded a stock kernel called stock_9.4.2.21_kernel-signed and a CWM recovery image and placed them inside the "tools" folder.
I opened a command window and while having the tablet plugged in, typed 'adb devices'. I get 'List of devices attached' but then a blank space.
Here's what happened next:
1. I re-plugged in the tablet in Recovery mode to my AMD X64 Windows 7 PC and got an "USB device not recognized" message.
2. I went to Device Manager and under "Universal serial bus controllers" I see a yellow triangle mark besides an "unknown device" option.
3. Right click on "unknown device" and try to update the drivers manually using the Universal_Naked_Driver_Beta_0.6.1
4. When I select the folder in which the drivers are located Windows gives me a message of "the best driver software for your device is already installed". Back to step 3.
5. I try "let me pick from a list of device drivers on my computer" and hit "have disk option"
6. Upon choosing the android_apxusb file inside the universal naked drivers folder, I get the following error: "the folder you specified doesn't contain a compatible software driver for your device (...) make sure it is designed to work with Windows for x64-based systems."
7. Try again this time choosing file android_apxusb; same error.
I heard that some Windows 7 x64 users are having issues installing drivers; that may be my case too. I, however, don't have access to any other Window or Macs or Linux PCs in my house. Still, if this is the issue, then I might try redoing things in a different PC at a friend's house or something.
Bottom line? I think I know what to do, but I can't install the universal naked (nor the official Asus Prime) drivers. What now? Is there an easy fix for Brick scenario 3?
I have read God knows how many discussions on the subject, but I haven't been able to find a solution to my issue. I got no support from Freenode #asus-transformer; some ops were even downright rude. Any help is greatly appreciated.
For what is worth, I'll be donating $50 to whoever is able to help me navigate through this issue and get my tablet back and running.
Thanks again for reading this far.
TL;DR: I bricked my Prime and I'm stuck in scenario 3. I will donate $50 dollars to whoever can help me unbrick it.
Hey,
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Go to the freenode IRC Channel "#asus-transformer" on Freenode (http://webchat.freenode.net/?channels=asus-transformer) and ask for help like described in the unbrick thread!
Greetz
Edit: No need for donate!
hanzo001 said:
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
Click to expand...
Click to collapse
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Thanks for your answer; I'll answer yours
djmcnz said:
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
Click to expand...
Click to collapse
1. Yes, in that order; I backed an empty ROM
2. No, I don't have a valid nandroid backup (go figure; just this single freaking time I forgot to backup before wiping data/cache/dalvik cache)
3. No other ROM on my device. I had a new ROM when I performed the flashing, but when I got to the point where I hit "deleate data" in the 3-option menu, I lost everything on the SD card
4. When I wipe and reflash I'm stuck on the same loop. Maybe flashing a 'good' ROM will fix it; the issue is, my PC doesn't know what I'm plugging in when I connect the tablet to it.
Thank you for your support
Thank you, I'll try a Live CD. I'm downloading now even as we speak.
When that's finished, I'll grab the Linux files.
I guess that sorts of confirms my hypothesis that my main issue is with Windows... *sigh* WINDOWS!
I tried getting help from freenode's #asus-transformer in the past, but... lets say that on the overall my experience could have been better. I'll try again later tonight, where hopefully I'll be able to talk to RaYmAn, a volunteer in the original Diamonback post who is offering supports to users in my specific situation.
By the way, thanks for pointing me with a clickable link to the IRC chat; I've never used IRC before in my life, and getting it to work, dumb as it may sound, took me quite to figure out. Thank you again for your help and support!
chrischdi said:
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Click to expand...
Click to collapse
Thank you for your answer. It is really nice to have a helpful person around; Like I mentioned in my op, my experience on freenodes' #asus-transformer chat was a bit... discouraging. I figured most would want some form of payment for their time, but here you both are, proving that there is kindness in this world.
I'll address your comments:
1. I did wipe /System; after NOTHING I tried on recovery worked, I did manual wiping of everything, trying to boot each time; similar results.
2. I do not have a good ROM on the memory card. Before doing the 'wipe data' from the 3-option menu, re-flashing a good ROM did no good nevertheless. From here is where I started suspecting that it was the fault of CWM not flashing a proper kernel.
3. I tried the advanced restore as well, an like in #1, I tried rebooting each time, just to make sure it would work. But it didn't.
Thank you again for your support. It feels great to know there's someone backing you up out of the goodness of their heart.
Right now I'll try to redo my steps from a Live CD Linux environment; hopefully that'll work. Freaking Windows...
Doktaphex said:
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Click to expand...
Click to collapse
Thank for your support, guys
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
hanzo001 said:
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
Click to expand...
Click to collapse
Hope it works out for the best, life is better with a little Nix in it.
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
You cannot use an external SDcard with any version of CWM for the Prime.
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the thought. I tried that too; for some reason, ClockworkMod Recovery won't read the SD card at all!
Linux
[Update]
In general, this could be going better.
I finally got Ubuntu.
I plugged in the tablet while (the tablet is) on recovery mode, and nothing happens.
I was expecting a pop-up menu, or a notification somewhere acknowledging that I connected a device to the PC, but nothing. I'm just going to assume that Linux somehow knows.
I then downloaded the Android SDK for Linux, unziped, and there's no executable file inside. I'm supposed to download the rest of the file via the terminal, apparently, but this one doesn't work like its Windows counterpart either, so I have no clue what to do now.
Jesus...
Bottom line: I'm in Linux, I downloaded the Android SDK, the universal naked drivers and a stock kernel. Now what?
Try to get ADB running in the recovery mode.
In the files of ViperMOD are the executables. Just open up a console / shell and go to the directory via the "cd" command.
Then in the ViperMOD directory execute "sudo ./adb shell" to try the adb connection.
If the adb connection is ok, mount the sdcard via Recovery Menu and then push a file / rom to the sdcard.
For example with the command:
"sudo ./adb push /media/rom.zip /sdcard/"
(I don't know if this are the correct paths.)
Greetz
Thank you, Chris.
While on the terminal, I'm inside the viperMOD folder. Whenever I try execute "sudo ./adb shell" I get this: "sudo ./adb: order not found"
The tablet is plugged in, and in recovery mode.
I haven't installed Java nor the Android SDK because I haven't figured out a way to do it --why can't Linux be double-click action-oriented? *sigh* Anyway, does not having those things installed have something to do with the answer I'm getting from the Terminal?
If so, how in the world do I install them?
I'm never using Touch Recovery again, my word.
Thanks in advance.
Hey,
are you sure that there is "order not found?"
Try the command "ls" to see what files are available. If there is one, called "adb" you are in the right directory. If there is no "adb" then you have to move to the right directory.
Maybe you could try a "chmod +x adb" first and then execute "sudo adb shell" or such if you are in the right directory.
This is going to sound like a stupid question and sorry if it does. but you can access clockwork still right? what happens when you try to flash back your backup? This is important because I had an error sort of like yours that no one could solve here want to make sure its what happened to me. When i tried to restore the original rom it would get to the part where it was restoring data partition and then error on me reading file or something like that. If thats what you see i know the answer. or at least how i fixed mine.
push a rom
Read NIlsonf post about how to adb push a rom to cwm, you get a stock rooted rom
And adb push the blob file, then run the dd command, unmount staging mount data.
This is what fixed mine, and it looks like it fixed nilsonf's also.
Was this ever resolved? I have the same issue and it looks like I've been through many of the same steps as you've gone through. If you were able to do anything to fix it, please let me know.
I would even up the reward to $100.
Just thinking
Why dont you get someone elses CWM backup and adb push it to the device and restore it from that?
OK so the goal is to get a CM10 nightly build on my Asus transformer prime
What i have done so far is unlock the device via downloading the Asus utility to my prime, that seems to have worked fine.
Here is where i think everything went wrong,
I installed sparkyroot on my prime, it seems to have worked fine but when installing superuser app i see "su file does not exist or have correct permissions" but i went and installed the app anyway.
Now im stuck at rom manager app on my asus, when i open the app i get "you must root your phone for rom manger to function" superuser was not found at /system/bin/su...." .
I obviously didn't root properly.
when i try and press flash clockworkmod touch i simply get "an error occurred while trying to run privileged commands"
I messed up can someone please give me clear and noob friendly instructions on how to get to my end goal of CM10 from where i am PLLZZZZZ
shaneZ95 said:
OK so the goal is to get a CM10 nightly build on my Asus transformer prime
What i have done so far is unlock the device via downloading the Asus utility to my prime, that seems to have worked fine.
Here is where i think everything went wrong,
I installed sparkyroot on my prime, it seems to have worked fine but when installing superuser app i see "su file does not exist or have correct permissions" but i went and installed the app anyway.
Now im stuck at rom manager app on my asus, when i open the app i get "you must root your phone for rom manger to function" superuser was not found at /system/bin/su...." .
I obviously didn't root properly.
when i try and press flash clockworkmod touch i simply get "an error occurred while trying to run privileged commands"
I messed up can someone please give me clear and noob friendly instructions on how to get to my end goal of CM10 from where i am PLLZZZZZ
Click to expand...
Click to collapse
I suggest you go here first http://forum.xda-developers.com/showthread.php?t=1426502 download and install naked drivers
Then go here http://forum.xda-developers.com/showthread.php?t=1774352 download and unzip nvflash
Then go here http://forum.xda-developers.com/showthread.php?t=1615990 download twrp and place it inside the nvflashpack directory where you see adb.exe
Then go here http://forum.xda-developers.com/showthread.php?t=1782413 download EOS 3
or
Go here http://rootzwiki.com/topic/32357-rombaked-tf201-blackbean-2-8-15/ and download bakedbean 2
Put either one in the nvflashpack directory where adb.exe is or if you have an external sdcard, load a rom onto it (preferred method)
I am not a fan of cm10 though it has some nice features I wouldn't start with it...
Now the hard part....
Go here and follow the instructions http://androidroot.mobi/t3_nvflash/
As per the instructions put your prime in fastboot mode...
to you start a command prompt, open the nvflashpack directory where adb.exe is. Press and hold shift while rightclicking in the window, select open command prompt here
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
Work your way all the way to the end until you see coming soon...
In the end you will have the modofied bootloader required for the lastest version of twrp (cwm doesn't work as well as twrp on the prime)
Now follow the instructions to install twrp this can be done through fastboot or through goo manager (download from market if you want to go the goo manager route)
Once that is complete with the prime still plugged into the pc, boot into twrp, now depending on if you have put the rom on an external sd card or not... if on sdcard, have it inserted before going into twrp, and install the rom from the card otherwise you can adb push the rom to the prime it will be adb push /name of rom.zip/ sdcard Note that the rom has to be in the same directory as adb.exe for this to work otherwise you need to type the path....for the name of the rom I suggest right clicking the file, go to properties and copy the name, then right click and paste in the command window... this eliminates mistakes.. and don't forget the.zip part.. the push will take about 5 minutes...
Then install the rom from twrp.....
No need to root as all custom roms are rooted... if your not comfortable with this, do lots more reading.....if something goes wrong you know the drill... I am not responsible.. blah blah blah...
Good luck!!!!!
I am attempting to build a compatibility file for my Polaroid PMID1000. Unfortunately this old device uses a special touch screen driver I have never found on other devices, and it is using kernel "3.0.8 #139 PREEMPT". I am using an older rom found here: http://www.slatedroid.com/topic/64378-rom-carbonrom-422/ and have success booting on my compatibility file. The issue is the touch screen is not interacting with the OS (there are other issues but I want to tackle this first). The kernel allows me to boot and the android GUI starts up (I can interact with a mouse just fine). Getevent shows me interacting with the screen so touches are being generated, but they are not getting to the GUI. Looking for any help you may want to provide.
Files can all be found here, including a logcat, dmesg, lsmod my compatibility zip as well as the carbon rom and gapps . https://drive.google.com/folderview?id=0B0c1jpaziDZ-S2hoczN0U0FiN3M&usp=sharing
going forward not backward
So I built a new kernel (3.0.101+) and have the gsensor and touch working now. Install the Carbon ROM, the GAPPS and the new compatibility file: PMID1000_carbon.compatibility-v1.zip
The only issue I have is no sound from the speaker, if you plug in a head set the sound is there.... anyone have an idea on this?
Domenic
new script.bin for sound and aokp support
I have updated the file and there is now sound support. I had a typo in my script.bin! I have also included a zip file for aokp_907_unofficial_2013-08-03.
PMID1000_carbon.compatibility-v2.zip
PMID1000_aokp.compatibility-v2.zip
Domenic
the process
domenictroilo said:
I have updated the file and there is now sound support. I had a typo in my script.bin! I have also included a zip file for aokp_907_unofficial_2013-08-03.
PMID1000_carbon.compatibility-v2.zip
PMID1000_aokp.compatibility-v2.zip
Domenic
Click to expand...
Click to collapse
So...I have the PMID1000, but what exactly is the process for this? I plan on using the CarbonROM(most likely). I have the Livesuite software on my pc, and all. I'm just curious as to what steps I need to take to make this thing work well? haha
I apologize for my ignorance,
Jonathan
jonathanhatch88 said:
So...I have the PMID1000, but what exactly is the process for this? I plan on using the CarbonROM(most likely). I have the Livesuite software on my pc, and all. I'm just curious as to what steps I need to take to make this thing work well? haha
I apologize for my ignorance,
Jonathan
Click to expand...
Click to collapse
Firstly remember that all data will be wiped from the tablet, and the camera's will not work; also I would not expect a beginner to attempt this so I will not write up a detailed step-by-step, but an overview of the files and when/how they will be used. Of course you will require a computer and a USB connection to the tablet and the drivers required. I am not certain if Windows Update will find them, so you may need to find them as well.
With all the above in mind lets start (note I am doing this from memory as I do not have the tablet handy):
You need to start by installing cwm (cwm6028-a10-9part-v2.zip) on the tablet. For this you will need a copy of adb.exe, which I have provided as the file adb.zip on my Google Drive which includes the files you need. The tablet will need to have USB Debugging enabled.
Enable USB Storage
Unzip all files in cwm6028-a10-9part-v2.zip and transfer them to the tablet.
Turn off USB Storage
From a command prompt (cmd.exe in windows) change to the directory when you have unzipped adb.zip and run the command 'adb shell' you will get another prompt. Note I have 'quoted' the commands but the quotes are not required when you run the commands.
type 'cd /mnt/sdcard'
type 'ls' and verify the file recovery.img is in this directory and if it is
type 'cat recovery.img > /dev/block/nandg'
once this command has finished type 'echo -en "boot-recovery\0" > /dev/block/nandf; sync; reboot'
The tablet will restart in cwm.
To move around in cwm use the home button to move the selection down and the power button to select.
copy the following files (do NOT unzip them) to the same directory as you put adb.exe.
CARBON-JB-UNOFFICIAL-20130619-1010-907.zip
gapps-jb-20130812-signed.zip
PMID1000_carbon.compatibility-v2.zip
On the tablet choose the option "install zip from sideload"
At the windows command prompt type 'adb sideload CARBON-JB-UNOFFICIAL-20130619-1010-907.zip'
Note you may need to run the command again if your computer has not found the tablet device.
Repeat the above two steps for the other two zip files.
Once completed on the tablet choose the option "wipe data/factory reset" then the option "reboot system now" Note the first reboot of the table will take longer than you would expect, don't worry you will get back to a functional tablet in about 5 minutes. Note the "wipe data/factory reset" is extremely important as you will not get a functional tablet if you skip this step.
Domenic
WOW. Far superior to my half-root/play store work around I was using before.
Thank you! This works really well on my PMID1000. Great instructions too!
I've noticed that with the Carbon ROM I don't have on-screen volume keys. Is that normal, or should I try clearing the cache, and doing another wipe data/factory reset?
I'm going to try the AOKP ROM next.
Thanks again, Domenic! It's hard to find anyone doing any development for these. I guess that means I should upgrade sometime haha
Jonathan
P.S. Any chance you know how I could adjust the internal partition to allow more space for apps?
I have not found a way to get the volume on the bottom screen, these builds do not allow for it.... but you could try an app from the play store, look for status bar volume and you should find something. The one other real issue I have besides the camera not working is the speakers do not disable when you plug in a head phone. It is fine until you want to use it on the bus and don't want to distract anyone.
I am not certain that you can make the app size larger, but you could try to install Link2SD from the playstore. It allows you to move (link) applications to you SD card freeing up space.
PS I am not a real developer, just a bit of a hack to cobble this together...
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
MrsPurchase15 said:
Hello All! I'm sorry, I'm very new to this. Can someone please point me in the direction of instructions that I need to follow in order to root my son's Star Wars Nabi? I'm not sure if it's a nabi 2 or not.. I can't find that anywhere. We just bought it for Christmas. The internal storage is used up and the games won't move to the SD card - so, I figured my only option was to root it. There are so many pages out there with root instructions and I'm not sure which ones to use. Any help would be greatly appreciated.
Click to expand...
Click to collapse
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
aicjofs said:
What is the name of the device in the "about tablet" tab in settings?
It's probably closely related to the nabi2S of i were to guess. You can either try a root method like Kingo root or a TWRP method. Since you are the first person I have seen here with a Star Wars I don't have all the answers.
-If you use Kingo there is no backup to help you if something goes wrong.
-If you use TWRP method there may not even be a version of TWRP that will work, and initially you will not want to install TWRP but run it from ram. So the commands will be a bit different then what you see on the forums. With that method though you will have a backup.
Click to expand...
Click to collapse
It doesn't have a name :/ It has a model number (SNB02-NV7A), an edition number (SNB02-NV7A-US-SW), android version (4.4.2), a kernel version (3.1.10) and then a build and hard ware number.
I appreciate the advice though. Thank you!
MrsPurchase15 said:
I appreciate the advice though. Thank you!
Click to expand...
Click to collapse
SNB02-NV7A is the model number for the NABI2S. It's likely the Nabi2S TWRP will work for the tablet. To use it though you will likely have to unlock the bootloader and that will erase all your personal data on the tablet. It's the safer method since you will have a backup of your tablet, but will require you to get your hands dirty.
You can read through this http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 and see if it's something you want to try.
Using the above linked thread as the basic outline, in general you would:
-Setup adb/fastboot and the windows driver.
-Unlock the bootloader(wiping all personal data on tablet)
-"fastboot boot" NOT "fastboot flash" the Nabi2S TWRP recovery to the tablet RAM.
- backup the recovery, boot, system, and addon(preload) partitions. Then you can always recovery the tablet if something goes wrong, and help others that need to recover their tablet.
-Download SuperSU and flash from TWRP to obtain root.
I can help with more detailed instructions but if it's something that seems uncomfortable to try then I don't want to type it all out. Again a kingo root or other root method will likely give you root, I personally like having a clean backup before beginning and there is none in existence yet.
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
MrsPurchase15 said:
Thank you so much! I am absolutely willing to try it. I can't do much worse to it then the state it's already in.
Click to expand...
Click to collapse
Again the Nabi general information thread is going to be the biggest help in understanding what needs to be done. That information is here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 The procedure below isn't as long as it looks I tried to add some troubleshooting stuff along the way.
Best to have a mircoSD card for this well at least 4GB. Start with the microSD in your computer if possible.
1) First you will need to grab all the files you need:
-Drivers: Refer to drivers section #4 in the General Info Thread. Your choice if you want to try PDAnet, NabiLab, or Universal Naked Drivers. The NabiLab drivers are self installing and work pretty good in a lot of situations but not always. Download which ever one you choose to your computer. I'm going to talk about Nabilab and Universal as first resorts, we will revisit PNAnet if you are having driver issues.
-ADB and Fastboot tools. Here it's best to refer to section #6 in the General Thread. Specifically:
Download and install this package(pay attention to where you install this as you will likely need to put files in there later): http://forum.xda-developers.com/showthread.php?t=2317790
From your start menu select "Minimal ADB and Fastboot" this should open a command prompt where you can type commands
If you didn't pay attention or forgot where you installed the files, at the command prompt that opens type "explorer ." The period is important, explorer <space bar> and a period. So type what is between the quotes.
-TWRP for the NABI2S. Get that file here: TWRP for Nabi2S
After this step you should have downloaded 3 files and the ADB/fastboot files you should have installed. That leaves the remaining 2 files. One should be NABI2S_TWRP271.img, copy that file to the folder where you installed ADB/fastboot(remember you can find that folder by selecting Minimal ADb and Fastboot from your start menu and typing "explorer ." as explained above.) The remaining file is the which ever driver package you picked. If it's universal naked extract the zip file to a place you know. If it's Nabilab drivers go ahead and install them. PDAnet we will try later if these 2 don't work.
2) Boot the Nabi to fastboot with the USB cable plugged in to your computer. Also open device manager on your computer so you can see when the interface comes up. I don't have a Nabi2S so this may be not exactly right. Start with the tablet off. Press and hold the power button AND the vol up buttons at the same time. At some point you should boot up and have a small text menu in the top corner of the screen.(If that doesn't work try power and vol down buttons). One of the menu items will be fastboot protocol. You will want to highlight that text using the volume keys, and then select it using the volume keys.(again I an not sure which is which. Vol - might change which is highlighted, and vol + will select that line, or vice versa, remember which does does what as you will need it later on). Keep trying combinations or timings if it's not working. When it's right your computer will acknowledge a new device plugged in and the device manager screen should show a fastboot or unknown interface.
3) Getting the drivers working. If you chose the Nabilab drivers they should automatically install, and in device manager you should see and item called Android device, and when expanding that entry some bootloader or fastboot interface(When you see this you should be done with this step). The tablet will also switch the text on the screen to say something like "continue", "bootlader", blah, blah. If you went with universal naked drivers this is where you would locate the unknown or fastboot device with the yellow exclamation mark and manually install the driver by pointing them to the folder you extracted(There could be driver signing issues depending on which version of windows you are using. You will have to google "disable windows driver signature enforcement", but basically you will reboot the computer disabling driver signature enforcement. Hopefully if you picked the Nabilab drivers and they work on your computer this step will be pretty painless and not as long as it looks.
4) Unlocking the bootloader. If you have the command window open now great, if not from your start menu select "Minimal ADB and Fastboot" this should open a command prompt. REMEMBER this step will erase all you data on the tablet, game saves, pictures, etc.
Get ready to acknowledge some text on the tablet itself as you have to be pretty quick using the volume keys to highlight and select(Same function as what you noted in step 2). At the command prompt type:
Code:
fastboot oem unlock
OR
Code:
fastboot -i 0x0489 oem unlock
On the tablet some text will pop up asking yes or no do you really want to unlock the bootloader? The selection is made with the volume keys. You should see some confirmation of erasing tablet and completed.
If this step isn't working when you type the command i.e. "waiting for device" the drivers probably still aren't installed correctly. If something failed in this step you may be forced to reboot the tablet and get back in fastboot mode(step2)
5) Install TWRP. With tablet in fastboot mode. Type at the command prompt:
Code:
fastboot boot NABI2S_TWRP271.img
or
Code:
fastboot -i 0x0489 boot NABI2S_TWRP271.img
If you are getting file not found errors the NABI2S TWRP file isn't in the folder. If all goes right the tablet will boot to TWRP. This is where we may have problems as I'm not sure if the NABI2S TWRP can boot the Star Wars Nabi. If it's not booting then we are pretty much done at this point...
6) Getting SuperSU(root). If the tablet booted TWRP. Download this UPDATE-SuperSU-v2.46.zip. Copy that file to your microSD you have inserted in the computer. When that is done safely eject the card from the computer and put it in the tablet.
7) In TWRP select the "mount" tab and check MicroSD(external storage) and the check box should become checked.
8) Make a backup. Select the "backup" tab in TWRP. You will have the options to backup "recovery" "boot" "system" and "preload(or addon)" select all 4 of those. Then select the backup location as MicroSD(external storage). Swipe to backup.
9) Only if step 8 worked install root. Select the TWRP "install" tab. Back out to the highest level, and find external_storage. The UPDATE SUperSU zip should be there. Select it and swipe to install.
10) Only if the step 8 and 9 worked go to the "reboot" tab and reboot. If they didn't work. Press and hold the power key until the tablet shuts off, and we can troubleshoot. If you rebooted the tablet will take a long time to boot initially since you wiped the tablet and it will have to rebuild data. You can then reset up the tablet.
11) Get superSU from Play Store and verify root.
12) If all this work your backup will likely be a benefit to future users so sharing it might be something to consider.
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
MrsPurchase15 said:
Well.. I followed everything above and it all appeared to work perfectly - however, I still can't access the microSD card to store games. Any ideas?
Click to expand...
Click to collapse
Are you using an app to do this(like link2sd)? Or just hoping root alone would allow you to do this?
I was hoping the root would allow me but I take it that's wrong, lol.
MrsPurchase15 said:
I was hoping the root would allow me but I take it that's wrong, lol.
Click to expand...
Click to collapse
Haha. Understood. You do need root to do it, but root is needed for the apps that can make it possible. My kids never had the problem when they had their old Nabi2's so I'm not as much help on the "how to" portion but I understand how the apps work. Read through this thread to gain some understanding of what it takes now that you have root. http://forum.xda-developers.com/showthread.php?t=2086338
There is another way also where you stop using internal storage altogether and use an external by editing the ramdisk but it has some limitations as well.
This was awesome i have the same star wars edition and everything works well i even made a backup which i can post and i used the 3.0.1.3 kernel backup to restore the tablet and it still worked
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