Database Users

Question :: Why doesn't TWRP stick?

Hi there XDA, I've recently been having issues with custom roms and random reboots, so I decided to go back to stock. Going back to stock I used fastboot to flash the system and boot images. After some setup I wanted to get root. Instead of there being twrp I ended up with the stock recovery somehow. TWRP 3.1.1 seemed to stick, then I decided to upgrade to the most recent version. And it no longer sticks(TWRP recovery).
I just don't know what to do or what the cause for this to happen may be. My only thought is that I'll have to fastboot flash recovery every time I want to modify something.
Any way you guys would be willing to shed some light on what's going on for me???
Sent from my SM-N7507 using Tapatalk

probably since you are not rooted

@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.

wizardwiz said:
probably since you are not rooted
Click to expand...
Click to collapse
Nah, I'm rooted through magisk

Exodusche said:
@dirtyreturn What was said above go grab the latest magisk.zip and have ready in your storage. Then after flashing twrp head into and flash the zip. Should stick from then on I haven't had any issues.
Click to expand...
Click to collapse
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.

double post

dirtyreturn said:
I don't doubt you, this hasn't happened to me before since owning the device. It just started, like, May 1/2 after flashing stock 8.1 system and boot images.
Click to expand...
Click to collapse
So your flashing twrp after first boot, rooting and still won't stick?

Exodusche said:
So your flashing twrp after first boot, rooting and still won't stick?
Click to expand...
Click to collapse
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.

dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
Who knows maybe google changed something. Do it my way and you will be fine.

dirtyreturn said:
Like, for two years I've had twrp on this device without any issue. Just all of a sudden after I fastboot flashed system and boot of 8.1 it just does not want to stay put.
Click to expand...
Click to collapse
When you flash system and boot images, root is removed. On Oreo, TWRP does not persist without root being maintained. I believe on Nougat or Marshmallow, this was not the case. When you booted into the stock rom, this restored the stock recovery.
Flash TWRP then boot directly into TWRP and flash Magisk. When installing new security patches, boot directly into TWRP and reinstall root.
Sent from my Nexus 5X using Tapatalk

any help ?

Do I have to flash no verity?

I really just want to root stock. I have the Boost Mobile Perry.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
Yes. Install twrp, flash no verity, format data (to remove encryption) flash magisk. Some people have said if you took the last security update, you may have to patch the boot.img with magisk manager then flash the patched boot.img in fastboot or twrp to root. And will likely need the latest magisk beta (16.4).

I really don't care about encryption.

guitardoc64 said:
I really don't care about encryption.
Click to expand...
Click to collapse
You have to remove encryption.

Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.

guitardoc64 said:
Ah okay. Thanks for letting me know. I guess I will have to wait till I get the time on a day off to get everything set up again.
Click to expand...
Click to collapse
Don't neglect to backup EVERYTHING in TWRP before doing ANYTHING (and store those images off-device!). Strongly suggest booting a TWRP image to perform this task vs. installing/flashing to the recovery partition, especially if interested in preserving/restoring OTA capability at a future time.

Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.

guitardoc64 said:
Of course I will back up everything. Honestly this is the first device I have not rooted since I started with Android. Everything else I rooted as soon as I got it.
Click to expand...
Click to collapse
Welcome to the 5% club which is probably generous based on the number of noobs (and veterans) who neglect to image their device before messing with core components. Of course that figure may be skewed as those that do take proper precautions rarely write posts that begin with "help!" and have no path back to the prior working state.
Also, resist the temptation to flash a custom recovery (twrp) vs booting from fastboot if you want to accept accept future OTA updates or roll back to pure stock. While restoring stock recovery is possible it certainly complicates the process. Can always revisit the decision at later time.

guitardoc64 said:
I really just want to root stock. I have the Boost Mobile Perry.
Click to expand...
Click to collapse
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
Don't have a definitive answer on the latest firmware. Suggest going through the above steps first. If no joy it's a simple matter to patch/flash boot.img .
You are wise to boot a twrp image vs flashing over stock recovery. Simplifies fallback should the need arise. Don't neglect to backup stock and store off device (or at least on a SD card).

