yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XA Ultra Questions & Answers] klengjaua:
So i followed the thread on how to root xperia xa ultra duel in here https://xdaforums.com/xa-ultra/how-to/how-to-root-xperia-xa-ultra-dual-t3439173

but after rooting and doing all steps after booting the device and checking it's functionality I noticed that the front camera is not working and it crashes everytime

so i wanted to flash a new firmware but my flashtool kept saying "no flash script found" and aborted the flashing >>so i waited for a new boot and the creator "rrvuhpg"

made a new boot for the test in here https://xdaforums.com/xa-ultra/development/f3212-f3216-stock-kernels-built-sources-t3527762

flashed it using adb and rooted the device one more time and booted the phone again now there are 2 problems while the camera problem is fixed

the screen won't turn off completely and after clicking the power button to turn it off it turns into a very dark screen "not noticeable in high light but in low light u can clearly see it's on"

and when i try to click the power button to turn it on again it does this weird TV like static and shows the normal screen afterwards

and the brightness level meter is always at the maximum and can't be changed so my phone battery dies very quick now

I need help because I can't flash anew firmware and i have to stick with "Battery Killer" setup i have right now so i need help with both flashtool and a fix for the boot or just a way to recover my stock firmware
[Sony Xperia XA Ultra Questions & Answers] klengjaua:
i checked one more time and i found out that the twrp can't wipe cache partition and if i factory reset the phone it doesn't work and all data remain
[Fire TV General] scoobysnack:
Not sure if anyone knew but PIA (Private Internet Access) does work on the Fire Stick with Alexa running 5.2.4.0 (I'm not sure if it works on 5.2.2.0). I will say it runs slower then running it through my router by half. Now to get this puppy rooted :) P.S. I give up on trying to upload pics.
[Fire TV General] Y314K:
To be more precise you are saying that the PIA Android app works fine on a FireTV Stick 2. Which is to be expected since the FTVS2's hardware is close to being as powerful as a FireTV 1 Box.

It's good to have confirmation. :good:
[Fire TV General] scoobysnack:
Yes it works flawlessly....I bought this thing to toy around with. Now if we can get root on this it would be pretty awesome.
[Fire TV General] philetus:
Is there any way to manage PIA on the stick or are you stuck with what is sets when you log in?
[Fire TV General] Y314K:
You don't, you just need to connect to the Wifi that already has the VPN working. The PIA Android App is only for those that want to run a VPN on a per device bases or if you can not run the VPN thru our router or secondary router. A router run VPN is always recommend due to specs. But being able to run it a FireTV device itself is a good second choice.
[Fire TV General] philetus:
That would work if I had the VPN in the router, but I just had it in my laptop.

I was able to install PIA in the firestick easily. It does change the IP so I'm good.
[Fire TV General] scoobysnack:
Use mouse toggle to change the VPN server.
[Fire TV General] philetus:
UPDATE: I was able to figure it out. Works great. Thank you.

I installed mouse toggle and I can access settings, but I can't figure out how to change the current region.
[Fire TV General] scoobysnack:
Click the region showing and it will bring up the rest use the 2 buttons on the right side of the remote to scroll up and down.
[Fire TV General] Y314K:
Some are able to run a Wifi signal as a repeater on a laptop or desktop. But running the app on the device itself is much less complicated.

Are you running PIA on a FTVS1 or FTVS2. Spec wise I would only recommend running it on a FTV1, FTV2 or FTVS2 but I bet it runs ok on a FTVS1 although those are way slow. Guess having only used FTV1's for myself & programed FTVS1's for my F&F's have giving me a slow experience with FTVS1's. Messed with a couple of FVTS2's recently. And I still would prefer my FTV1's speed & controller wise. I hope the GUI update for FTV1's gets release soon.
[Fire TV General] philetus:
I have the 2nd gen. FTVS2 amd Kodi Krypton 17. I've seen some saying PIA doesn't work well on 1st gen, saying it is on, but doesn't change the IP. IP Vanish is said to work good with gen 1. I just pushed the APK to the stick from my laptop with mimimal ADB and fastboot. Pushed mouse toggle also and everything works fine. Have you looked at Schism, https://www.youtube.com/watch?v=QiueM0jcL0k&t=603s
[Fire TV General] Y314K:
I mostly run/install FTG Builds (FireTVGuru Builds: http://firetvguru.net/) since those builds are the easiest builds to keep updated by folks that don't like to pay attention to things. But all of those are still Kodi v16.1 based.

I've seen the new Kodi v17-RC builds. I was gonna try Schim's first. Guess I got to get used to the new Kv17 layout. But got sidetracked by the SU /SDCard bug when updating my FTV1's....
[Fire TV General] nbaj2k:
Is it possible to have the PIA VPN enable automatically when Kodi is run but disable when you close out of the app? I was just curious since when I try to watch something on Amazon Prime it's blocked when the VPN is enabled.

I'm guessing probably not, just wondered.

-J
[Fire TV General] scoobysnack:
With PIA you can set it for per app. You will need mouse toggle to reach the settings.
[Fire TV General] nbaj2k:
Awesome I completely skipped over it. Thanks!
[Fire TV General] nbaj2k:
One other quick question. So I enabled it to use VPN in Kodi, but not use it in any other app. I still get a geographical error when trying to watch something regularly on Amazon prime. Do you happen to know if there another step I need to do in order to get it to work?

Thanks,

-J
[Fire TV General] scoobysnack:
Switch servers.
[Fire TV General] JeffDC:
Per app?

Can you point out that setting/method in PIA? I have not seen that option on the Windows, Mac or Android version.

Thank you.
[Fire TV General] scoobysnack:
The setting button is in the far upper right corner.
[Fire TV General] JeffDC:
Thanks for that. I don't have the same options on my Mac!

...

nor on my Windows PC.

It is on my Android phone though!

I'd think that option would be (even) more useful on laptops/PC's.
[Fire TV General] scoobysnack:
Yeah my bad.. There no option for the desktop. It's all or nothing.
[Fire TV General] nbaj2k:
Thanks, didn't realize that would be an issue since I had an American server chosen but apparently it was.
[Fire TV General] scoobysnack:
You might consider turning on the Kill Switch...I've had PIA fail on me once.
[Fire TV General] JeffDC:
I wonder if we put together a "kitty", for some wizards/some folks to get the root going...... would provide incentive?
[Fire TV General] DC321:
I am having a hard time getting the PIA app on the FIreTV. I had it before and the FireTV was running so slow I had to wipe and start over. Now I downloaded the apk file and it says it can't parse the file.

Any help would be appreciated.
[Fire TV General] nhow:
Problem installing PIA on Fire Stick

I installed PIA on my gen 2 Fire Stick OK but when I logged into my user account there was no menu for changing country location. It only defaulted to Southampton or London (my general area).

OK, this is what happened when I tried to install PIA last night on a 2nd gen Fire Stick. According to other posters it should work on Gen 2 but not Gen 1 Fire TV Stick I've now had the same problem with both. No way to change location and doesn't change IP. Is there any way to install PIA in Kodi (not through main Fire Stick settings)?
[LeEco Le Pro3 Questions & Answers] jts2111:
So I tried several ROM (CM13, Google EUI, Stock) when I tried to revert back to stock. Immediately after rebooting I noticed an issue: the bootloader was in Chinese. I thought it might be fine, but when the phone booted up, the SIM (AT&T) was not recognized. The option for "Mobile Networks" is grayed out and even CM (from a backup) has this issue now. I already flashed the US Modem zip and it is still occuring. Anyone able to help?

Update: Fixed 100% by flashing old stock firmware of EUI and OTA updating to 20s. Bootloader and modem fixed.
[Xiaomi Redmi Note 3 Questions & Answers] Del369:
Hi Folks

I just bought my girlfriend a Redmi Note 3 SE (Kate) quick back story, she received it turned it on added a pin to it got called away, when she got back to it she couldn't remember the pin, bad news is she hadn't yet turned on Developer Mode or USB Debugging.

Original SW - MIUI 7.5 android 6.0.1, at least that's what the Ali product page says (Sorry it seems I can't post a link to the actual product)

This began last Friday, since then she has tried the following:-

Installed MI Suite and registered a gmail account - so far "device not recognised"

Applied for an Unlock code.

Unlocked the boot loader which seems to have been successful.

Flashed two different (stock) ROM's which completed successfully but both stuck while booting the phone.

One was:-

"kate_global_images_6.12.29_20161228.0000.00_6.0_global" not sure what the other was.

On trying a different ROM today she's now getting the following error:-

"Can't Flash in miflash. Not enough storage is available to process this command"

Tried different versions of the Flash tool including the Beta version but still getting the same error on each of them.

Ticked the "Clear Data" box in the Mi Flash tool but that doesn't help.

A bit stuck on what to try from here and any help would be greatly appreciated if you need any more info please let me know.
[Xiaomi Redmi Note 3 Questions & Answers] theoneofgod:
I had the same bootloop problem with the stock firmware and miflash and driver was a pain to get sorted out.

What versions of miflash have you tried and which firmware did you download from xiaomi?
[Xiaomi Redmi Note 3 Questions & Answers] Del369:
Hi thanks for the reply, unfortunately I need to wait for an answer on that as she's not around at the moment, but from what I can gather she has tried miuiflash 1, 2 and beta and i know she tried this which I'm assuming is a firmware - kate_global_images_6.12.29_20161228.0000.00_6.0_global (if it's not please let me know what we should be using) *edit, mind you that's one of the files that got stuck showing the out of space error.

I also forgot to mention the PC is a win 10 64bit..

Soon as I can get you a better answer on the above I'll post it.
[Xiaomi Redmi Note 3 Questions & Answers] theoneofgod:
I would have them try this version http://bigota.d.miui.com/V8.1.1.0.M...DI_20161202.0000.00_6.0_global_ac46ea44bd.tgz it's the latest fastboot ROM.

Make sure when you install miflash you are running in test mode so the drivers install properly and accept any prompts about driver signatures. That is important. I believe MiFLash_v20160401 worked for me. Also you know when you're in EDL when the front LED flashes red now and then.
[Xiaomi Redmi Note 3 Questions & Answers] Del369:
Ah so it wasn't a firmware, alright I've passed this on as soon as I hear back I'll post here, many thanks.
[Xiaomi Redmi Note 3 Questions & Answers] Del369:
I just checked the link for the 8.1.1.0 Firmware but it gives a 404 error on the page, I'll look on their site for an alternative, but if you do know of an alternative please let me know.

**edit Never mind a right click and copy link location got it. :)
[Xiaomi Redmi Note 3 Questions & Answers] Del369:
So the issue looks to be solved, so firstly many thanks "theoneofgod" for your input.

Unfortunately due to a rather dodgy internet connection I haven't managed to get further into it, but here is what I received:-

"I used the same Kate and used miflash beta version.. i did the same as i did on first attempt.. after succesfully flashing it, i turned it on (result:same stuck on booting)

i switch it back to fastboot mode.

flash it.

result error.

i then press power on for about 5 seconds or till the mi logo appeared.

unplugged the USB cable and plugged it in again.

then phone booted.

and

When miflash beta version recognized my phone as just a device not com port. i flashed it. (it was just flashing endlessly)

So i tried to refresh the page, it then showed my device with an id as com10

(I have a feeling this might be the important part)

i flashed that too, and then it worked didn't get that error " no storage" anymore.

I'm not sure though if that helped

Basically I'm saying that i was flashing 1 device with two different id.

So I'm thinking simply the device refresh actually did the trick, anyway it looks to be solved, that was 3 days of no fun, and that whole thing about hey submit an application for a bootloader unlock and then wait 2 or 3 weeks and we might even refuse it lol.

Thanks again for your help "theoneofgod" thanks meter pressed.
[Huawei Watch] samjoandco:
I am on Negalite Huawei-Rom NX v2.6 , on rooted watch having TWRP.

Can i flash the dev preview 2 without losing root and TWRP?
[Huawei Watch] junioramboy:
If there's a flashable version. But there's none that I know of.
[Sony Cross-Device General] Ahmad Tawfik:
I don't have a Sony smartphone and probably won't use your tool but really thank you for that tool ?
[Sony Cross-Device General] munjeni:
Update: Now sin can be extracted! :)
[Sony Cross-Device General] munjeni:
You can extract boot.img with it! :)
[Sony Cross-Device General] Hamidreza2010:
bro first thanks for your great tool.

