I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
Hi, If you already have twrp recovery and you can boot into twrp recovery, then you need to download stock oxygen os 2.2.1 ota.
when you download oxygen os 2.2.1 ota, flash it via twrp recovery, after that wipe factory data reset, then you flash your custom roms later. this will bypass the error 7 and you will have to resume enjoying your custom roms.
Here's what happens, when u totally erases the system, data, and formats everything with twrp recovery, custom roms don't run again, i think they kinda need some basic files from the stock rom to enable them to run. i experienced this myself with aicp and this is how i fixed it. so go on, look for the oxygen 2.2.1 ota.zip, download, flash, then wipe data fastory reset, then you can now have your custom roms flashed and working. again.
Right!! but oos 3.0 official is also working
shahark86 said:
I've had many roms flashed on my op2 through twrp, but now whenever i try to flash any rom(cm, exodus, aicp etc.) I get error 7. I tried deleting asserts line on "updater-script" but no luck...
Current rom: Resurrection remix 5.6.9
Click to expand...
Click to collapse
It's there to protect you from flashing a ROM incompatible with your current bootloader (there's two of them, pre oos3 and oos3 bootloader/fastboot).
So if you want to flash a ROM which is Lollipop (or using Lollipop bootloader like easier versions of Graraks and Seraph08s builds) you will have to restore your phone to oos2.x.x first. Same goes the other way around, and also your recovery system must be compatible with respective bootloader.
This info should be force-feeded to every noob checking in on this forum hoping for an easy swapping of ROMs on this phone, which is not gonna happen because of this.
Related
i am using the latest hydrogen os..marshmallow...
but i can't restore previously backed up cm13 with the twrp used in installation of hydrogen os.....so i tried flashing normal twrp with fastboot....this led to not even getting to the recovery...i was stuck in the boot logo
so..i again flashed the hydrogen based twrp and tried flashing cm13 with it...but it didn't work either...
so guys...how can i use another rom..with my condition...i can't flash neither recover previous image...
help guys
Try flashing the latest community version of Oxygen OS first with the modified TWRP.
Then flash the stock recovery of Oxygen 2.1.2.
Now flash stock Oxygen 2.1.2 with the stock recovery.
Now you can flash the normal TWRP and restore CM13 image.
PS- I didn't try all these. But I think it should work.
This might help
I found a hybrid TWRP that claims to be compatible with Hydrogen. Oxygen, Vanilla Marshmallow etc., made for the OP2. Here you go.
http://forum.xda-developers.com/oneplus-2/general/recovery-twrp-3-0-2-hybrid-supports-oos-t3362904
With that you might be able to get into recovery again and install whatever OS you like. I found this searching for the TWRP decryption problem.
Fennec
I officially upgraded to 3.0.2, unlocked and rooted my phone.
It was fine for the first few times I flashed multiple ROMs. But ever since I flashed Exodus, I keep having issues switching to different ROM.
A week ago, I flashed "Switch to OOS3_H2OSMMv7" zip and was able to flash Resurrection Remix, but today when I tried switching to CM13 or PA it gets stuck at flashing the ROM zip. I tried flashing the firmware zip again and flash the ROM, but to no avail. It won't flash any ROMs now, just stuck at recovery while flashing the zip.
I have a working fastboot and recovery mode though, so I'm trying to avoid flashing the entire factory image but that seems to be only option left. Does anyone have any clue as to why this is happening and how I can fix it?
Edit: Resurrection Remix gets installed fine, CM13 and PA still giving me issues.
Edit: I downloaded the latest version of CM13 and it works. Earlier I was using June 30 build which seems to have issues with the new firmware. I'll try out the new PA build to see if it fixes that too.
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
piyushmodi01 said:
What error does your recovery gives?
Do you have Data Backup?
Can you access ADB while in Recovery?
Click to expand...
Click to collapse
It does not show any error as it just looping while installing the zip. I have to force shut down the phone to exit it.
Yes, I have backed up all my data
Yes, I am able to access my phone in both ADB and in fastboot modes.
After flashing Custom ROM, Wipe data, cache, d-cache and then reboot.
If still doesnt work try flashing another custom ROM. You can use adb-sideload to flash another zip in recovery mod.
I haven't unlock my phone yet. I used the qpst tool to flashed the rom to zui 0.9. Then I flashed the offical twrp.
Offical cm13, cm14 and some aosp rom(slim etc.) can boot and work well on my device after flashing, but cm based rom such as nuclearom and bliss cannot boot. They always stuck on the boot screen and fail to boot into desktop after a clear flashing. Have I missed something?
You have to unlock bootloader and do clean flash otherwise you may encounter such problems with custom roms
I unlocked my bootloader and managed to install TWRP and Magisk to get root on stock. But I don't like running MIUI, so I tried PA, which didn't boot, just stuck on the Mi logo without an animation on the bottom. So I tried Lineage and that one won't boot either.
Between each failed flash and boot I have to reflash MIUI using fastboot or otherwise I can't get into recovery. Next I tried to flash some GSI systems using fastboot flash system <image> and formatting user data, but that didn't work either, it loops on the kernel boot screen. Am I missing something? Are there more steps that I should take before being able to boot custom ROMs?
PS. I'm running the latest MIUI Global 10.3.11.0 (PFJMIXM)
paxy97 said:
I unlocked my bootloader and managed to install TWRP and Magisk to get root on stock. But I don't like running MIUI, so I tried PA, which didn't boot, just stuck on the Mi logo without an animation on the bottom. So I tried Lineage and that one won't boot either.
Between each failed flash and boot I have to reflash MIUI using fastboot or otherwise I can't get into recovery. Next I tried to flash some GSI systems using fastboot flash system <image> and formatting user data, but that didn't work either, it loops on the kernel boot screen. Am I missing something? Are there more steps that I should take before being able to boot custom ROMs?
PS. I'm running the latest MIUI Global 10.3.11.0 (PFJMIXM)
Click to expand...
Click to collapse
Are you sure you're following the ROM developer's installation instructions correctly?
Are you:
performing the correct TWRP pre-install routines? (e.g. wiping cache, system, vendor, etc.)
flashing a specified MIUI ROM prior to flashing custom ROM?
flashing some specified post-install scripts?
flashing a non-recommended GApps package? (for ROMs that don't include GApps)
others
Check each ROM's install instructions and make sure you follow them right to the dot.
haakufurou said:
Are you sure you're following the ROM developer's installation instructions correctly?
Are you:
performing the correct TWRP pre-install routines? (e.g. wiping cache, system, vendor, etc.)
flashing a specified MIUI ROM prior to flashing custom ROM?
flashing some specified post-install scripts?
flashing a non-recommended GApps package? (for ROMs that don't include GApps)
others
Check each ROM's install instructions and make sure you follow them right to the dot.
Click to expand...
Click to collapse
Yeah, apparently wiping system is necessary. I'm used to only having to flash a ROM and it would rewrite system completely on other phones.
Thank you for the help
Are you using the correct twrp? Wipe, advanced, wipe system,vendor, data, cache/dalvic. Install rom, then format data afterwards. Also recommend to have rom on a PC/otg since you're gonna be wiping internal storage
I wanted to upload a new rom to my phone (pine, 16GB), but it will never boot. Always after rebooting, TWRP will be loaded again. I'm tried multiple ROMs (LineageOS, DotOS, MokeeOS ), but the problem occurs for all rom. TWRP says, flash succed for every one system, but not booting after reboot.
I'm used twrp-3.5.0_9-20210101-pine-arm64 version. Only I can do flash a stock rom using MiFlash, but no custom rom via TWRP.
Mi device is correctly unlocked via Official Unlock Tool app.
Can you tell me why?
Thanks
Maybe try another twrp version or another completely like OrangeFox can't really tell you why i don't have as much knowledge in why or how it works but i have tried a lot on mine so this should be ur first troubleshooting step from my point of view also have you flashed the ROMs with their instructions some say the sequence you should format or wipe ur data etc...
Working for now,
The problem was that I didn't choose to Format data