H918 Stuck on secure startup "decryption unsuccessful" on boot - LG V20 Questions & Answers

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?

Related

TWRP prevents Marshmallow?

I may be doing something stupid, but I've tried various options...
I had an original 5.1.1 build that I let OTA to 6.0. Everything was working fine. I wanted to root, so I installed TWRP... and then the machine wouldn't reboot; it stuck at the "powered by Android" screen and never went into the standard animation screens. I could reboot into TWRP recovery easily enough and using that I could see the filesystem data, but the OS wouldn't boot.
So I reflashed back to 5.1.1 (using http://www.andromods.com/download-files/xt1575-stock-firmware-moto-x-2015-pure-edition.html ), let that OTA to 6.0, installed TWRP... same result.
Third attempt; started at 5.1.1 then installed TWRP (which worked) and then did OTA to 6.0... but this went into a reboot loop.
(Of course during all this I've lost my configs, but I can rebuild that)
Has anyone been able to install TWRP onto an X-Pure 2015 that's running 6.0 ?
What TWRP version are you installing? Make sure it's 2.8.7.1 https://dl.twrp.me/clark/
Sent from my XT1575 using Tapatalk
Sorry, yes, I should have mentioned that; twrp-2.8.7.1-clark.img
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread:
"I keep running into a problem after doing the MM update when I flash TWRP (either 2.8.7.0 or 2.8.7.1) where it won't boot into system, just sits there where the animation part should start. Booted/rebooted fine a few times after finishing the MM update, even after flashing the unlocked bootloader logo fix, but as soon as I flash recovery it won't boot system. "
Tried it several times with both TWRP 2.8.7.0 and 2.8.7.1 with no success. Also tried sideloading the OTA per the manual steps in this thread but still couldn't boot to system. Only by already having TWRP installed on 5.1.1 am I able to flash a custom 6.0 ROM successfully. Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
EVR_PR said:
Did you install TWRP as read only? I did this and now system recovery is overwriting TWRP and I have no idea how to get out of it.
Click to expand...
Click to collapse
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Dahenjo said:
I had the same problem a couple days ago and posted about it in the 'Android 6.0 Update rolling out! Pure Edition' thread
...
Haven't seen a really clear statement yet that someone has flashed TWRP on fully stock MM with no problem..
Click to expand...
Click to collapse
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
sweh said:
First time I let /system be read-write and second time I let /system be RO. However this likely isn't related to recovery overwriting TWRP; it's documented that on first boot the OS may rewrite the recovery data meaning you'd need to install TWRP again.
Click to expand...
Click to collapse
I have flashed TWRP twice and even rebooted to recovery from recovery and system recovery still overwrites TWRP after booting to system.
Only way I can access TWRP is either flashing it or booting into from the fastboot folder using the fastboot boot command.
Doesn't matter what I do, the option for changing TWRP from read-write to read only doesn't show up anymore.
sweh said:
Thanks; at least I know it's not me being stupid then (or if I am, then I'm not alone ).
Click to expand...
Click to collapse
Well, at age 65 I do put my socks on backwards sometimes..... :silly:
Read on a fairly-detailed post that using adb to flash recovery and rebooting into it should actually work fine!
Could anyone confirm? Is it even possible?
P.S. I'm on XT1572 Indian stock 6.0, and very eager for twrp
I had the exact same problem. I used adb. Stuck on loading screen and then suddenly black. Not able to boot the phone. I'd like to make a nandroid and after that I'd like to use systemless root. If I'm correct, I'll still receive ota's while using systemless root.
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
BooBzi said:
Same for me. Returned to stock EU 5.1.1, got update, installed it. Later unlocked bootloader and installed latest TWRP. And now I am stuck on booting up image.
So stock Marshmallow cant be used with TWRP?
Click to expand...
Click to collapse
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
Thanks for reply, I did listen to you and post on TWRP thread.
Dahenjo said:
That seems to be the case since I have yet to hear of anyone freshly setting up TWRP for clark/MXPE on purely stock MM without it failing to boot to system afterwards. If you already have TWRP on 5.1.1 you can install a custom MM ROM and then TWRP works normally (ie boots to system), but so far that's the only way I'm aware of to get it functional on MM.
I see you started another thread on this, which may help it get noticed, but maybe also post in the TWRP thread. I posted there on this issue over a week ago but have had zero response from OP, but if others keep doing so maybe that will help.
IMVHO, TWRP for MXPE isn't being supported well - this problem, the version being incorrect for several weeks causing confusion w/dozens of unnecessary posts (this alone could likely be fixed in 2 minutes), as well as the 'SD as internal storage' issue(s) which may be more involved but are still the type of thing those maintaining it are supposed to address. Even some acknowledgement that the issues are recognized and being worked on would be nice, but thus far not even that.
Click to expand...
Click to collapse
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Hello, is it possible to get step by step tutorial?
Later will try on Style with stock MM.
Thanks!
ccic2491 said:
I was on pure stock mm and sideloaded twrp without any issues. I use the twrp app (requires root) to reboot into recovery without any problems.
Click to expand...
Click to collapse
Did you not use the Fastboot Install Method on the TWRP site? We are unable to reboot back into system after using this on stock MM, which always worked fine on stock LP. If you used a different method that worked could you please share what that was?
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
gulshanstrider said:
I am using twrp 2.8.7.1 on my Moto X Style XT1572 Asia retail without any trouble for past two weeks.
I normally flashed it using the fastboot and never ran into trouble.
Click to expand...
Click to collapse
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Dahenjo said:
Just to confirm - when you flashed TWRP you were completely stock after installing the 6.0 OTA (not still on 5.1.1 before taking the OTA), correct?
Click to expand...
Click to collapse
Here is what I did:-
1) I was in Stock 5.1.1 (had unlocked bootloader)
2) I took the OTA.
3) Flashed the twrp 2.8.7.1 using fastboot
So yes I was completely stock 6.0 when I flashed the TWRP for MM

