[root][confirmed][5.1.1]

Search This thread
By:
Advanced…
K

k4y0z

Senior Member
Nov 27, 2015
1,468
2,055
CONFIRMED
I've looked a bit arround how we could achieve root on the fire without TWRP.
I don't have 5.1.1 installed, but I'm hoping the following is still possible.
(I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)
If someone could test this please:

Confirmed, working:
- Enable ADB-Debugging in Developer Settings, then:
Code: 
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell

You should now hopefully have a shell with root-priviledges:
Code: 
root@ford:/ #

Please test and report back.

To Flash SuperSU and make root persistent (thx @pappasmurfsharem):
https://www.androidfilehost.com/?w=files&flid=42700

If you are still inside "adb shell" from the last command above type "exit" first.
Or just skip the "adb shell" command above.

Code: 
adb remount
adb push files\libsupol.so /data/local/tmp/
adb push files\root_fire.sh /data/local/tmp/
adb push files\su /data/local/tmp/
adb push files\Superuser.apk /data/local/tmp/
adb push files\supolicy /data/local/tmp/
adb shell chmod 777 /data/local/tmp/root_fire.sh
adb shell /data/local/tmp/root_fire.sh
# This Part reopened fastboot and I just re-ran the cmds from the first post in this thread #

fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue

adb wait-for-device && adb remount
adb shell /system/xbin/su --install
adb reboot
 
Last edited:
  • Like
Reactions: ipdev, danrf, mongoosesRawesome and 43 others
C

cococo42

New member
Sep 22, 2009
1
0
It works, in fact I've used it to remove a couple of apks from Amazon on 5.1.1 but... I can't see firelauncher, for example.
 
blueberry.sky

blueberry.sky

Senior Member
Aug 20, 2014
455
168
Huge thanks k4y0z!
I have another Fire due to arrive tomorrow, will definitely try it if I get 5.1.1.
Could you give the commands for restoring the old bootloader? Or would we use FlashFire? I presume there is a risk of hard brick. Flashing the bootloader would include the preloader & amazon recovery? I see there is a Boot & a Recovery partition.
 
Last edited:
O

onqq

Member
Jan 16, 2015
9
0
Thanks, it is working on my fire 5.1.1.

now just need to figure out how load TWRP on here
 
K

k4y0z

Senior Member
Nov 27, 2015
1,468
2,055
cococo42 said:
It works, in fact I've used it to remove a couple of apks from Amazon on 5.1.1 but... I can't see firelauncher, for example.
Click to expand...
Click to collapse
Thanks for the feedback

blueberry.sky said:
Huge thanks k4y0z!
I have another Fire due to arrive tomorrow, will definitely try it if I get 5.1.1.
Could you give the commands for restoring the old bootloader? Or would we use FlashFire? I presume there is a risk of hard brick. Flashing the bootloader would include the preloader & amazon recovery? I see there is a Boot & a Recovery partition.
Click to expand...
Click to collapse
I have never used FlashFire.
I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.
You are correct, the following could potentially WILL brick your Fire, do at your own risk!
Code: 
adb push lk.bin /data/local/tmp/
adb push preloader_prod.img /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb shell "dd if=/data/local/tmp/preloader_prod.img of=/dev/block/platform/mtk-msdc.0/mmcblk0boot0"
adb reboot-bootloader
Now fastboot boot should hopefully work again.

Please test and report back!
 

Attachments

  • lk.zip
    223.4 KB · Views: 553
  • preloader_prod.zip
    74 KB · Views: 967
Last edited:
  • Like
Reactions: 4826estilo and blueberry.sky
J

jbraney

Member
Dec 30, 2014
49
10
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...

I just have a lack of android coding experience, but if you tell me, I'll understand very quickly... :p
 
Harry44

Harry44

Senior Member
Jul 14, 2010
449
379
TX, USA
jbraney said:
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...

I just have a lack of android coding experience, but if you tell me, I'll understand very quickly... :p
Click to expand...
Click to collapse

You don't need android studio to do any of this. Do you have ADB and fastboot installed? If you need help PM me.
 
  • Like
Reactions: kitcostantino and k4y0z
K

k4y0z

Senior Member
Nov 27, 2015
1,468
2,055
jbraney said:
Total noob question, I know... I haven't used Android Studio before, but am definitely a computer guy... Very simply, can you show me how to just run a straight up terminal to type these commands without creating a new "app"...

