Related
After religiously backing up everything I could, I'm about ready to wipe my SGS3 and put a new custom ROM on it. The reason I need to fully wipe the SGS3 is because I require disk encryption on the SGS3, and no TWRP version was able to successfully decrypt my phone, nor Phil's; I figure I must've encrypted it using a non-supported method which allows for decryption in the ROM but not in TWRP. Also it happens my modem is still MK3 and my version of SlimKat is a little bit unstable with random reboots every few days (I hear they all are, so I'm looking at other well-optimized ROMs).
So I just want to know --- anyone successfully decrypted using custom recovery on a non-TouchWiz KitKat ROM?
I am going to root my Nexus 5x very soon. I have some doubts, please help me to clarify those.
1. If I want to go with systemless root, I wouldn't have to flash modified boot.img. In that case will I be able to disable force encryption? If yes how?
2. If I have understood it correctly, in order to have disabled force encryption, I have to wipe user data after flashing SuperSU zip. Now in order to keep the encryption disabled, I have to wipe user data each time I flash a custom ROM or kernel?
I may seem noob in this question, but I am going through these encryption business for the very first time, so I thought its better to clarify rather than bricking my first Nexus [emoji6]
Thanks in advance.
Sent from my C6902 using Tapatalk
nondroid said:
I am going to root my Nexus 5x very soon. I have some doubts, please help me to clarify those.
1. If I want to go with systemless root, I wouldn't have to flash modified boot.img. In that case will I be able to disable force encryption? If yes how?
2. If I have understood it correctly, in order to have disabled force encryption, I have to wipe user data after flashing SuperSU zip. Now in order to keep the encryption disabled, I have to wipe user data each time I flash a custom ROM or kernel?
I may seem noob in this question, but I am going through these encryption business for the very first time, so I thought its better to clarify rather than bricking my first Nexus [emoji6]
Thanks in advance.
Sent from my C6902 using Tapatalk
Click to expand...
Click to collapse
You need to reformat userdata to remove the encryption. You do not need to continue to wipe after that for encryption purposes since it wont get re-encrypted unless forced encryption is enabled or you encrypt it. You will need to have a kernel/boot.img without forced encryption or it will re encrypt itself.
Systemless root has nothing to do with encryption and you could flash TWRP and root with SuperSU 2.6+ and still be encrypted.
A good starting place here
If I have got it right then I have to either flash boot.img or a kernel that disables force encryption in order to continue disabled force encryption.
Thanks for the clarification.
Sent from my C6902 using Tapatalk
Keithn said:
Systemless root has nothing to do with encryption and you could flash TWRP and root with SuperSU 2.6+ and still be encrypted.
Click to expand...
Click to collapse
Right and wrong at the same time...
Systemless root does disable force encryption: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The stock kernel will force encryption.
The stock kernel + systemless SuperSU will not force encryption.
Assuming you have all stock but TWRP installed, you would format data to remove encryption, then flash systemless root to stay unencrypted.
berndblb said:
Right and wrong at the same time...
Systemless root does disable force encryption: http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
The stock kernel will force encryption.
The stock kernel + systemless SuperSU will not force encryption.
Assuming you have all stock but TWRP installed, you would format data to remove encryption, then flash systemless root to stay unencrypted.
Click to expand...
Click to collapse
I see that the posted boot images don't have forced encryption along with other changes, but I didn't see anything saying it was necessary to use a kernel without forced encryption to have root. Does flashing 2.60+ also modify the kernel to disable force encryption (If enabled) when it does the necessary modifications for root? You can still be encrypted with systemless root so I figured that forced encryption would have no impact on the systemless root.
Edit- Looked at the script and it looks like it is supposed to. So whether it actually matters or not, it won't force encrypt after flashing SuperSU.
I recall that installing SuperSU on the HTC10 was originally a special case. Due to the encryption it used, originally flashing SuperSU onto the HTC10 would break the cellular radio, eventually SuperSU was updated to fix this.
I want to know if Magisk is in the same boat, or it could break your radio too like SuperSU used to, or if the way it works does not cause this issue on the HTC10.
And if so, can it be installed in place of SuperSU without having to wipe/reset your data?
I haven't used Magisk so I can't speak from experience.
However:
1) I know in the ICE Rom thread, that users have recently asked for an aroma option not to have SU installed (or PHH SU installed rather than SuperSU) so they can more easily get Magisk working.
2) Secondly, the original developer of Magisk has a HTC 10.
It's a pretty safe bet to say Magisk works if you follow the instructions...
Nearly all the instructions recommend wiping your data though, and that's not an option for me.
the Dev from Magisk has a HTC10 as main device ^^
so Magisk works flawless (except maybe sprint/verizon).
Super Su is not recommended anyway, as you can read on post Nr 2.
i've been using phh's SU for a while now and havent had a single issue.
AFAIK you dont have to wipe data but restore Stock System (Image) and kernel.
stock boot.img is important to wipe the Ramdisk.
I am already on the stock rom, all I originally did was unlock the bootloader then flash SuperSU, I never flashed a custom rom.
Works fine for me!
Works great for me on Leedroid.
1) Full unroot with SuperSU (don't restore anything)
2) Flash Magisk
3) Flash PHH root
4) Install Magisk Manager
5) Install PHH SuperUser
How is Magisk better than systemless SuperSU ?
CroCop18 said:
How is Magisk better than systemless SuperSU ?
Click to expand...
Click to collapse
Its not to say one is better than the either.....
To put it in VERY simple terms (There is much more to it)
Magisk is a utility for rooted related mounts and SElinux permissive status. It allows all mods to be truly systemless. It also allows rooted users to still have the ability to utilize Android Pay. You can read MUCH more at http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
To use Magisk effectively at this point, you need PHH SuperSU.
Magisk, systemless xposed, phh supersu are all under the same umbrella and are designed to be used together.
It works perfect for me on the HTC 10 with the multiple ROMS, including stock, that I have tested. I have used SUPERSU for as long as I remember, but in this case, the modified chainfire supersu did not work smoothly for me in the systemless magisk envionrment. Gotta give thanks to both topjohnwu, PHH and chainfire alike!
Does anyone know if you use magisk will that allow you to take ota updates from HTC or will the ota updates not work using magisk either ? Another question if anyone knows I have an Unlocked HTC 10 but may get the new Marlin due out being made by Htc so I am also wondering if magisk will work and you still get your updates from Google using magisk. I just thought maybe someone one here might know rather than try to go through tons of pages on that thread itself. I am hoping so as that would rock if you could still get your ota updates and have root too using magisk.
By the way, why did you say I might have problems if I am on Sprint?
Cyber Akuma said:
Nearly all the instructions recommend wiping your data though, and that's not an option for me.
Click to expand...
Click to collapse
they say it's recommended.
this is my experience ce seting up Magisk on a LG g4 (h811) running Resurrection Remix, and super su. I have an unlocked bootloader.
my main concern was maintaining viper4android (originally installed with arise (I don't remember the version))
I downloaded all the files for magisk plus the rom (resurrection remix official, just in case I needed to start clean)
I booted into twrp, made a complete backup (system would have been enough, but safety first)
I then rebooted into Android and backed up viper4android from /system/priv-app/. removed the following, super su binary, super su app, busybox/app, Viper driver then the app, and a few other root apps installed to system (I simply deleted the apk from /system/app and /system/priv-app)
now I rebooted back into Android, once booted I rebooted into recovery
and installed all Magisk requirements, and then Magisk viper4android mod.
and finally wiped cache and dalvik/art
now I shut down for about 30 minutes (phone got too hot) stupid snapdragon 808
booted back into Android, opened play and installed the Super user needed for Magisk.
now I open kernel adiutor and allow su access (need to turn off cpus 3-6)
Now I open play and install Google pay and safetynet playground.
now I open Magisk manager, and disable root.
Open play I add my cards fine.
I exit play, and open safetynet playground and check, it passes.
now I enable root again.
I install the Viper I backed up earlier as a user app, and try and use it. Nope it's trying to Install the driver. I cancel and remove it and install the official Viper.
it works fine (remember I already installed the Viper Magisk mod earlier)
Now I'm golden.
Now I never cleared my data, but I did clear dalvik/art and cache.
the only part of arise that I changed was the Viper version, I removed arise version of viper from /system/priv-app and installed the official Viper as a user app)
in all I'm just saying make a backup and try without wiping data.
I chose to wipe dalvik/art and cache because of the major change on the device.
This may or may not work for hboot lock devices. (I'm using a LG g4 (h811))
the release thread does say you need an unlocked bootloader
Hello fellow XDA members and flashaholic people! This is a guide about flashing sGSI or GSI (semi-GSI) Android Pie images on VINCE.
This guide is for VINCE only! Please don't try it on WHYRED it may work or it may not.
First you need to treble enabled custom recovery. I suggest OrangeFox V8.1 https://forum.xda-developers.com/redmi-note-5/development/official-orangefox-recovery-project-t3807479
You can either flash it via TWRP or extract zip and flash recovery img by fastboot method.
Second you need treble enabled custom Oreo ROM, I suggest Cardinal-AOSP as it's vendor.img works flawlessly. https://forum.xda-developers.com/redmi-note-5/development/rom-cardinalaosp-t3774232
And third step includes the GSI image. You can find several GSI's here; https://forum.xda-developers.com/project-treble/trebleenabled-device-development
After downloading .zip file from any ROM you wanted extract it to get its system image and move it into the either internal storage or SD card. [SYSTEM IMAGE ONLY NEEDED]
I tried Pixel Experience 9.20 and Havoc OS 9.18 builds both booted without issues.
Please note that you need GApps package for ROM's (Except PixelExperience) you can find them here; https://opengapps.org/ Suggested package is Nano one. But if you want more you can go for bigger packages. I always use Mini version of it.
Steps to get Pie working on our device:
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
PLEASE KEEP IN MIND I DO NOT DEVELOPING ABOVE GSI IMAGES OR HELPING TO DEVELOP. IF YOU HAVE ANY BUGS TO REPORT PLEASE REPORT IN PROPER FORUM POST. I CAN HELP ABOUT INSTALLATION ONLY.
Ah, and there is few screenshots i'll share (Pixel Experience 9.0):
Don't need to flash p lag fix, volte fix and other stuff?
Ritik17 said:
Don't need to flash p lag fix, volte fix and other stuff?
Click to expand...
Click to collapse
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
bdogan1912 said:
Since i did not have any problems about lag or freeze dont need to flash it. Though im not sure about VoLTE but it seems broken for me too. I still wait for official or unofficial Pie ports (which even redmi 2 and 3 got)
Click to expand...
Click to collapse
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
moralesnery said:
Any other bug or issue that you've found in the ROM? Camera problems? Bluetooth or Wifi's MAC changing or reverting to 00:00:00...? Battery drains, memory leaks, crashes? GPS problems? anything?
Click to expand...
Click to collapse
In few hours of usage i did not encountered very-serious level bugs. Battery was fine and didn't seemed like to draining. Bluetooth and WiFi had no issues for me either. Only VoLTE doesnt works and as may you know thats global issue on it. Did not faced any mem-leaks or running out of memory problems, with freshest install it used up to 1.3 GB mem and with some apps like social ones it went up to 1.6 to 1.9 GB but ROM was overall butter smooth without single lag or freeze. No FCs either, GPS works i guess it was enabled by default on fresh install as usual but since im not using the GPS that much i did not tested it fully though.
As you can guess those are still experimental/beta builds could have issues that i did not encounter. But overall was very fine for me. I'd keep it but it kinda messed "about phone" settings as it goes manufacturer and model both goes by unknown or phh-treble. It's very natural since i installed as GSI image but still bothered me.
Almost forgot; In Havoc OS settings goes direct crash if you touch battery in settings. PE works fine but it has problems with Dark theme beign not applied correctly. Also i did not used or tried substratum or its themes.
Thank you for your instructions. I wanted to install a GSI 9.0 ROM since Pie came out, but other threads with instructions were too complex or convoluted that I thought it was harder.
I would like to make some clarifications on your steps:
* I used the unofficial PixelExperience 9.0 GSI image, as you said. It feels and behaves almost exactly as the official PixelExperience build for our device, but with nicer interface. The image is HERE. Just as a sidenote, the System image comes with DPI = 360, things look a bit too big. To make it look like MIUI or the official PixelExperience build for vince, a dpi of 390 should be set (this can be done from settings > System > Developer Settings > Minimal Width, under the "draw" section).
1. Reboot to custom recovery (if you have) flash OrangeFox R8.1 treble-enabled recovery. [If you have already have OrangeFox Recovery skip this step]
2. Touch Wipe and wipe /system /data /cache /dalvik and format /data
* At this step, I had to make "Format Data", and only then reboot to recovery again, and make the wipes to all other partitions. Without rebooting the wipes weren't possible (it was showing errors while trying to mount partitions). VENDOR PARTITION SHOULD NOT BE WIPED
3. Flash cardinal-aosp ROM to your device You do not need to install GApps as we are going to use Pie anyway.
4. After flashing reboot to system it will directly go into launcher without setting stuff up. Reboot your device to recovery again.
At this point, you must check that the hardware works correctly. Touch, screen, audio, BT, wifi, RIL, LTE or whatever you use. If something doesn't work at this point, it won't work after installing the GSI image.
5. Touch install, touch install image and flash the system image you've extracted. Wait for it to complete.
* In OrangeFox, at this point before flashing the GSI's .img file, the recovery asks for the type of image. For noobs and careful people, "System Image" must be selected before proceeding.
5.1 If you installed other than Pixel Experience please install proper GApps right after. [IF GAPPS WONT INSTALL BOOT THE DEVICE INTO SYSTEM FIRST AND WHEN BOOT COMPLETED PLEASE REBOOT RECOVERY AND FLASH GAPPS IT WILL WORK] After GApps installed go to wipe and do a factory reset in recovery. Reboot the device into system.
6. After you set up your device there is several optional operations you can do;
6.1 Root: You can use Magisk v17.1 or above to get root access. [Flash via recovery, if Magisk app wont appear in app menu you can install it from apkmirror safely]
* When installing Magisk through recovery, the framework will be installed, but the APK won't appear in the app list. It must be downloaded separately from https://github.com/topjohnwu/Magisk/releases/download/manager-v6.0.0/MagiskManager-v6.0.0.apk
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Cast and mirror screen are broken. After choosing a screen to share the phone's screen to, SystemUI will crash. Apps with cast capabilites won't detect Chromecast devices (the cast button won't appear).
Thank you for your help
moralesnery said:
The following modules are working without issues in my setup:
* Youtube Vanced
* Google Product Sans font
* MagiskHide Props Config
6.2 Modules: Magisk modules like V4A, Unified Hosts Adblock etc. works. [Tested].
6.3 Kernel: You can use Genom Kernel or Dark Ages Tercero kernel. [Tested Dark Ages Tercero, works]
Thank you for your help
Click to expand...
Click to collapse
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Can't Show the Image File
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
GizPrime said:
After extracting the Hovac OS GSI file (a link that given) can not show Image file it shows file different files in different formats.
Click to expand...
Click to collapse
This is the correct link, you don't downloaded gsi file (I did the same thing, currently running Havoc 9 ):
https://sourceforge.net/projects/havoc-os/files/arm64aonly/
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Biggest thanks to you as i was in dilemma to try the PE 9.0.
However, the stock camera is so dark so i installed Camera2API, resulting the camera app FC, installed the crashfix Gcam apk i found somewhere in this thread not so long ago to no avail, the camera is still broken. Anyone having the issue ?
TIPS: I tried both Dark Ages and Genom Kernel, the brightness is crazy, i think its the late display driver provided within it: the brightness level is scaled incorrectly, with the 50% on MIUI is 0% in PE, and 50% in PE is equal to 100% of MIUI (the max brightness is at 50% and sliding all over to the right does nothing); clean flashed the whole thing and not using custom-installed kernel at all.
HungNgocPhat said:
I don't know what is "MagiskHide Props Config" but is MagiskHide working normally for you?
I'm currently using the Pie "V4 zip" from this thread but MagiskHide isn't working. If it is working normally for you I will try to flash in your way then.
And can I flash 9.0 GSI image over any 8.x roms? Or it must be PE or Havoc?
Click to expand...
Click to collapse
MagiskHide Props Config" its a module that replaces the ROM's fingerprint with a certified one. This way you get ctsProfile: true and basicIntegrity: true, thus passing SafetyNet. This combined with MagiskHide allows me to use some apps that rely on SafetyNet.
After flashing the Treble-enabling ROM (Cardinal OS) you can install GSI system images based on Oreo or Pie.
Is hotspot working in PIE GSI?
dahrel22 said:
sadly i can't flash pie rom because my phone is encrypted. i will try this someday, once i backup my files and do the full format (including internal storage)
i want to try PE pie
Click to expand...
Click to collapse
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Wyneg said:
If you use orange fox recovery you can wipe encripted partitions and flash custom roms, try it!
Click to expand...
Click to collapse
seems like i need to do a format data in recovery. but right now i cant afford to loose all my files in internal storage. once i back up all my file then i will do the format data.
i wish there is some way to decrypt my storage without formatting
btw, i got my storage encrypted because i flashed miui stable rom
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
moralesnery said:
And.. what If I installed a Treble ROM and I want to go back to stock MIUI, or a non-treble ROM? What should I wipe before going back?
Click to expand...
Click to collapse
If you do same wipes what you did to flash GSI it's totally ok
expextors said:
it's work but hotspot doesn't work
in cadinal i already check it's work but in gsi have a problem
Click to expand...
Click to collapse
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
soyti2x said:
Weird cause hotspot is working fine for me. My kids phone is able to connect without any problems.
Click to expand...
Click to collapse
i tried on havoc it doesn't work what your gsi you used ? i can't open hotspot because always off when turn on
For obvious reasons I am a big fan of custom ROMs and rooting. However, I also like Samsung Cloud. It does a more thorough job of restoring my apps and app data than the Google backup and it is a lot easier to use than Microsoft's Onedrive. However, when ever I update to the latest Samsung stock (XAR-T830XXU4CTG4-20200918235621) and root it with WETA kernel and Magisk, it breaks Samsung Cloud so it is not accessible. It doesn't happen on the previous stock (XAR-T830XXU4CTF5-20200625212120).
pastorbob62 said:
For obvious reasons I am a big fan of custom ROMs and rooting. However, I also like Samsung Cloud. It does a more thorough job of restoring my apps and app data than the Google backup and it is a lot easier to use than Microsoft's Onedrive. However, when ever I update to the latest Samsung stock (XAR-T830XXU4CTG4-20200918235621) and root it with WETA kernel and Magisk, it breaks Samsung Cloud so it is not accessible. It doesn't happen on the previous stock (XAR-T830XXU4CTF5-20200625212120).
Click to expand...
Click to collapse
UPDATE - I actually found a procedure to install Magisk root without a custom ROM or Kernel. It entails using Magisk Manager to modify the original AP portion of the stock ROM and substituting the modified version when doing an Odin flash of the stock ROM. No WETA kernel or TWRP required. Much cleaner as far as I am concerned. Encryption is kept and all stock apps and backups work 100%.