Develop Bugs

Regaws Root Method???

Is there something additional I need to do to actually gain "root"? I can't install the clear lock screen from smurf, can't wireless tether.... Don't know what's going on, all of this used to work fine on my Hero - what am I missing?

I don't think you have given enough info for people to even know what the problem is that you are having. Maybe you could be a bit more specific. Do you have superuser installed?

Sorry about that.... basically im on stock 2.2 with supposed "root" using regaws method - problem is, I can't use anything though; adb, wireless tether, I can't flash a lock screen (just sits at boot screen).

Download superuser app from the market place or google it if it is not on your phone already. Install it then launch an app that requires root. You will know real fast if you are rooted.

DomSim said:
Download superuser app from the market place or google it if it is not on your phone already. Install it then launch an app that requires root. You will know real fast if you are rooted.
Click to expand...
Click to collapse
I do have SU... that's the thing but when I try ADB Remount it says device not permitted or something like that, can't remember exactly

You could try full wipe / reflash.
Maybe try a diff ROM too.

You need to flash the engineering bootloader (0.76.2000). Go to Toast's method part 2 and follow the steps to unlock nand. You need the engineering bootloader in order to access /system.
Sent from my PC36100 using XDA App

sombdy said:
You need to flash the engineering bootloader (0.76.2000). Go to Toast's method part 2 and follow the steps to unlock nand. You need the engineering bootloader in order to access /system.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Nand root... I was looking for more info on this, I thought it was the culprit, thanks - ill post results, hopefully good
Edit: Won't work "Permission denied" .... this is really starting to piss me off grrr

DirtyShroomz said:
Nand root... I was looking for more info on this, I thought it was the culprit, thanks - ill post results, hopefully good
Edit: Won't work "Permission denied" .... this is really starting to piss me off grrr
Click to expand...
Click to collapse
Have you run Unrevoked Forever? This will turn off security permissions and should then allow you to flash anything.
Sent from my PC36100 using XDA App

Ok, the reason
Code:
adb remount
doesn't work is because the boot.img isn't patched to allow that, because I forgot to at the time of posting. You still have root (as long as you actually completed the guide successfully), that's just an all time access root through adb
To acheive the same results, type
Code:
adb shell
type
Code:
su
you will then see #. thats root.
Then remount your /system partition using
Code:
mount -o rw,remount / /system
there you go.

regaw_leinad said:
Ok, the reason
Code:
adb remount
doesn't work is because the boot.img isn't patched to allow that, because I forgot to at the time of posting. You still have root (as long as you actually completed the guide successfully), that's just an all time access root through adb
To acheive the same results, type
Code:
adb shell
type
Code:
su
you will then see #. thats root.
Then remount your /system partition using
Code:
mount -o rw,remount / /system
there you go.
Click to expand...
Click to collapse
When I try to type "su" it says "Permission denied"

DirtyShroomz said:
When I try to type "su" it says "Permission denied"
Click to expand...
Click to collapse
Do you have usb debugging on?

Try the new 1 click root in the dev forum. Unrevoked 3.2. See if that doesn't do the trick.
Sent from my PC36100 using XDA App

My guess is you didn't flash the 2.2-root.zip at the end then.. That's the best I can do w/ the info you've given.

one was already asked once but i had two questions
1. Is USB Debugging turned on or off? Settings > Applications > Development
2. you are using a stock rooted rom. are you trying to use sprint's wireless tether app? Sprint's app wont work you need to download wireless tether from the market.

joebags said:
one was already asked once but i had two questions
1. Is USB Debugging turned on or off? Settings > Applications > Development
2. you are using a stock rooted rom. are you trying to use sprint's wireless tether app? Sprint's app wont work you need to download wireless tether from the market.
Click to expand...
Click to collapse
Running stock 2.2. Regaw I did flash 2.2-root at the end and I am trying to use wireless tether not Sprints hotspot
I do have superuser in my apps list and I was able to install SNeoid, Swype, Setcpu, juicedefender and a few others that may require root but it wont let me do anything via adb or install any themes/mods that come in .zips

DirtyShroomz said:
Running stock 2.2. Regaw I did flash 2.2-root at the end and I am trying to use wireless tether not Sprints hotspot
I do have superuser in my apps list and I was able to install SNeoid, Swype, Setcpu, juicedefender and a few others that may require root but it wont let me do anything via adb or install any themes/mods that come in .zips
Click to expand...
Click to collapse
ok do this in command prompt and paste the results in code tags (to save space)
Code:
adb shell ls /system/bin/