you mean with this tool we can unpack kernel yes? ( with those command )

then how can repack it ( after do our change ) ?

sorry if this question is nooby
[Sony Cross-Device General] munjeni:
This is for unpacking only. :) You can read xda contain ton of tutorials related to how to pack boot image, just search please
[Sony Cross-Device General] munjeni:
Update:

now tool is able to extract any sin file and output it to converted.file
[Sony Cross-Device General] munjeni:
Sorry sin version 3 is not supported, I am working on it, only sin version 1 & 2 by now!
[Sony Cross-Device General] munjeni:
Now sin version 3 with lz4 compressed data is supported! Report bugs please if you get!
[Sony Cross-Device General] munjeni:
New version, improved non compressed sin files extraction, now for example 1.5 gb system.sin files can be extracted in just some secconds, amazing :)
[Sony Cross-Device General] munjeni:
Now versions for:

- Linux

- arm

- arm with pie

- Windows
[Sony Cross-Device General] russel5:
[MENTION=4120742]munjeni[/MENTION] thanks for this tool, great work. but :)

i'm trying your linux version and this tool not extract pagesize info and made broken boot.img, ie if i'm try extract kernel.sin your tool create boot.img (but it's a same sin file) and if i'm try extract .elf, tool create boot.img (but same elf)
[Sony Cross-Device General] munjeni:
You can't use folder out and boot.img from the same directory! Boot.img from ouy directory is nothing than temp file. In next version all temp files will ne deleted on app finish to prevent mess. Also next version will be working one for sin files, cutently I forgot to include spare data generation which cause non valid extracted big sin files e.g. system.sin, problem also is my compiler and can't fwrite bigger files that 2gb, tommorow I think I will finish all and finaly produce a valid tool.
[Sony Cross-Device General] SXUsr:
To be fair many of them don't work, I've even installed Linux on an old laptop to try and learn how to repack but always get stuck with "android boot magic not found" and googling hasn't helped at all. An updated guide really wouldn't go a miss.
[Sony Cross-Device General] munjeni:
Sin of big size - extraction is now working under linux 64-bit, need some small changes to do to get it working correctly! I am sorry I have removed 32-bit version since I have no idea how to make LFS working under 32-bit platform but have tried almost everything, no way. Please let me know if you have a tested and working example of the LFS for 32-bit windows! And tell me please which compiler you used!
[Sony Cross-Device General] munjeni:
Finaly fixed everything, now tool generates valid system.ext4, suport again for linux, for arm, for windows, tested only on linux and windows by now, tool support by now large files (LFS) and propertly generates output. If you find bugs please report. Please try on android since I have not tested. :good:

Edit:

Uh, downloaded z5 premium rom, extracted system.sin and tool failed on v3 sin, seems I forgot something in curently huge source code, will check tommorow sorry :( On z1 uncompressed images working flawles, since I have now z5 rom on my disk I will fix bug sorry :)
[Sony Cross-Device General] munjeni:
Newer sin e.g. system.sin contains mixed data, compresed and uncompresed, holy s I must rewrite half of the my code to get thing propertly parsed... Damn :(
[Sony Cross-Device General] munjeni:
Does android support off64_t on 32 bit toolchain anybody know?
[Sony Cross-Device General] munjeni:
finished. Now all types of the sin files can be extracted. Sin files decompression fail on 32 bit machines/devices if output file reach 0xffffffff bytes (4 gb) so everything after output of the 0xffffffff bytes (4 gb) is not a valid, I have no idea which toolchain have full 64 bit support on 32 bit platform so I am unable to make LFS (large files support) on 32 bit platfom. File output which is smaller than 0xffffffff bytes (4 gb) is valid on 32 bit platform. But on any 64 bit platform tool working flawless and you can extract any sin file so no problem with LFS and etc! I have tested on win10 64 bit and ubuntu 64 bit and can confirm that any sin files is extracted correctly. Tried on android 32 bit but file output which is smaller than 0xffffffff bytes (4gb) is a valid but till after file reach size of the 0xffffffff bytes (4gb) is no more valid. 32 bit platform is limited and we can do nothing on that. Not tried on 64 bit android but I am pretty sure it will work ok the same like on 64 bit windows and 64 bit linux.

This tool is primary designed for extracting any sony boot image format from, you can extract any boot image using this tool on 32 bit platform or on 64 bit platform without any problem, without cares to LFS! But for seccondary thing you can use to extract any sin file, on 64 bit platform it will success for sure but on 32 bit platform it is limited because LFS in my case is not working corectly on 32 bit platform if output of the file is bigger than 4 GB :)
[Sony Cross-Device General] munjeni:
While compared extracted sin with one of the flashtool I have noticed one or two blocks missing in my output file :(, it was since whileloop was wrong in one case, done some right small changes and now all case is ok, file is identic to one from flashtool, have verified booth output files by sha1 and it's identic.
[Sony Cross-Device General] munjeni:
Finally tool is abble to work on booth 32 bit and 64 bit linux, android and windows machine by fully supporting LFS, enjoy!
[Sony Cross-Device General] serajr:
Such amazing work! Congrats!! A must-have tool for sure!!!

Do you think it could possible to include this one in your tool?

Also dealing with Nougat's file_contexts.bin (unpack/repack maybe)?

Thank you!
[Sony Cross-Device General] munjeni:
Elf? My tool allready unpacks elf kernels, and one more thing autodetects 32 and 64 bit elf, and also one more extracts commandline from kernel, and allso create few other files like kernel offset, ramdisk offset and tags offset :) Also you can unpack things directly from block device, e.g kernel_dump out /dev/block/blalba.. Spent 8 days and almost 950 lines in source code, but sure I will investigate on file_context, just need to figure out format
[Sony Cross-Device General] serajr:
Thank you bro, tool is marvelous indeed! The swiss-knife of the kernels!!

Talking about code, we're used to managing large amount of them, eg my Xperia Home Xposed, its Hide Apps in Drawer feature class is reaching 2k lines of java code (1867 exactly) for a single feature (module has 35+ features).

I have no doubt you're gonna achieve it (file_contexts.bin). Keep rocking!!
[Sony Cross-Device General] munjeni:
Curently I need some free time to free my head :), I have figured file_contexts.bin format and made convertor (see attachment) and also provided source code, its just an consruction without checks and things, not a safe, just an very dirty app :), for safety unpacking you can inprove :), it converts to file based file_contexts but for reverting it back to binary you need to use android tool for it which is inside android source code in folder /android/external/libselinux/utils and tool name is sefcontext_compile, I didn't compiled that tool have no free time to mess with it, maybe later, but use filecont to convert to text mode & modify and use sefcontext_compile to revert back to binary :) Anyway text mode is working I think in ramdisk no need binary (unconfirmed curently)! Enjoy :)
[Sony Cross-Device General] serajr:
Really? Amazing as always! Thank you so much!!

