yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] lebigmac:
Are you trying to tell me that your stock read-only Samsung firmware is actually read/write-able by default? :unsure: :ROFLMAO:

Wait you ran my script on a Samsung device? And? What was the result? Could you please be so kind and send me your logs from the /data/local/tmp folder? Your feedback would help tremendously with improving compatibility with Samsung devices. Thanks ;)(y)

Right now I'm in the slow process of making the new version of the MakeRW / ro2rw binary unhackable for the cyber pirates out there ;)(y)

Nobody really enjoys being deleted from their own programs now do they... That's why as an open source developer I must take some safety precautions to protect my code (at least partially) even if it means that you have to wait a day longer. Thanks for your understanding. ;)

hackable-2-Unhackable conversion process: ======================================== 50%
[Android Software/Hacking General [Developers Only]] AnonVendetta:
@lebigmac: I'm curious to know which of your binaries are proprietary. From what I can tell, most of the ones like img2simg and simg2img are open source. The script certainly isn't proprietary "code", it's not a compiled binary, just a text script that executes commands. So, while your mod may have a select few proprietary components, most of it uses open source code.

I've noticed that you haven't included any GPL/LGPL/Apache/other license notices for the open source parts. As per the terms of those license agreements, text files must be included for any components which uses code covered by those licenses.
[Android Software/Hacking General [Developers Only]] lebigmac:
@AnonVendetta can you please send me those license files you're talking about so I can include them with the next version of my program? Thanks (y)

I haven't had much time to even think about the stuff you're writing about. :LOL: Been too busy with programming my unique and original RW program for Android from scratch. ;)(y)

Are you trying to tell me that only because a a shell script is open or naked and anyone can see the bare source code, that this source code has no owner or creator?

The word "proprietary" doesn't mean anything other than this source code has an owner AKA a copyright holder or creator. At least that's my understanding of the word proprietary. If you want to go into more details about what exactly the word proprietary means please feel free to send me a DM. Thanks (y)
[Android Software/Hacking General [Developers Only]] AnonVendetta:
I expect you to already know which licenses are relevant, or that you should know if you don't already. If you're going to use shared work that isn't yours, and it is covered by a license, then you should take it upon yourself to read those licenses so that you know what you have to do. You wouldnt want your work to be used without proper credit, so you must extend others the same courtesy.

So...exactly which of your binaries in the bin directory are proprietary? Obviously you don't need to include the source code for stuff that is entirely your original work, and uses no shared code. Moreover, I have no interest in reverse engineering it or stealing. I have little reversing knowledge anyway, I did no actual cracking myself, back in the days that I mingled with pirates. I just noted that you say your mod is proprietary. And so I'm asking, which parts? Certainly not all of it.
[Android Software/Hacking General [Developers Only]] lebigmac:
Not sure which license files you're talking about as I'm very busy working on my program right now but in the meantime please feel free to post them here so I can include them with next version of my program. ;)

Thank you.

I agree I still forgot a whole lot of talented people in my credits but I always give credits where it's due, unlike some other people in this forum who have obviously copied my hard work (or parts thereof) without giving any credits whatsoever to the original source (yet I don't see you lecturing them about licenses in their copycat threads but here you are pointing your finger at me).

Are you the creator of make_ext4fs binary? Or lpmake binary? If you happen to know the names of the talented programmers who wrote those amazing programs please let me know and I'll be happy to write their names in my credits as without their crucial programs my unique and original RW Multi tool wouldn't exist in the first place. Thanks :D(y)
[Android Software/Hacking General [Developers Only]] AnonVendetta:
@lebigmac: For starters, e2fsck and tune2fs are a part of e2fsprogs, and uses the GPL/LGPL/MIT. img2simg and simg2img appear to be Apache 2.0.
[Android Software/Hacking General [Developers Only]] lebigmac:
I think I kind of understand what you're talking about. Is it enough if I include that apache and GPL/LGPL/MIT license .txt file with my next release? Thanks (y)

I can't possibly fit any more characters into the welcome message itself....

If you are looking to join my dev team I am always happy to accept new talented developers on my RW developer team :D(y)

And then you will get full access to all my proprietary RW related sourced code :love:(y)

