Hey guys! So I just flashed cm13 on my zen5. And I'm having a problem with gapps. I have downloaded the x86, 6.0 pico version of it. The rom flashed fine i suppose. The issue is with gapps. As soon as I started to flash gapps, 3 lines of error came and went immediately. After that once again I tried and it showed it was done. I booted the rom after clearing dalvik and cache.(I'm dumb and I forgot to clear system data and all). So now, as soon as the OS boots, it gives me force close. For every single app. What to do? Please help.
UPDATE: UPDATE: The error was with TWRP it seems. None of the files are flashing through TWRP. Can you give me the latest/stable TWRP link for it? For the time being, I have no google play services whatsoever in my device. The rom is from dgadelha I think. CM13.1 20161205
TWRP 3.0 links
https://www.androidfilehost.com/?w=files&flid=52033
TWRP 2.8.x links
https://drive.google.com/file/d/0BzMGgN-tWY2zQnVucDdIUFlQdHM/view
https://drive.google.com/uc?export=download&id=0B05UM2q8MdJFb0VrV2oxTG5rTzQ
While I was on XOSP I faced the same problem so I had to go to 2.8.x version.
Hi,
Just installed ZTE_A2017V1.0.0B11 via here following instructions. I have the Chinese phone version by default.
https://forum.xda-developers.com/showpost.php?p=68873487&postcount=4
Loads fine, I install SuperSU, couple of other minor packages through TWRP, everything works fine. Each time I'm clearing cache after install.
Then I install Gapps from http://opengapps.org/ (ARM64, 6.0), I have tried Nano and Micro, again clear cache and instead I get stuck at Axon boot logo.
Clearing cache again doesn't help, the only option I have is to wipe system and re-install OS but no gapps I have tried has worked.
Any idea why this might be the case? Thanks.
The phone that I got originally did have google play incidentally, probably installed by the aliexpress seller, but I'm not sure how. I had to wipe it earlier though.
Gapps are designed for custom roms. They probably don't work in the Stock ROM you are trying to use.
Have you unlocked your bootloader first? Have you installed the no-verity patch? Otherwise you won't be able to boot a modified system partition.
Yes, unlocked bootlader.
Oh wow, I had no idea, I thought gapps was a generic installer.
That explains it, I also didn't realize you could install Google Play through ZTE Market either.
All working now.
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
Hi, I got Pie to install with TWRP_3.2.3-Pie_siankatabg_OP5 on my device.
Go to this link:
https://forum.xda-developers.com/showpost.php?p=78523940&postcount=13
And follow my post on the part where it says:
" Notes for the Pie update: "
Let us know if those steps work for you. The firmware is linked to on there, pre-modified. Try flashing that pre-modified zip and see if your device boots.
richstant said:
Hi,
I have a rooted OP5, running 5.1.7 and TWRP. I used Oxygen Updater to download the new android 9 ROM. I tried to install via TWRP, but got an error about zip compatability & a treble problem. I found a thread stating that I needed a newer TWRP to fix the treble problem, so I installed TWRP_3.2.3-Pie_siankatabg_OP5 , which said it had Pie support, from here:
https://androidfilehost.com/?fid=1322778262903996029
That worked fine, but when I tried to flash the 9 ROM, I got still got the same error. Another post said to remove compatibility.zip from the ROM zip. I did that, and it now installed, but it wouldn't boot. Re-flashing 5.1.7 booted fine. I tried another TWRP - twrp-3.2.3-0-20181227-codeworkx-nocompatcheck-cheeseburger from here:
https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
That installs, and boots to system, but won't boot to recovery, so I can't install the 9 ROM.
Any ideas where I go from here to upgrade to 9?
Thanks!
Click to expand...
Click to collapse
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
strongst said:
It sounds like you did not follow the detailed flashing instructions in the first post here: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Is your device storage encrypted or decrypted? Have you flashed magisk? Have you used an older magisk(your end link leads to my post where I mention that)? Have you downloaded the rom file without compatibility.zip or did you removed it on your own?
Click to expand...
Click to collapse
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Maybe try backing your device up, and then locking the bootloader. Try updating with stock recovery on a locked bootloader. If that works, you can then unlock the bootloader and copy your data back
richstant said:
Thanks for the links both, but still no go. I was on Magisck 17.1, uninstalled Magisk with the latest uninstaller, flashed the ROM with compatability.zip already removed. Same result as before - I get the oneplus logo, then it just reboots instead of starting the system. I've only wiped cache & dalvik, I don't really want to wipe more than that if I can help it - it is worth trying a system/vendor/data wipe? I recovered by flashing back to 5.1.7 (also updated to Magisk 18 while I was at it).
Any more ideas? One thing I find a little weird is that I'm on the @siankatabg TWRP, when I tried either the bluespark & codeworx TWPR, I couldn't get into recovery with either, I just got a blank screen with a LED staying on light blue. Only the siankatabg recovery works. Surely any of them should work? Does this point to a problem?
I'm not sure what you mean by encrypted or not - I get messages about unencrypting when going into recovery, which I assume means I am encrypted?
THanks!
Click to expand...
Click to collapse
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
strongst said:
Please use an older recovery like twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img the actual pie recoveries require pie firmware(mentioned in last post of blue spark thread for example).
Click to expand...
Click to collapse
OK, I understand now - if I use an older TWRP, or the siankatabg version, it works fine. I can then flash the Pie ROM, however it still won't boot - I get the oneplus logo, then it just reboots. However having done the Pie flash, I can then flash the more recent TWRPs (codeworx or Bluespark), and can now get into recovery fine. However Pie still won't boot - I've even tried re-flashing the Pie ROM from within the newer TWRPs, but the result is the same - it gets to the oneplus logo, then reboots. At this stage I guess wiping system/vendor/data is the only way forwards?
*Edit* - OK, so wiping everything fixed the issue, I'm now on Pie. Flashing Magisk didn't work when flashing the ROM, but I'll try again once it's finished downloading all my apps etc.
Sorry I'm on mobile! Poor formating and typing is all my fault
So I'm out of my mind trying to fix and find a guide to fix my issues. This is how it all started
I was running the latest magisk (20.1) and OOS (9.0.17), when I installed Vance through magisk. I didn't read the instructions all the way, so I installed the module, it worked, then I saw that you can uninstall the YouTube system apk then install Vance. I deleted the Vance on my next reboot AND uninstalled YouTube system app, and I got stuck rebooting my phone. I have TWRP installed on my phone, not flashed (I didn't know the issues with TWRP when I installed the zip through TWRP). When it got stuck booting, I flashed magisk Uninstaller and it fixed the issue. I tried to reinstall magisk 20.1, and I got the same issue, stuck at boot. So I was able to go home, and use the oneplus 6t manager found here on the forums, which roots with magisk 18.0, and, it worked! But I couldn't update to the new magisk without it freezing my boot. After some deliberation on it, I decided to wipe my phone to try and fix it, and TWRP was still installed, and all my issues still persisted. After this setback, I found fastboot rom also on xda, and got it working, did an Ota to 9.0.17 from 9.0.16. Everything was working, until I went into my recovery and it wiped my phone. I don't even know where to go from here and I need help. Any and all help would be appreciated!
Edit: I just local upgraded to android 10 oos, and it seems to be fine. I don't know yet fully because I'm not at my house!
Somebody mentioned this link as a ton for the x606f, but did not say which file.
TrebleGSI - Browse /crDRom at SourceForge.net
sourceforge.net
Any ideas?
Got a response the link is :
https://sourceforge.net/projects/treblerom/files/crDRom11/2021.04.28/crdrom-v306-210428-arm64-bvZ.img.xz/download
It flashed fine but the install of nikgapps failed due to storage full error. I tried rebooting to system and tehn going back to recovery, but now I get a request from twrp for the dta decrypt password.
I tried default_password and everything else I could think of. I even reflash twrp with no luck.
Any thoughts?
The gapps issue is system needs to be expanded and our version of TWRP fails when trying to resize the partition. I will try manually, but first I need to solve the twrp problem. A smaller gapps package might also work.
I got twrp working again by doing a full rescue with LMSA and then reflashing twrp and magisk, but that leaves me where I was before I started the exercise.
The new rom looks good, if I can get twrp and gapps to work.
Resizing the system partition works with stock room installed, but fails as soon as the gsi imaged is flashed and rebóoting back into recovery gives decryption password issue.
Anyone who has this working help?
I can get a clean install now. Figured out the steps. Will post once I get it fully working.
The issue I now is "This device isn't Play Protect certified." No google apps will run.
I will research that issue.
Got it working with a few caveats. I will create a new thread with instructions shortly.
I'm not sure anyone understands what this thread is about. At all.