I did that my own way too, directly inside tobias.waldvogel's tool (Z5 forum), using busybox (code below), which is very slow to perform read/write results, but works.

ctx=$(strings $contexts_bin | perform sed -n '/u:/,$p' | perform grep -B1 "/")
obj=$(echo "$ctx" | perform grep "/")
per=$(echo "$ctx" | perform grep "u:")
i=0
for obj_ in $obj; do
per_=$(echo ${per} | cut -d' ' -f$i)
# object tab pemission
echo -e >>$RAMDISK/file_contexts@0644 "$obj_\t$per_"
i=$((i+1));
done
[Sony Cross-Device General] munjeni:
New version of the filecont tool now in windows, linux and arm, and also new version of the kernel_dump tool, enjoy!

How to convert file_contexts.bin binary to plaintext file_contexts:

filecont file_contexts.bin file_contexts

You can use/modify these files and/or include them in your work as long as proper credits and a link to this thread are given.
[Sony Cross-Device General] munjeni:
New kernel_dump version. Removed part of the old mechanism related to sin version and file size detection, in some case cache.sin was failed to extract since file size calculation was wrong, now definitelly any sin file can be extracted
[Sony Cross-Device General] puargs:
Just wanted to say thank you so much for this tool. Really made things so much easier for me. I greatly appreciate the hard work. :good:
[Sony Cross-Device General] shoey63:
[MENTION=4120742]munjeni[/MENTION]

