[SAMSUNG][Android 6.x/7.x/8.x] SYSTEMLESS DevBase v2.1 | Encryption support

[_alexndr]

Another update:

v1.3:
- Fixed CscFeature MOD (e.g. G920I case, now should work with all Samsung devices/variants)

>> SYSTEMLESS_DevBase_v1.3.zip <<

 

[nestade]

Seems like you have a problem with rooting the latest Nougat beta (without wipe), not with DevBase itself. Please try to solve rooting/bootloop problems in SuperSU's thread and then flash systemless DevBase if you still want to. I'm sorry, I have no other ideas :highfive:

Hi,

It seems to be a problem with TWRP without wipe - I already posted in their thread but nobody answered yet.
I also tried some more times to install it and always the same problem - so I'd have 2 questions:

1.: Did you also OTA from BTU (MM) or did you flash Nougat Beta 1 and did an OTA to ZPLN? (well same result if I flash Beta 1 and OTA to Beta 5 and flash TWRP)
2.: Will I be able to get OTA if I factory reset, flash TWRP without booting to system and flashing root + devbase or does it have the same effect like enabling modifications at startup of TWRP?

Regards,
Nestade

 

[_alexndr]

Hi,

It seems to be a problem with TWRP without wipe - I already posted in their thread but nobody answered yet.
I also tried some more times to install it and always the same problem - so I'd have 2 questions:

1.: Did you also OTA from BTU (MM) or did you flash Nougat Beta 1 and did an OTA to ZPLN? (well same result if I flash Beta 1 and OTA to Beta 5 and flash TWRP)
2.: Will I be able to get OTA if I factory reset, flash TWRP without booting to system and flashing root + devbase or does it have the same effect like enabling modifications at startup of TWRP?

Regards,
Nestade

1. To be honest I have flashed latest "dumped" Nougat beta. Personally I'm not in "beta program" so can't perform OTA in my phone

"Supposedly" it was 100% clean, but just noticed it isn't...

If you are 100% sure that you never swiped "Allow system modifications" in TWRP in your current system and never remounted it rw (*) - you can help me to re-produce your issue with rooting latest nougat beta (and find a workaround, if possible).

(*) you can check if you have untouched /system partition by re-flashing ZPLN Stock recovery (from HERE). Flash it, then enter it and see if there is "dm-verity error..." message (or not) at the bottom.

If you do NOT have such error message then GREAT please provide me exact dump of your /system partition (use Terminal Emulator from Play Store):

su
dd bs=4096 if=/dev/block/sda14 of=/data/media/0/system.img