davejames500 said:
I just got a few of these phones and looking to root them. I installed all the latest updates. Did you to have to patch the boot.img with magisk manager then flash the patched boot.img in twrp to root?
Or I follow these steps only?
1. unlock bootloader
2. Boot into twrp located here https://forum.xda-developers.com/moto-e4/development/twrp-twrp-moto-g4-qualcomm-t3655160
3. delete the data folder
4. flash magisk
5. flash no-verify
6. done?
Click to expand...
Click to collapse
For .3, format data to remove encryption.
But the rest should work. If not, you have to download the current firmware ( the version you're on) if you can find it. Extract the boot.img from it. Then use magisk manager to patch it. And use fastboot to flash the patched boot.img

i have the moto e4 mkt which no verity version do i have to flash ?

Rafasama said:
i have the moto e4 mkt which no verity version do i have to flash ?
Click to expand...
Click to collapse
You shouldn't need a no-verity any longer. Newer versions of magisk should take care of it. Just TWRP, and magisk.

madbat99 said:
You can backup your data in twrp and restore after you format (after first boot). Restore only data though.
Click to expand...
Click to collapse
Hello, I am running a Samsung Galaxy J5 Prime at the moment, a friend told me I must flash no verity.zip after flashing TWRP because of the verification and I tried making a backup if the entire rom but it failed so I need to confirm, do I factory reset my device then flash the no verity file or I flash the no verity file and then factory reset the device??
I know it's an old thread but a quick reply would be awesome

January Images Posted

The January updates are up.

OTA is live too. Just 50.8 MB for 1st Gen XL.

ylapas said:
OTA is live too. Just 50.8 MB for 1st Gen XL.
Click to expand...
Click to collapse
Installing now

ylapas said:
Installing now
Click to expand...
Click to collapse
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.

sb1893 said:
I just flashed January Factory image...standard process as past months. Same platform tools, same TWRP. Magisk v18. ElementalX v4.10. Up and running. Root works fine. Experimenting with BlackenedMod3.0 now. But all seems to be fine on this update so far. Good luck to all.
Click to expand...
Click to collapse
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?

TENN3R said:
TWRP just booted of flashed?
The last update I heard about bootloops when flashing recovery and magisk 18, atm I only boot recovery to avoid any kind of problem. For you works fine?
Click to expand...
Click to collapse
I have always just booted TWRP - I never have flashed it. Sorry for the confusion.

Has anyone been able to root the January update with Magisk?
UPDATE:
I haven't had any boot loop issues after updating, flashing TWRP, and routing with Magisk, so I thought I would post my steps:
Note: My bootloader is unlocked.
Before updating, I flashed the Magisk Uninstaller zip.
Once completed, I rebooted to bootloader and flashed the January factory image (saving data) > booted TWRP > flashed TWRP > rebooted recovery > flashed Magisk 18.0 > rebooted.
I haven't had any boot loop issues.
Magisk is installed and passes Safety Net check, but I wasn't able to grant root privileges for apps right away. It took a while (5 minutes) to get the prompt to grant root privileges. Finally got the prompt and now everything seems to be working correctly.
I hope this helps someone!

Does anyone have the January pre-rooted boot.img?

BoboBrazil said:
Does anyone have the January pre-rooted boot.img?
Click to expand...
Click to collapse
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.

sb1893 said:
Not handy anymore, I deleted the .zip once I updated. But you should be able to grab it from the Factory image .zip readily available on the Google Developers site.
Click to expand...
Click to collapse
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.

^^^
This is a 1st.........never seen anyone ask for it........LoL

BoboBrazil said:
I need it pre-rooted. I'm trying to root someone else's phone for them and would be easier to just be able to flash it than transferring, using magisk manager, then transferring back to flash.
Click to expand...
Click to collapse
Sorry - my mistake - when you said "pre-rooted" I took that to mean "before rooted" - meaning the stock boot.img. Unfortunately, I do not have the Magisk rooted boot.img handy. But, it only takes a few minutes to root using the standard process with Magisk....might be quicker than waiting for a response to your request??? Just a thought...good luck...

crackerjack1957 said:
^^^
This is a 1st.........never seen anyone ask for it........LoL
Click to expand...
Click to collapse
Pretty common on the newer pixel and OnePlus forums. Someone usually shares it to save others some of the work

Update — February 2019

- There are no Pixel security patches in the February 2019 Pixel Update Bulletin.
-Functional patches
All Pixel devices running Android 9 will receive an Android 9 update as part of the February OTA. This quarterly release contains many functional updates and improvements to various parts of the Android platform and
supported Pixel devices.
Now it is installing. I still don't know what is changed. The Update is 111.6MB.
https://source.android.com/security/bulletin/pixel/2019-02-01.html
Security patch levels of 2019-02-05 or later address all issues associated with the 2019-02-05 security patch level and all previous patch levels. To learn how to check a device's security patch level, read the instructions on the Pixel update schedule.

Has anyone had issues updating to FEB then applying Magisk?
Thanks

I'm having issues flashing the factory image without "-w," gives me the "Your device is corrupt and cannot be trusted" screen. Anyone else?
EDIT: flashing the Jan update fixes this and allows my device to boot again

So, I found this little egg by tapping, then pressing on device number. Is this new?

Paint.apk ?

N3V3RS3TTL3 said:
So, I found this little egg by tapping, then pressing on device number. Is this new?
Click to expand...
Click to collapse
Nope, it's been there before.
The only visual change I have noticed on my Pixel 2 XL so far is a slightly different color on the About Phone section in Settings.

N3V3RS3TTL3 said:
Paint.apk ?
Click to expand...
Click to collapse
And where is that? Can we open it someway?
Sent from my Pixel 2 XL using Tapatalk

vagkoun83 said:
And where is that? Can we open it someway?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's the Easter egg:
"The new Easter Egg can be found by going to ‘System’ > ‘About phone’ > ‘Android version’ > and tapping the nine multiple times, then the old P Easter egg will appear on a Pixel 3. If you keep taping the ‘P’ a few more times, the drawing UI appears."

The about phone option is no more in the system section.

docluv01 said:
Has anyone had issues updating to FEB then applying Magisk?
Thanks
Click to expand...
Click to collapse
I had issues with the update in general, but it was my fault. Everything worked out in the end. I think more than a little of it was because of the changes under the hood that Google applied.

Updated perfectly. Downloaded OTA, flashed in TWRP with TWRP zip, reboot to recovery to flash kernel then magisk. No issues whatsoever.
February feels much better, although could just be a placebo ?

I flashed with Duece script at usual. I'm no longer able to fastboot flash TWRP because it just hangs at the initial TWRP screen. Then I have to flash the ota or stock boot.img for the phone to boot. The old process to root doesn't work for me on the February update. I still was able and flash a magical patched stock boot image. So now I'm rooted with no recovery to flash a custom kernel.

mookiexl said:
I flashed with Duece script at usual. I'm no longer able to fastboot flash TWRP because it just hangs at the initial TWRP screen. Then I have to flash the ota or stock boot.img for the phone to boot. The old process to root doesn't work for me on the February update. I still was able and flash a magical patched stock boot image. So now I'm rooted with no recovery to flash a custom kernel.
Click to expand...
Click to collapse
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.

jd1639 said:
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
Click to expand...
Click to collapse
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.

mookiexl said:
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
Click to expand...
Click to collapse
I'm not sure what state your device is in so I'd flash the feb factory image using the flash all batch file with the -w removed. That'll return your device to stock without wiping it. Then fastboot twrp, then install twrp, if you want it, then install magisk.

mookiexl said:
When I fastboot TWRP it hangs at the initial screen and never starts. On January and every other update I've had no issues booting TWRP.
Click to expand...
Click to collapse
USB cables, ports, and platform-tools up to date?

Badger50 said:
USB cables, ports, and platform-tools up to date?
Click to expand...
Click to collapse
Neither of those are the issue because I was able to fastboot flash the magisk patched kernel image. I'm kinda leaning towards TWRP issue. If I go back to January update I can then fastboot flash TWRP . I'm actually shocked no one else is having this issue.

mookiexl said:
Neither of those are the issue because I was able to fastboot flash the magisk patched kernel image. I'm kinda leaning towards TWRP issue. If I go back to January update I can then fastboot flash TWRP . I'm actually shocked no one else is having this issue.
Click to expand...
Click to collapse
Meh...I've had the same twrp file for months, and it's worked with all the updates. But hey, this is the P2XL...so anything's possible :good:

jd1639 said:
Fastboot boot twrp and then once booted install the twrp zip. Get away from doing things thru a tool kit.
Click to expand...
Click to collapse
Not sure if I'd consider Deuces flash script a toolkit per se...

New Rising said:
Not sure if I'd consider Deuces flash script a toolkit per se...
Click to expand...
Click to collapse
It's a toolkit. Toolkits generally simplify processes and hide output that advanced users can use to achieve the same results without the toolkit.

Not booting after Feb security update

Hey, after yesterday's security update, the phone is stuck on powered by android screen. The only thing I can do is go into fastboot. It does not boot into recovery (gets stuck on powered by android screen once again). I don't have an unlocked bootloader, so I cannot really flash directly from fastboot. Any ideas what could be done?

Hi,
I had the same Problem.
When my phone has booted, I could choose between "Start", "Fastboot" and "Recovery". I choose recovery, but everytime it booted to where I can choose between the options. After a few times (5 or so) it booted to TWRP. Then I Flashed Back to the January Update (OTA ZIP-File downloaden from the Essential Website). Then my phone booted normaly to Android.
Maybe if you Don't have TWRP, you can follow the instructions on the Website from Essential.

No issues here but I'm stock and unrooted

I had issues as well. The problem is anytime i try to boot into TWRP when i apply it to the current kernel. Magisk is fine, but TWRP, when applied to the current kernel doesn't seem to load.
1. After feb install, i put TWRP (with jan kernel) in slot B and i was not able to boot to it (it came right back to the fastboot screen). I could boot into A which was the new stock kernal but B was a no-go.
2. I then put the december kernel with twrp into slot b and that did the same thing! i was not able to boot into slot b.
3. Then i put the original TWRP mata file into B and then was now able to boot into twrp.
4. now in TWRP, in slot b, i ran the TWRP installer and it patched slot A and B. Upon reboot, slot a just bootlooped!
4. i then just copied the feb kernel with magisk into A and the phone boots.
5. i now have feb w/magisk on slot a and mata TWRP in slot b. I have not found a way to have twrp working in slot A!
JD

Well, in my case, the phone is fully stock. At this point, I think I am limited to fastboot as it's not booting in recovery. Is there anything that can be done within fastboot without unlocked bootloader?

update on "no booting with feb": i cannot get into twrp at all now. It doesn't matter if i use the original mata twrp kernel or any new or old kernels with TWRP; they all fail and boot to fastboot.
I reflashed jan and now twrp works just fine. Can someone confirm if feb does indeed work with twrp?
Thanks,
JD

Apparently the old version of TWRP isn't compatible with the February OTA update from essential, maybe all the future monthly OTA's as well.. but, a user has created and posted a February img for TWRP compatible with this month's OTA. I think the zip for that February version of TWRP is coming soon as well... Currently running February OTA with the February TWRP image on slot b.. I'm not flashing anything else until the zip for the new TWRP comes out

RoyalOrigin said:
Apparently the old version of TWRP isn't compatible with the February OTA update from essential, maybe all the future monthly OTA's as well.. but, a user has created and posted a February img for TWRP compatible with this month's OTA. I think the zip for that February version of TWRP is coming soon as well... Currently running February OTA with the February TWRP image on slot b.. I'm not flashing anything else until the zip for the new TWRP comes out
Click to expand...
Click to collapse
do you have a link for this twrp compatible with this months ota? i am not able to find it here on xda.
Thanks,
JD

Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs

RimvydasT said:
Is there anything that can be done within fastboot without unlocked bootloader?
Click to expand...
Click to collapse
Don't think so... You definitely can't flash anything with a locked BL.

RoyalOrigin said:
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
https://drive.google.com/file/d/11YtZTqgbDRgws10RpMwIGTSy_X_2A9re/view?usp=drivesdk
I will try that.
Thank you very much.

kt-Froggy said:
Don't think so... You definitely can't flash anything with a locked BL.
Click to expand...
Click to collapse
yeah.. it doesn't look good. I wonder what Essential reps will have to say about their update bricking the phone, but as it's out of warranty, I doubt there will be any positive outcome here.

RoyalOrigin said:
Yes, strange XDA won't let me upload the file.. tried posting the link to the Google drive location and that failed as well, if you go to Reddit and look for the essential thread "Flashed Feb OTA on rooted essential" you will find it in the comments posted by a "briank6932"
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Very nice find! Thank you for posting this information.
JD