[NEWBIE GUIDE] How to Unlock Bootloader/Root and install Addons FireStick 4k

[chinkster]

I don't understand how to open a terminal in the kamakiri directory

Sent from my ONEPLUS A5010 using Tapatalk

 

[chinkster]

I was checking the folder where kamakiri is to make sure it is read and write and it was read-only. I unchecked the box and applied settings but when I went to check again, it went back to read-only.

Sent from my ONEPLUS A5010 using Tapatalk

 

[itsyaboy]

I don't understand how to open a terminal in the kamakiri directory

Sent from my ONEPLUS A5010 using Tapatalk

I explained that already just type “cd” In the terminal (w/o the quotes) then drag and drop the ‘kamakiri’ folder into terminal, then hit enter in the terminal, it will change the directory, make sure u drop the kamakiri folder and not the kamakiri-mantis-v1

I was checking the folder where kamakiri is to make sure it is read and write and it was read-only. I unchecked the box and applied settings but when I went to check again, it went back to read-only.

Sent from my ONEPLUS A5010 using Tapatalk

Try to put it in File System/mnt

 

[brick00444]

I explained that already just type “cd” In the terminal (w/o the quotes) then drag and drop the ‘kamakiri’ folder into terminal, then hit enter in the terminal, it will change the directory, make sure u drop the kamakiri folder and not the kamakiri-mantis-v1

Another option : open the kamakiri folder and just right click in an open area and a submenu will popup then click on terminal in the submenu.

 

[chinkster]

I'm getting some kind of secure boot failure when I try to boot from the USB

Sent from my ONEPLUS A5010 using Tapatalk

---------- Post added at 08:49 AM ---------- Previous post was at 08:43 AM ----------

I explained that already just type “cd” In the terminal (w/o the quotes) then drag and drop the ‘kamakiri’ folder into terminal, then hit enter in the terminal, it will change the directory, make sure u drop the kamakiri folder and not the kamakiri-mantis-v1

Another option : open the kamakiri folder and just right click in an open area and a submenu will popup then click on terminal in the submenu.

When I right click I don't have any options for terminal in the submenu

Sent from my ONEPLUS A5010 using Tapatalk

---------- Post added at 09:05 AM ---------- Previous post was at 08:49 AM ----------

I explained that already just type “cd” In the terminal (w/o the quotes) then drag and drop the ‘kamakiri’ folder into terminal, then hit enter in the terminal, it will change the directory, make sure u drop the kamakiri folder and not the kamakiri-mantis-v1









Try to put it in File System/mnt

When I try to drag and drop the folder into terminal, it says kamakiri is not recognized as an internal or external command operable program or batch file

Sent from my ONEPLUS A5010 using Tapatalk

 

[itsyaboy]

I'm getting some kind of secure boot failure when I try to boot from the USB

Sent from my ONEPLUS A5010 using Tapatalk

---------- Post added at 08:49 AM ---------- Previous post was at 08:43 AM ----------



When I right click I don't have any options for terminal in the submenu

Sent from my ONEPLUS A5010 using Tapatalk

---------- Post added at 09:05 AM ---------- Previous post was at 08:49 AM ----------

When I try to drag and drop the folder into terminal, it says kamakiri is not recognized as an internal or external command operable program or batch file

Sent from my ONEPLUS A5010 using Tapatalk

You have to use the terminal that is in the bootable usb so u have to boot into it to do so, everything I explained is assuming u was able to boot in, if your having issues with that u’ll have to figure that out not sure why your having issues with that.

 

[chinkster]

Ok I got it to boot and was in the process but ran into an issue. It says twrp install terminate called after throwing instance of STD::bad_alloc

Sent from my ONEPLUS A5010 using Tapatalk

---------- Post added at 09:41 PM ---------- Previous post was at 08:49 PM ----------

So I have TWRP on the firestick now but I failed to push the mantis pre-rooted imaged due to std::bad_alloc. I thought it might be because I had a lot of apps installed, so I went back to firetv os, deleted all the apps and deregistered the device. Now I'm not sure what to do. I try to push the zip again but when I do adb devices in terminal, I don't see the firestick device.

Sent from my ONEPLUS A5010 using Tapatalk

 

[chinkster]

I managed to use fx file manager and sideload the mantis preroot zip into the firestick then boot into twrp and flash from twrp. Now I need to know how to get back into adb and disable the Amazon forced ota updater and the last step

Sent from my ONEPLUS A5010 using Tapatalk

 

[itsyaboy]

I managed to use fx file manager and sideload the mantis preroot zip into the firestick then boot into twrp and flash from twrp. Now I need to know how to get back into adb and disable the Amazon forced ota updater and the last step

Sent from my ONEPLUS A5010 using Tapatalk

Oh nice, does that method require doing the shorting? could u link me to that tut please, also let me know how if u figure out the ota thing as well, I think I had read some instructions on that but can’t find it / forgot what it said

 

[chinkster]

Oh nice, does that method require doing the shorting? could u link me to that tut please, also let me know how if u figure out the ota thing as well, I think I had read some instructions on that but can’t find it / forgot what it said

Yes you still have to do the shorting to unlock the bootloader to install twrp

Sent from my ONEPLUS A5010 using Tapatalk

 

[chinkster]

Got everything to work finally! Thanks devs and everyone that helped!

Sent from my ONEPLUS A5010 using Tapatalk

---------- Post added at 09:40 AM ---------- Previous post was at 09:37 AM ----------

Oh nice, does that method require doing the shorting? could u link me to that tut please, also let me know how if u figure out the ota thing as well, I think I had read some instructions on that but can’t find it / forgot what it said

