yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Flamefire:
reserved2
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] aapok98:
Thank you for keeping this rom up to date for this small but loyal userbase! A miracle come true for me cause I can't build roms on my own.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Dean F:
Thank you so much!! Can anyone report to me if flashing the new 18.1 directly over the previous version of 18.1 works?

I would test myself, but right now I cant afford to need to totally reset my phone if it doesn't work.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] landsome:
All I can say dirty flashing works well over the latest/previous 17.1 by Flamefire, which in turn works well over the latest modpunk (1.7). So it's worth a try.

More generally, although these ROMs are hardly as well tested as HavocOS, there are satisfied reports over on the original LOS17.1/18.1 thread.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] rez78:
Dirty flash from 17.1 to 18.1 and all work fine!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] landsome:
Exactly. Just not the other way around.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Flamefire:
Updated with the July security patches.

Note: AndroidFileHost was quite quirky today, so use the md5sum files to verify the integrity of the files
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] rez78:
Dirty flash. Work perfect!
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] landsome:
Thanks. Tried it for a couple of hours - dirty flashed over the 0702 version - and it works just as well so far.

I had one brief moment of panic: upon first boot the phone was stuck right on hitting the desktop for some 10 seconds (did not happen on the many previous dirty flashes); but then everything proceeded well.

Again, great work.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] banana(x):
@Flamefire Regarding the information to TWRP: There is an official TWRP version (maintained by @modpunk & @derf elot ): https://twrp.me/sony/sonyxperiaxz1compact.html :-)

Maybe you can update the information in your header.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] 7alvoo:
Your suggestion would be valuable if you share your experience:

- encrypted partition mount and decryption compatibility with LineageOS 17.1/18.1

- partition backup / restore - single / batch - with / without password protection

- other version differential bug report
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] Dean F:
Im running 18.1 ROM now and its working great. It works so much better than the previous January release, because the network connects properly now after restarting. There is no need to fiddle in the settings to switch to 3G, then switch back to 4G.

I really like it.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] xenonism:
Ok, I was bored and I made a mess, I could use some help. :(

I was on the latest and last 17.1 by modpunk. I updated TWRP to the latest official one. I tried to flash the latest 18.1 by Flamefire (I had to disable zip signature verification. I know :censored:). Upon reboot it spends about a minute on the LOS animated logo then reboots to TWRP. I then downgraded TWRP to the latest by modpunk and flashed his latest 18.1 from January. This bootloops to recovery without ever reaching the LOS logo.

I know this is my fault. This said, what's my best chance (if any) not to have to wipe everything? I read in a post above that downgrading from 18.1 to 17.1 won't work, otherwise that would be my next idea.

Thanks in advance to anyone replying! :)

EDIT: Silly me. I had just forgotten to flash 11.0 gApps. All is well with the dirtiest flash ever. :p
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] megaice:
It was not possible to boot LOS 17.1 with TWRP version from first post. (fresh flash, etc... ) However when using latest official twrp https://twrp.me/sony/sonyxperiaxz1compact.html everything works well.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] baboon23:
OUTSTANDING!

Thanks for bringing life to this amazing work, you are the best!

Much appreciated.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] mstrnemo:
@Flamefire

Im confused so u continue with updating the security patches every month correct ?

Im confused about the 18.1 u also only update it with securitypatches or also other stuf like making stable and fixing problems orwhatnot ?

Thank you for keeping our trusty xz1 compact alive a little longer.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] 7alvoo:
Does it respond to volume up button presses and in special system restart recovery mode? Prompts for a pin/pattern during login and successfully mount and decrypt the partition? So far no one else has reported using it and so far we knew 17.1 / 18.1 requires a different version. Your experience will help us a lot please share as much experience as possible about the new twrp.
[Sony Xperia XZ1 Compact ROMs, Kernels, Recoveries,] megaice:
i forgot to mention - i'm using lineage-17.1-20210702-UNOFFICIAL-lilac.zip build (not the latest ..20210720..)