Copy above file to your PC (it will be located in internal memory -> AKA emulated sdcard). Copy also your original (backed up by SuperSU installer) stock kernel - you can find it in both places - /cache and /data (it is named "stock_boot_****.tar.gz, where **** is SHA1 sum). Compress all files using zip or 7zip and give me DL link, please

2. Probably your device will not be able to boot (without wipe) if you unroot non-encrypted device but I'm not 100% sure (I never decrypted my /data @ G935F, yet...)

 

[_alexndr]

@nestade
I just tested your dump by flashing it into my phone (via TWRP's Terminal from OTG storage, due to encrypted /data not available under TWRP):

dd bs=4096 if=/usb-otg/system.img of=/dev/block/sda14
(I used system.img sent by you)

dd bs=4096 if=/usb-otg/boot.img of=/dev/block/sda5
(I used stock kernel image extracted from your attached backup)

dd bs=4096 if=/usb-otg/recovery.img of=/dev/block/sda6
(I used stock ZPLN recovery which I have, as you know)

Phone booted fine without root, with "Official" status, with all my apps and data (these are still encrypted, of course!). In stock recovery there is NO "dm-verity error..." message, finally! so it is exact same as yours (verified by recovery) stock ROM

My exact next steps:
- Flashed TWRP 3.0.2.4 via PC Odin and went directly to it (tap "keep read only", of course)
- Flashed SuperSU 2.79 SR2 ZIP (from OTG storage, due to encrypted /data not available under TWRP)
- Tap "Reboot System"

Phone booted fine WITH working root, with "Custom" status, with all my apps and data (remained encrypted, of course! There is no access from TWRP)


In sum - I still can't explain your problem with rooting latest beta.. I'm sorry

 

[nestade]

Hi,

Well - it's no problem.
By the way - I received the OTA to official Nougat Release.

OT: How can I extract the whole firmware to provide it to other users? (BL, AP, CSC, CP)

 

[_alexndr]

Hi,

Well - it's no problem.
By the way - I received the OTA to official Nougat Release.

OT: How can I extract the whole firmware to provide it to other users? (BL, AP, CSC, CP)

Issue with rooting encrypted ZPLN and DPLT confirmed

Warning has been added in #1

Let's hope @Chainfire will find a solution soon...

 

[babygau]

Issue with rooting encrypted ZPLN and DPLT confirmed

Warning has been added in #1

Let's hope @Chainfire will find a solution soon...

tks for ur warning, i couldn't wait to get my hand on the official nougat update. i've been using ur rom for months and nothing to complain about, battery life is great, phone is surprisingly smooth and fast performance-wise, i don't use xposed or magisk though. i don't even have a single crash since day one. ur approach is just unique, and i love that systemless idea. ur rom simply the best ive ever used since galaxy s5.

 

[nestade]

Issue with rooting encrypted ZPLN and DPLT confirmed

Warning has been added in #1

Let's hope @Chainfire will find a solution soon...

In my opinion it's caused by TWRP as it also appears if I only flash TWRP, "Keep read only" and reboot.

 

[_alexndr]

In my opinion it's caused by TWRP as it also appears if I only flash TWRP, "Keep read only" and reboot.

You're right... Just tested it - same here..

I skipped this important scenario and draw wrong conclusions WARNING has been edited:

Before:
(!) WARNING (related to rooting latest Nougat - e.g. ZPLN, DPLT): There are confirmed reports that installing SuperSU on encrypted phones causes bootloop. It is not just ordinary bootloop - phone will not be able to boot even if you restore stock boot image! You will need to wipe data to make your device bootable (losing all encrypted data, by the way)! Let's hope @Chainfire will find a solution soon.

After:
(!) WARNING (related to installing TWRP @ Nougat - e.g. ZPLN, DPLT): There are confirmed reports that entering TWRP on encrypted phones running Nougat causes bootloop (even if you just enter TWRP, tap "Keep read only", do nothing else and then tap reboot!). You will need to restore both - stock recovery and stock kernel (if you e.g. tried to flash SuperSU or other ZIP which might modify the kernel) to make your device bootable. In case of encrypted devices we need to wait for a solution..

 

[peyronnx]

Any hope for Nougat?
I guess we have to wait solution from Master ChainFire

 

[_alexndr]

Any hope for Nougat?
I guess we have to wait solution from Master ChainFire

At this moment there is only hope... and temporary solution (decrypted data = OTA impossible):
https://forum.xda-developers.com/showthread.php?p=70618589&postcount=8960

 

[nestade]

At this moment there is only hope... and temporary solution (decrypted data = OTA impossible):
https://forum.xda-developers.com/showthread.php?p=70618589&postcount=8960

Hi,

Is it still possible to flash the files manually with flashfire?
If yes, will I lose my app-settings etc./root/devbase?

 

[babygau]

i upgraded to nougat today with decrypted data and supersu 2.79, however i couldn't flash the dev-base file, it gave me "required files not found" on both csc and safe debloat feature. any idea?

 

[_alexndr]

I temporarily can't perform any physical tests as I broke display in my S7 edge :crying: I sold it for spare parts due to high price of screen replacement in the authorized Samsung service...

I'm going to buy next S7 as soon as possible but I'm not going to root it immediately (I need to test it some time to exclude hidden defects)

Hi,

Is it still possible to flash the files manually with flashfire?
If yes, will I lose my app-settings etc./root/devbase?

v0.55 shouldd work well with nougat (see changelog in #8):
https://forum.xda-developers.com/general/paid-software/flashfire-t3075433

i upgraded to nougat today with decrypted data and supersu 2.79, however i couldn't flash the dev-base file, it gave me "required files not found" on both csc and safe debloat feature. any idea?

I can't re-produce issue due to above "sad introduction" ...

Does this issue occur in both - TWRP and FlashFire?

EDIT: Check if you have physically required files, e.g. /system/csc/others.xml. I suppose that you flashed firmware via odin and then went to DM immediately after ROM flashing (WITHOUT performing all action from /cache by stock recovery). If I'm right - files in /system/csc/* really not exists (then it is NOT DevBase issue)

 

[babygau]

edit: pls disregard, you're right, i overlooked one of the step you mentioned above, i didn't boot the phone after wiping the data, hence the problem occur, all goods now

its sad to know u broke your phone. fyu, i flashed the firmware using odin, boot the phone normally, all bloatware are installed, i then installed the dev-base and got that error. reboot the phone and all bloatware still appear.

 

[babygau]

guys, been running dev-base with nougat for almost 3 days, it's been working flawlessly for me so far. since i enabled google assistant through build.prop and have fitbit app installed in favour of shealth, i found no need of svoice, sheath services and shealth app. i'd like to remove those. is it safe to do so? would it cause any prob with stock rom?

 

[Kamy]

guys, been running dev-base with nougat for almost 3 days, it's been working flawlessly for me so far. since i enabled google assistant through build.prop and have fitbit app installed in favour of shealth, i found no need of svoice, sheath services and shealth app. i'd like to remove those. is it safe to do so? would it cause any prob with stock rom?

Shealth works fine on a rooted phone. Just update following strings in build.prop

ro.config.knox=0
ro.config.tima=0

 

[babygau]

Shealth works fine on a rooted phone. Just update following strings in build.prop

ro.config.knox=0
ro.config.tima=0

thank you, but i think you misread my question. i meant to remove those apps, i don't wanna use shealth and svoice, based on @_alexndr suggestion from here. i'm wondering if there is any side-effects if i disable those apps, because it's known to deeply integrated into touchwiz

 

[Kamy]

thank you, but i think you misread my question. i meant to remove those apps, i don't wanna use shealth and svoice, based on @_alexndr suggestion from here. i'm wondering if there is any side-effects if i disable those apps, because it's known to deeply integrated into touchwiz

Yeah I got what you mean. But I guess after making any change in system you would lose the systemless feature and might not receiving OTA. Instead you can add all your unwanted apps in enforceskippingpackages.txt of the devbase.

 

[nestade]

At this moment there is only hope... and temporary solution (decrypted data = OTA impossible):
https://forum.xda-developers.com/showthread.php?p=70618589&postcount=8960

Hi,

Have you already tried the newer Nougat bases (DQAS, DQAN, DQAZ)?
Hopefully TWRP releases an update soon which fixes the encryption problem

Regards,
Nestade