It's not that hard to do the shorting. I just used a paperclip and held it steady with my left hand and plug in the power with my right hand. I tried aluminum foil but i think I had crappy foil

Sent from my ONEPLUS A5010 using Tapatalk

 

[itsyaboy]

I managed to use fx file manager and sideload the mantis preroot zip into the firestick then boot into twrp and flash from twrp. Now I need to know how to get back into adb and disable the Amazon forced ota updater and the last step

Sent from my ONEPLUS A5010 using Tapatalk

Got everything to work finally! Thanks devs and everyone that helped!

Sent from my ONEPLUS A5010 using Tapatalk

---------- Post added at 09:40 AM ---------- Previous post was at 09:37 AM ----------

It's not that hard to do the shorting. I just used a paperclip and held it steady with my left hand and plug in the power with my right hand. I tried aluminum foil but i think I had crappy foil

Sent from my ONEPLUS A5010 using Tapatalk

Lol ok kool, what about on how to disable the ota?

 

[RPM99]

To root or not

The statement below is from the Newbie guide on firestick 4k:

1. Does this mean that current prerooted version has issues?
2. What are the pro’s and con’s to flashing the current prerooted version?


UPDATE: Per Sus_i, this makes perfect sense:

"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."

Thanks for any clarification,
Steve

 

[Sus_i]

The statement below is from the Newbie guide on firestick 4k:

1. Does this mean that current prerooted version has issues?
2. What are the pro’s and con’s to flashing the current prerooted version?

Someone posted already a fix for the mentioned 'contact manufacturer error', you may search the prerooted thread...

Besides that I think that it's best to do this 'before' starting an unlock attempt:

UPDATE: Per Sus_i, this makes perfect sense:

"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip."

 

[RPM99]

Hello Sus_i and Thanks for the response

Someone posted already a fix for the mentioned 'contact manufacturer error', you may search the prerooted thread...

Besides that I think that it's best to do this 'before' starting an unlock attempt:

Hi,
I intend to do as you advise and update and unregister the stick before unlocking root.
I am still unclear what added benefit flashing a prerooted image gets you?


Thanks for the quick response,
Steve

 

[Sus_i]

Hi,
I intend to do as you advise and update and unregister the stick before unlocking root.
I am still unclear what added benefit flashing a prerooted image gets you?


Thanks for the quick response,
Steve

Why you want unregister the stick before doing the unlock?? That is unclear as it isn't required at all.

If your stick is already updated to the latest, there isn't a benefit, except addon.d support... in case you need this for whatever survivial scripts.

 

[RPM99]

Why you want unregister the stick before doing the unlock?? That is unclear as it isn't required at all.

If your stick is already updated to the latest, there isn't a benefit, except addon.d support... in case you need this for whatever survivial scripts.

Hi,

1. Do I need to unregister to avoid updates?
2. Is there an issue with current prerooted rom having an error screen?
3.What is the benefit of flashing a prerooted rom?
4. Is there a way to save an image of the current stock rom so that you can go back?
Thanks,
Steve

This is from another post on page 1 of this forum :
"Since the exploit can't be patched, it's in my opinion the best to do the setup at the beginning, pair the remote, then update to the latest over fireOS. That way you avoid a pending update nag setup screen after doing the exploit. Then enable ADB and unknown sources. After kamakiri I would flash only magisk.zip + sideload the manager app with adb... and avoid any prerooted rom flashing until there is an update to a somewhat higher version (and the current 6.2.6.8v1 has that contact manufacturer error screen)."


First very important, I wish I would have known this before but make sure you have a Laptop and a Monitor to Connect the FS to, so basically the USB Power cable from the FS connect it to your laptop and connect the HDMI portion to a monitor or TV
I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting

 

[Sus_i]

I also strongly recommend to have your FS deregistered before continuing as this will prevent your FS from automatically updating after rooting

Sorry, but deregistering the stick doesn't prevent anything.
Thats the reason I recommend doing the setup and all updates + enable adb... just infront of any unlock attempt.
If you mess the stick up, there isn't an easy way to recover back to stock, as it requires flashing some image files with hacked fastboot. Also unrecoverable hardware damages are possible.

Remember this, if you want to follow any guides:

You unlock your bootloader on your own risk. Nobody else takes any responsibility on your actions and any possible consequences. This will void your warranty. Only you are responsible for the outcome of any modification you do.

 

[RPM99]

Thank You

Sorry, but deregistering the stick doesn't prevent anything.
Thats the reason I recommend doing the setup and all updates + enable adb... just infront of any unlock attempt.
If you mess the stick up, there isn't an easy way to recover back to stock, as it requires flashing some image files with hacked fastboot. Also unrecoverable hardware damages are possible.

Remember this, if you want to follow any guides:

Thanks for being honest
I understand and I am working on a 2nd firestick.
Would still like to get your input why/whynot I would want to flash the prerooted rom.
Just what does that give me?

Thanks,
Steve

 

[Sus_i]

Would still like to get your input why/whynot I would want to flash the prerooted rom.
Just what does that give me?

Since it's recommended to disable the ota updater as soon the stick is rooted, you get an easy way to downgrade and/or update your stick anytime you want, without the need capturing OTA package links or files from big A.

For the older via 'supersu' rooted FireTV's and Sticks it's the only way to update the OS without losing root. This means the prerooted rom keeps root during an update (and all other stuff with propper survival scripts) thru addon.d support.

To answer your question.. If you want update to a somewhat higher version in the future, you can just grab a prerooted and flash it with twrp.
If you followed my suggestion and updated to the latest OS just before doing the unlock, there isn't a reason to flash it 'for now', i.e. doesn't make sense to flash an update twice