TWRP version 3.5.2_9.0

Magisk 20.4 -> 23

Entering recovery works well, pwr+vol down, vol up after pwr, or when set in Developer submenu - advanced reboot. I have active pin and fingerprint. When entering recovery, twrp asks for password for user 0, using my pin works and twrp decrypts FBE. i can mount and read user data by File Manager in twrp.
[General Topics] vcetina:
Hi there.

Im looking for a WM6 program that automatically hang up calls after a certain period of time. For symbian i used to use a program called autohangup. For WM i found one called phonescreenlock, but the hangup portion its not working on my WM6 HTC TOUCH.

Thanks for your help.
[General Topics] salespace:
try http://www.calllimit.com/order_now.php

it really works i have it
[Fire TV Q&A, Help & Troubleshooting] mydanuyen:
Sorry my english bad .

Caution it is hardware solution . Need change emmc . I share isp pinout Fire TV Stick 4K (mantis) . Ver new amazon disable Brom mode for cpu . Only mtk preload port. Then testpoint pc no view port . Only solution is change emmc new . After write dump make by me . Fire TV Stick 4K (mantis) boot done twrp and rom mantis-6.2.8.1 and adđ root Magisk-v23.0 . https://drive.google.com/file/d/14sLN-RIoO6sPkE--3T4_2c6s640JaDoD/view?usp=sharing . No write dump stock read for emmc old . Phone brick only mtk port preload . View attachment 5366231
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Thank you very much for the picture (y)
[Fire TV Q&A, Help & Troubleshooting] Bertonumber1:
@mydanuyen Excellent work thank you for sharing this photo.

Kind regards
[Fire TV Q&A, Help & Troubleshooting] Spamm00r:
Thanks for this useful information.

ANyone has done this and can give a comprehensive tutorial on this?

How do I wire these three points to an sd card reader or an USB stick to read and write to the eMMC.

And what about powering the chip? According to the guides at https://www.exploitee.rs/index.php/Interfacing_with_e-MMC_Storage_Devices

You also have to make sure voltage and powering is ok and not inteferred by the CPU.

Any complete guide on rooting the hardware way would be useful, as there is no other way to root the fire tv stick right now.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Read/write the eMMC is possible, but there is still no way to dowgrade the RPMB.

Without a downgrade of RPMB (antirollback), the SOC refuses to boot the somewhat older unlocked images, therefore an unlock/root isn't possible... right now ;)
[Fire TV Q&A, Help & Troubleshooting] Spamm00r:
I thought all you need for root is to copy the su binary in the xbin folder. If that is not enough, i guess it is really game over. Then why do hardware root at all?
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Back then as fireOS3 was a thing, this was working... copy su into xbin and done ;)

It worked on fireOS5 too, but needs to add proper SELinux contexts.

Since fireOS6, any modification on system will prevent booting, android uses some new security things like dm-verity, therefore the bootloader needs to be unlocked too, in order to boot unsigned images.
[Fire TV Q&A, Help & Troubleshooting] ri.su:
I'll second this. Would love to have some step by step instructions for this. Also can someone list the minimum equipment needed to do this?

Missed the window for software solution (stick is already at 6.2.8.7). I saw @Sus_i mention this might still be possible to do with hardware route in this post: https://xdaforums.com/t/unlock-root...stick-4k-mantis.3978459/page-87#post-86544297
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
In theory this should be possible.

Back then there was a hardware root method for the first gen fireTV & fireTVstick.

Amazon Fire TV Stick - Exploitee.rs

exploitee.rs

Some wires to the fireTV, a special eMMC adapter and a sdcard reader was/is enough to access and write data to the eMMC.

Interfacing with e-MMC Storage Devices - Exploitee.rs

exploitee.rs

For mantis we would need to write an old vulnerable preloader to the preloader partition, thats all. Then kamakiri should work fine.

