yashsingh1/xdaforums huggingface dataset:
[General Topics] s3r10us:
How to Unpack and Pack a Recovery ROM Using Mio Tool

Part 1:

1. Download Recovery ROM:

- Obtain the recovery ROM for your device

2. Unzip the Recovery ROM:

- Extract the contents of the downloaded recovery ROM to a convenient location on your computer.

3. Open Mio Tool and Create New Project:

- Launch Mio Tool.

- Create a new project within the Mio Tool interface.

4. Open the Mio Tool Project Folder:

- Locate and open the folder you designated as the new project in Mio Tool.

5. Move/Copy Payload.bin File:

- Transfer the payload.bin file into the Mio Tool project folder.

6. Set Unpack Toggle in Mio Tool:

- In Mio Tool, select the payload folder.

- Set the toggle to "Unpack."

7. Run Unpacking Process:

- Click on the Run button in Mio Tool.

- Wait for the tool to successfully unpack all the files.

8. Select Pack Toggle and Choose Files:

- After unpacking is complete, select the "Pack" toggle in Mio Tool.

- Choose the following files: {odm, odm_dlkm, product, system, system_ext, vendor, vendor_dlkm}.

Part 2: Preparing PixelOS for Fastboot

1. Create ROM Folder:

- After packing all the files, establish a folder for your ROM, e.g., "PixelOs_Fastboot."

2. Move Super.img File:

- Transfer the packed Super.img file to the "PixelOs_Fastboot" folder.

3. Move Specific Files:

- From the Mio Tool project folder, move the following files to the "PixelOs_Fastboot" folder: {boot, dtbo, vbmeta, vbmeta_system, vbmeta_vendor, vendor_boot}.

4. Download and Unzip Firmware:

- Download the required firmware for your device.

- Unzip the firmware file and copy all its contents to the "PixelOs_Fastboot" folder.

5. Download and Unzip Platform Tools:

- Download the Platform Tools folder, commonly used for Android development.

- Unzip the Platform Tools folder and copy its files, including the scripts, and paste them into the "PixelOs_Fastboot" folder.

By completing these steps, you'll have organized the necessary files and prepared the "PixelOs_Fastboot" folder for the subsequent fastboot flashing process.

Mio Kitchen Tool Link: https://github.com/ColdWindScholar/MIO-KITCHEN-SOURCE

Credits to: https://github.com/ColdWindScholar/
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Tidystuart:
Hi,

I have an SM-G981B, it was originally contracted from Three however that's all paid off and as a 'hand me down' I have put my GiffGaff sim in it, flashed the latest BTU firmware via Odin however it still retains all the Three operating system / bloat. Is there any simple way to remove this without using ADB / in phone settings?
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Tidystuart:
Further to this, If I root the phone, install custom ROM, recovery, Kernel etc (tripping Knox in the process) would this do the trick? or is this operator stuff on another partition somewhere on the phone? for more info, the phone is actually HG3/EUX as stated in the 'Carrier ID' within fastboot.
[Samsung Galaxy S20 / S20+ / S20 Ultra Questions & ] Tidystuart:
Fixed for anyone looking in - Changed the CSC to BTU manually using SamFW Tool, then flashed BTU firmware. Carrier is gone :)
[LineageOS Questions & Answers] Feenix0:
It looks like some apps that can create PDF documents from the camera depend on the system camera rather than their own software to capture the images, and those apps can't seem to do so with the stock camera in LOS 20.

Here are some screenshots. The first is of the stock camera being set up to take a picture (not a scan) of the document:

View attachment 6068153

If I attempt to scan the document with Google Drive's scan feature, I get the same interface as above, and this is what I get after taking the shot. As you see, there is no cropping and no option to save the image as a document:

View attachment 6068154

I get this same behavior from a variety of scanning apps that appear to depend on the system camera.

Next, if I attempt a scan with Adobe Scan, this is the setup:

View attachment 6068155

...and this is the shot.