regaw_leinad said:
ok do this in command prompt and paste the results in code tags (to save space)
Code:
adb shell ls /system/bin/
Click to expand...
Click to collapse
Code:
setconsole
dumplayer
svc
e2fsck_recvy
chownto
apph
ps
id
chownThp
notify
dhcpcd
pand
renice
bugreport
snd8k
hciattach
iqfd
top
lsmod
setprop
ionice
ifconfig
iptables
kthp_proxy
logwrapper
getevent
htcipcd
su
start
iqd
wipe
ip
smd
sleep
getWiMAXPropDaemond
newfs_msdos
vdc
sync
udhcpd
pppd
rmmod
fsck_msdos
netstat
route
sound8k
rm
radiooptions
pm
logcat
setWiMAXPropDaemond
resize2fs_recvy
htc_inittest
vmstat
dvz
mmcamera_test
keystore
dmesg
system_server
linker
fbtool
reboot
sdptool
busybox
hd
iftop
insmod
bootcomplete
rild
schedtop
debuggerd
wpa_supplicant
schedtest
bluetoothd
ping
btld
ime
omx_tests
tc
sendevent
racoon
toolbox
date
bma150_usr
bootanimation
wimaxDhcpRenew
log
installd
wimax_uart
applypatch
wimaxAddRoute
dexopt
monkey
ln
getprop
album_hdmiexe
stop
surfaceflinger
uevent
akmd
monitorMTD
wimax_mtd
mv
debug_tool
servicemanager
wimaxDumpKmsg
dumpstate
ipd
DmWrapperTest
nandread
kill
gzip
chmod
rmdir
lsc_camera
dbus-daemon
run-as
netcfg
cat
htclogkernel
sh
mount
printenv
mkdir
bmgr
wimaxDhcpRelease
umount
mke2fs_recvy
dnsmasq
input
df
ioctl
am
wimaxDumpLogcat
app_process
chown
htc_timezonetest
service
netd
ls
netsharing
cam_ins_spmo
mm-venc-omx-test
dalvikvm
ser2net
dmagent
shutdown
ndc
dumpsys
mediaserver
vold
sequansd
awb_camera
dd
keypress
cmp
mscompress
wimaxDumpLastKmsg
mtpd
watchprops

ok, so "su" is in there... you should be able to
Code:
adb shell
su
and it give you a #
try opening SuperUser.apk on your phone, THEN doing the above commands. a pop up should come up on your phone saying to allow root to su

regaw_leinad said:
ok, so "su" is in there... you should be able to
Code:
adb shell
su
and it give you a #
try opening SuperUser.apk on your phone, THEN doing the above commands. a pop up should come up on your phone saying to allow root to su
Click to expand...
Click to collapse
that worked, now to get remount do i have to always use that previous command you wrote?

root

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.

How to Unroot Kindle Fire! [Win/Mac/Linux][Video]

Here's how to unroot Kindle fire using adb, works on Windows, Mac, and Linux:
Step 1. Download adb.zip and unzip, you should get a folder called adb.
Download adb.zip
Step 2. Open up a command prompt or terminal and type:
For Windows:
cd \adb
For Mac or Linux:
cd /adb
Step 3. Type the following to get into ADB shell:
For Windows:
adb shell
For Mac:
./adb-mac shell
For Linux:
./adb-linux shell
Step 4. Copy and paste the following to enable read/write on filesystem:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Step 5. Type the following to remove rooting files:
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/xbin/su
Step 6. Type the following to reboot and your Kindle Fire should be fully unrooted!
reboot

Excellent instructions for both root and unroot, thank you. I wasn't aware of typing "su" though before step 4. Thankfully you covered that in the video.

Yes, should edit to mention su

Awesome!
Sent from my Kindle Fire using Tapatalk

Yep, nice concise post, but need to add a couple of things:
1. su before the mount command.
2. /system/bin/su doesn't always exist as it depends on what root method you used.
For me, only the xbin version existed, so people shouldn't freak out if they get a "No such file or directory" message!

Ota rootkeeper
Once the Kindle Fire is rooted, OTA ROOTKEEPER app allows you to easily root/unroot (i.e. you want to see Amazon Premium videos. Only allowed if unrooted.)
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
To see youtube video, search OTA Rootkeeper Kindle.
Download via Google Android Market.
Works great

ByByIpad said:
Once the Kindle Fire is rooted, OTA ROOTKEEPER app allows you to easily root/unroot (i.e. you want to see Amazon Premium videos. Only allowed if unrooted.)
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
To see youtube video, search OTA Rootkeeper Kindle.
Download via Google Android Market.
Works great
Click to expand...
Click to collapse
Definitely and so easy.

ByByIpad said:
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
Click to expand...
Click to collapse
I'll save you the trouble of rebooting...
Just stop the Amazon video app. There is no need to reboot. I use Advance Task Manager Pro personally because I purchased it for use with my Archos tablets but it isn't necessary you can do it through Settings-> Applications also.
Sent from my HTC Flyer P512 using Tapatalk

