Since almost one week i am trying to a S7 rooted, debloated and encrypted.
Starting encryption with a decrypted phone from CFW:
After installing a CFW on an decrypted, i were not able with two different CFWs to get it encrypted. If you select the encryption by AndroidMeni the process starts and after a few minutes, it does a usual reboot without any changes. I tried this method, and this as well. Some xda users told me, that i have to use stock. I had no chance to get it encrypted afterwards with selection through Android/Security menu.
Start with encrypted stock rom:
So i gave up and descided to start with stock (oct release) and encrypted.
Flashing Stock with Odin, let it reboot and let it encrypt on first start, go through the assistent, reboot to download mode and root with odin and cf-auto-root.
Dont have to install TWRP, hence doesnt make any sense. You dont get acces to /data nor to /sdcard (internal storage).
After that i tried several debloating scripts, some worked, some not. So i decided to debloat manually with SSHdroid & putty.
Then i recognized, that the apps were not removed, although the files were been deleted?!
I did a factory reset, now the phone was clean. But the encryption was gone
btw: my experiences with FlashFire were also negative. Somehow it doenst let FlashFire mount any partitions on restart. It just doenst work.
Do anyone have an idea, how can I use this damn S7 rooted, debloated and encrypted? I can live with stock too.
I lost my interest - just tired, wasted so many days. Just want to make my data on my phone safe against a thieve.
Thanks
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
TWRP is not fully supported under Oreo. It can't handle the full disk encryption. I've read that it is possible to set PIN / password *before* TWRP is installed and then it would work with the pass or pin you set before. But this didn't work for me. And I think there is no point in using it. Backup / restore function don't work and there might be more functions do not work.
If it's for magisk, there is also a way to install it without TWRP and / or there is no need to have access to storage. Installer just patches the ramdisk and you're good to go in ignoring the errors.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
JimZiii said:
So what are you using instead if you want to flash something? I found some posts saying you can get twrp working with the encryption if you do a factory reset and data format in twrp, that way you should get encryption that twrp can read but I've tried this several times and my phone refuses to boot every time, it's not even boot looping, it just stays on that blue honor loading screen and with the little animation in the text so it didn't freeze. If I then try to do a factory reset in stock recovery it stops on 99%, forcing me to reboot, it then starts over and jumps to 100 and when it boots up pretty much all apps are gone, even system apps and keyboard apps so you can't type. If I try factory reset again the same thing happens, stops at 99 and so on
Now I have to recover it through erecovery.
Yea, I patched stock boot in the manager instead
Click to expand...
Click to collapse
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
JimZiii said:
I updated to oreo but after flashing twrp I noticed that I can't use it because it's asking for decryption key.
How do I fix this? I found some post with a method to flash the rom without encryption but I'd like to keep the encryption if possible.
I think a factory reset fixed it the last time on nougat but last night my phone froze mid wipe which broke pretty much everything and took me a while to fix so I want to make sure this helps before doing it again
Click to expand...
Click to collapse
Try removing pin/password in settings and see if it still asks for key.
ante0 said:
Try removing pin/password in settings and see if it still asks for key.
Click to expand...
Click to collapse
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
cypher187 said:
It does. And I tried it already right after flashing RROS system image (treble) and before setting a PIN and / or after removing PIN.
Look here https://forum.xda-developers.com/honor-8/help/internal-storage-encryption-t3452737 for background knowledge about this encryption.
Only way to get TWRP fully working on our device is to remove encryption through formatting the storage. But the kernel will encrypt every time while booting and TWRP will not be able to access storage anymore.
With the Nougat custom ROMs this was not relevant because they were using LOS kernel not the stock one. Treble ROMs are using stock kernel - which is, of course, an advantage.
And I didn't get TWRP to work *with* encryption (with entering PIN or whatsoever). I hope anybody can and tell me how to do or what I did wrong
Also I want a (safe) way to use it. Specially as I know that it's use is not supported by OpenKirin Team it should be safe before I really want to use it.
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
You can Format Data (removes encryption) and edit /vendor/etc/fstab.xxxx and remove the fileencryption line on /data.
I don't have an Honor 8 so I can't check it, but this is how it was done on Mate 9/10 before we got TWRP with decryption on Oreo.
Of course, flashing a new firmware will replace fstab so you'd have to edit it again/restore previously edited one.
Edit: Also, for fun, default password for decryption is "default_password", so you could try that. It most likely will do nothing. This is done automatically when you have no password/pin set.
cypher187 said:
I didn't come in the situation to want to flash sth - except magisk. And I didn't want to try it as it gains no access to internal storage.
Boot screen takes up to 30 mins or more after formatting storage. Kernel encrypts it during this time. I cannot say if TWRP is able to read this encryption since it is hardware based. I think it is possible as TWRP should use same kernel on treble ROMs - as far as I know.
So... Just being very patient could make it - theoretically.
Let me know if it can :good:
Sent from my FRD-L09 using XDA Labs
Click to expand...
Click to collapse
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min ?
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
---
JimZiii said:
Oh ok, never knew it could take that long but I guess it makes sense. At one attempt I even waited 20-30min
I'll give it another shot when I got some time over.
But I just finished restoring everything from hisuite and changing back all my settings for the 6th time since hisuite don't save your system settings.
Do you know if it's possible to make a nand backup without twrp? Getting a complete nandroid backup would really help when you're not sure if the factory reset will help
Click to expand...
Click to collapse
Unfortunately there is no way. Only with HiSuite or sth else. If your device is rooted you can use TitaniumBackup. It can provide a more complete backup of apps, app-data and settings.
Sent from my FRD-L09 using XDA Labs
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Mumtaz77 said:
Hi.
I use the fstab mod and do a full data format in TWRP. After that the data partition decrypted, but FRP locked, oem unlock grayed and I can't do set my google account. If I want to set the google account, the process is start but the screen is turn to black (navigation buttons show on the bottom of the screen) and nothing more. Some seconds later its drop me back to settings page.
TWRP installed.
Bootloader unlocked
Rooted with Magisk
FRP locked
Stock recovery not flashed back because HWMT show FRP locked
Click to expand...
Click to collapse
Install a full package via dload method. Take an 'unbrick' guide from the guides section if you need. You can use a 'FullOTA' package for your region which you can download with FirmwareFinder by TeamMT.
Sent from my FRD-L09 using XDA Labs
My Google Pixel 2 phone is in a bootloop (perpetually showing G logo animation). I don't know if this was triggered by the almost full memory or by a mechanical shock. Simply, one morning it just refused to boot. However, after being stuck for several hours, it booted, worked fine for few hours and then powered off in the middle of taking a photo. Bootlooping since then. I tried various approaches with no success so far. There is locally stored personal data that is very important to me. I would appreciate very much any help provided to understand what is going on and recovering the data.
After discharging the battery completely (freezer) I was able to get into the Recovery menu, sideload two different replacement Android 8.1.0 OTA images via adb following the instructions on Maker, but the phone is still bootlooping. I also tried heating the back of the phone but I could not get it to boot that way either.
Device state is listed as: Boot-slot:a, Console: Disabled, Secure boot: yes (PRODUCTION), Device State: locked. According to recovery file oem flashing is supported but boot flash is currently locked.
What are exactly the limitations of locked device state and disabled console?
I was able to sideload update recovery OTAs. What is exactly locked and what can be still externally modified? The adb sideload process showed success message but the phone is not behaving any different, hence I am confused whether I have indeed managed to replaced the Android system code on my device with those from sideloaded OTA or not?
If yes, what could be the reasons that sideloading clean OTAs (neither the same - build G, nor a newer one - build Q) has not changed the situation at all?
From related posts it seemed that the almost full storage could be preventing the system to boot.
Would it make any sense to try to modify/patch these OTA images with some code that would e.g. delete some unnecessary data on the phone as early as possible in order to make sufficient space for the kernel to load? Perhaps deleting some swap file or temporary data would be sufficient?
Has anyone tried thist?
A
anyone?
anabbb said:
anyone?
Click to expand...
Click to collapse
First, you won't be able to modify the ota as it's signed by google and you'd need the signing key on any modified file.
If it's an issue with the storage being almost full you might try using adb to pull and then delete any large files you have.
Hi everyone,
I hope some of you are still following up on this device or maybe my query is not too specific after all...
To give you some background: When I rooted my Zenfone 3 Ultra in April 2019 the storage was encrypted such that I had to enter a key each time I powered it up. After ~ 1 year or so I could not access the OS anymore after a reboot because it said the key I entered was wrong. So I went to twrp and did a wipe in order to set everything up again, this time not using device encryption. I noticed that after this wipe the flash light and third party apps using the camera would cause crashes (black screen or immediate reboot). I could live with it so far but recently I thought more and more often that it would be nice to finally use the camera in third party apps. So yesterday I had some time and decided to address the issue by doing a factory reset.
Now the factory reset did not resolve the issue. I remembered that when I had rooted the device (and everything was still working) I had created a nandroid backup in twrp which I then restored. I included everything in the restore which was offerd by twrp, i.e. Boot, Data (excl. storage), System and System Image. Still the same issue. I am not sure anymore if I created the one nandroid backup which I still have before or after rooting but when I boot up the device and install Magisk Manager, Magisk is shown with the version I installed back then.
According to the ZU680KL unlock/root thread unlocking is not possible anymore. However, I would like to keep root / be able to regain it. I assume the latest firmware (UL-ASUS_A001-WW-14.1010.1804.75-user.zip) as well as the corresponding boot.img and recovery.img which @ndi provided in this thread (thanks!) would allow me to go back further. However, I noticed that in my boot menu it says "DEVICE STATE - locked", which already makes me kind of nervous due to the unlocking issue above. I just don't want to try anything else on my own because I am afraid to do something foolish. So maybe you can help me with these two questions:
With everything being as it is, how could I start as clean as possible without loosing root / the ability to root again?
If I was willing to sacrifice root access, how could I proceed to bring everything back to stock?
Or maybe you have some other idea to fix the camera issue. Any help will be appreciated.
Many thanks!
Hello again everyone,
I decided to move on and go back to stock. Eventhough I was not able to maintain/regain root, there is an approach that might be applicable to our device as well. Also, I would like to share what I found out regarding my initial goals (i.e. camera issues and resetting a rooted device).
Camera issues: It seems to me that these appear on (some?) ZU680KL devices running Android 7 (Nougat). They can affect the flashlight or the camera in general, as you can read here. I decided to go back to the latest Android 6 (Marshmallow) realease as suggested in the same thread. The system no longer crashes when I use the flashlight or the camera is used by a third party app. However I sometimes still need to start the camera app in order to make it work in third party apps.
Going back to stock: A guide for the Zenfone 3 siblings can be found here. I went back to stock using TWRP and a MicroSD card (with boot.img, recovery.img and ROM zip file):
I first flashed the boot and recovery (i.e. TWRP) partition with the stock images for the ROM I was planning to flash.
Then I booted into stock recovery and flashed the ROM zip file. The key combination to get into stock recovery was a little weird ('volume -' followed by 'volume +' while keeping 'power' pressed). It had to be entered during the 'no command' notification that was shown after choosing recovery from the fastboot menu.
After successfully flashing the ROM, I wiped cache and data and rebooted. I ran into a "Dm-Verity in EIO mode" error (see attached). This error had already occured after my last try to restore a nandroid backup in TWRP but I could resolve it with the steps described in this youtube video and repeated (2.). When I think about it now I guess I should have started with (3.) right away because of the Dm-Verity issue.
Regaining root: I think this is something yet to be done but it does not seem completely hopeless.
I hope this can be of help if you face any of these issues.
Hi,
I recently tried to install audio_hq magisk module, but i tried SE enforce. Now my phones boots for ages, then says that the android system is corrupt and that i should factory reset the phone or try again. However, I’d like to not lose my app data and the settings i spent a while tuning. I have access to fastboot, bootloader is unlocked, phone is rooted. I heard something about installing twrp and fixing perms (if that’s the problem) or using adb to modify the module file to disable SE, but i cannot find twrp for my phone. I have LiveBoot if a picture of the logs is needed or something
How can i fix this without losing my data ?
CSAE