Stuck on patching system image unconditionally when flashing oxygen - OnePlus 2 Q&A, Help & Troubleshooting

Hello
I had a problem with my phone earlier today where it would reboot one or two minutes before it started, so I install twrp recovery and tried installing Ota 009 which I found here on xda, how ever now I'm stuck when I'm trying to install it?
Thanks in advance

Did you flash the whole ROM or only the OTA file?
For the latest version (2.1.2), as there is no full zip, only the incremental file, you need to flash the FULL 2.1.1 and then directly the 2.1.2 in TWRP.
You can flash only the OTA file alone if your system is stock and untouched (no root / TWRP).
In your case you need to flash the whole ROM then the OTA.
Check this thread -> http://forum.xda-developers.com/oneplus-2/general/rom-mirrors-official-oxygen-os-roms-ota-t3209863

I'm trying to flash Oxygen OS 2.1.1 the full rom but it just get stuck in TWRP nothing happens. Im using the rom from that thread you just liinked

Try wiping dalvik cache, cache, system, and data. (NOT INTERNAL STORAGE) then flash again.

Related

rooted but running stock image... how to upgrade?

A while back i rooted my 4g plus and ran CyanogenMod for a while... it had a few small issues and people were raving how stable the stock image was so i downloaded and applied a stock image and have been running since.
Recently started getting the update notice but when i try to apply it the reboot just dumps me into TWRP, if i reboot from TWRP my phone boots back up and tells me the update has failed.
I have been googling around like crazy but am finding alot of different answers:
The download of the image is stored in cache and you just need to point TWRP to that temp image and it will upgrade
Where is the cached image stored on the phone?
Will this keep my phone rooted?
Download the latest release and apply it via TWRP like i did originally.
Will this update or wipe my phone like new?
Will the phone stay rooted?
Thanks!
I may have misinterpreted what you wrote - however, if you're referring to the stock (i.e. images from Motorola), you cannot update via OTA whilst you have TWRP recovery; the OTA updates only will flash via a stock recovery. Furthermore, the OTA update will fail if you're rooted or have other modifications to your system/recovery. Having an unlocked bootloader does not appear to matter.
In order to apply an OTA update, you'll have to un-root and flash a stock recovery onto your system, or flash a stock image (such as this Nougat fastboot image: https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369) which will remove root and TWRP on your system. Depending on what options you choose with the fastboot ROM, you can elect not to wipe your internal storage (but still a wipe of your cache and Dalvik at least is advised), check the linked topic for more information.
Then you should be able to update. Failing that, perhaps someone will be able to provide a TWRP backup of their system with the latest updates included, but from what I've seen, you may have to clear cache and data to boot.
If you wish to find the OTA update, it's not in your cache, it's actually hiding in '/data/data/com.motorola.ccc.ota/app_download'. You'll need root access to see the OTA file though.

Cannot update to 4.5.14

Hi,
I have a rooted OP5 with 4.5.13.
I tried to install the flashable zip (from here) via TWRP without wipe, but ended up in a bootloop.
I've restored to the nandroid backup, wiped data, and tried again. This time the OP5 managed to boot only to recovery.
I've verified the md5 of the file I've used.
Do you know why this is happening? Do you know how I can upgrade to 4.5.14?
Thanks.
Did you download the full ROM or just the update?
I tried both. I didn't succeeded to install the update (as it is not intended for rooted devices).
The full rom is what caused the bootloop.
If you are doing a dirty flash you wipe cache and system. If you are doing a clean flash you wipe cache, system and data. It doesn't sound like you wiped the correct partitions when doing your flash. You also need to flash Magisk or SU after the ROM flash and before booting up or you will lose TWRP and root. If your phone is decrypted for some reason you also need to flash a no verify zip or your phone will boot loop because OOS is made for encrypted phones.

[Question] How to restore TWRP backup of stock 8.0 ROM, after flashing 8.1 ROM

Before going into the subject, I'll say that I have tried to seach this matter in XDA and Google, but nothing showed up.
Okay, so my matter is that I can't restore my backup of stock rom(8.0) after I flash a 8.1 rom. I've backuped with official TWRP "recovery-3.2.1-2-oreo.img".
My procedures are :
back up stock 8.0(system, data, cache, efs) with official TWRP "recovery-3.2.1-2-oreo.img"
flash oreo rom(with wiping internel, data, system, cache) and boot it fine.
restore my stock backup with same TWRP
boot system
The results are :
Goes past boot logo
Boot animation('android one' with colors sliding) shows up
and... just infinite loop of boot animation.
The ROM I used is RR.
I think the main problem is related with encryption.... Just my thought, tho.
So what I'm asking is :
1. If you face the same problem as me?
2. If you aren't and you restore goes fine, please tell me your procedures including ROM used and TWRP used.
3. Whether it is safe to decrypt stock rom?
Thanks in advance!
You don't need to flash stock ROM again. You have a system image backup(system, data, cache, efs), right? Wipe data , system, cache if you are coming from any other ROM. Then reboot to bootloader. Boot into latest TWRP from Fastboot (don't flash). Then go to restore and restore the system image you had backed up. Don't restore efs if you haven't lost your IMEI.
I've done exactly as ypu told, but it doesn't boot...
Did you manage to restore without problem with your method?
Yes I was able to. No problem here.
What TWRP did you use? Also, what ROM have you flashed?
Used the latest TWRP by MohanCM for Oreo. I did it when I was on Lineage os and wanted to go to stock
@guy_infinity Okay, thanks for your answer! Gonna try out later, once more.
Hmmm.... Still didn't boot up.
I thought I had to do everything from the begining, but flashing stock with save userdata option rescued me.
P.S. does anyone know about the error E: recv error on uevent?
try flashing stock rom using mi flash and after flashing restore normally using latest twrp/deadman's without system image voila everything will be back
@arjunbalan1994 Big thanks for your suggestion! Will try that too later
Hi, did you solve your restore problem? I have the same w/ my Redmi Note 5 and stock Miui backup after flashing RR.
Thanks for your help
I was use 8.1 root and twrp recovery. Yesterday fastboot flash may rom and update 2nd may OTA
Don't understand : May rom is Miui rom?
And did you restore your miui rom 8.0 backup ith twpr after the fastboot flash stock?

