Related
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
THANHVO31 said:
Look here for hardwareid http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
I think this is an attempt to prevent root from amazon. However, if you know the procedure, the game is not over.
Click to expand...
Click to collapse
That link you posted doesn't use my same ids
Th3-Chronikk said:
My device ids and hardware ids are different than the ones in the drivers for rooting
Device Instance Id: USB\VID_0006&MI_01\6&FA091&1&0001
Hardware Ids: USB\Vid_1949&Pid_0006&REV_0216&MI_01
USB\Vid_1949&Pid_0006&MI_01
Compatible Ids: USB\Class_ff&SubClass_42&Prot_01
USB\Class_ff&SubClass_42
USB\Class_ff
How could I use these in the android_winusb.inf to make Adb recognize my device any help would be great
I think that other people have these same ids that is why I'm not the only one where Adb isn't recognizing my kindle fire I help this helps others help all the people that would like to root their device but cant because its not recognized
Click to expand...
Click to collapse
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
EDIT: and I made a huge mistake and i had not put in the bootloader (FIREFIREFIRE) on my bricked kindle, however, I took extra precaution and put it on my working kindle and to prevent it even further I am not using any roms and only using GoLauncher EX, googleframework, Superuser(root), and Market
as some roms are unstable and ALWAYS have a problem that something is not working correctly!
umarsl said:
Once you find the solution can you please let me know as well?
I am really interested in this!
btw, I have another Kindle that is working and gets recognized by computer in seconds and the other that has been bricked for over 2 months :'(
Click to expand...
Click to collapse
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Th3-Chronikk said:
I will post it on a new thread so you will know and I cant find anyone to help me with these ids
Click to expand...
Click to collapse
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\Vid_1949&Pid_0006&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006
Click to expand...
Click to collapse
And try again.
Goodluck
THANHVO31 said:
I just give you the fishing rod, not fish
Once your KF stuck at Kindle Fire, you can get your HardwareID
You should know the file call "android_winusb.inf" that you'll point to that to install driver for your bricked KF.
put the following
And try again.
Goodluck
Click to expand...
Click to collapse
Didn't work
Th3-Chronikk said:
That link you posted doesn't use my same ids
Click to expand...
Click to collapse
The hardware IDs in that link look identical to yours, and I think every other Kindle Fire I've seen. Yours don't look unusual.
I'm having the same damn issue, my 6.2.2 kindle is not recognized by adb. The weird thing is that sometimes it does see the device and then it disappears? The driver ID's that are posted are identical to the ones that are included with KFU.
If anyone figures this out please let me know!
Troy.
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
p-niiice said:
Mine are
USB\VID_1949&PID_0006&REV_0216
USB\VID_1949&PID_0006
And I can't seem to get recognized although the "Composite" piece of it is working...I cannot get ADB to see it. What do I need to add to my file?
The obvious thing to do is make the entries match this, but that's obviously not it. I do need help, it's not a crap question, and I have done everything to get this going.
Click to expand...
Click to collapse
android update adb
add 0x1949 on its own line to adb_usb.ini in C:\users\<username>\.android\adb_usb.ini
save the file
adb kill-server
adb start-server
adb devices
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
jcc2z said:
I had all these problems, but what fixed mine was manually typing in the "0x1949". I initially was copying and pasting, but I seen somewhere else that it was causing problems. Its the only text/line in the file.
I have absolutely no clue as to why this fixed it, but it did for me.
Click to expand...
Click to collapse
Thanks - doing this plus the hardware ID lines earlier in the thread got me further, but adb still isn't picking up the composite device.
androidcues said:
This post is ridiculously long and is kind of a rant... but Ive had it with all these "cant find adb in KF" posts and yes its a problem, and yes amazon devs are prob laughing at us but the answer is not on XDA forums or anywhere its not in Vashypooh's Teamviewer, its in your computer its in your Fire and you need to make it happen. Im probably going to regret posting this, but whatever, its a crap answer for a crap question.
Look - Ive messed around with just about everything from the kindle to the computer to using different computers to performing downgrades from Win8 to Win7 and trying to figure out why my Fire sometimes can be seen by adb and why sometimes it cannot...
I cant explain everything in one post its too much information but you need to mess around.
Without explaining these are the steps I took and I cant tell you which ones work because its like a very messy environment on a computer and everyones got different flavors and different variables...
try these (in no particular order) try them all at once or try them in pieces, but you need to reboot after each instance (think about your science teacher explaining why scientific experiments need to be controlled and clean and precise so as to eliminate any variables which may interfere with the end result!)
Do you have admin rights over your computer? If you dont... get it.
delete the .android file (this will have adb_usb file in it) try again. Watch for your driver action you need to know whats going on... you need to make your computer verbose so its reporting all its activity
Uninstall and delete (FULLY DELETE!) the Kindle Fire Utility if you have it.
Uninstall and delete (FULLY DELETE) the Android SDK if you have it. All of them if you have more than one.
Uninstall and delete (FULLY DELETE) any such programs you have that are dedicated to using adb.exe such as say AndroidCommander Droid Explorer or any of that stuff they are gone!
If you want to know if theres any other stuff on your computer, and dont really know how to use anything other than Windows Explorer, (shame on you) then install the greatest file finder I know - Everything.exe http://www.voidtools.com/download.php install that crap and then fix the options to "show hidden files and system files and hide nothing) and then when its set up, type in the search "adb" and "android" and "winusb" instances, then go to their parent folder and delete the whole thing, clear out your trash, uninstall all drivers, delete them, and UNPLUG all connected android devices so they dont throw stuff back into system and reboot the computer. You want a nice virgin promiscuous machine when it reboots, so you can pop its cherry with one Kindle Fire that needs to get its adb on.
install a verbose driver program (i am fond of USBDeview http://www.nirsoft.net/utils/usb_devices_view.html) make sure whatever program you use is VERBOSE and reports every activity, like in the options make everyhting so that it reports, displays and hides nothing. UNINSTALL AND DELETE EVERYTHING that indicates it could be connected to 1. ADB 2. Device 3. anything freaking android. Actually, I have been so frustrated in the past that I actually uninstalled every single driver on the computer....I highlighted all my drivers and Uninstalled... and they all uninstalled.. my mouse stopped working my keyboard stopped working but screw that, shut down the computer (irrelevant to whatever winblows geeks tell you it is NOT harmful to crash-power down your windoze machine) and then upon rebooting it will install all its relevant inner drivers) which may be bad for some of you if you have a complicated setup but whatever all I wanted was to get adb working at the expense of other drivers. Everything will reinstall when its connected, thats how drivers work -- you connect it and it starts talking to windows and **** happens right there.
So, delete everything! Reboot! you need to reboot your machine after each major change, because its just to eliominate the chances of not being able to communicate if winblows needs to reboot to be fresh.
If you have deleted uninstalled all of these android-related drivers... and if you have made your machine verbose, so that its not hiding information or thinking you are not interested in whats going on in system, and then you reboot, chances are when you first plug that KF in to your system, **** will happen. You just need to make it work.
you cant just sit around for two months waiting for someone to give you the fix -- the answer is right there in your hands... you just have to make it stick. Its there. Just gotta tweak the hell out of your computer to make it happen. If it doesnt work... keep trying... try again. if that doesnt work, change something. keep on tweaking, keep on shaking the nest and itll pop in.
HOWEVER I checked out the Jayceooi website and he/she has a good case to make there -- and if "it dont work" then thats because you are not trying hard enough.
Now.. all I can say is Ive lost adb.. and Ive found it again.. and I still have it because I have not installed ANY other android related or SDK ADB related programs after I found it.... everytime I do... everytime I attach my other HTC devices, it messes up everything and I repeat the above all over again
Click to expand...
Click to collapse
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
K3nDroid said:
This is why i use linux.. i just have way to many android devices i plug into my pc to have to be deleting and reinstalling drivers and android sdk everytime.
Ive rooted three kindle fires already, one on windows and two with linux. rooting with windows took me a whole day to get to work while it took me an under an hour with linux.
if you like to plug in android devices a lot and want to use adb on all of them, do yourself a favor and trash windows and install linux. I have 2 PCs so its not a problem for me. one house computer running windows, and my pc running linux..
windows hates android!
Click to expand...
Click to collapse
Interesting that you had such an issue with getting windows to work. I have rooted 2 Kindles(took an hour total to get them set up, rooted, recovery and Gapps installed), Samsung Epic 4g, Multiple Evo 4gs, Optimus M, Hauwei Ascend, and HTC Hero and never had an issue with drivers or having to uninstall them. I am running Windows 7 and each one I plug in it recognizes.
SO i posted this in another thread, thought I'd start one here.
Im sure a lot of people are facing the same issue as I am. So any assistance would not only help me, but plenty of others as well. Here it goes:
I just joined XDA...if there ever existed a supernoob when it comes to phones, then thats me...i have almost absolutely no idea about flashing, roms and whatnot...i just know they exist
My problem is that I have a galaxy nexus, yakjuux, here in Canada, and as everyone else, thinking of flashing to yakju for the updates.
I have a black macbook, and I was reading on how to flash...and i just couldnt piece together all of the information thats available.
Anyone here generous enough to help me flash to yakju to get the updates?
walk me step by step as to how to flash...like literally step by step, with every bit of detail.
Im not completely dumb with technology, but its just with phones that I fail.
Thanks!!
time for some tough love... You need to start reading and figure it out. These exact threads, nearly word-for-word, have been posted for the last 3 months straight, and have been answered the exact same for 3 months straight. There are guides, stickies, posts, videos, etc. all sitting in these forums. You are seriously going to get yourself into some nasty **** if you just let someone tell you what to do and you have absolutely no idea what's going on while you're doing it. Search. Please.
Good luck.
Thanks martonikaj,
I understand the multitude of information available out there, but there is nothing for mac in terms of videos that helps flash from yakjuux to yakju.
If i missed something, would you be able to post it? I would be grateful.
Its just a matter of getting a guide that's concise and concrete.
mace17 said:
Thanks martonikaj,
I understand the multitude of information available out there, but there is nothing for mac in terms of videos that helps flash from yakjuux to yakju.
If i missed something, would you be able to post it? I would be grateful.
Its just a matter of getting a guide that's concise and concrete.
Click to expand...
Click to collapse
There is nothing different about a Mac guide. In many ways its simpler. The only difference is that you need the Mac version of ADB and Fastboot files instead of Windows ones, and you need a "./" in front of the commands in Terminal (instead of Command Prompt). There are no "1 click" (toolkit) methods for OSX. Do it manually you'll be better for it anyway.
I've attached ADB and Fastboot files.
Got past that, serial number is not showing up though...aghh
is there no video to show how its done?
mace17 said:
Got past that, serial number is not showing up though...aghh
is there no video to show how its done?
Click to expand...
Click to collapse
so you've downloaded and unzipped ADB and pointed Terminal to that folder, connected your phone and enabled USB debugging, and type "./adb devices" and nothing shows up?
umm yeah I did all of that...
i sent you a message!
Sorry for the stress haha, tough love indeed it is...but this is driving me crazy...
mace17 said:
umm yeah I did all of that...
i sent you a message!
Click to expand...
Click to collapse
On computer:
1) unzip Mac_ADB_Fastboot.zip
2) Move files somewhere, like your <user name> folder
3) Open Terminal
4) type "cd " and drag the unzipped Mac_ADB_Fastboot file into the Terminal window (or manually navigate if you know how to do that) and hit enter
On phone:
1) turn on USB debugging in developer options
2) connect phone via USB
There is literally nothing else to do to get the computer to recognize the device.
Ok guys I need your help with this question, is there a way to root the Kindle Fire without a computer?
I've tried Z4 root and it crashes after a certain point and never roots and I'm without a computer for a few weeks and badly need to root my Kindle Fire and was hoping to find a solution that could possibly work.Hoping there was a app like z4 root that could be an alternative solution ....Please post your feedback
Thanks in advance!!!
No
Thanks for the info
I haven't tried it and I don't even know if it's possible, but theoretically you could run adb commands from another Android device.
You start an adbd server from within Android but whether it succeeds or not depends on whether or not it can recognize a Kindle Fire on the other end of the tether.
It's worth a shot.
All you need to do is get "su" to /system/xbin and the rest can be done on your own device.
soupmagnet said:
I haven't tried it and I don't even know if it's possible, but theoretically you could run adb commands from another Android device.
You start an adbd server from within Android but whether it succeeds or not depends on whether or not it can recognize a Kindle Fire on the other end of the tether.
It's worth a shot.
All you need to do is get "su" to /system/xbin and the rest can be done on your own device.
Click to expand...
Click to collapse
Interesting thought... I'm not sure it will work though.
You'd have to remount the /system partition as rw to get su on there and that requires root privileges. That's the chicken/egg problem you'd have to overcome.
Whatever the case, the whole experiment would require considerable blurring of the definition of "a computer."
kinfauns said:
Interesting thought... I'm not sure it will work though.
You'd have to remount the /system partition as rw to get su on there and that requires root privileges. That's the chicken/egg problem you'd have to overcome.
Whatever the case, the whole experiment would require considerable blurring of the definition of "a computer."
Click to expand...
Click to collapse
Well, if you have adb on your device and you enter "adb root" from a Terminal, it will start the adbd server as it would on a computer but returns "error: device not found", obviously because it doesn't detect a device connected to the USB.
Presumably, if you had another device tethered to the one you want rooted, you could, with USB debugging enabled, start an adbd server from the first device and "adb root", "adb remount", etc.
The problem with that is the "adbd cannot run from stock devices" garbage. I'm sure there's a way around it though.
[Edit:] Oh and...it was the egg.
Duplicate post. Deleted. Damn XDA app!
soupmagnet said:
[Edit:] Oh and...it was the egg.
Click to expand...
Click to collapse
The point of that is to point out the fact the chicken/egg paradox was only such because at the time of its inception, the answer was unforeseeable.
Code:
</geek>
[Edit:] Besides, who's to say it can't be done with fastboot?
soupmagnet said:
The point of that is to point out the fact the chicken/egg paradox was only such because at the time of its inception, the answer was unforeseeable.
Code:
</geek>
Click to expand...
Click to collapse
That's what the liberal media bias would have you believe!
Interesting how fast this discussion has degenerated from technical to scientific to political.... surely Hitler will come into play within the next couple of posts.
kinfauns said:
That's what the liberal media bias would have you believe!
Interesting how fast this discussion has degenerated from technical to scientific to political.... surely Hitler will come into play within the next couple of posts.
Click to expand...
Click to collapse
Hitler.
Hey, you were right!
Back on topic...If only I had a USB micro to USB micro cable to test it out with...
I think fastboot is the way to go.
soupmagnet said:
[Edit:] Besides, who's to say it can't be done with fastboot?
Click to expand...
Click to collapse
Because fastboot is the egg and by that point the host is in every way a computer but in name. I think we are way off the intent of the original OP which I'm sure was meant to ask if rooting could be accomplished on a standalone device without the aid of another attached to it... and the answer to that is still "NO."
EDIT: soup nazi!
kinfauns said:
Because fastboot is the egg and by that point the host is in every way a computer but in name. I think we are way off the intent of the original OP which I'm sure was meant to ask if rooting could be accomplished on a standalone device without the aid of another attached to it... and the answer to that is still "NO."
EDIT: soup nazi!
Click to expand...
Click to collapse
I must respectfully disagree with you. The intent of the OP is to be able to root without access to a computer that won't be available for a few weeks. The availability of another Android device is exponentially greater.
[Edit:] [email protected] nazi
soupmagnet said:
I must respectfully disagree with you. The intent of the OP is to be able to root without access to a computer that won't be available for a few weeks. The availability of another Android device is exponentially greater.
[Edit:] [email protected] nazi
Click to expand...
Click to collapse
"Exponentially" is reaching a bit, but point taken. He doesn't explicitly exclude the possibility of attaching another android device. I'll concede that point.
However, he does say he tried using some app and asks if there's another app that would do something similar for the Kindle Fire... and that at least implicitly supports my view of the OP.
Whatever the case may be... I don't think this debate needs to go much further. We've already invoked Godwin, so it should have ended already.
kinfauns said:
We've already invoked Godwin, so it should have ended already.
Click to expand...
Click to collapse
I secede to your geekiness
there is a way
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process.
of course it can!
Yes.. just download rootmaster
Of course it can!!!!
thacoolestnerd said:
Ok guys I need your help with this question, is there a way to root the Kindle Fire without a computer?
I've tried Z4 root and it crashes after a certain point and never roots and I'm without a computer for a few weeks and badly need to root my Kindle Fire and was hoping to find a solution that could possibly work.Hoping there was a app like z4 root that could be an alternative solution ....Please post your feedback
Thanks in advance!!!
Click to expand...
Click to collapse
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process.:laugh:
---------- Post added at 02:06 AM ---------- Previous post was at 01:58 AM ----------
Yes!!! There actually is a way.. but you need 2 apps to do this.. one is called rootmaster 1.0.5.1, and the other app is called root master ceskas Apk. One of the apps will halfway root the kindle fire, and the other one should complete the rooting process. Use rootmaster first(the one that is not ceskas,) it will start rooting the device until it gets to 50 percent and says you need to finish the root with te computer.. but when you use the other app.. it finishes the rooting process. But every time you open an app that requires root permission.. it asked for root permission to run the app. Just press the right button when the ceskas menu pops up..( it will be in a different language)[email protected]
This will also work on the s4 and any kindle base platform including hd, hdx, and it should work on the paper white.
WARNING:
Do not use this on Second Generation devices. This includes the Kindle Fire 2 and all Kindle Fire HDs. If your device is NOT running a software version of 6.3.2 and earlier, the tool you are looking for is here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The SoupKit
SoupKit consists of two major components: the SoupKit Installer and the SoupKit Utility.
The SoupKit Installer
This puts everything where it needs to be, installs any necessary dependencies, installs drivers, configures Linux to run adb and fastboot commands, puts the SoupKit in your $PATH and cleans up after itself. What this means for you is, you can open any terminal window and start entering adb or fastboot commands immediately. There's no need to change directories, add sudo commands or special operators ( ./ ). You can enter commands just as you see them in the tutorials. No more worrying about “ADB Offline”, “Status Unknown” or “List of devices attached ????????????????”. This alone can make a huge difference for anyone having Kindle Fire problems that can't be fixed in Windows or those who are overwhelmed by the technicalities of configuring Linux for Android. This part of the script alone can be invaluable for users fighting with Window's device drivers but this kit can do so much more...
The SoupKit Utility
This is for the people who just can't wrap their heads around all the things you need to learn about how the Kindle Fire works, although it is still useful for those who already have the knowledge. Hopefully it will prevent users from unnecessarily sending their devices back to Amazon (not that the damage hasn't already been done).
The SoupKit Utility can...
Detect bootmodes, effectively
Change bootmodes, quickly
Install custom recovery w/md5 check (from any bootmode)
Install any recovery you choose
Install custom or stock bootloader w/md5 check (from any bootmode)
Launch Pokey9000's Firekit, easily
Fix “Failure to mount...” issues (i.e. sdcard won't mount in recovery)
Transfer files to sdcard or other directory, easily
Prep device to safely “revert to stock” to prevent brickage
The SoupKit Utility will NOT...
Root the Kindle Fire
Work for 2nd generation devices
Fix app problems
Provide ETAs
Allow you to post in the development section
Make you more attractive
Fix stupidity (sorry, I tried)
This has only been tested on Ubuntu 12.x but should work for any Ubuntu and should theoretically work for any Debian based distro with apt-get installed.
How to use it:
Well, first you need Linux. OH NOES! Not the “L” word!
Luckily, all Linux distros are free to download and install on your computer. It can also be booted from a USB flash drive so you don't have to wipe out your current OS (although you probably should anyway). You can use a VM, but the only VM that I've found that can detect the Kindle Fire in fastboot mode is Parallels. Vmware won't cut it, and VirtualBox sure as hell won't cut it so don't waste your time with them if you ever need to do anything in fastboot (if you're bricked, you need fastboot). Probably the best method to get Linux running for a new user is by setting up a Linux LiveUSB.
I'm not going to teach you how to set up a Linux LiveUSB, but there are plenty of FREE programs out there that will not only create a Linux LiveUSB for you, but will download your choice of distro as well, and all you need is a USB flash drive (preferably 8GB or larger). A Google search of “Linux LiveUSB” will offer plenty of choices, although, PendriveLinux seems to be a favorite among most. Just be sure to add plenty of “persistence” (1 or more gigabytes) or you will lose everything every time you reboot. And the better quality of flash drive you can use, the better it will be in the long run. Some flash drives just don't do well and can cause some file system corruption over time (not something you want to be dealing with while you're having Kindle Fire problems).
You'll also have to figure out how to boot your computer from a USB. Check your computer's BIOS manufacturer website for instructions on how to do this.
If you're using a LiveUSB, there is no root/sudo password, just hit enter.
Once you have Linux installed and booted, you need to make sure your Internet is working. It may take some configuration on your part but it is necessary for the SoupKit to install properly. Luckily, once you have an Internet connection in Linux, the hard part is over.
Don't put the SoupKit.zip on the USB drive before creating the LiveUSB. Instead, use the web browser to navigate to this page and download it once you have Linux running and your Internet connected. Once it's downloaded, you'll likely find it in your Downloads folder. Right-click the “SoupKit.zip”, select “Extract here” open the SoupKit folder and follow the instructions in the README.
At any point after instalation, the SoupKit can be launched by opening a terminal window and entering “soupkit.sh” (without quotes).
Download:
[*]SoupKit w/SoupKit Utility 1.0
File hosting provided by Dev-Host.
No waiting, just high speed downloads. You're welcome
*If you have already installed the alpha version (8/32) of the SoupKit, delete your existing ~/bin/SoupKit folder before proceeding. This new version adds files necessary for some options found in the SoupKit Utility to work properly.
*The stock bootloader has been updated by Amazon to not display anything with "fastboot devices" and you can only enter one fastboot command at a time before you have to shut it down and start it up again. I have come up with a dirty workaround to deal with it so if you have a stock bootloader and get "Device Offline", just try to select one of the options anyway. The script will hopefully get you through it.
*32bit libraries are necessary for this to work. The script will detect whether you are running 32 or 64 bit and download the 32bit libs if necessary. The problem with this is Ubuntu is no longer supporting ia32-libs and they may or may not download when needed. It's best to use a 32bit system or create a 32bit LiveUSB to avoid any problems, although I've never personally had any problems downloading them.
I think that just about covers it. I've tried to make this as “new user” friendly as possible, while including as much error checking as I could think of, in order to prevent mishaps that may be caused by inexperience. If you have any trouble with this, please don't be afraid to ask (here preferably). In the meantime learn everything you can about your device so you won't be dependent on tools like this to get you out of a jam when things go really wrong.
Includes:
Team Win Recovery Project - TWRP 2.2.2.1
This is not the most recent release of TWRP for the Kindle Fire. I'll try to include the most recent release when the bugs get ironed out.
Cannibal Open Touch Recovery - COTR 2.0.2
Again, this may not be the most recent release of COTR, but be sure to check out the Official COTR forums and the COTR Google+ page.
* Fortunately, If you want to install a more recent version of the included recoveries or another one of your choosing, I have included an option to install ANY recovery.img at any point so there is no need to constantly update the utility.
FireFireFire - FFF 1.4a
FireFireFire 1.4a has the ability to change bootmodes on the fly. If you plan to do anything with your device at all, definitely install this bootloader. It will save you plenty of heartache in the future.
Stock Kindle Fire bootloader (for testing purposes)
Firekit
I can't say enough about the Firekit...so I'm not going to try. If you ever have a problem where your device will show absolutely no outward signs of life, you definitely need the Firekit
Disclaimer: I've said it before and I'll say it again...I take no responsibility for anything, EVER. Use this at your own risk. If the Kindle Fire explodes in your lap, burning the hair off your man purse, don't come crying to me. If you used this tool with a Kindle Fire 2 or Kindle Fire HD and turn your device into a doorstop, don't come crying to me. If your girlfriend/wife leaves you because you broke her brand new Kindle Fire from using this tool...on second thought, go ahead and send her crying to me, I'll fix it.
Credits & Thanks:
kinfauns - "practically" (<-he made me say it) everything I ever learned about the Kindle Fire, I learned from him. His guides are the most comprehensive Kindle Fire guides on the Internet (prove me wrong). If you want to get the most out of your Kindle Fire experience, go and read all of his posts. You'll be amazed at what you'll learn. kinfauns was an invaluable mentor to me and without him trying to keep me on the "straight and narrow", this would have taken a lot longer to complete. I cannot thank him enough for what I've learned.
Thepooch - for always being there when I needed something tested, and always being able to catch things that I would have missed otherwise.
Pokey9000 - for FireFireFire, the Firekit and his bootmode binaries. Pokey is a quiet force around here but his knowledge and advancements have saved many users from getting stuck with $200 paperweights (including me). Send a donation his way, he deserves it.
Hashcode - for FireFireFire 1.4 and pretty much everything else he's done for us. His constant support for this lowly device speaks volumes of his character and it will be a devestating blow to our community if he ever decides to leave us.
sblood86 - for Canibal Open Touch Recovery and his tutorial on enabling adb in Ubuntu.
Dees_Troy and Team Win - for Team Win Recovery Project. TWRP has been by far the most supported and stable open recovery I've seen.
forest_1971 - for his repartitioning tutorial
smirkis - for inadvertantly giving me the idea to learn shell scripting and start work on the SoupKit
Tahl - for allowing me to study some of his scripts and acquire an immense amount of knowledge from them.
All the people who helped me test the script in it's earlier stages.
Anyone else I may have forgotten.
The entire Kindle Fire XDA community
I hope this helps you to fix your Kindle Fire problems. If anyone has any questions, please, don't be afraid to ask...I'll be glad to help.
Reserved
Changelog:
10-23-12
Full release of SoupKit w/SoupKit Utility v1.0
8-27-12
Initial release of the SoupKit_a Installer
Reserved
Thank you VERY much. What perfect timing, yesterday I set my PC up to dual boot Ubuntu. I got everything setup and followed the directions in Sblood86's instruction thread to Enable adb under Ubuntu but I messed something up because adb devices didn't find my KF. Just found your thread, installed the Soupkit and success first try. Now I don't have to figure out what I did wrong. Saved me a lot of time so thanks again.
Sent from my Amazon Kindle Fire using xda premium
UPDATE: It appears your "Idiot-proof" comment may have underestimated some of us. I was playing with adb today and ran into a problem. Some adb commands, devices and push for example, work perfectly. However I could not use adb to change boot modes.
When I enter
adb shell ome idme bootmode 5001
I get an error
Invalid permissions
So I tried putting sudo in front of it and I get
sudo: adb: command not found
I am confident this is easy to fix but I am just learning adb and Ubuntu. I have been reading all of the beginner guides I can find but I haven't found a solution yet so any help would be appreciated, thanks.
Edit----
NEVERMIND - SOLVED- I obviously combined the fastboot and adb commands together. Leave the ome part out and it works perfectly. I said you underestimated us idiots.
Thanks again for the great kit.
Sent from my Amazon Kindle Fire using xda premium
JimCo06 said:
I said you underestimated us idiots.
Click to expand...
Click to collapse
Nope, not at all.
Thanks again for the great kit.
Click to expand...
Click to collapse
Oh, No...Thank You
In all seriousness, I'm glad everything worked out for you. If you ever need anything or have anymore "questions", please, don't be afraid to ask.
Edited: Solved!
Thank you!
You are the man .
For those who wonder I use this to create the live usb http://www.pendrivelinux.com/universal-usb-installer-easy-as-1-2-3/ must be quick formatted in windows fat32
And this distro of linux http://www.linuxmint.com/edition.php?id=103 32 bit
Just a little configuring in the control center if your using a touch pad mouse..
And keyboard shortcut for terminal can be added as well...
Great script. Thank you
Sent from my Galaxy Nexus using Tapatalk 2
Idiot proof you say??
soupmagnet said:
Wait, what? Idiot-proof?
yeah, but seeing as anyone on linux likely knows how to use a computer at least reasonably well and anyone on linux and xda surely will, you shouldn't need idiot proofing. Though having said that...
will this work with non kindle devices, ie the nexus 7?? I know this is in the kindle fire forum section, but is this universal??
Click to expand...
Click to collapse
Fallon9111 said:
yeah, but seeing as anyone on linux likely knows how to use a computer at least reasonably well and anyone on linux and xda surely will, you shouldn't need idiot proofing. Though having said that...
Click to expand...
Click to collapse
1) The "Idiot-proof" part of the title is out of humor and fun, get over it.
2) Pay attention. The Soupkit is for people who otherwise have no other working options with Windows (and there are plenty), not people who ALREADY know Linux, although it does make the process a lot easier. I thought I made that perfectly clear.
will this work with non kindle devices, ie the nexus 7?? I know this is in the kindle fire forum section, but is this universal??
Click to expand...
Click to collapse
3) Seriously? No. KF only.
Well the xda-developers portal post that links here definitely makes it sound as if this works with other android devices. I was about to install this. Sorry to bug ya, but would you care to explain why this is KF only. I apologize, but am curious and this would make some things much easier for any droid noobs. like me
beekah said:
Well the xda-developers portal post that links here definitely makes it sound as if this works with other android devices. I was about to install this. Sorry to bug ya, but would you care to explain why this is KF only. I apologize, but am curious and this would make some things much easier for any droid noobs. like me
Click to expand...
Click to collapse
It is just a simple shell script that installs and configures the adb driver and sets udev rules for the Kindle Fire. You can edit the script and add that particular information for your particular device pretty easily, if you know what to look for.
soupmagnet said:
Testing on ArchLinux proved to be unsuccessful so don't waste your time.
Click to expand...
Click to collapse
Hey soupmagnet install_it.sh contains Debian- and APT-specific commands, packages and paths so it will not work on non-apt distros (apt-get, dpkg, ia32-libs).
The script also makes use of addgroup, which may not be available on other systems. /etc/init.d is also distro-specific, as for e.g. Arch has rc.d.
Otherwise, it's all good. New users (that is, for this use case) should be directed to get Ubuntu or Mint anyway. Just thought this info should be up at a glance in case someone's interested in the Whys.
Yeah this guy must think debian is the only linux out there. How bout some arch support?
Edit: Just checked and nowhere in the OP does the word DEBIAN come up. Even though it is the only type of linux this will work on.
tyler1234567 said:
Yeah this guy must think debian is the only linux out there. How bout some arch support?
Click to expand...
Click to collapse
Just for that...
tyler1234567 said:
Yeah this guy must think debian is the only linux out there. How bout some arch support?
Click to expand...
Click to collapse
I learned shell scripting for the sole purpose of putting this script together. If you don't like the way it is, then go do it better...please.
Bump
The full release is finally here...OP Updated.
I'd like to put together a guide outlining how to root/S-OFF an Android Incredible 2 with Mac OS X, and perhaps develop a tool to assist. I've just done it with Parallels and Windows 7 via Revolutionary, but it seems to me there *must* be a way to do it directly. I know I can get ADB working, and issue commands via the terminal. The recoveries and ROMs are platform independent. Can someone tell me what a tool like Revolutionary actually *does* on a Linux system? Is it simply a matter of scripting a series of commands to perform some actions on some files? I don't seem to be able to find much reference on the nuts and bolts of the process, but it seems like duplicating it in Unix should be fairly simple. Any info or directions to further documentation would be much appreciated!
Edit: All I really need is link to some directions for manually rooting an Android Phone (and achieving S-OFF). Maybe something older, from before the days of packages like Revolutionary? Anyone?
Edit 2: OK, how about just very rough list of what ADB does during a Revolution-like session (send commands, push files)? If I can figure this out perhaps I'll have something to offer the thousands of Mac users who want to root their Android phones.