Database Users

[Q] Unable to install TWRP Recovery after CM12 YNG1TAS1K0 update

Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:

acemccloud1 said:
Hello Folks!!!
I was on a Rooted Stock 5.0.2 CM12 ROM with TWRP recovery, when I got the notification for an OTA update (YNG1TAS1K0). I found out that we had to flash stock recovery to install the update, so I did that, but the OTA update wouldn't install and kept throwing error saying something like "unable to update /sideload/". After multiple attempts, I finally flashed the whole ROM (cm-12.0-YNG1TAS1K0-tomato-signed.zip) via the stock recovery, and now I am on the latest stock build (YNG1TAS1K0). Unfortunately, I am stuck on the stock recovery now. Whenever I try to flash the TWRP recovery (TWRP 2.8.6.0 for Lollipop), it goes into bootloop. I have temporarily flashed stock recovery again to make my phone usable again, but I would really like to flash TWRP again and root it. Any advice/suggestions will be appreciated. Thanks. :highfive:
Click to expand...
Click to collapse
Same problem dude...

I too got same problem, but now solved. Use all in one tool box by gohel.vishal first unlock bootloader, 2] resart phone 3] now enable usb debugging 4] again use toolbox to fash custom recovery 5] after flashing remove battery and restart into recovery, thats all.

Issue fixed using this thread:- http://forum.xda-developers.com/yureka/help/unable-to-flash-custom-recovery-t3108847
(Remember to disable "Update CM recovery" option in Developer Options)

remove battery after install recovery before restarting phone

Upgrading Rooted (TWRP+SU) PE 1575 from 5.1 to M. Need Advice + I have a guide

Hello,
Now before you ask, I've been doing a lot of research though searching threads and post. I'm actually going to post everything I found so far. On my first attempt of getting Marshmallow a few weeks ago, I downloaded the OTA and installed it. BIG mistake as I had TWRP and stock update didn't know what to do. I had to use CLARK to go back to stock then restore my phone back to Lolipop. Then I had to fix my Wifi Issue. After that I started doing a lot of research.
Here's all of my research links:
[FiRMWARE] XT1575 PuRE FiRMWARE aNd STuFF
Already Rooted Moto X Pure 2015 (KitKat) - Upgrade to Marshmallow, How?
Marshmallow and root -pg 2
MXPE on the way. Root after getting M update? (POST #18)
I need some input on people who have already went though this. So, this is what I'm getting:
1) Flash/Update to TWRP twrp-2.8.7.1-clark.img
2) Download "XT1575 stock unrooted TWRP backup" (from the first link). UNZIP THE FILE and place it in the TWRP folder on your phones internal storage.
3) Reboot into Recovery. Backup, then Restore the "XT1575 stock unrooted TWRP backup" image
4) If TWRP ask to install SuperSU, DON'T INSTALL
5) Let the phone boot back up and setup Marshmallow.
NOW, in order to Restore your apps+data with Titanium Backup, your phone has to be rooted. Currently, your phone is not rooted so you have to do the following:
6) Download 2.62 supersu and move it to internal/external SD.
7) Reboot into Twerp.
8) Install 2.62 supersu
9) Reboot
10) Test Titanium Backup and you should be OK.
Now, has anybody used this method or a similar method? I think this is possibly a correct method. Also reading that there's no need to use the seamless root since you can use supersu 2.62.

Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.

lafester said:
Personally I would flash the full stock mm firmware in fastboot. Then flash twrp and root. I don't believe your method will update modem.
Click to expand...
Click to collapse
But if it doesn't update the modem, I could just flash that on there though TWRP right? NON-HLOS.bin?

If I can get some more feetback, it would be great. I'm going to attempt in one more day. If everything goes good, I want to make a quick guide since it's hard to find concrete guides for this situation.

TWRP bootloop after flashing TWRP Solved

Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.

Easier thing to do is flash boot.img from the factory image to boot_a and boot_b if you are having issues.
This problem occurs when you flash TWRP if you have root installed. To avoid, remove root before installing TWRP.
Oh, I should mention to get into bootloader from TWRP, simply use the adb command "adb reboot bootloader". Should work, worked for me.

