Related
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Same here...i flash all nougat rom and got bootloop..now i stay in mm only...:C
Reflash newest stock image, than hack the emmc bootloader of it and try again
reemar said:
Reflash newest stock image, than hack the emmc bootloader of it and try again
Click to expand...
Click to collapse
So you mean to flash the latest stock ROM, won't it remove TWRP and lock the bootloader? And how to "hack" the emmc bootloader? Sorry, I'm a newbie
Just wait for at least 15 minutes after flashing
DdroidTHEGAMER said:
Just wait for at least 15 minutes after flashing
Click to expand...
Click to collapse
What do you mean, wait in TWRP for 15 minutes or when booting up the OS? As I said, I waited for 30+ minutes while it booted up.
Try installing ROM without flashing the firmware
Minions007 said:
Try installing ROM without flashing the firmware
Click to expand...
Click to collapse
That was the first thing I did (I didn't know a firmware was needed so I only flashed the RR ROM). Same bootloop
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
SpeRator said:
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
Click to expand...
Click to collapse
Did it, same result. Wiped everything, copied zips to internal storage, flashed from there and boom, bootloop
Hmm strange. You could test a good modified rom of rr.
Try this Rom:
https://www.androidfilehost.com/?fid=673791459329049490
And these Gapps:
https://www.androidfilehost.com/?fid=673791459329049438
If it all not Work, you have to flash actually official Rom to restore all with edl.
I have the exact same problem. Cant flash any ROM without getting bootloop. The bootloop though isnt a standard one, i think. I get the logo of the ROM and the phone starts to give Tiny vibrations in regular periods of time. I also left the phone for a long time hoping it'll eventualy boot. No luck. Tried flashing stock ROM with miflashtool and edl. Didnt help as well. I wonder if it could be the fault of any previous roms i had installed.
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
SpeRator said:
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
Click to expand...
Click to collapse
Changed to writemode.. default options selected in the mounts screen.
unable to flash any Nougat roms- stuck in boot animation.
is it because the bootloader was unlocked unofficially via lollipop fastboot ROM 7.1.8??
All right, got it working.
I flashed the latest official MIUI ROM with the official flashing tool with the option "clear all". Then I had to open the bootloader again, then flash TWRP, then flash RR, and it works! Looks like something was wrong with the previous installation, the clearing everything did the job.
Were your bootloader unlocked officially?
aldhi said:
Were your bootloader unlocked officially?
Click to expand...
Click to collapse
Unlocked Unofficially via this method https://www.youtube.com/watch?v=2FmaCdnLi58
tonyrulez said:
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Click to expand...
Click to collapse
Backup all of your data from internal storage and flash latest fastboot developer ROM and setup it. This will fix all issues regarding ROMs, zips, bootloops and firmware and any other. After that flash latest ZCX recovery as RedWolf recovery causes problems for flashing ROMs and zips as per my experiance. Then simply flash RR and gapps and boot and wait for 15 minutes and till then don't restart device.
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?
Hey everybody,
I was on LOS 15.1 for a rather long time and I wanted to try RR, so as usual I backed up my system and tried to flash the RR-rom.
It did not work at all and I got several errors among which error 7 and the unability to mount system partition were the most prominent.
The device got bricked several times but I got it back to life with MiFlashTool, running either MIUI 8.5 or MIUI 9.
The strange thing is that even after flashing the MIUI-img - and basically bringing the device back to its factory firmware - I could not flash a rom.
I tried several recoverys; the latest TWRP, the TWRP linked in the LOS15.1 thread and OrangeFoxRecovery. None of them would work. I wiped all partition, nothing worked. I got different errors shown, most of them were error 7 or not being ablke to mount system, as stated before.
Right now I am back to MIUI and rooted it, which worked from OrangeFox, but I actually would like tzo run a custom rom again.
Any idea what I could do?
Cheers!
Noone who has an idea why it would not work?
I thought that after flashing via Flashtool the phone would be as good as new and all prioir changes would be gone? Wha can I not flash anything via recovery and get erros?
Or are there different versions of Orange Fox Recovery? RR would be treble, so I would need a treble recovery.
Cheers!
Have you tried to format internal storage?
If not backup data in sdcard or pc and format it using recovery.
Are you using trble supported recoveries?
Did you encrypted your data while using Lineage OS?
Hey,
well, yes, I encrypted data but since reinstalling MIUI via Flashtool this is gone. And I thought that this should be enough and reflashing it via MiFlash is like a factory reset? Is there anything I did not consider?
After Flashtool did not do the trick, wiped everything but External memory in TWRP, no kelp either.
I also did the normal wipe (where you dont have to choose which partition), this did not help.
As I said, I am currently on the latest OrangeFox Recovery but I also tried the latest TWRP and the TWRP in the LOS 15.1-Thread, which did not help.
To my knowledge all of the are treble recoverys?
I also tried to restore a vackup of LOS which did not work...
I flashed
wurst_wasser said:
Hey,
well, yes, I encrypted data but since reinstalling MIUI via Flashtool this is gone. And I thought that this should be enough and reflashing it via MiFlash is like a factory reset? Is there anything I did not consider?
After Flashtool did not do the trick, wiped everything but External memory in TWRP, no kelp either.
I also did the normal wipe (where you dont have to choose which partition), this did not help.
As I said, I am currently on the latest OrangeFox Recovery but I also tried the latest TWRP and the TWRP in the LOS 15.1-Thread, which did not help.
To my knowledge all of the are treble recoverys?
I also tried to restore a vackup of LOS which did not work...
I flashed
Click to expand...
Click to collapse
When you reply quote, I didn't get notifications for your reply.
Your bootloader is unlocked and you installed Twrp recovery.
Try copying Rom zip to SD card and wipe system, data, cache, dalviks cache, internal storage (exclude sd card off course). Then install it.
It should work
As I said, I did all of this, yet it does not work.
After wiping I tried to flash RR rom...
I get "Patching system image unconditionally...
Then I get E1001: Failed to update system image. (in white)
Updater process ended with: ERROR 7 (in red)
Error installing zip file 'patch...' (in red)
Updating partition details (in white)
Failed to mount '/system' (Invalid Argument) (in red).
As I said, that happens with different recoverys and different roms (treble and non treble)
wurst_wasser said:
As I said, I did all of this, yet it does not work.
After wiping I tried to flash RR rom...
I get "Patching system image unconditionally...
Then I get E1001: Failed to update system image. (in white)
Updater process ended with: ERROR 7 (in red)
Error installing zip file 'patch...' (in red)
Updating partition details (in white)
Failed to mount '/system' (Invalid Argument) (in red).
As I said, that happens with different recoverys and different roms (treble and non treble)
Click to expand...
Click to collapse
Are you sure the Rom you installating is for your device because error 7 occured if the rom you are trying install is not for your device.
Yes, of course, it was the correct ROM. Before error 7 I got error 1001 and I guess this was the initial problem.
My guess it that the problem was the decrypted partition which I did not format in twrp in my first go. Every wipe and format afterwards somehow did not help...
Now after having flashed recovery and different roms 10 times and using miflash 10 times it worked and now I am on RR. Don't ask me what eventually did the trick.
wurst_wasser said:
Yes, of course, it was the correct ROM. Before error 7 I got error 1001 and I guess this was the initial problem.
My guess it that the problem was the decrypted partition which I did not format in twrp in my first go. Every wipe and format afterwards somehow did not help...
Now after having flashed recovery and different roms 10 times and using miflash 10 times it worked and now I am on RR. Don't ask me what eventually did the trick.
Click to expand...
Click to collapse
Great to know
I hated MIUI because of the bloatware and ads. Have fun using RR. If you want you can use Liquid Remix Pie its a great ROM.
Yes. I also did not like MIUI that much, that's why I was using Lineage before I wanted to try RR: Thanks for the advice for anothe rom.
i fix this issue by format data, not only wipe then restart the recovery and install the ROM, then finally it works !
Shojimeguro said:
i fix this issue by format data, not only wipe then restart the recovery and install the ROM, then finally it works !
Click to expand...
Click to collapse
How did you format? noob
Shojimeguro said:
i fix this issue by format data, not only wipe then restart the recovery and install the ROM, then finally it works !
Click to expand...
Click to collapse
If I format data, then I have to reboot into the recovery menu to be able to use data again. But this is impossible, because it gets stuck into the bootloop every time I try to reboot. Any other option to fix this error?
EDIT:
I could fix it myself:
1. MIUI latest version; flash with MiFlash.
2. flash TWRP with e.g. YUware
3. flash latest fw_vendor in TWRP
4. full update pixel expierence (NOT incremental) rom flash
5. Partitions/Data/Format
6. Reboot and ready to use
Hej everyone,
I flashed a custom rom from mi-globe a few months. It was working great. Then I had the not so incredible idea of updating with latest miui eu 12, because the weekly update from the update menu was not working. It kinda worked, but it got too buggy. So I wanted to come back to a xiaomiEU Stable Rom.
It is now that problems begin. When I flashed miui eu 12, I got recovery loop. Lost all my data trying to fix, but I was able to flash the stock rom via the amazing XiaomiADBFastbootTools in my GNU/Linux distro. It worked! But the main issue is can not flash the custom rom again. I download the custom rom in the internal storage, flash the twrp via fastboot, enter recovery, create full backup, wipe to factory reset and flash the custom rom. Everything seems successful, but then I get a recovery loop again and when I try to restore the backup, the data folder is filled with folders and files with random chars in the names. Apparently the data folder becomes read-only for some reason as well. Then I have to flash the stock rom and tried everything again. I have done it at least 5 times now. I have searched a lot for some solution and nothing works
I have tried the OrangeFox recovery and the mi-globe rom, same issue. I really want a custom rom :fingers-crossed:, but I have no idea what to do anymore. If I could at least restore my backed up stock rom, it would help a lot.
Please help me out and sorry I posted in the wrong section.
Hello, i was using miui.eu 12.5.4 until yesterday. coz of lagging & hanging i thought to try a new custom rom. So, i did backup my "data & boot" partition in latest Ofox recovery before flash another rom.
Now, today i want to again go back to miui.eu rom. So, i flashed,
✓miui.eu 12.5.4
✓Then, Ofox zip (coz flashing miui.eu forced u to install twrp)
Then, reboot to Ofox,
✓Then flash magisk 23
✓Then, restore my previously backedup data
Then restart my phone.
But, it stuck with miui logo. Can anybody tell me, did i do anything wrong?
I did try same steps with back & forth. But, no luck..
update: it's the ofox recovery which have problems. i restored the same data with twrp & boila, its worked & my phone booted with my backed up data...
aamnahid said:
update: it's the ofox recovery which have problems. i restored the same data with twrp & boila, its worked & my phone booted with my backed up data...
Click to expand...
Click to collapse
Thanks for telling us. That is good to know.
But with which ofox did you try (beta or stable)?
And more important with which TWRP did you succeed?
Both were latest version..