yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] AnonVendetta:
I've always been aware that gsis are system image only, they don't aim to replace the vendor partition, and so they must use whatever vendor is on the device.

I'd like to get more into building, but my main issues are time, and lack of powerful enough hardware to do it. I'm at a point in life where money is tight, sooner or later I'd like to build a custom PC that is suitable for high end gaming and building. But that will come when it comes.
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] margee82:
Still no update ? Even if the Tab S7 is out of software updates ? Thanx
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] tqmatvey:
what do you mean by that?
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] margee82:
I mean, if someone started doing something like Custom rom ? Cause Tab S7 won't get updates anymore by manufacturer
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] tqmatvey:
noone afaik is working on custom ROMs, and noone cares if tab s7 will or will not get updates from manufacturer
[Samsung Galaxy Tab S7 / S7 Plus Questions & Answer] AnonVendetta:
The Tab S7 Plus will get security updates only, no major updates for stuff like OneUI. It already has stock Android 13, and that was the last major Android version we will get. It's what software devs call "EOL"/"end of life".

@margee82: You already know what your options are. Use stock ROM, or use custom GSI ROMs. Or roll your own ROM. It is what it is. It's still a perfectly usable and fast device, it should last a few more yrs. And I don't plan to upgrade until I have to, not until it starts having serious issues. It works really well for the things I do.
[Treble-Enabled Device Questions and Answers] Λαβιθήραν:
I cant find a GSI rom which supports my device.
[Treble-Enabled Device Questions and Answers] Λαβιθήραν:
I am trying to find a GSI ROM that works with my gadget, but I cannot find it, and I have no idea what an a and an ab portion are.
[Tilt, TyTN II, MDA Vario III General] Spin Dr Wolf:
I've recently upgraded to a Kaiser and i want to make the most of it and play with a few ROMs to find a nice fast one, maybe even find one to then customise with my favourite programs if i am feeling fruity. I've had a good sift through the amazing amount of information on here but i can't seem to find much in regards to copying the existing ROMS and SPL from my phone onto my PC as a backup/start point so i can restore it to where i started if i wish. I assume that this must be possible, if someone could please give me some help or point me in the right direction that would be great. I did have a look at the shipped ROMs list but mines not up on that list yet.

Also are there many major differences between WM6 and WM6.1, is it worth upgrading to the latter along the way ?
[Nokia Lumia 800] SzymonDevs:
Hi,

recently i found my dad's old Nokia Lumia 710 and i want to custom rom it. I searched like entire XDA, but every link to qualcomm bootloader is deleted.

If you have a nokia 710 qualcomm bootloader, please send it here.

Regards.
[Nokia Lumia 800] arsfr:
https://xdaforums.com/t/nokia-lumia-710-a-laymans-guide-to-install-custom-rom.2168413/

Try this.
[Nokia Lumia 800] SzymonDevs:
It says "The file link that you requested is not valid"
[Nokia Lumia 800] Crispymug:
I have the same issues

I need the files
[General Accessories] Guji:
can someone please provide info on pairing these two devices. I am trying to pair but have been unsuccessful.

Please help!
[General Accessories] knobbyhtccruise:
Hope this helps

Pairing using a Bluetooth passcode

1. Make sure that the mobile phone is switched on and the battery is

charged.

2. Switch on the Advanced Car Kit. For further information, see

"Switching the Advanced Car Kit on/off" on page 20.

3. Open the Bluetooth menu in the mobile phone and activate the

Bluetooth function.

4. Make the required settings on the mobile phone to activate a search

for Bluetooth devices within range. For further information on the

settings required on your mobile phone, see the relevant user’s guide.

5. Select Advanced Car Kit from the list of Bluetooth devices found.

6. When prompted, key in the Bluetooth passcode 0000.

7. The mobile phone has now been paired with the Advanced Car Kit

and is ready for operation.

P u t t i n g t h e A d v a n c e d C a r K i t i n t o s e r v i c e

18 Copyright © 2006 Nokia. All rights reserved.

Note: The Advanced Car Kit can only establish a Bluetooth

wireless connection to one compatible mobile phone.

Therefore, you may need to end or break an existing Bluetooth

wireless connection.

Automatic pairing with a compatible mobile phone

1. Make the appropriate settings in the mobile phone so that it will pair

with your Advanced Car Kit without requiring separate acceptance

or authorisation. For further information on the settings required on

your mobile phone, see the relevant user’s guide.

2. Switch on the Advanced Car Kit.

3. The Advanced Car Kit now starts an automatic 30-second search for

mobile phones that have previously been paired with it using the

