Related
This guide was written to provide more specific information for installation instructions than the OP below.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
OP for Tubutnu by x3maniac
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.
Instructions for installing new kernels for SBK1.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.2. Download the updated kernel from the OP.
a. Extract the .img file into the \bins directory of the installation application. You do not need to rename it because the command you enter in step 3 part b indicates the name of the kernel file.3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 6 whatever_the_kernel_filename_is.img
c. The filename is the name of the kernel you extracted and copied into the \bins directory. This name can really be anything so long as the command you enter reflects that filename.4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android. Boot to Linux now.
6. Download the supplemental kernel file to the root of your filesystem That is the / directory.
a. Open terminal and type this and press enter: sudo wget http://novaspirit.com/tubuntu/kernel_sup.tar.gz /
b. Then type this command and press enter: sudo tar zxvf /kernel_sup.tar.gz
c. This supplemental is installing modules and drivers to the appropriate locations.
d. Reboot.7. Please understand names of files especially the kernels and updates will change periodically. The commands and methods of extracting have not changed at this point so substitute the appropriate filename and you should be good to go.
For SBK1 devices, the installation of a custom Android ROM using recovery is very similar to updating the kernel instructions in the post above.
Instructions for installing custom ROM's for SBK1 with Lubuntu installed.
1. In your Tubuntu installation directories, locate transformer.bct and bootloader.bin.
a. Copy these 2 files to the \bins directory of the Tubuntu installation application.3. Copy the file cwrrecovery.img to the \bins folder.
a. You should be able to substitute a newer recovery file than what comes with the Tubuntu installation application.2. Download the zip file of the custom Android ROM you wish to install.
a. Copy it to either your Internal SD card or External SD card. Depending on the recovery version you flash you may not be able to use your Internal SD card.3. Open a command prompt to the directory of \bins for the Tubuntu installer application.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 cwrrecovery(orwhateverfilenameyourrecoveryis).img
c. The filename cwrrecovery.img is the name of the recovery that comes with the installer application. Please substitute appropriately if you are going to flash a different recovery application. You can also use TWRP just use the appropriate .img file name.4. After the copy completes you will be back at the command prompt.
a. Type this command and hit enter: nvflash -r --go5. Your tablet will reboot after the nvflash mode is exited and depending on your configuration it will boot to Android.
a. Now you want to boot to the Android recovery. Do that by powering off the tablet and booting like normal into recovery mode. This should be volume down and power. Hit volume up when prompted to do so. Flash your ROM according to the ROM owner's instructions. I recommend to complete your ROM's installation set up before proceeding to step 6.6. You must now flash your Tubuntu Linux kernel back or you will not be able to boot into Linux. Follow the instructions again from the \bins directory using the command prompt and putting your tablet back into APX mode which is volume up and the power button until the Tubutnu installation application shows green for APX Detected.
a. Type this command and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
b. Type this command and hit enter: nvflash -r --download 5 whatever_the_kernel_filename_is.img
c. Type this command and hit enter: nvflash -r --go7. You should now be back into your Android ROM again. From here simply power off and boot into recovery using volume down and power. Then hit volume up when it says to on the screen. If Linux boots without issue then you have successfully reinstalled your kernel.
I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
Click to expand...
Click to collapse
sainthout said:
I did exactly what's in the post. With Tubuntu 0.4.7, Prime ROM, Lubuntu V1.1-rc1 (12.10) and the *updated kernel 12/10/2012* (without supplements)
But after Android initial boot, I reboot but it doesn't finish booting Android. It stops here:
http://i50.tinypic.com/2zswdw3.jpg
Anything I can do to fix this? Android does boot properly, but Lubuntu doesn't
If anyone knows how to fix this with only Ubuntu (and without Android) then that is fine too..
Click to expand...
Click to collapse
0.4.7 fixes the issue with sbk1 and you don't have to do it with these instructions anymore.
However I did try the newer kernel and got stuck at the same spot you did using my instructions just before the 0.4.7 was uploaded. Go to the original thread and post the issue there.
Thanks for the quick reply! Will post the issues
Outdated Thread But Valid Information
This thread is now outdated. X3Maniac has updated his Tubuntu installation application (0.4.7) to fix the issues with installing kernels and recoveries for SBK1 devices.
The information in this thread is still valid for behind the scenes and you can still use the wheelie and nvflash as standalone items if you wish to do something with your device outside the scope of the main thread.
Thanks for all the thanks from users!
Found a bug with 0.4.7. It's possible the tab may not reboot into Prime automatically with this version. When the dev has time it will get updated. If it doesn't reboot and the Tubuntu application says everything is done, manually hold power and let it reboot to Prime to finish installation.
question..
TomTcom said:
This guide was written to provide more specific information for newcomers.
The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do.
1. Download the newest “tubuntu v0.x.x” without Prime (system.img) or Ubuntu.img as it is written in the OP.
a. This download contains the application, boot.img file, and basic kernels available at the time of this guide needed for installation. There will be updates for kernels specific to an Ubuntu image as the developer is able to work on them. Check for new downloads and posts.
b. The download also contains drivers and installation for APX mode located using the “Other” tab in the application.
c. This download does NOT contain the Linux operating system nor the Android ROM.2. Extract all the files in “tubuntu v0.x.x” to a Tubuntu folder wherever you wish. 7-Zip is the zip program of choice but any others should work fine.
3. Download Prime ROM [stock hc w/ root](system.img)
a. This download is the system.img that contains a root enabled Android ROM.4. Extract the system.img file from this download.
a. Copy this file to the \images directory. The images directory is a sub folder of the TF-101 Ubuntu Installer application that you extracted in step 2.5. Download the Ubuntu image of your choice.
a. Currently there are 2 Lubuntu downloads. Read the bullets and determine which one you want.6. Extract the image file of this download and place it in the \images directory. Rename this file to ubuntu.img.
7. Open the TF-101 Ubuntu Installer application.
8. Connect your usb cable to the TF-101 and the computer.
a. Shut down the tablet.9. Enter APX mode by holding the volume up button first, then hold the power button until you hear the usb sound from the computer.
a. Your screen will be black and the TF-101 Ubuntu Installer application will light up green and say APX Detected if you correctly entered APX mode.10. Change the dropdown to SBK 1 located directly below the green APX Detected text.
11. Click on the Flash tab.
a. Select Android/Ubuntu and then hit Flash.
b. Android is the primary boot option here.12. You will see an install log in the right of the application. Mine takes about 15 minutes or so but you will know you are finished when you see the Android ROM load as well as the red text APX NOT Detected (in case your screen is off when you come back).
13. Proceed with setting up Android. DO NOT reboot or power off before the initial Android set up is complete.
14. Once completed and you wish to enter Lubuntu, power off the TF-101 and hold down volume down first and then power. You will see your screen say hit volume up in 5 seconds for recovery. Hit volume up within 5 seconds and it should boot your Linux graphical desktop environment.
Click to expand...
Click to collapse
i just succeeded dual booting into ubunto.the prime rom just booted...can i install eos jb rom and still dual boot to ubuntu? thanks in advanced
Yes you can. You will need an updated recovery .img file that supports jb. You temporarily flash the new recovery boot into it then install the new rom. See my post on installing updated android roms. Its the third one I think.
oh sorry for the silly question,,i got it now thanks a lot.. nice job
Hi there,
First off, thanks for the tutorial and hard work!
I've been able to successfully install Lubuntu v1.2 and Lubuntu V1.1-rc1 but I've run into issues with both that I'm hoping you can help me with.
When I installed v1.2, my wireless adapter didn't work and I wasn't able to copy any files (kept saying I was out of space, probably a mounting issue).
When I installed v1.1-rc1, things seemed to work well (wireless worked) but when I tried to upgrade the kernel to 3.1 following the instructions, my mouse pad stopped working and so did my wireless adapter again. I saw that there is a way to fix the mouse pad but it seemed to require an internet connection. Any idea what I did wrong or how to fix the wireless on either v1.2 or on v1.1-rc1 with the 3.1 kernel?
Thanks!
You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/
TomTcom said:
You're welcome.
To solve the space issue, open terminal and execute this command: sudo resize2fs /dev/mmcblk0p8
The wireless adapter isn't working because the 3.1 kernel is not stable. Do Not Use It.
Get this from the OP:
Kernels
#470 Controlling your CPU for stability
Stable kernels (use with care for OC version)
[extreme]
2.6.36 - [cpu 1.6 ghz] [gpu 400mhz] - download
benchmarks - blowfish score 30
glxgear - 70 fps
Then get the supplement from the OP:
kernel supplement - 2.6.36.4-1210.zip
extract and copy the kernel suppliment to /lib/modules/
Click to expand...
Click to collapse
Awesome, works like a charm. Thanks again!
Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!
Treizy said:
Not sure if I'm the only one experiencing this, but every now and again whenever i click anywhere it thinks I'm trying to move a file (shows the little file icon when I move the mouse). Is this a known bug or just something in my settings I need to change?
Thanks!
---------- Post added at 12:40 PM ---------- Previous post was at 12:19 PM ----------
I also just found that my sound stopped working. It was working before when I used the instructions from the original post (using alsamixer) but I guess somewhere along the way of me messing around I broke it. Here is the error output when I try to play an mp3 in mplayer:
Code:
==========================================================================
Requested audio codec family [mpg123] (afm=mpg123) not available.
Enable it at compilation.
Opening audio decoder: [ffmpeg] FFmpeg/libavcodec audio decoders
AUDIO: 44100 Hz, 2 ch, floatle, 128.0 kbit/4.54% (ratio: 16000->352800)
Selected audio codec: [ffmp3float] afm: ffmpeg (FFmpeg MPEG layer-3 audio)
==========================================================================
Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting.
MPlayer interrupted by signal 6 in module: ao2_init
I've tried searching for a solution but still no luck. I've also tried other players and they don't work either. Any help would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse
See KingZaks post for sound settings. It's in the op and his signature.
The clicking shouldn't do that every time. Did you extract the supplemental zip and are you using the 1.2-1.6ghz kernels?
Hmm, I'm thinking of installing fresh to see if things get fixed. Is there a way to do that without touching the Android partition? I don't want to have to reflash EOS and what not. Do I just not include the Prime img in the images folder?
Thanks!
A Terribly Confused Noob!
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky
TheArtfulDodger said:
Hello:
I am terribly confused and I hope that someone can help me to understand a few things! I am sorry if I don't understand all the links but they seem to go round and round. Right no I have no less that 25 tabs open trying to figure out the first step.
So, to my first question (probably the first of many): This guide was written to help "newcomers", of which I am definitely one. But, right under that statement comes the statement "The Tubuntu installer application will not install the updated kernels for SBK1 devices and the manual procedure in post #2 will tell you what you need to do." Does that mean I'm actually supposed to start at Post #2? But Post #2 assumes I already have "Tubuntu installation directories", which I don't have so I can't locate the two files.
I am attempting to be a user of Ubuntu on my Transformer, not a developer - I take my hat off to all of you that have put your Transformers in harm's way developing the techniques and software that I want to use, but the instructions are terribly confusing for someone not familiar with all of the terms!
Any help would be most appreciated and I thank you in advance.
Sparky
Click to expand...
Click to collapse
Hey Sparky, there's no more active development on this just so you are aware. That means you can make your own images for newer Linux builds if you wish but things such as hardware acceleration and kernels will not be updated.
In step 1 of my guide you are going to the OP link by the dev who made the Windows based Tubuntu application.
Go to where you see these links:
tubuntu v0.4.7 [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.7 (jan, 3 2013)
tubuntu v0.4.6beta [1mb] Executable ONLY - download v0.4.2b and replace the tubuntu.exe with this one
download v0.4.6b (dec, 10 2012)
tubuntu v0.4.2beta [78mb] without Prime(system.img) or ubuntu.img
download v0.4.2b (dec, 7 2012)
tubuntu v0.3alpha [57mb] without Prime(system.img) or ubuntu.img
download v0.3a
Prime ROM[stock hc w/ root](system.img)
download
Download tubuntu v0.4.2beta (78mb).
Download tubuntu v0.4.7 (1mb).
Extract the files to whatever location on your Windows machine.
The 1mb file is a replacement of tubuntu.exe file. So just copy/paste and overwrite that file on your Windows machine.
Do you know how to put your tablet in APX mode? If not, you open tubuntu.exe (you might need .net 4.0 Microsoft framework to run the tubuntu.exe). With the tablet off and usb connected to your windows machine, hold volume up and power. The application tubuntu.exe should have a green indicator that it's connected. Change the dropdown to sbk1.
From there you can choose how you want to flash, such as android as the default boot and linux as the secondary boot.
Ignore.
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Path question
delete
Thanks a lot for this tutorial, i was searching for a way to root my kindle 2 (non HD) for the past 1 week and i almost felt like throwing it out of the window. Finally this helped me, installed SU successfully. Cheers!
Re-Rooted Kindle Fire 2 on Windows 7 X4-Bit
Finally, I'm going to bed!
Anyway, THIS is what I did.
BookCase said:
Finally, I'm going to bed!
Anyway, THIS is what I did.
Click to expand...
Click to collapse
Noobie question what do you actually type in when you add it to the path? Thanks
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
does this guide work to install a rom in Kindle Fire 2nd gen?
adisagio said:
does this guide work to install a rom in Kindle Fire 2nd gen?
Click to expand...
Click to collapse
No. It is a quick guide on how to root a 2nd gen
Recovery
Do we have KF2 recovery until now?
Follow Up - Feedback
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
bryanchapman9999,
Nice work bryanchapman9999, very solid How to.
when am trying to open the SDK manager nothing is happening. Can any1 help me ?
Open as admin ?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Thanks it worked!!
bryanchapman9999 said:
Device = Kindle Fire 2 and Windows 8 64bit
Although I have tagged this as a howto, its more of a compilation of what others have done - many thanks to them. This is the first howto post I've done so please thank the guys that made this happen - not me.
There are many, many posts showing how to root the kindle fire (HD and normal) but it took me a while to piece together all the information I needed to root (re-root actually!) mine.
As I've just re done mine and its fresh in my head, here it is.
Download the Android SDK and unzip it and copy the 'adt-bundle-windows' folder to your documents folder
Navigate to Documents/adt-bundle-windows/sdk/tools and run the android app - this opens the android SDK manager.
Go to tools - Manage-addon-sites and select the User defined Sites tab. Click new and add the following url
http://kindle-sdk.s3.amazonaws.com/addon.xml
Hit OK and close
Now scroll to the bottom on the SDK manager and under extras will be 2 kindle fire options 'kindle fire device definitions' and 'kindle fire USB driver' select both and install.
Now close the SDK manager.
If you have previously used your kindle on your PC, plug it in and go to device manager and un-install the drivers for it - now unplug it.
Navigate to \Documents\adt-bundle-windows\sdk\extras\amazon\kindle_fire_usb_driver and install the kindle USB drivers
Now add the location of the ADB.exe file to your path
You should now be able to plug in your kindle and execute adb devices and see your kindle - that means your good to go.
Download this tool made by Bin4ry - http://forum.xda-developers.com/showthread.php?t=1886460
Unzip the file you download.
Now goto the platform-tools folder of the SDK and copy all the files in here into the 'stuff' folder of the file you just unzipped.
Now simply run the 'RunMe' batch file.
Now, you mileage may vary of course but this is what worked for me.
Some threads that I used for reference;
http://forum.xda-developers.com/showthread.php?t=2035334
http://forum.xda-developers.com/showthread.php?t=1886460
http://forum.xda-developers.com/showthread.php?t=1893838
https://developer.amazon.com/sdk/fire/connect-adb.html#Prerequisites
Click to expand...
Click to collapse
Im a complete noob and was kind of lost through the process. Finally it took me around 40 minutes to complete the whole process. Thanks a lot!
Some things to consider for noobs like me:
1. You MUST have Java SDK installed in order to open the "Android" App (SDK Manager) (I didnt have it)
2. It is important to delete the drivers of the kindle fire at Device manager (while is connected) if you have used (connected) it before. After deleting the drivers disconnect the kindle fire and install the drivers again.
3. adb.exe is located at \adt-bundle-windows-x86_64\sdk\platform-tools\ (sorry I didnt know where it was located)
4. When referring to "execute adb devices" it means you should type in a command prompt "adb devices" (I was looking for an .exe or a .bat file named "adb devices"!) LOL
5. After running "adb devices" you should be able to "see" your kindle device as a large alphanumeric sequence. Now, this was the tricky part for me... I tried several times and couldnt "see" my kindle listed! So I figured out that maybe there was a different kind of connection I could configure and indeed there was! I had to set my Kindle Fire to be in ADB Debug Mode. This is achieved by going to Settings->Security->Enable ADB And after that it was a piece of cake! I downloaded the file made by Bin4ry and followed the rest of the instructions.
Excellent tutorial bryanchapman9999!! I really appreciate your time and effort to gather up this information!
Regards.
Root the Kindle Fire 2 (non HD)
Divanus said:
Im a complete noob and was kind of lost through the process. Finally it took me around 40 minutes to complete the whole process. Thanks a lot!
Some things to consider for noobs like me:
1. You MUST have Java SDK installed in order to open the "Android" App (SDK Manager) (I didnt have it)
2. It is important to delete the drivers of the kindle fire at Device manager (while is connected) if you have used (connected) it before. After deleting the drivers disconnect the kindle fire and install the drivers again.
3. adb.exe is located at \adt-bundle-windows-x86_64\sdk\platform-tools\ (sorry I didnt know where it was located)
4. When referring to "execute adb devices" it means you should type in a command prompt "adb devices" (I was looking for an .exe or a .bat file named "adb devices"!) LOL
5. After running "adb devices" you should be able to "see" your kindle device as a large alphanumeric sequence. Now, this was the tricky part for me... I tried several times and couldnt "see" my kindle listed! So I figured out that maybe there was a different kind of connection I could configure and indeed there was! I had to set my Kindle Fire to be in ADB Debug Mode. This is achieved by going to Settings->Security->Enable ADB And after that it was a piece of cake! I downloaded the file made by Bin4ry and followed the rest of the instructions.
Excellent tutorial bryanchapman9999!! I really appreciate your time and effort to gather up this information!
Regards.
Click to expand...
Click to collapse
Divanus,
First, the Android SDK is completely independent of other services and is only required for developers. The package includes Eclipse which is a Programming platform that people like us use to develop software for Android. The software used in Root MANY ANDROID includes the adb.exe utility needed to Root the Kindle.
You only need four things to Root the Kindle:
1. Root MANY ANDROID: http://ubuntuone.com/6LfERbIVoLRh822wHFicgR
2. Android ADB Driver: http://ubuntuone.com/4UaHeEJBrh9PT87RFzYR19
3. Windows PC
4. Kindle Fire 2
Step 1: Install the ADB Driver while the Kindle is Unplugged from USB, then Reboot your PC.
Step 2: Plug the Kindle into USB, wait 2 minutes for the driver to initialize
Step 3: Unzip Root_with_Restore_by_Bin4ry_v18.5.1.zip as Root_with_Restore_by_Bin4ry_v17 to your desktop
Step 4: If you installed the SDK, you need to disable it, otherwise Root Many Android will fail. You can disable it by changing the platform-tools folder to platform-tools-temp. This can usually be found C:\Program Files\Android\sdk\platform-tools
Step 5: Run Root Many Android RunMe.bat
Step 6: You now have Root!
I cant do it
I am running a windows 7 32 OS and i cant install the driver I uninstall the default and try to install the other one manualy but my kindle
isnt under other devices its under portable devices and when i select the driver it says its not supported and to check if the driver is used
on 32 bit systems
Some please respond or make a video tutorial please i want root for chain fire 3d driver graphics if you have anything email me at
"[email protected]"
I'm having problems
Now add the location of the ADB.exe file to your path
I don't get this part can someone please help me plus i'm having a lot of problems i'm running windows 7 32 bit so can some please do like
a video tutorial with windows 32 please I want my root.
Kindle Fire HD and 2 First Aide - 4.1.43-Beta - Dated 02/19/2013 at 22:15
Kusakus said:
I am running a windows 7 32 OS and i cant install the driver I uninstall the default and try to install the other one manualy but my kindle
isnt under other devices its under portable devices and when i select the driver it says its not supported and to check if the driver is used
on 32 bit systems
Some please respond or make a video tutorial please i want root for chain fire 3d driver graphics if you have anything email me at
"[email protected]"
Click to expand...
Click to collapse
Kusakus,
First let me apologize for the delay we have been working hard to improve our software. Please follow these steps to solve your problem:
Step 1: Remove Kindle driver by plugging the Kindle into USB, then Go to the Windows Device Manager and select the Kindle > Android ADB Interface - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 2: Remove the second driver found under Portable Devices > Kindle - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 3: Next you need to remove "phantom devices" in the Windows Device Manager. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties. Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
Step 4: Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
Step 5: In the System Variables section click on the "New" button.
In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1. Click OK.
Step 6: In the Environment Variables window notice how the new variable appeared in the System Variables section. Click OK.
Step 7: In the System Properties window click OK.
Step 8: Reboot the PC.
Step 9: Open Device Manager (Control Panel > System > Hardware > Device Manager).
Step 10: From the View menu click Show Hidden Devices and notice the change. Now remove EVERY instance of Kindle, Portable Devices, Android ADB Interface and Android ADB Composite Interface. Be sure to check the box to remove the driver from the PC.
Step 11: When you are done reboot the PC. Wait 3 minutes once you see the desktop for Windows to stabilize. Plug the Kindle into USB, wait 60 seconds and open the Windows Device Manager, you should now see two Yellow Triangles:
MTP
Unknown Device
Step 12: If you see two Yellow Triangles you have successfully removed all the Kindle Drivers! Unplug the Kindle from USB.
Step 13: Check Add/Remove Programs do you see Android SDK? If yes, please Remove it and reboot the PC.
Step 14: Please download and install Kindle Fire First Aide per this thread: http://forum.xda-developers.com/showthread.php?t=2096888
Step 15: Use Kindle Fire First Aide to install the Kindle Fire USB Driver - Option 12. Wait for the Install to complete. Once you see a successful driver install then go to the Kindle. Make sure "Allow installation of programs" is ON under the Kindle Status Bar - More + > Device. Also make sure ADB is ON under the Kindle Status Bar More + Security Enable ADB is ON.
Step 16: Plug the Kindle into your PC USB, wait 2 minutes, maybe 3 minutes for the driver to successfully install. When done go back to the Windows Device Manager, do you now see the following:
Kindle > Android ADB Interface
Portable Devices > Kindle
Step 17: If yes, then SUCCESS! Great work! Let's proceed, if NO post what you see in the Device Manger in the Kindle Fire First Aide thread here: http://forum.xda-developers.com/showthread.php?t=2096888
Step 18: Let's finally Root your Kindle Fire 2. Try Option 20 first if that root method fails, reboot the PC and Kindle then try Option 21. Pay close attention to the Kindle when using Option 21, the Kindle should ask to be "Restored" do not worry it is a fake restore that is only used to exploit the Kindle. When you restore the Kindle, the process will wrap up and you will have Root!
Step 19: You may use our software to install Google Play Store and Google Apps.
Kindle Fire First Aide Software Version 4.1.43-Beta The RunMe is Dated 02/19/2013 at 22:15:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/19/2013 at 22:15. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.
Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages. Also, if you see an ADB message alerting the following "adb server is out of date. killing.." then make sure you do not have another version of ADB or the Android SDK on your computer.
Finally, make sure you are running the latests version of Java SE Development Kit 7u13
Thank you to EVERYONE for working as a team to make this software a better product. We will never forget the people who have made this product successful.
---------- Post added at 01:20 AM ---------- Previous post was at 12:57 AM ----------
Kusakus said:
Now add the location of the ADB.exe file to your path
I don't get this part can someone please help me plus i'm having a lot of problems i'm running windows 7 32 bit so can some please do like
a video tutorial with windows 32 please I want my root.
Click to expand...
Click to collapse
Kusakus,
We are sorry this is more difficult than is has to be. To make you life easy, please download Kindle Fire First Aide from here, if you do not know if you have a 32-bit or 64-bit version of Windows use the Universal package:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Step 1: Unzip Kindle Fire First Aide to C:\KFFirstAide - make sure there is no number on the end of the C:\KFFirstAide and make sure there is not a second folder named KFFirstAide inside the folder C:\KFFirstAide
Step 2: Use Windows Explorer to navigate to C:\KFFirstAide, find the RunMe.bat, Right Hand Mose Click on RunMe.bat and select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Step 3: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Step 4: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Step 5: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Step 6: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAide
Step 7: That is it! The software is ready. Next we get the Kindle ready to Root! Grab the Kindle, pull down the upper Status Bar and select More + then select Device. Is "Allow Installation of Programs" ON? Good, next go to More + then select Security is Enable ADB ON? Good! Proceed.
Step 8: Plug the Kindle into USB. Wait 2 minutes for the Windows Device Manager to initialize. The open the Windows Device Manager by selecting the Keyboard "Windows Key" plus "Pause/Break", this will display the Windows System Properties. Click on the Device Manager tab do you see the following in the Device Manager?
Kindle > Android ADB Interface
Portable Devices
Step 9: If you do not see the above and you see two yellow triangles then remove the Kindle from USB and launch our software, select Option 12 to install the Kindle ADB Driver, wait for the driver install to complete, then plug the Kindle into USB, wait 2 to 3 minutes for everything to install, then inspect the Windows Device Manager again, do you see the two devices now? Good proceed!
Step 10: You are ready to Root, please elect Option 20 if that method of Rooting the Kindle fails do not worry we have more up our sleeve! Reboot the Kindle and the Computer.
Step 11: Please open Kindle Fire First Aide and this time use Option 21 to Root the Kindle. Please pay close attention to the Kindle, at one point the Kindle will ask to be Restored, click on RESTORE and let the software finish the process. In the end you will have Root!
Step 12: You may use our software to install Google Play Store Option 18 and Google Apps Option 23.
If you have any questions, please post them in our thread Kindle Fire First Aide: http://forum.xda-developers.com/showthread.php?t=2096888
Not trying to revive an old thread and I have been reading what I could find on the kindle fire 2. Recently got my daughter one and I'm not happy with the amazon store, etc. I would like to root and be able to use the playstore. Is this the best method? Is this what I need to do to accomplish this? She and her mother both like the stock ui and all, especially the carousel, so I have no intention of installing a different rom or launcher. So is it possible to simply root and get access to the google playstore? Thanks!
I used this thread recently and it worked fine
http://forum.xda-developers.com/showthread.php?p=36122126
Sent from my GT-P3110 using xda app-developers app
Hey It's me again
prokennexusa said:
Kusakus,
First let me apologize for the delay we have been working hard to improve our software. Please follow these steps to solve your problem:
Step 1: Remove Kindle driver by plugging the Kindle into USB, then Go to the Windows Device Manager and select the Kindle > Android ADB Interface - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 2: Remove the second driver found under Portable Devices > Kindle - choose Remove and be sure to check the Box to remove the driver from the driver database.
Step 3: Next you need to remove "phantom devices" in the Windows Device Manager. Go to Control Panel and double click on System. You can also right-click "Computer" on the Start menu (or on the desktop if it's shown there) and choose Properties. Note: A faster way for opening up the System applet is to press the Windows logo key on your keyboard and then press Pause/Break at the same time.
Step 4: Click on "Advance System Settings" link, and then click on the "Environment Variables" button.
Step 5: In the System Variables section click on the "New" button.
In the New System Variable dialog box, under the Variable Name value enter devmgr_show_nonpresent_devices (just copy the value from here and paste it there) and give it a variable value of 1. Click OK.
Step 6: In the Environment Variables window notice how the new variable appeared in the System Variables section. Click OK.
Step 7: In the System Properties window click OK.
Step 8: Reboot the PC.
Step 9: Open Device Manager (Control Panel > System > Hardware > Device Manager).
Step 10: From the View menu click Show Hidden Devices and notice the change. Now remove EVERY instance of Kindle, Portable Devices, Android ADB Interface and Android ADB Composite Interface. Be sure to check the box to remove the driver from the PC.
Step 11: When you are done reboot the PC. Wait 3 minutes once you see the desktop for Windows to stabilize. Plug the Kindle into USB, wait 60 seconds and open the Windows Device Manager, you should now see two Yellow Triangles:
MTP
Unknown Device
Step 12: If you see two Yellow Triangles you have successfully removed all the Kindle Drivers! Unplug the Kindle from USB.
Step 13: Check Add/Remove Programs do you see Android SDK? If yes, please Remove it and reboot the PC.
Step 14: Please download and install Kindle Fire First Aide per this thread: http://forum.xda-developers.com/showthread.php?t=2096888
Step 15: Use Kindle Fire First Aide to install the Kindle Fire USB Driver - Option 12. Wait for the Install to complete. Once you see a successful driver install then go to the Kindle. Make sure "Allow installation of programs" is ON under the Kindle Status Bar - More + > Device. Also make sure ADB is ON under the Kindle Status Bar More + Security Enable ADB is ON.
Step 16: Plug the Kindle into your PC USB, wait 2 minutes, maybe 3 minutes for the driver to successfully install. When done go back to the Windows Device Manager, do you now see the following:
Kindle > Android ADB Interface
Portable Devices > Kindle
Step 17: If yes, then SUCCESS! Great work! Let's proceed, if NO post what you see in the Device Manger in the Kindle Fire First Aide thread here: http://forum.xda-developers.com/showthread.php?t=2096888
Step 18: Let's finally Root your Kindle Fire 2. Try Option 20 first if that root method fails, reboot the PC and Kindle then try Option 21. Pay close attention to the Kindle when using Option 21, the Kindle should ask to be "Restored" do not worry it is a fake restore that is only used to exploit the Kindle. When you restore the Kindle, the process will wrap up and you will have Root!
Step 19: You may use our software to install Google Play Store and Google Apps.
Kindle Fire First Aide Software Version 4.1.43-Beta The RunMe is Dated 02/19/2013 at 22:15:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Please unzip the above packages to C:\KFFirstAide make sure the RunMe.bat is Dated 02/19/2013 at 22:15. Before running the software, make sure you do not have another folder inside C:\KFFirstAide named KFFirstAide32, KFFirstAide64 or KFFirstAide. After you Unzip the software you should only have one folder named C:\KFFirstAide, this is critical to proper operation.
Make sure you have a Environment Variable in the Microsoft Windows PATH Statement of C:\KFFirstAide otherwise you will see many 'unable to find ???package???.apk' messages. Also, if you see an ADB message alerting the following "adb server is out of date. killing.." then make sure you do not have another version of ADB or the Android SDK on your computer.
Finally, make sure you are running the latests version of Java SE Development Kit 7u13
Thank you to EVERYONE for working as a team to make this software a better product. We will never forget the people who have made this product successful.
---------- Post added at 01:20 AM ---------- Previous post was at 12:57 AM ----------
Kusakus,
We are sorry this is more difficult than is has to be. To make you life easy, please download Kindle Fire First Aide from here, if you do not know if you have a 32-bit or 64-bit version of Windows use the Universal package:
Microsoft Windows Kindle Fire First Aide Universal Version 4.1.43-Beta: KFFirstAide.zip
Microsoft Windows Kindle Fire First Aide 32-bit Version 4.1.43-Beta: KFFirstAide32.zip
Microsoft Windows Kindle Fire First Aide 64-bit Version 4.1.43-Beta: KFFirstAide64.zip
Step 1: Unzip Kindle Fire First Aide to C:\KFFirstAide - make sure there is no number on the end of the C:\KFFirstAide and make sure there is not a second folder named KFFirstAide inside the folder C:\KFFirstAide
Step 2: Use Windows Explorer to navigate to C:\KFFirstAide, find the RunMe.bat, Right Hand Mose Click on RunMe.bat and select 'Send to', select Desktop (Create Shortcut). Now press the Left Hand Mouse button to create the Shortcut named RunMe.bat.
Step 3: Find the RunMe Shortcut on your desktop, select it by left mouse click over the icon, then while on the icon choose Right Hand mouse click, select Properties.
Step 4: This will display the RunMe properties. Select the General Tab, change the top name to KF First Aide. Then click on the Shortcut tab, click on Advanced. Check 'Run as Administrator', click OK, then click Apply, then click OK. All windows should be closed.
Step 5: Double Mouse Click the new Icon named KF First Aide. You may be presented with a security window, just click Yes.
Step 6: Please click on the Windows Key plus Pause/Break, this will display the Windows System Properties. Next Click on the Advanced Tab and find "Environment Variables". Please click on Environment Variables and find the Path Statement. Carefully add at the end of the Path Statement:
Code:
;C:\KFFirstAide
Step 7: That is it! The software is ready. Next we get the Kindle ready to Root! Grab the Kindle, pull down the upper Status Bar and select More + then select Device. Is "Allow Installation of Programs" ON? Good, next go to More + then select Security is Enable ADB ON? Good! Proceed.
Step 8: Plug the Kindle into USB. Wait 2 minutes for the Windows Device Manager to initialize. The open the Windows Device Manager by selecting the Keyboard "Windows Key" plus "Pause/Break", this will display the Windows System Properties. Click on the Device Manager tab do you see the following in the Device Manager?
Kindle > Android ADB Interface
Portable Devices
Step 9: If you do not see the above and you see two yellow triangles then remove the Kindle from USB and launch our software, select Option 12 to install the Kindle ADB Driver, wait for the driver install to complete, then plug the Kindle into USB, wait 2 to 3 minutes for everything to install, then inspect the Windows Device Manager again, do you see the two devices now? Good proceed!
Step 10: You are ready to Root, please elect Option 20 if that method of Rooting the Kindle fails do not worry we have more up our sleeve! Reboot the Kindle and the Computer.
Step 11: Please open Kindle Fire First Aide and this time use Option 21 to Root the Kindle. Please pay close attention to the Kindle, at one point the Kindle will ask to be Restored, click on RESTORE and let the software finish the process. In the end you will have Root!
Step 12: You may use our software to install Google Play Store Option 18 and Google Apps Option 23.
If you have any questions, please post them in our thread Kindle Fire First Aide: http://forum.xda-developers.com/showthread.php?t=2096888
Click to expand...
Click to collapse
Ummm Well I used your software and i got it rooted (at least the software says it is) but now I cant even use the kindle it is really buggy and i press somthing and a minute later it does it plz help
If you got it rooted, try to put on the recovery and flash a custom one (slimkat is pretty awesome). The amazon OS is terrible IMO.
Kusakus said:
Ummm Well I used your software and i got it rooted (at least the software says it is) but now I cant even use the kindle it is really buggy and i press somthing and a minute later it does it plz help
Click to expand...
Click to collapse
First and foremost I AM NOT RESPONSIBLE FOR ANY HARD BRICKS,etc ,etc(Really hard to hard brick a kindle doing this unless you flash a weird rom package)
Now that thats cleared up, I have been seeing too many recovery bootloop bricks lately because I think the main tutorials people use haven't been updated(to mention you need to put a rom on the kindle beforehand now), so I thought why not write a tutorial that explains how to fix this problem since there are so many posts, that way we can just put a link to the tutorial in the peoples threads. So here we go!
Things you need to do this:
a micro-usb cable
patience
minimal command prompt experience
Instructions:
Boot your kindle into twrp (it should do this on its own at this point)
Make sure you have the adb drivers installed(they will need to be installed again if you flashed an older version of twrp), if not, update your drivers in the device manager with the ones in my signature.(See below if you don't know how to update your drivers)
Download the attached file and extract it somewhere
Put the rom and gapps in the folder you extracted the files to
Open a command prompt with admin privileges(start>all programs>accessories right click command prompt, hit run as admin)
CD into the directory where the extracted files are
Type this into the command prompt: adb push rom-or-gapps-name-goes-here.zip /sdcard/
As I said in the filename put either the rom or the gapps, but send both in two commands
At this point once the transfer is done unplug your kindle
If you are going from amazon to a cm based rom, at this point you should wipe system, cache, dalvik cache, and do a factory reset. If not just goto step 11.
Hit install, browse to the /sdcard folder and choose the rom and gapps files and flash them
Reboot and profit!
For people with driver issues that don't know how to install my driver:
Open the device manager
Find the device with a triangle next to it
Right click it and hit update driver
Choose the option that lets you search a folder for drivers by browsing
Choose the folder you extracted my drivers to
Let it search and install the drivers
Profit!
Note: If adb isn't picking up the kindle in recovery, try uninstalling the current kindle devices it detects first and then updating the drivers
It's about time someone posted a tutorial for how to fix this. Great job! This should be a sticky.
thanks
I had the same problem... the looping thing... you're tutorial saved me! thanks a lot.
rom and gapps
sry for my ignorance, but what do you mean with "rom and gapps"?
i explain what i've done:
i did everything in the guide to install twrp and 2nd bootloader.
i can acces in the twrp, but if i enter the reboot menu, if i push the botton "System", i had the boot loop problem (Kindle logo became orange and then blue forever)
Now the question is: where i find the rom and the gapps you're talking about?
You choose a ROM from the android development section for your model kindle, usually it tells what version of gapps(google apps) you need to flash with it. If it doesn't tell what gapps you need its pretty easy to tell, goo.im has the gapps posted for all versions of android, and have a chart telling which version goes with what os.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
*cannot read
When I go to push the file to the kindle I get a message in the command prompt saying *cannot stat 'rom.zip': no such file or directory.
I have the zip in the same folder as the adb file
Any suggestions?
Check the ROM name to make sure its not a typo? It should work. Make sure you didn't rename the ROM and add .zip because windows by default doesn't show extensions, so the filename might actually be ROM.zip.zip now if you did that.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sigh, I was hoping my first post on XDA wouldn't be a help request, but here I am..
I agonized for hours over the directions in this tutorial, checked all the right boxes, but I ended up in the bootloop as described in the OP. I can get to TWRP fine, but nothing else. My ADB drivers along with the Android SDK package were installed and previously working fine. Now, of course, the device no longer has a driver in Windows. I followed the instructions here, carefully selecting the extracted folder containing the ADB files, and Device Manager tells me—
"Windows was unable to install your Kindle. If you know the manufacturer of your device, you can visit its website and check the support section for driver software."
Click to expand...
Click to collapse
I tried a number of times to reboot both systems, uninstall the Kindle, try to pick it up again, etc., to no avail.
My device is a Kindle Fire HD 7" originally version 7.4.6. I made backups before I started as per the directions in the linked thread and I have my desired ROM and Gapp .zips all ready to go, I just can't get anything to the device. I'd prefer to avoid needing to get a factory cable, if possible.
Thanks for any help!
Edit: I've managed to get my .zip files to the /sdcard/ directory. For anyone stuck on the same problem I was, the instructions in this thread got my ADB drivers up and running again. The rest of the steps here worked fine at that point.
Oh good, someone finally made a tutorial for this.
Help please
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
CD means change directory, it does what it says, right now you are in your system32 folder so when you CD into the directory you extracted the zip file to you won't get that error. You should Google some command prompt basics.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Thanks
Thank you for this guide, googled some basic CMD knowledge and now i have cyanogen. Cheers
gallowayj3 said:
hello i am in need of some help, at step 6 can you explain what CD is. Also in Cmd i keep on getting this message below, please could you help me i also have just installed android ADB driver interface driver.
C:\Windows\system32>adb push cm-10.1-20130726-UNOFFICIAL-tate.zip /sdcard/
'adb' is not recognized as an internal or external command,
operable program or batch file.
Click to expand...
Click to collapse
Extract the file in the first post to somewhere on your C drive. (I put it in the C drive directly so it was just c:\adb\.)
Check this: ht tp://coweb.cc.gatec h.edu/ice-gt/339 - remove the spaces.
That should help.
Do
cd..
until you have just c:/. Then type cd:/adb and it should put you in the right place. Then you can do adb push.
I just figured this out actually and did it.
HELP
everything worked until i am flashing the rom, i get this error
updating partition details...
installing ' /sdcard/rom.zip'...
checking for MD5 file...
skipping MD5 check: no file found
assert failed: getprop("ro.product.device")=="blaze_tablet" || getprop(ro.build.product") == "blaze_tablet" || getprop("ro.product.device") == "tate" || getprop("ro.build.product") == "tate"
E:Error executing updater binary in zip ' /sdcard/rom.zip'
Error flashing zip ' /sdcard/rom.zip'
error flashing zip ' /sdcard/rom.zip'
epdating partition details...
PLEASE HELP
Sounds like an old twrp version I think, try downloading the latest twrp from android development for your device, It should have a flashable zip, just push it to your device and flash that, then reboot into recovery again and try flashing the ROM again.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stuck
Hi guys .., when i typed adb push cm-10.1-20130812-UNOFFICIAL-jem.zip /sdcard , it says
error: device not found.
i thing my pc didn't recognize my kindle. In device manager there ain't any devices not installed .
someone pls Help
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Sorry for my stupid question. ) what is service manager?
stunts513 said:
Find the android adb device in the service manager and uni stall it and let it install my drivers and see if it works, I'm guessing its a simple driver issue.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
My bad I think my kindle autocorrected a word incorrectly. It was supposed to say device manager.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
i'm kind of newbie on rooting and installing ROMs.
http://www.youtube.com/watch?v=hUW6KARo8Y4
i tried this youtube instruction and after step 20 My kindle fire wouldn't start. Not even the kindle fire with blue color.
and also pc didn't recognize my kindle , maybe because of it won't power on.
/this instruction is for kindle fire HD 8.9 , i don't know my kindle is 7 inch/
In device manager can't find adb devices .. what should i do?
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.
Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.
Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.
Using TWRP/unlock from [UNLOCK][ROOT][TWRP][UNBRICK] Fire TV Stick 3 and Fire TV Stick Lite (sheldon/p) with successfully installed OpenGapps on my Fire Stick Lite.
Needed files:
Open Gapps (Arm, 9.0, tvstock/tvmini)
gapps-config.txt (Attached Below) and edit as needed
These are the steps (guidance only! Some common sense is helpful!) if needed:
Boot into TWRP following the link attached
adb push <Download Location>/gapps-config.txt /sdcard/
adb push <Download Location>/open_gapps-arm-9.0-tv****-********.zip /sdcard/
adb shell
sheldonp:/ # twrp install /sdcard/open_gapps-arm-9.0-tv****-********.zip
sheldonp:/ # reboot or adb reboot
Install a custom launcher(Leanback on Fire recommended) and use Launcher Manager to disable stock launcher so Playstore becomes accessible
To pass Safetynet: use Magisk, Universal SafetyNet Fix and MagiskHideProps (I recommend MiBox S device fingerprint). YASNAC should return a pass!
Not working:
Google Search Voice (probably needs someone more advanced then me to figure it out)
Cast Receiver (Don't work on unregistered devices)
Android TV Launcher/TV remote (probably some accounts issue?)
To do:
Create a Magisk Module with stock Android TV boot animation
Compile tweaks/props that may be useful
Feel free to ask for help/comment!
Nice guide, thanks
Haven't had time to try it, but hopefully soon