yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] funem:
You can do it. I went from WM6 to WM6.1 and used a backup I did from 6 to restore everything to 6.1.

The only tip I can give you is this.

Do not restore anything in the file system data unless its non application stuff you put there, pictures, skins, browser favourites etc.

My phone works fine I have all my old contacts, mails and pim entries from my old rom. I just re-installed my apps that were on my phone, not my storage card. Anything that runs when the phone is switched on I always install to the phone. I even restored my start menu and found that most of the games and apps I installed to the memory card run fine, they just sometimes require you to re-enter the registration details the first time you run them after restoring.

You are restoring data not programs so it should be fine.
[Tilt, TyTN II, MDA Vario III General] jdmspecdc5:
i disabled sms threading in kaisertweak. tried to do restore using sprite again and all my sms messages show up but now i have a text message saying "account locked. company policy prohibits use of text messaging on this device. you ocannot send or recieve text messags."

also when the restore was done i got an error about sddeamon.exe
[Tilt, TyTN II, MDA Vario III General] kdwhit:
Thanks funem but when how do you specify which files to restore? When I start it makes sure I want to restore "everything." Also, I have the 10-day trial of the newest sprite but when i try and restore it says the program must be authorized to run. I emailed tech support because the trial says that it should be fully functional throughout the trial period. although its only a $10 upgrade, a free trial run just to get my text's back was all I was looking for.
[Tilt, TyTN II, MDA Vario III General] funem:
When you start a restore it should take you to a tree view of the data backed up with checkboxes next to each available branch, just remove the ticks from the boxes where you dont want to restore data.
[Tilt, TyTN II, MDA Vario III General] ilordvader:
Can anyone tell me a List of things we need to install

after we have windows 6.1 on the Tilt

Like:

Adv config

Camera cab

KaiserTweak cab

do we still need all these or ........
[Tilt, TyTN II, MDA Vario III General] rbastedo:
Using Sprite Backup 1st time:

Here's another "Can anyone tell me?" question:

How long should it take Sprite Backup to run on it's first time?

I went to the program, clicked Backup, it did a reset and came up to the

Windows

Mobile

Version 6.1

screen and has been there for a long time.

How long does it take? Is it hung, or is it working?

Thanks!

EDIT:

I waited a long time, then did a soft reset and it came back and ran properly and reset.

All good, thanks anyway.
[Tilt, TyTN II, MDA Vario III General] babyface215:
How come Sprite backup makes dual copies

of your menu items? After I had restored my Tilt using Sprite and I went to my Menu settings after it was complete..I had duplicate items....and I couldn't uncheck anything?? Calendar, Messages, WMP, ...etc ..etc..
[Tilt, TyTN II, MDA Vario III General] Kepela523:
I have this same problem. can anyone please explain why? and what can i do to fix it without re installing everything.

thanks
[Samsung Galaxy Note 9 Questions & Answers] Exynos985:
I Recently brought a Galaxy Note 9 off Amazon in the UK. As it turns out the phone is a USA Variant and contains the Qualcomm Snapdragon 845 Chipset and the model number is linked to the USA Variant. Ever since i have had mobile data issues on the phone where it will not enable or i get no signal. I have tried resetting the network settings, restarting the phone, manually choosing the operator etc and still no luck. And when it was display LTE Or 4G It would not load any google pages. Any help would be appreciated
[General Questions and Answers] dfg555:
Basically when you reformat your microSD Card via Windows/Android a new Volume Serial Number/VSN gets assigned to it which Android uses as the "Directory Path" eg. /storage/XXXX-XXXX/.

When I reformatted my microSD it changed its' VSN which causes certain Apps to behave differently as the "Directory" has changed. I've tried changing the microSD's VSN via Windows using CMD "volumeid" and a program called "Volume Serial Number Editor" which both caused my Phone to recognize the microSD as "Corrupted". Either there's another "Serial Number" that gets changed during this process or Android has some sort of "Link" to the original VSN prior to reformatting which causes that "Link" to break regardless if you put in the same VSN.

Galaxy S7

Android v7.0

Magisk v20

TWRP v3.4.0.0

Xposed v89

No Encryption

View attachment 5169413
[Google Pixel 4a Questions & Answers] DFurax:
Hi,

I have a Pixel 4a from google store. I had the october update on Android 11.