Brilliant tool this.

Nougat has just been released for Z5 but no FSC script in FlashTool by [MENTION=2807379]Androxyde[/MENTION], so I just ran the script and straight away got a flashable system.ext4 and kernel.elf directly from sin files.

Flashed and booted with no issues. Great Work!
[Sony Cross-Device General] munjeni:
Sorry I'm on z1c and... what mean FSC? :o

Edit:

Found what mean fsc and got some questions to op https://xdaforums.com/showpost.php?p=70595036&postcount=15 , do you know anything about it? Thx
[Sony Cross-Device General] Lefteris Fragiadakis (Frago):
Firmware. pkg of Sony android tv can be opened?
[Sony Cross-Device General] shoey63:
Just that some firmwares/devices need it and some dont. Good to know that your tool works if you want to avoid flashtool though.
[Sony Cross-Device General] munjeni:
Nop :)
[Sony Cross-Device General] munjeni:
New kernel_dump version. Redesigned a way for extracting boot.sin files, now it just convert to elf instead of unpacking it fully, so if you need to unpack fully just rerun tool with elf file. Also now we can convert on the fly and flash any sin file directly to block device, e.g

kernel_dump /dev/block/platform/msm_sdcc.1/by-name/system system.sin
[Sony Cross-Device General] munjeni:
I can confirm this is worked right now on my z1c :)

kernel_dump /dev/block/platform/msm_sdcc.1/by-name/system system.sin
[Sony Cross-Device General] munjeni:
We can use kernel_dump in flashable zip!? ;)
[Sony Cross-Device General] marisatomei:
Hello,

Nice tool, thanks for it :) Any plan to expand it to use it with the Sony TV Android firmwares? :angel:
[Sony Cross-Device General] munjeni:
Hi, since I don't have sony tv I realy have no idea what sony uses in their TV's, did fw of the tv contain sin files too?