FireTV 2 (sloane) Recovery [v6] - 3.0.0-5

[rbox]

Hi @rbox,
I looked at 2ndinit at github and I have a question.
You are using some code from phh's SuperUser to disable SELinux of init, ueventd, recovery and the shell from recovery. My question is, can this code be applied to get a full SELinux Permissive at boot? Just wondering cause we are trying to boot custom ROM on it and well, locked bootloader has his limitations...
I was about to pick up a commit from ggow (netd binary that loads at boot from init.rc) that injects some code to netd to disable SELinux at boot but the commit is gone. Will your 2ndinit help to get a full permissive SELinux at boot? It can be a good option since it runs directly after mount the system (ext4_resize).
Cheers and sorry for the OT.

Possibly. You can try calling setenforce after you've disabled it for init.

 

[Rortiz2]

Possibly. You can try calling setenforce after you've disabled it for init.

Yep, I tought that. I will give it a try. Another question (sorry xD). I replaced lineages ext4_resize by yours one and same for pppd. There's no more files to replace? I mounted your unbrick img and I can see a few libs in lib64 and linker64. They need to be replaced too?
Cheers!

 

[rbox]

Yep, I tought that. I will give it a try. Another question (sorry xD). I replaced lineages ext4_resize by yours one and same for pppd. There's no more files to replace? I mounted your unbrick img and I can see a few libs in lib64 and linker64. They need to be replaced too?
Cheers!

Those should just be standard android stuff. The only things you should need are 2ndinitstub and 2ndinit.

 

[Rortiz2]

Those should just be standard android stuff. The only things you should need are 2ndinitstub and 2ndinit.

Yupp, thanks you
Finally got to work boot menu in Lineage. My issue was that I was using system/etc/recovery instead of system/recovery
Now going to play with the 2ndinit to try what you said before about setenforce:good:
Cheers!

 

[Rortiz2]

@rbox
Got working SELinux at boot
Thanks you very much. We have bootanimation now!
This is what I added:
(2ndinit.c)

set_permissive("shell", &policydb);

(2ndinitstub.c)

execl("system/bin/setenforce/", "permissive", NULL);

Cheers.

 

[smumar143]

Any one Pls help me rooting my fire TV 2, Ios 5.2.7.2

 

[Rortiz2]

Any one Pls help me rooting my fire TV 2, Ios 5.2.7.2

https://xdaforums.com/fire-tv/devel...i-rollback-t3986303/post80588511#post80588511
Regards.

 

[Rortiz2]

Hey all,

I'm facing a problem while wiping any partition in TWRP.
When I need to wipe data or cache I go (as usual) to the wipe option, I select them and I swipe to wipe.
The problem is, when I swipe, it stucks there with "Formatting cache/data using make_ext4fs..." (10 mins and more..)
Since it gets stuck on there, I tried running

killall recovery

(to "restart" TWRP as OP says) but that makes things worse as ADB stops working and the GUI freezes at the splash screen and I'm basically forced to unplug the power supply causing "damage" to the partitions I was wiping leaving them corrupted and in next boot seeing errors like "cannot mount /data" and so on...
As a "note", I'm able to wipe the partitions "manually" with adb shell using

make_ext4fs /dev/block/platform/mtk-msdc.0/by-name/partition_name

and that works just fine.
There's something I can do..? Or I just keep wiping the partitions manually with adb?

EDIT: Ignore all, fixed it.

Regards.

 

[wdcspurs]

Im searching for a way to remove twrp and go back fully stock. Im able to successfully download the latest OS OTA, but when it reboots to install it hits TWRP and then boots up into the launcher without installing. Ive tried the factory reset option. Still have TWRP. Any help appreciated.

 

[Bertonumber1]

Anyone know a way to get into twrp without using boot menu on 3.0.05 , I haven't got a keyboard that works and my mouse doesn't work on the usb port either so I always get kicked into system instead of recovery.

 

[Sus_i]

Anyone know a way to get into twrp without using boot menu on 3.0.05 , I haven't got a keyboard that works and my mouse doesn't work on the usb port either so I always get kicked into system instead of recovery.

Yes, you're able to switch the bootmenu without a keyboard but with adb.
Easiest way, extract the force_recovery.img file out of the sloane amonet/bin zip folder, push it to your sd and then dd it to cache, then reboot...
If you're done playing with TWRP, wipe cache, in order to switch the boot menu back to system.

 

[Bertonumber1]

Yes, you're able to switch the bootmenu without a keyboard but with adb.
Easiest way, extract the force_recovery.img file out of the sloane amonet/bin zip folder, push it to your sd and then dd it to cache, then reboot...
If you're done playing with TWRP, wipe cache, in order to switch the boot menu back to system.

Hi @Sus_i thanks again for replying,

So in theory could I be able to put the spare force_recovery.img I have on my pc to /sdcard and dd it to cache mate or does it have to come from flashed bin folder?

chmod 777 /cache/force_recovery.img

I think I know that not sure if it's correct

 

[Sus_i]

Hi @Sus_i thanks again for replying,

So in theory could I be able to put the spare force_recovery.img I have on my pc to /sdcard and dd it to cache mate or does it have to come from flashed bin folder