Bluetooth passcode. The Advanced Car Kit pairs with the mobile

phone that it has last paired with. The active Bluetooth search is

indicated by the flashing light on the remote control button.
[General Accessories] RaptorRVL:
Search for the device, try to connect, enter 0000 as passcode.

That should do it. Though I also had some problems at first connecting to the carkit. But later it worked. Didn't do anything special.

See my topic about it here: http://xdaforums.com/showthread.php?t=434228
[Fire TV Original Android Development] Pro-me3us:
Temporary ADB root (PS7624/3337 or older)

View attachment 5944853

Standard Disclaimer: Use this at your own risk, I'm not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.

Instructions

Enable ADB debugging in FireOS settings

Download, unzip and copy raven_shrinker to your Cube

adb push raven_shrinker /data/local/tmp/

Give raven_shrinker execution permission (only needs to be done once)

adb shell
chmod +x /data/local/tmp/raven_shrinker

Run the program

For best results, run raven_shrinker 30-90sec after boot up, when loading is complete and the device is idle.

adb shell
/data/local/tmp/raven_shrinker
runcon u:r:system_app:s0 /system/bin/sh

How to disable package protection

Use raven_shrinker to open a root shell, runcon u:r:system_app:s0 /system/bin/sh and delete all the apps listed in the file /data/system/PackageManagerDenyList

/data/local/tmp/raven_shrinker
runcon u:r:system_app:s0 /system/bin/sh

echo '<?xml version="1.0" encoding="utf-8" standalone="yes" ?><map><set name="DenyListKeyPackages"></set></map>' > /data/system/PackageManagerDenyList

Clear Arcus Proxy, disable Arcus Proxy

pm clear com.fireos.arcus.proxy
pm disable-user com.fireos.arcus.proxy

Optional but strongly recommended, disable updates

pm disable-user com.amazon.device.software.ota
pm clear com.amazon.device.software.ota
pm disable-user com.amazon.device.software.ota.override
pm disable-user com.amazon.tv.forcedotaupdater.v2

A reboot is required before the protection removal changes take effect.

Verify that any apps you disabled actually are disabled.

pm list packages -d

Changelog:

v1.1 April 23th, 2023​

Fix for PS7608/3614

v1.2 May 4th, 2023​

added support for PS7206/1098

v1.3 June 23rd, 2023​

added support for PS7201/942

v1.4 August 27th, 2023​

added support for PS7229/1850

v1.5 May 31th, 2024​

added support for PS7212/1335
[Fire TV Original Android Development] Pro-me3us:
Bootless Magisk (PS7624/3337 or older)

These instructions use an adapted version of @diplomatic's bootless Magisk script, it's recommended you read the original post to better understand how it works, and it's limitations.

Disclaimer: Use this at your own risk, we're not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.

There are two reports of a possible compatibility issue with PS7614/3227, so we aren't recommending this method for that firmware at this time.

Instructions

Enable ADB debugging in FireOS settings

Download raven_bootless_magisk, unzip it, and copy it to your Cube keeping the same directory structure