Breakout Pins for mantis is known, thats not an issue.

But someone needs to guess / try the SOCs crystal / xtal which needs a shorting for stable eMMC access, otherwise the SOC will power on and mess things up.

I guess nobody will try this soon, because there are a lot vulnerable devices out there, still easy to find...
[Fire TV Q&A, Help & Troubleshooting] snam11:
i'm "refreshing" the post because i have a mantis in bootloop, on latest fw so i can't use kamakiri to unlock it and install twrp.

playing with the board i've found few other useful pinouts on it, (clk and cmd points on the kamakiri main topic pic are wrong) and i was wondering:

Sus_i​

do you think if soldering those pins (gnd/vcc/data0/clk/cmd) directly to an sd adapter (like the one in the picture) and manually injecting 3.3v to the vcc pin without powering on the fire stick, it would be possible to read and write the preloader partition?

EDIT: nevermind... according to this exploitee.rc doc ( https://www.blackhat.com/docs/us-17...acking-Hardware-With-A-$10-SD-Card-Reader.pdf ) a sdio controller is needed (with realtek rts5170 on it) in order to be able to have access to mmcblk0boot0, so even if the sd adapter works, this kind of reader is mandatory
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
The stick uses 1,8v so you would need the low voltage adapter mentioned at exploitee, but if you desolder the eMMC from the board, 3,3v will work fine without the need of a low voltage adapter. A sdcard reader capable of r/w mmcblk0boot0 is still required.
[Fire TV Q&A, Help & Troubleshooting] snam11:
so i was able to read boot0/1 of the emmc and i've flashed the patched kamakiri preloader.img to boot0, but when i run the kamakiri script i get an error:

[2024-03-07 21:42:23.451210] Waiting for device
[2024-03-07 21:42:23.787935] Found port = /dev/ttyACM0
[2024-03-07 21:42:23.824845] Handshake
[2024-03-07 21:42:23.847842] Load payload from ../brom-payload/pl/pl.bin = 0x3A04 bytes
[2024-03-07 21:42:24.940565] All good
[2024-03-07 21:42:25.434492] Check device_type_id
[2024-03-07 21:42:25.434597] Detected mantis (AKPGW064GI9HE)
[2024-03-07 21:42:25.434641] Check GPT
[2024-03-07 21:42:25.962362] gpt_parsed = {'': (0, 1), 'cache': (2662400, 1048576), 'boot': (23552, 32768), 'kb': (96256, 2048), 'tee1': (3072, 10240), 'tee2': (13312, 10240), 'system': (409600, 2252800), 'dkb': (98304, 2048), 'lk': (1024, 2048), 'recovery': (56320, 32768), 'userdata': (3710976, 11562591), 'vendor': (102400, 307200), 'logo': (89088, 7168), 'MISC': (100352, 2048)}
[2024-03-07 21:42:25.962544] Check boot0
[2024-03-07 21:42:26.442006] Check rpmb
[2024-03-07 21:42:26.473672] Downgrade rpmb
[2024-03-07 21:42:26.474770] Recheck rpmb
Traceback (most recent call last):
File "main.py", line 135, in <module>
main(dev)
File "main.py", line 74, in main
raise RuntimeError("downgrade failure, giving up")
RuntimeError: downgrade failure, giving up

same thing happens if i try to flash the preloader.img of the 6.2.8.0 ota update (update-kindle-mantis-NS6280_user_3236_0005067547780)

what am i missing?

full boot0 img is like 4mb, and the preloader img is just 150kb.

should i fill with 0 the bin to reach same filesize?
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Congratulations :) (y)

Thats a common kamakiri issue, the flashed PL works as expected, you may just need to comment out the Recheck rpmb part in the kamakiri main.py file. Then the script will proceed fine...

Would be nice if you tell us how you've flashed the PL to the eMMC...?
[Fire TV Q&A, Help & Troubleshooting] snam11:
while waiting for your reply i've already commented in kamakiri/modules/main.py