I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.

Nitemare3219 said:
I just have avoided flashing TWRP altogether. I rarely need to flash anything, so it can wait until I am at work or home to use a PC to BOOT TWRP each time I need it, instead of flashing it.
Click to expand...
Click to collapse
Until it gets a little more stable on the Pixel, this is probably a good idea.

Good idea. But I M sometimes flashing when I am at or on the way to work.
Flash junkie needs his daily dosis

mikaole said:
Don´t know if anybody had this kind of Problem before. Couldnt find anything.
Was on Stock V image with cutom kernel flashed via fastboot and SU flashed via fastboo boot to root.
Problem:
bootet TWRP via fastboot with newest drivers. Flashed RC via booted TWRP.
Wanted to reboot system, but was stuck in a TWRP bootloop. No chance to boot into bootloader also. Even tried changing slots in twrp but still only bootloop to twrp.
Than I thought about sideload because that's what I did with latest ota image from Google.
Here is what I did:
sideloaded the ota.zip via TWRP from PC "adb sideload ota_file.zip" ota_file should be the name of your ota file
It gave me an error, but after rebooting system all fine again. Back to stock V and bootloader is there again.
Click to expand...
Click to collapse
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.

Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
I have this issue and flashing supersu didn't fix my problem. Will go to factory image flashing.

Shadow of Destiny said:
I know its already solved, but here is what helps (for future):
Just flash SuperSU (latest Version)
Done. This will patch the boot.img so your phone boots in the OS again.
Click to expand...
Click to collapse
Thanks! This worked for me.

EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.

cognitivedissonance said:
EDIT: Never mind, I missed the comment guiding ppl to flash SuperSU. I suppose that when this thread was posted, that SuperSU was still being used instead of Magisk, so solution is essentially the same thing I'm recommending.
I think this thread is missing the much easier solution here:
I just ran into this issue with my Pixel 2 XL when I tried to update my TWRP version from 3.2.1-2 to 3.2.3-0. Here's how it went:
1. Downloaded the TWRP zip, md5 and so on from the official TWRP website for the Pixel 2 XL
2. Booted to TWRP and installed / flashed the zip of TWRP 3.2.3-0
3. Wiped dalvik and then chose Reboot to System from TWRP -- the phone booted right back into TWRP
4. Tried again to reboot the same way. Same result.
5. Installed / Flashed the 3.2.1-2 TWRP zip which was still on my phone, in order to revert to the previous version, and then Rebooted to System -- same result
6. Flashed 3.2.3-0 zip again, then flashed the Flash Kernel that I've been using, and then Flashed the Magisk v16.0 zip that I used to root, then chose Reboot to System -- AND IT WORKED; the phone booted normally and now I'm updated to the latest TWRP successfully.
tl;dr - The solution is to flash Magisk again after updating TWRP. Pretty sure this goes for kernel updates too.
Click to expand...
Click to collapse
This is a Pixel XL forum.

Homeboy76 said:
This is a Pixel XL forum.
Click to expand...
Click to collapse
Aren't the two systems (Pixel OG and Pixel 2) extremely similar? If they're not, then my advice should be ignored for anyone using the Pixel OG.

Motorola Moto X pure stuck on bootloop after failed root attempt, HELP!!

