How can I tell if I'm rooted? - EVO 4G Q&A, Help & Troubleshooting

I followed this thread:
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17766-how-full-root-evo-4g-mac-3.html
I went through all the steps and I'm exhausted since I spent like 2 hours doing this rooting process.
Now someone PLEASE tell me before I gouge my eyes out and skull **** myself if I achieved root.
Am I supposed to see a new icon indicating that I rooted? I don't see anything that says Super Agent but I followed those instructions to a T.
Right now I'm restoring my apps back on and I'm going to be very pissed if I'm thinking what I'm thinking. By the way I searched Google and someone on a forum said that if you cab download wireless tether from market then you're rooted. I was able to download it but does that really mean I am or did that just apply to that particular android phone?

open up a terminal or command line window.
run your adb program, with the following command line
mac
./adb shell
windows
adb shell
(or however you invoked it during the rooting process)
if your prompt looks like
Code:
#
you win.
else, you lose.
edit:
you'll only see superuser permissions if you install the app, not sure where to get it from as when i flash new roms they're preinstalled.
i suggest going on to flash a recovery image, so you can flash other ROMS with ease.

Thankfully I saw the # sign so that means I'm good. How do I go about starting to remove the apps I don't need anymore?
I have to research recovery roms because I don't have the patience to do it today.

just go flash a new ROM that has all the junk removed and save yourself the trouble.
i here there are programs that will do this for you as well, btu i dont know em off hand

gqstatus0685 said:
Thankfully I saw the # sign so that means I'm good. How do I go about starting to remove the apps I don't need anymore?
I have to research recovery roms because I don't have the patience to do it today.
Click to expand...
Click to collapse
1. Reboot in to recovery, so that /system will be writeable.
2. Launch an adb shell and navigate to /system/app:
Code:
./adb shell
# cd /system/app
3. Delete the programs you don't want by using the rm (remove) command:
Code:
# rm Flickr.apk
4. Reboot the device.
If you want to err on the side of caution, you can move the programs to your SD card, or your computer, so that you can restore them if needed:
Move to SD card:
Code:
./adb shell
# mkdir /sdcard/apkbackup
# mv /system/app/Flickr.apk /sdcard/apkbackup
Restore from SD card:
Code:
./adb shell
# mv /sdcrd/apkbackup/Flickr.apk /System/app
Backup to your computer:
Code:
./adb pull /system/app/Flickr.apk ~/Desktop/Flickr.apk
./adb shell
# rm /system/app/Flickr.apk
Restore from your computer:
Code:
./adb push ~/Desktop/Flickr.apk /system/app/Flickr.apk
Have fun!
cent

Related

Search key doesn't work.