72 if rpmb != b"\x00" * 0x100:

73 dev.reboot()

74 raise RuntimeError("downgrade failure, giving up")

and the flashing seems ok, but now i'm facing a new issue:

after the reboot nothing happens and fastboot script just hangs on waiting for device

[2024-03-08 09:45:04.861948] Waiting for device
[2024-03-08 09:45:10.817333] Found port = /dev/ttyACM0
[2024-03-08 09:45:10.853980] Handshake
[2024-03-08 09:45:10.877503] Load payload from ../brom-payload/pl/pl.bin = 0x3A04 bytes
[2024-03-08 09:45:11.970313] All good
[2024-03-08 09:45:12.465798] Check device_type_id
[2024-03-08 09:45:12.465911] Detected mantis (AKPGW064GI9HE)
[2024-03-08 09:45:12.465947] Check GPT
[2024-03-08 09:45:12.996151] gpt_parsed = {'': (0, 1), 'dkb': (98304, 2048), 'kb': (96256, 2048), 'boot': (23552, 32768), 'tee2': (13312, 10240), 'system': (409600, 2252800), 'cache': (2662400, 1048576), 'lk': (1024, 2048), 'recovery': (56320, 32768), 'tee1': (3072, 10240), 'logo': (89088, 7168), 'userdata': (3710976, 11562591), 'vendor': (102400, 307200), 'MISC': (100352, 2048)}
[2024-03-08 09:45:12.998877] Check boot0
[2024-03-08 09:45:13.479901] Check rpmb
[2024-03-08 09:45:13.515586] Downgrade rpmb
[2024-03-08 09:45:13.518708] Recheck rpmb
[2024-03-08 09:45:13.634838] rpmb downgrade ok
[2024-03-08 09:45:13.637124] Flash tz
[7265 / 7265]
[2024-03-08 09:46:14.418982] Flash lk
[613 / 613]
[2024-03-08 09:46:19.939988] Flash lk-payload
[7 / 7]
[2024-03-08 09:46:20.476732] Inject microloader
[2 / 2]
[2024-03-08 09:46:21.022276] Force fastboot
[2024-03-08 09:46:26.541824] Reboot

./fastboot-step.sh
< waiting for device >

any tips on how to solve this issue?

maybe a backup of boot0/1 from a pre patched mantis so i can flash them both, and from twrp recovery wipe everything and flash a new image?

of course i'm gonna try to make an howto if this method is gonna work.

little spolier: i'm using an ft232h device
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Thats also a known issue for some setups, usually a (forced) update of the fastboot package works this issue out.

Btw, you would still need the rpmb downgrade, so make sure only the recheck is gone, the stick won't boot without a downgrade, even fastboot may not work.

(y)
[Fire TV Q&A, Help & Troubleshooting] snam11:
well, how to do so? i mean i have no clues at all...

