Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
FrozenLord said:
Hi there,
Today I received my Xperia Tablet Z and sure enough, the first thing I did was flash a custom Rom
But my device wouldn't boot up anymore...
Basically I unlocked the bootloader via Sony's key, flashed a boot.img via fastboot and then flashed the Rom via the recovery.
All I got was a bootloop - regardless of which custom Rom I used (AOKP, Cyanogen stable, Cyanogen nightly, Cyanogen unofficial, ...)
I tried doing a factory reset but to no avail.
I manually checked for each delete / wipe option in the recovery, but the device simply would not boot further than the boot animation.
However, after some time I stumbled across a Rom that contained the TWRP recovery instead of CWM.
And this one asked me for a password when I booted.
"A password? What for?!"
Well, simply cancelling the request works.
But it seems that my whole problem had to do with that password request
As it turns out, the data partition was encrypted would not let me access it.
For some reason unknown to me, it was not wiped in CWM (some error popped up when trying to format /data).
TWRP allows for doing a format on this one ("full wipe" if my memory does not fool me) and voila - the tablet would boot!
So to sum it up:
After unlocking the tablet, there might still be an encrypted /data that can't be accessed by any custom Rom.
Wiping this /data solves the problem - and can be done via TWRP.
I just banged my head on that issue for 5 straight hours - downloading new custom roms, looking for similar bootloops, ...
Maybe this information will help someone
Click to expand...
Click to collapse
I usually just hit the thanks tab but feel I have to than you personally for this post. After hours of messing about I found this post, flashed the TWRP recovery, wiped data and was able to flash and boot my xperia..
Thank you for sharing this info..
For others searching you can get the twrp recovery in this rom http://forum.xda-developers.com/showthread.php?t=2383800
Hi guys i tried using twrp 3.1.1.0 and it says password for unmount data. Also my phone in settings says encrypted.
I tried wiping data cahce, etc but that diidnt worked also using default_password but that diddnt worked as well
Model x820 stock ROM
Zlade112 said:
Hi guys i tried using twrp 3.1.1.0 and it says password for unmount data. Also my phone in settings says encrypted.
I tried wiping data cahce, etc but that diidnt worked also using default_password but that didnt worked as well
Model x820 stock ROM
Click to expand...
Click to collapse
Have you try reboot the phone into normal Android system? and later try reboot into TWRP, I read somewhere it might work.
Moon75 said:
Have you try reboot the phone into normal Android system? and later try reboot into TWRP, I read somewhere it might work.
Click to expand...
Click to collapse
Hi guys the solution for my me was doing an entire wipe of everything except recovery then flash rom, it seems that the stock rom of le max was causing that
What was your ROM in the beginning? Was it Indian ROM? Did it have the update manager? Which ROM did you flash after wiping everything except recovery?
I bought the phone from geekbuying with EUI version 5.8.019S (Stable), BUILD: FGXOSOP5801910121S release-keys. It looks like the latest vanilla Indian ROM, but it is most likely vendor-modified since the phone was received unsealed and there is no update manager. The main problem is the encryption - phone is encrypted right from the start without any password or PIN prompts. Factory reset allows to set up everything from the start, but the phone is still encrypted. TWRP asks for a decryption password. I have tried multiple vendor and default passwords with no luck. TWRP factory reset does not prevent the encryption.
This question keeps coming up in forums since people do not seem to search for similar questions. Well, I did. Therefore, I will try to assemble the list related to the encrypted ROM:
https://forum.xda-developers.com/le-max-2/help/eui-roms-support-device-encryption-t3516825
https://forum.xda-developers.com/le-max-2/help/wiping-to-install-rom-le-max2-suddenly-t3518405
https://forum.xda-developers.com/le-max-2/help/update-eui-t3480614
https://forum.xda-developers.com/le...dian-stock-19s-rom-chinese-bloatware-t3484388
https://forum.xda-developers.com/le-max-2/help/benefit-form-leaving-x829-to-indian-t3609698
Proposed solutions:
CASE 1: No Update manger + encrypted ROM
Since it is a vendor ROM, you can try flashing a clear stock ROM from recovery that can be downloaded from the official LeEco forum http://forum.le.com/in/eui_detail.html?euiid=206 . It might not directly resolve encryption, but will make the update manager appear, which can be used to upgrade to ROM w/o encryption. If you want to stick to the Indian ROMs, but want to remove encryption - see below
More reading here: https://forum.xda-developers.com/le-max-2/help/update-eui-t3480614
CASE 2: Encrypted ROM
You most likely have an Indian ROM. You can try reinstalling the ROM (TWRP) and immediately wiping the data partition from TWRP. Some users report success with this.
More reading here: https://forum.xda-developers.com/le...dian-stock-19s-rom-chinese-bloatware-t3484388
One user has found that upon multiple resets with TWRP the encryption seems to be ignored
More reading here: https://forum.xda-developers.com/le-max-2/help/benefit-form-leaving-x829-to-indian-t3609698
Another user suggests Chinese ROMs since they are likely not to encrypt the files. In other words, updating to a Chinese ROM might help.
More reading here: https://forum.xda-developers.com/le-max-2/help/plz-help-unskilled-x829-user-to-update-t3609639/page2
Have any of the proposed solutions worked for you?
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
gordonthegopher said:
Formatting /data in TWRP uses up all the blocks, but encryption from Lineage needs 16kb of free space at the end of the partition to store the headers.
Click to expand...
Click to collapse
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Hi guys,
I'm kind of stuck right now because I cannot encrypt my phone anymore and I don't know why. I got my phone last year and installed LOS 14.1 right away. For security reasons I also encrypted it - without any issues whatsoever. When LOS 15.1 came out, I upgraded my phone, with encryption still working. A couple of days back for some reason I decided to do a factory reset. Obviously, the device wasn't encrypted anymore after the reset. I then installed the new nightly of LOS (20180807) and tried to encrypt my phone once again. When I select "Encrypt phone", I need to enter my PIN, the phone restarts and reboots without encryption being started.
What I've done so far:
I've flashed two different TWRP versions: 3.2.3.0 and a customized one (https://forum.xda-developers.com/re...other-development/rom-lineageos-15-0-t3690465).
I've clean installed different LOS versions (unofficial LOS 14.1 and LOS 15.1 starting from the 20180710 release)
I've clean installed Omnirom (current release and a release from 20180107).
I've even flashed MIUI 9 and reinstalled LOS thereafter because some guy in the above mentioned LOS thread wrote, that this did the trick for him.
I've disabled WI-FI and mobile data before trying to encrypt my phone, because I found a blog article stating that this might help.
Nothing helped. The phone just reboots and stays unencrypted.
Do you guys have any additional hints or ideas how I can manage to encrypt my phone once again? Could another TWRP version do the trick? Is TWRP even involved in any kind when it comes to encryption of the OS? Do you think another ROM could be helpful?
Click to expand...
Click to collapse
Try orangewolf recovery ....
Sent from my Redmi Note 4 using Tapatalk
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
shakil002 said:
Try orangewolf recovery ....
Click to expand...
Click to collapse
Thanks for the advice. But I'm afraid it didn't help
CanBostanci said:
I'm also having trouble with this. Many days ago, someone told they had successfully encrypted their phone. I tried to replicate what he did, got miui.eu and flashed LOS afterwards.
After tons of restarting, reflashing, all kind of stuff, the encryption still doesn't work. Pfff.
Click to expand...
Click to collapse
That's the most ****ed up part. For some people it does work, for some not.
There surely must be some ridiculous small detail we're not getting. Like disabling WI-FI while Bluetooth is enabled.
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
parkbank said:
Things I've also tried:
installed a new kernel: ElectraBlue (https://forum.xda-developers.com/re...rnel-electrablue-kernel-redmi-note-4-t3655651)
flashed an old LOS 14.1 with kernel 3.18.31 which I found here
used different screen lock types (PIN, password, pattern, swipe)
charged my battery up to 100%
reformatted my data partition with f2f
Of course, my device is still unencrypted...
Has anyone any idea why encryption might fail? I mean, it did work in the past with LOS 14.1. So why does it even fail with an old release of LOS 14.1? I don't do knowingly anything different to all the times I've successfully encrypted my phone in the past.
Does the factory reset still leave some files untouched?
Click to expand...
Click to collapse
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
CanBostanci said:
Mmm, maybe it's about the firmware? I was almost going to try lineageos 14.1...
Click to expand...
Click to collapse
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
parkbank said:
Huh... I didn't even think about the firmware. That would explain why the one user who flashed MIUI before installing LOS could actually encrypt his phone. I'll definitely give it a try.
Click to expand...
Click to collapse
I'm looking forward to hear the results. I'm about to become insane because of this encryption issue.
I've flashed both the dev and stable firmware found in this thread. No success
By flashing I mean factory reset, flashing the firmware and then installing LOS. I noticed, that flashing a new firmware while a ROM is still installed leads to some random ****ups.
After a couple of days of flashing, factory resetting, re-flashing, reading and a lot of cursing I finally found a working solution. I've added the fix to my initial post. Hopefully this helps
I was looking for solutions for quite a while and nothing else worked but did this and my device is encrypted again.
Thank you!
parkbank said:
I finally managed to find a working fix for this issue after having found this post. The origin of the problem is TWRP:
Fix
You have at least two solutions to fix this issue:
Resize your /data partition to free up the needed space. Here and here are guides how to do it. I haven't give it a try, so I can't confirm it's working, but several other guys reported this fix working.
If you're not comfortable to resize your partition, you can use an old version of TWRP. Beginning with version 3.2.0.0 TWRP seems to use up all blocks for /data. So you need a version prior to this one. I've used TWRP 3.1.0.0, but 3.1.1.0 should also work. Step by step:
Download and flash TWRP 3.1.0.0.
Boot into recovery and do a factory reset: Main menu -> Wipe -> Format Data (confirm with "yes"). I also wiped Cache and System (Main menu -> Wipe -> Advanced Wipe).
If you're going to flash a Nougat based ROM you can stop reading and start flashing and encrypting
If you're going to flash an Oreo based ROM you now need to update your TWRP version as anything prior to 3.2.0.0 doesn't support flashing Android 8.1. The official TWPR version sucks because you won't be able to decrypt your phone when booting in recovery. I've used the TWRP provided in this post.
Install your preferred ROM and encrypt it.
I haven't tested it, but dirty flashing a ROM (without a factory reset) might also work. But this usually leads to some random ****ups.
Also the TWRP alternative "Orange Fox" was mentioned as a solution in this thread. I actually can't remember if I've used Orange Fox to factory reset my phone or if I've flashed it only after having performed a factory reset using TWRP. For me Orange Fox didn't work (= encryption didn't work). But you might give it a try...
Original post
Click to expand...
Click to collapse
You have save my day "my MIDO" hehehehe
After the 1st PIE Rom the encryption was broken.
Your Step by Step save this and now Syberia 9 was able to encrypt with success :good:
Thank you one more time for sharing.
Thx!
---------- Post added at 07:22 PM ---------- Previous post was at 07:20 PM ----------
Orangefox worked
is there any plan to fix twrp itself?? thx
Thank you. It worked for me to get Havoc OS 9.0 with hardware encryption on my Redmi Note 3 SE.
I bypassed unlocking the bootloader by doing this. Then I installed TWRP 3.1.0.0 from the recovery, did the reset and everything as instructed here, updated it to 3.3.1.0, rebooted, then flashed the Pie ROM and latest gapps without any further wiping.
I use the first link, I've modified the partition size -> did the trick wihtout formating nor loosing datas
Great, thank-You.
Hi, I want to ask, what is this encryption features you been using? can u tell me?
Hello
I was at RUI C07 stock firmware.
I've managed to unlock the bootloader and to install TWRP 3.4.0. Then I've tried to flash derpfest (android 10), LineageOS and RevengeOS.
All of them seems to have flashed successfully, but TWRP always warns that there is no OS installed when I try to reboot. When I do reboot, it tries to load something, fails and goes back to TWRP.
What is the problem? Should I try to flash vbmeta? Where can I find it? I'm completely lost.
Thanks in advance
I've just followed the "unbrick guide" and there was little developement...Now the phone boots to fastboot/bootloader by default. I can boot to recovery if I request it. But if I just turn on the system or if I request system, it stops at the bootloader.
What a roller coaster ride!
What seems to have worked for me was to flash yet another ROM (crDroid). But this time I made sure that I've formatted DATA, and then I've wiped vendor, system, caches, internal disk.
I may have forgotten to format the data partition before, which might have been the cause for so much trouble.
If you are reading this, don't forget to format the data partition before flashing a custom ROM, at east when coming from the stock rom.
Hello!
Yesterday, I updated my phone from A10 to A12 with full OTA and applied magisk on inactive slot.
After rebooting, all seems to work, no bootloop, android was optimizing apps... so far so good, I reached the point where my patter was asked. There was no problem with it.
The problem appeared when trying to open any APP and the android answer was (for any app) "Failed to read the app data. Cannot start the app"
Okay, I tried to go to settings and was unable to do so. After putting phone in airplane mode, settings worked but clearing apps cache or data did not help.
Trying to fastboot boot twrp.img did not work until I found https://github.com/rabilgic/twrp_device_oneplus_hotdogb/tree/Android-12.1 by another xda user.
Even being another device it worked (afaik they were unified twrp so they should work for both). However, once booted, the first problem appears. Inserting my patter did not decrypt the data in twrp... Booting into system removing pattern and try TWRP again and nothing changed...
Checking in twrp the data/data lead see all folders and files encrypted there... So this is probably why any app is working...
After reading, I saw that fbev2 was applied to A12 so this might be the problem. My guess was that flashing a A11 rom might save my data since the encryption should be the same older one v1. However, I am unable to flash ROMS with TWRP... Tried with OTG or sideload, but both failed. I would like to know if there is a way to flash an older rom (A10 whcih was my original one or A11) to decrypt the data or make the A12 decryption work to recover all my apps and data.
I do not know if flashing any further (of if I had already) lost the decryption keys or what is going on.
I had extracted the .img from a full A10 OTA (OOS) and I am hesitant of flashing all 32 images to the phone or if that will wipe data partition.
How can I proceed if possible without losing data with a flash, or how can I decrypt the data to make it work with A12?