Related
Ok, to save some people some time here for rooting and opening it up to non-market apps on your bravo, and probably any motorola AT&T device.
1. Z4Root is the easiest way to root since you just get it from the market. One buttons press then done.
2. to modify the settings.db in /data/data/com.android.providers.settings/databases/ use the SuperOneClick which you can get here
http://forum.xda-developers.com/showthread.php?t=803682
3. I used root explorer, which you can get from the market and just edited the /system/etc/motorola/com.android.providers.settings/secure.mkitso
and /system/etc/motorola/com.motorola.android.providers.settings/settings.mkitso files in place. Copying them, editing them, and chmodding them didn't seem to work for me for whatever reason. The way I did it, you don't have to do anything other than edit the file in text editor and factory reset your phone.
Rooted mine the other day using the Droid 2 root method at modmymobile.
I can't post links yet, so here's the instructions:
dragonius said:
Setup:
- Make sure you have ADB installed properly and the latest Motorola drivers.
- Download attached archive
- Extract to a directory, I used C:\Droid2Root
- Make sure you have USB degugging enabled
- Change connection to PC Mode
Process:
- Open Command Prompt (Start - Run - cmd - Enter)
- adb devices (to verify the connection)
- cd C:/Droid2Root
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push su /sdcard/su
- adb push busybox /sdcard/busybox
- adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage-arm5.bin
- adb shell
- cd data/local/tmp
- chmod 0755 rageagainstthecage-arm5.bin
- ./rageagainstthecage-arm5.bin
- Let the process run until the prompt returns you to C:/Droid2Root (be patient, it takes a while, but does happen. If not, reboot phone and try again.)
- adb devices (to verify the connection)
- adb shell (you should now have a # prompt)
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- cp /sdcard/Superuser.apk /system/app/Superuser.apk
- cp /sdcard/su /system/bin/su
- cp /sdcard/busybox /system/bin/busybox
- chmod 4755 /system/bin/su
- chmod 4755 /system/bin/busybox
- mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
- exit
Once you have achieved root, to update the Superuser.apk to the latest version, run these commands:
- adb shell
- su
- mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
- rm /system/app/Superuser.apk
- pm uninstall com.noshufou.android.su
Then search on the market for Superuser and download the one by ChainsDD. Confirmed working on latest Droid2 2.2 OTA & the new leaked 2.3.15 OTA.
Click to expand...
Click to collapse
On the Bravo its not "PC Mode", I think its "Portal and Tools" Other then that, everything worked flawlessly.
Thanks, a bunch. I actually used the Z4Root app from the market and it worked flawlessly. Now I'm just trying to figure out how to allow non market apps and maybe get an overclock going on this. any suggestions?
Grape Drank said:
Thanks, a bunch. I actually used the Z4Root app from the market and it worked flawlessly. Now I'm just trying to figure out how to allow non market apps and maybe get an overclock going on this. any suggestions?
Click to expand...
Click to collapse
I just bought this phone for my younger brother and I'm impressed. I have a Droid Incredible and its just as smooth. I also verified that the Z4root app from the marketplace roots the phone.
Did anyone get it unlocked yet
Yeah, it's a great phone. I'm trying to get the settings.db thing to work so we can install non-market apps, but it doesn't seem to be working. I got the db modded and put back in place, but I still don't see the option in the application manager screen.
IMO this is the #2 android phone on AT&T next to the captivate. that SAMOLED is great and the GPU on the captivate is top notch.
Anyway, if anyone can assist on the non-market app thing that would be great.
So far, I have rooted with Z4Root, removed the AT&T crapware, installed the MarketAccess to get around the stupid AT&T market filters. Last thing is to get the non-market apps going. After that it's a matter of waiting for this device to gain popularity and some custom ROMs.
I managed to get my Bravo to install non-market apps using:
1. SuperOneClickv1.5.5-ShortFuse
2. Click Here
I am not sure if just step 2 alone would be OK though.
Remember, you have to factory reset after you have finished with step 2.
Good Luck!
I edited my original post with the steps and tools I used to get the phone rooted and non-market unlocked.
Wait so can some explain how to unlock it?
Sent from my SGH-T959 using XDA App
cooldead said:
Wait so can some explain how to unlock it?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
If you mean "unlock" as in able to use the phone on a different carrier no one has posted how to do it yet. The OP meant allowing non-market apps.
Got cha, thanks.
Sent from my SGH-T959 using XDA App
cooldead said:
Got cha, thanks.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
No problem
I'm lost here,
Downloaded z4root onto my phone because it's not available on Market,
but it won't let me run the z4root.apk because it's not a market app.
total newb here, so any help would be appreciated.
thanks
Nevermind, got z4 to install using Android Central's Sideload Wonder Machine, then rooted my phone no problem, installed TiTanium backup, and rid of the bloatware.
Phone processes quicker, from settings, fetching list of running apps, data manager, manager etc, list loads much quicker now.
How did you go about getting rid of the garbage-ware? curious.
Hi I'm posting here in hopes to get a response because I cannot seem to get a response on the S1C forum. I rooted with z4root but cannot get non market apps enabled using S1C. I have .net framework 4.0 using vista and the motorola drivers from their site. I get as far as "getting mount path" and then it fails. Am I missing something or should this be working for me. And if so, what could be the problem? Many thanks.
SideloadWonderMachine worked for me, give it a shot. 2 clicks to add an app. Pretty foolproof (I am a fool).
Rooted my Bravo using adb install z4root (linux PC) then ran z4root from phone, worked great.
just rooted Bravo using Droid2Root files and manual ADB commands, from the thread that Gumpo10k shared in this thread, up above. Worked great, now I need a good 2.2 ROM to get tethering working.
1. Download and install Samsung_USB_Driver_for_Moblie_Phones_v1_4_6_0.exe
Link to download: http://www.multiupload.co.uk/YXE6FWLFAR
2. Download and install Android SDK (http://dl.google.com/android/android-sdk_r16-windows.zip)
3. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
4. Using windows/cmd go to the folder where Android SDK was installed (make sure that the folder android-sdk/platform-tools/ contains fastboot.exe and adb.exe etc....
5. using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
6. First we have to unlock bootloader,
use this command to unlock bootloader > fastboot oem unlock
(warning.. you will loose all data)
After the bootloader is unlocked the device will reboot normally.
7. Once normally booted from the command prompt issue the commands given below (after each command press enter button)
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
cancerouspete said:
it would be good to note that many people have issues with the initial android driver installation.
if you install the drivers, but the phone doesn't show up after a period of time, open control panel -> system -> device manager and look for any devices that have a yellow triangle error (no driver). right click and open properties, and manually select the driver, not auto! the next screen will give you an option to 'select from a list', do this, and find SAMSUNG, then select the latest drivers.
after this, it can still take a minute or two the first time for drivers to install properly, you usually can see the status of this in the usb system tray icon.
if you rebooted to the bootloader (power vol(+) vol(-)), from the command line, if you type "fastboot devices" it should list a device and serial number. if not, you need to go check your drivers, something is missing. also, don't forget how magical a windows reboot can be at times : )
Click to expand...
Click to collapse
Hi
Thanks for this note which would help many users.
Hi, noob here.
First of all, thanks for the guide.
I have already unlocked the bootloader about a month ago (up to step 6), but would like to root.
Will my phone lose all data again if I root the phone now? I'm not even sure what this actually does, but would like to learn and mess around with it.
You will not loose data. Rooting gets access your system folders by pushing su and superuser through adb.
Hope it helps.
Sent from my Galaxy Nexus using xda premium
smohanv said:
Note: you need su and superuse.apk (which can be downloaded from here: https://rapidshare.com/files/1319181583/su.zip)
unzip the downloaded file in the same folder where fastboot.exe exist i.e /android-sdk/platform-tools/
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
adb reboot
Done!... your device is now rooted.
Click to expand...
Click to collapse
Did you actually test that with a stock rom?
Because adb root will not work with ITL41F at least.
Code:
./adb root
adbd cannot run as root in production builds
Furthermore the chmod for Superuser.apk is totally bogus. No need to mess with it's permissions.
i think a better way is get su and SuperUser.apk from the developers (ChainsDD) site and install it with a temporary boot CWM to install it.
(these instructions are also from memory And i rooted my one from source, but that's a bit involved)
this would mean instead of step 7 do.
7. Download CWM into the same directory as fastboot
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.4-toro.img (Verizon)
or
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.5.0.2-maguro.img (GSM)
Make sure to get the right version for your device.
8. download http://downloads.androidsu.com/superuser/Superuser-3.0.7-efghi-signed.zip
onto the internal storage of the phone( "sdcard" )
9. With the phone turned OFF, hold VOLUME UP + VOLUME DOWN and power the phone on. This will put you in bootloader mode
10. again using windows/cmd go to the folder /android-sdk/platform-tools
From this folder try the command "fastboot devices" (do not include ") which should list the device connected to your PC.
11. Start CWM (without installing it)
fastboot boot recovery-clockwork-XXX-XXX.img
(use the right filename from step 7)
12. choose install update and select the zip from step 8.
You need to use volume up/down to navigate and power to select.
I wanted to change my device model, so I copied build.prop from another mobile to my mobile. I am already rooted. But unfortunately I did not change the o.s. from gingerbread to froyo in build.prop ( I have android 2.2 FROYO) When I rebooted, there were many errors. It is now showing no sim card. Mobile network search gives error. Effectively, I can not use the mobile. Terminal emulator, X-plore etc. stopped working. Only Rom toolkit free version works and astro file manager works. Other programs are forcefully closed. Needles to say, I must replace new build.prop with new one.
Using adb I can only pull files but can not write as it is in read only mode.
adb root and adb remount works only if you are in recovery mode ? Y mobile does not have any custom recovery so when I boot in recovery mode it hangs.
Superuser has installed su in system\bin directory. But from adb shell I can use su also. It gives permission denied error. Hence I can not remount the system.
I have read similar threads and found that on some mobiles adb root or adb shell su works but on some not.
I am using Vista 32 bit with admin rights, still can not use root in adb.
Please tell me, how can I mount system read-write. I can not install root explore as google play and even internet is not working.
Please help.
maheshchavan said:
Using adb I can only pull files but can not write as it is in read only mode.
Click to expand...
Click to collapse
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
ruscan.calin said:
activate USB debugging then in console
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
adb push build.prop /system/build.prop
check where is your build.prop
Click to expand...
Click to collapse
OMG ruscan.calin i COULD KISS YOU! I had tried to change my OG EVO 4G's buildprop file to another phone so that I could purchase & download an incompatible Google Play app. However after I restarted the phone wouldn't start! It would boot into my rooted HTC EVO 4G Android 2.3.3 and HTC Sense 2.1 but it would get stuck on the wallpaper with just the notification bar at the top and all buttons would be frozen. However I noticed when I plugged in my phone to my computer via usb the computer recognized it. I always keep my phone with USB debugging enabled so I thought I should be good right? I have spent the last 4 hours trying to install and setup adb with no real previous experience with it. I am familiar with dos from years ago and that helped me as it's basic procedure, commands, etc. Then I found out how to install the HTC drivers which I needed and then download the Android SDK with adb that's included which many guides show easily. I started the command prompt (cmd), typed my adb devices command and hurray it showed my phone! I connected and quickly navigated to the build.prop system folder! Luckily when I changed the file I made a bak backup and left it in the same folder. Now the main issue was figuring out how to change the naming of the files which I did via usual adb commands (mv build.prop.bak build.prop). But then to no avail I couldn't get it to write due to it being a system read only folder! Arg! Then I found your post on here, above, and typed it in simply leaving out the adb push portion and replacing that with the mv file command instead and first changing the name of the bad file and then replacing the bak file as the good copy! I exited back to the adb main and unplugged my phone. Moment of truth and man was everything flashing through my head at once! I booted up and YESSSSSSSSSSSSSS, it worked! I went back into root explorer and got rid of the offending leftovers and I've learned my lesson! I just don't want to think about what would have happened if I hadn't found this post. Thank you and if anyone else makes this hug mistake let me know and maybe I can help. Moral of the story don't mess with the build.prop or any system folder unless you know what you're doing! Thanks again!
Quick Guide to Fix Android "build.prop" Issues:
1. Find and download USB drivers for your phone by model or type (HTC EVO 4G's HTC Fastboot drivers): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
2. Download and install Android SDK and choose adb: http://developer.android.com/sdk/index.html
Guide: http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
3. Run a command prompt from the "c:/program files/android/android-sdk/platform-tools/" directory. I had to copy the command prompt to get it to open there but sometimes a right-click action will do it. The guide below will help just navigate down to "Using ADB" and skip the rest.
Guide: http://www.howtogeek.com/114667/how...y-default-move-almost-any-app-to-the-sd-card/
4. Once you open the command prompt and you're in the "c:/program files/android/android-sdk/platform-tools/" foler type "adb devices" and your device should appear. If it does move on to next step.
5. Then type adb shell and use the ls command to see directories. Then you'll need to navigate to the system folder by typing "cd system" and then type "ls" to look around in the directory (similar to "dir" in DOS). You should now see the bad build.prop file.
6. You'll need to rename the file or push a correct version. First you need to use the "adb shell" command again and then "su" and finally "mount -o rw,remount /dev/block/mmcblk0p1 /system" to make the directory writable (see ruscan.calin post above for additional info).
Note: I only had to rename my build.prop as I already had my old one in the same system folder. You may have to copy the bad build.prop to your computer, edit it and then push it back to the same system directory. These directions are only for renaming files in the same folder. For the info on how to copy the file to your computer and push it back to your phone go to step *10 below or use the guide below it.
7. I already had the bad build.prop in the system directory with my old one which I had named build.prop.bak. If you have this too simply rename by changing the name first of the bad file to anything by typing "mv build.prop build.prop.bad" or similar.
8. Next rename the build.prop.bak to build.prop by typing "mv build.prop.bak build.prop". Everything should go smoothly and move onto the next step.
9. Finally, If no error messages are found, simply type "adb reboot" or "adb shell reboot" (Depending which version of ADB you have). You should be done, your phone will reboot like normal (working, lol) and everything should be working again! YAY!
*10. To copy the build.prop to your phone type "adb pull /system/build.prop c:\" and the file should be placed in the main c:/ directory on your computer. Navigate to the root (c:/) directory and then right click and "open with" the "build.prop" file using a notepad or other file editor. Then use the text editor (Notepad, etc) to change back what you originally changed to mess everything up. There is tons of stuff on the net to let you know what to fill back in depending on your phone model/type. Or it's possible to get a previous version from an old Nandroid backup or similar. Save the changed text file and make sure its named the same "build.prop" and make sure it's still in the root directory (If you're having issues on this step or just want more insight check out the guides and threads below for more help).
Guide 1: http://androidforums.com/admire-all...p-computer-not-phone-using-root-explorer.html
Guide 2: http://www.modaco.com/topic/328943-quick-guide-to-modifying-buildprop-with-adb/
Guide 3: http://forums.androidcentral.com/sp...-replaced-build-prop-phone-wont-start-up.html
*11. We've already made the directory writable in step 6 so we simply need to push the file back to the phone. If any error message appear re-do step 6 to make writable again. Otherwise push the modified file back to the phone by typing "adb push c:\build.prop /system/". Back to step 9 above! Yay!
If anyone wants to help cleanup this quick guide or make any changes feel free. I just wanted something so that if anyone else has this issue they won't have to worry or search forever to find a solution. OMG it's 2:30AM, to bed... I ride! LOL
Enjoy,
5th :highfive:
THANK YOU!!! Totally saved me today.
One thing that I noticed. After pushing the correct build.prop, I had to fully power down, then turn back on my Razr for it to load up the fixed build.prop.
error message,Help please
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
jigarpattani said:
Hello, when i am going to mount and change the permission i am getting constant error od device not found or sh:not found.
What to do?Help me please?
Click to expand...
Click to collapse
What step are you on? What phone do you have? More info please?
i am have problem whit my pantech flex i need to use the build.prop.bak but when i type the su it stay in blank do nothing any ideas pls help
ehy there hope someone can help me...i have an archos 97b platinum, messed up with build.prop. So i pulled out and restored but can't push in any way. I have a cwm installed, tablet rooted but i alwais got "permission denied" at push command. Other error is operation not permitted" if i try remount command from adb. i can do mount -o rw,remount /dev/block/mtdblock7 /system but after that push still give me permission denied.
any suggestion?
http://imgur.com/FDLp4fl
i open a 2nd cmd, give the mount -o rw,remount /dev/block/mtdblock7 /system , and system is now rw, but from the first cmd when i give "push build.prop /system (or /system/build.prop) it will always return me permission denied
help
dev.block
i want to view to dev/block using adb shell #
eg . what block is boot.img
what block is recovery.img
what block is system.img
what block is cache.ing
adb shell getprop mtd is not work . Pls Help Me & sent to mail [email protected]
** 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
After dabbling around in some murky waters trying to achieve root, and going trough some 2010 stuff I did, I did discover a method I devised back then works to some extent, strangely.
Using fastboot (boot) to a TWRP recovery image (TWRP_v2.8.6.0_honami-f2fs_from_cm12.1_150423.img), mounting /system, and pushing a version of busybox, bash and using the supersu su binary already in the TWRP recovery image.
boot-new.img.bz2.zip (rename to boot-new.img.bz2 before extracting -.Just TWRP_v2.8.6.0_honami, with a different kernel and dt image included to boot from fastboot)
bash and busybox i compiled from git and debian sources yesterday/today
Basically this; (use only for reference.)
Code:
# Magically push all files in place here.
# Optionally, move /system/bin/sh out of the way and link /system/bin/sh to bash
./"$ADB" shell "chmod 755 /system/bin/bash && chown 0.0 /system/bin/bash"
./"$ADB" shell "chmod 4755 /system/bin/busybox && chown 0.0 /system/bin/busybox"
# TWRP
#./"$ADB" shell "cp /supersu/su /system/bin/_su"
./"$ADB" shell "cp /supersu/su /system/bin/su"
./"$ADB" shell "cp /supersu/supolicy /supersu/su /system/xbin"
./"$ADB" shell "cp /supersu/libsupol.so /system/lib/"
./"$ADB" shell "chmod 0644 /system/lib/libsupol.so && chown 0.0 /system/lib/libsupol.so"
./"$ADB" shell "cp -r /supersu /system/app/SuperSU"
./"$ADB" shell "chmod 0755 /system/app/SuperSU && chown 0.0 /system/app/SuperSU && chmod 0644 /system/app/SuperSU/SuperSU.apk"
#
#./"$ADB" shell "chmod 4755 /system/bin/_su && chown 0.0 /system/bin/_su"
#./"$ADB" shell "echo "busybox su -c "_su"" > /system/bin/su" # or busybox su -c "_su -c /system/bin/sh-org"
./"$ADB" shell "chmod 4755 /system/bin/su /system/xbin/su* && chown 0.0 /system/bin/su system/xbin/su*"
# Quite dangerous - Suggest moving passwd when in normal use
./"$ADB" shell "echo "root::0:0:0:/root:/system/bin/sh" > /system/etc/passwd"
./"$ADB" shell "chmod 0644 /system/etc/passwd"
Next step, to remount /system with write permissions from a normal boot, I think, would be to modify boot.img/default.prop and set "ro.secure=0"
Thought I had done this prior, I run with touch disabled as I cracked my screen (impressively massive drop of at least 30 cm! - onto object.. ) ... I could not remount system when I first tried.
Notes:
If i adb in early i can use supersu/su to gain root, when system is loaded busybox su -c ""supersu/"su" works. - NO AUTH
Hm, updated SuperSU via google play and suddenly it realized it was rooted . = ) Still keeping the supersu/su intact in /system/*bin
Thankfully I've been unsuccessful in grabbing root from /data/local/tmp this way as of now. Seems the permissions are reset. Though getting root without any auth is a serious matter no matter how you flip the coin. At least it's not as easy as pushing an archive to /data/local/tmp and running busybox su -c su. Also with a modified busybox you could easily skip the part where I write a /etc/passwd with no password.. Incredibly handy if you need root without Android running, say with setprop ctl.stop zygote, media and bootanim. But incredibly dangerous!
Fastboot to attached TWRP and install [STABLE][2016.02.02] SuperSU v2.65 - http://forum.xda-developers.com/showthread.php?t=1538053 - drop the zip to somewhere on the device and use the install function, i installed supersu via google play first. Attached is the kernel image i'm using. On a side-note, the script above failed .
Apart from this, the attached gnu-tools i will have to update... Got a neon flags optimized for out cpu and all, but that's for a different day.
Cheers, have a good one mates
Noob question: what is the difference between using this method for root and kingroot method? Which is better to use?
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
threader said:
I've not checked Kingroot. But my thought is not to rely on nasty kernel exploits and have an as clean as possible root. Kingroot was not working when i first started this post. Also i dont leave system read write mountable. To do system modification i fastboot the TWRP image
Click to expand...
Click to collapse
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Noticed my boot img was rebooting sometimes, went off and updated my compiler toolchain and had a look at the kernel and recent developments.
Had a look at X-Honami v6 and ported some parts of that effort to the latter Sony kernel used in 14.6.a.1.216.
* Messed around with memutils and implemented ARM_PLD_64BYTE and USE_LDRDSTRD_OVER_LDMSTM atop memutils from the Xperia-dev unified kernel. - this needs some testing but appears to be stable at least with the options turned on.
* Slight overclock of GPU to 533 mhz, and underclock to 27 mhz on idle.
* Has kexec hardboot
I cannot busybox su -c su with this kernel. Which is only useful for developers anyway. You'd be wise in running some benchmarks before and after the flash.
Kernel needs to be flashed via fastboot.
Source:
https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/
DectonX said:
Kingroot give you root but not supported and their binary are weired but when you replace it with supersu you can't mount system read/write cause of ric but thanks to Chainfire and his tools I find way to root with kingroot and replace it by supersu and disable ric
Click to expand...
Click to collapse
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
Ok i have done step #1 by manually updating supersu and it deleted the kingroot by itself. Now i need answer for #2 only, Which recovery should i install in stock based rom ?
VikasG09 said:
I have rooted my phone with king root , downloaded SuperSU-ME-PRO_9.3.8 to replace kingroot with supersu but the app stucks in middle while processing data. Can you please help me with the following things:
1. Which chainfire apk to use to replace kingroot with supersu (kingroot ver is 4.9.2)
2. I need to install Xposed framework, for which i belive i need to flash a recovery. As i am on stock based kernel and rom can you help me which recovery should i flash and further steps to get the xposed framework in my xperia z1 (5.1.1)
Click to expand...
Click to collapse
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
DectonX said:
long steps but 100% works
1. Download kingroot and root your phone
2.Download replace kingroot with SuperSU and extract it to internal memory
3.Download XZDual Recovery for your phone
4.Download Terminal emulator for play store
5.Download FlashFire by Chainfire from play store
6.Download SuperSU zip package
what you will do
1. Get root using kingroot
2.open terminal and write
Code:
su
sh /sdcard/mrw/root.sh
3. it will open SuperSU.... press update manual
warn : Don't click Reboot, if you rebooted phone ric will work and you will not have access to system partition
4. open FlashFire and grant SuperSU then press on lighting button
5. choose XZDual Recovery zip file and tick auto remount and press on flash or lighting button
black screen will apear preparing files and flash it then phone will reboot
6. when you see the green led press vol down to enter TWRP
7. flash SuperSU package
Note : if there is bootloop , enter recovery and go to setting> fix premission
and reboot
now you have SuperSU working 100%
Notes : no recovery will bring you xposed.... just try to open Xposed thread and download the package for your SDK
the recovery i use is XZDual Recovery from [NuT] it's very good for locked bootloaders
hit thanks if helped
Click to expand...
Click to collapse
Thanks a lot..
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
VikasG09 said:
Thanks a lot..
Click to expand...
Click to collapse
threader said:
I still suggest using the fastboot method with the TWRP boot image attached in the first post, mount the system partition, select install Zip SuperSu, forum.xda-developers.com/showthread.php?t=1538053 .
Cheers
I've got a kernel-copyleft-14.6.A.1.xxx to finish up and officially forum post ; ) https://github.com/threader/kernel-copyleft-14.6.A.1.xxx-backports/ . And update and official post might come this week. Been running this for months now and its stable, and fast, whee.
Click to expand...
Click to collapse
I just used kingroot, unlocked bootloader, flashed dual recovery, flashed prerooted Rom. That's it. Easy as pie.
Sent from my D5503 using Tapatalk