I just have a lack of android coding experience, but if you tell me, I'll understand very quickly... :p
Click to expand...
Click to collapse

You don't need Android Studio, you just need adb and fastboot, your best bet is to search this forum for these two.
 
  • Like
Reactions: tuckerwagner
L

lordpit

Member
Dec 16, 2015
11
0
Installed supersu on 5.1.1 ... works perfect ! THX VERY MUCH!!
 

Attachments

  • 2015-12-16_21h12_13.png
    2015-12-16_21h12_13.png
    66.3 KB · Views: 1,700
M

maratd

Member
Mar 6, 2011
40
12
k4y0z said:
Thanks for the feedback


I have never used FlashFire.
I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.
You are correct, the following could potentially brick your Fire, do at your own risk!
I have the old fastboot attatched to this post to flash it:
Code: 
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
Now fastboot boot should hopefully work again.

Please test and report back!
Click to expand...
Click to collapse

This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:

Code: 
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
 
  • Like
Reactions: codepilot, auggiej, hammer-is and 3 others
K

k4y0z

Senior Member
Nov 27, 2015
1,468
2,055
maratd said:
This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:

Code: 
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
Click to expand...
Click to collapse

Damn can you still get into fastboot with VOL-DOWN + Power?

Maybe we also have to flash the older preloader
 
blueberry.sky

blueberry.sky

Senior Member
Aug 20, 2014
455
168
jbraney said:
Does this mean that the bootloader is unlocked? With root we can now flash CM12.1 and GAPPS?
Click to expand...
Click to collapse
Bootloader is still locked. But if we can downgrade to the 5.0.1 fastboot bootloader then we can return to flashing CM12.1, SlimLP, gapps as we did before (temporarily loading twrp into memory then flashing rom).
 
K

klsystem1

Senior Member
Oct 1, 2014
110
5
Linz
k4y0z said:
CONFIRMED
I've looked a bit arround how we could achieve root on the fire without TWRP.
I don't have 5.1.1 installed, but I'm hoping the following is still possible.
(I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)
If someone could test this please:

- Enable ADB-Debugging in Developer Settings, then:
Code: 
adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell

You should now hopefully have a shell with root-priviledges:
Code: 
root@ford:/ #

Please test and report back.

If it works we can probably restore the old bootloader with "fastboot boot" support. :)
Click to expand...
Click to collapse

Is this all I habe to do, getting into the root shell or are there any more things to do for a root in my 5.1.1?
Thanks
 
You must log in or register to reply here.

Similar threads

csolanol
[ROM] SlimLP 5.1.1 for Amazon Fire 2015 (DISCONTINUED)
Replies
1K
Views
255K
T
TheJaHa5
ggow
  • Locked
[discontinued][ROM][unlocked][ford,austin] Fire Nexus ROM [26 MAY 2019]
Replies
3K
Views
584K
L
luc_luke
ggow
  • Locked
[discontinued][ROM][unlocked][ford,austin] Lineage-12.1 [05 MAY 2020]
Replies
2K
Views
290K
C
castone123
ggow
[ROM][unlocked][ford,austin] Lineage-14.1 [21 JUN 2023]
Replies
978
Views
233K
S
Shanye
ggow
  • Locked
[discontinued][ROM][unlocked][mustang] Lineage-14.1 [27 AUG 2019]
Replies
680
Views
113K
Macusercom
Macusercom

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 46
    K
    k4y0z
    CONFIRMED
    I've looked a bit arround how we could achieve root on the fire without TWRP.
    I don't have 5.1.1 installed, but I'm hoping the following is still possible.
    (I tested it on a brand-new fire, that never came in touch with TWRP or a custom rom)
    If someone could test this please:

    Confirmed, working:
    - Enable ADB-Debugging in Developer Settings, then:
    Code: 
    adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell

    You should now hopefully have a shell with root-priviledges:
    Code: 
    root@ford:/ #

    Please test and report back.

    To Flash SuperSU and make root persistent (thx @pappasmurfsharem):
    https://www.androidfilehost.com/?w=files&flid=42700

    If you are still inside "adb shell" from the last command above type "exit" first.
    Or just skip the "adb shell" command above.

    Code: 
    adb remount