adb shell mkdir /data/local/tmp/bin
adb push raven_bootless_magisk/* /data/local/tmp/
adb shell pm install -r /data/local/tmp/magisk_manager.apk

Give scripts & binaries execution permissions

adb shell
chmod +x /data/local/tmp/start.sh
chmod +x /data/local/tmp/magisk-boot.sh
chmod +x /data/local/tmp/bin/raven_shrinker
chmod +x /data/local/tmp/bin/magiskinit

Install Launcher Manager on your Cube, open, navigate to 'other settings', 'ADB Commands'

Tap on the + icon in the top right corner to create a new command

Enter Name: Start Magisk

Enter Command: sleep 30 && /data/local/tmp/start.sh

Check 'Execute on Boot'

Save

View attachment 5886051	View attachment 5886053	View attachment 5886055

When you reboot your Cube, bootless Magisk will automatically start ~30sec after your homescreen loads. It's important that FireOS has loaded and that the device isn't busy, so don't open any apps until after Magisk has loaded. There's a greater chance that raven_shrinker will fail or reboot the Cube while launching Magisk if the device is busy.

TO AVOID BRICKING YOUR DEVICE:

Be careful of what apps you give root access to. Giving root access to an app that modifies the boot, system or vendor partitions will brick your device. DM-verity is still actively checking that system/vendor directories haven't been tampered with.

Don't run the boot-magisk.sh script (from either ADB or Launcher Manager) more than once per boot. Doing so will mess up the mounting and module initiation.

Never toggle ADB debugging off/on in the Developer's menu while Magisk is running. This will kill the Magisk daemon running in the background, and could corrupt your device if it's in the middle of an important process.

Only use WiFi ADB, not USB ADB. Booting the Cube with an USB attached computer puts USB in device mode, and ADB will close and kill Magisk when the Cube sleeps in device mode.

This release includes Magisk v21.4 (magiskinit) and Magisk Manager v8.0.7. Don't update Magisk! Patching your boot image will brick your device!

Changelog:

v1.1 April 23th, 2023​

Fix for PS7608/3614

v1.2 May 4th, 2023​

Added support for PS7206/1098

v1.3 June 23rd, 2023​

Added support for PS7201/942
[Fire TV Original Android Development] Pro-me3us:
Bootloader unlock, install TWRP & Magisk (PS7292/2984 or older)

This rooting method will put your Cube on the same exploit and software versions used in the original Raven Root, without a DFU recovery option. Please post any questions or problems regarding this post & it's process, on the Raven Root thread.

Disclaimer: Use this at your own risk, I'm not responsible for any data loss or corruption to your device. There is a nonzero chance of bricking the Cube, and little to no recovery options.

NEVER FACTORY RESET YOUR CUBE!!!

NEVER ALLOW AN AMAZON OTA UPDATE!!!

Both of these will brick your Cube!

To avoid any potential conflicts, if you were previously using a different version of Magisk, such as bootless Magisk (v21.4), first delete /data/adb/magisk.db before proceeding.

Instructions

Enable ADB debugging in FireOS settings

Download the raven_root_shrinker, unzip, and copy the 7 files to /data/local/tmp on the Cube

adb push raven_root_shrinker/* /data/local/tmp/

Give raven_shrinker & install script executable permissions

adb shell
chmod +x /data/local/tmp/raven_shrinker
chmod +x /data/local/tmp/install_root.sh

Open a root shell and run the install_root.sh script

adb shell
/data/local/tmp/raven_shrinker
/data/local/tmp/install_root.sh

Finish by typing 'exit' to switch root back to regular shell, install Magisk Manager, and reboot to TWRP

exit
pm install -r /data/local/tmp/magisk.apk
reboot recovery

The Cube will reboot to TWRP, automatically flash Magisk and Amazon OTA blocker module, then reboot back to FireOS.

NOTE: It's very important to NEVER allow the Amazon OTA app to update the firmware. NEVER run the factory reset option in FireOS settings. If either of these occur, the Cube will be bricked.

Read here for TWRP firmware flashing instructions

Changelog:

v2.2.1 April 23th, 2023​

Added additional Magisk script to help prevent user from accidentally initiating FireOS factory reset.

If you already installed v2.2, you can copy and paste the following as one ADB command to add this script to your Cube:

echo '#!/sbin/sh
# Rename misc partition
mv /dev/block/misc /dev/block/misc_real
# Create symbolic links
ln -s /dev/null /dev/block/misc' > /data/adb/post-fs-data.d/misc_hide.sh && chmod +x /data/adb/post-fs-data.d/misc_hide.sh

v2.2.2 May 4th, 2023​

Added support for PS7206/1098

v2.2.3 June 23rd, 2023​

Added support for PS7201/942
[Fire TV Original Android Development] Pro-me3us:
Resources

- How to skip forced update during new device setup / following factory reset

How to block updates with a DNS block, entered during WiFi password setup​

- TWRP firmware flashing instructions, requires unlocked bootloader

- Firmware links (XDA)

- FIrmware, Apps & Souce Code links (Github)

- Set a custom launcher with Launcher Manager

Wolf Launcher​

Flauncher​

LeanBack on Fire​

Projectivy Launcher​

Emotn​

​

- Better way to disable Amazon homescreen

- Remap remote app buttons

USB bootable OS (unlocked bootloader required)

CoreELEC: Kodi OS with support for TrueHD/DTS-MA, 8k@30 fps

EmuELEC: Retro gaming emulation station

Root Version History

May 15th, 2022

[UNLOCK][ROOT][TWRP][UNBRICK] ≤ PS7242/3516

Install TWRP, Magisk & full root

Full recovery from any brick

* Requires HDMI dongle & Linux to install

April 8th, 2023

[UNLOCK][ROOT][TWRP] ≤ PS7292/2984

Install TWRP, Magisk & full root

Unbricking options are more limited

DFU eFuse is preserved if installed on ≥ PS7242/3616

HDMI dongle can be used for Full unbrick options

[Temp ROOT] ≤ PS7624/3337

Spawn temporary root shell, gone after a reboot

Run a single file directly on the Cube to gain ADB root

Remove app protections

enable/disable any app even without root

use custom launcher

block OTA updates

disable Amazon AppBlockList

backup & restore app data

access all files and folders, and more...

[BOOTLESS MAGISK] ≤ PS7624/3337

Lite version of Magisk to grant root to any apps, and use su in ADB.

Limited, most Magisk modules don't work

* No HDMI dongle needed. Requires ADB run from Windows, Mac, Linux or Android to install, your choice.

June 16th, 2023

[Temp ROOT ] ≤ PS7646/3565

Same as temp root from April 8th, 2023 using new GPU exploit
[Fire TV Original Android Development] errut:
to bad: mine was already on PS7633/3445
[Fire TV Original Android Development] coltxL2717:
Hey @Pro-me3us . I've been trying to use the 2.2 update with no luck. My cube is on version PS7292/2984. I keep getting the message "/data/local/tmp/raven_shrinker: can't execute: Permission denied." Not sure what I'm doing wrong. Any help would be greatly appreciated.
[Fire TV Original Android Development] Pro-me3us:
I didn't need to change the permissions on raven_shrinker while testing, but maybe that's different on other firmware versions.

Try this:

chmod +x /data/local/tmp/raven_shrinker

This will give the file execution permission. Let me know if that works, then I'll add it to the instructions. You only need to do this once for that file.

You may also need to do the same for install_root.sh in that case. Try running it first without, and if needed use:

chmod +x /data/local/tmp/install_root.sh
[Fire TV Original Android Development] coltxL2717:
That did it. Thank you so much. I had to chmod both files for the root to work.
[Fire TV Original Android Development] Pro-me3us:
Thanks for confirming, added granting executable permissions to the instructions
[Fire TV Original Android Development] errut:
How to block future updates?
[Fire TV Original Android Development] Michajin:
Post #2 (needs root). unless you are on PS7633/3445 +, then you have to do it on a network router blocking the OTA webwites.
[Fire TV Original Android Development] teschke:
Good afternoon . I would like to clarify whether it is possible to install TWRP on my Cube?

View attachment 5889057
[Fire TV Original Android Development] Pro-me3us:
Yes, your firmware is older than PS7292 so you can use these instructions

This will install TWRP 3.7.0-9.0 + Magisk 25.208.
[Fire TV Original Android Development] u_no_fr:
Hi all,

where can I DL "The exploit program (raven_shrinker") ?
[Fire TV Original Android Development] Pro-me3us:
It's part of each of the three methods listed in the OP

1) Temporary root (raven_shrinker only)

2) bootless Magisk

3) bootloader unlock

Check the post attachments
[Fire TV Original Android Development] Osaka_23:
Hi,

Thanks for posting this.

I have two Gen 2 Cubes that are on Fire OS 7.2.4.2 (PS7242/2906). Both have updates blocked.

If I installed TWRP and Magisk, what can I do? Are there and roms you recommend I install?

Sorry for asking. I have installed roms on old Samsung and LG phones but never done anything like this on Fire TV products.

Thanks
[Fire TV Original Android Development] Pro-me3us:
There aren't any custom ROMs for the Cube at the moment. TWRP would let you update to PS7624/3337 while maintaining root, but honestly I don't see a whole lot of benefit to the post PS7273 firmware. There are a handful of small new features, nothing particularly great IMO.

Magisk might actually have more of a functional benefit for you. With that you can grant apps root, and use modules. Exposed Edge is very nice, and will let you completely remap your remote buttons, including double and tripple clicks, overlays, shortcuts, etc. You can change the bootup logo, use file explorers with full system access etc. TWRP/Magisk are just the tools, what you do with them is up to you ;)
[Fire TV Original Android Development] yakovperelman69:
Hello Pro-me3us, my cube is running PS7633/3445. I followed the instructions #2 to Temporary ADB root (PS7624/3337 or older)

I was able to push the file (or i had to push the folder???)

Well, then after

raven:/ $ /data/local/tmp/raven_shrinker

fingerprint: Amazon/raven/raven:9/PS7633.3445N/0027347744000:user/amz-p,release-keys

/data/local/tmp/raven_shrinker: flags_change failed

: Invalid argument

what can i do now?

any help ?

thanks

Note: the file was pushed because:

1|raven:/ $ cd /data/local/tmp/

127|raven:/data/local/tmp $ ls

raven_shrinker
[Fire TV Original Android Development] Pro-me3us:
The vulnerability was patched in PS7633/3445, so it won't work on any firmware newer than PS7624/3337. There's no workaround.
[Fire TV Original Android Development] Pro-me3us:
Ok, the Adep app must not have been added to FireOS until PS7624, so don't worry about that one. You are all set.

Yeah, you can use any app to disable or block apps that you want.

TIP: Many 'TDUK tools' are just SweenWolf's apps + ads. Get the originals here without any trackers or banners.
[Fire TV Original Android Development] SpranklesXDA:
i should clarify that error was on a cube on older 7.2.2 something( with the old UI)

maybe something to do with TDUK blockers ?

no errors on the 7.6.1.4 and wolf laucher works by default

thanks for everything and i will be doing bootloader unlock on the Old cube and hopefully the next 4 i open are 7.2.9.2 lol
[Fire TV Original Android Development] SpranklesXDA:
thanks alot for everything. thanks for the TDUK tip i always see SeenWolf lol
[Fire TV Original Android Development] Pro-me3us:
Oh ok, in that case Adep was added somewhere between PS7273 and PS7614.

Did you buy a bunch of Cubes from the last Woot sale? It seemed like most of those came with PS7292.

The bootloader unlock is easier, and the temp root instructions aren't really necessary for Cubes running through the bootloader unlock script. Just mind the warning to never run a FireOS factory reset, or allow an Amazon OTA update.

Ask for help if there are any issues, rather than risk digging yourself deeper. There are a few safe guards implemented to allow you to fix most problems.
[Fire TV Original Android Development] SpranklesXDA:
Yep the $40 woot deal . I was ditching All My firesticks when they pulled stock on Amazon and dropped the Gen 3 . I knew they were going to dump old 2 gen stock eventually and got lucky I seen it drop on woot. Like the Gen 3 ( and still debating if I should go ahead and purchase now for firmware exploit but kinda disappointed it's the same 2gb/16gb instead of 4gb/32gb . A little steep on the price lol.

Yeah I have been reading this thread for months and fully aware to never do factory reset after bootloader unlock. I will post back in week or two when I get to other cube's and let you know what firmware. So far everything was new and had the plastic wrap around the cube BUT inside that was a plastic wrapper on the back that had the HDMI,micro USB and power slots poked open almost like they mass upgrade all of them/ or tested them all out. I don't really believe they were refurbished since Amazon was sitting on brand new stock when the 3rd gen dropped. Kinda odd but just my opinion ( they updated them to block custom launcher ) . Thanks!
[Fire TV Original Android Development] Pro-me3us:
My hunch is that Amazon replaces the outside shells during the refurbishment process. You can get a very rough feeling of how used the device is by looking at the boot count (raven:/ # idme print bootcount - run as root ), it's not reset during refurbishment. I got one of those Woot Cubes and it had a few dozen boots on it.

Cubes don't sell in high volume, so stock is slow to change. I'd bet if you wait until Black Friday to get a 3rd gen Cube, you won't get one that ships with post PS7646/3550 firmware.
[Fire TV Original Android Development] p0werpl:
Will this exploit work on this device? The GPU is Mali so it should, although the SOC is Mediatek, not Amlogic.

The Fire OS is 7.2.4.0.
[Fire TV Original Android Development] Pro-me3us:
The exploit itself should work on that TV, but not the raven or gazelle versions here. Getting the exploit to work on any device requires modifying the original Pixel6 POC to work with the security layer of the target device's kernel.

Unfortunately, that's not a straightforward process.

Since your TV is still on pre PS7273 FireOS, you have most of the main benefits of temp root already, custom launcher use and no protected packages.
[Fire TV Original Android Development] votkalivirgul:
Hi Pro-me3us,

Thank you for your effort. I did Bootless Magisk for root and update PS7624. I wanting to use NowTV but its detect root, I tried Magisk module for hiding did't success, cannot bypass.

I'm looking for a way to temp unroot for to use Nowtv. How can I do that?
[Fire TV Original Android Development] Pro-me3us:
Avoiding root detection is a cat and mouse game, there are a lot of methods used by apps to detect root. This thread suggests that NowTV detects MagiskManager (MM) app itself, even if the device is not rooted. And changing the MM package name doesn't help. At one time disabling MM was enough to pass the NowTV root check.

I don't know of a good option in this case. Because there is no recovery menu for FireTV, no TWRP or DFU, I don't want to suggest trying anything that might lead to a bricked Cube. And I don't have a NowTV account to do any testing myself. Bootless Magisk is a creation of this thread, you can check there for root detection avoidance possibilities.

Are you using Magisk regularly? Maybe regular temp root would be enough?
[Fire TV Original Android Development] votkalivirgul:
I don't use Magisk all the time. temp root is enough for me. How do I convert from "Bootless Magisk" to temp root? if I do temp root, can I switch back to bootless magisk in the future?