View attachment 6068156

This is the attempt with OneDrive:

View attachment 6068157

View attachment 6068158

As you can see, Adobe Scan and OneDrive scan both work, but appear to bypass the system camera in favor of their own camera implementation. I haven't been able to find any FOSS apps that don't use the system camera for scanning, and this is a problem because I'm looking to move away from apps that track me, such as OneDrive and Adobe Scan, in favor of open source apps and private cloud services -- Proton, in my case. Unfortunately, Proton Drive doesn't have a built-in scanner yet.

Any recommendations for FOSS apps that do what I need, or how to make the system camera work for this? I'm open to being educated if I'm obviously missing some important knowledge about this issue!
[General Questions and Answers] marxus79:
Good evening all. I am an absolute noob but i can follow steps pretty well. I have rooted my S10 with magisk and for a long time it worked flawless. Today while a was running a mock location app for argument reality game PoGo and was also running the game i forgot to leave the phone on charge and the phone died. So i restarted the phone while plugged into my PC with the usual vol up. Bixby power button combo. Root access is gained again but after few minutes the phone restarts and lose root. After 5 more tries is always the same thing. Anyone knows what might have happen and how to fix this problem.? Thank you
[Android Q&A, Help & Troubleshooting] abwalhsn005:
I have bought Samsung Galaxy S24 Ultra because of Real-time translation.

It was shocking for me that it does not support Arabic language (My native language). I searched about it and I found that, in last November, it was supporting two language only, Korean and Japanese, whereas is supports more than ten languages now.

obviously, it seems to be that more languages will be supported in the future.

But I am asking if there anyone knows a more official and accurate details about adding more language by Samsung.

I am really in need to know anything about that.
[Android Q&A, Help & Troubleshooting] KamfromCali:
The S23 Ultra supports arabic language. I wish the S24 Ultra did at launch.
[OnePlus Open] Jonnyswboy:
I disabled the OnePlus Photos app and use Google Photos. All works perfectly except in the camera app when you click the preview on the bottom left it tries to open the OnePlus photos app.

Any way to change this? It's not in the usual "default apps" area.

Thanks!
[OnePlus Open] Jonnyswboy:
Bump.

Is there nobody who has accomplished this? What about modifying the camera app somehow?
[OnePlus Open] FoxyDrew:
You can use a modded version of GCAM, but it's not perfect yet. But you can set your default gallery app.
[OnePlus Open] Jonnyswboy:
If I do manage to find a GCAM port + config is there even a way to change the double tap power button shortcut to GCAM?
[OnePlus Open] thesm4rt1:
Mind sharing which version of GCAM and config file you're using?
[OnePlus Open] Jonnyswboy:
https://www.reddit.com/r/OnePlusOpen/comments/17yeuu0

Still can't change the double tap power button shortcut... :rolleyes:
[OnePlus Open] thesm4rt1:
Thanks!

I used Tasker to detect Emergency Calling mode (3x power button presses) then open GCAM. There is a way to get the double tap on power but this was easier for me.
[OnePlus Open] Jonnyswboy:
What is the way?

Also, if you manage to get pictures out of GCAM that look as good as the stock camera app let me know. They looked significantly worse for me.
[OnePlus Open] thesm4rt1:
https://www.reddit.com/r/tasker/comments/etm6ee

I didn't spend too much time trying to import and get it running myself, volume to get to stock camera is good enough.

So far the GCAM pics are looking worse, not sure why people would use it over stock app. Especially if you consider the different modes available in the stock app
[OnePlus Open] Jonnyswboy:
Because you are forced to use the OnePlus Photos app.
[OnePlus Open] thesm4rt1:
Lucky Tool has an option to modify camera app to open last image/video taken with third party app (including Google Photos). You can keep swiping through photos taken from there, edit, share, etc.

Releases · Xposed-Modules-Repo/com.luckyzyx.luckytool

LuckyTool. Contribute to Xposed-Modules-Repo/com.luckyzyx.luckytool development by creating an account on GitHub.

