I only want to root the phone so I can debloat it and maybe install a GSI rom if it's stable enough and has better battery life than the OneUI.
Does this kernel run on U3 bootloader?physwizz a12s kernel version 4
Based on a127f U1 binary
For OneUI 3.1
( also works for GSIs)
Samsung securities disabled
More CPU governors
Conservative, On-demand, Userspace, powersave, performance, energy_step, shedutil
Optimised for performance
Overclocked for performance
Underclocked for battery
CPU: 130MHz - 2210MHz
lz4 compression added to zram
Ready for spectrum installation
Install from TWRP
Install adb tools on pc
Connect to PC
Copy zip file to adb folder on pc
Open terminal on pc
Navigate to adb folder
adb sideload name.zip
Go to HKtweaks- virtual memory
Turn off zram
increase swappiness to 200
increase size to 4096
turn on Zram
physwizz has 33 repositories available. Follow their code on GitHub.github.com
Didn't try all the intricate ways yet (reflashing the stock firmware, then Magisk-patch it all, etc.) but the simplest, which is use Odin over whatever I have (LineageOS that is with the stock recovery) and flash, fails for me. It just hangs forever on the Sam logo screen. Interesting thing: LineageOS hangs on the boot animation if I am using the "purged" vbmeta (and I have to use it to flash TWRP, of course, otherwise Download gets excited over missing signatures). Theoretically it shouldn't affect anything at this stage of the booting process but it does.@uluruman
U3 versionfor testing.
Afaneh TWRP NOT for baseband u3 or greater (Working u3/u4 version on post #2) Download tar file. Extract recovery.img from tar file Method 1. If you have already installed recovery and decrypted. 1. Boot to recovery. 2. Install recovery.img 3...forum.xda-developers.com
Agh, finally, I found combination, that works for me.Thanks physwizz! With these new recoveries I finally got TWRP booting! I've formatted data okay, have the sdcard accessible after that and a reboot, but now the next problem: a lot of "Unable to find partition for path '/system_root'" messages. And indeed, there is no "system_root" partition entry in fstab. Also the "Mount system partition read-only" checkbox in the Mount section is unresponsive and remains always checked. Any ideas?
Glad it now works.Agh, finally, I found combination, that works for me.
I have spent days and physwizz hours PMing with me to double, triple check, if I missed some point. It still remain mysterious, why steps leads to different results, as a novice, I can just speculate, if there is some tiny important difference between A127F/DS and A127F/DSN. Or, well.... what about starting "Stock ROM" we are different.
But there have been some clues.
Afaneh92's TWRP, it can boot for me, but there has been two things that stink for me. Select Storage - shown Internal storage 0MB capacity and unmountable Data partition, that even if it reports 0MB size, cannot as an empty be backuped, for example. Reboots after proper steps (Format data) leads to slow bootlooping (10mins, I guess Android factory reset trying to finish with some bug in the end).
Newest TWRP - that one reported lasttime, Srilanka user, it can in some point (physwizz remount command) starts to report Storage size, even Data partition, but installing multidisabler didnt worked for me, leads to Cannot install zip file error. So, not surprise, after data format and reboot, it lead to nothing, well I can just speculate it that un-disabled encryption. Physwizz advice to remount solves part of red colors anout system root.
I combine those TWRP, using both for part of the job.
1. Rebooted to Afaneh92 TWRP,
2. run remount command
3. run multidisable twice
4. Reboot directly to download mode
5. flash SriLankas TWPR, and boot it
6. Remount command, Format data
voila, system starts, initiate standard default process. Srilankas TWRP can backup all partition I want (including /data). All done.
I have no idea, if this procedure will help others and will work in other conditions, thats the task for you guys, much much advanced than me. I have just some unclear imagination, whats those steps are about, but there has to be something unfinished with afanehs twrp, that prevent it to work OK in some conditions (hardware, original but regional stock rom)
Let others know, if it worked for ya.