Related
I have been trying to get the kindle fire software running on the Gtablet, so far I can get through registration. After that force closes like crazy. If anyone has any ideas that might help feel free to discuss, in the mean time I will keep at it and see what happens, and if I get it to a useful state I will release it. I am currently using Flashback as a base which may account for some of the issues since the kindle fire runs 2.3 however I have had less apps crash on HC.
I have added crash logs below and rather than upload all the apps/libs that are required to even boot the launcher, I have uploaded a CW rom flash for the 1.2 bootloader only!! The rom is tlbardelljr's Flashback with some amazon stuff added.
*Update* I have managed to get it past registration, but then it force closes (com.amazon.kindle.otter). I am now at a stand still until I either learn more about modding apps to work with the core os, or I find a developer who has more knowledge than I to help get this going. If you are interested in helping and are knowledgeable in this area please contact me with a PM. Thanks, and in the mean time I will get to learning
*Update 11-26-11* Thanks to rajeevvp I am getting a little bit further with sorting out errors (I get past registration now) hopefully I will have something new soon.
*Update 12-6-11* The issues appear to be OpenGL/Driver related now, so for now I am putting this project aside. If anyone would like to take over from here feel free.
Warning: This is for testing purposes only!!! Be sure you know how to use nvflash!!!
Code:
11-26 12:31:39.927: W/InputManagerService(1031): Got RemoteException sending setActive(false) notification to pid 2203 uid 10025
11-26 12:31:39.927: E/AndroidRuntime(2393): FATAL EXCEPTION: GLThread 14
11-26 12:31:39.927: E/AndroidRuntime(2393): java.lang.IllegalArgumentException: Thread: + GLThread 14 No configs match config spec
11-26 12:31:39.927: E/AndroidRuntime(2393): at com.amazon.kindle.otter.ogl.FSAAConfigChooser.chooseConfig(FSAAConfigChooser.java:102)
11-26 12:31:39.927: E/AndroidRuntime(2393): at android.opengl.GLSurfaceView$EglHelper.start(GLSurfaceView.java:981)
11-26 12:31:39.927: E/AndroidRuntime(2393): at android.opengl.GLSurfaceView$GLThread.guardedRun(GLSurfaceView.java:1326)
11-26 12:31:39.927: E/AndroidRuntime(2393): at android.opengl.GLSurfaceView$GLThread.run(GLSurfaceView.java:1180)
11-26 12:31:39.937: D/SurfaceFlinger(1031): screenshot: sw=173, sh=101, minZ=0, maxZ=21010
11-26 12:31:39.937: W/ActivityManager(1031): Force finishing activity com.amazon.kindle.otter/.Launcher
http://www.multiupload.com/HW4GXSCNF7 - Rom
http://www.multiupload.com/1HBY5YH7ST - Full Crash Log
Just out of curiosity. Since the Kindle Fire software was developed for froyo, have you tried like a vegan tab 5.11 ROM. I know some modules in the kernel software are present in the vegan froyo ROMS that are not present in the later kernels. This is a great idea and I will be watching this thread with great anticipation. Maybe you could post the software you are trying to load. Like if it is an APK host with mediafire or something. Then others like me can download and try to get it working too. once again GREAT IDEA!!!!!
Awesome, this is exactly what I want, wish I could help
Sent from my HTC Glacier using xda premium
I thought the kindle fire was gingerbread?
Sent from my GTablet using Tapatalk
I think you are right. I read an old article, it is 2.3. I will be updating with my crash logs and files soon.
Sent from my Nexus S using XDA App
barracudacm said:
Just out of curiosity. Since the Kindle Fire software was developed for froyo, have you tried like a vegan tab 5.11 ROM. I know some modules in the kernel software are present in the vegan froyo ROMS that are not present in the later kernels. This is a great idea and I will be watching this thread with great anticipation. Maybe you could post the software you are trying to load. Like if it is an APK host with mediafire or something. Then others like me can download and try to get it working too. once again GREAT IDEA!!!!!
Click to expand...
Click to collapse
I have tried vegan with no luck, the launcher won't even start on vegan. I have also tried to make a full from port with the vegan kernel and I can't get it to boot. I am not super experienced with ports though. I am a themer at heart, but just decided to try this because it is something that I would use a lot.
Sent from my Nexus S using XDA App
I am guessing they made quite a bit of changes to the underlying system
Sent from my HTC Glacier using xda premium
the3dman said:
This is the main error I am trying to figure out (com.amazon.dcp):
Click to expand...
Click to collapse
At least 3 errors are readily evident from the log file.
1. "No JNI_OnLoad found in /system/lib/libCommonWrapper.so 0x40587208, skipping init"
This looks like the wrong libCommonWrapper.so library is being used. Check for multiple copies of this file, or, if there is only one copy, try using the /system/bin/linker and /system/lib/libdl.so from the Kindle Fire.
2. "Error creating directory /system/etc/labdictionary"
The /system partition may be mounted read-only or the application trying to create the directory might not have permissions to create it in /system/etc. Create the directory and use the permissions of the original dir on the Kindle Fire.
3. "Native KRF library failed to load.
java.lang.UnsatisfiedLinkError: Couldn't load ft2KRF: findLibrary returned null"
This looks like a straightforward library missing problem. Look for any *KRF* in /system/lib on the Kindle Fire and copy those files to the same place on your ROM.
rajeevvp said:
At least 3 errors are readily evident from the log file.
1. "No JNI_OnLoad found in /system/lib/libCommonWrapper.so 0x40587208, skipping init"
This looks like the wrong libCommonWrapper.so library is being used. Check for multiple copies of this file, or, if there is only one copy, try using the /system/bin/linker and /system/lib/libdl.so from the Kindle Fire.
2. "Error creating directory /system/etc/labdictionary"
The /system partition may be mounted read-only or the application trying to create the directory might not have permissions to create it in /system/etc. Create the directory and use the permissions of the original dir on the Kindle Fire.
3. "Native KRF library failed to load.
java.lang.UnsatisfiedLinkError: Couldn't load ft2KRF: findLibrary returned null"
This looks like a straightforward library missing problem. Look for any *KRF* in /system/lib on the Kindle Fire and copy those files to the same place on your ROM.
Click to expand...
Click to collapse
Thanks for the assistance, it is much appreciated. I will definitely try these.
Sent from my Nexus S using XDA App
rajeevvp said:
At least 3 errors are readily evident from the log file.
1. "No JNI_OnLoad found in /system/lib/libCommonWrapper.so 0x40587208, skipping init"
This looks like the wrong libCommonWrapper.so library is being used. Check for multiple copies of this file, or, if there is only one copy, try using the /system/bin/linker and /system/lib/libdl.so from the Kindle Fire.
2. "Error creating directory /system/etc/labdictionary"
The /system partition may be mounted read-only or the application trying to create the directory might not have permissions to create it in /system/etc. Create the directory and use the permissions of the original dir on the Kindle Fire.
3. "Native KRF library failed to load.
java.lang.UnsatisfiedLinkError: Couldn't load ft2KRF: findLibrary returned null"
This looks like a straightforward library missing problem. Look for any *KRF* in /system/lib on the Kindle Fire and copy those files to the same place on your ROM.
Click to expand...
Click to collapse
I have set permissions and created the directory but am still getting: "Error creating directory /system/etc/labdictionary"
Also I cannot use the linker from the kindle I just get bootloops when I try.
Not quite sure if this will help. But here is a gingerbread kernel that slimm6099 compiled for me for use with gingerbread. He used alot of normally unused modules to make it,.. including loop device support and swap functionality. Just thought it might help.
http://dl.dropbox.com/u/14075340/barracudacm-kernel.zip
p.s. I cant boot linux or bactrack5 on gingerbread without this kernel. (dont know if thats relevant?!......)
barracudacm said:
Not quite sure if this will help. But here is a gingerbread kernel that slimm6099 compiled for me for use with gingerbread. He used alot of normally unused modules to make it,.. including loop device support and swap functionality. Just thought it might help.
http://dl.dropbox.com/u/14075340/barracudacm-kernel.zip
p.s. I cant boot linux or bactrack5 on gingerbread without this kernel. (dont know if thats relevant?!......)
Click to expand...
Click to collapse
Thanks, I will give it a shot.
Sent from my Nexus S using XDA App
the3dman said:
I have set permissions and created the directory but am still getting: "Error creating directory /system/etc/labdictionary"
Click to expand...
Click to collapse
Hmm. That's strange. Are other dirs/files missing? Try doing a filesystem comparison using the file listing on both devices using adb if possible. On a Linux system (on Windows, install Cygwin first):
Code:
[I]Connect gTab to PC[/I]
$ [B]adb shell find /system | sort > gtab-find.txt[/B]
$ [B]adb shell ls -lR /system > gtab-ls.txt[/B]
[I]Disconnect gTab and connect Kindle Fire[/I]
$ [B]adb shell find /system | sort > kfire-find.txt[/B]
$ [B]adb shell ls -lR /system > kfire-ls.txt[/B]
[I]Find differences[/I]
$ [B]diff -Bbu gtab-find.txt kfire-find.txt[/B]
Then look for dirs/files missing on the gTab and use the detailed listing in the kfire-ls.txt as a guide to creating the correct permissions.
Also I cannot use the linker from the kindle I just get bootloops when I try.
Click to expand...
Click to collapse
That is a risk you always take when messing around with the linker. Did you also copy the /system/lib/libdl.so library? Try using the linker and libdl.so from the latest CyanogenMod update.zip file.
rajeevvp said:
Hmm. That's strange. Are other dirs/files missing? Try doing a filesystem comparison using the file listing on both devices using adb if possible. On a Linux system (on Windows, install Cygwin first):
Code:
[I]Connect gTab to PC[/I]
$ [B]adb shell find /system | sort > gtab-find.txt[/B]
$ [B]adb shell ls -lR /system > gtab-ls.txt[/B]
[I]Disconnect gTab and connect Kindle Fire[/I]
$ [B]adb shell find /system | sort > kfire-find.txt[/B]
$ [B]adb shell ls -lR /system > kfire-ls.txt[/B]
[I]Find differences[/I]
$ [B]diff -Bbu gtab-find.txt kfire-find.txt[/B]
Then look for dirs/files missing on the gTab and use the detailed listing in the kfire-ls.txt as a guide to creating the correct permissions.
That is a risk you always take when messing around with the linker. Did you also copy the /system/lib/libdl.so library? Try using the linker and libdl.so from the latest CyanogenMod update.zip file.
Click to expand...
Click to collapse
Thanks for the help, I will attempt this when I have a free chance.
I'm really hoping to see this working on g tablet soon. I'd like to see what the kindle fire software is like.
bdds13 said:
I'm really hoping to see this working on g tablet soon. I'd like to see what the kindle fire software is like.
Click to expand...
Click to collapse
Same here, this will be really cool.
Well after playing around some more I got it narrowed down to one major issue. OpenGL seems to be what is now causing the force close, and I think until we get some proper drivers we are sol. I could be wrong, like I stated in the OP I am just an amateur at this. So for now I am going to take some time away from this, but if anyone would like to pick up from where I am leaving off then feel free.
the3dman said:
Well after playing around some more I got it narrowed down to one major issue. OpenGL seems to be what is now causing the force close, and I think until we get some proper drivers we are sol. I could be wrong, like I stated in the OP I am just an amateur at this. So for now I am going to take some time away from this, but if anyone would like to pick up from where I am leaving off then feel free.
Click to expand...
Click to collapse
I think you are right, the problem with all the ROMS for G tablet seems to be proper Nvidia drivers.
Hi All:
I'm a long time Viewsonic GTablet owner and have ran just about every ROM xda/slatedroid/ and other have to offer.
I really appreciate the work that ppl have done here but was curious as to why other than just because we can.
My friend has purchased a Kindle Fire and there are a few things really like about it and somethat I really hate. This all JMO and in no way am I trying to knock the work being done here. With that said, here are some of my observations:
-PRO- Kindle Fire UI is one of the cleaniest I have ever seen and I've been a tablet user for over a year now.
-PRO- the "newstand" UI concept is one that can get even the most non tech person into a tablet with the least amount of pain
-CON- Marketplace is not available
-CON- need to setup yet another email account on amazon (cant use a google account)
-CON- cant add additional mail accounts (gmail, yahoo, hotmail, etc) simpily
My overall impression is that the Fire is a inexpensive Ipad for digital consumer that want to do just that, consume, and not pay $700 to have the right to do so.
Good luck too all and happy holidayz, I'll keep an i-out to see if we make any progress and will glady be a alpha-beta tester.
nyciz said:
Hi All:
I'm a long time Viewsonic GTablet owner and have ran just about every ROM xda/slatedroid/ and other have to offer.
I really appreciate the work that ppl have done here but was curious as to why other than just because we can.
My friend has purchased a Kindle Fire and there are a few things really like about it and somethat I really hate. This all JMO and in no way am I trying to knock the work being done here. With that said, here are some of my observations:
-PRO- Kindle Fire UI is one of the cleaniest I have ever seen and I've been a tablet user for over a year now.
-PRO- the "newstand" UI concept is one that can get even the most non tech person into a tablet with the least amount of pain
-CON- Marketplace is not available
-CON- need to setup yet another email account on amazon (cant use a google account)
-CON- cant add additional mail accounts (gmail, yahoo, hotmail, etc) simpily
My overall impression is that the Fire is a inexpensive Ipad for digital consumer that want to do just that, consume, and not pay $700 to have the right to do so.
Good luck too all and happy holidayz, I'll keep an i-out to see if we make any progress and will glady be a alpha-beta tester.
Click to expand...
Click to collapse
I am also a kindle fire owner. When I am not making themes for my GTab, I really only use the GTab as an e-reader and to browse the net. I never use the google market on it, I use the amazon one though for the free apps, I don't check email on it I either use my nexus s or my computer. So really the only stuff I use is the amazon stuff, so I figured why not just have 2 kindle fires around the house so that when my wife is reading on the real fire, I have my own GFire to read on with a bigger screen. But I was also doing it because I love the UI and like you said because I can (It was something to keep my busy).
Port Kernel3.x for kindle fire To get full HW Accelorate., Any suggestions?
Now we have:
uboot for kf :kf_u-boot(FIREFIREFIRE) , by pokey9000
Kernel for kf: kernel2.6.35, by Steven Lin
Android for kf: Kindle-Fire-CM9 ,by JackpotClavin
Is anyone interesting the really full function CM9 for Kindle fire?
Let's do it together!
MOD edit: email addresses removed, these should remain private
And now the UART is work.
So .......
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Try this... delete your drivers and configure and reinstall your own from the AndroidSDK
http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
Then use command prompt to issue the appropriate adb and fastboot commands to manually root your device using the method posted here:
http://forum.xda-developers.com/showthread.php?p=24124828
If, after you reinstalled your drivers, you can't get adb to connect through command prompt, you may need to make sure that your user account has the appropriate permissions to perform such tasks (although I can't imagine why you wouldn't anyway).
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
I am inclined to agree with you with so many different instructions with different levels of experience how the new user can achieve root and proper driver installation has become muddled to the point where people are getting stuck in modes rendering thier devices unseen by thier computers. Stuck in fastboot or recovery or soft and hard bricked with batteries draining and time running out to achieve a fix. There is a serious need for a clear easy exploit for very low experience level OS dedicated. KFU worked perfect for me and so did adb but with others it has created a problem if I had the knowledge base to build a one click wonder I would but its way out of my experience level even though I have successfully rooted every device I have 2 kindles a galaxy tab 10.1 and my droidx after the .621 ota for droidx. So where do we go from here?
kinfauns said:
I've seen you mention the Android SDK a number of times as it relates to driver installation. This is not meant as an argumentative post, but the SDK is entirely unnecessary if the user won't be "developing" software and just wants to install the drivers.
The SDK method is a lot of unneeded bulk to install the Java JDK, so you can install the Android SDK installer to get at the USB driver extras. Then the user has to go manually edit the .INF file with the necessary KF details before installing. Then create the .android folder in the right place and add a correctly named .INI file with more information. All these hoops create problems because most people who come here looking for help are flustered enough as it is and missing any one of these things or doing it wrong will just cause more issues that will have to be ironed out. It's just a bad idea all around.
And just in case you believe that the SDK drivers are somehow "better" than the KFU ones... they're not. All of the relavant files are identical. When I was writing my drivers guide, I checked them all to see if it could be a potential source for differences on why one install would work and not another. All of the md5 checksums for each and every .DLL and .CAT file match each other.
The only difference I found was in the source.properties files and that was just in the order of the name=value pairs at the bottom and the SDK distribution has an "Extra.NameDisplay=Google USB Driver" pair while the KFU one does not. I tried to find out how this file gets used in the driver installation, but the fact that I came up empty leads me to believe that it's a a non-player in the whole scheme of things.
Of course, the android_winusb.inf file is different between the two because some Kindle Fire specific information has already been added to it in KFU, but this is a good thing because you won't have to go do it manually and therefore skip an error prone task.
Please do not complicate matters by having people do this unnecessarily. If people want to install the drivers manually, they can point the driver update wizard to the KFU folder containing the android_winusb.inf file and it will do the same thing. If they use KFU's install_drivers batch file to install, they'll even get the .android folder created in the right place and the adb_usb.ini tossed in there with the correct values.
If you believe my reasoning is flawed, please let me know how installing from the SDK makes a difference. If you have a sound argument, I'm perfectly willing to admit my wrong, change my position and my guide as well.
Click to expand...
Click to collapse
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
That being said, the people that I told to do it the "hard" way haven't needed any further help.
And if it does come back to bite me in the ass, you can rest assured, I'll eat my words.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Yes, I know.
The point is to get people to forget about KFU for a minute and learn to do it the right way first (so as not to get distracted) so when they ARE ready to use a utility like the KFU they will know what to do when problems arise. You learn to do it the hard way first (one that will be around LONG after the KFU is gone) and THEN you can take shortcuts. That's pretty much standard procedure for learning anything.
I think it's safe to say that the KFU has caused more problems for newbies than has helped. And the ones it has helped usually have to learn the old way anyway. I'm just trying to get rid of the middleman.
Just think of how great this place would be if everyone knew how to how to do this on their own.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him.
---------- Post added at 09:47 PM ---------- Previous post was at 09:43 PM ----------
marcelloLins said:
Hi everyone, i am trying to root my kindle fire device , but the process is not working.
Here is what i've done:
1. Installed Drivers from "install_drivers.bat" file from KFU
2. Manually Installed Drivers
Still cannot make ADB Status to go "ONLINE".
The way i can make it "ONLINE" is by executing the "run.bat" file as administrator, but, doing this, leads me to error "cannot find tools/wget.exe". Ofc, because running with administrator privileges forces it to run from system32 folder.
I've already tried to run from the Command Prompt, even running the command prompt as administrator aswell.
Any idea of how to solve it ?
My Kindle is 6.3 Version. I bought it in February.
I used the KFU 0.9.5 version.
I also tried to install drivers manually, from a difference source ( a youtube video tutorial of how to root 6.2 version ), but, the device manager says the drivers are already up to date.
My device manager shows a "Android device" at the top of the list, but no "Kindle" or "Amazon Kindle" device in the whole list.
What am i doing wrong ?
Please, if you can't solve it, at least, bump this thread.
Thanks !
Click to expand...
Click to collapse
So, instead of totally hijacking this thread for the sake of an argument...
I think you need to confirm that your drivers are installed properly. Regardless of what path you take to get them installed, pay attention to the middle part of this post...
http://forum.xda-developers.com/showpost.php?p=23747671&postcount=2
and make sure that you are seeing the right things in the device manager. You'll have to verify that part of it is working right, so Windows and the Kindle Fire are able to communicate with each other before moving ahead in your troubleshooting.
kinfauns said:
I get your point about KFU and I think my guide is evidence of that. However, I'm in complete disagreement about your suggestion for the driver installation process. I don't believe fixing one's Kindle Fire should first involve learning the roundabout way of installing the drivers. In my mind, the KFU utility is entirely separate from the driver installation batch file. I see no good reason make that part of it any more difficult than it has to be. I also think your middleman analogy is a bit flawed. It's more like having the guy go chop down a tree in the dead of night when you've already got a stack of firewood for him
Click to expand...
Click to collapse
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
soupmagnet said:
Let me say just this and I'll let it be. Ask yourself, "What's more likely to stand the test of time? Android SDK or KFU?" What happens when KFU becomes obsolete/unmaintained and is no longer hosted for people to download? What happens when KF owners move on to other Android devices not supported in such a way? Configuring and installing device drivers is a basic skill that every Android device owner should have anyway, and it causes no harm pushing people to learn it. I'm not breaking any rules by doing so and until now you are the only one to have had a problem with it.
That being said, don't let my disagreement fool you into thinking I have anything anything less than the utmost respect for you. - Quite the contrary in fact. I personally have learned a lot from you and many others here and I feel it is my duty to pay it forward. I apologize if the method I use offends you, and if others here feel the same way I will definitely take it into consideration.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Believe me, I'm not offended by this discussion. We are just having a respectful disagreement over a mutually shared desire to help people who want to mod their KF. I understand that you aren't doing anything wrong. I'm not wagging my finger at you or yelling, "my way or the highway!" It's just my belief that going the SDK route is error prone and the cost/benefit of doing it that way may be too high for most users to bear.
Let me share an experience I had with someone who PM'd me for help after deciding to install the drivers from the SDK. After days of back and forth, he figured out that he had created the adb_usb.ini file as a text file and Windows was hiding the file suffix. So, he actually had an adb_usb.ini.txt file and with Windows Explorer only showing the adb_usb.ini part, he hadn't really considered the possibility that the file could have been named incorrectly. It's the silly things that will trip up even a knowledgeable user.
I'm not saying never to the SDK... I'm just saying it shouldn't be the first choice. I certainly won't be upset if you decide to instruct users to install the SDK just for the drivers, but they might be if they figure out they could have gotten to the same place with KFU's driver installer in 1/20th of the time.
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
-----------PROJECT HAS BEEN ABANDON AND IS OBSOLETE----------
WORKS ON 5.1.1 ALSO!
(Link in next reply)
Fully automated and noob friendly. :3
Done:
Root
BusyBox
Disable OTA
Change Launcher
Install full Google Play Functionality
Autoinstall flash player
build.prop optimizations
A few more features...
This may be compatible with other fires, but I have only tested it on the Fire 7" 5th generation.
This is a script I wrote in my spare time.
This script will optimize, root, install google play, and debloat your device.
Enjoy :3 Don't forget to hit thanks.
STEPS
1. In device options, tap on serial number until the developer options appear. If required (which it is likely not, but for some it is. DON'T DO THIS IF IT'S ALREADY WORKING.) install the ADB driver by going into the device manager of windows and rightclick update driver on your device under unkown devices, then point it to the driver folder included in this zip, or, you know, try the driver installer .exe included. Make sure driver signature enforcement is disabled in Windows!
2. Go into the developer options of android and enable Debugging
3. Go to the homescreen on the tablet, EXTRACT the zip on your computer, and run the script 1_ROOT_FIRE.bat in the zip on your computer.
This should only take around five minutes too complete.
YOUR DEVICE WILL REBOOT SEVERAL TIMES.
Easy enough, right? :3
Troubleshooting:
Unless you are running Fire OS 5 or higher, using this script probably won't get you playstore access, but it may root it. This was made primarily for the Amazon Fire 5th Generation 7" Tablet. (The "50 dollar tablet")
Don't run as root or admin.
If your device gets stuck in fastboot:
When the device reboots and goes into fastboot mode the drivers didn't recognise it. Leave the script running and go into Device Manager. Your Kindle will be listed as "Fire" with a yellow icon. Follow same steps to install drivers but instead of directing it to the "usb driver" folder contained in the zip file - select "let me pick from a list of drivers". Then pick adb interface then scroll to the bottom and select the last option.
The script hangs on adb daemon started:
If it hangs there, android debugging on your device isn't communicating with your computer. The fix can range from reconnecting your device, making sure android debugging is enabled in the Device> Developer options, making sure adb drivers are installed, or restarting the script.
Keep in mind, if you give this tablet to a non tech savvy user, open SuperSU, go to options, and click full unroot.
XDA:DevDB Information
AutoRootScript, Tool/Utility for the Amazon Fire
Contributors
glitch3yf0x, JaboJG, KennBr, k4y0z
Version Information
Status: Stable
Current Stable Version: 4.14
Created 2015-12-30
Last Updated 2016-04-08
Secondary Download Mirror
(Recommend) REGULAR VERSION:
https://www.androidfilehost.com/?fid=24352994023705981
NO DEBLOAT version:
https://www.androidfilehost.com/?fid=24391638059059079
Read the post below to choose the version right for you.
Version diffrences
Regular version: Choose this if you want the full android experience to your tablet with the added features of the script. This will remove all the unwanted Amazon bloatware that fills up the internal storage and will make your tablet feel more like an android tablet.
No debloat version: Choose this if you want to keep the Amazon experience with the added features of the script. This will leave Amazon's features and will make your tablet feel more like an Amazon tablet.
Notice: this script will not wipe or touch any of your files on the internal storage or sd card
Fully stable!
Great news! All bugs have been fixed! As of version 4.14 uploaded 1/5/16, all OS versions have been tested and are confirmed working properly. Enjoy!
If anything goes wrong, such as a USB cable being unplugged or the battery dying, pretty much anything can be fixed by booting into recovery and adb sideloading the latest firmware.bin from amazon.
Thanks for Donating:
Lorenzo
@BarbaraaK
So was the Mac OS X issues fixed?
pride0929 said:
So was the Mac OS X issues fixed?
Click to expand...
Click to collapse
I believe so [Old post. Issue fixed with 4.14, if there was one.]
I ran the script using OS X, everything seemed to go well. But the Fire is stuck booting at the "fire" logo.
Mac OS X
jmallow said:
I ran the script using OS X, everything seemed to go well. But the Fire is stuck booting at the "fire" logo.
Click to expand...
Click to collapse
Updated issue. [Issue fixed with 4.14, if there was one.]
glitch3yf0x said:
Give it 10 minutes before force rebooting. It may be rewriting cache. This is very odd. Any error messages on the computer?
Don't worry about your tablet. We can adb sideload if anything wen't wrong.
What OS is your tablet running? Is your tablet the Fire 7? It may be an issue with build.prop. I'm retesting it now using the Mac OS X source files. In the mean time, tell me if your Fire boots.
Click to expand...
Click to collapse
It's a 5th gen Fire 7 (the one that was released in Sept 2015). I side loaded to get back to factory, but mistakenly used the fire hd .bin file...and now it won't turn on at all. Lol. Might be a dead battery though I think, so its plugged in now. Will try again after a bit.
jmallow said:
It's a 5th gen Fire 7 (the one that was released in Sept 2015). I side loaded to get back to factory, but mistakenly used the fire hd .bin file...and now it won't turn on at all. Lol. Might be a dead battery though I think, so its plugged in now. Will try again after a bit.
Click to expand...
Click to collapse
Alright. Best of luck. I tested it on my fire again and there were no problems. If you have problems the second time tell me.
Any results?
glitch3yf0x said:
Any results?
Click to expand...
Click to collapse
I bricked it by installing the wrong version by mistake.
Hopefully Amazon warranty will replace it without question.
I've just run the script for my daughters fire 6 5th gen running 5.1.1 and all went smoothly. Has the look and feel of a great wee device now!
Thanks for your efforts ☺
Thread moved from http://forum.xda-developers.com/amazon-fire/general/root-fire-5th-gen-autoroot-script-noob-t3276923
Just installed this without a hitch. So far so good!! Thank you!!
Worked really well on 5.1.1 Thank you so much!
Now the only issue I have is that I want to use Google Now Launcher in place of Nova. Is there a way to do it?
EDIT: Never mind, it asked me which home to set after a reboot.
thehrushi said:
Worked really well on 5.1.1 Thank you so much!
Now the only issue I have is that I want to use Google Now Launcher in place of Nova. Is there a way to do it?
EDIT: Never mind, it asked me which home to set after a reboot.
Click to expand...
Click to collapse
I should post a poll. Google Now or Nova.
glitch3yf0x said:
I should post a poll. Google Now or Nova.
Click to expand...
Click to collapse
Just add a selector in the script and have it push the appropriate apk
BaT420 said:
Just add a selector in the script and have it push the appropriate apk
Click to expand...
Click to collapse
I was gonna suggest the same. Nova after rooting makes sense, since the widgets work. But I like Google Now on left swipe.
Yeahhh
Very good. Fire 7 2015 5.1.1.
Now I've an Android table not a garbage :good:
thanks a lot.
GitHub - testandroidtests/amazon_onyx_dump at onyx-user-7.0-PS7318-1957-amz-p,release-keys
Contribute to testandroidtests/amazon_onyx_dump development by creating an account on GitHub.
github.com
This was done through a sql injection on my pc then a dna hijack and I plugged my fire into my switch which they were using as a bridge finally got the group out of my system but I’d like to know if I can get maybe Kali or cinnamon or another Linux distro now I have downloaded the toolbox tried every they have I think there is a hidden partition I have a fresh 128g sd i could flash or any other ideas!!! This was also a 2020 fire 8 10th gen
Synikkk said:
GitHub - testandroidtests/amazon_onyx_dump at onyx-user-7.0-PS7318-1957-amz-p,release-keys
Contribute to testandroidtests/amazon_onyx_dump development by creating an account on GitHub.
github.com
This was done through a sql injection on my pc then a dna hijack and I plugged my fire into my switch which they were using as a bridge finally got the group out of my system but I’d like to know if I can get maybe Kali or cinnamon or another Linux distro now I have downloaded the toolbox tried every they have I think there is a hidden partition I have a fresh 128g sd i could flash or any other ideas!!! This was also a 2020 fire 8 10th gen
Click to expand...
Click to collapse
Nobody has any ideas
I don't think anyone has any idea what happened, what you're asking, or what you did.
Yeah sorry after re reading it doesn’t sound right, I got hacked they seem to have rooted it for me remotely lol but I want to turn it into a Linux machine anyway or at least a form of or something close but I don’t know what to do it has exactly what’s on the GitHub I can’t factory reset cans clear partitions have no authority all my apps that run in the background I can’t turn off so I need some help on deciding where to go from here how does one turn a hacked fire 8 into a Linux machine or something close
Synikkk said:
Yeah sorry after re reading it doesn’t sound right, I got hacked they seem to have rooted it for me remotely lol but I want to turn it into a Linux machine anyway or at least a form of or something close but I don’t know what to do it has exactly what’s on the GitHub I can’t factory reset cans clear partitions have no authority all my apps that run in the background I can’t turn off so I need some help on deciding where to go from here how does one turn a hacked fire 8 into a Linux machine or something close
Click to expand...
Click to collapse
I know for sure I bought a fire 8 10th gen and that says Android onyx 7, I have SD cards Linux machines and a pi I just don’t know what to do