The force_recovery.img is an (almost empty) image file with only one file in it...
Can't remember in detail, but I think it was something like this: /cache/bootmenu_recovery
That file will switch the bootmenu to TWRP at every boot, as long the file is there.
You need to use the one from sloanes amonet... (via dd command to cache) or you can create the file by hand...
Both should work fine :good:

Edit: You can run something like this:

adb shell
su
dd if=/sdcard/force_recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/cache
exit
exit

 

[Bertonumber1]

The force_recovery.img is an (almost empty) image file with only one file in it...
Can't remember in detail, but I think it was something like this: /cache/bootmenu_recovery
That file will switch the bootmenu to TWRP at every boot, as long the file is there.
You need to use the one from sloanes amonet... (via dd command to cache) or you can create the file by hand...
Both should work fine :good:

Edit: You can run something like this:

@Sus_i thanks again my friend you're a diamond :good:

Updated Sloane to 5.2.7.1 r1 hopefully if its possible it will update USB driver, don't know why my keyboard/air mouse ain't showing up, shows up in twrp but not on boot menu screen.

Edit ## updated SU with 2.79 SR3 ZIP as it was old version, what's difference between flashing the supersu zip and magisk? Cos the supersu is already bound into ramdisk?

 

[Sus_i]

@Sus_i thanks again my friend you're a diamond :good:

Updated Sloane to 5.2.7.1 r1 hopefully if its possible it will update USB driver, don't know why my keyboard/air mouse ain't showing up, shows up in twrp but not on boot menu screen.

Edit ## updated SU with 2.79 SR3 ZIP as it was old version, what's difference between flashing the supersu zip and magisk? Cos the supersu is already bound into ramdisk?

No, there isn't any update for usb.
The mouse won't work at all at the 'bootmenu', most of the keyboard won't work too, except (or only) the two arrow keys (left/right) are working.
Maybe try pressing two times the 'left arrow' key, should do the trick.

You can update chainfires SuperSU, the latest version is SR5-SuperSU-v2.82-SR5-20171001224502.zip, grab it from here. It is normal that the SuperSU App won't open, it's somehow blocked by the fireOS. Just ignore the update messages...

Magisk won't work on the locked bootloader. Roger needs a new development box

 

[Bertonumber1]

No, there isn't any update for usb.
The mouse won't work at all at the 'bootmenu', most of the keyboard won't work too, except (or only) the two arrow keys (left/right) are working.
Maybe try pressing two times the 'left arrow' key, should do the trick.

You can update chainfires SuperSU, the latest version is SR5-SuperSU-v2.82-SR5-20171001224502.zip, grab it from here. It is normal that the SuperSU App won't open, it's somehow blocked by the fireOS. Just ignore the update messages...

Magisk won't work on the locked bootloader. Roger needs a new development box

Haha sound advice m8. Was wondering wtf was happening, been round everyone stealing their keyboards n mouse today and wondering if it was fire os needing update,

I can't even get any to work on Sloane once he boots up to homescreen, at least the sdcard is expandable eh?..

As for supersu yeah I noticed it didn't do anything when I flashed it. So I'll update to 2.82 and get rid of some bloat, job done.
Wouldnt mind magisk though would be better :good:

Cheers again Sus_i

 

[Sus_i]

I can't even get any to work on Sloane once he boots up to homescreen, at least the sdcard is expandable eh?..

Have you tried an usb stick or keyboard in fireOS? You have to disable usb debugging in order to use it...

 

[Bertonumber1]

Have you tried an usb stick or keyboard in fireOS? You have to disable usb debugging in order to use it...

Ah well @Sus_i everyday is a schoolday mate (except a saturday and sunday) :laugh: i neverr knew adb had to be switched off .
Will try it out shortly when i finish using keyboard on pi . :good:

Yeah it's working with USb debugging off

Ta much :good:

 

[ldeveraux]

Hey all,

I'm facing a problem while wiping any partition in TWRP.
When I need to wipe data or cache I go (as usual) to the wipe option, I select them and I swipe to wipe.
The problem is, when I swipe, it stucks there with "Formatting cache/data using make_ext4fs..." (10 mins and more..)
Since it gets stuck on there, I tried running

killall recovery

(to "restart" TWRP as OP says) but that makes things worse as ADB stops working and the GUI freezes at the splash screen and I'm basically forced to unplug the power supply causing "damage" to the partitions I was wiping leaving them corrupted and in next boot seeing errors like "cannot mount /data" and so on...
As a "note", I'm able to wipe the partitions "manually" with adb shell using

make_ext4fs /dev/block/platform/mtk-msdc.0/by-name/partition_name

and that works just fine.
There's something I can do..? Or I just keep wiping the partitions manually with adb?

EDIT: Ignore all, fixed it.

Regards.

How did you fix this? I tried upgrading my rom in twrp, wiped cache, and it hung. I foolishly rebooted and now it only boots to twrp and won't mount cache.

 

[Rortiz2]

How did you fix this? I tried upgrading my rom in twrp, wiped cache, and it hung. I foolishly rebooted and now it only boots to twrp and won't mount cache.

I don't really know, that was long time ago and now my box it's hard bricked.
I'd recommend you to manually format cache with make_ext4fs as the op says in the first post.
Regards.