I followed this tutorial to root my phone : https://android.gadgethacks.com/how-to/root-android-11-pixel-4a-every-step-covered-detail-0333038

After doing the step 16 (magisk), my phone booted with the Google logo for a long time.

Then I went to the donwload mode, I have the error message "Your device is corrupt. It can't be trusted and may not work properly."

What should I do to re install android and to get my phone rooted ?

Thanks
[Google Pixel 4a Questions & Answers] DFurax:
UP
[Google Pixel 4a Questions & Answers] hasenbein1966:
You had the wrong Magisk version, so it patched the boot.img wrongly.

On Android 11, one must use the newest Canary version of Magisk.

Get the newest Platform Tools (important!), get the newest Full OTA from Google's website, flash it via the flash-all.bat which is included.

Then repeat the rooting process with the right Magisk version.
[Google Pixel 4a Questions & Answers] DFurax:
Thank you for your answer.

I'm so afraid of downloading the wrong files and bricking my phone, would you mind sending me the links of the things you told me to download ?

Thanks :)
[Google Pixel 4a Questions & Answers] DiamondJohn:
I am using the BETA version of Magisk with no issues as far a I can tell. Apart from failing SafetyNet
[Fire TV General] Bertonumber1:
Excellent work , a lot of time and effort paid off m8 .

Well done👍

just a small question.... another member had mac issues after restore , I imagine this is same case scenario to his case given it is a restore from another 4k via twrp ?

Has this been tested on other 4K sometimes it csn be problem different devices but should be okay
[Fire TV General] burcbuluklu:
No I didn't tried with another device, unfortunately I have only one :(. I would be appreciated if you test it. Thank you very much. Also can you please share the thread that you mentioned?
[Fire TV General] Bertonumber1:
Yeah sure heres some information here , not sure if this is different from your technique but sounds similar .....

https://xdaforums.com/t/unbrick-fire-tv-stick-4k-help.4021923/
[Fire TV General] Bertonumber1:
Ok my friend i can confirm we are good to go .

Everything intact remote paired , wifi /ethernet bluetooth all good (y)smooth operation

Thank you , again excellent work
[Fire TV General] burcbuluklu:
Thank you very much. What a relief. You're the first beta tester :) much appreciated.
[Fire TV General] story:
I got this working on 2 FireTV 4k.

I used the YouTube but I could never get the Amazon voice search to work with it. Do you know how to set it up correclty?
[Fire TV General] story:
Is there a way to make the Backward Play and Forward button to work with YouTUbe?
[Fire TV General] burcbuluklu:
I don't know about backwards/forward button or voice search on youtube. Maybe you can try installing original youtube app from amazon store or google play.
[Fire TV General] Bertonumber1:
Just a word to the wise as of recent events it is strongly advised members disable OTA updates on Mantis should they wish to continue modifications such as #root, launchers , adb pm commands etc etc . Update bin 6.2.7.7 has a 2nd "system updates" part to it that contains the boogeyman and is breaking things like adb commands etcetera .
[Fire TV General] burcbuluklu:
It is possible to downgrade anytime with twrp backup right? I might try to build the same setup for the new versions later.
[Fire TV General] Bertonumber1:
Yeah ofc , should be able to do this tgrough

Should be , should be enough to :

Disable addons (xposed )

boot to twrp and wipe /system , dalvik, cache

Leave data alone

Then after previous firmware has been flashed from twrp

Reboot and enable xposed , addons again , maybe another reboot ? IDK
[Fire TV General] burcbuluklu:
Ok thanks
[Fire TV General] eckengucker:
The lastest update breaks kodis "audio passthrough" under certain conditions too. DTS has been disabled by Amazon.
[Fire TV General] Velcro31:
Just wanted to say thanks! My Fire Stick became a mess and this was a breeze to install. Not sure if the following behaviour is intended, but one thing I found annoying was that when you stream something via a streaming service, the video continues to play in the background when you press the home button (you can still hear the audio). I solved this by changing the home button behaviour to "kill current foreground app".
[Fire TV General] Bertonumber1:
Hi try this app , should kill all background processes and free up some memory also

Fast Task Killer 3.1.0 | TechDoctorUK

www.techdoctoruk.com

Thanks to tduk
[Fire TV General] story:
I use YouTube a lot so that's the only perspective I can give. I am using the same YouTube apk.

