Related
Hey,
Is there a way to disable force encryption? I tried format data in TWRP and flash Magisk without reboot. Ends up in a bootloop. ?
Thx
No, there's not.
Sent from my ONEPLUS A6003 using Tapatalk
i cant seem to edit the fstab in twrp located in /vendor
it gets restored to stock after a reboot, so i think the fstab is being loaded from the boot img
The Android P DP2 kernel doesnt have force encryption, so my storage isnt encrypted!
---------- Post added at 14:38 ---------- Previous post was at 14:38 ----------
B3501 said:
No, there's not.
Sent from my ONEPLUS A6003 using Tapatalk
Click to expand...
Click to collapse
thats wrong
Interesting. Is the Android P DP 2 Kernel compatible to OOS 5.1.8?
I think we need a patched boot image with disabled Dm-Verity and Force encryption entries in the fstab file.
[WORKING] Decrypt Oneplus 6 by virtyx
https://forum.xda-developers.com/oneplus-6/how-to/test-decryption-t3818775
Disable_Dm-Verity_ForceEncrypt .for oneplus 6T will do?
Disable_Dm-Verity_ForceEncrypt .for oneplus 6T will do?
Hi,
I just flashed the latest stock update.
The problem is that I can't decryt my data in TWRP, and hence cant flash anything from internal storage.
Is there any TWRP build that supports encryption/decryption ?
A Taiwanese regularly compiles TWRP up to date with the security updates on Zentalk (TW). You can check this MEGA folder every month he uploads to. The latest one works with .339
In case you cant fix it, next time make sure that you flash the files in this order: rom, magisk, decrypt.zip
farhanshaikh671 said:
In case you cant fix it, next time make sure that you flash the files in this order: rom, magisk, decrypt.zip
Click to expand...
Click to collapse
Sometimes people actually want their data encrypted, so that's more like a dirty fix.
farhanshaikh671 said:
In case you cant fix it, next time make sure that you flash the files in this order: rom, magisk, decrypt.zip
Click to expand...
Click to collapse
What is the difference when applying in rom, magisk, decrypt compared to rom, decrypt, magisk?
I use the latter method always because that is recommended by this guide:
https://forum.xda-developers.com/as...to/rom-update-stock-firmware-keeping-t3808269
camlin said:
Hi,
I just flashed the latest stock update.
The problem is that I can't decryt my data in TWRP, and hence cant flash anything from internal storage.
Is there any TWRP build that supports encryption/decryption ?
Click to expand...
Click to collapse
No you have to factory reset
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
itcanbdone said:
Just got the xt1687 usa model retus software channel... Is it safe to flash potter roms on here?
Click to expand...
Click to collapse
What firmware? 7.0 or 8.1? If you are on 8.1 it's as safe as it ever is to flash a custom ROM.
If you're still on 7.0 you should update first and in any case make a full nandroid backup incl. Persist and EFS before you flash anything.
Sent from my Moto G5 Plus using XDA Labs
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
itcanbdone said:
Currently on 7.0 so unlock bootloader n twrp after update? Thanks
Click to expand...
Click to collapse
Yes. If you can update via OTA that should be the way to go. If you can't flash full Motorola signed fastboot 8.1 firmware:
https://mirrors.lolinet.com/firmware/moto/potter/official/
Unlock the BL on Motorola website, boot to or flash TWRP and make a full nandroid incl. persist.
After that you shoud be good to go and flash custom ROMS. Check whether the selected ROM needs 7.0 or 8.1 as base, almost all of them need stock Oreo.
Sent from my Moto G5 Plus using XDA Labs
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
itcanbdone said:
Oh yeah, I'm rusty.. Software channel duh, linux gets its stuff there... I guess it is potter xt1687, which is odd though as a website said it wasn't potter.. Anyway, looking in the gsm arena and checking against other variants of our g5 plus, it seems that everything but the radios are the same so is it safe to flash variants backing up the original radio? Thank you very much
Click to expand...
Click to collapse
You wrote you're on the retus channel and model is 1687. Here are the firmwares for your device, the second one ( OPS28.85-17-6-2) is the latest and last build, flash that one and everything should be fine:
https://mirrors.lolinet.com/firmware/moto/potter/official/RETUS/
You still know how to fastboot flash? Unzip firmware to ADB/Fastboot folder etc.?
Here's a post I made for someone else, it includes a link to a flashall.bat, put in in there too so you don't have to manually flash all partitions, just double-click it and it'll run all the commands for you.
https://forum.xda-developers.com/g5...solve-imei0-explanation-t3825147/post80478329
Sent from my Moto G5 Plus using XDA Labs
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
itcanbdone said:
So I was on stock and flashed twrp after successful unlock of bootloader. After backing up, got stuck at bootloader before any further changes made, yet it was booting fine with bootloader before that.. Saw in a post to flash stock after re locking bootloader, then unlick again...
I skipped that just to get a rom on, now running havoc 9.0 but cannot seem to root as the two su & magisk arent cuttin it in twrp.
Are you really telling me I gotta revert back to stock and flash root in stock to get root?
If so, couldnt i just flash havoc 8.1 and root that way.
Yes i still remember how to flash via adb. Thank you very much
Click to expand...
Click to collapse
I'm not sure that I understand everything. After flashing (official) TWRP and making a nandroid you weren't able to boot to system, only to bootloader?
Have you updated to 8.1 stock Oreo before?
Havoc needs that definitely:
https://forum.xda-developers.com/g5-plus/development/rom-havoc-os-v2-2-t3906282/post79018816
It won't make any sense to revert to stock and root it because after flashing havoc root will be lost anyway. What do you mean with "the two su & Magisk aren't cuttin it in TWRP"? (English is not my native language)
Why two? There should be magisk only to flash.
So the goal seems to be making TWRP work correctly when running havoc to be able to flash magisk.zip and boot to system.
Can you post a recovery log after the attempt to flash magisk from TWRP (the function is in TWRP/ advanced/log.)
Can you boot to havoc directly now?
Are you able to reach TWRP?
I need the error message that appears when you try to flash magisk, should be in the log.
And what is it about two things, su AND magisk?
Magisk.zip is the su binary.
Please provide some more information and sorry if it's me who don't understand something.
Sent from my Moto G5 Plus using XDA Labs
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
itcanbdone said:
- I got root after all. Seems I was just flashing no verity before root and it was suppise to be after.
- there was a super su which I'd rather have to mod things with but neither worked until i figured out as mentioned above
- now I'm trying to get gaps to work..
- also having problem flashing rom withou encryption, it keeps forcing it encrypted.
- here is link to 3 images of what i've got currently:
https://mega.nz/#F!q3pVQIDJ!kwfNgjMEEssa97rrZJjWHg
Thanks
Click to expand...
Click to collapse
Never use SuperSU alongside with magisk but I think you know that now.
To remove encryption: It's not enough to wipe data in TWRP, you have to format it (the option where you have to confirm with "Yes" and not just wipe). That will wipe your internal storage too.
Only formatting data in TWRP will remove the encryption and the Disable_Dm-Verity_ForceEncrypt_02.04.2019.zip will keep it decrypted. Make sure usb debugging is enabled.
Boot to TWRP and flash ROM and Gapps (both in one action without a reboot in between).
Now flash the no verity-force encryption.zip.
You can reboot to system now but you can also flash the magisk.zip directly afterwards, it helps to keep the data partition encrypted too.
I flash everything in a row.
Check that thread: https://forum.xda-developers.com/g5-plus/how-to/guide-how-to-remove-device-encryption-t3863586
(page 2)
Sent from my Moto G5 Plus using XDA Labs
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
itcanbdone said:
Thanks for the encryption link.. Any idea on the pros n cons on encryption in the world of flashing zips and modding?
I see pros n cons on google search for encryption but not from developments perspective
Click to expand...
Click to collapse
I decrypt my device, for example to have access to /data in case of a bootloop because of a magisk module. I don't like the idea of not physically seeing parts of my partitions or even not being able to edit it.
From the sight of security it's better to encrypt naturally. It depends a bit how old your device is and what you want to do with it.
I never lost my device or it was getting stolen so as long it's in my pocket I don't need encryption.
But that's just my personal opinion.
Sent from my Moto G5 Plus using XDA Labs
Hey so I found a really cool way to decrypt but ROM after it's already been encrypted and you have all your stuff in it, I figured it out on accident. What I did was simply did a backup through TWRP and formatted the drive. When I restored the drive it was decrypted! And all this time everyone ever told me that you cannot decrypt. Pretty cool. Actually found this out by switching to a ROM and then going back anyway maybe people should know this? Hope it helps thanks for all the pointers
I made a better way to flash GSIs
https://forum.xda-developers.com/nubia-red-magic-5g/development/swapper-generate-flashable-zips-img-t4133591
Go here and use that.
Nubia's bootloader and fastbootd is **** and both can't flash images to the logical partitions like the system partition and vendor partition.
So we need to build an image for the super partition to be flashed.
If you just wanted to flash a custom rom skip part 1 and download the super.img from the link (los or havoc, havoc recommended as los's brightness control is half broken)
Requirements: An unlocked RM5G booted into the bootloader (not fastbootd, if you don't know what that is, you probably are in bootloader), An A/B GSI image (yes we need a A/B image not an A-only image, from android 9 released devices all phones are systeam as root), A linux environment (I did it in WSL), the download file
BACKUP YOU'RE SUPER PARTITION BEFORE FLASHING AND SAVE IT SOMEWHERE SAFE BEFORE FLASHING
(Seriously, tho I figured this out while trying to unbrick my phone after ****ing up my super partition. Trust me, it will be a life saver. Doing this will also break flashing stock ota rom via recovery until you flash your backup)
Part 1: Building the super image
Download tools.7z and extract it
Place the GSI image in the same folder and rename it to system.img
Execute the lpmake.sh script in a linux environment (It will say invalid headers at magic, it's not an error so just ignore it)
When it is complete there will be a super.img file in the folder (takes about 1 min)
Part 2: Flashing the super image
Before we flash the super.img we have to disable verity.
flash vbmeta and vbmeta_system with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
(You don't have to flash these every time. Just once)
Now we can flash the super.img with
fastboot flash super super.img
You also have to wipe dalvik, cache, data
If you have twrp do it in twrp.
If you don't, you shouldn't be doing this, I told you to backup your super partition.
That's it.
Tested GSIs:
LOS 17.X : Boots, Wifi/Data/BT works, Brightness control is half broken (always at full brightness)
Android 11 DP3 : Doesn't boot
Havoc 3.4 : Boots, 3.5 doesn't work
Phh-Quack : Doesn't boot
Descendant X : Boots, same as LOS
Oh, and for people wondering about the fingerprint sensor. It doesn't work. The phone doesn't even know it has it under the display(Maybe a problem with all under display fingerprint sensor phones).
After more testing, found out slot count can be 1 instead of 2.
Link to files
https://drive.google.com/open?id=1DuQp2_uebwRr9mD5MQxibQGdPBQyPkHN
Wow amazing, so we can use any other gsi except the one forced by these guys
Sent from my NX659J using Tapatalk
---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------
apersomany said:
https://drive.google.com/open?id=1DuQp2_uebwRr9mD5MQxibQGdPBQyPkHN
Click to expand...
Click to collapse
Also does everything work like the air triggers and the fan ect
Sent from my NX659J using Tapatalk
keep it up. the fingerprint sensor is a goodix sensor it was the problem on other devices too. we will need to ask nubia for the goodix sources to fix it.
is the fan, gaming triggers and 144hz working? also what about the slider any functionality?
gokhujee said:
Wow amazing, so we can use any other gsi except the one forced by these guys
Sent from my NX659J using Tapatalk
---------- Post added at 09:55 AM ---------- Previous post was at 09:53 AM ----------
Also does everything work like the air triggers and the fan ect
Sent from my NX659J using Tapatalk
Click to expand...
Click to collapse
Sadly air triggers, fans, 144hz, slider doesn't work (Maybe it'll work if we port the app to the rom)
For the fingerprint sensor I'm gonna try some things.
apersomany said:
Nubia's bootloader and fastbootd is **** and both can't flash images to the logical partitions like the system partition and vendor partition.
So we need to build an image for the super partition to be flashed.
If you just wanted to flash a custom rom skip part 1 and download the super.img from the link (los or havoc, havoc recommended as los's brightness control is half broken)
Requirements: An unlocked RM5G booted into the bootloader (not fastbootd, if you don't know what that is, you probably are in bootloader), An A/B GSI image (yes we need a A/B image not an A-only image, though the treble info app says that our device is A-only, it's not), A linux environment (I did it in WSL), the download file
BACKUP YOU'RE SUPER PARTITION BEFORE FLASHING AND SAVE IT SOMEWHERE SAFE BEFORE FLASHING
(Seriously, tho I figured this out while trying to unbrick my phone after ****ing up my super partition. Trust me, it will be a life saver. Doing this will also break flashing stock ota rom via recovery until you flash your backup)
Part 1: Building the super image
Download tools.7z and extract it
Place the GSI image in the same folder and rename it to system.img
Execute the lpmake.sh script in a linux environment (It will say invalid headers at magic, it's not an error so just ignore it)
When it is complete there will be a super.img file in the folder (takes about 1 min)
Part 2: Flashing the super image
Before we flash the super.img we have to disable verity.
flash vbmeta and vbmeta_system with
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_system vbmeta_system.img
(You don't have to flash these every time. Just once)
Now we can flash the super.img with
fastboot flash super super.img
You also have to wipe dalvik, cache, data
If you have twrp do it in twrp.
If you don't, you shouldn't be doing this, I told you to backup your super partition.
That's it.
Tested GSIs:
LOS 17.X : Boots, Wifi/Data/BT all works, Brightness control is half broken (always at full brightness)
Android 11 DP3 : Doesn't boot
Havoc 3.4 : Boots, So far everything works, Probably will stay on this
Oh, and for people wondering about the fingerprint sensor. It doesn't work. The phone doesn't even know it has it under the display(Maybe a problem with all under display fingerprint sensor phones).
Click to expand...
Click to collapse
So you got your phone working again! Nice Is volte calls working on havoc?
And it looks like you uploaded the converted gsi images? Thanks
NO WIFI for me on havoc
VZTech said:
So you got your phone working again! Nice Is volte calls working on havoc?
And it looks like you uploaded the converted gsi images? Thanks
NO WIFI for me on havoc
Click to expand...
Click to collapse
That's probably because you're boot.img is not from the same version as mine (2.46) try flashing the one I uploaded to google drive
apersomany said:
That's probably because you're boot.img is not from the same version as mine (2.46) try flashing the one I uploaded to google drive
Click to expand...
Click to collapse
Your not having issues? Mine is laggy, calls not working
VZTech said:
Your not having issues? Mine is laggy, calls not working
Click to expand...
Click to collapse
The lag goes away if you turn the screen on and off.
apersomany said:
The lag goes away if you turn the screen on and off.
Click to expand...
Click to collapse
Ouch, this isn't good
Thanks for the super img tools/instructions - this will actually come in handy on another device I'm working on.
MishaalRahman said:
Thanks for the super img tools/instructions - this will actually come in handy on another device I'm working on.
Click to expand...
Click to collapse
The script has a fixed partition size specified for the rm5g so you might wan't to change the partition size.
there seems to be a workaround to keep Fingerprint functionality while rooting and even with twrp installed. it seems it's even possible to lock the bootloader at the same time. will wait for xda guides to explain as i don't understand it yet. i saw video evidence and it's pretty easy. the guy even forgot oem unlock in dev options and it still worked for him.
only cn rom supported it seems. and it's a similar guide to the redmagic 3.
apersomany said:
The script has a fixed partition size specified for the rm5g so you might wan't to change the partition size.
Click to expand...
Click to collapse
Wondering if we could add the ims.apk to the image??? Its needed for volte. If its done on the os, the phone doesnt boot.
VZTech said:
Wondering if we could add the ims.apk to the image??? Its needed for volte. If its done on the os, the phone doesnt boot.
Click to expand...
Click to collapse
It's possible, but I would rather make a magisk module for it, it takes way less time.
apersomany said:
It's possible, but I would rather make a magisk module for it, it takes way less time.
Click to expand...
Click to collapse
I tried adding it. Didnt boot. Just a black screen. exactly which havoc did you use?
VZTech said:
I tried adding it. Didnt boot. Just a black screen. exactly which havoc did you use?
Click to expand...
Click to collapse
I used https://forum.xda-developers.com/pr...e-development/havoc-os-3-3-gsi-archs-t4076903 this one, specifically the Gapps Included ARM64 A/B version.
apersomany said:
I used https://forum.xda-developers.com/pr...e-development/havoc-os-3-3-gsi-archs-t4076903 this one, specifically the Gapps Included ARM64 A/B version.
Click to expand...
Click to collapse
Thanks. I used that ones too. I extracted the system image, added the file, repacked, then used the tool to convert to super, but it wouldnt boot.
VZTech said:
Wondering if we could add the ims.apk to the image??? Its needed for volte. If its done on the os, the phone doesnt boot.
Click to expand...
Click to collapse
VZTech said:
Thanks. I used that ones too. I extracted the system image, added the file, repacked, then used the tool to convert to super, but it wouldnt boot.
Click to expand...
Click to collapse
Hmm... That's weird.
Have you increased the size of the partition that you've added the file to in the script? (If it was added to the system img probably won't matter as I've set the value to something like 3gigs if I remember correctly)
So doing it without adding the file works, but if you add it it won't boot right?
nadejo said:
there seems to be a workaround to keep Fingerprint functionality while rooting and even with twrp installed. it seems it's even possible to lock the bootloader at the same time. will wait for xda guides to explain as i don't understand it yet. i saw video evidence and it's pretty easy. the guy even forgot oem unlock in dev options and it still worked for him.
only cn rom supported it seems. and it's a similar guide to the redmagic 3.
Click to expand...
Click to collapse
Yes in our forum in Telegram: ZTE Nubia Redmagic 5G Channel people are using the Chinese ROM and bypassing the bootloader unlock. I have not yet tried. We are perfecting the process ATM. We even got a guy to restore a TWRP backup of Global ROM. It isn't an easy process. You have to be very, very careful. There are a lot of wipes that go on in between. Will post once we have a 100% working solution. Under the Bootloader Unlock tutorial in XDA for this device.
Hello guys! I installed twrp but it doesnt allow me to decrypt data so i cant flash anything. Any solutions??
Thanks in advance!!!
ionakos said:
Hello guys! I installed twrp but it doesnt allow me to decrypt data so i cant flash anything. Any solutions??
Thanks in advance!!!
Click to expand...
Click to collapse
What is your ROM and which TWRP do you use?
Use the official TWRP.me twrp-3.6.0_9-0-davinci.img and it will work with up to MIUI 12.5, A11, supporting Data encryption
For A12, there is no TWRP yet supporting its Data encryption. You could use OTG stick - e.g., put the zip file you want to flash to OTG
zgfg said:
What is your ROM and which TWRP do you use?
Use the official TWRP.me twrp-3.6.0_9-0-davinci.img and it will work with up to MIUI 12.5, A11, supporting Data encryption
For A12, there is no TWRP yet supporting its Data encryption. You could use OTG stick - e.g., put the zip file you want to flash to OTG
Click to expand...
Click to collapse
Iam using 3.6.0 and iam on miui 12.1.4 global and it doesn't even ask for pin to decrypt data. I even tried previous versions of twrp
ionakos said:
Iam using 3.6.0 and iam on miui 12.1.4 global and it doesn't even ask for pin to decrypt data. I even tried previous versions of twrp
Click to expand...
Click to collapse
Try changing unlock from pin to pattern, or disable screen unlock
For me, on EEA it worked fine
zgfg said:
Try changing unlock from pin to pattern, or disable screen unlock
For me, on EEA it worked fine
Click to expand...
Click to collapse
I've tried all these things and it still doesn't ask me for encryption password
ionakos said:
I've tried all these things and it still doesn't ask me for encryption password
Click to expand...
Click to collapse
I'm on Xiaomi.eu Stable 12.5.2, it's better ROM:
MIUI 12.0 - MIUI 12.0/12.1/12.2/12.5 STABLE RELEASE
STABLE RELEASE RULES WHEN POSTING 1. If a ROM is not published DONT ASK ABOUT ITS ETA 2. If a ROM is not published DONT ASK why! 3. If a ROM is available, download it and use it 4. If a ROM has bugs, post the bug to the bug section if the BUG is not already listed 5. If you use any form of...
xiaomi.eu
zgfg said:
What is your ROM and which TWRP do you use?
Use the official TWRP.me twrp-3.6.0_9-0-davinci.img and it will work with up to MIUI 12.5, A11, supporting Data encryption
For A12, there is no TWRP yet supporting its Data encryption. You could use OTG stick - e.g., put the zip file you want to flash to OTG
Click to expand...
Click to collapse
Hi, need some more info about the OTG to flash, I was on LOS 18.1, upgraded to LOS 19.0, only realized now no TWRP to decrypt A12, you mean we still can flash the system update or zip (magisk) via TWRP with OTG even though it does not decrypt internal data? flash system update or magisk zip via TWRP will goes through? I thought encryption would be whole phone?
gl7 said:
Hi, need some more info about the OTG to flash, I was on LOS 18.1, upgraded to LOS 19.0, only realized now no TWRP to decrypt A12, you mean we still can flash the system update or zip (magisk) via TWRP with OTG even though it does not decrypt internal data? flash system update or magisk zip via TWRP will goes through? I thought encryption would be whole phone?
Click to expand...
Click to collapse
It will read from OTG and flash to System or Boot, hence Data and Internal storage are not needed
Nevertheless, I would suggest for Magisk to Patch the boot.img and to flash from Fastboot