I don't know if it has anything to do with it, but after I installed the new google voice search, my search key didn't work any more. When I touch the search key now, it doesn't do anything. Any idea?
Thanx in advance.
Sent from my PC36100 using XDA App
Same boat.
Cm6.
Any ideas people?
Add me to this list same here
The voice search isn't to blame it's the new Google search widget that you need to blame.
Sent from my PC36100 using Tapatalk
you got to hold it, hold it for like 3-4 seconds, it will work, at least on fresh does!!
What ive been looking for..
Sounds like a great fix to that annoying thing. I hate that it comes on all the time. Think ill install it just for the break rofl....................
jonathaflores said:
you got to hold it, hold it for like 3-4 seconds, it will work, at least on fresh does!!
Click to expand...
Click to collapse
That asks for the long press one
I'm talking about the single press search
Here's how to fix (from your Terminal/Command Prompt, where ADB is):
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell rm /system/app/GoogleQuickSearchBox.apk
adb shell rm /system/app/VoiceSearch.apk
adb shell rm -r /data/data/com.google.android.voicesearch
adb shell pm uninstall com.google.android.voicesearch
adb reboot
Now go install the Google Search and Voice Search from the Android Market. Problem solved.
NOTE: You have to have full root. That means # in your shell, and NAND unlock. If you don't, you are SOL.
drmacinyasha said:
Here's how to fix (from your Terminal/Command Prompt, where ADB is):
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell rm /system/app/GoogleQuickSearchBox.apk
adb shell rm /system/app/VoiceSearch.apk
adb shell rm -r /data/data/com.google.android.voicesearch
adb shell pm uninstall com.google.android.voicesearch
adb reboot
Now go install the Google Search and Voice Search from the Android Market. Problem solved.
NOTE: You have to have full root. That means # in your shell, and NAND unlock. If you don't, you are SOL.
Click to expand...
Click to collapse
I am fully rooted anyway to do this via titanium backul? Is the main goal here to uninstall the old apps?
Jsimon9633 said:
I am fully rooted anyway to do this via titanium backul? Is the main goal here to uninstall the old apps?
Click to expand...
Click to collapse
No way that I found. His way is flawless and just requires typing what you see.
the adb commands worked awesome...I still have a slight lag with the "hard" key search button...still requires a long press.
Thanks!!
Quick note: If you do all of that, and when short-pressing the Search key, you don't get the Google Search (and assuming you've installed Google Search from the Market), use these commands:
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell cp /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/GoogleQuickSearchBox.apk
adb reboot
This thread oughtta be stickied. I've already quoted my post in here three times.
drmacinyasha said:
Here's how to fix (from your Terminal/Command Prompt, where ADB is):
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell rm /system/app/GoogleQuickSearchBox.apk
adb shell rm /system/app/VoiceSearch.apk
adb shell rm -r /data/data/com.google.android.voicesearch
adb shell pm uninstall com.google.android.voicesearch
adb reboot
Now go install the Google Search and Voice Search from the Android Market. Problem solved.
NOTE: You have to have full root. That means # in your shell, and NAND unlock. If you don't, you are SOL.
Click to expand...
Click to collapse
I've already uinstalled/rebooted/installed both the voice search and the google search. Do i still proceed with the above steps? And if so, can I type these commands as I see them into the Terminal Emulator on the phone itself?
The commands are meant to be done via ADB (a command prompt/shell on your computer).
If you already have everything working (including the search key) then there's no need for you to do this.
drmacinyasha said:
Quick note: If you do all of that, and when short-pressing the Search key, you don't get the Google Search (and assuming you've installed Google Search from the Market), use these commands:
Code:
adb shell mount -o remount,rw /dev/block/mtdblock4 /system
adb shell cp /data/app/com.google.android.googlequicksearchbox-1.apk /system/app/GoogleQuickSearchBox.apk
adb reboot
This thread oughtta be stickied. I've already quoted my post in here three times.
Click to expand...
Click to collapse
You are a lifesaver. Was freaking out when my search button broke. This fixed it. Thank you!
Sent from my PC36100 using XDA App
drmacinyasha said:
The commands are meant to be done via ADB (a command prompt/shell on your computer).
If you already have everything working (including the search key) then there's no need for you to do this.
Click to expand...
Click to collapse
I've just uinstalled/rebooted/installed both the voice search and google search. Voice search works fine, but as I said previously, the google search button is broken.
I want to use your instructions but I've never used adb on my computer before. Can you help me out? I've always avoided using it, but maybe it's time I learn.
tranquilchaos said:
I've just uinstalled/rebooted/installed both the voice search and google search. Voice search works fine, but as I said previously, the google search button is broken.
I want to use your instructions but I've never used adb on my computer before. Can you help me out? I've always avoided using it, but maybe it's time I learn.
Click to expand...
Click to collapse
there's a thread in development on how to use adb.
seriously, once you get the least bit familiar with it, you won't want to use anything else...
i do everything from adb. it's just easier. trust me. i've tried all the other methods, and they're a pain in comparison
timothydonohue said:
there's a thread in development on how to use adb.
seriously, once you get the least bit familiar with it, you won't want to use anything else...
i do everything from adb. it's just easier. trust me. i've tried all the other methods, and they're a pain in comparison
Click to expand...
Click to collapse
Wowsers, so I found the following post: http://forum.xda-developers.com/showthread.php?t=502010 (adb for dummies) but I'm lost.
It seems to be designed for Windows users....So far I have:
downloaded the newest SDK package, Eclipse and installed the ADT Plugin. Now what? I'm so confused...any help would be great!
tranquilchaos said:
Wowsers, so I found the following post: http://forum.xda-developers.com/showthread.php?t=502010 (adb for dummies) but I'm lost.
It seems to be designed for Windows users....So far I have:
downloaded the newest SDK package, Eclipse and installed the ADT Plugin. Now what? I'm so confused...any help would be great!
Click to expand...
Click to collapse
You don't need Eclipse or anything like that.
Just go to Start>Run, type in "cmd" (no quotes) and then type the command:
cd *location of where you saved the Android SDK*
cd tools
So if you copied the Android SDK to "C:\Program Files (x86)\Android SDK", you would type:
cd "C:\Program files (x86)\Android SDK\"
cd tools
Now just type in the commands, starting with "adb " such as "adb reboot" or "adb shell" and so on.
EDIT: Since there was an update for the Nexus One version of CM6, there's now a new GApps ZIP which contains the new search, Voice Search, etc. Just copy it to your SD card, reboot into recovery, and flash it:
http://mirror.kanged.net/gapps/gapps-hdpi-20100814-signed.zip