Having problem rooting my Axon 7 A2017U

Hey guys, first of all sorry about my english, im french.
So my problem is: I tried rooting my Axon 7 A2017U many times, with different guides. I always end up with a softbricked phone, having to restore to stock using MiFlash.
My bootloader is unlocked, i have stock recovery and stock rom for now.
Whenever i flash TWRP, either the signed one (from @tenfar) or unsigned (and up to date) ones, i can't go past the menu saying something like "your phone cant be checked for corruption, please lock your phone [...]" it just freeze. i did read somewhere that i should flash chainfire's root or a special .zip that, i guess, disabled some check that could prevent booting a phone with unsigned stuff/edited system (after flashing TWRP, so it could boot) that didn't work out. i think i found that information in some LineageOS thread here on XDA.
My ultimate goal would be to get a rooted stock nougat 7.1.1, up to date TWRP recovery and to be able to switch to LineageOS to try it out soon.
For what it is worth, i rooted many phones over the years, so while i'm no expert, i should be able to follow most of the steps you give me.
Thanks alot!
What version of TWRP did you flash first?
I have the same root problem i can not install in twrp install in twrp ok but su application displays no root cause i have latest twrp
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
KwesiJnr said:
What version of TWRP did you flash first?
Click to expand...
Click to collapse
this
https://forum.xda-developers.com/axon-7/development/recovery-official-twrp-zte-axon-7-t3515715
And @tenfar's signed one
Okay. Download and flash this one alone via fastboot and see what happens. This is one the I personally use. It is required for any of the newer versions to work properly.
twrp-3.0.2-2-a2017u.img
You can choose to rename it to just recovery.img, then:
1. fastboot flash recovery recovery.img
or
2.
if you choose to work with the same filename:
fastboot flash recovery twrp-3.0.2-2-a2017u.img
Select reboot to recovery from the bootloader menu now and try again.
Either way, should work fine. I know you mentioned you knew the basics, but just want to be sure.
Also forgot to mention. If TWRP works but you still can't get your phone to boot, you need to follow this guide here
You can start from the part that says:
-----------------------------------------------------
UPDATING FROM B20_Boot / B20 / B27 / B29 / B15(N)
-----------------------------------------------------
Again, that's the ROM I personally use if I want to go back to stock, not the one from the ZTE site.
Gonna try it and give feedback. thanks for taking time to help!
edit: im downloading the rom from the link you shared.
like you said, i can get TWRP to boot but not the phone.
So if i use full stock from ZTE, it can't boot with modified recovery?
edit 2: i don't know what worked, i think it might be the bootstack. or the rom by DrakenFX. now i can boot to the rom with a TWRP recovery installed. It worked, but i soft bricked again trying to flash SuperSU. So now i'm retrying with an updated TWRP.
I haven't tried that yet, but I really suspect that's the reason you're having problems. I rarely use pure stock ROMs. Like you, I'm not an expert in Android Development so I can't tell you why. Just been a flashaholic for years so made a few observations.
Which supersu are you installing? If you're swiping to the right in twrp, you need to install the dm-verity zip or supersu 2.79. There's some issues with newer builds.
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable
Click to expand...
Click to collapse
Glad you're up and running root. :good:
lololo2 said:
Everything is working like a charm! Now im going to finally give lineageOS a try
I used Chainfire's SuperSU 2.79 stable.
Edit : Everything is working flawlessly! I'm running the lastest LineageOS nightly with root (Chainfire's 2.79). Followed their instruction and installation was smooth as butter. I should also point out i flashed the lastest official TWRP which seems more stable than the one @KwesiJnr suggested. The one he suggested was giving me some "can't read X partition" in red text everywhere in the log section, which the official one doesn't do. It was doing his job properly anyway though.
I can't thank @KwesiJnr enough, it helped me find the single mistake i was making.
Click to expand...
Click to collapse
Yeah, like I mentioned before that was the base TWRP you needed to flash first, before any of the newer ones. You weren't intended to use it indefinitely.
There's a lot of Dev love for our device now and support is growing ... exciting new ROMs cropping up. Don't hesitate to try them out.