github.com

Tested on latest IN rom .701.
[General Questions and Answers] wackowizzard:
Hi,

Does anyone know if it is possible to install custom transition animations (fade, fly-in, slide,...) in Android 14?
[Samsung Galaxy Watch 6] bikereep:
Has anyone had any luck in pair Autowear with their Watch 6? I've trawled through Google searched and tried some the options like adb pairing, then connecting then setting port 7272 through termux but no matter what I do, I cannot get Autowear to connect to the watch. Specifically I want to run Tasker tasks to mute / unmute etc. I contacted Joao but didn't get a response. Can anyone help?
[General Questions and Answers] ms1083:
I have discovered my galaxy a14 5g hasn't got band n28 for 5G activated because it's an import.

Is there any way to activate it? I have read about the app samsung toolkit unlock more and samsung band selection but neither seem to work on android 14.

Is there any way at all to get into the relevant secret menu or manually turn on inactive bands?
[General Questions and Answers] ajitshukla19:
Have you got any solution
[Touch Pro, Fuze General] tvos:
Would someone kindly point me in the right direction that will allow me to install codecs for the ppc. I am missing a codec for AC3? for audio playback.

I tried WM player, Coreplayer and no luck.

Please advise if there is a suite out there for instal.

Thank You,

tvos
[Touch Pro, Fuze General] jayk2100:
go to http://www.hpcfactor.com/downloads/tcpmp/ and get the plugins for tcpmp and tcpmp. find the smartphone cabs in the zip and copy them to the phone. install them by selecting them on the phone. It should then prompt for a save location and then install. coreplayer should then be able to playback the files.
[AT&T Samsung Galaxy S 5] A Cool User:
Temporary Unlock​

This is for the G900A (S5 ATT) ; Not the G870A (S5 Active ATT)​

DISCLAIMER:

* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.

What you need:​

A 4GB or bigger uSD card

A computer with Linux

The attached ZIP file

AT&T S5 on ABOOT (firmware) version G900AUCS4DQB1

Getting to the right firmware​

If you want your phone to still boot without a PC:​

Download G900AUCS4DPH4 and flash it in odin​

Download PH4-QA1.zip and QA1-QB1.zip

Flash both in recovery (Use ADB sideload from a computer or flash from uSD card)

