Related
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
point here.
phorcus said:
So i was flashing Hydrogen Os v2.5 through twrp and since 20 mins the .zip file did not flash so i switched off the phone and when i tried re-installing h2os v2.5 it was again taking longer to flash so i turned the phone off again and this time i installed oxygen os v3.1.0 ,for sometime the phone was in bootloop but when it booted there was no wifi, no network and i found that my phone had no imei number plus unknown baseband, unknown bluetooth also i don't have an efs backup can anyone help me restore my phone to normal once again?
Click to expand...
Click to collapse
Same happened with me phone doesn't boot... Can't install recovery...
Nothing works tried all possible ways like hard reset
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
zipalign said:
point here.
Click to expand...
Click to collapse
thank you for your help so i was on mokee 7.1 when i flashed only this hydrogen modem v1.1 and when i booted i did not find any volte option, so i went back to latest twrp recovery and tried flashing h2os v2.5 but since 20 minutes i was seeing this ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png ) so i switched off my phone midway and then i installed oxygen os v3.1.0 although it got into a boot loop but when it booted there was no wifi, no imei no, no baseband and many more and when i tried installing mokee or cm14.1 again although they got flashed but when i booted my device i saw oneplus logo and for a few seconds i also saw cm logo and the device continuously kept rebooting in a loop also i am only able to flash oxygen os v3.1.0 that too with no wifi, no imei etc. whereas cm14.1 and mokee wouldnt even boot but they do get flashed and h2os wouldnt even flash , please help :crying:
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Rohandd said:
what recovery are you guys using?
---------- Post added at 03:26 AM ---------- Previous post was at 03:24 AM ----------
This version works with TWRP 302.2, make sure you are using that.. DO NOT use stock recovery..
---------- Post added at 03:32 AM ---------- Previous post was at 03:26 AM ----------
The ideal way to flash h2os is, flash the rom, flash the debloater, dont flash gapps at all.. boot into the rom, the first boot takes a lot of time so dont worry as long as the phone is not rebooting again and again.. once it boots up go through the setup, dont use oneplus account, then install the google installer apk..
https://www.techmesto.com/install-hydrogen-os-google-apps-oneplus-2/
then follow the procedure written in this link to install gapps.. and you're done.. you can use h2os 2.5 now!
Reverting back to OOS 3.1, I have not tried myself.. Maybe, get into recovery (twrp) do a factory reset first after going into wipe, then go into advanced wipe, wipe everything EXCEPT internal storage.. then flash OOS 302 instead of OOS 3.1, and see if it working with all the connectivity. THIS PROCEDURE IS NOT TESTED BY ME!!
Click to expand...
Click to collapse
i am using twrp-3.0.2-2-oneplus2.img but h2os takes forever to install, but i did flash h2os v2.5's modem v1.1 before flashing h2os v2.5.
i am also seeing this message in twrp " Failed to mount /system (invalid argument) " please help guys
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
shravansp24 said:
As far as I know, the current oxygen version does not support the latest modem.. So you have two options..
1) install HOS again and like the above method use as it is
2) install HOS again to regain the networks(don't install gApps) and then using latest twrp, do a clean install of cm14.1 official.. But cm14.1 official with the latest modem is highly unstable if you use the mobile network..
My recommendation is to stick to the beta version of HOS for a few days and continue using it if you like it or flash cm14.1 once a stable build supporting the newer modem comes.. And when the updated oxygen OS comes in this or the next month, you can install it!
Click to expand...
Click to collapse
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
I didnt try the seraph build.. Will try it! Thank you
phorcus said:
thanks for writing out, but i am unable to flash H2OS it is taking forever to install, it just says " patching system image unconditionally " i tried installing it through latest twrp and i tried hybrid recovery too
Click to expand...
Click to collapse
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Rohandd said:
Flashing h2os does take more time than usually flashing other roms.. maybe 10 mins or so.. but not 20-25 mins.. and ideally 302.2 should work with h2os without any issues.. I am using that right now.. i can boot into recovery and everything.. I'm not really sure what is the problem here now..
---------- Post added at 05:01 AM ---------- Previous post was at 05:00 AM ----------
I did return to cm14.1 by seraph after flashing h2os.. and i did not experience any random reboots with mobile data on 4g.. im using vodafone and idea..
Click to expand...
Click to collapse
can you please check this screenshot ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
shravansp24 said:
I didnt try the seraph build.. Will try it! Thank you
Yeah itll show that message and will last for 5-10mins.. Hydrogen is very slow to install.. If it lasts longer, try flashing the recovery again and trying it..! Or directly flash cm14.1 to see if its booting
Click to expand...
Click to collapse
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
phorcus said:
i reflashed the recovery and installed cm14.1 but then the device gets into boot loop,what's the problem here?
Click to expand...
Click to collapse
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
shravansp24 said:
Even i got into a bootloop after flashing RR or cm14.1.. Dont know the exact issue..
But installing the new h2os, booting it and then clean flashing cm14.1 solved the bootloop issue..!
Click to expand...
Click to collapse
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
phorcus said:
can you tell me the steps you followed to install h2os? cause when i am installing it, it takes forever to install like i waited for almost 20 mins before giving up, or should i wait more?
and did you get the same message as i got like " failed to mount /dev/block/bootdevice........and so on..... device or resource busy "
check the screenshot here ( https://2.bp.blogspot.com/-s77sPKpb...600/Screenshot_1970-01-01-06-55-47%5B1%5D.png )
Click to expand...
Click to collapse
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
shravansp24 said:
1) Got into recovery
2) wipe-advanced wipe-everything except internal storage
3) install-HOS rom
(took around 5 minutes)
4) boot rom and finish initial setup
5) Got into recovery
6) wipe-advanced wipe-everything except internal storage
7) install-cm14.1 rom + gapps
8) boot
Maybe your rom is corrupt, try redownloading and im using latest twrp
Click to expand...
Click to collapse
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
phorcus said:
Thank a lot Bro that worked like a charm the downloaded file was corrupt but i got only one network and i am still on h2os, did you get both networks on cm 14.1?
Click to expand...
Click to collapse
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
shravansp24 said:
I got both networks to work in cm14.1 but theyre extremely unstable.. I have my phone in flight mode most of the time to avoid reboots.. Wifi works fine.. The moment you activate the sim, it depends on your luck then.. Mine worked 10mins, sometimes 15, then reboots, again 5-10mins and again reboot(tried official as well as seraph's)
Click to expand...
Click to collapse
everything is back to normal on my phone, actually i visited the service center today and they told me that my phone is dead and that i would need to pay 17k to change the motherboard :laugh:
problem here is that H2OS 2.5 messed up all our modems, and who has not made OOS EFS backup via terminal is in trouble now.
when problem popped up in all forums [XDA, and OnePlus one mainly] there have been proposed several solutions, like flashing H2OS modem .zip via recovery, after installing OOS.
so now many users have different scenarios to approach, and a working allwide solution seems not to be found 'til now.
personally I have official TWRP 3.0.2-2 and all my flashings have been made with it.
started from OOS 3.1.0 I had on my phone in the last week, 100% working, then flashed H2OS 2.5. seen the new ROM, decided to get back to something more familiar, so I wiped all and flashed latest nightly of CM13. it was working like a charm, but I had bluetooth issues with my xiaomi mi band [like I always had with OP2 and CM13], so I decided to flash back OOS 3.1.0 wiping data.
OOS 3.1.0 booted up, but without connectivity.
then I realized my modems have been messed up, and started looking for a solution.
the only one I'd try is to fastboot flash OOS 3.0.2 .zip [kindly uploaded by Spannaa], and see if my phone starts working again like it should.
'til now, I will stay with H2OS 2.5 which works perfectly. but when I have time, I'll empty my phone backupping all my stuff [fastboot flashing the .zip mentioned above will wipe userdata too, so I'd lose all my stuff] and try the fastboot thing [I already did it a few months ago, no issues at all].
for those who are in big trouble, that cannot flash anything from recovery, I'd suggest to try to fastoboot flash OOS 3.0.2 with the .zip linked above.
if this solution still doesn't come to an happy ending, then you have to try with the unbrick tool from Qualcomm and see what will happen.
the most important thing is and always will be: don't do anything until you are not aware of what you're actually doing to your phone.
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.
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
Device: ZB602KL 4gb
I was using the latest Liquid Remix 10.0.6 with the stock darkonah kernel for a wee after having just updated from LR 10.0.5 and Singh 2.7. When I noticed he released a stable update for his kernel to 2.8 I downloaded it and flashed it as normal. Upon booting into LR, the lockscreen no longer responded to my fingerprint. It wasn't even turning the screen on. After inputting my password, I noticed that my wifi wouldn't turn on. And later when I tried the stock gcam, it kept crashing. Cam2API Probe is completely blank.
Things I've done to try and fix this:
1. Rebooted multiple times.
2. Someone suggested wiping /system and /vendor only and dirty flashing the rom. Did that, dirty flashed LR, openGApps(wasn't sure I needed to, did it anyway), and Magisk 19.
3. Clean flashed stock 340, decrypt and magisk19.
4. Flashed fw_only-X00T-WW-16.2017.1902.037.zip. I had previously flashed fwpie050.zip(the one from opendesktop) when updating LR before all this happened.
5. Fully wiped phone including internal storage and flashed the latest HavocOS which I am on right now as I've given up and just need it to work as a phone for the meantime.
Camera seems to be working again on Havoc, though. Fingerprint is still missing from Security settings and WiFi will not turn on.
Any help would be appreciated. Thanks!
I also got bootloop by using magisk 19.0,use magisk 17.1 or 18.1.
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Tianhe said:
How did you clean flash stock 340 ? If it was through TWRP then try fastboot ROM
Click to expand...
Click to collapse
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
defurious said:
Yes, through twrp. What are the adb commands to do it through fastboot? I used Avinash's modified stock340 btw.
I think the modem firmware is corrupted somehow. I cannot receive or make calls but can get 4g data connection and SMS. My wifi mac address sometimes is "Uknown" or 02:00:00:00:00:00.
Click to expand...
Click to collapse
Flash fastboot stock rom it will fix the issue.
https://forum.xda-developers.com/as...ow-to/guide-revert-to-stock-rom-lock-t3798420
Hit thanks if it helped
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
farhanshaikh671 said:
Flashing stock rom thru adb basically reverts your phone to factory state so everything should be fixed unless somehow your hardware is damaged
Click to expand...
Click to collapse
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
defurious said:
Yeah, i understand. I'm just a little confused because the steps in the linked post above are for 334. I don't know how to do it using 340. Should I just follow those steps then after relocking, manually update to 340, and then unlock bootloader again?
Is there any way to flash fastboot rom without relocking bootloader?
To me it seems that i'm having some problems with pie beta firmware. After flashing 339 and then LR 10.0.5 which is the last version before requiring pie beta firmware, everything is working normally again. But as soon as i try to update to 10.0.6 or latest Havoc with pie beta firmware, the wifi and fpsensor stop functioning. But the strange thing is, I was on LR 10.0.6 for a week before flashing Singh 2.8 kernel which then killed my hardware.
Now I'm wondering if I should just wait for official Pie release from Asus.
Click to expand...
Click to collapse
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
akhil850 said:
Just Flash Stock rom via fastboot to fix this issue. Dont bother about bootloader getting relocked.( U may unlock it ri8 after flashing)
And one more thing.
If u flash Decrypt.zip used for Stock Oreo roms on Stock Pie, you will loose wifi and fingerprint options.(I experimented this thoroughly)
So flash decrypt.zip for pie on Pie Stock(Beta or Stable).
Tested personally and worked fine.:good:
Hit thanks if it helped,
Click to expand...
Click to collapse
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
defurious said:
This must be the problem then because I didn't know there was a decrypt for pie beta and i usually do flash decrypt coz i have a phobia that my internal data will get encrypted with no password to recover. ?
Can you provide a link for pie beta decrypt please? I can't find it here in xda. Thanks
Click to expand...
Click to collapse
Here https://forum.xda-developers.com/as...w-to/decrypt-zip-asus-stock-pie-roms-t3923265
Hit thanks if i helped.
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?