[Q] youtube app porting help!!! please!!!

can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
betterment66 said:
can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
Click to expand...
Click to collapse
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
gremlyn1 said:
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
Click to expand...
Click to collapse
ok i get to remount rw but the when i type in the nect code it says
mkdir falied for /sdcard/backup read-only filesystem
I install it using terminal emulator.
All I do is type
Su
#rm /system/app/YouTube.apk
#cp /sdcard/DirectoryWithTheYoutubeApp/YouTube.apk /
system/app
Or after you rm, just use the "My Files" app and go on your sdcard and click YouTube.apk and it'll install and work fine. But remember to sign out of youtube before you close it by going to your page and clicking sign out or else it'll keep force closing after you start it up.
I hope I helped...
Sent from my SPH-D700 using XDA App
you guys are gonna freaking kill me. ALL THE TROUBLE I WAS HAVING WAS BECAUSE I HAD MY SDCARD MOUNTED THE WHOLE TIME I WAS TRYING TO DO THIS THE MINUTE I TRIED IT WITHOUT IT BEING MOUNTED IT WORKED...IM SO DUMB!!!!! LOL BUT THANKS FOR THE HELP ALL OF U!!!!!! U GUYS ROCK!!!! N SO DOES THE NEW UTUBE APP .....BTW I UNDERSTAND UR NOT SUPPOSED TO SIGN IN TO IT RIGHT???
I just uninstalled the original, put the modded youtube.apk in the SDX backup folder and installed (restored) it with SDX stock app remover. Simple, fast and no typing required.
Glad you got it worked out though.
me 2!!! this app rocks
Glad it's working! Having the SD card mounted while trying to adb is a common mistake and always a good first troubleshooting check.

ADB

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!!!

[Q] G2 Rooting Issues

Hello All,
So I decided to try rooting after doing all this research. I chose to use the "rage" method shown here: http://forum.xda-developers.com/showthread.php?t=834228
I download all the files and everything needed, I get adb to work, and I type in the displayed commands. My problem comes in when I move over to the phone and use Terminal Emulator. I type in /data/local/tmp/rage just as the directions specified but emulator then spits back: /data/local/tmp/rage:not found.
I have scoured the internet to find a solution to this problem and I can't seem to find any postings of someone else having the same problem. How do I get past this. Is there something I am missing? Please help!
in terminal or in adb shell... go to that directory to tmp
then do ls to check if rage is in there
so you would go
cd /data
cd /local
cd tmp
then
ls
and hopefully you should see rage in there if you do then try it again if you dont push it back in there
I tried your suggestion using terminal on my phone and it keeps telling me Is: permission denied. So I tried cd /data\local\tmp and it let me get to that point. then i tried the dir command and I get dir: permission denied.
hey, i recently rooted my desire z and i had that problem too
i found that if you don't do run this
Code:
$ adb shell chmod 0755 /data/local/tmp/*
make sure you run that before you type /data/local/tmp/rage in your terminal
I got it to work!! I am rooted. I finally realized that I had missed a space. I am about to flash my first rom!! YAAAAYYY. Thanks to all the hard work of others and their wonderful directions lol

Root for Fire Phone with SuperSU

** 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

Categories

Resources