The quick and dirty way (your phone won't boot anything but download mode) (MAY NOT WORK! IN TESTING!)​

Flash QB1 aboot.mbn (Included in the ZIP) ./heimdall flash --ABOOT QB1_ABOOT.mbn

Booting to TWRP​

Download/unzip the attached zip file

Open the folder in the terminal

Power off your S5

Put the uSD in your S5 and plug it in to your PC

Run bash main.sh -p && bash main.sh -t and follow the instructions

You should now be in TWRP!

Installing LOS (or your ROM of choice)​

Download your ROM (This should be for klte)

Run bash main.sh -z YOUR_ROM_FULL_PATH and follow the instructions

You should now be in your ROM!

Doing a normal boot​

When you need to reboot, follow this:

Run bash main.sh -b and follow the instructions

Big thanks to Frederic who made the POC this is based on!

Github Repo

POC Source
[AT&T Samsung Galaxy S 5] Ben Garp:
is this the way to unlock the bootloader?
[AT&T Samsung Galaxy S 5] A Cool User:
No - there is NO bootloader unlock. This is a exploit in Download Mode that allows flashing a custom ROM. It requires a PC to boot.
[AT&T Samsung Galaxy S 5] Ben Garp:
so why flash a 900 rom on a 870 device?
[AT&T Samsung Galaxy S 5] A Cool User:
This is FOR the G900A - NOT the G870
[AT&T Samsung Galaxy S 5] Ben Garp:
ok sorry thanks
[AT&T Samsung Galaxy S 5] A Cool User:
Thanks for asking... Forgot to add that it was for G900A at the top of the post.
[AT&T Samsung Galaxy S 5] Moonwalker89:
Can I possibly use part this to get into twrp on this phone so I can erase my screenlock and it still be ok to go back to normal? I dont want to do anything except delete my screenlock pin in there.. Just want to make sure before I go and do somethin I dont want to do by mistake cuz its my daughters phone and I told her i'd do my best to get in it and not erase anything lol. My life is in yall's hands right now lol.
[AT&T Samsung Galaxy S 5] A Cool User:
This will only work if you are on firmware G900AUCS4DQB1. You should be able to flash the ABOOT from QB1 to do it. Sometimes Samsung has downgrade protection... Something like this should work:

Reboot into recovery to get current OS version

Download that OS update zip from the web. (If your OS version is G900AUCS4DQA1 for example, download the G900AUCS4DQA1 update zip, and extract the aboot.mbn from it.)

Reboot into download mode

Flash the QB1 ABOOT (In the first post)

Reboot in download mode again

Run and follow the exploit to boot into TWRP

Do whatever you want there

Reboot back into download mode

Flash the ABOOT from step 2

Reboot the phone (It SHOULD boot fine)

NOTE: If the ABOOT version does not match the system version, the phone will not boot anything but Download Mode (which is embedded into the ABOOT)!

TIP: You can extract data right from TWRP to be safe.

Also, i'm not responsible for any data loss lol.
[AT&T Samsung Galaxy S 5] Moonwalker89:
Thank you for the quick reply brother. Thanks so much for the guidance as well God kniows I need it these days, I have forgotten quite a lot. **** bro, mine is sayin this so I guess this wont work for me.

Model Number : SM-G900A

Region Code : SM2G900AZKAATT

Device Version info :->>

BL version : G900AUCS4CPA4

AP version : G900AUCS4CPA4

CP version : G900AUCS4CPA4

CSC version : G900AATT4CPA4
[AT&T Samsung Galaxy S 5] A Cool User:
Well you can still do the steps I gave you in my previous post. Since that is Android 5, this might work...

tl;dr

You can flash the QB1 ABOOT, reboot to download mode, run the exploit, and then downgrade back to CPA4 ABOOT.
[AT&T Samsung Galaxy S 5] Moonwalker89:
O wow your awesome my man thank you so much bro!! I hope it works lol.
[AT&T Samsung Galaxy S 5] ethical_haquer:
Just one question (at least before I begin :) ) - If I follow the above steps, do I still have to use a computer to boot? Or is the stock ROM still installed and you just boot into that if you don't have a computer?

I'd be installing a custom ROM, and possibly rooting.
[AT&T Samsung Galaxy S 5] A Cool User:
You (unfortunately) have to boot with a PC. You theoretically could partition it so you could dual boot, but it would probably be hard.
[AT&T Samsung Galaxy S 5] ethical_haquer:
Thanks for the reply!

What would happen if say, you're battery ran out? Or if you accidentally rebooted "normally", without a computer? What would the state of the phone be in then?

Also, what are you running on your G900A?

TIA.
[AT&T Samsung Galaxy S 5] A Cool User:
I am running Android 13 but have also ran 14. If you reboot, you would boot to the "Unauthorized software found on your device" (HAHA yes AT&T I AM running LOS) state. If you need to reboot (Like you updated Magisk or something) then reboot directly to download mode, and run the program on your PC.
[AT&T Samsung Galaxy S 5] ethical_haquer:
:ROFLMAO: The beginning of a post I was writing:

So yeah, I get that page right after LOS is done loading. I then used the -b flag and rebooted again into LOS, but after the loading symbol I go right back to that page. I'm trying out the Android 13 LOS. TIA.
[AT&T Samsung Galaxy S 5] ethical_haquer:
Here's what happens after the loading symbol:

Black screen,

Vibration,

Black screen with this text:

SYS REV CHECK [K] : No Version
SECURE: SECURE VERSION failure (boot. img)

