Hi, I came from 4.2.2 stock rooted. I was updating to 4.4.2 (D80220a-ESA-XX) via LG Support Tool and make it go back to stock unrooted again. Next I rooted using ioroot25. After a fresh flash, I performed encrypt phone but the process was too fast, I was amazed until I checked that the disk wasn't actually encrypted.
I did again, but this time I was using factory reset via Backup and Reset and performed encrypt phone, but same result. The device just rebooted and blank, no android logo with encrypting process shown thus the encryption process failed.
Is this a bug? Anybody here face the same problem?
Any help will be appreciated :good::good:
I finally went back to stock, the encryption was working out. Here is what i've done:
Run make_ext4 /dev/block/mmcblk0p35, reboot again and apply encrypt phone (failed)
Back to stock using offline mode and re-apply encryption (success)
Root, Install TWRP and reboot (failed, TWRP 2.7.0.0 didn't prompt password for encrypted partition)
Install PAC ROM and CM 11 via TWRP sideload (success), BUT both of ROMs can't open the encrypted storage (failed)
Back to stock again, root, install TWRP, install PAC ROM, boot into PAC and apply encryption (failed, the PAC ROM can't perform encryption, it's just back to boot normally). This applied to CM as well.
My conclusion, LG has performed their owned encryption method instead of using AOSP method. I can't understand why PAC and CM failed performed their encryption method while using AOSP encryption method.
For now, I'll stick to stock since I need the encryption.
Related
I searched for my particular issue and haven't found a solution that works yet so here goes. any help with this issue would be greatly appreciated.
I've painted myself into corners before tinkering with this phone and always found a way out but this time I'm stumped.
HOW I BROKE MY PHONE:
1) had latest CM 11 nightly installed but wanted to try the OTA.
2) In TWRP I restored a back up of my stock rooted software.
3) Unfroze bloat in titanium back up.
4) Checked on phone for OTA, received notification, and began download
5) On completion of download I initiated the update.
6) It booted to recovery (TWRP) and every time I rebooted, or started the phone from powered down it always goes into TWRP.
7) I attempted a factory reset and restoration of my stock back up- same result. It booted straight into recovery.
8) I factory reset and installed cm11 fresh from the SD card- same result
9) Here's my real screw up: since neither installing a fresh ROM or restoring my stock recovery weren't working I went for the nuclear option, I decided to format everything and use the LG Flash tool to get this puppy back up and running.
10) Only to discover I can't get into Download mode and while the G2 is "seen" by my PC it's listed under "other devices."
Dear kind and wise individual who's read my tale of woe. What might my next step be? I've considered attempting to sideload a ROM with TWRP in sideload mode, but I'm afraid I'd just have the same result as when I tried reinstalling CM11 from the SD card.
this
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Many thanks! I'll give this a try.
Hello Guys
So i was trying to update my rooted Decrypted Nexus 6P from 7.0 to Developer preview 7.1 .
I followed the instructions to flash the OTA zip and then root it with SuperSu (http://forum.xda-developers.com/nexus-6p/general/available-android-7-1-developer-preview-t3483739).
I then flashed Franco's latest kernel as I usually end up doing that. The phone booted fine, but of course the camera had some problems as reported here (http://forum.xda-developers.com/showpost.php?p=69226309&postcount=373) which meant that the Franco kernel was at 7.0 and I needed 7.1 kernel.
So stupidly enough I just extracted the boot.img from the 7.1. OTA zip and flashed it through flashify app to revert to stock kernel for 7.1 and just re-started my phone.
But since that boot img was not patched it forced encryption on the phone which I did not realize until I found the phone was sitting at the boot animation for a long time and I just force re-started it.
Wrong decision . Now I have a phone that boots up to a screen which says Encryption Unsuccessful and has a button which asks me to wipe all the data.
Booting into TWRP asks me password for decrypting the data partition which I assume would be my PIN and supply it, but it sits on message saying 'Decrypting data' and just sits there endlessly. I have tried this as well (http://forum.xda-developers.com/showpost.php?p=66163153&postcount=826) i.e. trying the 3.0.0.1 twrp but that one does not like the PIN that I supply.
I followed this (http://forum.xda-developers.com/verizon-htc-one-m8/help/decryption-unsuccessful-currently-t3074855) to extract the whole data partition from my phone and essentially I have this 58 GB file which i tried to mount in Linux but unfortunately there is nothing that i see in that partition.
Is there anyone who has encountered this and has successfully retrieved their data??? I know it was stupid of me that I didn't take a backup of my internal storage plus the nandroid backup I had is on the phone .
Any help is much appreciated.
Thanks
Hey fellas,
so I rooted my phone and tried to install some Magisk modules, but after rebooting it got stuck in the TWRP bootloop. So I flashed the Nandroid backup and it got stuck in the OOS boot animation. After that I tried reflashing OOS, but it didn't change anything, so I tried Lineage OS and now it won't even get past the Oneplus logo at the beginning and keeps restarting.
Thanks in advance
EDIT: when I flash the stock ROM through TWRP it installs normally, but then when I try to reboot it says there is no OS. So I flashed the stock OS to try adb sideload, but my pc says it cannot read the zip.
I also decrypted my phone through the OP5 Decrypt App, before the bootloop it worked for some time.
Of course I wiped everything before every action.
if you can bootup into recovery, try go into advanced and format data and system.
if you can't your last chance is using adb - flash a default rom.
Is it any different than wiping everything? Because it didn't do anything. I can access both twrp and fastboot so I guess it's not that bad
sounds like you went from unencrypted to an encrypted rom and your data is encrypted, or visa versa.
yep, it's vice versa, I used the OP5 Decrypt App after rooting. Is OP5 encrypted by default?
If you've tried the Android 8.0 Rom, just go to the official OP5 support site and download stock rom, flash it via ADB sideload if you can. (Don't forget to format data etc etc..) and restart from scratch.
Unlock BL if it's relock, then flash TWRP and go for a custom ROM. That's what I did, happened to me 2 days ago.f
EDIT : Oh you just flashed Magisk.. Well, try this anyway.
I tried flashing Lineage, but I can't install Oxygen
Ok, so apparently OOS boots up only after relocking the bootloader. And I had to make adb use more RAM to get sideload to work.
Hi,
sorry if that question has been already answered, but I cannot find an clear answer
I need to encrypt my cell phone, however each time I try I get an error telling that the encryption
did not finished correctly, and my cell phone is corrupteur and need to Factory reset
Is there a 7.1.2 Rom that exists with encryption working ?
if not do you know if a 6.x Rom exist that's support encryption.
Many thanks for your help.
I finely found a way to have ZUK Z1 encrypted under 7.1.2.
Below steps used:
Factory restore using All in One tool
Flash TWRP Official 3.0.2
Using TWRP installation of a 6.0 ROM
After boot and setup, enter Preference/Security/Encrypt
At this point ZUK Z1 appears encrypted
The issues are that under TWRP unable to mount or see files
I flashed lineage and open_gapps using the “adb sideload” option.
After a reboot, ZUK Z1 appears as encrypted
For the time being all is working fine, except the fact that TWRP cannot mount the device, because it’s encrypted. I guess that’s an issue with TWRP itself. I don’t know if a version exists to fix this ….
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Ecoka said:
I tried to do it same way with several 6.0 ROMs still available here (a lot of dead links...) but each try using device encryption ends with an
automatic reboot and back to welcome screen without encryption.
At the moment I am using TWRP 3.1.0 (comming fomr 3.0.2) with 7.1.2 Nuclear ROM.
Any ideas? Device Encryption is important for me.
Click to expand...
Click to collapse
The 6.0 ROM that's worked for me was " Temasek-20160217-NIGHTLY-ham "
Make sure you fully factor restore using the All In One tool
boot your phone on V5 and setup your cell phone account
Then using TWRP install V6 ROM with the Temasek one.
then Encrypt your phone .... that's should work ok
then us "adb sideload" to inject the V7 Lineage ROM
Let me know at which step you are stuck !
Hey, sorry for long delay ...
It will work up to "Temasek-20160217-NIGHTLY-ham", flashing AOSP 4.6 (Android 7) by sideload will cause "Password wrong" problems while booting
decrypting data partition. Still hope to get a way working zu install AOSP 5.1 (Android 8.1) with full encryption. Tried TWRP 3.02 and newer 3..2.1.
no worry about "password", I already installed nightly build of Lineage without issues using sideload.
Of course I got the message about password, I just ignore it
the only point is that I had to install TWRP V2.8.7 and not 3.x. because with 3.x sometimes I was not able
to boot recovery mode.
Before each install I fully backup my cell phone in case of .... SMS, Pictures etc...
Good luck,
The problem is not the password while starting to recovery 3.x.x, its the password while booting...
1. Factory restore using All in One tool (okay, works)
2. Setup Phone and encrypt (works, okay - Password will be accepted)
3. Flash TWRP (3.02 / 3.2.1.0) - tried both (okay, works - Password for encryption Recovery will not be accepted
4. I skip that and sideload flash (clearing cache etc.) "Temasek-20160217-NIGHTLY-ham.zip" (okay, Recovery = not, While Booting = Password accepted) (I choosed PIN and something like : OfferMe#1963ZU several times)
5. I skip Password in Recovery and sideload flash (clearing cache) "lineage-14.1-20180124-nightly-ham-signed.zip" (okay, Recovery still not, While Booting = Password NOT accepted)
Seems no matter if Lineage ROM 14.1 or higher...
Still confused
I am not using password at boot. I only set a password to unlock the phone after boot.
Hi,
I'd like to have root and xposed installed and keep the encryption enabled, I don't care about backing up the data partition or creating nandroid backups, so having a custom recovery is not important.
I've followed these steps:
- Flashed stock Oreo firmware using Odin 3.13
- Flashed TWRP 3.2.1.1, then boot to it.
- Flashed no-verity-opt-encrypt-6.0 and Magisk v16.0 from TWRP then rebooted.
but I still get Verification failed.
I've also tried to patch the boot image using Magisk Manager and flash it with Odin, but got the same results.
Can anyone tell me what else do I need to do?
Phone is Exynos (SM-G935F) edition.
Thanks.
Any luck
Hi
Just wondering if you had any luck with this?
Im actually trying to get the OREO stock ROM to allow internal storage to be accessed in TWRP so I can do a Nandroid backup but I can never seem to get it to work.
Everytime I come back it cant mount data.
Ive tried flashing ROM then TWRP immediately after.
Boot into TWRP install Magisk and no verity then reboot to system.
Once i come back data is gone. Are you able to access data in Recovery?
This custom ROM is as close to stock as possible less the unnecessary bloat. As far as I am aware, this is the only Oreo ROM that you can encrypt. Make sure you follow the instructions and then you'll have an encrypted rooted phone running Oreo:
[ROM][G935F/FD][ALEXNDR] * U2ERF4 (Oreo) * DevBase v5.8 * Encryption support [Jul-03]
https://forum.xda-developers.com/s7-edge/development/rom-dqd1-devbase-v4-1-multi-csc-safe-t3591647