Related
Hi,
I have a problem and hope you can help me. I did quite a bit of rooting and installing custom roms on other devices but this was my first try on a Huawei.
I wanted to install a custom rom. The phone was on Lollipop 5.0 (can't remember what firmware it was on). I installed TWRP, did a backup, looked up a rom online and got stuck on boot. So I restored my backup, did some more research and found out that it is possible to upgrade to Marshmallow with an official system update manually.
I then checked what firmware it was running: balongV100R001C50b311. I looked online for the stock recovery for that version, flashed it, then flashed a vendor upgrade to get away from the balong-version (was recommended in another forum in order to be able to upgrade to MM).
So now: I'm on Firmware version ALE-L21C432B564. The thing is, I'm still on Lollipop 5.0. As I understand it, B564 is a MM firmware. I flashed the recovery of B564 for manual updates (via Huawei update extractor), but I still can't do a local update (via dload) to B565 or B574. I tried to manually install the update to B564 again, hoping it would upgrade my Android version to MM, but no luck. It just gives me the error: 'Software install failed!'.
I couldn't find anything online about being on B564 and still running Lollipop. I hope some of you can help.
Thanks in advance
tostre said:
Hi,
I have a problem and hope you can help me. I did quite a bit of rooting and installing custom roms on other devices but this was my first try on a Huawei.
I wanted to install a custom rom. The phone was on Lollipop 5.0 (can't remember what firmware it was on). I installed TWRP, did a backup, looked up a rom online and got stuck on boot. So I restored my backup, did some more research and found out that it is possible to upgrade to Marshmallow with an official system update manually.
I then checked what firmware it was running: balongV100R001C50b311. I looked online for the stock recovery for that version, flashed it, then flashed a vendor upgrade to get away from the balong-version (was recommended in another forum in order to be able to upgrade to MM).
So now: I'm on Firmware version ALE-L21C432B564. The thing is, I'm still on Lollipop 5.0. As I understand it, B564 is a MM firmware. I flashed the recovery of B564 for manual updates (via Huawei update extractor), but I still can't do a local update (via dload) to B565 or B574. I tried to manually install the update to B564 again, hoping it would upgrade my Android version to MM, but no luck. It just gives me the error: 'Software install failed!'.
I couldn't find anything online about being on B564 and still running Lollipop. I hope some of you can help.
Thanks in advance
Click to expand...
Click to collapse
Why you don't just update it from the system updates, you know?
I have EMUI 3.1 too but I received an MM update right when I flashed it
XTutorials said:
Why you don't just update it from the system updates, you know?
I have EMUI 3.1 too but I received an MM update right when I flashed it
Click to expand...
Click to collapse
You mean Settings->Updater->Check for Updates? It tells me there are no updates. It did so even before I started fiddling with it
tostre said:
You mean Settings->Updater->Check for Updates? It tells me there are no updates. It did so even before I started fiddling with it
Click to expand...
Click to collapse
Reset on factory settings, maybe you it will find it? In what region you are?
XTutorials said:
Reset on factory settings, maybe you it will find it? In what region you are?
Click to expand...
Click to collapse
Factory reset doesn't change anything, unfortunately. Still on B564, Lollipop. The region is Europe.
One more thing that could be helpful: The device is unrooted
tostre said:
Factory reset doesn't change anything, unfortunately. Still on B564, Lollipop. The region is Europe.
One more thing that could be helpful: The device is unrooted
Click to expand...
Click to collapse
But you have TWRP. Download B596 update.zip (you will find a thread in "general" section), then restart to TWRP, go to wipe~advanced wipe~ tick Data, system, dalvik/art cache and cache (Be sure to have backup!) and click wipe. Then flash B596 update.zip that you have downloaded
XTutorials said:
But you have TWRP. Download B596 update.zip (you will find a thread in "general" section), then restart to TWRP, go to wipe~advanced wipe~ tick Data, system, dalvik/art cache and cache (Be sure to have backup!) and click wipe. Then flash B596 update.zip that you have downloaded
Click to expand...
Click to collapse
Hm, I read somewhere that flashing an update only works with the stock recovery. But I'll give it a try, thanks
XTutorials said:
But you have TWRP. Download B596 update.zip (you will find a thread in "general" section), then restart to TWRP, go to wipe~advanced wipe~ tick Data, system, dalvik/art cache and cache (Be sure to have backup!) and click wipe. Then flash B596 update.zip that you have downloaded
Click to expand...
Click to collapse
Well, I flashed it via TWRP. Even though it aborted at "Writing radio" or something like this and gave me an unknown error, it seems to have worked.
I'm now on B596, Android 6.0. This device is killing me Thank you very much for your help
tostre said:
Well, I flashed it via TWRP. Even though it aborted at "Writing radio" or something like this and gave me an unknown error, it seems to have worked.
I'm now on B596, Android 6.0. This device is killing me Thank you very much for your help
Click to expand...
Click to collapse
My pleasure
I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.
campeadore said:
I folowed this tutorial https://forum.xda-developers.com/nova-plus/development/rom-aospextended-v4-6-t3717372 and all flashing was fine. Due to some inconveniences of this new flashed rom i decided to restore to default rom. I extracted recovery and update.app version Can-L11 B396 i think from firmware finder and flased with adb this recovery. After that, it asked me to do an factory reset, i did it, but it wont boot any of huawei or Aosp Extended. The main problem i have is i can`t acces any more my phone with adb terminal, maybe after flashing the new original recovery usb debbuging reverted to un-enabled. How can I do now? Thanks in advance.
Click to expand...
Click to collapse
Check this post.
I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.
campeadore said:
I cant access my phone via adb or twrp recovery. I wonder why. Before flashing a stock recovery all Was fine, adb Was connecting with no problem.
Click to expand...
Click to collapse
Try to flash the TWRP again with fastboot.
PS: I don't understand how you people end up like this. It never happened to me.
I cant, adb cant be connected to device. Says null operation.
finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?
campeadore said:
finally i succeed to revert o stock rom. Now i have on About phone CAN-L11C432B397, Emui 5.0 and Android 7.0. One question please, I dont see anymore the Update system tab or something, "Actualizator" on romanian language. Is that normal? How i can check for updates?
Click to expand...
Click to collapse
You need to install the other zip too which has the word "data_full" at zip's name or something like that.
EDIT: @campeadore, i suggest you to edit the thread name and add "[SOLVED]" at begin and write the way you've fixed your phone (the solution), so it'll help other people who might run into the same problem as you.
I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.
campeadore said:
I`ll do it as soon i fully resolve the problem. I followed your link and everything went fine at step 1 (Go back to EMUI 4.1 (MM). System is booting, but system update is not working. So, i want to flash EMUI 5, but can-l11c432b330 or can-l11c432b396 cant be updated, around 45% gives an error. The only version who work is can-l11c432b320 but i dont have update_full_CAN-L11_hw_eu, only the first update.zip.
Click to expand...
Click to collapse
Newer / newest firmware downloaded from Firmware Finder needs to be approved by Huawei and that can take some time. It's failing to install because it wasn't approved. I've read this in past somewhere.
Try B381 or B382 as i've always installed that one when i've went back to EMUI 5.
Yes, i did it now with can-l11c432b330. I think my mistake was trying to flash to EMUI5 with usb cable connected. With cable off all went fine like a charm. Now i do all approved updates with system update. Thank you so much man, really appreciated.
Seeking help: I have a smartphone huawei nova lite plus (TRT LX1) that fails to restart. It goes continuously in a loop. Entering recovery only the first 2 functions come out: wipe wash factory reset and wipe wash partition. Then using eRecovery from PC with the USB cable, proceed up to a certain point and then not continue. I think it's in soft brick. I definitely need the right software for flashing, stock roms and usb drivers. Where can I find them? Many thanks
Hello,
I'm having big problems flashing any ROM on my Oneplus 5 atm.
At the beginning of this month, I wanted to unroot my rooted Android 8.0 or 8.1 (One of them, it was OxygenOS, but not the newest version)+ Xposed Oneplus 5.
I got a couple of errors, most of the time error 7.
After hours, old and new recoverys (TWRP) from blu_spark, codeworkx and some xda user recoverys and diffrent OxygenOS versions i finally managed it to install a Oxygen version with Android 7.1.1 on the phone. The Problem was: I always got errors (Installation failed) when I wanted to intall Software Updates no matter if I tryed it by myself or with the official system update in android.
So and today the official beta build of OxygenOS for 9.0 released and I was so stupid and thought I can make this an easy one.
Now I'm sitting here since 9:30am and try to flash Android 9, or any Android except 7.1.1 (only Oxygen Versions). Most of the Time i'm getting ERROR:7, it doesnt matter with which Recovery or Build.
When I got this problem at the first Time, my Phone was shown as "" (The error was something like: This Package is for a "Oneplus 5" this is a "").
When I get this scentence now (not every Recovery is showing it) it says my Phone is a "OnePlus5T", but i have a Oneplus 5.
Also (maybe partly) important things are:
- I tryed to edit the updater-script and delete the assets lines but there were no asset lines. Tryed it anyways and it didnt work. (and i really dont want to try this again)
I tryed to google this error for hours and many people meant that this is the way to go but I dont belive it. Isn't there any way to rename my phone, if yes: what do I have to do? I have TWRP and access to the command prompt aswell. If anyone can successfully create the 9.0 beta without the assets I would be happy but i dont think that is the solution for my problem, just a workaround.
- I think the problem is just something about my devices name. The strange part is that it accepted 7.1.1. And this was 100% a Oneplus 5 ROM.
- 7.1.1 isnt the way to go for me anymore. I dont like android 7 and it has so old security patches..
- Fingerprint sensor and screen got replaced
thank you for reading this and maybe helping me. I dont have the best language skills, if you need more Information about my Phone, please ask
EDIT1: As I said, 7.1.1 is still successfull, i tryed it a couple of mins ago. no error 7 or sth
maybe you can try revert to fully stock setup{without TWRP) and update to pie?
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
petryrety said:
I have problem with error 7 when i tried to flash latest open beta (pie). I didn't find any solution.... :crying:
Click to expand...
Click to collapse
Make sure the download isn't corrupt or if you extract the compatibility.zip use a recommended tool.
I had this problem couple of months ago. I solved it by flashing an old os version then flashing stock recovery(I don't remember if I locked the bootloader). boot in to the phone and download and update through ota( I did 3 updates this way). Then install twrp and root. Now I can flash any oos update without error 7.
May work
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
iwantademo123 said:
This is a post I wrote for another thread. I have found that this method fixes the error 7 issue, and allows you to update all the way to Pie without issues. When updating to Pie, use 7-Zip, not winrar or any other non-recommended programs to remove compatibility.zip from the firmware archive before flashing. I found that winrar causes treble errors or error 7.
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
Click to expand...
Click to collapse
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
strongst said:
Yeah, that's what I wrote here https://forum.xda-developers.com/oneplus-5/help/massive-problems-error7-t3878372/post78503983 and in flashing instructions for open beta and stable builds in their first posts.
Click to expand...
Click to collapse
That's good, It's good advice. I am just stressing to everyone in this thread, how important it is to follow that and use a recommended tool to remove compatibility.zip because removing compatibility.zip sounds very trivial thing, but it's actually really important to use a tool like 7-Zip that doesn't break the firmware in the process.
Also, the link to my other post ( https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13 ) should be detailed and comprehensive enough to help people with error 7 in other scenarios or that are trying to update to oreo or other stock firmwares too. This method restores the phone back to factory condition, including all the partitioning. Updating with a locked bootloader can fix a lot of update errors. I've found that after 5.1.5 it is safe to unlock the bootloader and take updates. But as you mentioned, for an unlocked bootloader, compatibility.zip needs to be removed from the firmware archive, and a tool such as 7-Zip must be used to do so as other archive managers break the update entirely (with error 7).
Good luck everyone trying to update, hope our advice helps :good:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
TurtleSandals said:
So I flashed OOS 5.0.1 then went back to stock recovery. I then locked my bootloader. After which I booted into OxygenOS and updated it all the way to pie(took 3 OTAs). Now I've got a locked bootloader and pie but I'm wondering if the process to unlock the bootloader is the same or different now that there is a vendor drive?
Click to expand...
Click to collapse
The unlocking process of the bootloader is the same!
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
mathgerm said:
I am having the exact same problem, tried everything from above. Can get anything more recent than 7.1.1 on my oneplus 5. evrything else is error 7. Any update
Click to expand...
Click to collapse
Please see here https://forum.xda-developers.com/on...xygenos-4-5-2-7-1-1-ota-t3627003/post79938097
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
mikekote666 said:
it seems youre trying to flash a new twrp image that is higher than the allowed 3.2.3-4 in the root process,go to fastboot mode reflash twrp image 3.2.3-4 or an older one.If that's not the issue please provide more information
Click to expand...
Click to collapse
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
mikekote666 said:
You should flash latest after installing this one by installing recovery img in TWRP i am telling you cause i have tried 3.2.3-5+ with the dirty santa process for my phone and thats the message i was getting unless downgrading to 3.2.3-4
Also decryption is unsuccessful comes as a result of not formatting data on twrp after the first install of twrp but you said that you did format data so i thought you were trying to flash newer twrp via the root process of the H918
Click to expand...
Click to collapse
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
you need to format data first time
noddledizzy said:
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258
and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption unsuccessful. I tried it with other stock based rom like a prerooted one but the result are still the same. I am never new to this problem and usually this get solved by going to twrp and wiping data(the one you have to type yes) but it did not solve this problem. Really need help badly.
Click to expand...
Click to collapse
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
noddledizzy said:
do you have 3.2.3-4? I couldn't find it anywhere unfortunately
edit:already solved it by using 3.2.3-0/1 from official twrp website. but the problem is that i get 0mb storage on internal storage on TWRP. I am not exactly new to this problem but even after flashing no verity op encryption zip. I still get it. sigh.
Click to expand...
Click to collapse
Format data
gandyprakoso said:
I have this problem too for a couple days a go,
but now it have been fixed.
Flash TWRP 3.2.3 via fastboot
Boot into TWRP
format data
reboot system
done
I think Its TWRP 3.3 bug or something that not decrypt perfectly..
---------- Post added at 01:53 PM ---------- Previous post was at 01:46 PM ----------
Format data
Click to expand...
Click to collapse
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
noddledizzy said:
I did format data so many times already that it nuked my twrp(just stopped booting into it all of a sudden, still unsure if that caused it though)
Click to expand...
Click to collapse
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L.. and since your TWRP has been nuked, youll have to reflash TWRP again yes? ?
Or, if youbdont want to downgrade TWRP, you can use AOSP based rom such as LOS15.1.. i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
gandyprakoso said:
Yes me too, and it almost make me crazy back in the days ?
the solution (at least for now) is downgrade TWRP it into v3.2.3-4. flash it via adb fastboot command, format data, then reboot. But sorry i dont have TWRP for H918, becoz im using F800L..
Or, you can use AOSP based rom such as LOS15.1.
i already tried that rom and it dont have problem with encrypt/decrypt thing like stock based rom.
Click to expand...
Click to collapse
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
noddledizzy said:
I am currently using v3.2.3.0/1 i couldnt find v3.2.3-4 anywhere.
I am using Resurrection Remix, everything was perfect until i stopped receiving sms once the phone goes deep sleep
Click to expand...
Click to collapse
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
gandyprakoso said:
Here it is, hope it helps..
TWRP: https://androidfilehost.com/?fid=11410932744536982445
H918 Prerooted Oreo 20g:
https://androidfilehost.com/?fid=11410932744536989567
H918 SIM Unlock:
https://androidfilehost.com/?fid=11410963190603886898
All credits goes to @Phoenix591
Click to expand...
Click to collapse
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
noddledizzy said:
Thank you so much, no wonder i wasn't able to find v3.2.3-4 because it's labeled as the release date. What does the sim unlock do? I mean, I can receive messages and stuff but just not get any once in awhile. Will this actually solve that?
Click to expand...
Click to collapse
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
gandyprakoso said:
Yes i knew that. My TWRP 3.2.3-4 IMG file is labeled with same date like that.
About sim unlock, Actually I dont know for sure because in f800l we dont seeing any sim problem at all.. but in my opinion just download it, in case you seeing problem with locked sim after flashing, it will be very useful..
anyway, i found a thread that discussing about h918 sim unlock thing
https://forum.xda-developers.com/v20/how-to/discussion-t-mobile-sim-unlock-t3821051
Click to expand...
Click to collapse
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
noddledizzy said:
Thanks, I will try going back to stock roms and will report back to you.
And I forgot to mention that I already got twrp fixed after it got nuked. Sadly, I don't think fastboot flashing works on h918 so I had to do lafsploit method to flash twrp again.
Click to expand...
Click to collapse
Ok then and happy flashing m8 ?
noddledizzy said:
Where does it exactly say that I cannot flash anything higher than 3.2.3-4. All it says is to download the latest twrp from https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Do you have a link to 3.2.3-4? It seems like 3.2.3-5 is the lowest twrp I could find in Phoenix591's android filehost https://androidfilehost.com/?w=files&flid=235271
edit: while waiting for responses, I went ahead and installed unofficial LOS15 then I was able to boot without any problem. It seem like this will only happen with stock/stock based roms.
Click to expand...
Click to collapse
Where? Right in the portion where it says Known Issues of the first link.
Downgrading TWRP to 3.2.3-4 will fix it. I had the same issue.
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
From TWRP thread:
Changed one last thing to try to fix stock Oreo decryption.
There were an upstream TWRP change that should fix the issue where formatting was still leaving /data encrypted as well (this was actually in the last build, but I didn't notice it then)
Click to expand...
Click to collapse
If you still have your non-Encryption-supporting TWRP as download mode, wipe data from there. For some reason which was documented in the TWRP thread, most versions of V20 TWRP doesn't remove the encryption flag even on a full wipe. I've gone through the pain several times, but here's roughly what I went through about a month ago. It's possible that using the latest TWRP may allow you to skip straight to step 8. As of this latest wipe, I'm finally at a point again where my phone works properly and TWRP can still see my data.
Basic process to hopefully have a working ongoing phone and TWRP:
1. Reboot to download-mode TWRP
2. Wipe dalvik/cache/data from the older download-mode TWRP
3. Factory reset with YES, still in older download-mode TWRP
4. Reboot to system; it should give you the new-system-setup past the Decryption unsuccessful screen on your wiped device
5. Setup without a Google account or fingerprint
6. Reboot back to recovery, not download TWRP; use download mode to get there if you need to
7. Flash the latest TWRP version from the thread (no older than October 25, 2019)
8. Reboot back to recovery
9. Wipe dalvik/cache/data
10. Reboot back to system
11. Setup as you like
12. Reboot back to recovery and make sure you can see your storage
If it gets a decryption error on latest TWRP at step 12 and you can't see data while in Recovery, try skipping adding a fingerprint during setup (run through steps 8-12, no fingerprint on 11) and see if that fixes it.
frohro said:
Thanks for the notes. Unfortunately this did not work for me. I ended up in this position after updating Magisk to 20.2, or trying to. My H918 went to being stuck in the fastboot mode. I was able to get to TWRP, and reinstalled H91820h.zip, but then faced with "Decryption unsuccessful" I downgraded TWRP to twrp-3.2.3-0, and deleted everything except the external microsd card, reinstalled H91820h.zip, but still stuck at the "Decryption unsuccessful". Are there other things I should try?
Thanks,
Rob
Click to expand...
Click to collapse
My solution turned out to be formatting /data. Wiping it was apparently not really wiping it clean. Formatting it got me back to a working phone, though I had to re-install everything.
Thanks everyone for the help!
Rob
anyone knows how to fix fingerprints not working? h990 oreo rom mk2000 kernel is there any fix?
do i need to return to nougat but than what? please help
edit: was able to fix that by flashing nougat modem
now wifi wont turn on tho anyone know how to fix?
Hi,
I bought a oneplus 5 phone because I was told it was going to be easy to install Lineage OS. I have try to install Lineage OS 16 on it for 2 days without success.
The first issue i had was installing twrp. Most of the twrp available did not worked with my phone. After flashing them with fastboot and reboot to recovery I would end up with a black screen and the the blue led turn on.
However I did find two TWPRs that work:
- twrp-3.2.1-1-cheeseburger.img
- twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
There might be other that would work, but this are the ones that I have tested.
After being able to boot to TWRP I try to flash the firmware 9.06 with success. Without reboot I flash lineage without success. I try to reboot and the system did not worked and I never reboot.
After a while I found a OxygenOS 4.5.10 that I hope is the stock rom. I has the following sha256sum: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
That did worked and give me a breath. At least I had a working phone now. However I try to update and it did not worked.
From there I have been strugling with this project to install Lineage OS in my new phone. I know there are guides out there, but most of them did not work or are outated. There ara also threads in this forums, but are to big to try to follow. So I start this one, hopefully you can help me.
It would be great if there is a step by step guide on how to run Lineage OS in this phone.
Best,
Panoramix Druida
panoramix.druida said:
Hi,
I bought a oneplus 5 phone because I was told it was going to be easy to install Lineage OS. I have try to install Lineage OS 16 on it for 2 days without success.
The first issue i had was installing twrp. Most of the twrp available did not worked with my phone. After flashing them with fastboot and reboot to recovery I would end up with a black screen and the the blue led turn on.
However I did find two TWPRs that work:
- twrp-3.2.1-1-cheeseburger.img
- twrp-3.2.3-0-20180822-codeworkx-cheeseburger.img
There might be other that would work, but this are the ones that I have tested.
After being able to boot to TWRP I try to flash the firmware 9.06 with success. Without reboot I flash lineage without success. I try to reboot and the system did not worked and I never reboot.
After a while I found a OxygenOS 4.5.10 that I hope is the stock rom. I has the following sha256sum: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
That did worked and give me a breath. At least I had a working phone now. However I try to update and it did not worked.
From there I have been strugling with this project to install Lineage OS in my new phone. I know there are guides out there, but most of them did not work or are outated. There ara also threads in this forums, but are to big to try to follow. So I start this one, hopefully you can help me.
It would be great if there is a step by step guide on how to run Lineage OS in this phone.
Best,
Panoramix Druida
Click to expand...
Click to collapse
Hello, seems that you did not follow the installation instructions within the official LineageOS thread https://forum.xda-developers.com/oneplus-5/development/rom-lineageos-16-0-pie-oneplus-5-t3843064
Your issues are clearly missed or skipped steps.
Please follow the instructions there and if you get stuck, report back with detailed information :good:
Thanks a lot for your quick response. It do have an issue with that guide and it is with point 1:crying::crying:
- Make sure your phone was running OxygenOS 5.1.4 at least once
Click to expand...
Click to collapse
I have OxygenOS 4.5.10 and it does not upgrade to OxygenOS 5.1.4. What happened, is that in my first attempts to get this thing working I brick the phone and loose the stock firmware. Then I found this rom that allow me to use the phone (OxygenOS 5.1.4)
OnePlus5Oxygen_23_OTA_015_all_1708252353_f05918.zip
sha256: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
It make the phone usable, but not upgradable. I doubt is the original, but I found the link on the Oneplus forums. (I can not post links because I am too new here)
After that I search for a ROM that comes with 5.1.4 and was really happy, and try to flash. It did not work, it is like it tries to boot, but never finish booting. I wait at least for 10 minutes. This the file and the sha256 hash:
OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip
sha256 2bb2e21a43572ac4bd2e5d1d30a3fb7562ddec280df3d452d61f58a4a8135f14
So I guess my first step would to find a way to get Oneplus 5.1.4 working. When I first try to upgrade the phone, I upgrade it from OxygenOS and it worked, however then I mess things and brick the phone. I found the rom that allow the phone to work (4.5.10), but for some reason the upgrades do not.
Thank you very much for your time.
panoramix.druida said:
Thanks a lot for your quick response. It do have an issue with that guide and it is with point 1:crying::crying:
I have OxygenOS 4.5.10 and it does not upgrade to OxygenOS 5.1.4. What happened, is that in my first attempts to get this thing working I brick the phone and loose the stock firmware. Then I found this rom that allow me to use the phone (OxygenOS 5.1.4)
OnePlus5Oxygen_23_OTA_015_all_1708252353_f05918.zip
sha256: 7a8268f6a133f090a2d304aad2f92393aefbd4df34a6c2ed088909aaf7ccc2dd
It make the phone usable, but not upgradable. I doubt is the original, but I found the link on the Oneplus forums. (I can not post links because I am too new here)
After that I search for a ROM that comes with 5.1.4 and was really happy, and try to flash. It did not work, it is like it tries to boot, but never finish booting. I wait at least for 10 minutes. This the file and the sha256 hash:
OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip
sha256 2bb2e21a43572ac4bd2e5d1d30a3fb7562ddec280df3d452d61f58a4a8135f14
So I guess my first step would to find a way to get Oneplus 5.1.4 working. When I first try to upgrade the phone, I upgrade it from OxygenOS and it worked, however then I mess things and brick the phone. I found the rom that allow the phone to work (4.5.10), but for some reason the upgrades do not.
Thank you very much for your time.
Click to expand...
Click to collapse
You need to clean flash oxygenOS 5.1.4, then take ota update to 9.0.7 so you have the latest firmware.
Clean flash means that you need to wipe system, data, cache and format internal storage too.
So please backup everything off your device at first!
Everything you need you find here on xda, like the roms https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
strongst said:
You need to clean flash oxygenOS 5.1.4, then take ota update to 9.0.7 so you have the latest firmware.
Clean flash means that you need to wipe system, data, cache and format internal storage too.
So please backup everything off your device at first!
Everything you need you find here on xda, like the roms https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Thanks, I would try this when I have time later today.
strongst said:
You need to clean flash oxygenOS 5.1.4, then take ota update to 9.0.7 so you have the latest firmware.
Clean flash means that you need to wipe system, data, cache and format internal storage too.
So please backup everything off your device at first!
Everything you need you find here on xda, like the roms https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
Click to expand...
Click to collapse
Finally I had time to work on this. The rom for 5.1.4 is: OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip, that I already tried and never boots . With twrp it seems that the Rom is installed, with the stock recovery the installation never ends. I am going to try with other ROMS. Hopefully one of them would allow updates.
I am going to start with the newest 5.1.7, and if that does not work would keep going down.
Thanks again.
panoramix.druida said:
Finally I had time to work on this. The rom for 5.1.4 is: OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip, that I already tried and never boots . With twrp it seems that the Rom is installed, with the stock recovery the installation never ends. I am going to try with other ROMS. Hopefully one of them would allow updates.
I am going to start with the newest 5.1.7, and if that does not work would keep going down.
Thanks again.
Click to expand...
Click to collapse
5.1.7 did not boot, however I have some progress. I installed 4.5.12, I was previously at 4.5.10, so my android setup security patch levels went from July 2017 to to September 2017. Small step forward.
I have have that hypothesis that it would work with 4.x.x versions and not with 5.x.x versions. Tomorrow I would try to flash the latest 4.x.x and the earliest 5.x.x to see when does this things stop working.
I did the tests and I can flash up to 4.5.15. I tried to flash 5.0 and that did not worked. It flashes correctly, but it never finish booting, I waited up to 10 minutes.
So there is something preventing the phone to use version 5.x.x Should I try upgrading the firmware? Other ideas?
panoramix.druida said:
I did the tests and I can flash up to 4.5.15. I tried to flash 5.0 and that did not worked. It flashes correctly, but it never finish booting, I waited up to 10 minutes.
So there is something preventing the phone to use version 5.x.x Should I try upgrading the firmware? Other ideas?
Click to expand...
Click to collapse
Please give detailed steps what you did including file versions. Otherwise I cannot help further.
Every oxygenOS version has firmware built in, no need to update it seperately.
Follow this:
1 flash this recovery with fastboot like the first time https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
2 boot the new twrp recovery
3 flash magisk 18.1 to make twrp stick
4 FORMAT internal storage(not wipe only) and wipe system and data partition
5 transfer oxygenOS 5.1.4 to the phone and flash it
6 boot oxygenOS 5.1.4 and take ota update to tg and latest OxygenOS(9.0.7 actually.
7 now you're on the latest OxygenOS and firmware version
Thank you very much, now I am with LineageOS