Help with soft brick

Hi guys,
I got the ASUS Zenfone 3 Zoom and started playing with it. Unfortunately I managed to soft brick it and somehow I can't go back to stock. Here are all the things I did. I would be happy to get any ideas what to try next:
1. unlocked the bootloader - using asus's official unlock tool
2. flashed twrp recovery - twrp-3.2.1-0-Z01H-20180304.img, using:
adb reboot bootloader
fastboot flash recovery twrp.img
3. updated asus's firmware to the latest official one:
copying UL-Z01H-WW-71.60.139.30.zip onto internal memory
android detects the update and applying it using android
4. Enabling lock pattern at boot (from android settings). Correct pattern required even when booting into recovery
5. Installing supersu via twrp:
adb reboot recovery
installing supersu
wiping caches (the cache partition cannot be wiped)
6. SuperSu working (tested via android)
7. Reading about Magisk. Trying to install magisk via twrp. Magisk's installer complained that the system is not vanilla (due to SuperSu modifications). Have to uninstall SuperSu to return to previous state.
8. Tried uninstalling SuperSu from the program itself (in android). The uninstaller got stuck. The phone become unresponsive and had to reboot.
9. Found a script packaged as an executable zip (to be installed via twrp) that will uninstall SuperSu and return system to pristine state (SuperSu makes a backup of the files it changes before installation) - UPDATE-unSU-signed.zip. Uninstallation worked.
10. Magisk installation still complained about the bootloader. Then things started to go wrong. I unpacked the latest firware UL-Z01H-WW-71.60.139.30.zip, took out boot.img and tried to flash just the bootloader
fastboot flash boot boot.img
11. Upon reboot the phone got stuck at the ASUS logo. Reboot into recovery and into fastboot still works (soft brick). Still shows unlock pattern at boot.
12. I tried flashing the original firmware using TWRP (install a zip). However the installation threw some errors. Unsuccessful.
13. I've tried flashing the system.img from the original firware using fastboot but still it's stuck at the ASUS logo at boot.
fastboot flash system system.img
Here I am stuck. I've read that TWRP cannot install properly the ASUS official firmware but if you flash the original recovery, it can probably flash it properly. Another thing that I think might explain why I cannot get out of the soft brick is that I've enabled the lock pattern at boot, which effectively encrypted some parts of the phone and I have a strong feeling this interferes with the boot process. I will look for a script/installable zip (via twrp) that can remove the lock.
I really need ideas/suggestions before I make something that will turn my phone into a hard brick. Thanks.
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Thanks
+)KEV1N(+ said:
What you need to do is flash stock MM recovery from bootloader using "fastboot flash recovery recovery.img"
Since it came with MM preloaded you'll have to install the ROM using stock recovery via adb. It'll take a while, but after that you should upgrade to the latest MM update.
After that, update to any Nougat patch update you wish to receive, because I still haven't figured out yet how to apply them all with @shakalaca's recovery images.
Once you're done, you can install twrp again and flash magisk.
Good luck and hope this helped you
Click to expand...
Click to collapse
Thanks,
I tried to find a stock recovery images but unsuccessful. Can you tell me where to get it from?
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
-- [link] removed due to XDA regulations
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
mollonado said:
Sorry I misread your comment. I'm updating to the latest ROM and installing TWRP. Thanks for the help.
Click to expand...
Click to collapse
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
mollonado said:
Thanks, I managed to flash 11.40.86.75 and stock ROM using your instructions. I will look now into updating and applying magisk. Just a final question. You mentioned to install Nougat patch update and not a full firmware, but my phone came preloaded with Nougat. Will this be a problem? I installed stock 71.60.139.30 and it worked fine (i was able to boot into twrp).
Click to expand...
Click to collapse
It came preloaded with Nougat? Interesting.
+)KEV1N(+ said:
Glad to help!
---------- Post added at 01:33 PM ---------- Previous post was at 01:30 PM ----------
It came preloaded with Nougat? Interesting.
Click to expand...
Click to collapse
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
mollonado said:
Hi I managed to flash stock ROM - 71.60.139.30, but after that I can't flash twrp - twrp-3.2.1-0-Z01H-20180304.img. I tried with:
adb reboot bootloader
fastboot flash recovery twrp.img
but when I try to boot into recovery with:
adb reboot recovery
it goes into the stock recovery. Is there something I missed? Do I need to downgrade to flash TWRP?
Click to expand...
Click to collapse
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
+)KEV1N(+ said:
Quick question: which of these warnings do you get when you boot?
https://www.androidauthority.com/go...rrupted-and-modified-android-software-629180/
Also, did you try power cycling to get it to boot?
And since the version number made such a large jump, I believe they must have changed something internally with the latest update and that it's probably going to be one of the last Nougat updates before Oreo (which was delayed until June).
I still need to update to that version to check it out, but I might reset soon since I was waiting for Oreo to reset.
Click to expand...
Click to collapse
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
mollonado said:
I have the Orange warning. It looks a bit different but the wording is the same. Yes, i tried powercycling and still I boot into the stock recovery. What can I do now? Is it possible to downgrade? I am not sure if I boot into stock recovery if it will let me flash an older stock ROM.
Click to expand...
Click to collapse
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
mollonado said:
I read here - https://android.gadgethacks.com/how-to/twrp-101-install-best-custom-recovery-for-android-0179547/
that once you flash twrp Android upon next reboot might overwrite it with the stock recovery. Is that possible?
Click to expand...
Click to collapse
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
+)KEV1N(+ said:
So, how did you flash TWRP exactly? Using that guide? Or flashed through bootloader?
And to answer your question: yes, it happens sometimes.
Click to expand...
Click to collapse
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
mollonado said:
Hi, I managed to get around it by directly booting into TWRP from fastboot. Yes, apparently unless I flash some TWRP files to the system partition upon next reboot, the recovery will return to stock. Anyway, I managed to install Magisk and Exposed framework and have been poking with those two for the last couple of days.
The youtube vanced app is great, but I found something that worries me. I can't login to facebook/twitter. I checked and the reason is I can't connect to the facebook.com or twitter.com https sites (even over chrome). I think either:
- I've installed some module which is messing with that
- my rooted phone is hacked
I've installed a module that is meant as ad blocker, that updates the hosts file. However I removed all modules and the problem remains. I really don't wanna start all over again just to check. And even if I reflash and it works, I will not know what caused it and how to fix it myself next time. Do you have any ideas on how to figure out what the problem is?
Regards,
Click to expand...
Click to collapse
First off, my apologies for this late reply (Been superbusy with school and internship assignments)
Secondly, and that is why I only use magisk. Because once you mess with the host file, depending on what module you install, it can range from tripping safetynet to bootlooping.
So quick question, is it still in this state right now since 9 days ago?
Greetings,
Kevin
+)KEV1N(+ said:
Here's a link to Shakalaca's recovery images.
In the Old folder you'll find MM stock recoveries.
https://mega.nz/#F!p90wgAaY!l1JbJilmAUEKTKWu43pT9w!I89QgZpK
Flash 11.40.86.75 recovery
Boot into recovery
Flash 11.40.86.75 stock rom via adb (it'll take a while)
Once it's done, boot into Android.
Download your respective region's latest MM rom.
Send it to your micro sd.
Install it once Android detects the update file.
(It won't work with custom recovery. I tried every recovery Shakalaca has and only those two seem to work)
Once on the latest MM rom install any nougat patch update you wish to apply, because once you have a nougat rom, you can't boot stock recovery. (As far as my testings went)
So if I were you, I'd go for any update after the zenui 4.0 update since it's a bit better looking imo.
After that final update you can flash TWRP to root your phone. I prefer using magisk, since it doesn't modify the system files.
All you need to do is flash magisk and that's it. No need for SuperSU or anything else. And by any means, do NOT wipe your cache partition once you flash TWRP, otherwise you'll get stuck on the Asus logo during boot.
If you wish to retain the "certified" status in google play store's device certification, do NOT go into the play store before installing magisk. Also, don't delete play store data, otherwise you'll lose your previous purchases.
This post was longer than I initially thought it'd be, but I guess this sums it up pretty well.
Good luck
Click to expand...
Click to collapse
I made a mistake and could not install recovery stock, I followed what you wrote in the beginning install MM recovery and so I did a hard reset and I was able to install the most current recovery stock and installed ROM Oreo, Thanks. Sorry, I'm on google translator.

Error when installing new rom

So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
cblock said:
So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
Click to expand...
Click to collapse
Please post your question only once https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Please answer some questions:
Which twrp (file name)?
Which xXx rom(file name)?
Decrypted or encrypted storage?
Which rom do you want to install (exact steps)?
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
cblock said:
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
Click to expand...
Click to collapse
Decrypted or encrypted storage? Which rom do you want to install now? Please use latest codeworkx recovery.
Which xXx rom exactly you're coming from(file name)?
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
cblock said:
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
Click to expand...
Click to collapse
Just follow instructions in first post for clean installation, make sure you made backups: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Encryption means, you cannot access your internal storage without entering a pin when starting twrp or accessing the devices memory from outside.
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
cblock said:
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
Click to expand...
Click to collapse
For the error 7 make sure you downloaded the correct files, without download issues(maybe use checksum). have you removed compatibility.zip from the OB22 rom zip with either 7zip or total commander?
For vendor partition error try to mount vendor partition within twrp manually, if there's no checkbox, you need to flash what I suggested you here https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Earlier open betas created this vendor partion. You can try with OB13.
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
yohouse2 said:
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
Click to expand...
Click to collapse
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
cblock said:
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
Click to expand...
Click to collapse
How did you fix it? Can you explain what you mean by codeworx firmware? Could you provide link for file or guide?
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
strongst said:
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
Click to expand...
Click to collapse
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
cblock said:
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
Click to expand...
Click to collapse
Which twrp version and developer? And after this can I flash Pie directly or should I install something before it? Did you dirty flash or did you use clean install? Sorry for too many questions but I tried it many times and am frustrated that it didn't work, but you fixing it gives me hope.
yohouse2 said:
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
Click to expand...
Click to collapse
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
I was able to flash pie directly after updating the firmware.
twrp 3.2.3 should work
strongst said:
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
Click to expand...
Click to collapse
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
yohouse2 said:
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
Click to expand...
Click to collapse
Did you try the firmware link I posted earlier?
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
Will try in just a minute
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
still getting system patching unconditionally
Does it get stuck with an error?
Its suppose to say that

After updating to Oxygene 10..3.7 'Unable to boot,

Hello,
need some help.
Phone was setup with Oxygene OS 10.3.6, TWRP 3.0.3.2, Magisk. Target was to update the Full OTA of 10.3.7 via TWRP from downloaded file..
Unfortunat4ely im not able to boot the Phone anymore. Im able to try to start a update by sideload from TWRP wich doesnt work (getting error code KInstallDeviceOpenError )
By rebooting into TWRP i wasnt asked for the Pincode (?)
Any hints or tips would be appreachiated very much.
Thx. a lot
:jolt: said:
TWRP 3.0.3.2
Click to expand...
Click to collapse
Are you sure about that TWRP version? Either you are using a very old outdated version of TWRP, could be the problem, and likely the reason you weren't prompted for a pin, or that's not the correct version.
You need the latest version of TWRP which hopefully you can boot from fastboot.6T TWRP Downloads here. Note, 3.4.0.2 did fix the rom flashing issues, and you can use the installer zip no issues now. If you are able to get back into TWRP, I would backup your data as soon as you get access to it just in case. These phones are easy to fix, as long as you aren't worried about your data.
Thx for your reply, should been version 3.2.3.2. All in one Tool works and i flashed the imagge again, unfortunately all userdata was deleted.
Backup, a liddle old, was avaible .. so not a really Problem. Only the Time that i have wasted..

Categories

Resources