ByByIpad said:
Once the Kindle Fire is rooted, OTA ROOTKEEPER app allows you to easily root/unroot (i.e. you want to see Amazon Premium videos. Only allowed if unrooted.)
Once you unroot/root with OTA Rootkeeper, you will need to restart for new settings to take.
To see youtube video, search OTA Rootkeeper Kindle.
Download via Google Android Market.
Works great
Click to expand...
Click to collapse
Thanks SO MUCH! Definitely add this to your Kindle if you're trying to keep hacking it but can't stand to be without all six seasons of LOST.

Mount Issue
When I run the command to mount i get the following error:
mount: Operation not permitted
I'm using Mac OS 10.7.2
Nevermind!! Just had to see the "su" command in the tutorial. Sorry.

I have to unroot so I can send my KF back to Amazon.
If I user the OTA RootKeepr, is their anyway for them to figure out it was rooted? Once I use that app, I just wipe my KF? Thats it?

Just update to 6.2.1 and it should wipe it.
Sent from my Kindle Fire using xda premium

borborpa said:
Just update to 6.2.1 and it should wipe it.
Sent from my Kindle Fire using xda premium
Click to expand...
Click to collapse
I apologize but do I update? My KF says 6.2_user right now.
---------- Post added at 07:53 AM ---------- Previous post was at 07:07 AM ----------
c:\>cd adb
c:\adb>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
What am I doing wrong?

OTA Rootkeeper is freaking awesome! My mom was so bummed after I rooted her KF and found out she couldn't watch movies anymore. This saved my bacon.
Sent from my EPAD using xda premium

I unrooted but still cannot view prime videos. Any suggestions?

Hi... I have a kindle fire ver 6.3 I am trying to unroot it but when i get to adb shell, it said device not found... i have installed android sdk, and kindle driver but no help... please advise!

Thanks for the nice contribution! Covered both! No need to worry how to root or unroot.
Would like to read more tips on using the Kindle Fire as the tablet column I came across in aneesoft.
Cheer!

I followed the method and unrooted my kindle. I found one issue after rebooting , it gave error " android.process.acore" has stopped working. As per Zedomax suggestion, I did Factory reset and problem was solved
Thanks for helping!!

[Q] Google Plus: no map on location

Hello everybody,
i noticed an issue this morning with google plus.
As i think you know, latitude is going to disappear and i activated the location share on google plus.
But when i go into local, i can see all my friends sharing their positions, but the map doesn't show... as a matter of fact, i see icons on a empty display.
I tried to reboot, to clear cache and dalvik, also to remove and re-install google plus app, but nothing changed... have you some idea? what kind of problem is this?
Thanks,
Claudio

Same problem here on my Nexus 4 with CM 10.1. Aso reboot, reinstall, etc. does not help.
Maybe somebody else knows how to resolve this issue.

Same here on my Nexus 4. CM 10.1.1.
This issue doesn't seem to be reported anywhere else. Hopefully we can get to the bottom of this.

Yeah, it's true.
I tried to google the problem, but i can't find any report

I will add this is also an issue on my nexus 7 with cm 10.1.1.
Sent from my Nexus 7 using XDA Premium HD app

Yes, confirming this on N4 with CM 10.1.1.
Weird

Solution, it seems.
A potential solution:
MAKE SURE YOU ARE COMFORTABLE WITH YOUR FILE EXPLORER
Claude Robinson on G+:
"Google plus needs to be a system app in order for locations to work. There is an adb method but I don't know how to do that so I did it manually with root explorer.
First you need to go to /data and move com.google.apps.plus-1.apk to /system/app then you have to go to /data/app-lib/com.google.apps.plus-1 move all the files out of that folder into /system/lib reboot and you're done. You should now have the locations feature with maps working. While you are moving Google plus it will force close on you. Just hit OK until you are done and can reboot."
If you have any issues try clicking on the .apk to install it while it is in system/app. I cleared my data, but I don't know if that is necessary. My maps are working again.

sjoshua270 said:
This should fix the issue, if I am not mistaken.
Click to expand...
Click to collapse
this, what?

djsnake81 said:
this, what?
Click to expand...
Click to collapse
Sorry, forgot the text there.

Thank you sjoshua270, your fix worked for me!
This is what I did:
Code:
[email protected] ~ $ adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # cp /data/app/com.google.android.apps.plus-2.apk /system/app/
[email protected]:/ # cp /data/app-lib/com.google.android.apps.plus-2/* /system/lib/
[email protected]:/ # rm /data/app/com.google.android.apps.plus-2.apk
[email protected]:/ # rm -R /data/app-lib/com.google.android.apps.plus-2
Mount system as read-write (not sure if needed)
Copy apk from /data/app to /system/app
Copy libs from /data/app-lib/.. to /system/lib/
Remove original APK
Remove original libs
Reboot phone