The boot time is significantly longer than FireOS. I hook mine up to the TV USB so it cold boot every time. I would say it's double the amount of time to boot your rom.

1. The remote works beautifully on FireOS. It allows skipping without that shadow thing coming and interrupting and dedicated buttons for play/pause is essential.

2. FireOS using the same APK doesn't support backward on LIVE stream.

I will be switching back it was fun hacking this. It's been a while.
[Fire TV General] Bertonumber1:
Anybody experiencing not being able to delete anything from priv-app folder on 6.2.7

6 and above ? Trying to delete manually in file explorer . When i try to mount system rw it returns a device/resource busy /dev/block/soc/11230000/by-name 》sytem - system Error .

Ive disabled most of the junk but theres a lot that can be removed permanently .
[Fire TV General] 0815hoffi:
Try in twrp. I allways use twrp for that.

Boot twrp

adb shell "mount -o rw /system"
[Fire TV General] Bertonumber1:
Still the same in Twrp mate , same error.

adb shell "mount -o rw /system"

Error : mounting /dev/block/mmcblk0p11 on /system failed : device or resource busy.....WTF?

Is this a new thing with newer os ? Ive never had this before
[Fire TV General] Raphael S:
Hello guys, everything in the install process worked fine for me, however after that, I'm not able to pair my remote.. It looks like that bluetooth in generell isn't working, WiFi does tho.

Any recommendations on what to do now?

Many thanks
[Fire TV General] nokenokex:
hello!

Can this also be used for firestck TV 4k max?

Thank you.
[Fire TV General] Sus_i:
No :)
[Fire TV General] Zinyth:
Same thing for me, I got it working with a keyboard, using the add remote FireTV menu. I finally go back to the original rom, this one with Google play is way too long to boot.
[Fire TV General] Raphael S:
That's the thing, I can't get it to work with a keyboard either... My FireTV Stick doesn't even "see" any Bluetooth devices at all
[Fire TV General] ri.su:
I couldn't make this or any other 6.2.7.6 roms pair the newer style remote either with a brand new stick. I do wonder if this is because the newer remote would require some changes not present in the old rom or if it's something else that is going on here..

But did then notice that while testing with patched 6.2.8.1 it paired the new remote immediately.

By new remote I mean the one with prime ideo, netflix, disney+ etc buttons. I don't have access to the older remote immediately but can potentially test it later on.

After pairing the remote once with newer rom and then after downgrading to 6.2.7.6, remote is actually discovered automatically as it doesn't ask to pair it again :)