same goes with the rpmb downgrade (i've just commented those few lines, i dunno what else to check).
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Depends on your linux system. If you use an arch linux based system then you can use pacman command, like this: pacman -Sy fastboot

For ubuntu you can use apt or apt-get in order to update the fastboot package to the most recent version (to fix the issue, i.e. a bug in fastboot for some systems).

Thats ok. (y)
[Fire TV Q&A, Help & Troubleshooting] snam11:
thnx and sorry for the dumb questions :D

i've used 2 vm and a notebook to rule out any potential issues related to hardware

so with fireiso modded linux (on a notebook and a vm on a desktop) i get:

:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
error: target not found: fastboot

so to my understanding it simply won't update the fastboot because it can't find any device in fastboot mode?

i did also a try on a linux mint vm (same one i've used to unlock my tank device) and what i get is hilarious (check the pic).

i suppose on mint i need a different command that clearly can't be pacman...

at this point i'm out of ideas.
[Fire TV Q&A, Help & Troubleshooting] Sus_i:
Connect the fireISO system to the internet and then run the mentioned pacman command.

This fixed the fireISO fastboot issue for countless people here...

After the bootrom-step (which may need to run until the fastboot-step works), run lsusb too.

If it still fails, then do the bootrom-step on the fireISO via VM and if you see the reboot to fastboot message, switch the stick to the host operating system via vm settings., open up a CMD window over there and run fastboot devices. If the stick is in fastboot mode, you can just run the commands from fastboot-step.sh in the CMD window.

If nothing will work, you can still write the stuff from the fastboot-step via ft232h device. In this case I would connect a usb ttl uart device to the uart pads to look whats going on during boot, to get an idea why it fails to boot into fastboot (may fail to boot system too).
[Fire TV Q&A, Help & Troubleshooting] snam11:
yea i've updated the package while ago, but just to be sure i've started fresh again:

[root@fireiso ‾]# pacman -Sy fastboot
:: Synchronizing package databases...
core 134.0 KiB 184 KiB/s 00:01 [######################] 100%
extra 8.4 MiB 519 KiB/s 00:17 [######################] 100%
community 45.0 B 0.00 B/s 00:00 [######################] 100%
error: target not found: fastboot

and from there every time i try,i get the same reply (right after the bootrom script)

and waiting for device right after the fastboot sh script

[root@fireiso ‾]# pacman -Sy fastboot

:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
error: target not found: fastboot

i dunno if it was necessary in the first place since i've unlocked and used fastboot with no issues at all on my other stick (an old tank device).

btw i've noticed when i plug the usb cable to connect the stick, it shows up for like a sec than it just disappears for a few seconds, and appear again and disconnect after a sec, in an infinite loop.

when it shows up with lsusb i get

Bus 001 Device 009: ID 0e8d:2000 MediaTek Inc. MT65xx Preloader

i've tried kamakiri at least 20 times and it just won't connect afte the flashing and reboot.

well i need to figure out first how to write stuff with the ft232h because atm i can flash boot0/1 and userdata with it. dunno how to write the recovery partition (since is not stored in boot0 or 1 i guess). Do you know how to do it?

i'm gonna also solder later today the pins to the usb uart so i can at least see what happens with it after the kamakiri flash.
[OnePlus 6 Questions & Answers] RJrocks01:
Hi Channel,

fastboot boot twrp-3.5.2_9-0-enchilada.img is successful BUT lands in crash dump error (init killed continue and exit). How can I boot into recovery? Any suggestions

Device : Oneplus 6 with Bootloader Unlocked

Currently running Oxygen OS Android 11 OB1
[OnePlus 6 Questions & Answers] Pundy:
Check this :) https://xdaforums.com/t/oxygenos-android-11-open-beta-1-for-oneplus-6-6t.4304161/#post-85343061

flash the boot.img in fastboot: fastboot flash boot boot.img and reboot ^^
[OnePlus 6 Questions & Answers] RJrocks01:
fastboot flash boot boot.img

This needs to be done for both slots A and B?

Also, when you say reboot, does it mean reboot to system
[OnePlus 9 Pro] samwhiteUK:
Yesterday I rooted my device thanks to you guys, which went really well and passing SafetyNet was a breeze. I just have a few questions that I'd like to get solved:

1) Play Store Certification - I accomplished this by using the fingerprint mask Magisk module, and I chose OnePlus 8 Pro Android 11 for my fingerprint. Play Store certification is now accomplished, but should I have had to do this? This leads on to question 2....

2) I thought I would be able to get certification by adding the Play Store to Magisk hide, but Play Store doesn't appear in the list of apps in Magisk. Same with Netflix. I was confused by this, as a) I thought that all apps should appear and b) the root tutorial pinned to the forum specifically says to add Play Store and Netflix to Magisk hide

3) My Netflix Widevine is now L3. Did I mess up somewhere? I've read that on OOS11, unlocking the bootloader doesn't trip Widevine
[OnePlus 9 Pro] Ninxha:
Well you could have gone much easier.

1) Turn on Magisk Hide and Systemless Hosts.