Software not authorized screen with this text in upper left corner:

SECURE FAIL: KERNEL

I'm thinking it's probably something I did (I had to do certain things multiple times), so should I try redoing the process?

TIA.
[AT&T Samsung Galaxy S 5] ethical_haquer:
Also, I've always gotten output like this, after doing flashes where I hold down vol-down and home:

Uploading BOOT
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: BOOT upload failed!

Ending session...
ERROR: Failed to send end session packet!
Releasing device interface...

Is that part of the exploit?
[AT&T Samsung Galaxy S 5] A Cool User:
Sorry I didn't see this until now (notifications weren't working for some reason... 😝)!

Yes, that is normal. It is because the exploit exits Download Mode, instead of rebooting.

Yeah, I got that one a lot to. LOS just crashed and rebooted for some reason. It seemed to happen at first for a while. I ended up switching to Android 11, which has been stable for ~2 weeks. I might reinstall Android 13 and look at the logs at some point to see why it crashes.
[AT&T Samsung Galaxy S 5] ethical_haquer:
No problem, I've had the same thing happen to me!

👍

Alright, thanks for replying!

I was about to ask what OS you used, to see if that might have something to do with it, but now I'll try again with LOS 11.

I also want to try out DivestOS. I learned about it when I looked at this helpful table. (BTW he has multiple other tables as well, links are at the top of that one I linked to)
[AT&T Samsung Galaxy S 5] A Cool User:
That is a very nice table! Thanks! It also looks like you can get DivestOS based on Android 11, if the latest version doesn't work.
[AT&T Samsung Galaxy S 5] ethical_haquer:
👍 Yeah, klte is listed under "18.1 / 11.0 / Red Velvet Cake / END OF LIFE" for DivestOS. Probably because it's a fork of LOS, which only officially supports the S5 up to 18.1. That's fine though, I don't need A13 for anything.
[AT&T Samsung Galaxy S 5] ethical_haquer:
Well, trying to use DivestOS turned out differently...

After the loading symbol it rebooted into Recovery.

I get this text in Recovery:

"can't apply symbolic in '/system/csc/ATT/csc_contents' -> '/system/csc_contents' (Permission denied)"

I turned the phone off and then used bash main.sh -b, but got the same result.

So, it didn't boot properly, but at least it did something different. :ROFLMAO:

Trying LOS A11 next.
[AT&T Samsung Galaxy S 5] ethical_haquer:
Experiencing the exact same issue with LOS 18.1.

I have some questions:

When TWRP starts up (right before flashing the ROM), should I do anything when it asks about the system and read-only?

Is it normal for white text to scroll while in Download mode?

TIA.

EDIT: I finally got it!

It took me a dozen tries, but I'm now in LOS 18.1.

So my original issue was that LOS 20 was rebooting.

I didn't realize that, but thanks for telling me.

The second issue, the one that was causing the permission error, was that I had prepared the phone improperly, somehow.

I got that permissions error multiple times due to this, before I decided to do "The quick and dirty way" to get to the proper firmware.

Then I was able to successfully flash LOS 18.1. (So that method worked for me)

I still plan on trying to flash DivestOS, now that I know how, but this is just great, running a custom ROM on an un-lockable device!

I really appreciate your help!
[AT&T Samsung Galaxy S 5] A Cool User:
Glad it ended up working! Very interesting that doing "The quick and dirty way" made it work...
[AT&T Samsung Galaxy S 5] ethical_haquer:
(y) I just flashed DivestOS with no issues.

Except it was kind of weird because it basically just "updated" LOS to DivestOS.

A factory reset in Recovery and then re-flashing DivestOS fixed the issue. 😊

I would recommend trying it out; the only issue I'm having is that the camera app crashes, but LOS 18.1 had the same issue. The camera issues (and actually auto rotate as well) could be related to the dirty flash though: link.
[AT&T Samsung Galaxy S 5] SoneCorTam:
Can someone help me, I get stuck at this part. doesn't boot into rom.