adb push files\libsupol.so /data/local/tmp/
adb push files\root_fire.sh /data/local/tmp/
adb push files\su /data/local/tmp/
adb push files\Superuser.apk /data/local/tmp/
adb push files\supolicy /data/local/tmp/
adb shell chmod 777 /data/local/tmp/root_fire.sh
adb shell /data/local/tmp/root_fire.sh
# This Part reopened fastboot and I just re-ran the cmds from the first post in this thread #

fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue

adb wait-for-device && adb remount
adb shell /system/xbin/su --install
adb reboot
    View
    10
    B
    bmurphr1
    blueberry.sky said:
    Yes, we do need someone to test flashing the preloader+fastboot. That code is correct.

    Here are quotes from the two people who tried flashing the bootloader ("lk") only, maratd & kleydejong. You can see that they did not flash the preloader.
    Click to expand...
    Click to collapse

    Looks like I'm batting next as to flashing the preloader and fastboot together as mentioned in my code? I know this is a one in a million shot and I'm about to sacrifice my tablet to the Amazon Gods but IDGAF since I have another one coming Sunday via Amazon Prime's quick replacement service.

    EDIT: I'm about to flash the preloader and fastboot together in one go...wish me luck.

    ---------- Post added at 07:20 AM ---------- Previous post was at 07:01 AM ----------

    It's a no go flashing the preloader and fastboot...it bricked my device for good. The output said that both operations were successful, but after doing the bootloader-reboot my tablet went dead and is now bricked.

    I hope this helps out anybody who's thinking that flashing both will give us the ability to launch TWRP. I don't mind donating this tablet to the Amazon Gods since my replacement arrives on Sunday, so that's why I went ahead and tried the flash mentioned earlier...I figured that was the closest we could get to be able to un-neuter fastboot and allow TWRP to be executed.
    View
    7
    Tomsgt
    Tomsgt
    DoLooper said:
    Yep. :D Will be a day or two.

    For rooted stock:

    - Install custom launcher
    - Disable Fire launcher
    - scripts to switch between custom and Fire launchers
    (run from shortcut on launcher home screen)

    - Move custom launcher to system/priv-apps (for widgets)

    - Disable OTA

    Not sure about doing an su install script since right now it relies on sh scripts written by someone else.
    Click to expand...
    Click to collapse

    http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
    enjoy
    View
    6
    M
    maratd
    k4y0z said:
    Thanks for the feedback


    I have never used FlashFire.
    I believe it should be enough to flash the old fastboot, though I'm unsure about the preloader.
    You are correct, the following could potentially brick your Fire, do at your own risk!
    I have the old fastboot attatched to this post to flash it:
    Code: 
    adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
    Now fastboot boot should hopefully work again.

    Please test and report back!
    Click to expand...
    Click to collapse

    This bricked my fire on 5.1.1 ... do not do this! Here is what I did to brick it:

    Code: 
    adb reboot-bootloader
fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb push lk.bin /data/local/tmp/
adb shell "dd if=/data/local/tmp/lk.bin of=/dev/block/platform/mtk-msdc.0/by-name/UBOOT"
adb reboot-bootloader
    View
    6
    P
    pappasmurfsharem
    flyapart said:
    Great! Noob question warning -- I can get the root prompt but can't seem to install SuperSU. Can you tell us what commands you used from the terminal to do this? Also which file you used to install it (apk vs zip) and where they need to be placed? Thanks!!!
    Click to expand...
    Click to collapse

    I just opened the root.bat from the other method in the 5.0.1 page and pasted the cmds manually in a cmd prompt

    seems to have worked as I can use a terminal emulator and enter 'su' and get Superuser prompt

    I believe it is/was more or less this

    You will need the root_fire.zip from the other thread, and then open a command window in the folder where you extract those files.

    adb reboot-bootloader
    fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
    fastboot continue
    adb wait-for-device && adb remount
    adb push files\libsupol.so /data/local/tmp/
    adb push files\root_fire.sh /data/local/tmp/
    adb push files\su /data/local/tmp/
    adb push files\Superuser.apk /data/local/tmp/
    adb push files\supolicy /data/local/tmp/
    adb shell chmod 777 /data/local/tmp/root_fire.sh
    adb shell /data/local/tmp/root_fire.sh
    # This Part reopened fastboot and I just re-ran the cmds from the first post in this thread #

    fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
    fastboot continue

    # after device reboots and you see it with 'adb devices' #

    adb remount
    adb shell /system/xbin/su --install
    adb reboot
    Click to expand...
    Click to collapse
    View

New posts