sjoshua270 said:
A potential solution:
MAKE SURE YOU ARE COMFORTABLE WITH YOUR FILE EXPLORER
Claude Robinson on G+:
"Google plus needs to be a system app in order for locations to work. There is an adb method but I don't know how to do that so I did it manually with root explorer.
First you need to go to /data and move com.google.apps.plus-1.apk to /system/app then you have to go to /data/app-lib/com.google.apps.plus-1 move all the files out of that folder into /system/lib reboot and you're done. You should now have the locations feature with maps working. While you are moving Google plus it will force close on you. Just hit OK until you are done and can reboot."
If you have any issues try clicking on the .apk to install it while it is in system/app. I cleared my data, but I don't know if that is necessary. My maps are working again.
Click to expand...
Click to collapse
Thanks sjoshua, this worked great to me too!!!:good:

I moved the files as explained but find that now G+ is not installed. When go to run the APK from the /system/app/ folder to install it I get a "Parse Error" and can't install the app.
Can anyone help? This is the first time I've tried moving an app to the system folder.

from http://productforums.google.com/forum/#!msg/google-plus-discuss/PC4OKKAdjPM/6_FD10neqL0J
Solution found!!!
https://productforums.google.com/d/msg/google-plus-discuss/a_BJvcTJvtE/WAXOWtU_TckJ
https://plus.google.com/109052420587654093130/posts/Rzg2aL4wpi5
Note that if you are a TitaniumBackup user, the "convert to system app" does not work for this. You must follow the steps outlined in the G+ post.
Click to expand...
Click to collapse

google plus, missing maps
the new google plus has the friends locations . but when i go to locate a friend it shows the name of friend but no map. just this bunch of little squares..
how do i make the map show up. ?? is there a fix for that?
im on CM 10.1

never mind guys i found this gapps that fix the issue.
Steve Jones is the man to thank.
http://goo.im/devs/trevd/gapps/gapps-jb-20130615-signed.zip

Lw00d said:
never mind guys i found this gapps that fix the issue.
Steve Jones is the man to thank.
http://goo.im/devs/trevd/gapps/gapps-jb-20130615-signed.zip
Click to expand...
Click to collapse
Found it through G+, actually, but thanks for dropping this here!
Reported thread for merging with http://forum.xda-developers.com/showthread.php?t=2359379 (older thread), as I believe its the same issue.

I realized that I have to move the app / reinstall it from system folder after each restart, or it keeps force closing on me :\
Is there any other, more reasonable workaround yet?

Abondhal said:
I realized that I have to move the app / reinstall it from system folder after each restart, or it keeps force closing on me :\
Is there any other, more reasonable workaround yet?
Click to expand...
Click to collapse
New gapps package
http://forum.xda-developers.com/showthread.php?t=2369403
Lw00d said:
never mind guys i found this gapps that fix the issue.
Steve Jones is the man to thank.
http://goo.im/devs/trevd/gapps/gapps-jb-20130615-signed.zip
Click to expand...
Click to collapse

Thanks, but this package also doesn't seem to include G+ as system app. So it's not force closing, but I'm back to no map tiles :-\
Sent from my Nexus 4 using xda app-developers app

Worked for me, but my apk had a "1" not "2"
Code:
[email protected] ~ $ adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # cp /data/app/com.google.android.apps.plus-1.apk /system/app/
[email protected]roid:/ # cp /data/app-lib/com.google.android.apps.plus-1/* /system/lib/
[email protected]:/ # rm /data/app/com.google.android.apps.plus-1.apk
[email protected]:/ # rm -R /data/app-lib/com.google.android.apps.plus-1
Abondhal said:
Thank you sjoshua270, your fix worked for me!
This is what I did:
Code:
[email protected] ~ $ adb shell
[email protected]:/ $ su
[email protected]:/ # mount -o rw,remount /system
[email protected]:/ # cp /data/app/com.google.android.apps.plus-2.apk /system/app/
[email protected]:/ # cp /data/app-lib/com.google.android.apps.plus-2/* /system/lib/
[email protected]:/ # rm /data/app/com.google.android.apps.plus-2.apk
[email protected]:/ # rm -R /data/app-lib/com.google.android.apps.plus-2
Mount system as read-write (not sure if needed)
Copy apk from /data/app to /system/app
Copy libs from /data/app-lib/.. to /system/lib/
Remove original APK
Remove original libs
Reboot phone
Click to expand...
Click to collapse

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