2) Right bottom of Magisk Hide theres the Magnifying glass to search. Click on it and click Show System Apps. Then Play Store and Google Services will be shown. Hide everything in Play Store tab and Google Play Services Tab. Also Netflix tab.

3) Clear cache of Play Store, Google Play Services, Netflix(might even unistall updates here just to be sure, thats what i did).

4) Reboot Phone, Go Play Store and update Netflix through Play Store at this point. Should be at Widevine L1
[OnePlus 9 Pro] samwhiteUK:
Ok I will try this, thanks for the pointer. I had hit that System Apps thing before but perhaps it didn't refresh. I can see it now
[OnePlus 9 Pro] samwhiteUK:
I can't install Netflix from the Play Store, it says the app is no longer compatible with my device. If I search for it, it doesn't appear. I can only get there by clicking the pre-installed icon, and then I can't do anything
[OnePlus 9 Pro] Ninxha:
Download it from apkmirror. Give it some time should be available soon on playstore after it gets Certified. Wasnt for me on playstore at first. give it some time and check again. BTW did you delete your module of fingerprint?
[OnePlus 9 Pro] samwhiteUK:
I will download from there, that's what I did before. I deleted the fingerprint, and hid the Play Store, and I'm now certified with Play Protect without all that rubbish. Is it just a matter of time then before Netflix shows up again? I will install the APK - presumably I will still be able to get updates through the Play Store after that. I will let you know if I get Widevine L1
[OnePlus 9 Pro] samwhiteUK:
Nope, still L3. I don't even watch Netflix that much on my phone, so it's not urgent, but I'd just like to know that everything was working as a standard phone would :/
[OnePlus 9 Pro] Ninxha:
To me it was shown after some time. got a update of netflix through playstore and got widevine L1. Unistall udpates on Netflix and wait maybe u will get it from playstore after some time
[OnePlus 9 Pro] samwhiteUK:
Did you start off with Widevine L3 when you first unlocked? If it's supposed to remain at L1 and it hasn't for me, then I don't know if it's worth waiting. Can it go back up?
[OnePlus 9 Pro] Ninxha:
I dont actually know that. Netflix was not available after rooting. And since i had just unlocked bootloader phone was resetted. So i was installing all apps and updates and netflix was not available. I managed to install all updates of apps and installed new apps, did magisk hide and hide netflix, play store, google services, clear cache, reboot. still netflix wasnt available but i did not open it, until later when i got an update through netflix, logged in, checked it was L1
[OnePlus 9 Pro] samwhiteUK:
Got the update, just came through. Added to Magisk hide, logged in, but it's still L3. :(
[OnePlus 9 Pro] Ninxha:
:/.. clear cache again idk... damn
[OnePlus 9 Pro] Ninxha:
Does Playstore says certified? There would be no reason for L3 if you already got netflix on play store working fine... Try unistall it again, clear data again, reboot and go install it again from playstore..... meh
[OnePlus 9 Pro] samwhiteUK:
I'll wait and see if anyone else comes along, and I'll do some more searching. Thanks for your help!
[OnePlus 9 Pro] samwhiteUK:
Yeah, Play Store certified, assuming I'm checking in the right place (in the settings menu)
[OnePlus 9 Pro] Ninxha:
Yes play store settings and then about in the end... Try one more time what i told you and idk what else. I got L1, dont think i was just lucky...
[OnePlus 9 Pro] samwhiteUK:
Yeah, uninstalled and reinstalled and it's still L3. DRMInfo says L3 as well
[OnePlus 9 Pro] flameteam:
Although Widevine L1 is displayed, it becomes L3 and gives an error when watching Netflix downloaded content. not working properly.