Installing LOS (or your ROM of choice)​

Download your ROM (This should be for klte)

Run bash main.sh -z YOUR_ROM_FULL_PATH and follow the instructions

You should now be in your ROM!

waiting for TWRP...

Turning on ADB sideload

adb: no devices/emulators found

Sideloading ROM

adb: sideload connection failed: no devices/emulators found

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: no devices/emulators found

adb: no devices/emulators found

Waiting for device...

what am i doing wrong here.....
[AT&T Samsung Galaxy S 5] A Cool User:
Duplicate, DELETE.
[AT&T Samsung Galaxy S 5] A Cool User:
Did you flash the right ABOOT? Try following the "Getting to the right firmware" section of the first post. This is a TETHERED exploit though, so your gonna need your PC every time you boot it.
[AT&T Samsung Galaxy S 5] SoneCorTam:
Tell me if i am doing something wrong.

1. Flash G900AUCS4DPH4 (using Odin)

2. PH4-QA1.zip & QA1-QB1.zip (flash both zip file using ADB sideload) while phone is in recovery mode (vol button up + home + power)

3. than go back into download mode ( heimdall to flash the QB1-aboot.mbn in the ATT Exploit folder )

4. than i Run bash.sh - p && bash main.sh -t (while in download mode) than it boots into TWRP mode..... what do i in TWRP? format data?

5. Run bash main.sh -z ROM FILE.zip ( and this is where it boot back into TWRP and try to do the adb sideload but won't work )
[AT&T Samsung Galaxy S 5] A Cool User:
It looks like your doing everything right... For now just run this (in the exploit folder):

1. Boot into TWRP:

bash main.sh -p && bash main.sh -t

2. Wait for TWRP to load

3. Start ADB sideload (manually or by running this):

adb shell twrp sideload

4. Wait for ADB sideload to start

5. Sideload your ROM:

adb sideload /path/to/your/rom.zip

6. Wait for sideload to be done

7. Reboot to Download mode (manually or by running this):

adb shell twrp reboot download

8. Extract/Flash the boot image of your ROM:

unzip -d /tmp/ /path/to/your/rom.zip boot.img
bash main.sh -i /tmp/boot.img
[AT&T Samsung Galaxy S 5] SoneCorTam:
Thank you, i got it to boot into the rom, but i think my rom is bad or no good because it will be stuck on the DivestOS logo for like 10 mins and reboot into recovery mode, won't log into the rom. Where can i get a good 18.1 LineageOS complete zip file?
[AT&T Samsung Galaxy S 5] ethical_haquer:
Does Recovery Mode say anything?

I had the same issue. Here's how I fixed it.
[AT&T Samsung Galaxy S 5] SoneCorTam:
Thank you thank you, got it to bot into rom. My only problem now is the APN setting for the mobile network, i can't seem to add my own in there to get my phone working again on the Spectrum Mobile (Verzion piggy back) so i am not getting any services.
[AT&T Samsung Galaxy S 5] ethical_haquer:
Hmm, I'm not exactly sure what you're talking about; Is it an issue with VoLTE, or something else? If you can still receive/send messages but can't call it's probably VoLTE.
[AT&T Samsung Galaxy S 5] SoneCorTam:
Got lineageOS 18.1 install, everything working Great, just can't use it with Spectrum Mobile for now, but my tmobile sim card work fine on it. awesome guys. Thanks for the help.
[AT&T Samsung Galaxy S 5] puddingtiger:
Hi! I'm looking to perform some data recovery on my old G900A, and need root access to create a Nandroid backup for this purpose. It sounds like flashing just "aboot.mdn" instead of the full firmware theoretically allows it to be downgraded without wiping any user data, but has anyone actually tested this yet? For reference, I'm currently running the QD1 firmware on Android 6.0.1. Of course there's always some risk of data loss when rooting, but it would definitely be nice to at least get confirmation that this is possible. Any help would be very much appreciated!