TWRP upgrade from 4.4.2 to Lineage OS 13 - Moto X Q&A

Hey, guys, my phone is stuck on a bootloop after downgrading from LineageOS 13 to spring 4.4.2, and back to anything pass 4.4.2.
I have twrp 3.0.3 TWRP-3.0.3-0-XPerience-LPAS23.12-21.7-1-GHOST-UNOFFICIALv2.img installed. I did a clean wipe before trying to get out of 4.4.2. I also tried to restore my CM13 twrp restoration and i am still stuck in bootloop. Bootloop is will be gone when I flash the flashable 4.4.0 zip. But I want my android 6.0 back.
anyone know what I am doing wrong?
solved by manually flashing to 5.1 system and recovery, then flashing twrp and lineageos13 zip

Related

Question about new Oos 4.0 flashing

I saw that the 4.0 version of Oxygen OS was available with a full version to flash. I have finally recieved my OP3T today, got TWRP installed with supersu root as well. Will I ruin anything if I flash the new 4.0 nougat version? I haven't gotten xposed installed yet (wanted to check out DPI scaling on nougat first), will that be possible after flashing 4.0 as well?
thanks in advance, so excited about this phone!
Hi
You can flash the zip using TWRP. Just flash SuperSU afterwards. Xposed won't work.
I've done that now, got nougat working fine, with twrp and SuperSU but I can't get the dm-verity warning to go away. I've tried flashing the stock recovery and then reflashing twrp and superSU, but no luck so far

No sim card after twrp restore

I have a oneplus 3t and am on OOS 4.0.3 and decided to upgrade to OOS 5.0. I downloaded the ROM, took a backup and then clean wiped my phone. Then I tried installing the ROM but it failed. So I decided to restore my backup from USB OTG. While restore failed and it showed error 255 while restoring data, so I wiped again and then restored everything except data. The phone rebooted and everything is fine except the phone is not detecting my sim card. I have tried restoring again and rebooting but it didn't work. I am using twrp 3.1.1
Please give a solution or tell me which ROM version to flash to solve this problem.
Just follow this guide to get back to factory default. And then try OTA update with the default recovery instead of TWRP.
https://www.google.se/amp/s/forum.x...ck-unbrick-tutorial-oneplus-3t-t3515306/page1
You need a special TWRP in order to upgrade to Android Oreo. Just google for Oneplus3 Oreo TWRP and theres a OnePlus-Forum Thread where you can download the TWRP that is needed for the Oreo Upgrade. Your Backup should work without Problems after you installed Oreo
just install bluSpark TWRP v8.61 from
https://forum.xda-developers.com/devdb/project/dl/?id=27655
and download official 5.0.1 ROM zip file from oneplus official site.
then you can proceed. You can use Magisk 15.3 after ROM installation for root access.
Make sure to reboot TWRP once after wiping everything from TWRP otherwise you may lose TWRP where stock recovery may take place.

OTA Updates Continue To Fail

Currently running LineageOS 15.1 nightly 5/28 with TWRP 3.2.1-0 on my Nexus 6 (Sprint). No root.
For sometime now, I haven't been able to successfully install an OTA update. About the time I started having issues, I accidentally installed SuperSU. To correct and remove the SuperSU install, I replaced the boot and system images by flashing stock Android 7.1.1 (N6F27M) including stock Android recovery. I then flashed TWRP and Lineage back and waited for the next OTA update. Once I received the update notification, I proceeded through the usual update process and when it reboots to recovery, it just halts in TWRP. I'm not getting a Status 7 error so I'm not sure what's wrong. (See attached image).
I personally don't have any issue downloading the nightly zip and flashing the update that way. It just bothers me that something isn't right and not working as it should.
Any one encounter this? Are there any solutions? Any help is appreciated. Thanks.
Update: Just flashed 6/3 nightly.
MadFoss1 said:
Currently running LineageOS 15.1 nightly 5/28 with TWRP 3.2.1-0 on my Nexus 6 (Sprint). No root.
.
Any one encounter this? Are there any solutions? Any help is appreciated. Thanks.
Click to expand...
Click to collapse
Update TWRP . . .
https://eu.dl.twrp.me/shamu/twrp-3.2.3-0-shamu.img.html

Stuck on boot loop after installing official Oxygen OS Pie Community build

I was running a custom ROM (Skydragon) earlier. I simply booted into TWRP, did the basic wipe then flashed the official zip file. Then after booting, its stuck on the boot animation for more than 20 minutes now. Any ideas how to resolve this?
I too faced the same issue. formating the data partition and flashing community beta build booted successfully for me. before you do this, completely back your phone contents to pc
You must flash with TWRP 3.2.3.0 or older!
i had the same issue. formated data had 3.3.0 twrp but still bootloop so i used unbrick tool to put my phone back to stock and then updated to last build though stock recovery and then unlocked bootloader, installed twrp, magisk and done.

Help with Magisk root Pixel 2 factory Android 9.0.0 installed

Hello,
I have been struggling to root my device. I have not wiped and rooted it in some time and now coming back to it again magisk keeps breaking my device.
I have clean flashed the latest android 9.0.0 build. I have flashed TWRP custom recovery 3.3.0 successfully. I have tried to flash magisk 3 times now and afterwards my phone wont boot. I originally used magisk manager to get the latest zip and patch my boot image. I then rebooted to to bootloader and ran fast boot flash boot patched_Magisk.img. This wiped out my twrp recovery and my phone wouldn't boot, i couldn't get back into twrp recovery. I reflashed latest 9.0 build and wiped everything. I flashed twrp again and tried to flash Magisk 20.0 from recovery. It was successful but again i couldn't boot into my phone and it eventually restarted back into recovery which i still had twrp this time. I then tried it again with 19.3 and the same thing happened. can anyone tell me what is going on here? What am I missing? I have been having reflash factory 9.0 build each time just to get it to remove the patched boot image and boot up again.
Was either the TWRP version or the two check boxes it has now to install twrp app as system. Installed 3.2.3-1 and didnt install the twrp app through the recovery check boxes and it worked.

Categories

Resources