Related
Hello everybody! I recently bricked my s7e by trying to install the superman mod because I was jumping between two guides and just followed the chapter for flashing the new bootloaders and not the beginning about twrp and so on.
Now I've done everything more carefully and thoroughly and executed the file for disabling dm verity and encryption. However I want to know if it is really disabled because I don't want to make the same mistake and have to reset me device again. Can you guys help me with how I check the status of em verity and encryption? I've tried to reach but just finds posts about people having the verification fail issue.
Thanks
Anyone our there that can help me or give me an idea?
Open a TWRP root shell and type:
Code:
surya:/ # avbctl get-verity
verity is disabled.
surya:/ # avbctl get-verification
verification is disabled.
lebigmac said:
Open a TWRP root shell and type:
Code:
surya:/ # avbctl get-verity
verity is disabled.
surya:/ # avbctl get-verification
verification is disabled.
Click to expand...
Click to collapse
Does it have to be with TWRP because Pixel 5 A12 doesn't have TWRP yet
elong7681 said:
Does it have to be with TWRP because Pixel 5 A12 doesn't have TWRP yet
Click to expand...
Click to collapse
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release (see link in my signature). Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification
lebigmac said:
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release. Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification
Click to expand...
Click to collapse
Can you send me a link to where I can find your tools?
lebigmac said:
No. You can run the same command in Android too and it will work. You can find avbctl binary in /tools subfolder of my SystemRW release (see link in my signature). Good luck!
Bash:
adb shell
su
./tools/avbctl disable-verity
./tools/avbctl disable-verification
Click to expand...
Click to collapse
Trying to use this on a slightly more out of date system. Is it possible to get you to release your tools in 32bit?
strayedsoul2003 said:
Trying to use this on a slightly more out of date system. Is it possible to get you to release your tools in 32bit?
Click to expand...
Click to collapse
I'll try to compile a 32 bit version sometime in the future but I can't say when. Just subscribe to the thread in my signature and you should be notified if there's any update
Wish me luck! Thanks
elong7681 said:
Can you send me a link to where I can find your tools?
Click to expand...
Click to collapse
Just click the link in my signature
elong7681 said:
Can you send me a link to where I can find your tools?
Click to expand...
Click to collapse
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
I'm quite disappointed with camera quality, pics look nice overall but awful when zoomed - lack of details, water paint effect, so on.
So I decided to look into camera settings located at /system/etc/camera folder. There are many XML files with a lot of settings, but I lack knowledge to understand them :/ For example, one is really interesting: camera/davinci/default/imgproc.xml with content like this:
Code:
<Config>
<Global>
<InvalidYuvCorrec>0</InvalidYuvCorrec>
<NoiseReducFlag>1</NoiseReducFlag>
<ContrastEnhanceFlag>1</ContrastEnhanceFlag>
<SharpnessEnhanceFlag>0</SharpnessEnhanceFlag>
<ColorManageFlag>1</ColorManageFlag>
<MaskGuidedContrastFlag>1</MaskGuidedContrastFlag>
<MaskGuidedSharpnessFlag>1</MaskGuidedSharpnessFlag>
</Global>
<NoiseReduction>
<ISO1>
<isovalue>100</isovalue>
<NoiseReducFlag>1</NoiseReducFlag>
<ContrastEnhanceFlag>1</ContrastEnhanceFlag>
<SharpnessEnhanceFlag>1</SharpnessEnhanceFlag>
<ColorManageFlag>1</ColorManageFlag>
<luma>-100</luma>
<chroma>-85</chroma>
<lumaHF>-85</lumaHF>
<chromaHF>-90</chromaHF>
<detail>-100</detail>
<shading>1.0</shading>
<percentLow>0.2</percentLow>
<percentHigh>0.8</percentHigh>
<diffusion>0.8</diffusion>
<alphaLUT>0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 128</alphaLUT>
</ISO1>
[...]
<ContrastEnhancement>
[...]
</ContrastEnhancement>
<SharpnessEnhancement>
[...]
</SharpnessEnhancement>
So it look promising, maybe we can tweak post-processing to not be so aggressive?
I have the same interest but maybe Mate9 has reached its limitation in camera aspect so I dont have any hope for this.
Now that's interesting! Thank you for digging this up. I'd love to play around with those settings and see if they have any actual effect on the JPEGs. I am sure the RAWs are left as-is though.
I'm gonna mess with this file also, by making magisk module maybe
But I lack free time right now, so it will took me few days I think...
Any news on how the experimentation is coming along?
I did some changes blindly (because I don't understand all settings) but no effect in camera.
I lack free time right now, so my tests are postponed until next week I think.
I did some poking around too. The thing I noticed is that all those xml files also exist under /product (this seems to be unique to Huawei). I think that's the real location. I had previously tried to make a magisk module to overwrite the camera apk with the one from the P10, but there was no change when I applied it to /system. That's when I noticed that the apk and the xml files also lived under /product. I haven't looked into any further, but my initial attempt to get magisk to replace files on /product failed. I'm pretty new at this though, so it may just be that I have no idea of what I'm doing.
All that to say, I would try playing with the files under /product as well. If you need someone to help test some settings, let me know. I'm interested as well.
It's possible that /product is not automounted by magisk, so your changes are overwritten when android mounts it. I didn't verify that it's just an idea.
@tim.malone I did some investigation and camera files are located at /vendor also. Magisk magic mounts works only for /system and /vendor partitions, it does not work with /product, I don't really know if it's possible to handle it without changes in magisk itself.
But I made module replacing files in all 3 locations and I'm gonna check if camera reacts to my modifications tomorrow. Maybe right place is /vendor partition?
I will be interested to hear about your results. Unfortunately, if I recall correctly, the settings files located in /product seemed more specific (I think they had file names that referenced the image sensor in the phone) and thus more likely to be the right ones. I could be wrong though. I think you're right that magisk just can't touch /product without some modifications. I might try to just directly edit the files and see what happens. Maybe I can at least make camera crash.
rufik said:
@tim.malone I did some investigation and camera files are located at /vendor also. Magisk magic mounts works only for /system and /vendor partitions, it does not work with /product, I don't really know if it's possible to handle it without changes in magisk itself.
But I made module replacing files in all 3 locations and I'm gonna check if camera reacts to my modifications tomorrow. Maybe right place is /vendor partition?
Click to expand...
Click to collapse
Yes, /product and /vendor differs a lot, see 3-way comparison in attachment. The main difference is that /product has imx286dual folder and default folder is missing.
Before you try to make direct modifications in /product or /vendor, please, do a TWRP backup of these partitions. You can easily mess up with them with bootloop as result. Maybe i'll try it also in next few days...
Quick test - I've made magisk module to put modifications (check attachment) into /system/etc/ and /vendor/etc/ successfully. What I've modified is to set various flags to 0 in ScenesTypes section, ex:
Code:
<NoiseReducFlag>0</NoiseReducFlag>
<ContrastEnhanceFlag>0</ContrastEnhanceFlag>
<SharpnessEnhanceFlag>0</SharpnessEnhanceFlag>
<ColorManageFlag>0</ColorManageFlag>
And you can find two shots in attachments - original without any modifications and modified. Do you see any difference in picture quality?
I did twrp flashable to replace imgproc.xml file in /system, /vendor and /product dirs. Magisk can handle only /system and /vendor, so I have to alter these partition through TWRP unfortunately.
You can find 2 test pics (full 12MP res) before and after my applying modification: https://drive.google.com/drive/folders/0B6Z0_2ag0vJVWHMwSDJsalQ1U2M?usp=sharing
Anyone can see any difference?
Hmm, I don't see a difference. I wonder if you need more extensive edits to the file. It would be nice if it was a little clearer what all the settings do.
I have no idea what the settings do :/ I just changed it blindly.
If you would like to poke with them, I can share my TWRP flashable zip.
I thought id put together a thread with all my main tweaks and modifications to allow our device to perform better
lets start!
Decrypt
this ones an easy one - flash noverity and decrypt and you're on your way right?
i took this a step further and modified the boot.img for 4.7.6 to remove encryption and verity and added some mount flags
the flags ive added are:
noatime - noauto_da_alloc - nodiratime - data=writeback - barrier=0 - nobh
you can google to find out more information about these flags, but they all deliver top performance with minimal risk (possible risk: sudden power off may result in data loss)
How to
easy! *required /data to be formatted if you are not already decrypted
flash the modified boot image: https://drive.google.com/open?id=1WItoR1ifuCRYXwBvzBdis3hUnCftlUd-
format /data
flash supersu / magisk if you were rooted otherwise stay stock
if you want to flash a kernel you need to replace the fstab.qcom with the modified version (to do this open the kernel zip and paste over the fstab.qcom)
kernel fstab.qcom: https://drive.google.com/open?id=1XRI5EWwREnvxCVWrjY4FFu1PQs1bbUje
Disable journaling completely
my favourite tweak - disables journaling
How to
i like doing this before first boot but you can do it whenever really
ideally in TWRP
first, explorer /dev/block/
for every file you see in /dev/block you add tune2fs -O ^has_journal before it
so for example, if /dev/block has a file called sdd01
you will type: tune2fs -O ^has_journal /dev/block/sdd01 in TWRP terminal
and so on for sdd02 etc etc (or you can create a script to do this for you) it will not succeed on all blocks as some dont have this features.
DOES NOT WORK ON 5T FOR SOME REASON WILL NOT BOOT INTO OS AFTER THIS IS DONE
Misc tweaks
some other tweaks i have not tested to see if they're working on the 5T
but here they are
How to
Scripts (you can run on boot or on demand):
fstrim (requires busybox): https://drive.google.com/open?id=1MSqvVlOr59Y8y-3DiJ3Snms_rEvJWVzX
sqlite vaccum and reindex database: https://drive.google.com/open?id=1NcW33rvoInQPSx9w8RcQ__GC_5Vhv-6a
also requires this file in xbin: https://drive.google.com/open?id=1p2COCUjhiAaIjyZjV84EmvUgntp0_bdi
zipalign: https://drive.google.com/open?id=1wWyfoy6QuVCtwUUkI9TVrobNbv7Kset8
also requires this file in xbin: https://drive.google.com/open?id=1K25bOrA7eVUacHEVrHNN2At6D-Dnfgmi
mark disk as non-rotational,disable iostats, simple iomerges no hash lookup, rq_Affinity set to 2 - best for multitasking uses all cores to complete request instead of cpu 'group' : https://drive.google.com/open?id=1YJ5GHGqwl8tzxvRyEGYINPIp4zdHUgTd
Stock Boot 4-7-6
https://drive.google.com/open?id=1OQKJB9gRj2SG7WS9J-ucuUaWmqPn1gMl
Stock Boot 4-7-6 no flags, decrypt no verity
https://drive.google.com/open?id=1gXYYw7E2fzSRkh2J-1hZIS4EH34zeBPT
if anyone has any other tweaks they'd like to share ill be sure to add them in!
THIS WORK IS OPEN TO ANYONE FOR USE
FREE KNOWLEDGE FOR ALL
Thank for the tips, could you post the boot img for 4.7.6 with out the flags being set.
freegame619 said:
Thank for the tips, could you post the boot img for 4.7.6 with out the flags being set.
Click to expand...
Click to collapse
updated OP
Hi @virtyx
I'm sorry I'm hijacking this thread but I can't find answers to my questions anywhere.
Why would you decrypt the phone ? Why is useful ? Does TWRP can't read from the sdcard partition if the phone is encrypted ? What can't you do with an encrypted phone ?
Everybody is talking about decrypting the phone but nobody says why is it for.
raptor2003 said:
Hi @virtyx
I'm sorry I'm hijacking this thread but I can't find answers to my questions anywhere.
Why would you decrypt the phone ? Why is useful ? Does TWRP can't read from the sdcard partition if the phone is encrypted ? What can't you do with an encrypted phone ?
Everybody is talking about decrypting the phone but nobody says why is it for.
Click to expand...
Click to collapse
in my experience decrypting makes the phone perform better (people will argue it makes no difference) but every time ive done it i notice improvement.
twrp is fine for reading the sdcard, decrpytion has its benefits but also drawbacks (easier to hack, etc) you can do the research yourself, but there are benchmarks showing the differences (mainly reads are affected)
if you're smart with your phone (i.e dont download suspicious stuff) you should be fine without encryption.
ive never had it on, except when i cant turn it off
raptor2003 said:
Hi @virtyx
I'm sorry I'm hijacking this thread but I can't find answers to my questions anywhere.
Why would you decrypt the phone ? Why is useful ? Does TWRP can't read from the sdcard partition if the phone is encrypted ? What can't you do with an encrypted phone ?
Everybody is talking about decrypting the phone but nobody says why is it for.
Click to expand...
Click to collapse
To run decrypted ROMs mainly. I see no other reason but im curious too
Since some ROMs can only boot if you are decrypted i guess it's that
Did a very quick lookup of that journaling business and it sounds interesting. Have you noticed much of a difference in performance on vs disabled?
virtyx said:
updated OP
Click to expand...
Click to collapse
I was mentioning about the boot img without the flags being set not the one without the encryption turned off.
freegame619 said:
I was mentioning about the boot img without the flags being set not the one without the encryption turned off.
Click to expand...
Click to collapse
oh ok sorry i thought you meant stock boot.img
updated.
showofdeth said:
Did a very quick lookup of that journaling business and it sounds interesting. Have you noticed much of a difference in performance on vs disabled?
Click to expand...
Click to collapse
definitely found better responsiveness with it disabled, and multitasking is much better
Can u help me to create script for disabling journal? I had 100 files on block folder ?
Oh and also, can I flash ur modified boot.img on 4.7.5? Because I haven't got system update to 4.7.6. it would be troubling me if I had to reflash the whole 4.7.6 rom since I had around 300 apps installed. Thanks before btw
andrizmitnick said:
Can u help me to create script for disabling journal? I had 100 files on block folder
Oh and also, can I flash ur modified boot.img on 4.7.5? Because I haven't got system update to 4.7.6. it would be troubling me if I had to reflash the whole 4.7.6 rom since I had around 300 apps installed. Thanks before btw
Click to expand...
Click to collapse
Shouldn't have a problem booting 476 on 475 but you need to test
virtyx said:
oh ok sorry i thought you meant stock boot.img
I am on OB1 oreo, encrypted, oreo compatible twrp, rooted with magisk 15.2, the boot image available here are for nougat, is it possible you can do it for oreo, or any help towards this, thanks for your help, Regards.
Click to expand...
Click to collapse
vtec303 said:
virtyx said:
oh ok sorry i thought you meant stock boot.img
I am on OB1 oreo, encrypted, oreo compatible twrp, rooted with magisk 15.2, the boot image available here are for nougat, is it possible you can do it for oreo, or any help towards this, thanks for your help, Regards.
Click to expand...
Click to collapse
when I get time I'll look for the oreo boot img
Click to expand...
Click to collapse
virtyx said:
vtec303 said:
when I get time I'll look for the oreo boot img
Click to expand...
Click to collapse
ok thanks mate, cheers.
Click to expand...
Click to collapse
Hi , so apperntly the only way currently to modify system files of OnePlus 8 Pro is through flashing magisk modules , Tried using several file explorers but couldn't change permissions , tried via twrp but system won't be mounted , so my question is if there is a magisk module that someone made to mount r/w , if there is , I would like to get it , if there isn't , I would appreciate if anyone can create that for me , and please don't tell me to go to terminal and type commands because IT DOESN'T WORK, I don't know exactly what flashing magisk modules do but I figured out that it's the only way I can change system files , please help
Mounting system as R/W is impossible on stock software (OOS, OneUI etc).
This applies to all devices launched with Android 10, so, 7T/Pro and up.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Your best shot is to create a module that 'modifies' the system systemless-ly.
Lossyx said:
Mounting system as R/W is impossible on stock software (OOS, OneUI etc).
This applies to all devices launched with Android 10, so, 7T/Pro and up.
https://source.android.com/devices/tech/ota/dynamic_partitions/implement
Your best shot is to create a module that 'modifies' the system systemless-ly.
Click to expand...
Click to collapse
That's literally the magisk module i'm asking for
ilan0098 said:
That's literally the magisk module i'm asking for
Click to expand...
Click to collapse
Literally not. You asked for a module that could make system R/W.
Anyway good luck
As mentioned, no r/w module...
galaxys said:
As mentioned, no r/w module...
Click to expand...
Click to collapse
Anyway such a module won't do any good IMHO. System/product/vendor partitions are combined into a single "super" partition.
The individual parts for /system, /vendor, /product are then mounted from there.
You will never be able to physically write on files in those partitions (if that is/was your intention).
However, you can write a Magisk module (easily) which replaces files with others (e.g. I replaced my /system/etc/hosts files with a version that has ad-blocked IP addresses). You can "delete" files by making them "empty" with a Magisk module (e.g. I have hidden the OnePlus phone/dialer/calculator/messages/notes apps in this way as I prefer the Google variants).
It's not that hard ... assuming you have a bit of Linux dev skills.
Can you be more specific about what exactly you want to do? Edit some file?
foobar66 said:
Anyway such a module won't do any good IMHO. System/product/vendor partitions are combined into a single "super" partition.
The individual parts for /system, /vendor, /product are then mounted from there.
You will never be able to physically write on files in those partitions (if that is/was your intention).
However, you can write a Magisk module (easily) which replaces files with others (e.g. I replaced my /system/etc/hosts files with a version that has ad-blocked IP addresses). You can "delete" files by making them "empty" with a Magisk module (e.g. I have hidden the OnePlus phone/dialer/calculator/messages/notes apps in this way as I prefer the Google variants).
It's not that hard ... assuming you have a bit of Linux dev skills.
Can you be more specific about what exactly you want to do? Edit some file?
Click to expand...
Click to collapse
Also if I do want to edit a system file , I can't , it won't let me do that , the file I edited just won't save
foobar66 said:
Anyway such a module won't do any good IMHO. System/product/vendor partitions are combined into a single "super" partition.
The individual parts for /system, /vendor, /product are then mounted from there.
You will never be able to physically write on files in those partitions (if that is/was your intention).
However, you can write a Magisk module (easily) which replaces files with others (e.g. I replaced my /system/etc/hosts files with a version that has ad-blocked IP addresses). You can "delete" files by making them "empty" with a Magisk module (e.g. I have hidden the OnePlus phone/dialer/calculator/messages/notes apps in this way as I prefer the Google variants).
It's not that hard ... assuming you have a bit of Linux dev skills.
Can you be more specific about what exactly you want to do? Edit some file?
Click to expand...
Click to collapse
I would very much like to edit the build.prop file, and let Adaway (F-droid) edit the hosts file to add its adblocking lists.
Are either of those things possible? Thanks!
R2-Brute said:
I would very much like to edit the build.prop file, and let Adaway (F-droid) edit the hosts file to add its adblocking lists.
Are either of those things possible? Thanks!
Click to expand...
Click to collapse
Enable systemless hosts in magisk manager and adaway will work. And for editing build prop, look up "resetprop", it's a magisk tool to modify build prop systemlessly.
Thank you so much! Adaway is up and running! I just got a new phone, and got so worried when it dawned on me that the System folder was locked down!
And I found "MagiskHide Props Config". Is it better or worse than Resetprop, or the same? "Props Config" has already flaked on me in the half hour I've been using it, but since a reinstall, it's working again.
I'm hoping it's just getting comfortable, but if you think Resetprop is more stable, please tell me.
And thanks again! Feeling good about technology.
I have ROOTED, rooted mean now you are Administrator of all in your phone. But live is not like a dream, I can't delete or modify anything in system folder on my rooted samsung phone, when using Z Archiver to delete empty and junk folder it says failed even sometimes it says Access Denied ( maybe the problem is here) converted RO->RW, tried through ES File it says in use or busy, Root Explorer is useless even if I adds write permission, but when using lucky patcher to uninstall & install and apps as system then it can creates or delete in systm app, which means there may be a way for me to modify it, if the trash can't be deleted then the system partition will be filled with garbage forever and can only get fatter. Who know how to solve it?
You have to patch super image to make everything r/w.
[GUIDE] How to make your System RW / Super R/W read/write-able
Welcome to the one and only, the original, universal SystemRW / SuperRW feat. MakeRW / ro2rw by lebigmac This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware. This allows you to mount...
forum.xda-developers.com
in case someone still struggling with that
i wanted to copy trusted certificate ".0" file from storage to /system/etc/security/cacerts
i couldn't and tried to do the adb mount thing but i couldn't
anyway it worked when i tried MT manager ( i literally shocked ) its not in play store but you can find it online
if that didn't work i guess you have two option
1) open platform tools after enabling usb debugging and do "adb push /sdcard/yourfile /system/etc/security/cancerts
that will copy the file from sdcard to system/etc/security/cancerts
second option i didn't really tried but i saw it worked for some
is magisk module called "overlayfs" if you can't find it online i will attach it here
BUT before all that try MT manager .. idk how it really worked lol
Mazen550 said:
in case someone still struggling with that
i wanted to copy trusted certificate ".0" file from storage to /system/etc/security/cacerts
i couldn't and tried to do the adb mount thing but i couldn't
anyway it worked when i tried MT manager ( i literally shocked ) its not in play store but you can find it online
if that didn't work i guess you have two option
1) open platform tools after enabling usb debugging and do "adb push /sdcard/yourfile /system/etc/security/cancerts
that will copy the file from sdcard to system/etc/security/cancerts
second option i didn't really tried but i saw it worked for some
is magisk module called "overlayfs" if you can't find it online i will attach it here
BUT before all that try MT manager .. idk how it really worked lol
Click to expand...
Click to collapse
i have installed overlay fs but i can edit only /system, /product and some files in /vendor and /system_ext, i have android 13 with one ui 5.1
This can:
Bypass TMO flash lock as it uses 9008 EDL.
Remove TMO sim lock and oem lock as you will be using global rom.
Convert your KB2007 (KB09CB) to KB2005 (KB05AA) as much as possible. (Although you're using the latest KB2005 firmware, any LineageOS stuff, such as LOS system,LOS recovery and LOS fastbootd, will still recognize it as KB2007. This is the same in OOS 11. But in OOS 12 system, it shows and acts like a KB2005.)
Should enables dsds (dual sim dual standby) in OOS 12. (Not tested. But status bar shows two empty sim slots in KB2005 OOS 12. After I flash LOS 19.1, slot 2 won't act unless boot with "persist.radio.multisim.config=dsds" prop.)
Give you access to Global OxygenOS firmware. (Bye slow TMO~)
Probably give you better overall condition (e.g. partition) than some fastboot scripts, as it's done directly by 9008 EDL.
AND THIS WILL DELETE ALL YOUR DATA ON DEVICE!!!
Actually, you should be able to change any brand device to any version you like by this method, but take your own risk as nothing is solid tested.
This can't:
Give you a second IMEI. (In OOS IMEI2 is "null". I guess it's hard baked somewhere.)
Remove TMO flash lock or unlock a locked bootloader. (You still need unlock token for that.)
You tell me please. I don't have enough time to test everything.
Please:
BE AWARE THAT YOU ARE RESPONSIBLE FOR WHAT YOU DO TO YOUR HARDWARE, NOT ME.
MY SUCCESS DOESN'T MEAN IT MAST HAPPENS TO YOU.
YOU ARE THE ONE WHO TAKE ALL THE RISKS. (And your phone, too.)
Be kind to other readers and help them, I can't stay online all day, sorry.
Why:
I own a fully unlocked KebabT running LineageOS 18.1, and I decided to try LOS 19.1 out.
But OOS 12 firmware is so buggy that it even broke my LOS instance, and the fastboot (not fastbootD, for hell reasons I can't enter LOS recovery AFTER ALL firmware upgrade) is also too buggy to fix my issue.
I unbricked my phone using this " https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180981/ " (Thanks for sharing!!!), but only to find that TMO firmware is so old, buggy and limited.
Then I googled and found this "https://www.droidwin.com/convert-oneplus-t-mobile-metro-to-global-on-locked-bootloader/" and this "https://github.com/bkerler/oppo_decrypt" ,but they are slightly outdated and doesn't fit kebab.
I fetched global firmware from here "https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/" (Thanks for sharing!!!) and started trying.
After a few tries I succeed and decided to share what I found.
How:
Firstly, know your hardware. Especially your ram type (ddr4 or ddr5) !
Then follow what this "https://www.droidwin.com/convert-oneplus-t-mobile-metro-to-global-on-locked-bootloader/" said, BUT WITH EXTRA MODIFICATION on your "settings.xml":
1. Overwrite "BasicInfo Project", "Version", "ModelVerifyPrjName", "ModelVerifyRandom" and "ModelVerifyHashToken", these makes you pass MsmDownloadTool's pre-check.
2. Scroll to the end of file and overwrite [Target ID="1" Desc="O2"] with [Target ID="101" Desc="TMO"], otherwise your flash won't begin as the tool can't find right hardware to flash.
3. Search for "Image ID=" and modify the results. For me, I have a DDR4 device, so I go with "xbl.img" and "xbl_config.img", so FOR ME I change "Image ID="1"" to "Image ID="101"", and change "Image ID="65537"" to "Image ID="65637"". Otherwise MsmDownloadTool won't be able to locate the right xbl img file to flash.
4. Follow the rest of that great guide and have a few tries, you won't lose more as you're already under EDL mode. Wish you success!
And:
Sorry in advance for any possible confusion as I'm not a native English speaker. You can ask in replies!
Please let me know if I'm wrong, I'll try to correct.
If this is already shared by other great guys, please forgive me as I really didn't find any related post in this forum.
I doubt this "https://forum.xda-developers.com/t/...m-unlock-or-bootloader-unlock-needed.4188491/" (Thanks for sharing!!!) is done in the same way but no one mentioned about it.
Special thanks to bkerler for creating this awesome "https://github.com/bkerler/oppo_decrypt" project!
Special thanks to LuK1337 for maintain LineageOS for OnePlus 8T!! You're great!!
Question:
It it possible to remove flash lock in this way?
I've tried several times to flash with kebab not kebabT MsmTool. But I can't make it work.
I can fix in os12 but need rw or unpack repack rom
Mr Hassan said:
I can fix in os12 but need rw or unpack repack rom
Click to expand...
Click to collapse
I don't understand.
Fix what or unpack what?
Is this what you need? "https://github.com/bkerler/oppo_decrypt"
I'm kind of curious to know what your model number would show up as in the About Phone screen. Being able to incorporate the SIM fix into the ROM would be a good thing. There was a link in the OP to a took that could unpack and repack the OPS file. My concern is, at least with the bastardized Color/Oxygen OS stock hybrid, that it will still see the device as a KB2007 and not an actual KB2005 outside of just the firmware version.
jcsww said:
I'm kind of curious to know what your model number would show up as in the About Phone screen.
Click to expand...
Click to collapse
For LOS and OOS 11, KB2007. (But for OOS 11 software update page, it shows as KB2005. You're able to get KB2005 OTA updates without any problem.)
For OOS 12, KB2005 everywhere.
You can try to spoof device model by using magisk_hide_props_config module, but it's another story.
jcsww said:
Being able to incorporate the SIM fix into the ROM would be a good thing.
Click to expand...
Click to collapse
If you use global version OOS or flash LOS, sim lock no longer exists.
IAAxl said:
I don't understand.
Fix what or unpack what?
Is this what you need? "https://github.com/bkerler/oppo_decrypt"
Click to expand...
Click to collapse
Unpack whole rom system vendor product odm
Its all in super.img
Mr Hassan said:
Unpack whole rom system vendor product odm
Its all in super.img
Click to expand...
Click to collapse
You can get super.img using oppo_decrypt.
But, I thought that's an unencrypted raw disk image, am I wrong?
And by the way, I flashed KB2005 super.img into my KB2007, but fastboot flash lock is still there, have to use unlock code bin file to disable it.
I apologize, as I don't quite understand the original post. This seems to be trying to specify a way to get dual-sim on KB2007 with A12? Apologies for the dumb questions, 1) How do I found out if my KB2007 has DDR4 or DDR5? 2) The instruction link https://www.droidwin.com/convert-oneplus-t-mobile-metro-to-global-on-locked-bootloader/ , following these steps seems to still leave the device on Android 11 (because that is the rom that comes with the MSM tools). If we then update to Android 12, won't that disable the dual-sim again?
raven911 said:
I apologize, as I don't quite understand the original post. This seems to be trying to specify a way to get dual-sim on KB2007 with A12? Apologies for the dumb questions, 1) How do I found out if my KB2007 has DDR4 or DDR5? 2) The instruction link https://www.droidwin.com/convert-oneplus-t-mobile-metro-to-global-on-locked-bootloader/ , following these steps seems to still leave the device on Android 11 (because that is the rom that comes with the MSM tools). If we then update to Android 12, won't that disable the dual-sim again?
Click to expand...
Click to collapse
In os12 ofcourse your 2nd sim will disable by bootloader partitions and some other as i mention in another post
But good news is i can fix
But bad news no way yo unpack repack or rw after root
raven911 said:
I apologize, as I don't quite understand the original post. This seems to be trying to specify a way to get dual-sim on KB2007 with A12? Apologies for the dumb questions, 1) How do I found out if my KB2007 has DDR4 or DDR5? 2) The instruction link https://www.droidwin.com/convert-oneplus-t-mobile-metro-to-global-on-locked-bootloader/ , following these steps seems to still leave the device on Android 11 (because that is the rom that comes with the MSM tools). If we then update to Android 12, won't that disable the dual-sim again?
Click to expand...
Click to collapse
To answer your questions:
1) Check here: https://wiki.lineageos.org/devices/kebab/fw_update
By the way, 8T hardware has two major variables: UFS 3.0 / 3.1 storage, and lpddr 4 / 5 memory. Storage type doesn't matter to rom flash, but memory type does.
2) Yes! You're still on OOS 11 after change-brand flash, but then you can OTA to KB2005 OOS 12 directly.
And, because my final goal is to run LOS, I didn't put my sim in while my phone is on OOS, so I can't really answer if dual sim is available in OOS 11 or 12.
In LOS, I use magisk_hide_props_config module to add "persist.radio.multisim.config=dsds" into system prop to enable dual sim. You can also try this "https://forum.xda-developers.com/t/...bile-8t-kb2007-with-lineage-aosp-rom.4262669/", same stuff.
If your KB2007 is flash locked, you can try the following steps and see if it will work:
A. Use oppo_decrypt to get elf files from msm rom;
B. Use QPST (and the elf file) to flash magisk patched boot.img into your device under 9008.
C. Install magisk model and get dsds.
∆ The risk is in step B.
I'm not familiar enough with QPST and never succeed to get QPST work to do anything.
Mr Hassan said:
Unpack whole rom system vendor product odm
Its all in super.img
Click to expand...
Click to collapse
Err… Try use MsmTool readback?
Oppo_decrypt offers an option to enable readback. I haven't used it though.
Or can you change what you have to, directly on a rooted device, and check if it works?
I'm still confused. Aren't those img file raw disk images? Can't you mount and read them on any Unix-alike device? How do you usually do this with other devices?
IAAxl said:
Err… Try use MsmTool readback?
Oppo_decrypt offers an option to enable readback. I haven't used it though.
Or can you change what you have to, directly on a rooted device, and check if it works?
I'm still confused. Aren't those img file raw disk images? Can't you mount and read them on any Unix-alike device? How do you usually do this with other devices?
Click to expand...
Click to collapse
let me tell you msm have rb option
but you still not got my pov there,s no rw option in rooted device even after root
so how can i make dump or backup or for which purpose i need backup if i dont even modded something in rooted device
another option which left is unpack system.img vendor.img odm.img etc and modify then repack it
but there,s not way to even convert it to raw i try simg2img but not support by this
even if i able to convert it to raw i can do something
and no its not raw format men. its payload and super
Mr Hassan said:
let me tell you msm have rb option
but you still not got my pov there,s no rw option in rooted device even after root
so how can i make dump or backup or for which purpose i need backup if i dont even modded something in rooted device
another option which left is unpack system.img vendor.img odm.img etc and modify then repack it
but there,s not way to even convert it to raw i try simg2img but not support by this
even if i able to convert it to raw i can do something
and no its not raw format men. its payload and super
Click to expand...
Click to collapse
Okay I understand now..
The goal is to change sth inside vendor and other partition, but they can't be remounted read-write inside system.
And the img file can't be exacted or repacked.
Will you try to remount those partition in recovery ADB maybe?
IAAxl said:
Okay I understand now..
The goal is to change sth inside vendor and other partition, but they can't be remounted read-write inside system.
And the img file can't be exacted or repacked.
Will you try to remount those partition in recovery ADB maybe?
Click to expand...
Click to collapse
Yes now you fully understand
Yes i tried many thing
And yes in twrp also tried remount etc
I also pull files and edit but when i push
Its said device not have enough space
Its maybe need resize etc
Mr Hassan said:
Yes now you fully understand
Yes i tried many thing
And yes in twrp also tried remount etc
I also pull files and edit but when i push
Its said device not have enough space
Its maybe need resize etc
Click to expand...
Click to collapse
I don't know if this helps or not.
But there are some scripts to exctract partitions from SUPER, flash them and make -rw.
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Rootk1t said:
I don't know if this helps or not.
But there are some scripts to exctract partitions from SUPER, flash them and make -rw.
[TOOL][WIN,LIN,AND,DARW] Super image tools | extract or make partitions RW in super partition
Disclaimer: Super image tools was made for testing and educational purposes, ME is not responsible for what you do on/with your device using our tools, you must agree that you using our tools on your own risk, I am not responsible for anything...
forum.xda-developers.com
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com
Click to expand...
Click to collapse
I done manything even convert to ext4
In shel its showing rw
And also in root explorer get rw but still not edit anything
I also try similar approach using qpst. I can read/save qpst and qcn but i can't write back.
vortex91 said:
I also try similar approach using qpst. I can read/save qpst and qcn but i can't write back.
Click to expand...
Click to collapse
Could you please share what you find?
I'm really unfamiliar with QPST, any info could help.
So, I'm not need T-Mobile help to sim unlock my phone?
Just convert it to global, and it will be carrier unlocked?
Are I read this right?
Deleted.