Amazon Fire 5th Gen 2015 Root[only hd 7 and os 5.0.1]

Have you tried adding the su binary to /sbin in the ramdisk, and editing default.prop to ro.secure=0?

just adding it to /sbin wont solve this. you would have to add all the selinux info for it also and then also manage to start the su daemon.
ro.secure=0 is already inside the attached boot.img above, doesn't seem to help

If we have r/w to the filesystem, take a look at the root script in this LG package: http://xdaforums.com/lg-g3/general/guide-root-method-lg-devices-t3129197

Do you think this method would work?

Lol wow! Seems to be sparked by my discovery of this new root method! Anyhow, @jkchr1s might be on to something.

---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------

jkchr1s said:

If we have r/w to the filesystem, take a look at the root script in this LG package: http://xdaforums.com/lg-g3/general/guide-root-method-lg-devices-t3129197

Do you think this method would work?

Click to expand...

Click to collapse

I'll try it!
EDIT: DON'T DO IT! IT CONTAINS LG DEVICE SPECIFIC THINGS AND IT COULD BRICK YOUR DEVICE. GOOD THING I LOOKED AT THE INSTALL.BAT BEFORE I TRIED IT!

Vlasp said:

Lol wow! Seems to be sparked by my discovery of this new root method! Anyhow, @jkchr1s might be on to something.

---------- Post added at 11:12 AM ---------- Previous post was at 11:10 AM ----------



I'll try it!
EDIT: DON'T DO IT! IT CONTAINS LG DEVICE SPECIFIC THINGS AND IT COULD BRICK YOUR DEVICE. GOOD THING I LOOKED AT THE INSTALL.BAT BEFORE I TRIED IT!

Click to expand...

Click to collapse

I don't mean to run the root.bat file, look at the root script. It copies SuperSU binaries, adds a su service, and chcon's the necessary files.

jkchr1s said:

I don't mean to run the root.bat file, look at the root script. It copies SuperSU binaries, adds a su service, and chcon's the necessary files.

Click to expand...

Click to collapse

Yeah, but we are going to have to change the device specific stuff (if it matters for our device).

This will work for rooting this device now.

Someone is root .............

With boot.img

Vlasp said:

This or KingRoot will work for rooting this device now.

Click to expand...

Click to collapse

I adapted the guide and u know what?. I am root!!!
Did all the steps by hand and SuperSu is working, i can make su in adb shell.
I can't write a guide right now, i have to go out of the house but this is done guys.

Vlasp said:

This or KingRoot will work for rooting this device now.

Click to expand...

Click to collapse

What do you mean? KingRoot says it failed booting with the boot-firestarter.img

jkchr1s said:

What do you mean? KingRoot says it failed booting with the boot-firestarter.img

Click to expand...

Click to collapse

yeah, sorry. only the tutorial will work.

Vlasp said:

yeah, sorry. only the tutorial will work.

Click to expand...

Click to collapse

Sorry, I'm not seeing a guide or tutorial on that link. That's a link to KingRoot.

Just for those of you that wanna root it just now:

Files needed and a boot.img to apply with fastboot boot boot.img:
https://www.dropbox.com/s/nurzm8q3pqx2v4z/root_fire.zip?dl=0

Unzip the attachment and push the files directory contents to /data/loca/tmp using adb
Example: adb push Superuser.apk /data/local/tmp/
adb push su /data/local/tmp/
...

and then do the follwing in adb shell:


mkdir /system/app/SuperSU
chmod 0755 /system/app/SuperSU
chcon ubject_r:system_file:s0 /system/app/SuperSU

cp /data/local/tmp/Superuser.apk /system/app/SuperSU/SuperSU.apk
chmod 0644 /system/app/SuperSU/SuperSU.apk
chcon ubject_r:system_file:s0 /system/app/SuperSU/SuperSU.apk

mkdir /system/bin/.ext
chmod 0755 /system/bin/.ext
chcon ubject_r:system_file:s0 /system/bin/.ext

cp /data/local/tmp/su /system/xbin/su
chmod 0755 /system/xbin/su
chcon ubject_r:system_file:s0 /system/xbin/su

cp /data/local/tmp/su /system/bin/.ext/.su
chmod 0755 /system/bin/.ext/.su
chcon ubject_r:system_file:s0 /system/bin/.ext/.su

cp /data/local/tmp/su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
chcon ubject_r:system_file:s0 /system/xbin/daemonsu

cp /data/local/tmp/su /system/xbin/sugote
chmod 0755 /system/xbin/sugote
chcon ubject_r:zygote_exec:s0 /system/xbin/sugote

cp /data/local/tmp/supolicy /system/xbin/supolicy
chmod 0755 /system/xbin/supolicy
chcon ubject_r:system_file:s0 /system/xbin/supolicy

cp /data/local/tmp/libsupol.so /system/lib/libsupol.so
chmod 0644 /system/lib/libsupol.so
chcon ubject_r:system_file:s0 /system/lib/libsupol.so

cp /system/bin/sh /system/xbin/sugote-mksh
chmod 0755 /system/xbin/sugote-mksh
chcon ubject_r:system_file:s0 /system/xbin/sugote-mksh

cp /system/bin/app_process32 /system/bin/app_process32_original
chmod 0755 /system/bin/app_process32_original
chcon ubject_r:zygote_exec:s0 /system/bin/app_process32_original

cp /system/bin/app_process32 /system/bin/app_process_init
chmod 0755 /system/bin/app_process_init
chcon ubject_r:system_file:s0 /system/bin/app_process_init

rm /system/bin/app_process
rm /system/bin/app_process32

ln -s /system/xbin/daemonsu /system/bin/app_process
ln -s /system/xbin/daemonsu /system/bin/app_process32

touch /system/etc/.installed_su_daemon
chmod 0644 /system/etc/.installed_su_daemon
chcon ubject_r:system_file:s0 /system/etc/.installed_su_daemon



Once all is done you need to fastboot boot boot.img again to establish proper perms to the new files. Actually we can't change ownership of files to root from adb.

Run this command in adb shell:
/system/xbin/su --install

Then reboot and voila! you are root.

Sorry for text format by chrome doesn't allow me to format it as code...

Awesomeslayerg said:

Dosent work?

Click to expand...

Click to collapse

@csolanol said it does...

Proof [emoji12]

Awesomeslayerg said:

chown 0.0 /system/app/SuperSU gives me operation not premitted

Click to expand...

Click to collapse

Yup, i edited the post to delete that line. That ownership change will be applied when you reboot from fastboot with the custom boot.img again. Note the end of the post.