how can i make a Bypass Firehose File for Poco x3 Pro?? please someone help me! my Phone hardbricked!
this is the FireHose File of Poco x3 Pro Global Stable 12.0.6.0 version
prog_ufs_firehose_sm7150_ddr.elf
i cant find any of it in Google or YouTube
my Phone is Dying..
Thought sm7150 is SD 730 series. Sure looking on correct phone?
pl1992aw said:
Thought sm7150 is SD 730 series. Sure looking on correct phone?
Click to expand...
Click to collapse
Authorized Account is needed to flash in MiFlash
PHnambawan said:
Authorized Account is needed to flash in MiFlash
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/poco-x3-pro-hard-bricked.4277803/post-85025433
PHnambawan said:
how can i make a Bypass Firehose File for Poco x3 Pro?? please someone help me! my Phone hardbricked!
this is the FireHose File of Poco x3 Pro Global Stable 12.0.6.0 version
prog_ufs_firehose_sm7150_ddr.elf
i cant find any of it in Google or YouTube
my Phone is Dying..
Click to expand...
Click to collapse
when looking the file within hex editor i found :
IMAGE_VARIANT_STRING=SDM855LA
OEM_IMAGE_VERSION_STRING=c4-xm-ota-bd033.bj
QC_IMAGE_VERSION_STRING=BOOT.XF.3.0-00571-SM8150LZB-4
abit looking at web i found it using sdm855 which lead me to LG G8 Thread
Link to SDM 855 Programmer Firehose file, QPST, VOLTE configs, ABL/XBL files inside
Here are all the required files to root the LG G8 Reuploaded from the pan.baidu.com links via this page: https://bbs.lge.fun/thread-110.htm Link to the relevant LG v40 root method that uses a very similar process...
forum.xda-developers.com
blakdulz said:
when looking the file within hex editor i found :
IMAGE_VARIANT_STRING=SDM855LA
OEM_IMAGE_VERSION_STRING=c4-xm-ota-bd033.bj
QC_IMAGE_VERSION_STRING=BOOT.XF.3.0-00571-SM8150LZB-4
abit looking at web i found it using sdm855 which lead me to LG G8 Thread
Link to SDM 855 Programmer Firehose file, QPST, VOLTE configs, ABL/XBL files inside
Here are all the required files to root the LG G8 Reuploaded from the pan.baidu.com links via this page: https://bbs.lge.fun/thread-110.htm Link to the relevant LG v40 root method that uses a very similar process...
forum.xda-developers.com
Click to expand...
Click to collapse
soo.. should it work?
PHnambawan said:
soo.. should it work?
Click to expand...
Click to collapse
i dont know im not testing it, since my phone not bricked.. yet
PHnambawan said:
soo.. should it work?
Click to expand...
Click to collapse
Doesnt work for me. Even tried patching strings
OEM_IMAGE_VERSION_STRING
QC_IMAGE_VERSION_STRING
(REplaced them from original xiaomi firehose)
PHPoenX said:
Doesnt work for me. Even tried patching strings
OEM_IMAGE_VERSION_STRING
QC_IMAGE_VERSION_STRING
(REplaced them from original xiaomi firehose)
Click to expand...
Click to collapse
did you found firehose file or found a way to bypass mi authorization..>???
simonastani said:
did you found firehose file or found a way to bypass mi authorization..>???
Click to expand...
Click to collapse
I tried to use firehoses from 855 and 855+, they didnt work. My patched variant(based on 855 with edited revision strings) didnt work too
Also, I found out that there is some type of integrity or signature check. I cant load firehose with one edited byte in log string
Still there is no solution for edl flashing
PHPoenX said:
I tried to use firehoses from 855 and 855+, they didnt work. My patched variant(based on 855 with edited revision strings) didnt work too
Click to expand...
Click to collapse
Same here . tried all the solution... possible option left.
1. Research to modify firehose file and try bypassing mi edl authentication.
Did you try flashing other official Flashable rom like of oxygen os with same chipset 860...
simonastani said:
1. Research to modify firehose file and try bypassing mi edl authentication.
Click to expand...
Click to collapse
PHPoenX said:
Also, I found out that there is some type of integrity or signature check. I cant load firehose with one edited byte in log string
Click to expand...
Click to collapse
Exploiting Qualcomm EDL Programmers (1): Gaining Access & PBL Internals
Research & Exploitation of Qualcomm EDL Firehose Programmers: From PBL (Boot ROM) Extraction, Research & Analysis to Secure Boot Bypass in Nokia 6. (Part 1)
alephsecurity.com
Patching ELF files
blog.elfy.io
elfy.io | ELF viewer and editor Online
ELF viewer and editor
elfy.io
Thereis no auth firehose but thereis miflash mod no auth in some technician toutuber. One thing i notice by tecnician do server/remote service they can change vayu to edl mode via fasboot, no need test point btw this trick is remain hidden/secret since they all make money from it.
I patched prog_ufs_firehose_sm7150_ddr for no auth... is anyone want to try it, contact me.
Zibri said:
I patched prog_ufs_firehose_sm7150_ddr for no auth... is anyone want to try it, contact me.
Click to expand...
Click to collapse
Upload it please , i want to try
ugers said:
Upload it please , i want to try
Click to expand...
Click to collapse
there is nothing to try.. I checked it, and it does not boot. I have to analyze if it's protected by itself (self check) or it's checked bu the previous loader for integrity... but if you change even a single byte it does not boot. Perhaps SBL checks ABL.
Zibri said:
I patched prog_ufs_firehose_sm7150_ddr for no auth... is anyone want to try it, contact me.
Click to expand...
Click to collapse
Can you please explain how did you find auth code?
Zibri said:
there is nothing to try.. I checked it, and it does not boot. I have to analyze if it's protected by itself (self check) or it's checked bu the previous loader for integrity... but if you change even a single byte it does not boot. Perhaps SBL checks ABL.
Click to expand...
Click to collapse
Afaik, PBL checks firehose. What do you mean by "boot"? Is flashing with your patched loader succeeds?
I did not find any auth code.. I just reverse engineered firehose and patched it to skip the check... but as I said.. after further analysis, I failed because any patch to firehose cause it not to run.
Related
Hello All,
Seems UE has Qualcomm MSM8226 Snapdragon 400,
which is a the same as the S3 mini/HTC mini.
I have a question, if anyone can shed some light on it.
In the Android FS, there is a file imei.bin usually in /data/rfs/data/ some path, can't remember exactly.
If this file was to be modified, how would things work? Or is this file only for the AP level stuff, because ultimately the modem connects to the network, i'm guessing this file is just read out of the modem at boot time?
what is MSL? I have seen a number of commercial tools available which can repair IMEI, just wondering why they can do it.
Would I need to be rooted in order to read/write to the modem fd?
Thanks AJ
There is not rfs on our g
Hello,
Please could you advise:
" There is not rfs on our g "
I managed to get QPST talking to the modem, by making the modem go to bootloader mode, then set it to BP tools...
I got 3 USB ports one of which is QC Diag Port, I installed drivers..
Then started NV Editor and read the PAGE files from the modem......
I changed some digits, then tried to write. QPST does not return any error or issues, however nothing has changed on the device.
I am guess the modem FD (part where the NVRAM is stored) is READ_ONLY as the UE is not rooted.
Thanks Aj
aj4u said:
I am guess the modem FD (part where the NVRAM is stored) is READ_ONLY as the UE is not rooted.
Thanks Aj
Click to expand...
Click to collapse
Do u succeed ?
rgonera said:
Do u succeed ?
Click to expand...
Click to collapse
Read only!
This mod enables the earpiece to be used as a secondary speaker while playing music or videos.
Disclaimer : I'm not responsible for any damage to your device.
Downloads : Releases
Youtube [RM3 Pro] :
Steps :
Download the modified mixer [Normal or Boosted]
Rename it to original mixer file name [Only if you have downloaded the boosted version]
Copy the modified mixer file and paste it into /system/vendor/etc
Replace the original mixer
Reboot
Done
Credits :
Dante63 for his mega-guide
Reserved
Thanks. That's really nice of you except that no-one could unlock their bootloader or get root permission yet. Correct me if I'm wrong but did you mange to do that? Have you successfully tested this mod?
greenys' said:
Thanks. That's really nice of you except that no-one could unlock their bootloader or get root permission yet. Correct me if I'm wrong but did you mange to do that? Have you successfully tested this mod?
Click to expand...
Click to collapse
Files provided by and tested by user on RMQ.
Regards,
acervenky
acervenky said:
Files provided by and tested by user on RMQ.
Regards,
acervenky
Click to expand...
Click to collapse
That's pretty great I guess but still without root we can't do this, we can't access system folder. How did the mentioned user achieve root permission? What do I do to duplicate the scenario? Some kind of tutorial would be great. Thanks.
greenys' said:
That's pretty great I guess but still without root we can't do this, we can't access system folder. How did the mentioned user achieve root permission? What do I do to duplicate the scenario? Some kind of tutorial would be great. Thanks.
Click to expand...
Click to collapse
They achieved root using patched boot image, after managing to unlock bl via patched indepth tool.
I've uploaded stock images for CN variant, Realme has not released any for IN Realme 5 Pro yet!
Regards,
acervenky
acervenky said:
They achieved root using patched boot image, after managing to unlock bl via patched indepth tool.
I've uploaded stock images for CN variant, Realme has not released any for IN Realme 5 Pro yet!
Regards,
acervenky
Click to expand...
Click to collapse
I see. What about Realme Q that I ordered from China? I tried in-depth tool but it says phone model doesn't support in depth test.
acervenky said:
They achieved root using patched boot image, after managing to unlock bl via patched indepth tool.
I've uploaded stock images for CN variant, Realme has not released any for IN Realme 5 Pro yet!
Regards,
acervenky
Click to expand...
Click to collapse
indepth tool no support realme Q and realme 5 pro....
greenys' said:
I see. What about Realme Q that I ordered from China? I tried in-depth tool but it says phone model doesn't support in depth test.
Click to expand...
Click to collapse
Did they flash global rom on it? Or is it still CN?
Anyway I don't own the device and patching the device detection seems like a very dangerous way.
Wait for RealMe to release the instructions!
29y6145 said:
indepth tool no support realme Q and realme 5 pro....
Click to expand...
Click to collapse
It will eventually support them.
Regards,
acervenky
acervenky said:
Did they flash global rom on it? Or is it still CN?
Anyway I don't own the device and patching the device detection seems like a very dangerous way.
Wait for RealMe to release the instructions!
It will eventually support them.
Regards,
acervenky
Click to expand...
Click to collapse
Seems like it's still China. After all it only supports English and every Asian language by default. None other European or global languages. I guess I'll wait for source code release. It indeed seems more safe.
Doesn't work
I did everything but double speaker doesn't work. Can some kindly fix it?
Madhuvrata said:
I did everything but double speaker doesn't work. Can some kindly fix it?
Click to expand...
Click to collapse
Which rom are you using?
Upload your mixer files!
Regards,
acervenky
acervenky said:
Which rom are you using?
Upload your mixer files!
Regards,
acervenky
Click to expand...
Click to collapse
I've tried on LOS and on stock. On LOS there is no effect at all. On stock I can't change system partition to rw. I spend yesterday whole day for it but can't change. Without rw you cant replace the files. Do you know how to change permission of system to RW?
Ps. In few minutes I will upload files you asked
Above I've attached original file from stock rom.
The permissions are read only, and cant change it. Is it possible to make some flashable .zip file to get these permissions on system partitions changed?
Is there any way to get this work?
Madhuvrata said:
Above I've attached original file from stock rom.
The permissions are read only, and cant change it. Is it possible to make some flashable .zip file to get these permissions on system partitions changed?
Click to expand...
Click to collapse
Madhuvrata said:
Is there any way to get this work?
Click to expand...
Click to collapse
This is the same mixer that I've edited, to be able to mount vendor r/w flash the r/w permissions fix zip via TWRP.
Regards,
acervenky
Sorry, my mistake for file, I'll send in one hour proper one. But where can I get this fix for permission you have mentioned? Could you give link please?
I've attached proper file from stock room A.13. Could you please provide link to fix of the rw permissions?
acervenky said:
Which rom are you using?
Upload your mixer files!
Click to expand...
Click to collapse
Any chance to get this mid working on r5pro?
Must be phone rooted?
I made a video explaining how google blocks 5G in the software by default for unlisted countries.
I also tried posting this on reddit at r/googlepixel but mods deleted it.
I think this information should be spread to the wider general public because it affects just about every one of us here, having to root our phones to enable 5G, when this should just be enabled out of the box with absolutely no tinkering required.
If a phone is advertised as "5G ready", we should expect to be able to connect to our carrier's 5G network out of the box, regardless of being in a "supported country" or not.
This video shows that carrier-google certification is not necessary to connect to your carrier's 5G network.
I wonder if it's possible to file a class action lawsuit because blocking 5G in the software clearly has to be some sort of "misleading" or "false advertising" in terms of the phone being "5G" ready.
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
swangjang said:
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases/tag/0.13
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
Click to expand...
Click to collapse
Thanks, I agree making this thread was a good idea.
I managed to pull the modem.img from the device.
To find which partition has what installed:
su
ls -la /dev/block/bootdevice/by-name
To pull the modem partition:
su
dd if=dev/block/sda12 of=/sdcard/modem_a.img
dd if=dev/block/sda13 of=/sdcard/modem_b.img
Unfortunately, it's not organised in folders to something like mcfg_sw/generic/*
but instead, it's all labeled in numbers.
They also can't be extracted using the method in post #2.
5G now working on my P5 with Free Mobile in France. Thanks for this post
swangjang said:
I managed to pull the modem.img from the device.
To find which partition has what installed:
su
ls -la /dev/block/bootdevice/by-name
To pull the modem partition:
su
dd if=dev/block/sda12 of=/sdcard/modem_a.img
dd if=dev/block/sda13 of=/sdcard/modem_b.img
Unfortunately, it's not organised in folders to something like mcfg_sw/generic/*
but instead, it's all labeled in numbers.
They also can't be extracted using the method in post #2.
Click to expand...
Click to collapse
@swangjang I have a quick question for you, before I rooted and started flashing roms and kernels but after I unlocked my bootloader I had the ability to record phones calls through the Google phone app but I only used it once so I stopped paying attention to the phone app while I was using it but I just recently noticed that I can no longer record phone calls, the record button is no longer present when I'm using the phone. I live in the US and that option is available for us but I no longer have the option, is there any chance you could help me get that option back ?
elong7681 said:
@swangjang I have a quick question for you, before I rooted and started flashing roms and kernels but after I unlocked my bootloader I had the ability to record phones calls through the Google phone app but I only used it once so I stopped paying attention to the phone app while I was using it but I just recently noticed that I can no longer record phone calls, the record button is no longer present when I'm using the phone. I live in the US and that option is available for us but I no longer have the option, is there any chance you could help me get that option back ?
Click to expand...
Click to collapse
I don't know much about it either lol. As far as I know, phone call recording was supposed to be removed from Google Phone app due to recording laws. Maybe you somehow had the beta version of the app and it got updated?
I use skvalex's recording app. You have to pay for premium after a free trial and it's quite costly for an app but I don't regret paying for it. It records both sides internally so bluetooth calls are also recorded both sides.
Something that might be worth considering if you can't find a way to get it back.
swangjang said:
I don't know much about it either lol. As far as I know, phone call recording was supposed to be removed from Google Phone app due to recording laws. Maybe you somehow had the beta version of the app and it got updated?
I use skvalex's recording app. You have to pay for premium after a free trial and it's quite costly for an app but I don't regret paying for it. It records both sides internally so bluetooth calls are also recorded both sides.
Something that might be worth considering if you can't find a way to get it back.
Click to expand...
Click to collapse
Thanks for your quick reply and the app reference
swangjang said:
@elong7681
In reply to your other question. (proton rom thread may not be the best thread to discuss this)
carrier_policy.xml file is located inside the carrier mbn file.
To extract the mbn file, you need:
Efs Tools https://github.com/JohnBel/EfsTools/releases/tag/0.13
dotnet-core https://dotnet.microsoft.com/download/dotnet-core/3.1
dotnet https://dotnet.microsoft.com/download/dotnet/5.0
1. Install dotnet-core and dotnet
2. Copy mbn file into the efstools folder
3. Run in command prompt: EfsTools.exe extractMbn -i mcfg_sw.mbn -p mcfg
4. New folder (mcfg) will be created and mbn file will be extracted inside.
Carrier_policy.xml is inside the "policyman" folder.
This video will also explain how the mbn files are used to enable or disable 5G.
Click to expand...
Click to collapse
Hi, this is helpful, but it would be great if you could give further detailed instructions as to how to enable 5G for unsupported carriers. In other words, what needs to be done after step #4 above (editing and copying of files)?
Also, would this process work is a dual sim configuration?
Thanks for your expose!
nsiti said:
Hi, this is helpful, but it would be great if you could give further detailed instructions as to how to enable 5G for unsupported carriers. In other words, what needs to be done after step #4 above (editing and copying of files)?
Also, would this process work is a dual sim configuration?
Thanks for your expose!
Click to expand...
Click to collapse
There are tutorials in other threads in this forum on how to do that. But if written guides are difficult to follow (not judging, the guides assume you have some PC knowledge and it took me a while to understand them too), I can make a video showing step by step process this weekend.
I'm not sure about dual sim 5G. 5G DSDS (Dual Sim Dual Standby) was only just implemented in March update and I don't have a 5G esim to test it.
swangjang said:
There are tutorials in other threads in this forum on how to do that. But if written guides are difficult to follow (not judging, the guides assume you have some PC knowledge and it took me a while to understand them too), I can make a video showing step by step process this weekend.
I'm not sure about dual sim 5G. 5G DSDS (Dual Sim Dual Standby) was only just implemented in March update and I don't have a 5G esim to test it.
Click to expand...
Click to collapse
@swangjang that would be awesome
elong7681 said:
@swangjang that would be awesome
Click to expand...
Click to collapse
Seems it's not necessary any more.
Finally , One Module-unlock 5G-Volte-VoWIFI
Hello,, After a long term of tries and workarounds. Finally found some module by ender-zhao :love::love::love::love::love::love: Thanks for him so much. Simply one module to enable 5G and Volte ,vowifi... install it from magisk , restart and...
forum.xda-developers.com
I haven't tried it yet but it seems promising.
swangjang said:
Seems it's not necessary any more.
Finally , One Module-unlock 5G-Volte-VoWIFI
Hello,, After a long term of tries and workarounds. Finally found some module by ender-zhao :love::love::love::love::love::love: Thanks for him so much. Simply one module to enable 5G and Volte ,vowifi... install it from magisk , restart and...
forum.xda-developers.com
I haven't tried it yet but it seems promising.
Click to expand...
Click to collapse
@swangjang if it isn't too much trouble and you have the time I personally think it would still benefit the community if you did that video tutorial because being able to do it manually would teach people how to do it versus using a simple magisk module either way thank you for your help and work thus far.
@swangjang is it possible to flash the Google and Qualcomm binaries and if so can you point me in the right direction?
elong7681 said:
@swangjang is it possible to flash the Google and Qualcomm binaries and if so can you point me in the right direction?
Click to expand...
Click to collapse
Sorry, I'm not sure what you mean by that...
swangjang said:
Sorry, I'm not sure what you mean by that...
Click to expand...
Click to collapse
They are located here https://developers.google.com/android/drivers Maybe this will help explain my question
elong7681 said:
They are located here https://developers.google.com/android/drivers Maybe this will help explain my question
Click to expand...
Click to collapse
Oh. I have no idea lol.
swangjang said:
Oh. I have no idea lol.
Click to expand...
Click to collapse
Ok I appreciate your response, besides the XDA Developers website is there any other websites like this one that you can recommend ?
elong7681 said:
Ok I appreciate your response, besides the XDA Developers website is there any other websites like this one that you can recommend ?
Click to expand...
Click to collapse
To my knowledge, I don't there are any other alternatives that's English based.
I still dont understand, do I need to root my device to do this?
Hi all, I am a new owner of the ROG Phone 5 Tencent version. I got it from Jingdong(a Chinese Amazon-like platform) and I have been busy flash my phone for the last couple of days. Now I got my phone converted to WW(sort of) and I am going to start using it as my regular phone - bye-bye Oneplus 6.
It's actually a back and forth process of the conversion. I manage to get the phone converted to WW at the first attempt. However, I am not happy with the HardwareStub warning message and the fact I am not able to receive OTA. Then I restore my phone back to CN version and try to live with the CN version. I tried to debloat + install GApps however I don't like it. Last night I flash my phone with the latest WW firmware.... again. I still hate this HardwareStub notification, so I decompiled the HardwareStub apk. From the source code, I found a function checking the value of the property ro.boot.image.valid. If this property is not "Y", then the warning message will be set and persist on the notification bar. Then I use dumped all the props from adb shell to verify the theory. Yes, it's not "Y".
[ro.boot.image.valid]: [N]
I also noticed some other props that still indicating CN flag despite all others using WW.
[ro.boot.country_code]: [CN]
[ro.boot.product.override]: [CN_I005D]
[ro.build.description]: [CN_I005D-user ***build number***]
[ro.odm.build.fingerprint]: [asus/CN_I005D/ASUS_I005_1 ***build number***]
[ro.vendor.build.fingerprint]: [asus/CN_I005D/ASUS_I005_1 ***build number***]
This makes me wondering:
1. If all the CN flags change to WW, does this change the ro.boot.image.valid to Y?
2. Is it possible to change mentioned props?
Note: I am not a rom customization expert so I might be asking nonsense questions...
The conversion guides all mention modifying the CN values.
Yes, I did modify the vender/factory/COUNTRY file content from CN to WW. I didn't see any other places that need to be modified from the tutorial I have seen. Maybe I missed something....
twistedumbrella said:
The conversion guides all mention modifying the CN values.
Click to expand...
Click to collapse
At this moment, flash WW rom and change COUNTRY file only give us a 90% conversion and leave some itchy problems. I am thinking more about "perfect" conversion. Let's say if we could find a way to make all above props correct (WW) does it give us a perfect conversion? I am not sure you get my point. Maybe it's not a thing at all.....
bleachwind said:
Thanks for your advice, just a quick question. Besides change /vender/factory/COUNTRY file, what else need to be modified during the conversion?
Click to expand...
Click to collapse
twistedumbrella said:
I'm not sure. Mine arrived as WW
Click to expand...
Click to collapse
bleachwind said:
So I guess your one is converted version as well. Would you mind check your props got any "CN" value by run getprop? Thanks
Click to expand...
Click to collapse
twistedumbrella said:
There are none
Click to expand...
Click to collapse
bleachwind said:
Cool, thank you very much!
Click to expand...
Click to collapse
Quoted from
Anyone having trouble install Netflix?
Hi all, I just noticed my Netflix app is not usable after convert CN to WW. ROM: Tencent device with 86(latest) WW firmware. Cannot find the Netflix app in Play Store. Installed manually from APK and the app says "The device is not support by the...
forum.xda-developers.com
There is two additional things to look at it ..
1) asuskeys partition backup all of it
And u will notice that asus key 4 has CN written in it and need to be modified using hex editor .. and by help of computer u have to flash twrp and reboot to fastbootd using command fastboot reboot fastboot to flash asuskey back with modification of ww
The extra thing which i could not trigger is when u go to setting /system /about phone /software information /(baseband version) of CN is different than WW .. need special way to change that and i cannot figure it out
bleachwind said:
Yes, I did modify the vender/factory/COUNTRY file content from CN to WW. I didn't see any other places that need to be modified from the tutorial I have seen. Maybe I missed something....
Click to expand...
Click to collapse
How did you change it?
I don't have access to modify it through root explorer or TWRP.
JazonX said:
How did you change it?
I don't have access to modify it through root explorer or TWRP.
Click to expand...
Click to collapse
I believe one way is to unpack the image, modify it, and flash it back. It should be the vendor partition (or vendor_boot). Hopefully, there is a better way. That's tedious.
twistedumbrella said:
I believe one way is to unpack the image, modify it, and flash it back. It should be the vendor partition (or vendor_boot). Hopefully, there is a better way. That's tedious.
Click to expand...
Click to collapse
I don't think OP chose this path, for the obvious reasons.
I did it in the ROG 2 / ROG 3 both with Root Explorer, But was unable to do it in the ROG 5 due to Android 11.
@bleachwind - Any thoughts, comments ?
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Win_7 said:
how do i get the samsung screen recorder and secure folder on my a226b and or any other samsung ad i dont have them for some reason and i would like to know if theres any universal twrp or odin thing to flash that would gove them back or maybe secret setting to enable or apk to install
Click to expand...
Click to collapse
There Isn't a screen recorder or secure folder on the SM-A226B you can use calculator+ and flash a android 13 GSI to use the screen recorder.
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
fede2782 said:
You can enable screenrecorder by modifiying some lines in /system/etc/floating_feature.xml
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
<SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>-pip</SEC_FLOATING_FEATURE_FRAMEWORK_CONFIG_SCREEN_RECORDER_ITEM>
Without spaces. If there is already the value simply change to this. I'm working on a way to enable secure folder in my free time. First tests were successful however there are still some problems. I'm extracting files from A13 5G (SM-A136B) because it has the same chipset as A22 5G and has secure folder
Click to expand...
Click to collapse
thanks!!!! will this work on any other phone other than a226b?
and do you know of any file manager app that can actually edit system files (i have a good one called filemanager+ but it can only read even if i do mount -o remount,rw /
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (https://www.apkmirror.com/apk/samsu.../samsung-capture-5-4-22-android-apk-download/) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
eh thats ok i used adb and accepted root on device
my phone didnt have the file is that ok if i just create it?
also you made a mistake on the url can you send a working one?
fede2782 said:
Yes, it should. If this doesn't work there is another line that may need to be changed. Make sure you have at least one ui 3. Updating Samsung Capture may be required (Here's where you can download latest apk) Let me know.
I do not know any good file manager because I modify system files with Magisk. You can use termux. Pull file to pc or use quick edit on phone.
Click to expand...
Click to collapse
um how can i fix "system partition doesnt have enough free space" when trying to convert newer samsung capture to system app
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
fede2782 said:
You don't need to convert. Just update with apk when phone on. Like every app. I made a mistake in the link. I fixed it. The file should exist on every Samsung one ui device.
Click to expand...
Click to collapse
oh bruh i deleted system app and reinstalled
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
fede2782 said:
An apk of Samsung capture must remain in the /system partition in order to get priv-app permissions
I recommend you to reinstall original firmware (One UI 5.1 if it is available in your region) then modify floating_feature.xml.
This file is placed in every samsung device in /system/etc/floating_feature.xml
You do not have to create nothing. Just modify it add that lines. In my firmware (official one UI 5.1) the second line is already placed in the file. So I simply added:
<SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>TRUE</SEC_FLOATING_FEATURE_FRAMEWORK_SUPPORT_SCREEN_RECORDER>
in the middle of the file
Click to expand...
Click to collapse
i still didnt have the file i made it and updated capture but didnt get screen recorder even after reboot :/ am on android 11 and im not updating especially as theres bootloader update
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
fede2782 said:
For me it is working. The file floating_feature.xml needs to exist. if it doesn't exist this means your firmware version is old and it doesn't have modern one UI. I don't know how I can help you more
Click to expand...
Click to collapse
i have a70 with screenrecorder its on android 10
my a22 is on oneui 3.1
I don't know.
fede2782 said:
I don't know.
Click to expand...
Click to collapse
alright then sorry for bothgering you
Win_7 said:
alright then sorry for bothgering you
Click to expand...
Click to collapse
Don't worry
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
fede2782 said:
Image clipper wip being prepared! Object Eraser! deCorizer - Add missing One UI features to A22 5G
You can flash this Magisk module AT YOUR OWN RISK. I AM NOT RESPONSIBLE for lost warranty, bootloops, lost data or any other damage to your device. THE SOFTWARE IS PROVIDED “AS IS” This module tries to add as many One UI features as possible to...
forum.xda-developers.com
Click to expand...
Click to collapse
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Win_7 said:
it didnt work
it just said system is root and a couple other things then i rebooted nthing
Click to expand...
Click to collapse
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
fede2782 said:
At the moment is only for DWC1 OXM
I'll try to download your file from AVA1 as soon as I can and I'll patch it
Click to expand...
Click to collapse
i have AVA6 not 1