Sanity Check on Flashing Stock 5.1.4

Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
UPDATE: I did do something stupid after all. I forgot that my Oneplus was decrypted. So all I had to do was go into TWRP and go to Wipe and format data to re-encrypt it.
Z-Blade said:
Ok, so I am not new to flashing rom but for some reason I am having huge issues trying to install clean stock OOS 5.1.4 rom. Just want to double check I am not doing anything stupid since I mainly been flashing custom roms (xXx rom mainly).
So I simply wipe dalvik/ART cache, cache, system and data (want to start off completely clan) then flashed the OnePlus5Oxygen_23_OTA_037_all_1807181258_7b4b6.zip file in TWRP.
I am currently on the latest blue TWRP and after flashing, it will try to boot but reboots back into TWRP. I have tried the zip file from a number of sources and they all do the same. Am I missing something here?
Click to expand...
Click to collapse
When starting fresh, wiping of internal storage should be considered. I recommended 2 guides here https://forum.xda-developers.com/on...nos-beta-1-android-oreo-t3710003/post77205633

Actual custom rom flashing instructions ??

This is my first Oneplus device and I just realized that in this device, in order to flash Custom Roms, you need to have a OOS installed beforehand plus not wiping /System partition.
So I was wondering which one is the best and quickest way to do a clean and fresh install from scratch, with the less amount of stuff from previous roms since wiping /System will end up on a bootloop.
Would it be something like this:
Starting from fresh and clean OOS latest version:
-Wipe /Data /Cache /Internal
-Flash Rom + kernel (optional) + TWRP
-Reboot recovery
-Flash Gapps + Magisk.
-Reboot System.
Is this the cleanest way to do it ?
I've seen @Koogly 's video but I dont know if theres a better way to do it.
Thank you all.
dirtyl0lharry said:
This is my first Oneplus device and I just realized that in this device, in order to flash Custom Roms, you need to have a OOS installed beforehand plus not wiping /System partition.
So I was wondering which one is the best and quickest way to do a clean and fresh install from scratch, with the less amount of stuff from previous roms since wiping /System will end up on a bootloop.
Would it be something like this:
Starting from fresh and clean OOS latest version:
-Wipe /Data /Cache /Internal
-Flash Rom + kernel (optional) + TWRP
-Reboot recovery
-Flash Gapps + Magisk.
-Reboot System.
Is this the cleanest way to do it ?
I've seen @Koogly 's video but I dont know if theres a better way to do it.
Thank you all.
Click to expand...
Click to collapse
First time from oos zip
Flash latest stock rom oos
Flash twrp zip
Wipe data and cache
Reboot to recovery
Flash latest stock rom oos zip
Flash twrp zip
Wipe data and cache
Flash custom rom zip
Flash twrp zip
Flash gapps zip
Flash magisk zip if you want root
Reboot to system
If you are already on custom
Flash lastest stock oos zip
Wipe data and cache
Flash custom rom zip
Flash twrp zip
Flash gapps zip
Flash magisk zip if you want root
Reboot to system
If going from custom to oos
Back up all your internal storage pictures videos music etc
Wipe data internal storage and cache
Flash latest stock oos zip
Flash twrp zip if you still want to customize
Reboot to recovery
Flash latest stock oos zip
Flash twrp zip if you still want to customize
Flash magisk zip if you want root
Reboot to system
If you want a custom kernel on any of these methods I would recommend booting the rim first and going through setup process the rebooting back to to twrp after and flashing the kernel
Also you will want a USB c otg port bc after the first flash your data will be encoded. You can select the otg storage via twrp to make the process easier.
If you don't have an otg cable you will need to sideload each zip via cmd prompt with fastboot tools and sideload in twrp
After all flashes are complete and you boot the rom the encrypted data will no longer be encrypted on custom rom flashing if going back to stock oos rom you lose all internal data
Most ROMs threads have instructions in main thread and those should be followed first. Some ROMs may require some bits and pieces from original oxygen rom prior to custom install
Asoip for example
Is flashing oos necessary if we unlock bootloader?
I see instructions for lineage os dont mention flashing of oos bit they have the first step as unlocking the bootloader
mustafabakrolwala said:
Is flashing oos necessary if we unlock bootloader?
I see instructions for lineage os dont mention flashing of oos bit they have the first step as unlocking the bootloader
Click to expand...
Click to collapse
You flash oos first so you have the correct vender and up to date files etc before flashing. Some ROMs require you to flash old oos versions bc their rom was based on that oos vender

Resources