I do wonder if this is all that great solution in case firetv loses the remote pairing (pretty sure this has happened to me few times with my previous Mantis stick but it could have also happened after OTA updates so can't immediately tell if this will be an issue or not)

EDIT: This only helped to get rid of the the initial remote pairing popup. This specific ROM still doesn't pair this remote properly because data is wiped but other patched 6.2.7.6 ROM worked with this hack.

EDIT 2: wiping dalvik/cache keeps remote paring but doing factory reset will get rid of the exististing pairing apparently
[Fire TV General] Toothless_NEO:
How did you add the TV settings in to it, could you please tell me? I really want/need to add the TV Settings because there are a lot of options Amazon settings don't allow you to access.
[Fire TV General] ri.su:
I did some further looking around and doing a diff using 6.2.8.1 between data state right before pairing the remote and after pairing and it revealed that the remote pairing changes the data in a whole lot of places. I've tried to find out which files are mandatory for this but not much luck so far. Basically the remote pairing data is present in data because I can backup this data using TWRP and even restore it on 6.2.7.6 and have remote that is paired but this obviously breaks a ton of other things as not all of the data is backwards compatible.

I do suspect there's either some device ID or firmware update on the newer remote that prevents older ROMs from pairing it (but these ROMs can still work if the pairing is done on newer version).

I'm curious if there's some way to fix this properly without getting older remote (I guess you'd have to buy some 2020 firetv stick that still ships with the old style remote without the extra netflix etc buttons as 4k model isn't sold with that remote anymore). Other alternative is to just use 6.2.8.1+ but then the (DTS etc) audio passthrough is broken again.

I tested bunch of ROMs and 6.2.8.1 is first one that pairs the remote my stick shipped with. Data folder has mention of (remote?) firmware version v27.

Ideal solution to this would be to be able to adjust 6.2.7.6 ROM to accept the newer remote somehow but even being able to manually restore only the files that contain pairing data would be fine, as long as one could identify all the required changes (I think this would still leave the extra netflix etc buttons nonfunctional since the older ROM doesn't seem to implement them?).
[Fire TV General] ri.su:
It's been a while and realized I didn't report back here. I didn't end up using this ROM specifically, but rather rebuilt something similar myself with similar steps. Wanted something that was bit cleaner as basis but still used 6.2.7.6 ROM. I installed bunch of newer APKs to make the remote and other apps more compatible. Updated stock apps can be found here: https://gist.github.com/JulyIghor/d3d3dd460527a1d2b5b67954160d4abf (if you've blocked cloudflare from router to block amazon OTA updates, you need to bypass that limit somehow, I just used VPN for this).

So basically what I've done is:

- paired remote on 6.2.8.1, didn't even do registration at this point yet, just restarted it immediately after remote got paired

- took TWRP backup from data immediately after this

- installed 6.2.7.6 and did a factory reset

- restored data only from that 6.2.8.1 backup to restore functional remote pairing. this breaks bunch of stock apps since the data from newer ROM is incompatible with the older app versions but following will fix that:

- installed these APK's manually:

"Amazon Appstore" / com.amazon.venezia from 2022-04-21

"Equipment Control" / com.amazon.tv.devicecontrolsettings from 2022-01-18

"Fire TV Device Control" / com.amazon.tv.devicecontrol from 2022-01-18

"OOBE" / com.amazon.tv.oobe from 2022-01-13

Basically having these newer APKs fix the incompatibilities I got after restoring data backup from 6.2.8.1. In theory one might be able to wipe the cache at this point and repair the remote but I haven't dared to try because this system is now functional for me. My only issue atm is that sleep is broken but it might not even be related to these changes (have read others have gotten stuck with black screen on sleep even on unmodified 4K sticks).

Worth noting that the app shortcut buttons on the new style remote still don't do anything on 6.2.7.6 despite updating the APKs, I don't know if it's limitation of the launcher (I don't use stock launcher) or something about 6.2.7.6 itself not just having support for. This applies only to the four buttons on the bottom for netflix etc, the new guide button still works.

If you are using the backup from the original post on this thread, you could try installing these APKs alone on top of it and see if it fixes your remote pairing.
[Fire TV General] bnevets27:
After a lot of messing around and not realizing I had skimmed over reading this post, I can confirm I had the same issues. I thought I would try to flash this ROM on a fresh out of the box stick to see if it was possible to jump right into a fully setup stick, avoiding updates, amazon account log in etc. It didn't end up being possible, at least in my case with this ROM. Could have been a multitude of things but I did try a lot of combinations. Aside from not being able to get into the setting after flashing this, pairing the remote or getting past the pairing screen on startup also posed problems I couldn't get around.

After reading about the 6.2.7.6 with newer remotes not working I grabed an old remote (no services buttons) and it paired right away.

It's unfortunate that it looks like you couldn't find the location of the paring information. That would be really great to find. That way we could put that back in place after flashing a rom and not have to re-pair the remote. As well as being a lot easier to get around this new remote problem.

I did learn a bunch of little tricks to work without a remote and without the use of an OTG cable which I'll post up in a new thread I'll start, as I want to find away to have something like this but actually working for me. I would also like to get google assistant working as well. Actually would probably make a version with google assistant and one with Alexa as people have their preferences.

So thank you for the tip about the remote and spending the time to do the diff compare, as that was my next thought.

If you are interested or willing to share your twrp backup that might be a helpful starting point if you managed to get it into a good state. Either way I plan on trying to make my own version. I had hoped this would have worked, would have saved some time. Still not sure why it won't work for me.

Also planning on doing this sort of thing for the 3rd gen (sheldon), taking it as far possible and playing around a bit. Not sure if it's possible to get this far with that version or not as I haven't worked with is as much as the 4k.

