Wipe doesn't touch media (internal sd card) but will not remove encryption. Format deletes everything in userdata, including internal sd card and will also remove encryption
Wipe doesn't touch media (internal sd card) but will not remove encryption. Format deletes everything in userdata, including internal sd card and will also remove encryption
Hi guys, here I am again... hehe =D Just one more doubt, this time, about Magisk... I bought a external card, and then I could flash 2.5 on Odin, then flash ed 2.5.2 on TWRP, multidisabler...and that's all OK. The trouble is about Magisk.. After first boot, set up everything... Then I download Magisk.zip version 20.3, put it on external sd card and rebooted in recovery mode, after I flashed this magisk the system got bootloop...My question is : What the hell ??? haha What's the right version of Magisk to flash with this version 2.5.2? THanks for all that support my doubts =D
Hi guys, here I am again... hehe =D Just one more doubt, this time, about Magisk... I bought a external card, and then I could flash 2.5 on Odin, then flash ed 2.5.2 on TWRP, multidisabler...and that's all OK. The trouble is about Magisk.. After first boot, set up everything... Then I download Magisk.zip version 20.3, put it on external sd card and rebooted in recovery mode, after I flashed this magisk the system got bootloop...My question is : What the hell ??? haha What's the right version of Magisk to flash with this version 2.5.2? THanks for all that support my doubts =D
Hello ! I just installed your ROM and so far i'ts really good so first let me thank you for this awesome work !
I was wondering if there was a way to get rid of the warning screen saying the bootloader is unlocked and also hide the red warning on the samsung logo screen.
I'll probably fix it in the next update (which also will update to November security patch)Hi again ! Since yesterday I have a notification saying that there is a system update available and I can't find a way to make it go away, even temporarily, since it's a system notification.
View attachment 5157983
Do you have the same problem ?
I'm not really sure, I know TWRP is actively being worked on but I don't know if adb is fixed. There are newer builds of TWRP than I provided, I'm testing and if they're bootable, I'll update this ROMI have a question about the /System partition. After installing there's only about 8mb left in the /System but I need some space there because I use Frida for pentesting and it must be installed in there. I tried to resize the partition using Parted but I can't get adb to work in TWRP. Is there anyway I can free some space in the /System partition or at least get adb to work in TWRP?
I'm not sure, I've never tried it.Speaking about system partition, could be that small that copying some ringtones in the corresponding folder (inside system) causes an out of space message ??
Well, the red warning message is normal, that means at least it flashed something correctly.Hello,
So i flashed the firmware with odin 3.14 to my A71, but apparently, after rebooting to recovery to flash the rest of the files, clearing cache and rebooting, it is stuck in a boot loop.
There's the usual red warning message about not running official firmware and so on...
After this, it just crashes and reboots. No bootscreen whatsoever. I can still boot it into recovery and download mode just fine.
Looked into the filesystem and noticed the system folder was "empty". There were 3 folders (bin, etc, sbin)
Something else i found was the system_root folder in /, which contained the root file system PLUS all system files. Did i flash something wrong?
For the time being, i installed stock firmware. I hope to get this fixed eventually.
It goes to TWRP and i can flash, mount, backup, restore, ... from there.Well, the red warning message is normal, that means at least it flashed something correctly.
But wait, you said you can reboot to recovery? As in, TWRP recovery? Or does it go directly to stock recovery instead of TWRP?
Another thing, you can't view system stuff in this device with TWRP as of yet (I believe it's being worked on) so it is normal to not see anything inside that folder.
Well, if TWRP booted you were almost there. You just needed to do a real data format (loosing everything in the internal storage)It goes to TWRP and i can flash, mount, backup, restore, ... from there.
As i said, i am using stock recovery for now until there is a possible solution to this.
And I can see the system files, as it mounts the system to /system_root. All is there, it just can't boot.
I tried exactly that quite a few times. Even re-flashing the entire thing, booting to twrp, FORMATTING /data, rebooting to download mode, flashing again and formatting it once more didn't work.Well, if TWRP booted you were almost there. You just needed to do a real data format (loosing everything in the internal storage)
The bootloops could be a sign of the encrypted data partition.
And did you flash Magisk and the encryption disabler? Those are essential to making this ROM boot. Don't use normal Magisk, download canary.I tried exactly that quite a few times. Even re-flashing the entire thing, booting to twrp, FORMATTING /data, rebooting to download mode, flashing again and formatting it once more didn't work.
Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about flashing this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you. HARD!
Unlocking BL on modern Samsung devices have some caveats, so I figure this would be helpful.
Allow bootloader unlocking in Developer options → OEM unlocking
Reboot to download mode: reboot and press the download mode key combo for your device.
Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
Go through the initial setup. Skip through all the steps since data will be wiped again later.
Connect the device to Internet during the setup.
Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader.
Your bootloader now accepts unofficial images in download mode.
Worked perfectlyThere's a Magisk module called "Bluetooth library patcher" which fixes this issue. Apparently, its a common problem with rooted Samsung devices.
There's a Magisk module called "Bluetooth library patcher" which fixes this issue. Apparently, its a common problem with rooted Samsung devices.I'm using much less bluetooth now, but since I've installed NcX 2.5.2 my phone doesn't remember the paired devices, I should pair them every time I use it, somebody had or has the same problem?
Check out the latest projects on our Telegram group, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA
Check out the latest projects on our Discord, where we share our advancement on new things and try to help as best as we can.
For anything already released, please ask here in XDA