Database Users

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.

Bootloop after TWRP backup[Oreo]

I decided to upgrade to the latest Oxygen OS yesterday.
I had root, and TWRP Custom Recovery(3.2.1-0) and unlocked bootloader.
I unrooted, relocked bootloader and installed the latest full zip from oxygen os.
Then I unlocked bootloader and rerooted again and installed TWRP Recovery again.
Everything was working fine.
After everything was installed/restored I figured it would be good to take a nandroid backup, I took one and on reboot I get a bootloop to recovery.
I was able to reproduce this twice.
I think this has to do with something with fingerprint setup.
I'm a bit a loss on how to fix this without going trough a full wipe again.
I already tried wiping cache and dalvik, but no solution.

i had the same kind of issue. were you decrypted before?

If you are decrypted you need to flash the no verify zip. If you are encrypted try a dirty flash of OOS and Magisk. If you aren't using the most up to date version of Magisk that could have caused your problem. I've had no issues with Nandroid backup problems caused by fingerprint or pin security when using Codeworks or Blu Spark TWRP.

I was encrypted before and I am still encrypted.
I don't understand that taking a backup renders the phone unusable.
Restore fails with createTarFork() process ended with ERROR=255.
I made a clean flash(and locked bootloader) as it is a requirement for the latest OOS due to the upgrade to oreo.
Would it be possible to do a dirty flash with the full zip (I used: OnePlus5Oxygen_23_OTA_028_all_1801031502_04d7cc5.zip) and unlocked bootloader?
Secondly, I think I will try one of the suggested recoveries and see what it brings.

Should I flash twrp?

I'm currently running magisk, I've been trying to do everything systemlessly but it's getting frustrating, failed boots, bugs, limitations... I want to stick with systemless so I can count on my warranty which I can get back with two commands. Now, my question is, how hard and risky is to get stock recovery and lock back the bootloader once twrp is installed. Another thing I'm concerned about is if OTA update kicks in, I uninstall magisk and update it and it fails, I'm stuck, can't get any data or backup. Twrp would help a ton and I'm pretty sure I can just flash the new OTA image from twrp. But how hard and risky is restoring factory phone image (system+bootloader+recovery) once lord twrp is installed?

Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.

Daydreamaway said:
Why do you need to install TWRP if you can just boot it from fastboot? Well, using Magisk and updating system is always a bit risky, they have a guide on how to update and temporary remove Magisk, but it is always recommended to do a full backup.
To restore your device to a stock state, you can use MiFlash or download the fastboot version of the ROM, inside there is a script that will wipe everything and relock the bootloader, leaving no traces of your voided warranty.
Click to expand...
Click to collapse
That's great, and fastboot is always available no matter how corrupt the system is, right? What do you recommend for a full backup and what about allowing system modifications when twrp boots?

[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?

Need help regarding twrp backup

So I was on stock rom that was unlocked plus rooted,I was also on a different kernel. Before flashing that kernel, I had taken a full backup(It had magisk installed) through TWRP. Full means I didn't leave any of the boxes unchecked,it was a 11GB+ backup. Then it was all well and fine until I found that these kernels weren't liking my 64gb sd card(I created a thread earlier). So I went back to TWRP to restore my backup, I did so, well and smooth no issues. Now when I booted my phone, my phone would just turn off after showing the Asus LOGO, I tried multiple times to no success. It would just turn off after showing ASUS logo. To get out of this mess, I flashed Stock rom through TWRP.
Now I'm clean and fresh, I want to take a good backup and then flash AEX rom! What partitions should I backup??

Backup
Deeptesh Basak said:
What partitions should I backup??
Click to expand...
Click to collapse
Backup:
Data
Boot img
System
You may have to flash magisk/SU again after restoring in some cases...

Deeptesh Basak said:
So I was on stock rom that was unlocked plus rooted,I was also on a different kernel. Before flashing that kernel, I had taken a full backup(It had magisk installed) through TWRP. Full means I didn't leave any of the boxes unchecked,it was a 11GB+ backup. Then it was all well and fine until I found that these kernels weren't liking my 64gb sd card(I created a thread earlier). So I went back to TWRP to restore my backup, I did so, well and smooth no issues. Now when I booted my phone, my phone would just turn off after showing the Asus LOGO, I tried multiple times to no success. It would just turn off after showing ASUS logo. To get out of this mess, I flashed Stock rom through TWRP.
Now I'm clean and fresh, I want to take a good backup and then flash AEX rom! What partitions should I backup??
Click to expand...
Click to collapse
Backup everything for your first backup.
For incremental backups - boot, system, vendor & data should suffice.
While restoring only select the above four i mentioned. For cross rom restore functionality vendor partition is required.
For restoring stock rom from stock - only boot, system and data should be enough.