And thanks for putting this together burcbuluklu.
[Fire TV General] ri.su:
Ah I actually dropped the whole 6.2.7.6 since I don't really need the DTS passthrough that badly with FireTV. I'm currently running 6.2.8.9 with leanback launcher and play store but it's bit hacked setup where I've stripped a lot of stock apps to free space etc. Backup isn't possible I'm afraid but can give pointers on how to do this if someone is interested. Going with 6.2.8.9 did also update the remote again so I don't think I can go back to 6.2.8.1 etc without doing the mixed app setup again.
[Fire TV General] bnevets27:
Well you bring up the other point I was trying to figure out also. Which is the "best" version to go with? Unless the newest version breaks things like say DTS (and currently I don't need this either but nice to not loose features) then probably good to be on a reasonably new firmware.

Looks like I'll have to have a mix of firmwares, old 4k, new 4k and 3rd gen. Might be looking for some advice in the future on how to get the playstore installed and such. Everything being done to the fire tv sticks is a hack so not worried about that.
[Fire TV General] ri.su:
I think 6.2.8.1 is best all around version today if you want to go custom. I had setup like this for a while too and you can find those custom kernels for NTFS etc file support for it. 6.2.8.9 offerings are more limited.

Basically:

6.2.7.6 - Last version with full HDMI audio passthrough with DTS, TrueHD etc support. But can be problematic with paid DRM since it's so old already. Custom kernels available.

6.2.8.1 - Loses passthrough for anything but few Dolby formats streaming services use (and LPCM still kinda works). Afaik this version still works with most paid streaming services. Custom kernels available.

6.2.8.9 - same as 6.2.8.1 but no custom kernels available. Newer DRM module so probably more future proof for paid streaming. Requires extra patch to be able to run custom launcher with this one.

There's now 6.2.9.0 and 6.2.9.1 too but I haven't followed what they change and what it requires to make them usable on customized setup so can't really talk anything about them. Of course every solution requires caution that you don't get OTA updates and not accidentally lose the root access that makes all this possible. I've removed all OTA related apps and blocked the amazon update servers from router just to be safe.
[Fire TV General] Povlig:
Hi All!

I have successfully installed "Firestick 4K Android TV TWRP Backup.rar", thanks!

My stick is locked by Amazon. I can't register this device. How I can bypass initial requirements of registration at Amazon?
[Fire TV General] Hotrod369:
What's preventing you from registering your firestick 4k?
[Fire TV General] Povlig:
I cant' register firestick at Amazon because I bought "replaced" device as Amazon told me. At initial boot it is necessary to login to Amazon account, I'm entering code, logging using username and password - nothing happens.
[Fire TV General] Hotrod369:
I had a buddy that thought his wifi had been hacked so he calls Amazon and has them deregister his firesticks. Well, he ran into the same issue when he tried to reregister them. He ended up having to call Amazon again. to get it sorted out.
[Fire TV General] anphabvn:
Use twrp File manager delete OBB in system/privateapp
[Fire TV General] Povlig:
🤔 What do you mean by delete OBB ? I found folder "system/priv-app" but there is no folder or file in it named OBB ...

anphabvn​
[Fire TV General] Finnzz:
/system/priv-app/com.amazon.tv.oobe

OOBE: out-of-box-experience
[Fire TV General] Povlig:
I've deleted folder "/system/priv-app/com.amazon.tv.oobe" using TWRP file manager and rebooted firestick4k.

Anyway I see screen with login to Amazon using username and password. I'm entering credentials and it shows "registering device" and switching back to the screen with credentials. It can't login to Amazon. I have checked this folder "/system/priv-app/com.amazon.tv.oobe" again after these manipulations and it still there... Is there anything else that must be done in order to bypass login to Amazon on boot of firestick4k ?
[Fire TV General] anphabvn:
Its OOBE. sorry.
[Fire TV General] anphabvn:
You need delete oobe.apk inside that folder and factory reset.

What is your FireOs version ? Try to use 6.2.7.7
[Fire TV General] Povlig:
After several different attempts finally I was able to do that.

If you have firetvstick4k that is blocked by Amazon you must boot in TWRP, mount system folder, open file manager - navigate to folder "/system/priv-app/com.amazon.tv.oobe" and set permissions on apk file in this folder to "0400".

(I've tried to delete file as it was recommended but it does not help and it appears again).

Everything works for me except of original Amazon remote control - I can't pair it. I'm using FireTV application on my phone for navigation, also I was able to pair PS4 dualshock controller.

Is there any trick that allows to pair Amazon remote control ?