Hello guys,
i'm having the problem that whatever custom rom i'm trying to install with TWRP it will boot forever(>15min).
The stock OxygenOS boots just fine.
Rom's i've tried LineageOS 14.1, Resurrection Remix 5.8.3, ViperOS and some inofficial CM/LOS 13 versions.
Of course i tried to install all of them cleanly.
Once the installation failed or was corrupted and I had to use this unbrick guid to get access to my phone again: https://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Things i've tried so far: Reinstall TWRP, try different versions of each ROM and TWRP
Do you have any suggestions? Thanks in advance!
UPDATE: With clean install of newest OxygenOS(3.5.8) SimCard isnt being recognized.
bump
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'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!
I have an S5 that was running CM 14.1. I had moved from 13.0 to 14.1 with out whipping everything, so things were not perfect.
I wanted to move to Lineage 14.1 with a clean install.
I booted in recovery (Cyanogenmod Recovery) and whipped as much as possible.
When trying to Apply Update with the Lineage OS 14.1 nightly .zip, I got the "failed to verify signature" error. I have redownloaded the rom a second time to make sure I did not have a corrupted .zip.
I ended up reinstalling CM 13 because that is what I had not to far and needed a working phone.
So my question is about the recovery and the error I got with the Lineage rom.
Do I get the error because the type of recovery I have or does the Lineage OS .zip is known for generating this error (since it's still all very new)?
If the recovery is the problem, can I use the Official TWRP App to switch from Cyanogenmod recovery to TWRP ?
I have already tried to replace the recovery in download mode but Heimdall 1.4 generated an error as well regarding the "PIT file" so the process got interrupted.
Thank you in advance for any input!
bump!
Surely someone can answer this simple question!
thanks!
Hey there,
tried to install new lineage os 14.1 on my d802. came from cm13.
twrp is 3.1.1.0
Install new version 14.1 after clean factory reset. but all my phone does is to boot into recovery.
any help?
thanks a lot!
Hi,
I used Lineage OS 17.1 Lavender on my Xiaomi Redmi Note 7. I used their recovery to install the ROM and open gapps. Recently I downloaded the Brave Browser and I wanted to enable rewards. I than googled, that Brave doesn't allow rewards on rooted phones. I decided to wipe the entire phone, since I don't use the root functionality and to re-flash Lineage OS 17.1. I factory reseted the phone and wiped everything, just like I did, when I installed Lineage for the first time. I clicked on "Yes" when prompted that the ISO couldn't be verified, and waited for the flash. After a while I was "greeted" with Updater process ended with Error 7. I did some research and found out that it is something to do with the updater file verification and that I should try and delete some lines. I did that, but the error persisted. I than decided to try another ROM. I used Pixel Experience since it was working on my device before. Unfortunatly I had no luck. Same error message. I than tried to flash TWRP with fastboot, which worked. Wiped my device, just like they say it in all the guides (Dalvik, Data, Cache) and tried to flash Lineage (still no luck), than PixelExperience (still no luck) and Magisk worked. After I flashed Magisk I tried Lineage and Pixel once again, but still the same error.
If you know, how to fix that error I will be so glad. Is it possible that my device is bricked and beyond recovery? Thank you in advance.
update your tvvrp
Which firmware do you have installed? Use stable to maximum compatibility, on some ROMs if you have latest you gonna get that error. Also, use the latest TWRP or Orange Fox.
As Tatoh said, this error occurs when you have old firmware flashed on your RN7, some roms require specific version but usually flashing latest stable will give you best compatibility, here you have xda links to latest xiaomi firmware files: https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871