hey this took me a few hours, i know a bit about androids and it gave me a hard time... thought i would share:
digix sophix 8" tablet root 840g
1: make sure you install your adb drivers, and your tablet is connected to your pc with usb debug mode on, and install unknown sources on.
2. goto your platform-tools adb dir and copy the attached zip files to that dir..
3. run command prompt navigate to your adb platform-tools dir
4. you could create a script, but i had to do it by hand, run these commands from your dos prompt:
Code:
adb shell mount -o rw,remount /system
adb push superuser.apk /system/app/superuser.apk
adb push su /system/bin/su
adb push su /system/xbin/su
adb shell chmod 7655 /system/bin/su
adb shell chmod 755 /system/bin/busybox
adb shell chmod 644 /system/app/Superuser.apk
adb shell chown root:shell /system/bin/su
adb shell chown root:shell /system/xbin/su
adb shell chown root:shell /system/app/Superuser.apk
adb reboot
i hope that works, cause thats all i should have had to do, and i ended up doing a ton of other things that i didnt need to... i had to re-install google apps, and market cause when i tried to root it i accidentially deleted em somehow....
but that should work.. if not.. you can understand the method of the script, and something can be worked by this im pretty sure!
my neighbor bought this tablet at gamestop.. i rooted it for him.... pissed me off for a while... it would be nice if someone could verify this... thanks!
enjoy!
Can you private message me..i really want to root my new sophix tablet... old methods are not working
does either of your tablets freeze all the time? I tried reflashing and everything went through but it still freezes
deathspankd said:
does either of your tablets freeze all the time? I tried reflashing and everything went through but it still freezes
Click to expand...
Click to collapse
I just got mine, and yeah it has frozen up a couple of times. Not all the time, but still annoying. I might return it if it keeps happening.
This is my first time rooting anything.
I have no idea what the first post means past step 1. Can I get some help?
SanguineNoir said:
This is my first time rooting anything.
I have no idea what the first post means past step 1. Can I get some help?
Click to expand...
Click to collapse
I've made a batch script that should help you. It automatically pushes Superuser and the SU binary to their proper places, fixes permissions, and reboots the device over ADB.
I haven't tested it on my father's 840G yet, so use it at your own risk, but theoretically everything should work.
jerbear294 said:
I've made a batch script that should help you. It automatically pushes Superuser and the SU binary to their proper places, fixes permissions, and reboots the device over ADB.
I haven't tested it on my father's 840G yet, so use it at your own risk, but theoretically everything should work.
Click to expand...
Click to collapse
Hey thank you so much.
However, i'm still confused/cautious.
So I got my ADB drivers from adbdriver but when I start the batch it says: Daemon not running, and then Daemon sucessfully started and then nothing. I left it for 15 minutes but nothing happened...what'd I do wrong?
SanguineNoir said:
Hey thank you so much.
However, i'm still confused/cautious.
So I got my ADB drivers from adbdriver but when I start the batch it says: Daemon not running, and then Daemon sucessfully started and then nothing. I left it for 15 minutes but nothing happened...what'd I do wrong?
Click to expand...
Click to collapse
It didn't recognize the device. How exactly did you install the drivers? It would have proceeded if they were correctly installed.
Go into ADB and type:
Code:
adb devices
If nothing comes up the tablet's not on, not plugged in, or the drivers are incorrectly installed.
Worst case scenario, download TeamViewer and I'll try to help you remotely.
SanguineNoir said:
Hey thank you so much.
However, i'm still confused/cautious.
So I got my ADB drivers from adbdriver but when I start the batch it says: Daemon not running, and then Daemon sucessfully started and then nothing. I left it for 15 minutes but nothing happened...what'd I do wrong?
Click to expand...
Click to collapse
I've linked another version of the batch in my first post in this thread. It's got a command that I believe is causing the issue commented out, as well as a bit more troubleshooting.
Also, there's a thread now that has a 15 second ADB driver installer. If the batch still doesn't work, download it here.
jerbear294 said:
I've linked another version of the batch in my first post in this thread. It's got a command that I believe is causing the issue commented out, as well as a bit more troubleshooting.
Also, there's a thread now that has a 15 second ADB driver installer. If the batch still doesn't work, download it here.
Click to expand...
Click to collapse
Yeah it's not showing up. I installed all the drivers correctly.
I'll grab team viewer and we'll just figure it out tomorrow, Reach me on skype at SanguineNoir
SanguineNoir said:
Yeah it's not showing up. I installed all the drivers correctly.
I'll grab team viewer and we'll just figure it out tomorrow, Reach me on skype at SanguineNoir
Click to expand...
Click to collapse
I would Skype you, but my mic's messed up right now. Once you grab TeamViewer, PM me the computer ID and password and I'll connect to find out what's wrong. Hopefully by then I figure out what's wrong with my mic.
sophix 840G TAB ROOT WORKS!!!!
Baidu root 2.3.9.......rooted mine an then I installed supersu for tablets off play store/ but there are no recoveries or custom ROMs for it
Related
Alright all,
I know there's another thread about "easier" method, but this is easiest for me. 3-Clicks after installation.
I was really tired of typing the same crap over and over after rebooting just to get my temproot back to do more testing/playing.
So I redeveloped this to be quicker/easier upon reboot. Mainly I altered the Term app to be have a scripted start-up on the 1st 3 launches.
I also updated the su/Superuser combo with ChainDD's latest stuff.
Here's how it works, after it's installed.
3ClickTempRooter said:
1) You run the terminal app once, wait a few seconds and it disappears.
2) You run the terminal again, wait for it to FC.
3) You run the terminal a final time and receive root.
Click to expand...
Click to collapse
Now on each reboot, it will be simply 3-clicks (running terminal app 3 times).
Finally ... any executable script placed in /data/local/tmp will be in the path of the new terminal mod. This makes running other scripts very easy.
Installation
Download the attached QuickTempRooter.zip and place it in a directory and unpack it.
Turn on USB debugging and install through adb ...
Here's the adb installation snippet ...
Code:
adb kill-server
adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push rage /data/local/tmp/rage
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/busybox
adb shell chmod 0755 /data/local/tmp/rage
adb shell chmod 0755 /data/local/tmp/root
adb shell 'pm uninstall com.android.term'
adb install Term.apk
Has made my life wayyy easier when playing with this phone while we wait for the real-deal!!!
Hope you enjoy!
NOTES
If you get a permission denied on the ''adb shell 'pm uninstall com.android.term' '' ... this is normal if you don't have a terminal already installed or have an alternate terminal app (using a namespace other than com.android.term.
If you have another Terminal App installed, you may want to uninstall it first, to avoid confusion.
Also, you may need to reboot after the initial installation for it to work properly!
ummmmm.....Enomther??
Did you get a G2 already?
Great to see you helping out with this
Great to see you here man! Trying this now can't wait to get themes rolling once we get permanent root!
Sent from my T-Mobile G2 using XDA App
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
burton14e7 said:
I get a permission denied response when running "adb shell 'pm uninstall com.android.term'"
Click to expand...
Click to collapse
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Thank you sir. Appreciate the goodness.
damn i wish i could hit the thanks button
Thanks man good to have you on the G2 too
Sent from my T-Mobile G2
enomther said:
If you didn't already have a terminal app installed that error is normal. Also you may need to reboot once after the initial installation for it to work properly.
~enom~
Click to expand...
Click to collapse
good to see you on this side.... i have terminal app installed rebooted but still get this denied when running adb shell 'pm uninstall com.android.term
Edit: fixed it uninstalled the Android Terminal E,ulator and just ran the setup now have root thanks
Thank You..
Enom.. (sigh)
Welcome Home..
thank u so much now i can wireless tether. easiest root ever
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
ddgarcia05 said:
Sorry, this is my first Android. I came from WM and I was pretty good with it.
I've searched XDA, Youtube, and web to ADB and SDK. I've downloaded it and it's installed. The only thing I don't get is when you said to
"Download the attached QuickTempRooter.zip and place it in a directory and unpack it."
You mean place the extracted files into the sd card correct? That's why the command is "adb push su /sdcard/su".
Click to expand...
Click to collapse
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
HamNCheese said:
No, he means on your PC. You are running adb to push files contained in the zip to your phone.
Click to expand...
Click to collapse
So they go into the tools folder? Damn. I think I've in over my head here.
Like this?
If you have better terminal, you can also add the rage and root to specific keys.
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
kevdawg said:
At this command I'm getting told "failed to copy 'su' to '/sdcard/su': Read-only file system"
adb push su /sdcard/su
Click to expand...
Click to collapse
Unplug then plug ur phone back in then try again also make sure u are in usb debug mode
Good work, Temp root in like 5 seconds
Quick question, ok I was able to get root for a few mins, then it went away I guess I have to have the terminal always open or ignore so my taskiller doesnt terminated it?
Don't use task killers. (IMHO)
But I tend to have to reboot every once in a while to keep root in tacked within terminal but all my apps seem to stay with su permissions until reboot (or sometimes 12 hours)
I'm trying the rage root method after reading up on all the stuff. I managed to get adb installed and connected, but i can't use adb actions.
I type in c\androidsdk\tools\adb shell
$ su
$ SUermission denied
even without su, if i try to type "adb push su /sdcard/su" it says adb permission denied.
I have kept my phone screen on as per another thread, but i do not get a prompt that asks for adb permissions. Am i missing an app or something? I do have debugging and screen awke both on.
I have placed the g2 root folder in the androidsdk\tools\ folder, both just the files and the entire folder just to be sure.
Obviously I'm new to adb, so If i'm doing something completely wrong just let me know.
as long as you're not rooted (temp or perma) you can't use "su" in adb-commands... If you tell a little more about what you're trying to push, then I can help some more
Im just trying to root the phone with rage since visionary seems unreliable.
Im trying to adb push the su/ sdcard/su as per the first line of instruction in the rage temp root guide
hehe... I used the visionary root, and it have worked good for me btw, I think you should've posted in the rage-thread instead of opening a new topic, but now it's already opened so here it goes
firstly... are you sure you're in the right folder, and have the folder "su" in there?
If so, don't go into "adb shell"... use the lines exactly as stated in the OP. adb inside an adb shell won't give the results you want... Post back if it doesn't work
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Ok, my adb stuff is in c:\tools .. so when I first open command prompt, I have to type this:
cd c:\tools
That puts me into the correct folder. If yours is in C, then you'd probably have to do this:
cd c:\androidsdk\tools
Then type:
adb devices
It should at least give you SOME sort of output, either with your device number (if it's connected, and adb is working properly), or just say devices, with no numbers (incorrectly)
dwang93 said:
I don't think Im using adb right then, how do I just type in "adb push ...?" If I do that, it just says that the command is not recognized internally or externally.
For example,
Adb push su/ sdcard/su
gives me that error.
I've tried to set a path directly to adb, but that didn't work, so I was manually going
AndroidSKD\tools\ Adb push su/ sdcard/su but that also didnt work.
I don't have the $ prompt without shell, is that wrong?
I'm pretty sure Im in the right folder, as androidsdk\tools\adb gives me the adb directory, just nothing else works. What exactly does SU folder mean? I have the su file in the tools folder, dont know about the su folder.
Click to expand...
Click to collapse
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
FYI you will not see the $ symbol. that just indicated the next line you have to enter in commnad prompt. Each time you see $ just mean you type that line then press enter. Wait to see a result of transfer from prompt then enter next line and so on.
rsxtypes72 said:
You, apparently, need to read some more.
Do it exactly as written here
http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2
Click to expand...
Click to collapse
This!! I'll be kind though.
Make your life easy. Unzip the contents of g2TempRoot, to your tools folder, in sdk. So, unzip the g2temproot to your desktop. Go into that folder. Copy all, and move them to c:\androidsdk\tools. Now, once that's done, go into command prompt. cd c:\androidsdk\tools. Then, do as follows, as per that link
$ adb push su /sdcard/su
$ adb push Superuser.apk /sdcard/Superuser.apk
$ adb push rage /data/local/tmp/rage
$ adb push busybox /data/local/tmp/busybox
$ adb push root /data/local/tmp/root
$ adb shell chmod 0755 /data/local/tmp/*
(Sorry I couldn't be of more help, as I used VisionaryR12 and it worked fine for me.)
One more word of advise...
I would recommend you try temp root first.
Become used to using adb then try to get full root.
When you use temp root everything you do is temporary only.
Rebooting will reset everything back to stock so its good practice.
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
any tips on going onto the perm root?
Click to expand...
Click to collapse
Read .. research .. double check .. triple check .. and right before you do it .. check again. As you're doing it, go over every letter, space, and character to make sure it's as it should be.
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Daughain said:
On the subject of adb, I have it installed, but when I run adb devices to find my phone, I get "???????????? no permissions". What am I doing wrong here?
Click to expand...
Click to collapse
Upload a screen shot of your command window
with the error
dwang93 said:
thanks for the help guys, but i figured it out. I just wasn't in the right directories from the get go.
Edit: Just finished the perm root! And it didn't brick.
Click to expand...
Click to collapse
dude..I think I am doing something like you...could you please post what you did....I think is an issue of directories..but I'm not that familiar with adb and i have not been able to figure this out.....
Thanks!!!
For 6.3 see http://forum.xda-developers.com/showthread.php?p=24129239
Please do not reupload/redistribute BurritoRoot2/BurritoRoot3, instead link directly to my hosting. I own the server, it will no go away any time soon. This allows me to update it if a bug is found.
BurritoRoot3 is not opensource, it is free, but it is not free to distribute. Please do not redistribute it.
Tested on 6.2, 6.2.1 and 6.2.2
Disclaimer:
BurritoRoot3 may void your warranty. While it was tested, over and over, a chance of data loss or hardware damage always exists. If something bad happens due to your use of BurritoRoot3, well it is your fault not our's, don't blame any of us.
Wine/Coffee/Device Funding:
To donate to jcase of TeamAndIRC for BurritoRoot go here:
http://forum.xda-developers.com/donatetome.php?u=2376614
To donate to pokey900 for the FireFireFire Bootloader go here:
http://forum.xda-developers.com/donatetome.php?u=466725
Download:
http://download.cunninglogic.com/BurritoRoot3.apk
BurritoRoot3 is an all in one package, to root and install the custom bootlaoder, FireFireFire, onto the KindleFire.
Instructions are pretty plain and simple, however you will have to get adb working on your own (if you have written, or know of adb guides for the Kindle Fire please PM me to list them here).
ADB GUIDES
MAC GUIDE: http://forum.xda-developers.com/showthread.php?t=1443071
WINDOWS GUIDE: http://www.jayceooi.com/2011/12/13/how-to-install-kindle-fire-adb-usb-driver/
LINUX GUIDE: http://forum.xda-developers.com/showthread.php?p=22067293
What it does:
Gains root, installs superuser, installs su and installs the FireFireFire bootloader.
At this time, we do not have permission to distribute any recovery, once one is available for our use, we will add auto flashing of recovery.
How to use:
adb shell chmod 777 /data/local/tmp
Run app, follow directions given by the app.
Usage example :
[email protected]:~$ adb shell chmod 777 /data/local/tmp <---- This one is important, it may not create BurritoRoot3.bin if this is not done
[email protected]:~$ adb install BurritoRoot3.apk
4897 KB/s (1151520 bytes in 0.229s)
pkg: /data/local/tmp/BurritoRoot3.apk
Success
<go open the app now>
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --root
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
Gaining root...
Installing Superuser APP, if it erros as already exists, please ignore the error.
pkg: /data/data/net.andirc.burritoroot3/bin/Superuser.apk
Success
Restarting adbD as root...
Please run adb shell /data/local/tmp/BurritoRoot3.bin --install
[email protected]:~$ adb shell /data/local/tmp/BurritoRoot3.bin --install
BurritoRoot3 Installer 0.1 by TeamAndIRC
#########################################################################
Usage: BurritoRoot3.bin <parameter>
--root - Restart adbD as root, and install Superuser app
--install - Install su
#########################################################################
BurritoRoot3 kroot 0.1 - TeamAndIRC
Remounting /system...
Cleaning up, ignore any errors
rm failed for /system/xbin/su, No such file or directory
rm failed for /system/bin/su, No such file or directory
Installing su...
Remounting /system..
Root installed
Starting: Intent { act=android.intent.action.MAIN cmp=net.andirc.burritoroot3/.FireFireFire }
Please check your Kindle's screen
[email protected]:~$
If you already have root, and want to safely install the FireFireFire bootloader, you can use the app, just install, open/close the app then
adb shell am start -a android.intent.action.MAIN -n net.andirc.burritoroot3/net.andirc.burritoroot3.FireFireFire
To install the CWR recovery by DoomLord after gaining root:
Download it, and push it to your Kindle
adb push <filename> /data/local/recovery.img
adb shell dd if=/data/local/recovery.img of=/dev/block/platform/mmci-omap-hs.1/by-name/recovery
Would you support the archos G9 devices
jutley said:
Would you support the archos G9 devices
Click to expand...
Click to collapse
Doesn't archos sign or lock system?
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
---------- Post added at 10:06 AM ---------- Previous post was at 09:55 AM ----------
CharlieBoy808 said:
I love you Devs so much. I just got a Kindle today, but as I watched the video your Kindle shows up under Other Devices as if it didn't install the device driver. Mine is installed under portable devices. Can I just update that one or is there a debug mode for the Kindle that I'm missing?
Thanks for all you do!
Click to expand...
Click to collapse
LoL Nevermind I think I know why mine isn't there... I've already installed ADB from before. I shall continue on and see what happens :-D
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
AproSamurai said:
I'm currently running Ubuntu 11.10(Without access to a windows computer to do so.) And after following the steps within the BurritoRoot I get error: insufficient permissions for device when entering adb root. I've rebooted my kindle and laptop as well as changed usb ports.
I've set it up so that it's acknowledged within /.android. Am I perhaps missing something sdk wise? The usb configuration install for extras within it says Linux isn't compatible. But any insight into this would be appreciated I'm not new to Android or adb for that matter. Things seem to be done differently for the Kindle is all.
Thanks guys.
Click to expand...
Click to collapse
adb kill-server
sudo -s
adb devices
should see it now
Quit following me around jcase
Unheard said:
Quit following me around jcase
Click to expand...
Click to collapse
Hah Where you been?
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
notsointeresting said:
I can not get ADB to recognize the device for the life of me.
I know I have the drivers installed the Fire is recognized as "android composite adb interface" under the Android Phone category in Device manager. But I can not get adb to see it.
"Adb kill-server"
"adb devices"
and it shows no devices attached. Ive done a factory reset on the tablet just to see (knowing it wouldn't make a difference)
Im running Windows XP
if someone could help me out.
Click to expand...
Click to collapse
I'm sure its related to windows' drivers but I have no clue. Sorry
jcase said:
adb kill-server
sudo -s
adb devices
should see it now
Click to expand...
Click to collapse
Thanks man, I knew I must have failed to do something. It's much appreciated.
Dis this last night and it worked fine. Thanks!
I did have a few minor stumbles though. It seems the newest version of the software changed the name of the superuser app but the guide still uses the old name in the install command. Once I realized this I just changed the name in the command and it went right in.
Also for some reason I couldn't select the text in the adb box on the web page so I had to enter the commands by hand. No big deal but I would have felt more secure if the commands were in simple text so I could have copy/paste them in.
Like I said though everything worked and I have the market installed now. Thanks for the hard work!
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
My sd card is showing up as unmounted and not sure how to remount it. I sent adb remount and it didn't work. Any help would be appreciated.
Fee454 said:
I'm having some trouble with mine...I am trying to follow the video instructions to the link but it shows downloading a .android folder and extracting it to my user name on desktop but there is no such link. I have downloaded SDK and installed google usb drivers as well. I have 6.2.1 firmware and downloaded kindleroot_androidpolice.apk and placed on my kindle and I also downloaded superuser-2. I am not able to install the driver to the fire either. I go to my computer, manage, device manager, kindle, update driver software, browse my computer, etc. I have no INF file to choose under my .android folder.
Any help would be appreciated
Click to expand...
Click to collapse
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
[/COLOR]
b63 said:
would suggest to use this:
http://forum.xda-developers.com/showthread.php?t=1399889
Click to expand...
Click to collapse
This tool will attempt to install the correct Drivers for the Kindle Fire.
It will also perform the setup required for adb_usb.ini in .android for you.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
The system cannot find the path specified.
Press any key to continue . . .
I tried to install the drivers for the kindle but i receive the above message
---------- Post added at 09:56 PM ---------- Previous post was at 09:07 PM ----------
My issue is it cannot find my device...where can I find the kindleADB.zip I keep hearing about?
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
You should get the same files from the android Sdi. Good luck.
Jcase, I know that you said the unroot button did not work, but is there a method of unrooting?
b63 said:
did you do install_drivers.bat first ?
take a look:
http://forum.xda-developers.com/showpost.php?p=20698002&postcount=283
that should correct the path issue
Click to expand...
Click to collapse
Yes thank you. Moving it to the same as the run.bat seemed to have worked as it shows online now when running the Kindle Fire Utility. I switched it to fast boot but now seems to have been frozen at the kindle fire logo for quite some time now. I heard you have to switch to fastbook to install TWRP first before rooting?
I am not sure if I should attempt to somehow reboot this as it seems to be stuck at the boot up screen
wrong - switch back to normal boot and use the utility
I have tried every version of KFU from 0.9.5 on up, and have reinstalled the KFU drivers multiple times. FFF & TWRP install fine, but when KFU gets to the part where it removes the root checker I get an error:
Attempt to remove root checker
mv: can't rename 'system/bin/check_rooted': No such file or directory
Please wait...
The Kindle then continues to boot up as normal. It then attempts to install SU:
Installing Superuser.apk
Error: Cound not access the Package Manager. Is the system running?
KFU then states that root has been installed, when in fact it has not. I know that I could simply use TWRP to flash CM 10.1 which would have root, but this Kindle is my wife's (I already have CM on mine). I need root to be able to use Titanium Backup and save all of her app data. Any help resolving this would be appreciated!
diskoman21 said:
I have tried every version of KFU from 0.9.5 on up, and have reinstalled the KFU drivers multiple times. FFF & TWRP install fine, but when KFU gets to the part where it removes the root checker I get an error:
Attempt to remove root checker
mv: can't rename 'system/bin/check_rooted': No such file or directory
Click to expand...
Click to collapse
This is normal. Nothing to really worry about.
Installing Superuser.apk
Error: Cound not access the Package Manager. Is the system running?
KFU then states that root has been installed, when in fact it has not. I know that I could simply use TWRP to flash CM 10.1 which would have root, but this Kindle is my wife's (I already have CM on mine). I need root to be able to use Titanium Backup and save all of her app data. Any help resolving this would be appreciated!
Click to expand...
Click to collapse
I've run into this problem before. This is from attempting to install the .apk before the device is booted far enough for the package manager to be available. This can be easily fixed by pausing the script for an amount of time to ensure the package manager is available before continuing with the rest of the script. You should probably contact the developer about it.
You might be able to just install Superuser.apk using the following command:
Code:
adb shell pm install -r /system/app/Superuser.apk
THANK YOU!!!
soupmagnet said:
This is normal. Nothing to really worry about.
I've run into this problem before. This is from attempting to install the .apk before the device is booted far enough for the package manager to be available. This can be easily fixed by pausing the script for an amount of time to ensure the package manager is available before continuing with the rest of the script. You should probably contact the developer about it.
You might be able to just install Superuser.apk using the following command:
Code:
adb shell pm install -r /system/app/Superuser.apk
Click to expand...
Click to collapse
Your response made all the sense in the world (duh moment for me, lol)! I took a look at the batch file for KFU, and located the line of code where it calls the sleep function to wait for the Kindle to boot up:
::Wait for Android to finish booting, and install Superuser.apk.
tools\adb wait-for-device
tools\sleep 20
echo. Installing Superuser.apk
tools\adb install -r files\Superuser.apk 2> nul
I changed the 2nd line of the section to call sleep for 60 seconds instead of just 20. Voila! That did the trick. I have sent a message to the developer as well, so that he can make this simple fix. Thanks again for taking the time to help get me on the right path! :highfive:
diskoman21 said:
Your response made all the sense in the world (duh moment for me, lol)! I took a look at the batch file for KFU, and located the line of code where it calls the sleep function to wait for the Kindle to boot up:
::Wait for Android to finish booting, and install Superuser.apk.
tools\adb wait-for-device
tools\sleep 20
echo. Installing Superuser.apk
tools\adb install -r files\Superuser.apk 2> nul
I changed the 2nd line of the section to call sleep for 60 seconds instead of just 20. Voila! That did the trick. I have sent a message to the developer as well, so that he can make this simple fix. Thanks again for taking the time to help get me on the right path! :highfive:
Click to expand...
Click to collapse
Yeah, 60 seconds may be a bit much LOL, but I'm glad it worked out for you :good:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **** This method is designed for Amazon fire phone. Do not use it on other devices unless you are familiar with Android file system and are able to apply proper modifications. **
This has been tested with the unlocked US version running 4.6.1.
This procedure installs superSU root binaries and busybox on your system.
Requirements
Make sure your PC can communicate with your fire phone via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the permission when the phone prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your phone, open the Kinguser app, open settings (the wheel at the top right corner of the screen), Root authorization setting, and Remove Root permission. The app will self-uninstall.
6- Uninstall the other two Kingroot programs that are still on your phone (KingRoot and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
rm /system/bin/shipclean
rm /system/bin/start-ssh
busybox chattr -ia /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install_recovery.sh
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
rm -rf /data/data-lib/com.kingroot.RushRoot
rm -rf /data/data-lib/com.kingroot.kinguser
rm -rf /data/data-lib/king
Again, leave the adb terminal window running and go to your phone.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the phone. After about 5 minutes your root is ready.
Hint: It is a good idea to disable Amazon device client platform, DCP platform contracts, and two apps called System Updates in Amazon settings. They are responsible for regular updates, constant chatter with Amazon servers, and possible patching of your root exploit. Also disable Kinesis service which is responsible for major battery drain and heating. You will find it under settings, display, configure motion and gesture settings. Disable all.
Troubleshooting
1- Most of the problems that I noticed people have encountered is due to not reading the instructions fully. So make sure you read the OP word by word.
2- If you miss a step or mess up something go back to installing Kingroot and start over from the beginning.
3- If instant video or some other Amazon app doesn't work it is because you should run them at least once prior to rooting the phone.
4- Finally, I noticed that with an AT&T sim card in the phone Kingroot fails (why am I not surprised?) Either a reboot occurs in the middle of rooting or it completes the cycle without accomplishing root. If that occurs, my best advice is to change your phone company. If that fails, you may need to factory reset your phone or even install the firmware from scratch and try again without the sim card.
Okay. Working. I tried it 2 Times because i get in troubles with the SuperSu App.
After First Time i Cant open it anymore after adb shell.
Second Time i installed SuperSu, but after adbshell the app was gone (!?) - but i installed it again with adb shell before reboot. Now SuperSu is Working.
And now tell me how to change the FireOS to a Android Status Bar with Notifications, and youre my Hero ;D
najoor said:
** DISCLAIMER: I AM NOT A DEVELOPER. I DO THIS AS A HOBBY AND SHARE MY FINDINGS IN CASE SOMEONE ELSE FINDS THEM USEFUL. **
** THIS WORKED ON MY DEVICE BUT IT MAY NOT WORK ON YOURS. APPLY AT YOUR OWN RISK **
This has been tested with the unlocked US version running 4.6.1.
Requirements
Make sure your PC can communicate with your fire phone via adb.
The success of this method depends on following the procedure very carefully. So read the instructions and make sure you understand every step before you try it.
Procedure
1- Install and run Kingroot 4.0. You can google and download it or you can use the one in the attached zip file. When Kingroot runs it is all in Chinese, but basically you need to be connected to the internet for it to work. It will do its thing and show progress up to 100% after which you can exit the program. Now your phone is rooted. The following steps replaces the Kinguser with SuperSU.
2- Unzip the attached file in your adb directory and then open an adb terminal and make sure the PC can see your phone (you can check that by typing adb devices). Then type the following:
Code:
adb push su /data/local/tmp
adb push busybox /data/local/tmp
adb shell
3- In the shell that you get type the following and make sure you give the permission when the phone prompts you:
Code:
su
4- Continue by typing the following commands:
Code:
mount -o remount,rw /system
cat /data/local/tmp/su >/system/xbin/daemonsu && chmod 0755 /system/xbin/daemonsu
cat /data/local/tmp/busybox >/system/xbin/busybox && chmod 0755 /system/xbin/busybox
daemonsu -d &
The key is to keep this session running while you continue with the rest, so be careful with typos and monitor this window for any errors.
5- At this point, leave the adb terminal window running and go to your phone, open the Kinguser app, open settings, Root authorization setting, and Remove Root permission .
6- Uninstall the other two Kingroot programs that are still on your phone (KingRoot and the other one with the blue icon and Chinese text under it).
7- Back to the adb terminal, and type the following:
Code:
cat /data/local/tmp/su >/system/xbin/su && chmod 0755 /system/xbin/su
busybox chattr -ia /system/xbin/ku.sud
busybox chattr -ia /system/xbin/supolicy
rm /system/xbin/ku.sud
rm /system/xbin/supolicy
rm /system/bin/rt.sh
rm /system/bin/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh
rm /system/etc/install-recovery.sh
busybox chattr -ia /system/etc/install-recovery.sh-ku.bak
rm /system/etc/install-recovery.sh-ku.bak
rm /system/kroot_*
rm /sdcard/kr-stock-conf
rm -rf /sdcard/Kingroot
rm /system/usr/icu/icusuflag.conf
busybox chattr -ia /system/usr/iku/isu
rm -rf /system/usr/iku
Again, leave the adb terminal window running and go to your phone.
8- Install superSU (from the attached file) on your phone, run it, and let it update the SU binary.
9- Reboot the phone. After about 5 minutes your root is ready.
Hint: It is a good idea to disable Amazon device client platform, DCP platform contracts, and two apps called System Updates in Amazon settings.
Click to expand...
Click to collapse
Not sure what I'm doing wrong but everything works till I get to rm stage of step 7. Im getting 255 read only file system error. Any ideas what I did wrong. since it didnt work to I have reinstall Kingroot and start over or do I start over from the adb shell part?
Viperise152 said:
Not sure what I'm doing wrong but everything works till I get to rm stage of step 7. Im getting 255 read only file system error. Any ideas what I did wrong. since it didnt work to I have reinstall Kingroot and start over or do I start over from the adb shell part?
Click to expand...
Click to collapse
Do you close the adb window between steps 4 and 7? Step 7 should be continued in the window that you left open in step 4.
Do you get any error message after you type each command in part 4?
To redo the process you should install the Kingroot again and stay overt from the beginning.
I did not get any errors for part 4 just when I get to the first rm command in part 7, I'm getting (rm failed for /system/xbin/ku.sud, Read-only file system). Is that normal?
FIXED!!!
Ok i was not following this step properly "open the Kinguser app, open settings, Root authorization setting, and Remove Root permission ." I was not doing through that Root authorization setting which was a few slots down.
Viperise152 said:
Not sure what I'm doing wrong but everything works till I get to rm stage of step 7. Im getting 255 read only file system error. Any ideas what I did wrong. since it didnt work to I have reinstall Kingroot and start over or do I start over from the adb shell part?
Click to expand...
Click to collapse
Please copy and paste the entire content of the adb terminal up to the point that you get the error message and send it to me via pm so I can debug it.
najoor said:
Please copy and paste the entire content of the adb terminal up to the point that you get the error message and send it to me via pm so I can debug it.
Click to expand...
Click to collapse
I still had this page open while I was giving it another go. I figured out what i was doing wrong. The " open the Kinguser app,open settings, Root authorization setting, and remove root permission." part I was just opening Kinguser settings and hitting the big center button turning it off. Did'nt realize i had to go down a few slots to the Root Authorization Setting then hit the Remove Root Permission. After i did it right Kinguser disappeared unistalled the other 2 apps. Everything after that work fine then. Thanks for trying to help me out. Maybe my confusion will help others.
Viperise152 said:
I still had this page open while I was giving it another go. I figured out what i was doing wrong. The " open the Kinguser app,open settings, Root authorization setting, and remove root permission." part I was just opening Kinguser settings and hitting the big center button turning it off. Did'nt realize i had to go down a few slots to the Root Authorization Setting then hit the Remove Root Permission. After i did it right Kinguser disappeared unistalled the other 2 apps. Everything after that work fine then. Thanks for trying to help me out. Maybe my confusion will help others.
Click to expand...
Click to collapse
Thanks for updating with what you were doing wrong. I was having the same issue. Cheers!
funkadelik said:
Thanks for updating with what you were doing wrong. I was having the same issue. Cheers!
Click to expand...
Click to collapse
And me too I should have read your post instead of bugging najoor who has been a great help to resolve my SuperSU
installation
Great thread :good::good:
thx for the guide.
can you explain why it is better to have SuperSu. What is wrong with kingsu?
planning to do this soon, cheers for the guide
so what is safe to remove out of the stock apps
veti said:
thx for the guide.
can you explain why it is better to have SuperSu. What is wrong with kingsu?
Click to expand...
Click to collapse
King user might even be a better SU than superSU, who knows? The problem is that we don't know kinguser. We don't know who wrote it, we don't know what kind of information it gathers, we don't know if it puts a backdoor exploit in your OS, etc. Super SU is a tool that we have used for years. We know exactly what supersu does and who wrote it. We can even communicate with him on xda. Chainfire, the author of SuperSU even has a weblog that he often uses to talk about the intricacies of designing a tool like superSU. There is almost nothing unknown or suspicious about superSU.
On the contrary kingroot/kinguser seems to be intrusive and sneaky. The first thing it does after rooting your phone is to install some random app on it that has nothing to do with rooting and at best I can describe it as bloat. It saves files and folders all over your phone for no apparent reason. Then, it does everything it can to prevent you from removing it. In effect, the only straightforward way to remove it is to give up root, and even then it very suspiciously leaves some executable files behind that God knows if they are sleeper cells or what. To devise the procedure in the OP I had to go through an extensive search to find every little carp that king user has planted into the system and truth be told I will not be surprised if I discover more hidden gems left behind.
The corrected op guide worked great. I had to tap a blue rectangle at two different times to get kingroot to finish (get to a screen that had 100% on it), but other than that, everything worked.
najoor said:
King user might even be a better SU than superSU, who knows? The problem is that we don't know kinguser. We don't know who wrote it, we don't know what kind of information it gathers, we don't know if it puts a backdoor exploit in your OS, etc. Super SU is a tool that we have used for years. We know exactly what supersu does and who wrote it. We can even communicate with him on xda. Chainfire, the author of SuperSU even has a weblog that he often uses to talk about the intricacies of designing a tool like superSU. There is almost nothing unknown or suspicious about superSU.
On the contrary kingroot/kinguser seems to be intrusive and sneaky. The first thing it does after rooting your phone is to install some random app on it that has nothing to do with rooting and at best I can describe it as bloat. It saves files and folders all over your phone for no apparent reason. Then, it does everything it can to prevent you from removing it. In effect, the only straightforward way to remove it is to give up root, and even then it very suspiciously leaves some executable files behind that God knows if they are sleeper cells or what. To devise the procedure in the OP I had to go through an extensive search to find every little carp that king user has planted into the system and truth be told I will not be surprised if I discover more hidden gems left behind.
Click to expand...
Click to collapse
Thank you _so_ much for your effort. I was doing some research too in advance prior to installing kingroot, but didn't get near as much useful information. Sniffing the network connection for any suspicious behaviour via wireshark and my router wasn't successful at all, as they use https.
I came up with the idea that they could have patched some of the system-apps to load an payload even after you tried to "delete everything"(tm). I am currently checking the MD5 and SHA-1 checksum of a identical, second Firephone without root.
---------- Post added at 09:09 PM ---------- Previous post was at 09:05 PM ----------
Also the Mods should pin your post. I totally agree that KingRoot uses intrusive behaviour - as it seems mostly for statistics, but anyway - and should be replaced with the method described in the OP.
EDIT: The MD5 checksum of an unrooted firephone is identical. The System apps might not have been replaced or touched at all. I didn't got a easy chance to check all apps with the SHA-1 checksum though.
Followed the directions and got the root with 0 issues
Just saw this article saying root is now achievable w/ SuperSU via Towelroot: http://dottech.org/180812/how-to-root-amazon-fire-phone-on-android-4-4-kitkat-guide/
Can anyone verify?
amf100 said:
Just saw this article saying root is now achievable w/ SuperSU via Towelroot: http://dottech.org/180812/how-to-root-amazon-fire-phone-on-android-4-4-kitkat-guide/
Can anyone verify?
Click to expand...
Click to collapse
No, it doesn't work. When you run it, the towelroot app pops up a message saying the phone is currently not supported.
Hmph! That's too bad. I wasn't with my fire phone to check for myself. The internet is so weird lol. Why make a whole page with instructions for nothing? Ugh lol
rm /system/bin/rt.sh
Click to expand...
Click to collapse
This part is not working for me. Can't seem to remove it with root explorer either. Any tips?
Im on 4.6.1 with SuperSu. If im Sideload 4.6.1 again and do an Factory Reset. Is root gone? Because Amazon send me New One Because Hardware issues