How To Guide Installing a custom recovery, and disabling encryption in the system.

[super_sonic]

This is clearly not because of the patch, I have put it on for a long time, and there are no problems. Yes, and he only disables encryption in the system, how can he influence this.

Could you share systemrw_1.32 to create the RW img of super?
Thanks a lot

 

[arraki]

Could you share systemrw_1.32 to create the RW img of super?
Thanks a lot

Yes, of course

[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter) by lebigmac

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

 

[super_sonic]

Yes, of course

Thanks, it works well.
Can I use your TWRP to flash custom ROM or is it necessary to use custom boot and vendor_boot?

 

[arraki]

Thanks, it works well.
Can I use your TWRP to flash custom ROM or is it necessary to use custom boot and vendor_boot?

No, in the way they are made, custom are not put through twrp, only RavenUI is put. I, for the sake of intres, redid the custom for installation via twrp, but it's a long story to tell

 

[super_sonic]

No, in the way they are made, custom are not put through twrp, only RavenUI is put. I, for the sake of intres, redid the custom for installation via twrp, but it's a long story to tell

Sade. Adb sideload is not the same in twrp12? I looked inside payload.bin. It must be possible to extract each partition and flash it. It's what you did? If I understood, once custom rom is flashed, you reflash TWRP and stock vendor_boot, and it works?

 

[arraki]

Sade. Adb sideload is not the same in twrp12? I looked inside payload.bin. It must be possible to extract each partition and flash it. It's what you did? If I understood, once custom rom is flashed, you reflash TWRP and stock vendor_boot, and it works?

A little bit wrong. I took the custom, disassembled the firmware, and collected images in super.img, and now I have already flashed it through twrp

 

[super_sonic]

A little bit wrong. I took the custom, disassembled the firmware, and collected images in super.img, and now I have already flashed it through twrp

Ok. Do you know which partitions.img from payload.bin are necessary, really useful, not custom. I suppose the others are stock. Am I right? I could flash on TWRP only those custom files

 

[arraki]

Ok. Do you know which partitions.img from payload.bin are necessary, really useful, not custom. I suppose the others are stock. Am I right? I could flash on TWRP only those custom files

You can of course try to flash separately the sections included in super.img:system.img,system_ext.img,product.img,vendor.img However, I didn't do that, so I can't say with certainty that it will work, although anything is possible. It's not clear just why it's all?

 

[lebigmac]

Hi @arraki thank you for your interest in my SystemRW / SuperRW feat. MakeRW project
Oh and by the way nice DFE project !
My SystemRW script is it required for your DFE program to work or your program only patches stuff in fstab? In that case shouldn't your DFE also work on read-only devices?

And please keep in mind I am currently working hard on a brand new version of my SystemRW / SuperRW feat. MakeRW script with some new features like autoresize and more. Hopefully I can release it soon. Please wish me luck. Thanks!
That old version of my SystemRW script is too outdated I can't believe it still works on some devices to this day...
By the way do you have any special feature requests for the new upcoming version of my SystemRW script? Now would be a good time to let me know. Thanks for your feedback!

 

[arraki]

Hi @arraki thank you for your interest in my SystemRW / SuperRW feat. MakeRW project
Oh and by the way nice DFE project !
My SystemRW script is it required for your DFE program to work or your program only patch stuff in fstab? In that case it should also work on read-only devices.

Can you please remove that unofficial, unauthorized, incomplete (repair script is missing) re-upload? Instead, you can simply write a link to the official SystemRW / SuperRW feat. MakeRW project page. Thank you
Please keep in mind I could publish the new version any day now and you don't want to miss out on the latest and greatest features trust me
That old version is too outdated I can't believe it still works on some devices to this day...
By the way do you have any special feature requests for the new upcoming version of my script? Now would be a good time to let me know. Thanks for your feedback!

Yes, of course.
Well, I don't seem to have any wishes, especially since I'm transferring the system to RW in a different way.
But this script is quite a convenient solution for many users.
I did not go into the details of the DFE, the main thing is that this script works fine when the system is in RO.
And my script, although it is also not mine, as it is written in the script, I just slightly altered it for us.
And yes, he just edits the fstab file, and for this it is necessary that the system be in RW

 

[super_sonic]

Ok. Do you know which partitions.img from payload.bin are necessary, really useful, not custom. I suppose the others are stock. Am I right? I could flash on TWRP only those custom files

I tried without success: size error for partitions... But flash zip from ofox12 directly is good, for custom rom and recovery stock rom.
I tried to restore data backup with twrp but il fails each time, doen't boot. Is there something to do before restoring? data format? Disable encrypt? ...

 

[arraki]

I tried without success: size error for partitions... But flash zip from ofox12 directly is good, for custom rom and recovery stock rom.
I tried to restore data backup with twrp but il fails each time, doen't boot. Is there something to do before restoring? data format? Disable encrypt? ...

So, which sections of the super did you try to sew? Strange of course, I was recovering normally. After what and how did you do the recovery?What exactly was restored?

 

[super_sonic]

So, which sections of the super did you try to sew? Strange of course, I was recovering normally. After what and how did you do the recovery?What exactly was restored?

I tried to restore data partition only, backuped with twrp and restored with twrp and I tried with ofox too. The phone did not boot and came black to recovery. This data partition was uncrypted.

 

[arraki]

I tried to restore data partition only, backuped with twrp and restored with twrp and I tried with ofox too. The phone did not boot and came black to recovery. This data partition was uncrypted.

I'll check later, now my system is encrypted again, just like I'm testing new recovery builds.

 

[arraki]

I tried to restore data partition only, backuped with twrp and restored with twrp and I tried with ofox too. The phone did not boot and came black to recovery. This data partition was uncrypted.

So, it didn't work out with the old recovery, now we are testing a new recovery

 

[super_sonic]

So, it didn't work out with the old recovery, now we are testing a new recoveryView attachment 5760563View attachment 5760565

Good news. I tried your new twrp to backup but not restore yet.

 

[arraki]

Good news. I tried your new twrp to backup but not restore yet.

Just with the restoration there are problems, on 4PDA a person wrote that he restored it normally on the custom, but on miui there are problems with this, I found the culprit, but we need to figure it out even further. If your firmware does not boot after recovery, but reboots in recovery, then you need to delete folder 0 along the path /data/system/users/ Then the firmware will load, only you need to make some initial settings. In the meantime, we will figure out why this is happening

 

[super_sonic]

Just with the restoration there are problems, on 4PDA a person wrote that he restored it normally on the custom, but on miui there are problems with this, I found the culprit, but we need to figure it out even further. If your firmware does not boot after recovery, but reboots in recovery, then you need to delete folder 0 along the path /data/system/users/ Then the firmware will load, only you need to make some initial settings. In the meantime, we will figure out why this is happening

I flashed your ery last twrp and miui global 13.0.4 didn't want to reboot. So I formatted data partition , rebooted a few time and returned to recovery to restore data, and it works. Good job

 

[arraki]

I flashed your ery last twrp and miui global 13.0.4 didn't want to reboot. So I formatted data partition , rebooted a few time and returned to recovery to restore data, and it works. Good job

I didn't understand about the first one. And the second, yes, on the latest versions of android, this is exactly what you need to do. Did you delete folder 0?

 

[super_sonic]

I didn't understand about the first one. And the second, yes, on the latest versions of android, this is exactly what you need to do. Did you delete folder 0?

No delete folder 0. No initial configuration to do again at first boot