Related
Hi all,
Is there any way to pull out the system completely into a .img format? Since I did some modification on my system, I was wondering if there is an easy way to create a .img out of the unit itself. Thanks!
kazuni said:
Hi all,
Is there any way to pull out the system completely into a .img format? Since I did some modification on my system, I was wondering if there is an easy way to create a .img out of the unit itself. Thanks!
Click to expand...
Click to collapse
You need recovery and that's not available yet.
Ah I see.
Another question regarding this, I notice that there is no parameters under fastboot that allows pulling the system image, but it can flash one. There aren't any options?
Blagus said:
You need recovery and that's not available yet.
Click to expand...
Click to collapse
@Blagus
is is possible to use dump_image binary from preshoot's kernel maker update.zip to dump system.img???
DooMLoRD said:
@Blagus
is is possible to use dump_image binary from preshoot's kernel maker update.zip to dump system.img???
Click to expand...
Click to collapse
If dump_image can get NAND read access from within Android system, then yes. It'll probably have to be run as root.
Hi guys!
I have noticed that developers continue to develop new Android versions for the HD2, there is always something of new (KitKat it's already avaible).
Developers make Android Roms bootable from MicroSD through a partition without delete W.M.
They can edit the Linux Kernel in any way.
Surely you know projects like XDAndroid that use the "haret.exe" file.
But which sofwares and which coding languages do they use to "build" these Roms?
I read about
-Eclipse and Android Studio
-Gedit and Nano
-Kate and Vim
...
What do you know? Help me
Mich-C said:
What do you know? Help me
Click to expand...
Click to collapse
ROMs/kernels are written in C / C++. And are built/compiled usually from the terminal in a linux OS.
More info here -> http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built.
HypoTurtle said:
ROMs/kernels are written in C / C++. And are built/compiled usually from the terminal in a linux OS.
More info here -> http://xda-university.com/as-a-developer/introduction-how-an-android-rom-is-built.
Click to expand...
Click to collapse
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Mich-C said:
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Click to expand...
Click to collapse
Well, yeah...
When you compile you rom you need to imstall ot this way:
You need 3 things:
1. Ext4 partition on your sdcard
2. Some recovery build for booting over haret ( you can take sd twrp's)
3. Your rom in flashable zip.
When you have all that, make a folder in your sd card, put your android flashable zip and extract your sd recovery there. Then run haret from that folder, and flash your android trough recovery. Then reboot, and go to the folder you have made for your android build, there should be a folder called NativeSD. Go in it an run haret an you will be booting in your android
ADD: You need to install w/ NaticeSD method only
Sent from my leo using XDA Premium 4 mobile app
Mich-C said:
So Is the procedure to make Roms for native Android phones the same of the one to make Roms for not-native Android phones?
Right?
Click to expand...
Click to collapse
In a way yes. A Rom is made up of a kernel which is bundled with a ramdisk (essentially boot instructions). to make a boot image.
On top of which is the system files which make up the OS itself. During compilation device specific details are taken from the files and baked in to the files that'll be running on the device itself.
The problem with making ROMs for non-Android devices is getting the device specific stuff - the HD2 is close enough / the same as a couple android phones (Nexus One / Desire S (??)) so getting these files was relatively easy.
You've mentioned haret.exe, which i believe just needs a rearranged ramdisk, other than being able to flash an open bootlader (magldr / lk in the HD2's case) that would be the only way to run android on a WM device.
The real question is, do you have working android kernel for your device..
Sent from my leo using XDA Premium 4 mobile app
What do you think about my concept for porting guide treble to non treble devices ???? That was only sample , and I don't do test's on other devices than my . http://80.211.218.7/index.php/rom-porting-guide-for-no-treble-devices/?fbclid=IwAR0qi_JDP0i9tcvBGAcp7lRtNu9QwKWQEGNXm5TG5W9NfeFx1pcIcmxOmZ8 Who want to test ???? I'm waiting for your opinion
I am interested if anyone knows how to create Treble Support for Non-Treble Devices.
zombie_ryushu said:
I am interested if anyone knows how to create Treble Support for Non-Treble Devices.
Click to expand...
Click to collapse
I know . I say how in other than my thread . This method is universal for other devices too .
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886/page91#post79523146
MAREK10747 said:
I know . I say how in other than my thread . This method is universal for other devices too .
https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886/page91#post79523146
Click to expand...
Click to collapse
Do you think you can try and see if its possible for the Blu Vivo 5?
zombie_ryushu said:
Do you think you can try and see if its possible for the Blu Vivo 5?
Click to expand...
Click to collapse
I don't know
what are you saying ..porting treble to non-treble already exist ...but you need to repartition the phone ..you need to make a repartition script ..you also need to create a vendor.img
KevMetal said:
what are you saying ..porting treble to non-treble already exist ...but you need to repartition the phone ..you need to make a repartition script ..you also need to create a vendor.img
Click to expand...
Click to collapse
who would I go too that has experience doing that?
I'd be interested, but unfortunately your webserver is no more available
Can you upload your stub guide somewhere?
No I cant reupload because I delete all data from my pc . Re partition ZIP is avalaible to download from XDA and my threads . This ZIP make vendor partition . Image of vendor you must make manually with permissions .
MAREK10747 said:
No I cant reupload because I delete all data from my pc . Re partition ZIP is avalaible to download from XDA and my threads . This ZIP make vendor partition . Image of vendor you must make manually with permissions .
Click to expand...
Click to collapse
Do you have any tutorial to point me on how to move the contents of /system/vendor to the vendor partition and any other necessary modifications (such in boot.img ramdisk/dtb) for GSIs to boot successfully?
KaMyKaSii said:
Do you have any tutorial to point me on how to move the contents of /system/vendor to the vendor partition and any other necessary modifications (such in boot.img ramdisk/dtb) for GSIs to boot successfully?
Click to expand...
Click to collapse
Tutorial don't exist. You need to use zip for create vendor , next step is mount new vendor , next step is mount system and copy files from /system/vendor to /vendor partition . If you device found bugs look for lib's in system . After prepare vendor partition , you need flash GSI and prepare kernel supporting and mounting /vendor as partition . Tables of partitions in kernel too .
link deead
MAREK10747 said:
Tutorial don't exist. You need to use zip for create vendor , next step is mount new vendor , next step is mount system and copy files from /system/vendor to /vendor partition . If you device found bugs look for lib's in system . After prepare vendor partition , you need flash GSI and prepare kernel supporting and mounting /vendor as partition . Tables of partitions in kernel too .
Click to expand...
Click to collapse
Gonna try this on a Huawei P8 Lite. Wish me luck as the USB port has its data pin ripped clean off
I know . I say how in other 8rental.com than my thread
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
antoinejr1111 said:
Are there any working ROMs on the Onn 8" that are running Android 10? I wanna have the latest version of Android.
Click to expand...
Click to collapse
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
All the android 10 GSI's are too large for our system partition. The only one that installs is PHH's 10 v209 but video playback isnt possible outside of YouTube. Its also very unstable, it required several resets do to even simple modifications.
Click to expand...
Click to collapse
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Viva La Android said:
Yeah we need a repartitioning utility to increase /system size. I believe some of the GSI Android 10 ROMs would be great for the Onn tablets if only the allocated /system size was larger. Has anyone tried doing this via TWRP? If /system could be formatted to a larger size, the /userdata partition could be decreased in size to compensate.
Click to expand...
Click to collapse
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
Another option would be a custom rom built for our devices. Or maybe a modified gsi with only the sruff needed for our device. The img size would be much smaller. Things like fingerprint unlock and such is just waisting space.
Click to expand...
Click to collapse
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
jwarrior319 said:
So i tried the new PHH 10 V214. It does install and boot in the same we we install his Pie versions. But, it still cant play video outside of youtube app/website. Still a vendor problem i would assume. Havent tested it long enough to know if the other issues exist yet or not. Im restoring my backup of bliss rom pie.
Sent from my SM-G975U1 using XDA Labs
Click to expand...
Click to collapse
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
angadsg said:
I tried to install PHH 10 v215 (both A/B image and A-only) - but I cannot get it to boot. It does not go past the ONN logo and then reboots. Have made backups of all partitions using TWRP.
Tried both methods - fastboot flash system and TWRP install image.
Also tried the 9.0 pixel experience. Same result.
Any ideas what could be going wrong?
Click to expand...
Click to collapse
At the boot logo connect to adb. Make sure its recognized and issue the following command: adb shell setprop debug.stagefright.ccodec 0
Sent from my SM-G975U1 using XDA Labs
Viva La Android said:
True. An image kitchen can be used to decompile the GSI so that non-essential apps and services could be deleted. A slimmed down Android !10 GSI would surely work on this device.
Click to expand...
Click to collapse
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
antoinejr1111 said:
How can I get this image kitchen with Windows 10 or Linux? And possibly how to decompress the image.
Click to expand...
Click to collapse
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Viva La Android said:
Personally, I use @SuperR.'s Kitchen for cooking Android ROMs. The kitchen allows you, for example, to toss in a system.img of an Android 10 based ROM. The kitchen decompiles the image into a workable /system folder and full filesystem. You are given options to debloat, add root, BusyBox, deodex, zipalign, etc. You can also toss in the boot.img and vendor.img from the Android 10 ROM and the kitchen will create for you the META-INF file with updater-script and update-binary. It will add your symlinks, permissions and all Edify commands needed to mete out a TWRP flashable Android 10 ROM with all the customizations you've added. The kitchen is available in both a free and a donate version (which is $15 I think). It's available for Linux and Windows based systems. Here is a link to the Windows version I use. Well worth the humble amount of money he asks for the donate version, as you'll see in the thread. https://forum.xda-developers.com/ap...dows-linux-superr-s-kitchen-v3-0-0-0-t3601702
Click to expand...
Click to collapse
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
antoinejr1111 said:
Do you think you can break down a version of Android 10 that works for the Onn 8" and send it to me? Please?
Click to expand...
Click to collapse
My only dilemma there is that I've got multiple projects going right now for various LG and Motorola devices. However, I fully plan on future development for the Onn series of tablets (primarily the newer Onn Surf series due to Treble support). As soon as my schedule permits, I'm on it. Here's the beauty with Project Treble: if an Android 10 GSI will boot on the Onn Surf 10.1, it is almost certain that it will also boot on the Surf 8. Out of curiosity, what is the allocated /system partition size on the Onn Surf 8? Is it the same as the Surf 10.1? Also, I noticed recently that there are some rather slim GSI builds of Android 10 (Go Edition). Some of these might be worth looking into.
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.