Hey everyone I just recently got a Moto X Pure with TWRP recovery already installed and the bootloader unlocked, unrooted. The phone was stuck on Marshmallow so I went to update and it would take me to TWRP recovery every time and when I reboot back into the system, I'm still stuck on Marshmallow. So I downloaded an app that would make me download OTA updates while still having TWRP recovery but it needed root access, which I didn't have. I tried all of the one-click root apps but non worked then I stumbled across an easy root method: ( oops it said I can't post links, but basically I downloaded a supersu zip and flashed it) which I followed very precisely and I'm pretty sure I did nothing wrong. But when I flashed the ZIP using TWRP and booted back into system it was stuck on the Motorola logo which I'm assuming is bootloop. I was going to download a stock recovery using fastboot but I discovered that it would relock the bootloader, which would render the device useless to me so I can't. I also tried wiping the Dalvrik Cache but it always failed. I'm new to all of this so please guys I'm desperate for help. Thanks in advance

You can flash with fastboot the newest stock(the same version or upper) without commands "...oem..." at start and the end.
Or
The newest downloadable without commands "..oem, bootloader, gpt, oem...". @Philo0o
BL will be still unlocked.

Do you have a tutorial on how to do that please?

https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110 @Philo0o

More accurately you need to flash boot.img which is the kernel , in the case where root was being installed using systemless mode.
Otherwise, if you tried an old SuperSU version (where systemless didn't existed or the ones that failed to detect to install using systemless method on this phone) you'll need to reflash the whole system partition (using Firmware system chunks or custom ROM zip file).

gts4lv: magisk rooted twrp + stock works, but lineage19/20 boot loops

Hi,
Disclaimer:
First post here, sorry if opening a thread here instead of replying to, e.g.
https://forum.xda-developers.com/t/rom-official-gts4lv-gts4lvwifi-13-lineageos-20.4536203/
is not correct. I've read the forum rules, and searched for similiar issues with that device, but at a glance did not find something alike.
Appologies in advance if I did a mistake or overlooked something, I'll try to learn and do better next time.
Device: Samsung Galaxy Tab S5e LTE, SM-T725, gts4lv
Bootloader: unlocked
Aim: magisk rooted twrp in recovery, lineage20
Following these instructions, I'm able to root the latest stock rom with magisk, flash that via odin, and get a magisk-patched twrp recovery:
https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root
https://twrp.me/samsung/samsunggalaxytabs5elte.html
(Details:
Get the current stock via frija, extract AP, patch via magisk on device, adb pull to host, flash stock with odin (magisk'ed AP,BL,CP,CSC).
Reboot device into stock, finish magisk app install. Reboot once. Device rooted. Installed TWRP app, granted root permissions to it, download twrp for device, patched image with magisk, flashed that to recovery via twrp app.
Sucessfully tested twrp, looks good.)
Trouble begins when I install lineage via twrp adb sideload, following
https://wiki.lineageos.org/devices/gts4lv/install#installing-lineageos-from-recovery
with the difference using twrp instead of lineage recovery.
Coming from the magisk-in-twrp-recovery rooted stock, I did a factory reset (wipe cache/dalvik cache/data), and twrp adb sideloaded the latest lineage20 for that device.
Console command outputs look good, no obvious errors. After the initial reboot, I got a recovery boot loop.
Going back to square one, reverting to magisk rooted stock using odin.
Then, I also tried sideloading lineage19, same result.
For the record: I initally started the lineage installation also flashing NikGApps or MindTheGApps (arm64), and the fdroid priviliged extension afterwards, but got the boot loop there.
I wiped system/data/cache/dalvik, went back to magisk-in-twrp-recovery rooted stock as described above and then tried with just lineage, but still a bootloop.
Do I maybe have to once again flash the AP with the VBMeta.tar via odin prior to moving from the rooted stock to lineage?
I am a bit hesitant to do so, because
https://topjohnwu.github.io/Magisk/install.html#important-notes says
"Never just flash only AP, or else Odin may shrink your /data filesystem size. Flash AP + BL + CP + HOME_CSC when upgrading."
Not sure if the VBMeta step is only required to initally unlock the device.
I am thankful for any advice how to narrow down the issue.
Best regards

I tried to install lineage+twrp+magisk/root at the same time without great result as well.
I was able to install lineage and twrp, but when I was there it was impossible for me to "activate" Magisk
So I switched back to custom rom + twrp + magisk/root. All good, but that's not what I was searching for.
I installed Lineage from Odin, then flashed twrp. https://wiki.lineageos.org/devices/gts4lv/install.
Try this guide, if you'll have success please let me know how you did it.

See my post here https://forum.xda-developers.com/t/rom-13-official-crdroid-9-4.4541563/post-88458655
Issue is with patching twrp with magisk it seems. Use either stock Lineage recovery or follow instructions I posted.