Just DM me your resume ;)(y)
[Android Software/Hacking General [Developers Only]] AnonVendetta:
I wasn't aware that anyone had stolen your work. Or that these thieves had threads of their own. I'm not pointing the finger, it's obvious that you've stolen nothing. You're an eager modder that has something original and useful to share. And a lot of work to do to make it better. I was just saying that it would be a good idea that you should check the licenses for the binaries you didn't write yourself, and include a text copy of their licenses in your next release zip. As a goodwill gesture to whoever authored those works. It's easy to forget things in our haste to get stuff done. And no, I didn't write the code for any of the binaries.
[Android Software/Hacking General [Developers Only]] lebigmac:
Yes I finally understand you sir. Took me a while to get back out of that encryption mode LOL. And I totally agree with most of what you wrote. Always give credits where credits are due. (y)

Thanks for reminding me about all those various license files that I forgot to include. Just been so busy with the program itself... It's so next level now I'm still shocked... I hope it works just as good on your device as on mine... Now let me get back into that encryption mode... Going offline...
[Android Software/Hacking General [Developers Only]] AnonVendetta:
@lebigmac: You should look into code obfuscation techniques. Maybe a little hidden function here or there that detects changes and refuses to run if detected. Or wipe their partitions.

On the other hand, I don't see any harm in allowing your code to be modified, *IF* they don't distribute it publicly, pass it off as their own work, and not share their changes with others. In other words, as long as it's for private/personal use only, no harm, no foul. If all of these were really true in a particular scenario, you wouldn't know anyway, and couldn't stop them.
[Android Software/Hacking General [Developers Only]] lebigmac:
@AnonVendetta if you're bored can you please upload those missing license .txt files here and I'll include your name in my shout-outs. Thanks ;)(y)

I basically need the license files for all the binaries in the /bin subfolder.

That way I can focus on finishing this and uploading it for you all to enjoy :love:(y)

Or else I'll have to include those license files in v1.37 only...

Right now I'm working on v1.36 and I have zero time for those damn license files. The whole world is waiting...
[Android Software/Hacking General [Developers Only]] AnonVendetta:
I'll pass. I don't want to be credited for anything. I didn't do any work. Also, not my project, not my responsibility. I'd initially posted here only because I was curious to know if the ext4 partitions in the super could be converted to f2fs. For better performance, if possible. Whether my devices would boot is another scenario.
[Android Software/Hacking General [Developers Only]] AnonVendetta:
@lebigmac: This is exactly why I didn't buy the Note 22 Ultra. I knew about the f2fs read only and decided it wasn't worth it. I absolutely must have real (i.e. without Magisk or systemless modifications) write access to my partitions.

Like you, I'm a busy man, with pet projects of my own to work on. So as much as I'd like to be a part of this, no, not really. Not enough time. I'm merely an end user, not a dev. I do write some code for personal use only, but that's it. I'm what you would call a tech enthusiast, but not a dev, and I have no professional expertise in such matters. For me, it is a hobby only.

If I had come up with a project like SystemRW, I wouldn't have shared it with anyone. Too many ungrateful and demanding users that have no respect for your personal time. They forget that devs on XDA aren't paid for their work. And then there are the thieves that make little changes here and there, then pass it off as their own.
[Android Software/Hacking General [Developers Only]] lebigmac:
I don't do it for the money. LOL what money? I do it for the love of the RW game :love:(y)

If you buy a brand new next-gen smartphone device with your hard earned cash you should have full read/write access to both the software and the hardware. Just my 2 cents 🪙🪙
[Android Software/Hacking General [Developers Only]] Aitra:
The result after manual installation is obtained 2 files: super_patched.bin & super_patched_new.img both smaller than super_originnal.bin file. so is it ok?
[Android Software/Hacking General [Developers Only]] SpatialDistortion:
I installed v1.35 before, can I directly install v1.36 without having to uninstall my previous v1.35?
[Android Software/Hacking General [Developers Only]] lebigmac:
Can you please show the log? Thanks (y)

Screenshot is looking good :D(y)

Just delete whole sysrw_1.35 folder and replace with new v1.36 folder ;)(y)

If u dont want to initiate the dumping process again just disable backups in config.ini ;)(y) backup=0

