I have tried to flash Quark OS 3.0 in my yureka(AO5510) but it's not flashed and saying for error as "updater error 7"
YVTalan said:
I have tried to flash Quark OS 3.0 in my yureka(AO5510) but it's not flashed and saying for error as "updater error 7"
Click to expand...
Click to collapse
Don't flash directly.
First you have to wipe everything include system, data,internal storage,dalvik & cache. Have a try.
If not solved
Try to update modem first using fastboot. This error occurs due to baseband mismatch. In yunique also this error occurs when flashing lineage 14.1
Good luck
Related
I have a Lenovo a6000 device running on cm12.1 . After using it for about 2 months I downloaded miui 7 based ROM. But when I flashed the ROM it said "Updater process ended with error 7." and finish. I have tried with another miui 7 5.1.1 ROM but same error. Plzz help!!
arindam28 said:
I have a Lenovo a6000 device running on cm12.1 . After using it for about 2 months I downloaded miui 7 based ROM. But when I flashed the ROM it said "Updater process ended with error 7." and finish. I have tried with another miui 7 5.1.1 ROM but same error. Plzz help!!
Click to expand...
Click to collapse
First boot to twrp wipe system, data, cache, dalvik and then choose reboot to recovery from twrp only. After the phone reboots into twrp again, flash the ROM.
Thanks.. it really worked!!
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.
Hello,
Long story short. Moving from OP3T -> OP5, and I'd like to install LineageOS, or more preferably, the "new" MicroG (https://lineage.microg.org/).
Installed the latest TWRP according to the steps in this guide; https://wiki.lineageos.org/devices/cheeseburger/install
TWRP installed and everything transferred to the phone. Wiped the Cache, system and data. But trying to install i get an "Error 7" or more specifically: "Updater process Ended with ERROR: 7".
I have tried two versions of microG from (https://download.lineage.microg.org/cheeseburger/) and the latest "Normal" LineageOS. Same result. Also tried wiping the Dalvik Cache. Same error.
Any ideas?
Thanks for any help!
Update:
Downladed the latest OxygenOS from: https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-mirrors-official-oxygen-os-t3628190
and that installed fine in TWRP. Still would like microG Lineage Though...
try multirom twrp
more_than_hater said:
try multirom twrp
Click to expand...
Click to collapse
Tried. Same Error.
You need to flash latest firmware
So this is strange....
I tried installing the latest AISOP, just for trying. And the installation process worked fine, but I got all sort of errors when android was starting - so i did a complete wipe and tried microG again... and it worked. So microG is installed now with "normal" TWRP.
This was happening to me while updating from OOS 5.0.0 to OOS 5.0.2, the culprit was twrp bluespark. Flashed the other twrp latest version and it resolved my issue.
Hey! I have a OP5 with unlocked bootloader and had xxxROM v9.3 running
after updating to xxxROMxxx v9.5 I got a bootloop and decided to reset it
I flashed system, data, cache, dalvik with TWRP and wanted to flash the OOS5.0.1 OTA via TWRP, but I got ERROR 7
so I flashed the stock recovery, wiped cache, reset system, and tried to install the zip as an update but after a few seconds it closes without and error message and I am back where to select the zip file. I have already downloaded the same zip with different browsers 3 times and the old nougat ota as well, always the same! adb sideload doesn't work because OnePlus drivers suck with windows 10, it always says "not recognised" on my pc when I connect it. I have had many devices and adb sideload always works on my xperia z5 and fire tablet
pls help me I don't know how to fix that!
Use an Oreo compatible TWRP. Codeworkx, bluspark or some other.
Error 7 refers to some compatibility issue.
Rhoban said:
Use an Oreo compatible TWRP. Codeworkx, bluspark or some other.
Error 7 refers to some compatibility issue.
Click to expand...
Click to collapse
thanks man!
I don't know why it did not work before because I have already tried the recommended TWRPs and then I wiped everything, installed codeworkx universal and then flashing the zip worked just fine! I'll let it fully boot up once and make a full backup in case I f**k up again
Hello,
So basically, I got an OTA update today for my EvolutionX custom rom and I've installed it. Afterwards I got a boot loop.
Turns out, that for some reason, no matter what recovery I use, after the flash is done and recovery states "Updating partition details..."
I get a bunch of errors:
Error opening: '/sth/sth' (Operation not permitted)
Same thing happens if I try to wipe Cache or Dalvik through the recovery.
I've found some threads related to the issue, such as this one, but nothing helps.
I've tried several different versions of both TWRP and OrangeFox, no avail.
I can't roll back to previous ROM version because apparently it disappeared from EvoX website (it was EvolutionX 5.8, this one)
Any clue?
As far as i kniw newest evox is 7.3 and uses 4.19 kernel. It needs special recovery handle 4.19
matthias1976 said:
As far as i kniw newest evox is 7.3 and uses 4.19 kernel. It needs special recovery handle 4.19
Click to expand...
Click to collapse
Could you link me the aforementioned recovery handle? I can't seem to find anything
If you mean the one included in the EvoX zip then it doesn't work.
Update: Flashing the old ROM did not work.
Update2: I've managed to restore the OS by wiping data completely...does not fix the encryption issue in recovery however.