Related
The main reasons to root the kindle is to gain access to the Google Android Market and or flash a Rom. The the act of rooting the stock software is very near obsolete in most cases. For one reason or another this appears to be an arduous task for the kindle, the computer, the utility and for the inexperienced user. There`s a better way, not a new way but far less talked about. My hope is to create a better safety net for the average user. A few simple steps and you`re well on the way. The process involves getting drivers installed correctly, putting a custom recovery in place as well as a bootloader, managing your first backup and installing a modified stock Rom with root. It`s a good idea to first understand some basic things about what your device will need to make all this possible. I do not believe it could be anymore clearly laid out for you than FSM Kinfauns wrote here [GUIDE] Kindle Fire For Beginners. If you`re new to rooting or just to the Kindle Fire this is a must see.
Drivers
Well I`m sorry the first part is difficult at least for some users it requires getting drivers in order. I`m not going to go into great detail on this it`s very well highlighted in the second post of the above thread. Some things that may help installation.
Avoid using 3.0 USB ports users have had trouble with them not reacting well to fastboot causing serious problems.
Make sure your using the proper cable.
Run the Install_driver bat file first. Any errors during this may indicate the need for a manual installation. Windows XP requires manual installation.
Plug in the Kindle. Watch to see if windows shows installation of drivers and which one. Windows 7 usually shows a popup balloon of the driver it`s installing, click on it to view progress and type.
Open device manager. In device manager you should see "Android phone" click to view driver it should read "Android Composite ADB Interface".
If it reads "Android ADB Interface" more work is needed.
Right click then select update driver.
Click "browse my computer for driver software", and point it to the kindle drivers. On my Windows 7 machine, for instance, it's C:\Documents and Settings\HP_Administrator\Desktop\Kindle_Fire_Util ity_v0.9.6\Kindle Fire Utility\drivers\kindle.
Include subfolders and click next. Disregard any warnings update driver software anyway, preferably it will then read "Android Composite ADB Interface".
For manual installation here`s a very good tutorial. How to install Kindle Fire adb USB driver?
Driver flex testThere`s a way to test the driver before ever attempting to send anything to your device. The Kindle Fire driver is in and of itself multifaceted and Windows has only met with the first half of it. A mild introduction to the second half could very well prevent Windows from being confused when you need it function correctly for the technical part of this process. I would consider this "the lesser of two evils" with the only risk being stuck in fastboot. This far less under weighs actually physically breaking something if it were to fail.
Plug your kindle in.
Unlock the screen.
Tap disconnect at the bottom of the screen to stop the USB file transfer application if it auto launches.
Open device manager.
Launch Kindle Fire Utility.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000.
In KFU select # 1 Bootmode Menu then select # 2 Fastboot <4002> the Kindle will be told to reboot in fastboot mode. Setting bootmodes with KFU takes a bit be patient.
Check device manager see that the driver reads "Android ADB Interface" without errors such as an exclamation point or a question mark.
Powering the device off and back on again while attached can prompt new hardware found for updating driver on XP and proper installation of the driver in Windows 7.
If it does have an error or Windows does not recognize the device you must once again right click then select update driver to make it read "Android ADB Interface".
Press any key to continue
If it says ADB status offline Boot Status: Unknown disregard and select # 1 Normal <4000> this will tell the Kindle to reboot in Normal mode.
After booted press any key to continue.
Press 0 to recheck device status.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000. This completes the driver flex test. If you get stuck in fastboot don`t panic there`s no damage, just an altered bootmode. Keep working with your drivers, powering the device off and back on again while attached seems to work pretty well.
Device preparation
Start with a fully charged battery.
This step is very important under settings/device turn on allow installation of applications from unknown sources.
Plug your kindle in.
Unlock the screen.
Tap disconnect at the bottom of the screen to stop the USB file transfer application if it auto launches.
Status verification
Open device manager.
Launch Kindle Fire Utility.
Confirm driver indicates "Android Composite ADB Interface" in device manager and Kindle Fire Utility indicates ADB Status: Online / Boot Status: 4000.
TWRP installation
Select # 3 Install Latest TWRP Recovery. The Kindle will be told to reboot in fastboot mode. If all goes smooth it will reboot, in the terminal it will download the recovery, send it, write it. Then return your kindle to normal bootmode.
If nothing happens after 3 or 4 minutes and it just sits there <waiting for device> simply hold down the power button while connected till it turns off then turn it back on again. This could even take a few times always wait the 3 or 4 minutes in between.
Bootloader installation
Hopefully now the risky part is over and you`re booted back to the stock OS of the kindle.
Swipe to unlock the screen.
Do not disconnect the USB file transfer application. If it fails to auto launch touch upper left of screen, tap USB is connected select to copy files to/from your computer. This will show the contents of your sdcard on your computer.
Download bootloader only from here [bootloader][05-26] FFF 1.4A bugfixes + new look + recovery boot [.zip file size]. All files to be flashed in recovery must be in zip form. DO NOT EXTRACT. Do not use the bin file from KFU it`s not intended for flashing in recovery and will break the bootloader.
Drag and drop fff-u-boot_ v1.4a.zip on to your sdcard but do not place it inside of a folder.
Then disconnect the file transfer application when finished transferring.
In KFU select # 1 Bootmode Menu then select # 3 recovery <5001> this will tell your kindle to enter recovery.
In TWRP select install then locate fff-u-boot_ v1.4a.zip tap on it and flash it, leave the boxes unchecked.
When finished hit the home button upper right to return to TWRP home screen.
Select reboot.
Select system if prompted.
First backup and flashing rooted stock
After reboot Swipe to unlock screen.
Do not disconnect the file transfer application.If it fails to auto launch touch upper left of screen, tap USB is connected select to copy files to/from your computer.
Drag and drop this Rom zip onto your sdcard [ROM] 14 Jun Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire. Use the standard version not the altrom but do not put it inside of any folder. I`m not trying to highlight just one developers work but this is needed for this method.
Disconnect the file transfer application after the transfer has finished.
Unplug kindle from pc.
Power the kindle off , then back on again. When you see the white Kindle blue Fire logo quickly depress the power button a few times till you get a boot menu select --Recovery--.
In recovery select backup the default selections are fine, swipe to backup. This backup you will later rename noroot631 without spaces. Adding spaces will cause it to fail if you need to restore it.
When finished hit the home button upper right.
Select install.
Tap on GR9 Modaco zip and flash it. Do not enable force MD5 check or zip file verification or it will fail.
When done select reboot.
Select system if prompted.
Final result
When the Kindle reboots it will have root and have the Google Android Market in your applications.Take note that this is the only Rom that you flash without doing the proper wipes. To increase your safety net it is recommended to perform an MD5 check on fff-u-boot_ v1.4a.zip and Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire using this application WinMD5Free. You may ask" Why so many steps?" or "Why not flash everything at once?" This is to insure everything works throughout the process and prevent mishaps. The entire point of this thread to avoid having to use a factory cable or firekit to rescue your device because something went wrong. I hope that some of my tips and tricks will make your rooting experience safer and easier. Good luck and have fun.
How to flash another Rom
1. Transfer Rom zip and matching gapps zip to sdcard.
2. Enter recovery.
3. Create a backup.
4. Wipe factory reset.
5. Wipe cache.
6. Wipe dalvik.
7. Wipe system.( unless same Rom, same system, same developer)
8. Flash Rom zip.
9. Flash gapps zip.
10. Select reboot, then system if prompted.
11. Enjoy!
A very special thanks for all they continue to teach me and coaxing me to strive for more.
Kinfauns for Kindle Fire For Beginners
Soupmagnet for All the fun
Thanks to Vashypooh for Kindle Fire Utility
Thanks to Paulobrien for Gr9 (6.3.1) - MoDaCo Custom ROM for the Kindle Fire
reserved
Your welcome.
Got up to the "Open adb_usb.ini with notepad.", but the file was not there. Did I forget something?
---------- Post added 12th October 2012 at 12:09 AM ---------- Previous post was 11th October 2012 at 11:53 PM ----------
Got up to the "Open adb_usb.ini with notepad.", but the file was not there. Did I forget something?
adb_usb.ini needs to be located in your .android folder if its not copy paste it from Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers\kindle to .android and plug your device in. Make sure that 0x1949 is written in if its written in twice or not written in the device will appear offline.
Thepooch said:
adb_usb.ini needs to be located in your .android folder if its not copy paste it from Kindle_Fire_Utility_v0.9.6\Kindle Fire Utility\drivers\kindle to .android and plug your device in. Make sure that 0x1949 is written in if its written in twice or not written in the device will appear offline.
Click to expand...
Click to collapse
Did the trick. Ty sir
No problem.
abd Server offline and offline and offline......
Hello
I have a very neus Kindle Fire. Unfortunately I can not make it to rooten it.
For two days I build drivers back and forth. Always unsuccessful. The adb server is offline. Can it be that the device is too new? The device connects normal with win7. All attempts failed to use the modified drivers. It was only when I entered in my driver hardware ID from the Kindle (USB \ VID_1949 & PID_000A & REV_0216
USB \ VID_1949 & PID_000A) I was able to install the driver. Then stood in Device Manager under Android Phone ADB interface. Unfortunately the Kindle but then disappears completely from the workplace. But brings no good, the adb server is offline. Weis someone whether to run the adb server must also, not even when the kindle is connected? In Task Manager starts at least the adb exe.. Comes in the shell, but the message is written if I have adb properly etc.
I hope anyone have any advice.
Greetings and thanks
kindle-user said:
Hello
I have a very neus Kindle Fire. Unfortunately I can not make it to rooten it.
For two days I build drivers back and forth. Always unsuccessful. The adb server is offline. Can it be that the device is too new? The device connects normal with win7. All attempts failed to use the modified drivers. It was only when I entered in my driver hardware ID from the Kindle (USB \ VID_1949 & PID_000A & REV_0216
USB \ VID_1949 & PID_000A) I was able to install the driver. Then stood in Device Manager under Android Phone ADB interface. Unfortunately the Kindle but then disappears completely from the workplace. But brings no good, the adb server is offline. Weis someone whether to run the adb server must also, not even when the kindle is connected? In Task Manager starts at least the adb exe.. Comes in the shell, but the message is written if I have adb properly etc.
I hope anyone have any advice.
Greetings and thanks
Click to expand...
Click to collapse
Very important...what software version is your KF running?
soupmagnet said:
Very important...what software version is your KF running?
Click to expand...
Click to collapse
Hallo
My systemversion is 10.2.1_user_2030020
Don't do anything to your device until you read this:
http://forum.xda-developers.com/showthread.php?t=1928866
Hallo
Thank you for your Info. I will send it back to amazon. With original software do not like it.
best regards
soupmagnet said:
Don't do anything to your device until you read this:
http://forum.xda-developers.com/showthread.php?t=1928866
Click to expand...
Click to collapse
Bump
KFU ERRO
Well, I did exactly as in the procedure, but when I install TWRP, the KFU informed the log below:
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
3440 KB/s (510876 bytes in 0.145s)
The kindle has been told to reboot in Fastboot Mode.
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait...
< waiting for device >
... OKAY [ 0.198s]
finished. total time: 0.198s
rebooting...
finished. total time: 0.002s
***********************************************
* All Done! *
***********************************************
That's all folks. TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue . . .
_______________________________________________________________________
OBS:
In KFU shows the device status ONLINE.
I'm using Windows 7 Enterprise 64bit.
I figured it was giving error downloading the file, so I consulted the log and I downloaded manually, I created a folder "twrp.img" inside the folder "recovery" and threw the file "openrecovery-2.2.2.1-twrp-blaze" inside, but kept giving the same error.
The KF just restarts and nothing happens and does not install TWRP.
The version of my KF is 6.3.1.
Does anyone have a solution? Thankful!
PS: Sorry for the English, I'm using Google Translator!
Up!
Thank you your the best Thepooch
svartes said:
Well, I did exactly as in the procedure, but when I install TWRP, the KFU informed the log below:
***********************************************
* Recovery Installer *
***********************************************
***********************************************
* WARNING *
***********************************************
Make sure to read each screen carefully!
Make sure to follow instructions given to you!
twrp.img has been found.
***********************************************
* NOTICE *
***********************************************
Installing TWRP...
If we get stuck here for awhile, power the kindle on and off a few times.
You should also check device manager for "kindle" If so, rerun the driver
installer that came packaged with KFU.
***********************************************
* Activating Fastboot (4002) *
***********************************************
3440 KB/s (510876 bytes in 0.145s)
The kindle has been told to reboot in Fastboot Mode.
Cannot open input file recovery\twrp.img
error: cannot load 'recovery\twrp.img'
***********************************************
* READ ME *
***********************************************
If we get stuck here a long time, check the ADB drivers in windows.
Fastboot uses a different device than ADB, so make sure it is installed as an
ADB device. If you see "kindle" in device manager, you need to install the
drivers. You can also try running install_drivers.bat in the drivers folder.
Do NOT unplug the kindle if we are stuck here, leave it plugged in and on.
Do NOT touch the kindle at all if we are stuck.
Setting Normal Bootmode.
Please wait...
< waiting for device >
... OKAY [ 0.198s]
finished. total time: 0.198s
rebooting...
finished. total time: 0.002s
***********************************************
* All Done! *
***********************************************
That's all folks. TWRP has been installed.
Please tap reboot on the kindle.
Press any key to continue . . .
_______________________________________________________________________
OBS:
In KFU shows the device status ONLINE.
I'm using Windows 7 Enterprise 64bit.
I figured it was giving error downloading the file, so I consulted the log and I downloaded manually, I created a folder "twrp.img" inside the folder "recovery" and threw the file "openrecovery-2.2.2.1-twrp-blaze" inside, but kept giving the same error.
The KF just restarts and nothing happens and does not install TWRP.
The version of my KF is 6.3.1.
Does anyone have a solution? Thankful!
PS: Sorry for the English, I'm using Google Translator!
Click to expand...
Click to collapse
I had the same issue, I had to rename the recovery file name to twrp.img then it worked perfectly. Also delete the file you created for twrp in the recovery directory in the kfu package and just replace the copy of twrp (if the is one there) in the recovery folder with the one you downloaded and renamed.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
everything is set but when i open the KFU 0.9.9 it look like this.
failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
This is a great guide that goes into more detail than most of them which helps a lot for troubleshooting.
Unfortunately, the /data file system on my fire is read only, so copying the files to root it is not possible. I'm using KFU 0.9.9 and the kindle is running 6.3.2. Compter is windows 7 64-bit. What do I need to do to get permission to write to the kindle's filesystem? See the screenshots below.
Thanks for the guide
Sent from my Amazon Kindle Fire using xda app-developers app
hi guys inhd eed help for my kindle fire hd.
i want to add the "google play store" app, so i'm going to root it
i downloaded all files
but when i open cmd and type: "adb shell" appears this error: "device not found"
please help me!!!!
Google Play Market Kindle 7" Software 7.2.3
diego_berta said:
hi guys inhd eed help for my kindle fire hd.
i want to add the "google play store" app, so i'm going to root it
i downloaded all files
but when i open cmd and type: "adb shell" appears this error: "device not found"
please help me!!!!
Click to expand...
Click to collapse
I suspect your Kindle Fire 7" HD is now running Software Version 7.2.3 (Device - About), correct?
Your problem "Device not Found" is either driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/showthread.php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Downloaded and install the GoogleServicesFramework.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Play.apk to upgrade the the android market to the current Google Play market.
I have also attached copies of these noted files to this thread.
prokennexusa said:
I suspect your Kindle Fire 7" HD is now running Software Version 7.2.3 (Device - About), correct?
Your problem "Device not Found" is either driver related or ADB Security issue. I assume you have ADB enabled under Security - Enable ADB? Also enable "Allow Installation of Applications" under the Device tab - this will allow installation of Google Play applications. If all OK, move onto the next step.
Next, as per the Qemu thread noted here http://forum.xda-developers.com/showthread.php?t=1893838 you will find a driver package named "Kindle_Fire_HD_ADB_Drivers.zip", be sure to install the ADB driver package. Reboot the PC and next the Kindle.
As you noted, if you want to use Google Play, you must Root the device. Just to keep everything consolidated, I will give you a brief Rooting instructions which works for Software 7.2.2 and 7.2.3.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/showthread.php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/showthread.php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
You should now have root AND if this is true your ADB communication is also functional. Finally to Google Play.
Play Step 1 Downloaded and install the GoogleServicesFramework.apk
Play Step 2 Reboot the Kindle
Play Step 3 Download Vending.apk
Play Step 4 Using Root explorer app on the Fire (be sure it has Superuser Permissions). Move Vending.apk to /system/app with permissions set to Owner: Read-Write, Group: Read and Others: Read.
Play Step 5 Install Vending.apk
Play Step 6 Google Play should show up in your Kindle Fire HD Apps. Tap on it and follow the steps.
Play Step 7 Download and install the Play.apk to upgrade the the android market to the current Google Play market.
I have also attached copies of these noted files to this thread.
Click to expand...
Click to collapse
thanks dude but still not working.
ADB enabled on the indle fire HD - Version: 7.2.3
Root step 1: when i open root MANY ANDROIDS i press 1 (normal methods). Error: adb server is out of date. killing...
how can i do now??? P.S. now adb is installed
diego_berta said:
thanks dude but still not working.
ADB enabled on the indle fire HD - Version: 7.2.3
Root step 1: when i open root MANY ANDROIDS i press 1 (normal methods). Error: adb server is out of date. killing...
how can i do now??? P.S. now adb is installed
Click to expand...
Click to collapse
Seems you still have a driver issue. If you open the device manager on your pc you should see the kindle recognized as android composite adb interface. That is how you'll know if its just your driver(which most likely is).
Try using this first:
https://docs.google.com/folder/d/0B4lZEJI5lYeMdnFHeVRMQUtRYWc/edit
It is the driver application provided by amazon for sdk
If that doesn't do it (or even if it does) then I would recommend installing SDK, it will insure you have everything you need. Amazon provides add-ons, including usb drivers so you'll know for sure its all right. I posted link below for amazons page for installing sdk and kindle add-ons
https://developer.amazon.com/sdk/fire/setup.html
After you fix the drivers then use the method posted above to root. Good luck hope this works for you.
hi guys i'm a new forum member. I'm trying to root my kindle fire hd (7.2.3) but when i run "RunMe.bat" the device seems not to be connected! I've enabled the adb on the kindle and installed the ADB driver package. help!!!
ps sorry for my english
onemeila said:
Seems you still have a driver issue. If you open the device manager on your pc you should see the kindle recognized as android composite adb interface. That is how you'll know if its just your driver(which most likely is).
Try using this first: REMOVED : NEW USERS CAN'T LINKS
It is the driver application provided by amazon for sdk
If that doesn't do it (or even if it does) then I would recommend installing SDK, it will insure you have everything you need. Amazon provides add-ons, including usb drivers so you'll know for sure its all right. I posted link below for amazons page for installing sdk and kindle add-ons
REMOVED : NEW USERS CAN'T LINKS
After you fix the drivers then use the method posted above to root. Good luck hope this works for you.
Click to expand...
Click to collapse
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
adb server is out of date. killing..
diego_berta said:
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
Click to expand...
Click to collapse
Looks like you made quite a bit of progress. If I understand correctly, you have the driver installed and when you go into the Windows Device Manager you actually see "Android Composite ADB Interface" when the Kindle is plugged into USB, correct?
Looks like the SDK ADB Server is running or someones ADB Server is running. Drop to CMD and type: adb devices do you see a serial number? If yes, this is your Kindle, type: adb kill-server - this should terminate any adb server running. Now run Root Many Android, choose normal method. Ignore the errors, does the Kindle show a Restore All dialogue box? If yes, proceed to my original response. If no, are you sure you have enabled ADB on the Kindle? Also, when the Root Many Android and Qemu Batch files run, they both call to there own ADB Server. If you created a PATH statement in Windows pointing to the SDK ADB Server, there is a possibility of failure in these scripts. To eliminate this possibility, Rename the SDK ADB executable to ADB-TEMP, then run Root Many Android, does the error "Error: adb server is out of date. killing.." disappear? If yes, proceed in Normal mode IGNORING all the errors. When you execute the Root Many Android batch file, it will attempt to communicate with the Kindle and transfer some files through ADB. You will know this transfer was successful when the Kindle has an active dialogue box asking to "Restore All".
Note: The idea at this point is to focus on getting the ADB Communication path opened to your Kindle, once this is done everything else should be easy. Also, run Root Many Android and Qemu from your desktop. That is, when you extract these utilities, extract them to a folder on your desktop.
ADB driver
Raffo17 said:
hi guys i'm a new forum member. I'm trying to root my kindle fire hd (7.2.3) but when i run "RunMe.bat" the device seems not to be connected! I've enabled the adb on the kindle and installed the ADB driver package. help!!!
ps sorry for my english
Click to expand...
Click to collapse
What version of Windows are you running? Is your version of Windows 32-bit or 64-bit? If you plugin your Kindle Fire 7" HD to USB do you see the Kindle drive in My Computer? The Kindle power is on and the battery has a solid charge, correct?
Depending on your version of Windows, the directions will vary a little bit. Let's look in the Windows Device manger: Right Hand Mouse Click on My Computer or Computer, choose Properties. Now Click on Device Manager. Do you see something like "android composite adb interface" in the device manager when the Kindle is Powered up and plugged into USB?
Reply back with the answers and I will try to help you.
diego_berta said:
so bad. still same problem.
devices installed, sdk installed (with superuser and su), kindle is recognized as android composite adb interface, kindle software version 7.2.3
i tried some tutorials with cmd, with qemu and with "root many android"
here the problems:
WITH CMD) Error: cannot create /data/local.prop permission denied
WITH Qemu) Error: you must install your device specific drivers so that the device is visible to ADB
WITH ROOT MANY ANDROID) Error: adb server is out of date. killing..
thanks guys to help but it didn't work yet i'm lost
Click to expand...
Click to collapse
Open a cmd prompt and type this command:
Code:
android update adb
Then type these:
Code:
adb kill-server
adb start-server
adb devices
If all is working properly then you should see the device listed as a serial number
prokennexusa said:
What version of Windows are you running? Is your version of Windows 32-bit or 64-bit? If you plugin your Kindle Fire 7" HD to USB do you see the Kindle drive in My Computer? The Kindle power is on and the battery has a solid charge, correct?
Depending on your version of Windows, the directions will vary a little bit. Let's look in the Windows Device manger: Right Hand Mouse Click on My Computer or Computer, choose Properties. Now Click on Device Manager. Do you see something like "android composite adb interface" in the device manager when the Kindle is Powered up and plugged into USB?
Reply back with the answers and I will try to help you.
Click to expand...
Click to collapse
first of all thx for your reply. On my pc runs Windows 7 Professional 64-bit. when i plugin my kindle i can see it in my computer and obviously it's power on :laugh:
furthermore in Device Manager when i click on kindle i can see "android composite adb interface"!
the only thing that I could not install is the sdk.
Raffo17 said:
first of all thx for your reply. On my pc runs Windows 7 Professional 64-bit. when i plugin my kindle i can see it in my computer and obviously it's power on :laugh:
furthermore in Device Manager when i click on kindle i can see "android composite adb interface"!
the only thing that I could not install is the sdk.
Click to expand...
Click to collapse
Raffo17,
Unless you are going to do Android software development, you can do without the SDK. People like Bin4ry (Root MANY ANDROID!) and sparkym3 (Qemu automated root) have spent a lot of time to develop these tools so we can focus on other aspects of the Kindle.
Judging by your response, it looks like nothing should stop you from Rooting the Kindle. Go back to my original response in this Thread, download and extract to your desktop Root MANY ANDROID! and Qemu automated root. When you run Root MANY ANDROID! in Normal Mode, you will notice quite a few errors, ignore these errors. You will know that Root MANY ANDROID! has done its job when your Kindle asks to be Restored and then your Kindle will Reboot.
Go back to my instructions and remember, you are performing a risky upgrade(although it is worth it), so be careful.
prokennexusa said:
Looks like you made quite a bit of progress. If I understand correctly, you have the driver installed and when you go into the Windows Device Manager you actually see "Android Composite ADB Interface" when the Kindle is plugged into USB, correct?
Looks like the SDK ADB Server is running or someones ADB Server is running. Drop to CMD and type: adb devices do you see a serial number? If yes, this is your Kindle, type: adb kill-server - this should terminate any adb server running. Now run Root Many Android, choose normal method. Ignore the errors, does the Kindle show a Restore All dialogue box? If yes, proceed to my original response. If no, are you sure you have enabled ADB on the Kindle? Also, when the Root Many Android and Qemu Batch files run, they both call to there own ADB Server. If you created a PATH statement in Windows pointing to the SDK ADB Server, there is a possibility of failure in these scripts. To eliminate this possibility, Rename the SDK ADB executable to ADB-TEMP, then run Root Many Android, does the error "Error: adb server is out of date. killing.." disappear? If yes, proceed in Normal mode IGNORING all the errors. When you execute the Root Many Android batch file, it will attempt to communicate with the Kindle and transfer some files through ADB. You will know this transfer was successful when the Kindle has an active dialogue box asking to "Restore All".
Note: The idea at this point is to focus on getting the ADB Communication path opened to your Kindle, once this is done everything else should be easy. Also, run Root Many Android and Qemu from your desktop. That is, when you extract these utilities, extract them to a folder on your desktop.
Click to expand...
Click to collapse
thanks again prokennexusa, tomorrow i'll try it then i reply to this post and tell news... sorry bad english
Update - Kindle Fire HD Root then install Google Play
diego_berta said:
thanks again prokennexusa, tomorrow i'll try it then i reply to this post and tell news... sorry bad english
Click to expand...
Click to collapse
Diego_berta,
I will be available tomorrow, so I will watch for your response.
Rooting kindlefireHD 7.2.3
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
prokennexusa said:
Diego_berta,
I will be available tomorrow, so I will watch for your response.
Click to expand...
Click to collapse
hi prokennexusa again, i rooted the kindle with succes with root many androids but it react very slowly but it's blocked i can't do nothing sorry bad english
diego_berta said:
hi prokennexusa again, i rooted the kindle with succes with root many androids but it react very slowly but it's blocked i can't do nothing sorry bad english
Click to expand...
Click to collapse
Diego_Berta,
Looks like you are at Step 2, proceed to Step 3 and now run Qemu automated root, the Kindle will return to normal speed once you have completed ALL the steps.
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete to the end.
Root Step 4: Click on Superuser.apk under the Apps tab.
---------- Post added at 12:05 PM ---------- Previous post was at 11:54 AM ----------
dagelo said:
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
Click to expand...
Click to collapse
Dagelo,
The utility adb is used for Android Software development and advanced users. Sure you can root the Kindle using adb but you need to spend time learning the adb commands. I would recommend you download Root MANY ANDROID! and Qemu automated root, use these utilities to root your Kindle 7" Fire HD - they have adb embedded in each utility, so no need to install the SDK.
The following steps assume you have the Kindle plugged into USB, the driver is installed, you can see the adb driver in Windows Device Manager and adb is enabled on the Kindle (go back to the beginning of this tread for more details).
Root Step 1: Run Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore" a dialogue box on the Kindle.
Root Step 2: The Kindle will reboot and react VERY slowly, this is normal - leave it alone. Proceed to Step 3.
Root Step 3: Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838. Let this utility complete all the steps.
Root Step 4: Click on Superuser.apk under the Apps tab.
You now have Root!
---------- Post added at 12:25 PM ---------- Previous post was at 12:05 PM ----------
dagelo said:
hello there,
now i have tried to do all of this under windows 7 32b.
But have same problem. When i run adb.exe devices, its doesnt return me anything. Just empty.
I have Kindle in mz computer, so the drivers is installed succesfully.
Any idea why i get empty list in device with adb.exe command ?
Click to expand...
Click to collapse
Dagelo,
If you want to work with ADB, open a new Thread since this thread seems to be focusing on Rooting Kindle 7" Fire HD and then installing Google Play. I would be happy to try to help in the new thread, although since there are many capable people in this community so you will probably not need my help.
There can be many reasons for the missing device: Device driver problem, ADB out of date, ADB disabled on the Kindle, etc.
Send me a PM once you open the new thread.
no sorry i didn't tell you all... the qemu doesn' t work it gives me the same error: you must install your device specific drivers so that the device is visible to ADB. tomorrow i'll try again with qemu and i'll tell u all... thanks again, good night!
diego_berta said:
no sorry i didn't tell you all... the qemu doesn' t work it gives me the same error: you must install your device specific drivers so that the device is visible to ADB. tomorrow i'll try again with qemu and i'll tell u all... thanks again, good night!
Click to expand...
Click to collapse
diego_berta,
So if I understand you correctly:
A) You have installed the device drivers and ADB driver shows up in Windows Device Manager
B) You ran Root MANY ANDROID! http://forum.xda-developers.com/show....php?t=1886460. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
C) When executed Root MANY ANDROID! RunMe.bat in Normal Mode
D) You pressed "Restore" On the Kindle and the Kindle rebooted
Now the Kindle is slow and will not do anything - this is normal.
Leave the Kindle plugged into USB - turned on, you are 1/2 way done!
The error you are describing in Qemu is normal and can be ignored. Run Run Qemu automated root http://forum.xda-developers.com/show....php?t=1893838 following these detailed instructions:
1) Plug in the Kindle Fire 7" HD into USB
2) On your desktop should be Qemu, open the folder
3) Run RootQemu.bat
4) Select Option 1 - Root
5) Ignore the first error, press Enter
6) Ignore the second error/warning, press Enter
7) ADB daemon will start and detect the Kindle
8) Next it will begin to transfer the binary files across ADB, then Exploit the Kindle
9) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
10) Press Enter
11) ADB daemon will start and detect the Kindle
12) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
13) Continue to follow the Qemu instructions allowing the Kindle to be detected by Windows again - about 60-120 Second after every reboot
14) After about 2 - 3 more Reboots Qemu will test the Superuser account and display a Success message
15) When fully completed Qemu will close automatically
16) You should now have root
17) Download and install Root Explorer from the Amazon Apps - it is free
18) Go back to the beginning of this Thread and follow the instructions to install Google Play
prokennexusa said:
diego_berta,
So if I understand you correctly:
A) You have installed the device drivers and ADB driver shows up in Windows Device Manager
B) You ran Root MANY ANDROID!. Run Normal Method and ignore errors. Pay attention, you will need to answer "Restore All" a dialogue box on the Kindle.
C) When executed Root MANY ANDROID! RunMe.bat in Normal Mode
D) You pressed "Restore" On the Kindle and the Kindle rebooted
Now the Kindle is slow and will not do anything - this is normal.
Leave the Kindle plugged into USB - turned on, you are 1/2 way done!
The error you are describing in Qemu is normal and can be ignored. Run Run Qemu automated root following these detailed instructions:
1) Plug in the Kindle Fire 7" HD into USB
2) On your desktop should be Qemu, open the folder
3) Run RootQemu.bat
4) Select Option 1 - Root
5) Ignore the first error, press Enter
6) Ignore the second error/warning, press Enter
7) ADB daemon will start and detect the Kindle
8) Next it will begin to transfer the binary files across ADB, then Exploit the Kindle
9) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
10) Press Enter
11) ADB daemon will start and detect the Kindle
12) The Kindle will reboot, wait for the Kindle to be detected by Windows again - about 60-120 Seconds
13) Continue to follow the Qemu instructions allowing the Kindle to be detected by Windows again - about 60-120 Second after every reboot
14) After about 2 - 3 more Reboots Qemu will test the Superuser account and display a Success message
15) When fully completed Qemu will close automatically
16) You should now have root
17) Download and install Root Explorer from the Amazon Apps - it is free
18) Go back to the beginning of this Thread and follow the instructions to install Google Play
Click to expand...
Click to collapse
i moved vending.apk but the kindle is blocked again and gave me error. i had to restore all to factory settings... tomorrow i'll re-root the kindle but why it was blocked???
i try to root my kindle fire hd 7 7.2.3 using the tool Run Root MANY ANDROID! but nothing happens appear only :
If the device is not detected you may try to unplug it and reconnect it.
Waiting for device to be detected...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and other time appear:
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
*this thread is for m9+. it will NOT work on m7,m8,m9(or anything else). search your device general forum for a specific thread
if you have recently s-off'ed using an exploit that changed your banner in the bootloader screen to software status: modified,then this thread is for you.
*you must be s off.
*you must have superuser installed
read this:
this will not work if your s on
the usual disclaimers:
this has been tested,but if it melts your phone into a little pile of aluminum goo,its not my fault.
credits
-beaups for schooling me on echo command protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info) wich started off my love for chasing such things.
- @omar302 for getting the ball rolling,providing dumps,and lots of testing. he s-on'ed his phone several times during the tests,and has provided a huge amount of valuable info
IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and lower)
-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:
cd c:\miniadb_m7
your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)
-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:
adb devices
if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,then enter this command:
adb reboot bootloader
this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.
now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.
if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot
and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:
troubleshooting connectivity issues:
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine
failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)
failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above
note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities
-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window
-fastboot with phone in fastboot,enter:
fastboot devices in cmd window
in either case,a properly connected phone with working drivers installed should report back the phones serial number.
Click to expand...
Click to collapse
this process,in your cmd window,should look something like this:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR]
c:\miniadb_m7>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FAxxxxxxxxxx device
c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR]
FAxxxxxxxxxx fastboot
c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR]
rebooting...
finished. total time: 0.037s
c:\miniadb_m7>
2)reset your "tampered flag"
enter the following:
adb devices
adb shell
su (if needed to get a # prompt)
echo -ne '\x00' | dd of=/dev/block/mmcblk0p11 bs=1 seek=39940
(i would very strongly recomend you copy/paste this)
exit
(exit a second time if you need to to get back to a normal > prompt)
adb reboot bootloader
verify software status: official
if this does not work for you
*first reread this thread in its entirety. make sure you have met the prerequisites,and double check your code and make sure you have not forgotten a step,or screwed something up trying to type it (especially if using a terminal emulator),and check that you have not gotten any errors.
if youre still confident you did things correctly,you need to PM me:
1)the results of: fastboot getvar all
2)a link to an uploaded p11.
you get fastboot getvar all by:
-place phone in fastboot
-enter in fastboot getvar all right click,click mark,highlight in white,hit enter or right click to copy
you dump p11 by:
adb shell
su (if needed to get a #)
dd if=/dev/block/mmcblk0p11 of=/sdcard/mmcblk0p11
transfer the file on internal storage to your pc and upload it
im not trying to be a ****,but its not helpful to post "didnt work" if you screwed something up,or if your not willing to help find a solution. especially if others have found it to work on their same variant.
important:
from now on,i will need a copy of your cmd window as well if we want to get to the bottom of whats happening. some folks seem to be simply writing extra bytes,wich is screwing up the flag location. please make sure this shows an entire session,not just a last part where it looks correct. we cant figure it out if you only show part of what you did.
mine too
scotty1223 said:
mine too
Click to expand...
Click to collapse
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.
deleted. Better to wait Scotty's stock guide.
west2cool said:
@Scotty. What we need is how to change from Relocked to Locked on Bootloader.
Click to expand...
Click to collapse
You cannot do it without turning s on. P9 is now being protected,and any attempts to modify it in any manner result in security being turned back on
Planning a back to stock guide once I'm fairly certain it can be done safely
Sent from my Nexus 9
yvtc75 said:
echo -ne ......
Click to expand...
Click to collapse
Don't do this unless you're ready to be stock and s on,and have all your ducks in a row. It could leave you bricked or stuck in the bootloader with a security warning.
There's good reason I didn't post it.
Sent from my Nexus 9
Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.
Worked for me! Thanks!
omar302 said:
Just to confirm that it worked fine on my phone as per the screen photo in OP post. Also, just a warning to others, S-Off through SunShine might give you problems or would fail in case of repeated attempts (going back & forth between S-ON & S-OFF).
Thanks again to @scotty1223 for his help & work time this possiblef or the M9+.
Click to expand...
Click to collapse
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem
tbalden said:
Could you please detail, what problems? I s offed twice, but I'll be cautious if I knew there might be a problem
Click to expand...
Click to collapse
Apparently SunShine has some security system that detects if you are unlocking many times & then would just stop stop working & gives you message that your device is acting in an unusual way. I then had to contact their support to get it resolved.
i am rooted but s on, how can i s off to use your method? can someone help me
Rabia said:
i am rooted but s on, how can i s off to use your method? can someone help me
Click to expand...
Click to collapse
Currently they are using sunshine
Sent from my HTC One using Tapatalk
scotty1223 said:
Currently they are using sunshine
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
is that the paid thing, do they send a file accross or is it a physical thing
Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
http://theroot.ninja
Sent from my HTC One using Tapatalk
Rabia said:
is that the paid thing, do they send a file accross or is it a physical thing
Click to expand...
Click to collapse
You install the app & run it on your phone with a internet connection, after the app makes some tests & confirms your device is compatible you will be prompted to pay through the app itself ($25.00). The app itself will run & phone restart & then you get S-OFF. My M9+ was also from UAE (official-UAE version) & S-OFF worked from the 1st time. Very simple process.
Stock Locked bootloader?? @scotty1223
jureca said:
Stock Locked bootloader?? @scotty1223
Click to expand...
Click to collapse
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk
scotty1223 said:
Not possible currently. Attempting to modify p9 will cause you to turn s on. It may be possible to use it to your advantage if you need to be 100% stock,but I haven't had a chance to come up with a process that I believe would be 100% safe for all users
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Ok thank you, see if you can :good:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.
Guys,
I'm on 9920 and need to Brick it. I cant get the tablet into Fastboot mode but then its not responding and the PC (Ubuntu and Windows 10) doesnt 'see' it on the USB port (tried different ports).
ADB sees it fine on both OSes -- I can run any ADB command, like "adb reboot bootloader" and screen goes black and at the bottom I see "=> Fastboot mode..." -- I can also run isusb, etc and it sees the device fine (its the only one on the system)
When I run 'brick-9820.sh' and the script waits at "< waiting for any device > " and nothing ever happens until I break out of it (CTRL-C).
-- rebooting the tablet boots into the OS just fine. I even tried Factory Reset from Recovery mode... did not help
I can run STEP-1.SH but I just get "Platform Not Supported" over and over until I break out of it (I think this is to be expected since I don't have root)
Any help is HIGHLY appreciated!
LivinOne said:
Guys,
I'm on 9920 and need to Brick it. I cant get the tablet into Fastboot mode but then its not responding and the PC (Ubuntu and Windows 10) doesnt 'see' it on the USB port (tried different ports).
ADB sees it fine on both OSes -- I can run any ADB command, like "adb reboot bootloader" and screen goes black and at the bottom I see "=> Fastboot mode..." -- I can also run isusb, etc and it sees the device fine (its the only one on the system)
When I run 'brick-9820.sh' and the script waits at "< waiting for any device > " and nothing ever happens until I break out of it (CTRL-C).
-- rebooting the tablet boots into the OS just fine. I even tried Factory Reset from Recovery mode... did not help
I can run STEP-1.SH but I just get "Platform Not Supported" over and over until I break out of it (I think this is to be expected since I don't have root)
Any help is HIGHLY appreciated!
Click to expand...
Click to collapse
Try it to factory reset by using secret code from Amazon search ;oobe
Try this to use exploit package for Douglas from @k4y0z: https://forum.xda-developers.com/hd8-hd10/orig-development/unlock-fire-hd-8-2017-douglas-t3962846. Follow the steps carefully.
Can anyone help?
I've Factory Reset the HD8 twice and am using @k4y0z Douglas exploit package. I've ran exploits on many older HD8s (2016) & HD10s (2017) but never needed to Brick any... this HD8 2107 firmware is 9920 and I want to let my kid use it and put a custom ROM on it so I can run Google Family Link (which FireOS cannot).
thx for the help!
What device shows is it on lsusb?
Michajin said:
What device shows is it on lsusb?
Click to expand...
Click to collapse
tablet ID shows properly in both Windows 10 & Ubuntu in ADB (and can accept commands just fine too). When in Fastboot mode, it does not show up at all, or accept commands.
Should the tablet show as a USB device when in Fastboot mode? ... and if it should, what would cause it to not show up in FB mode, but work properly in ADB
LivinOne said:
tablet ID shows properly in both Windows 10 & Ubuntu in ADB (and can accept commands just fine too). When in Fastboot mode, it does not show up at all, or accept commands.
Should the tablet show as a USB device when in Fastboot mode? ... and if it should, what would cause it to not show up in FB mode, but work properly in ADB
Click to expand...
Click to collapse
You said it shows up.... What device does it say it is when you do a lsusb at the teminal in ubuntu?
LivinOne said:
Can anyone help?
I've Factory Reset the HD8 twice and am using @k4y0z Douglas exploit package. I've ran exploits on many older HD8s (2016) & HD10s (2017) but never needed to Brick any... this HD8 2107 firmware is 9920 and I want to let my kid use it and put a custom ROM on it so I can run Google Family Link (which FireOS cannot).
thx for the help!
Click to expand...
Click to collapse
Did you update all of the repositories the post calls out?
Also, how are you accessing Ubuntu?
Lastly, I'm sure you've checked this, but make sure it is a Douglas.
Michajin said:
You said it shows up.... What device does it say it is when you do a lsusb at the teminal in ubuntu?
Click to expand...
Click to collapse
It shows the ID. When sending ADB commands it works perfectly.
Kctucka said:
Did you update all of the repositories the post calls out?
Also, how are you accessing Ubuntu?
Lastly, I'm sure you've checked this, but make sure it is a Douglas.
Click to expand...
Click to collapse
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
LivinOne said:
It shows the ID. When sending ADB commands it works perfectly.
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
Click to expand...
Click to collapse
Does anything show up in lsusb in fastboot mode or do you see anythign like...
When you say it is in Fatboot mode, but nothing works, but you see a device in lsusb, what is the device called?
Like..
ID 0e8d:2000 MediaTek Inc. MT65xx Preloader
ID 0e8d:0003 MediaTek Inc. MT6227 phone
What is it being called?
---------- Post added at 12:36 PM ---------- Previous post was at 12:34 PM ----------
From my understanding you are trying to downgrade to unlock (which will temp brick your device), is this correct? I can try to help...
LivinOne said:
It shows the ID. When sending ADB commands it works perfectly.
Yes, I updated all repo's. I even killed my install and rebuilt the Ubuntu, under Windows Linux Subsystem. I used this exact setup, on the same PC, for 2 other Fire Tablets (HD8 2016 & HD10 2017) and it worked 100% smooth.
using... amonet-douglas-v1.2 and brick-douglas
The issue is the OS does not see the tablet once in Fastboot mode.
Click to expand...
Click to collapse
Does it recognize your other devices in fastboot mode?
If I recall correctly WLS doesn't work with fastboot. Something related to USB devices without storage.
I'd try booting Ubuntu using a USB stick with persistent storage.
Kctucka said:
Does it recognize your other devices in fastboot mode?
If I recall correctly WLS doesn't work with fastboot. Something related to USB devices without storage.
I'd try booting Ubuntu using a USB stick with persistent storage.
Click to expand...
Click to collapse
Here is a nice live disk pre-set up for the firestick 4k. I have used this on a few tablets.... But seems like it would still show up in fastboot in windows, if that was his issue...
https://github.com/amonet-kamakiri/fireiso/releases
Michajin said:
Here is a nice live disk pre-set up for the firestick 4k. I have used this on a few tablets.... But seems like it would still show up in fastboot in windows, if that was his issue...
https://github.com/amonet-kamakiri/fireiso/releases
Click to expand...
Click to collapse
Does the ISO run in Virtual Box, or something else? I've only been using the Windows Linux Subsystem as I rarely need to use Linux other than for my Synology NAS. Thx for the help!
LivinOne said:
Does the ISO run in Virtual Box, or something else? I've only been using the Windows Linux Subsystem as I rarely need to use Linux other than for my Synology NAS. Thx for the help!
Click to expand...
Click to collapse
It is a live disk. Burn it to a USB and boot from it...
Guys,
I noticed that in Windows 10 vs Ubuntu (Windows Linux Subsystem / WLS), they both work great with ADB... but they seem to be loading different versions...
Windows: adb server version (39) doesn't match this client (41); killing...
Ubuntu WLS: adb server version (41) doesn't match this client (39); killing...
Could this be an issue where Fastboot is a problem due to version?
thx
LivinOne said:
Guys,
I noticed that in Windows 10 vs Ubuntu (Windows Linux Subsystem / WLS), they both work great with ADB... but they seem to be loading different versions...
Windows: adb server version (39) doesn't match this client (41); killing...
Ubuntu WLS: adb server version (41) doesn't match this client (39); killing...
Could this be an issue where Fastboot is a problem due to version?
thx
Click to expand...
Click to collapse
No
Looking through the unlock thread, The OP says it is a fastboot issue and recommends using the live disk i sent a link for see posts #265 and #268
https://forum.xda-developers.com/hd...unlock-fire-hd-8-2017-douglas-t3962846/page27
Everything points to your computer not recognizing the fastboot device- Try the live disk....
I fixed it! Windows will not load the driver when I try to do it in Device Manager, manually. I used this installer THEN I opened Device Manager, right-clicked the unknown item under Android, and pointed it to root of the C Drive! It found and installed the driver.
Hope this helps someone in the future.
thx guys!