Hi Guys,
I'm hoping the community can provide some advice.
I have an LG G5 H850 and with an unlocked bootloader. After trying fulmics rom temporarily to look at improvements, I wanted to try the latest Resurrection Remix, however, after wiping data, system cache etc and formatting data in TWRP the installation 'failed'. I have put failed in inverted commas because the installation says it has been successful but the phone boots straight back into TWRP and the is clearly no OS on the device when I open file manager. This is the same when I attempt to install any OS (Prime's 10E, Lineage, Fulmics again) none of them take.
Does anybody know what might have happened or what I can do to fix it? I do have access to download mode still.
Thanks in advance,
Chris
unsrm said:
Hi Guys,
I'm hoping the community can provide some advice.
I have an LG G5 H850 and with an unlocked bootloader. After trying fulmics rom temporarily to look at improvements, I wanted to try the latest Resurrection Remix, however, after wiping data, system cache etc and formatting data in TWRP the installation 'failed'. I have put failed in inverted commas because the installation says it has been successful but the phone boots straight back into TWRP and the is clearly no OS on the device when I open file manager. This is the same when I attempt to install any OS (Prime's 10E, Lineage, Fulmics again) none of them take.
Does anybody know what might have happened or what I can do to fix it? I do have access to download mode still.
Thanks in advance,
Chris
Click to expand...
Click to collapse
Search XDA LG G5 boots into TWRP there are several threads that cover causes and solutions.
I wouldnt hurt to format some of your partitions especially DATA as it can get encrypted automatically depending on the rom, although ive used fulmics and it has never encrypted my data partition (RR did though!).
Related
I try to install Lineage 14.1 but I can't because It says wrong bootloader, and that my bootloader is unknown. I installed lollipop by flashing the system.img image and the boot.img image because I had no ROM installed because my internal storage and SD card got corrupt or something. Can anyone help me by supplying a Lineage 14.1 backup or a LineageOS system.img and boot.img file? Thanks in advance...
Wrong bootloader . . .?????
I think the issue you are having is what I was having, and that is that you are not COMPLETELY wiping the previous operating system. Use TWRP's advanced features to make sure you do a complete wipe.
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Billc47 said:
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Click to expand...
Click to collapse
I was getting the same error the user above was until I used TWRP's advanced wipe and got rid of everything. Of course make sure you do a backup of whatever you currently have working just in case, but once I did an advance wipe I was able to installed Cyanogen. I however still cannot get Lineage 14.1 to work, it simply gets into an install loop. But since your question was about the boot loader, once I did the complete wipe the error message you are referring to went away for me.
thank you for your reply
hi i am from india and huge fan of huawei i got this phone from usa(mt2-l03) i rooted the phone using some one click root tool and tried to flash twrp which ended in saying recovery image failed,please update to the authorized images.however as there was was root i changed the dpi(think 420) now the phone screen is blank(only in the system ui not the boot image or vendor image(huawei)) i am having the imei and s/n at the battery but i dont have the product id so is there any way i can get the product id and unlock the bootloader of my phone or is there any way to repair my phone
In the general area, in the stickies there are many options you might try. This one https://forum.xda-developers.com/as...to-fix-soft-bricked-phone-using-twrp-t2886630. Seems like it might be the way out for you but I'm not a dev or an expert, just someone who's screwed up his phone alot and found fixes in that section
Sent from my MT2L03 using XDA-Developers Legacy app
I got Resurrection Remix 7.1 (official 3/15) installed and working and I have never run a custom ROM before on any phone, but I must say WOW. This work(ed) so beautifully. Very responsive and clean interface and the battery life was looking phenomenal. It was basically everything I could have wanted and then some.
Now the bad news. I was trying to run a file manager that seemed to lack root access and I clicked on SuperSu which said it needed to update, I chose "update normally" instead of via TWRP. It ran and said it succeeded but needed a reboot. Now I am in the "Get Resurrected" bootloop and I don't know if there is any way to recover at this point. I can obviously get back into TWRP and I tried wiping and re-flashing 35B bootstack and RR ROM zips. No luck.
Before this ROM I was thinking seriously of upgrading from G3 to something newer but after seeing how well this runs on the G3 hardware I don't see any reason to upgrade given how well this run, though I only had it up to test for 4-5 hours.
Any help would be appreciated. I did find another post on CM13 in bootloop from SuperSu install/update and flashing a 'make permissive selinux' fix which worked for this situation. I am wondering if it may work for RR bootloop as well? Again any help would be appreciated.
Big thanks to Rohlm who suggest system format before re-installing!
I went into the Wipe options in TWRP and selected the format data and then went through the install steps again. Data, cache, Dahlvik wipe, 35B bootstack flash, RR 7.1 flash, gapps 7.1 arm flash and I'm now "Re-Resurrected!" And I checked still have root access!
Cheers,
-Scott
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?
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
kishikaisei said:
Hey all, so it appears that I screwed my phone, I am not sure how.
I was running LineageOS, and wanted to update to Android 10 one, so I followed the steps, and I think I screwed the sideloading part, so... long story short now when rebooting from OrangeFox RecoveryProject it says no OS detected, and when it boots it says encryption unsuccessful, I tried wiping and installing DisableForceEncryption_Treble_v17.2 and restarting, and the same thing happens.
I tried to flash through recovery both, and did not work:
https://xiaomifirmwareupdater.com/firmware/beryllium/
https://xiaomifirmwareupdater.com/archive/vendor/beryllium/
And when trying to flash through miFlash it doesn't work:
I go to fastboot in poco, hit refresh in miflash, it shows a device in the list, but the phone goes dark with 'something key to shutdown` written in the top left corner and if I hit the flash button nothing happens.
Can anyone assist with that please?
Click to expand...
Click to collapse
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
mecoromeo said:
This happened to me when I accidentally deleted the OS when flashing the latest MIUI 11 build (using TWRP). THIS IS HOW I FIXED IT.
Find a full firmware of whatever you wanted to flash, either Lineage or MIUI 11. Then flash via your recovery (you said you have orangefox). Use an external sd card, external USB or HDD since you technically wouldn't have access to your internal data. After flashing, same process as most updates, clear cache and dalkiv. Then flash a newer DFE (if you still want to decrypt, there is a page here in xda with it. Or go to miui forums Happybuddhist, the mod there, made a new one prebuilt with Magisk). Then reboot into recovery to make sure you keep your custom recovery. Once booted to recov. Boot to system. Should fix the issue.
Click to expand...
Click to collapse
I tried that, now I am a step forward I think, I flashed the stock firmware I found, and installed the latest stock ROM, rebooted (doesn't say no os anymore), but the only thing I see is a DELETE ALL DATA button and at the bottom 'Encryption was interrupted and can't be completed. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google account.'
Darklouis said:
You could check my guide here on how to unbrick your pocophone:
https://forum.xda-developers.com/poco-f1/how-to/unbrick-flashing-stable-rom-pocophone-t3901152
Click to expand...
Click to collapse
I have an issue with the MiFlash part, it seems that it doesn't work as I mentioned...
Aight all, formatting data partition to ext4 worked, now it is booting
kishikaisei said:
Aight all, formatting data partition to ext4 worked, now it is booting
Click to expand...
Click to collapse
Works now?
mecoromeo said:
Works now?
Click to expand...
Click to collapse
So I had an OS-less phone that don't get recognised in MiFlash, and I had orangeFox recovery.
The steps to fix were:
- Flash a full stock Firmware
- Flash the stock ROM
- Flash DFE
- Format data to ext4
- Reboot and it works
So thanks all for your help