Hey @LeeGarChat how you like my brand new getTotalImgSize() and compareNum() functions (among many other unique functions)? They work rock solid it seems. Since you have been thoroughly studying my old systemrw_1.32 script every single day, day in and day out since I originally released it back in 2021 you should know that awk is my favorite tool ;) Why it's not in the default toybox? :unsure: Oh well maybe it's in the busybox. I must say awk is much more reliable than the standard POSIX method of comparing numbers. :D(y)

getTotalImgSize(){
ls -l $imgDir/*.img | awk '{sum+=$5}; END {print sum}'
}

compareNum(){
if [ $3 ]; then
echo $1 $2 | awk 'END {ret=($1 > $2) ? 0 : 1; exit ret}'
else
echo $1 $2 | awk 'END {ret=($1 < $2) ? 0 : 1; exit ret}'
fi
return $?
}
[Android Software/Hacking General [Developers Only]] Aitra:
Your free tool is awesome. Thank you for your hard work and dedication to the world.
[Android Software/Hacking General [Developers Only]] lebigmac:
You are very welcome sir. Donation page coming right now ;)(y)

It's work?!

Can you please show log or screenshot? Can you do this now?

Thanks for your amazing feedback and support ! :love:(y)
[Android Software/Hacking General [Developers Only]] Aitra:
My Mi 11 lite 5g phone with f2fs memory was able to toggle ro/rw. Thank you for this great dedication!
[Android Software/Hacking General [Developers Only]] lebigmac:
wait what f2fs? My official F2FS-RW patch only coming in 1. quartal 2023 :ROFLMAO:

Maybe only /data is mounted f2fs ;)(y)

The rest should be EXT4-RW now AKA FULL-RW :love:(y)

You can send me log in DM if you want ;)
[Android Software/Hacking General [Developers Only]] k.syedhussain:
Hello i created dynamic partion through sysrw.1.5zip and that when I try reboot the mobile long running script in boot screen no chances of reboot to normal screen....

What I done i flashed original firmware LOCKED THE BOOTLOADER of dynamic partion .i unable to unlock the bootloader nor delete the dynamic partitions.every timewhen i try to boot fastboot it booted with fastbootd. what to do.. I am unable access "A" partion firmware and bootloader..now my phone running in dynamic partion os and bootloader fastboot d.

Wait for solution.
[Android Software/Hacking General [Developers Only]] lebigmac:
Hello. Apparently you didn't properly follow the instructions in 1. post of this thread (or in the included readme file).

Also there is no sysrw.1.5.zip you are probably talking about the sysrw_1.36_flashable.zip file that I just uploaded to my website a couple hours ago right?

No no not lock bootloader. You need unlocked bootloader and root for this...

If you have problems unlocking your bootloader please visit your device's sub-forum here and you will most likely find the answer on how to properly unlock bootloader for your specific device.

Sorry I am not familiar with fastbootd, my device only use normal fastboot.

What to do? Just unlock bootloader, root it and then install my script according to the instructions. If you have any more questions just ask! Good luck! (y)
[Android Software/Hacking General [Developers Only]] k.syedhussain:
Thank you for your fast reply actually I didn't elaborately mentioned my problem I am LG v60 user I unlock the bootloader and rooted the device successfully after rooting I try to edit a built prop but I am unsuccessful so I come across your script system sysrw.zip.

I paste your script file inside local temp folder after placing I successfully run your script dynamic super partition and I got nearly 24 GP of data on my the 24 GB data to memory card I patched partition successfully then what happened when I try to reboot my device .... dint boot up long running scipt excute near 50 min keep running .so flashed the firmware again with unlocked bootloader.after flashing i locked the bootloader....

Now my mobile working in dynamic super image partion with inside two firmware .....

Simplly i locked the bootloader with super parition ...i cant unlock bootloader to erase super partion fastboot mode is not working ....now only fastbootd.
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi I want try to help but you must start fresh as you seem to have messed up royally somewhere along the way. Just reinstall your stock firmware and then call me. I waiting.
[Android Software/Hacking General [Developers Only]] lebigmac:
Yeah I've actually thought about implementing an antitheft feature that automatically detects if a cyber pirate is trying to hack and steal my proprietary software and then instantly proceeds to format his hard drive lmao :LOL:
[Android Software/Hacking General [Developers Only]] gvshil:
Xiaomi Redmi Note 10 Pro (8/256) - Superb works!
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi. Congratulations for making your next-gen Android device FULL-RW with my original RW Multi tool for Android! Enjoy customizing and debloating your fully read/write-able next-gen Android device :love:(y)

Can you please show me the main.log and the lpdump.txt files from this path? Thanks (y)

/data/local/tmp/sysrw_1.36/log

NOTE: the dmesg_error.txt log could potentially contain private info about your phone such as serial number or IMEI!

The dmesg_error.txt log is only created for debugging purposes at the end of the script if lpmake command fails. I'll probably remove that with next version. Nobody ever looks at those dmesg logs anyway :LOL:

And now that the program has finally reached stable status thanks to the built-in highly experimental AUTO-DEBLOAT feature, I don't need that dmesg log anymore.

Thanks for your amazing feedback and support! :D(y)
[Android Software/Hacking General [Developers Only]] Bogdkdkd:
After i flashed super_patched.bin phone succesfully booted and I got fully rw copability. Thanks for your work, lebigmac🫂. But, when i try mount /vendor to rw, it returns "Operation not permitted". I hope this can be fixed.
[Android Software/Hacking General [Developers Only]] lebigmac:
Hello. Congratulations! Enjoy customizing and debloating your fully read/write-able next-gen Android device! :love:(y)

Okay see now the dmesg command could actually be useful for you to find out why the hell you get this "Operation not permitted" error even though you are clearly root + you got FULL-RW capability... :unsure:

Try remount /vendor as rw again and immediately afterwards run dmesg and search for the reason! If you find out the reason please let me know so I can include the fix in the next version. Of course you will be properly credited! Thanks and good luck! (y)
[Android Software/Hacking General [Developers Only]] lebigmac:
OMG OMG that log though :love:(y)

And in combination with your beautiful screenshot it almost brings a tear to my eye ;)

Auto-Debloat worked on all except on 1 partition.... What the hell? Can you please highly compress and send me your stock my_company_a.img sub-partition and try make it smaller than 300MB if you can (my internet is very bad). I want to simulate your error here on my device. Thanks ;)(y)

I see a few errors in the log and yet it still works? OMG OMG. I am amazed. Which Realme is this?
[Android Software/Hacking General [Developers Only]] Bogdkdkd:
[16488.814408] (3)[17516:mount][20230113_21:39:17.529776]@3 [OPLUS]System partition is not permitted to be mounted as readwrite [16488.814427] (3)[17516:mount][20230113_21:39:17.529799]@3 do_mount:kevent_send_to_user
[Android Software/Hacking General [Developers Only]] Bogdkdkd:
Yes, it works. Realme GT 5g
[Android Software/Hacking General [Developers Only]] lebigmac:
ok I write you now in list of successful devices on front page. You sir are a celebrity now :D(y)
[Android Software/Hacking General [Developers Only]] lebigmac:
Thanks for the file (y)

What you can try to do is remount /vendor as rw inside TWRP recovery and if you don't get the same "operation not permitted" error there, then it's probably some kind of Android operating system protection feature...
[Android Software/Hacking General [Developers Only]] slick777:
I can't get it, it gives me an error, realme mee
[Android Software/Hacking General [Developers Only]] lebigmac:
Hi thanks for your log (y)

Why your recovery is selinux enforcing? :unsure:

It looks like you successfully activated the new auto-debloat feature by writing auto_debloat=1 into the config.ini file :D(y) but you didn't write any debloat paths into the auto_debloat.txt file?

According to your log you must debloat over 3GB of bloatware which will be very difficult to do without causing bootloop... Now browse around on your phone and search for useless bloatware in your stock firmware to write into the debloat list ;)

If you debloat the wrong thing you will end up in bootloop so think twice what you write in the auto_debloat.txt file ;)

Good luck! (y)
[Android Software/Hacking General [Developers Only]] Timmmmaaahh!:
┤Thread Closed├

Hello everyone

As helpful as @lebigmac may be, no one – not even us – is above XDA's Forum Rules. Our work as moderators usually remains in the background but it felt necessary to provide some transparency here. After consulting our team I have decided to ban the OP of this thread for three months and it will remain locked until OP requests to open it back up after the ban expires. For some of you this will come as a complete surprise and may seem unfair but I would like to stress that we have invested a massive amount of energy and a mountain of patience to come to a resolve with lebigmac. Several moderators were involved. Despite our many efforts, (s)he persisted to openly accuse people of plagiarism, inciting conflict, call out the people involved and communicated in a very condescending and demeaning way.

We of course regret this course of action. Developers and development is everything to us but boundaries must be respected. After several earlier time-outs we had no other option but to proceed this way. We're hoping this will bring back some peace in this feud as well. With so much going on in the world we really don't need opposing developer parties. Open source is about cooperation and improving existing code, not about bitter fights over protecting your own code, which is based on the work of others anyway. One questionable screenshot aside, there hasn't been any viable proof of plagiarism provided to us related to this project.

Thank you all for your understanding and as always we remain available to answer your questions and concerns via PM. Have an amazing day!

Kind regards

Timmy

Senior Moderator
[Android Software/Hacking General [Developers Only]] Oswald Boelcke:
Allow me to add some more information to above post of my teammate @Timmmmaaahh!

The account of the author of this thread has been permanently suspended. In your own interest, I ask everybody not to promote a banned user or his website, blog, work etc. on XDA. Thanks very much for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Android Software/Hacking General [Developers Only]] lebigmac:
v1.22 added to first post :D

That should fix your issue @Articul8Madness

@nttuan I'm not sure if this will work for you but you can try it.
[Android Software/Hacking General [Developers Only]] nttuan:
I tried version 1.22 and still the same issue. Please see the attached files.
[Android Software/Hacking General [Developers Only]] lebigmac:
@nttuan can you successfully run lpmake command manually?

Check the excellent Brepro1 tutorial and the excellent AndyYan tutorial on how to do this. Thanks.

@nttuan I have a possible solution for you. Check your PM
[Android Software/Hacking General [Developers Only]] kory-vadim:
I've already told you several times that you don't need to convert to sparse, because lpmake will still write a raw image to super.img.

Also, why are you merging the super section into a file? It takes time and a lot of space, pull the images directly from the super section.
[Android Software/Hacking General [Developers Only]] quanqw:
It don't work on my g8 android 10. It show error: 225
[Android Software/Hacking General [Developers Only]] quanqw:
It don't work on my g8 android 10. It show error: 225.
[Android Software/Hacking General [Developers Only]] lebigmac:
@kory-vadim you are absolutely right. Lpmake will automatically convert from sparse to raw before writing new super_fixed.bin so there is no point in using img2simg before running lpmake. I can confirm this.

The reason why I am dumping original super partition to image file on local storage is for backup purposes before new super_fixed.bin is flashed irreversibly to block device. Feel free to deactivate the dd function if you want ;)

@quanqw thanks for your log. It's looking good. Apparently system_a.img and system_b.img have been successfully patched. Did you try flashing them yet in fastboot?

Please make a backup of the original files first.

For flashing you can do

adb pull /data/local/tmp/makesysrw_1.22/files/nosuper
adb reboot bootloader
fastboot flash system_a ./system_a.img
fastboot flash system_b ./system_b.img
[Android Software/Hacking General [Developers Only]] quanqw:
This is my error.

makesysrw: The filesystem of vendor_a.img was successfully resized

makesysrw: Removing 'shared_blocks feature' of vendor_a.img...

e2fsck 1.44.4 (18-Aug-2018)

makesysrw: There was a problem removing the read-only lock of vendor_a.img
[Android Software/Hacking General [Developers Only]] lebigmac:
@quanqw In that case we must try to figure out why e2fsck command failed for vendor_a.img

Can you run the command manually?

e2fsck -y -E unshare_blocks ./vendor_a.img
[Android Software/Hacking General [Developers Only]] kpykpy:
failed create super_fixed.img

free space 230GB

adb shell "ls -Alg /dev/block/by-name | grep 'super'"

lrwxrwxrwx 1 root 16 1970-01-17 12:45 super -> /dev/block/sda19
[Android Software/Hacking General [Developers Only]] Rahamatulla:
Working in REDMI K30 Device
[Android Software/Hacking General [Developers Only]] Vishal_SG:
Great! Partitions are rw now.

My device is POCO X2 and i can confirm its working . Tried both A10 and A11. thank you all for your hard work :)
[Android Software/Hacking General [Developers Only]] Vishal_SG:
Any downside of this? impact on performance or anything?