Hi everyone, I got my kindle fire today and I'm trying the procedure to root it.
The problem is that adb doesn't see my kindle on pc because I wasnt able to edit the adb_usb.ini file in my user/.android folder, because it doesn't exists. why I don't have this .ini?
do you work with kfu or the sdk ?
anyway - create the .android folder and put the attached file in it
don't forget to rename it from .txt to .ini
http://forum.xda-developers.com/attachment.php?attachmentid=894821&d=1328819007
android sdk. I have the .android folder but inside only an empty avd folder, androidwin.cfg and repositories.cfg, that's all
edit: btw the ini file you provided worked, now adb sees mi device
use drivers from kfu
Sent from my HTC Glacier using xda premium
sorry for the newbie question but what is kfu?
Tony84 said:
sorry for the newbie question but what is kfu?
Click to expand...
Click to collapse
There's no need to apologize, it's the Kindle Fire Utility.
ah ok, thanks. but now I was able to proceed to root the 6.3.0 with sdk procedure.
glad to help ...
if your problem is solved please mark the subject of the topic (edit first post) with [Solved]
Related
Hi I downloaded this android peeing on Apple logo bootscreen, it installed well so I got too excited and wanted to put tux hammering the Windows logo before android pee on the Apple, I made all 70 png's but did not touch anything either than creating the images. I then zipped them according to the original names but when I flash it I get ..... E: wrong digest, system/media/bootanimation.zip
I have tried several times but no luck, yet the original one would easy install. Help guys
Sent from my HTC Hero VillainRom 12, flykernel11 using XDA App
any idea someone
You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did
kyouko said:
You probably need to sign the update zip, possibly change the install/flash location. Upload what you have in a zip and I'll make one for ya
Edit: and explain what I did
Click to expand...
Click to collapse
Too bad everyone doesn't do that.
I have decided to change the part1 folder images with custom ones, I will upload the whole zip later so when you help me I won't have to re edit it again, thanx for your replies
Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside "google" create a folder named "android" <- forgot about this step
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip
thanks mate I will download it today, thanks for the tutorial man its highly appreciative, thanks a lot
kyouko said:
Apologies as this is long overdue. Finally had some free time this weekend
Attached are both the working bootscreen AND the original for those who want to see what was changed between the two.
Edit: added the non-signed bootscreen.zip for reference as well. Never know who may want to look at it.
Setup
Extracted the zip (original_doesntflash.zip) into its own directory
Created the META-INF folder
Deleted the CERT.RSA, CERT.SF, and MANIFEST.MF files
Created the "com" folder inside META-INF
Inside the "com" folder I created another folder named "google"
Inside there I placed the "update-script" (if you want to know how to make one of these by hand refer to my post HERE)
Added both folders (META-INF and system) to a zip - in this case named it "bootscreen.zip"
Signing The Zip
I'm running linux currently so I do it slightly different, but I'm assuming the majority of you guys and gals are windows users. If that's the case follow these directions:
Go HERE and download AvaboxV2
Extract the AvaboxV2.zip where you want it. Personally I'd made a separate AvaboxV2 folder in my AndroidSDK dir. But the desktop still will work
Copy the newly created zip (bootscreen.zip) into the "Auto-Sign" folder found in AvaboxV2
As per the README.txt:
Start a cmd prompt AS ADMINISTRATOR (not really needed if running Win7)
cd <to the directory of the Auto-Sign folder> [Example: cd C:\AndroidSDK\AvaboxV2\Auto-sign]
java -jar signapk.jar testkey.x509.pem testkey.pk8 bootscreen.zip bootscreen_signed.zip <- same command as used in linux, at least for me
Press enter...wait...wait...done
Congratulations you now have a working/flashable bootscreen zip
Click to expand...
Click to collapse
I got an error when flashing the signed zip I got no update file found
elliotn said:
I got an error when flashing the signed zip I got no update file found
Click to expand...
Click to collapse
LOL uhh, I'll take a look at it and test it out... and edit my previous post with w/e I did wrong
Forgot to add the ''android'' folder in the zip. Fixed and should work now
With my former rooted S2 I was perfectly able to connect it with my desktop and the program Android Commander recognised it. I used that software to transfer files to the root folders.
Now I have a stock-rooted S4, I wanted to use Android Commander again. But alas, it doesn't recognise my phone.
I don't have any clue as to what is causing Android Commander to not 'see' my S4.
I would like to know if anyone is able to use this software with their S4.
Or if anyone has an idea how to fix my problem.
Thanks.
+1, i need AC working too
Android Commander for Galaxy S4
criszz said:
+1, i need AC working too
Click to expand...
Click to collapse
You have to update the ADB counsel on bin folder
Steps:
1- Download View attachment bin.rar
2- Extract with replace to all 4 files on bin folder "C:\ProgramFiles\Android Commander\bin" or "C:\ProgramFiles (x86)\Android Commander\bin" if you have windows x64.
3- enjoy using Android Commander:good:
Note: either change the folder security to add permission for everyone to allow winrar to extract and replace the files directly or extract the rar file outside (i.e. desktop) and simply copy and replace the files.
If it help you, please hit thanks below:good:
mohazia said:
You have to update the ADB counsel on bin folder
Steps:
1- Download View attachment 2097524
2- Extract with replace to all 4 files on bin folder "C:\ProgramFiles\Android Commander\bin" or "C:\ProgramFiles (x86)\Android Commander\bin" if you have windows x64.
3- enjoy using Android Commander:good:
Note: either change the folder security to add permission for everyone to allow winrar to extract and replace the files directly or extract the rar file outside (i.e. desktop) and simply copy and replace the files.
If it help you, please hit thanks below:good:
Click to expand...
Click to collapse
Thank you very much!! It works like a charm! Very happy with this!
mohazia said:
You have to update the ADB counsel on bin folder
Steps:
1- Download View attachment 2097524
2- Extract with replace to all 4 files on bin folder "C:\ProgramFiles\Android Commander\bin" or "C:\ProgramFiles (x86)\Android Commander\bin" if you have windows x64.
3- enjoy using Android Commander:good:
Note: either change the folder security to add permission for everyone to allow winrar to extract and replace the files directly or extract the rar file outside (i.e. desktop) and simply copy and replace the files.
If it help you, please hit thanks below:good:
Click to expand...
Click to collapse
Thankyou very much dear,,, its working fine after update bin folder...
This helped me with AC not recognizing the S4.
Anyway, how do you get it to obtain root access? On the Xperia I had to use an app called ADBD Insecure, but it doesn't seem to work on the S4.
So I have all the files I think I need in the platform-tools folder and adb recognizes the device but when I type adb sideload update.zip, it says *cannot read 'update.zip' *. The problem isn't that it doesn't read sideload, but it doesn't read the file. Any thoughts?
I hope I'm able to help I had the same prob...when I renamed the file to update.zip. The thing was the file was really update.zip.zip, so try that as file name and see what happens....
Make sure the file you want to sideload is in the same folder as your adb folder, or type out the full path to the file you want to install.
Sent from my HTC One using XDA Premium HD app
I only named the file update so its full title would be update.zip so I don't think its the name that's causing the trouble. The file is already stored in the same folder as adb and fastboot. Thanks though, it really means a lot to have help on this
I had this issue as well. I only renamed it to update....after trying again and renaming it to update.zip it work fine. It'll show the file to be sideloaded as update.zip.zip
Sent from my Nexus 4 using xda premium
1. The update.zip.zip would have worked, it finally started sending, but I didn't want to lose any data so I did the framework service hack instead. Thanks guys!
I cannot get the tegra note drivers to install I have installed the latest sdk modded the winusb.inf file. I am a novice please help I watched the rootjunky vid and some downloads were mentioned in particular one called impactor.zip but no links were shown. I appreciate any assiatance.
zalazin said:
I cannot get the tegra note drivers to install I have installed the latest sdk modded the winusb.inf file. I am a novice please help I watched the rootjunky vid and some downloads were mentioned in particular one called impactor.zip but no links were shown. I appreciate any assiatance.
Click to expand...
Click to collapse
Goto http://visualgdb.com/tutorials/android/usbdebug/manualinstall.php
Very neat guide with screenshots. I hope this helps you. I followed this guide and installed ADB drivers for my TN7.
i dont know why its not working for me.
when i get to step 12, "Enter the path to the Google USB driver. Normally it is located in the following directory:
C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
it keeps telling me that directory doesnt exist.
is there some .exe i can download somewhere that will install the right drivers for me
or maybe someone can tell me where to manually place the drivers, because i have the .dll files downloaded, just didnt come with any way to put them in the right place.
thanks in advance
Hey guys
I have been strugling for 10 hours to find out how to install all apk files, from a folder local on my mac, to my Nexus player.
Can someone guide med on how to make some kind of *.* install, so that i can install all APK files from a folder in a script ?
I can se that i can just put each apk file name in the script, but the thing is that the APK file names changes constantly, so i would really like to be able just to install all APK files from a folder instead ?
Really hope someone can help me, have a nice day!
You can follow this tutorial to install Fastboot and ADB: https://www.youtube.com/watch?v=qhYnHsmuJfo
Make sure you turn on Developer Options on your Nexus Player and also turn on USB Debugging. Then you can installs APKs using "adb install app.apk"