Develop Bugs

problems flashing twrp

hello,
I tried to flash twrp to my p605 but when I boot to recovery I get this message " Recovery is not Seandroid Enforcing".
The only solution is to reflash twrp checking autoboot to fix problem. I have tried various versions of twrp. how I could fix this problem?
I am not rooted and I attach some info of my device.
thanks a lot.

any idea please?

Two ways to fix this error
georgew2 said:
any idea please?
Click to expand...
Click to collapse
It is likely you used the wrong TWRP for your Note (LTE version for P605). Be sure to use this xda forum for version and instructions. Sadly I have also made this error on various devices I have owned over the years. lol
https://forum.xda-developers.com/showthread.php?t=2515656
The first method is to boot into recovery and wipe data and reset to factory. The drawback here is you lose (probably) all your data, and it may not work then you have to try the second method anyway.
1: Power off your Samsung Galaxy Note 10.1. Make sure that it's completely turned off, this is the tricky part because of the bootloop. It takes patience and timing.
2: Now press; power, home and volume up to enter the recovery mode
3: Hold the buttons for at least 5 seconds until the android logo appears on the screen
4: The screen will be redirected to the recovery mode of your Samsung Galaxy Note 10.1
Use the volume button to navigate between the options and power button to select the highlighted option.
The second method, especially if that does not work, is to use ODIN to re-flash stock firmware onto your device. That is a process that using search will get you great detailed instructions, much better than I can describe.
Linuxmon
(search is your friend)

thanks for your time to help me. i downlaod twrp files from here: https://twrp.me/devices/samsunggalaxynote1012014qcom.html
I wonder if the new security udpate of february 2017 causes problems of installing twrp.
i will consider if i will try one of these methods.

[RECOVERY][UNOFFICIAL][TWRP] For Sony Xperia T3 D5103 (seagull)

Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone

Cool, although upon booting into recovery the screen isn't operating normally, similar to what happens when flashing the fxp lollipop. Might be because I'm on stock ROM/kernel though.

What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute

EmaMaker said:
What do you mean with "isn't operating normally"? The screen only displays coloured bands? If so, it should have be fixed, maybe only the download link is wrong. Tell me, I'll fix in a minute
Click to expand...
Click to collapse
Yes, sorry for not being more specific xD, I'm indeed getting the white-grey bands on screen.
---------- Post added at 11:25 AM ---------- Previous post was at 11:10 AM ----------
It's possible it's the lollipop kernel that's to blame, since I've had the same problem with other lollipop builds.

Fixed
Download link fixed with working version

EmaMaker said:
Download link fixed with working version
Click to expand...
Click to collapse
Will try it and report back ?

Tried the updated one, still no luck. It could be just my device though.

Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls

EmaMaker said:
Try the one from AFH. I really don't know why. The 3.0.2-1 version works on both my two seagulls
Click to expand...
Click to collapse
Tried both versions, so it's probably my device.
(However, if it is it's fine, since I do have working twrp.)

Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,

Don't know
goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
One of my two seagulls came back from assistance and I tried to flash TWRP on it without any problems. I don't know if it had an updated bootloader or what, but the firmware was stock

goosnarrggh said:
Does this build require an updated bootloader to allow access to the "recovery" partition?
I've got a T3 with a successfully unlocked bootloader, but fastboot gives an error (something about a missing partition table) when I try flashing anything to recovery.
Google tells me that Sony released an updated bootloader some time ago which ought to make a recovery partition available, but I cannot find any active links or instructions for downloading and installing it anywhere,
Click to expand...
Click to collapse
In order to flash recovery, you first need to download and install the Emma flashtool and restore your phone through it. That will add a recovery partition so you can flash twrp. (The Emma flash tool supports only the D5103 model of the T3 as far as I know)

I tink you will have the same as the eagle (m2) device, you need to update your bootloader and then flash recovery...

EmaMaker said:
Hi guys, I decided to start modding this smartphone, now that I have a computer capable of compiling in a few hours.
I ported TWRP 3.0, based on Omni 6.0 source to this device. There are a few things not working and I need other people's help and feedback.
READ FULL GUIDE AND NOTES BEFORE FLASHING!!!
-Necessary steps:
Unlock bootloader. Here's a guide from Sony
-How to install:
1)From computer, open a terminal (Linux and MacOS) or command prompt (Windows) where you saved the file (download below). (Linux And MacOS. On Linux you'll need to flash with sudo) or where you have the platform-tools (Windows)
2)Poweroff your phone.
3)Boot into bootloader by pressing Volume+ button while connecting the usb cable into the usb port (the usb cable has to be inserted into the computer's port too, to successfully boot into fastboot)
4)With unlocked bootloader, type fastboot flash recovery twrp_3.0.2-0-seagull-UNOFFICIAL.img, if you renamed the files, substitube "twrp_3.0.2-0-seagull-UNOFFICIAL.img" with your file name or the directory where you saved the file.
5)When you see the OK message from fastboot, disconnect your phone.
6)Press Power, Volume+ and Volume- untile the phone vibrates.
7)Release Volume+ key. When you see the Sony logo appear, wait 3-4 seconds and then release Power button.
8)You should see TWRP bootscreen after a few seconds
-What's working:
Almost all. I could succesfully flash GApps and Root packages from this recovery, Backup, Restore and Wipe partitions. Settings work fine. Terminal and File manager work.
-What's NOT working:
Can't read files MicroSD or USB-OTG, can't browse in them and can't wipe. Investigating about it.
-Download:
(GDrive) Version 3.0.2-1
(AFH) Version 3.0.2-1
-Source and guide to build:
https://github.com/EmaMaker/device-sony-seagull/tree/twrp-3.0
Changelog:
30/04/2018: I think I fixed the screen problem by using the Lollipop kernel instead of the Marshmellow one
Thanks Everyone
Click to expand...
Click to collapse
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers

Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards

EmaMaker said:
Maybe you can try by holding down the volume down button when rebooting, it may work.
In other case, I think the only option is fixing the button
Best regards
Click to expand...
Click to collapse
Oh, thx for your reply, I didn't expect it really after so many days This method doesn't work, unfortunately. But I won't bother fixing the power button, actually Ive just being using my old Xperia for testing purposes only. But thank you anyway :good:
Regards
Sent from my mido using XDA Labs

Boot loop
Lord Sithek said:
Hi
I'm playing with my old Xperia T3 recently and I was able to unlock bootloader and install your TWRP on my device. I'm able to boot into recovery with the method you described. But since my power buton is in a quite bad condition, I'm looking for another way to boot into twrp. I rooted my Xperia with Magisk and I tried to enter recovery from it, but the phone just rebooted. The same happend when I tried to enter recovery from terminal. What can be the cause? Is there any other reliable way to boot into your twrp?
Cheers
Click to expand...
Click to collapse
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:

sushil lad said:
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
Sorry bro, I don't own this device anymore and I truly don't remember the procedure...
Sent from my SM-T720 using XDA Labs

sushil lad said:
Boot loop
my device is d5102 xperia t3
So i followed these steps as per instructed after unlock boot loader.
i got ok message from fastboot
but now its not booting up
and not even boot into recovery ( i tried to boot into recovery mode as per the steps but each time it just vibrate 3 times and then after 2 seconds again it will vibrates 3 times , i don't get even sony logo or boot screen or error)
device dead ?
completely help less , please help if possible !:crying:
Click to expand...
Click to collapse
same me too

Moto G7 Power xt1955-4 and TWRP 3.5.2_10-0-ocean problem.

Hi, I have Moto G7 Power xt1955-4 with Android 10 Q, unlocked for any GSM carrier, used on T-Mobile network. I unlocked the bootloader and i'm trying to install TWRP recovery image into it. Mostly I follow this guide https://www.androidinfotech.com/root-moto-g7-power-ocean-android-10 . I got the latest available for my phone TWRP -3.5.2-10-ocean from https://dl.twrp.me/ocean/twrp-3.5.2_10-0-ocean.img.html, switched my phone into fastboot mode so it's visible to 'fastboot devices" command, then i run "fastboot boot twrp-3.5.2_10-0-ocean.img" Phone reboots to temporary TWRP now, shows "Enter password for User [0] - ... Data successfully decrypted".
Now, when I try to permanently install TWRP, I got a problem, even though everything looks ok, no error messages: first I installed Disable_Dm-Verity_ForceEncrypt.zip file, with Success. Then I installed twrp-installer-3.5.2_10-0-ocean.zip via TWRP itself: it shows "######## TWRP installer for A/B devices ######## Running image patcher on boot_a... Running image patcher on boot_b... Image patcher complete! Done installing TWRP ***Note: You are now unrooted!*** Updating partition details... Success!" - note no errors here.
BUT when I reboot into recovery mode again, I see only TWRP logo, then phone beeps for 1 sec, and nothing happens after that, no menu shows up, no prompt to "Enter password for user" as before. No response from screen touches. Only reboot helps.
So I understand that TWRP was not installed correctly. What did I do wrong?
Any suggestions will be appreciated.

You should join and follow the G7P (Ocean) telegram group if you haven't already done so. Any questions can be asked there or are already answered in the #notes section. As far as twrp goes because the device is a/b type I never install the zip. I connect to pc and fast boot twrp image to flash ROMs.

Skippy12359 said:
You should join and follow the G7P (Ocean) telegram group if you haven't already done so. Any questions can be asked there or are already answered in the #notes section. As far as twrp goes because the device is a/b type I never install the zip. I connect to pc and fast boot twrp image to flash ROMs.
Click to expand...
Click to collapse
Thank you Skippy12359, I found just "Moto G7 Power Ocean/River Channel" on Telegram, with 10 subscribers - is it the one you mentioned?
My goal is to install Magisk-v23 on my phone, to complete rooting procedure. I was going to use TWRP for this, and install it via zip file. But if I use temporary TWRP and just install Magisk-v23.0_renamed_apk.zip, after reboot Magisk app shows "Installed" status as N/A! Apparently it doesn't work as intended... So I thought that permanently installed TWRP would give better result.
UPD: Also I see "Moto G⁷ Power | Builds™" channel with 445 subscribers, and "Moto G⁷ Power | Discussion™" with 379 members. Signed up for those!

There's a Moto g7 power discussion group and a Moto g7 power builds group. If you're new to flashing ROMs put all your ROMs, magisk, gapp files on your sdcard. Then fastboot twrp and flash ROMs, magisk from there. You can install the twrp zip if you want just found it easier not to because it gets overwritten anyway because the device has no separate partition for recovery like an A- only has for example.

Actually this method (fastboot to temporary TWRP, then install magisk.zip file from sd card) works! I was able to install Magisk this way, and first time it boots normally, Magisk shows Install status v23, CheckRoot app shows that everything is ok. But on second reboot i'm getting into bootloop After Warning message and 5 sec wait my phone beeps and reboots.

Magisk has an uninstall zip file if you have boot problems. Once magisk is uninstalled from recovery it should boot up fine. There is also a magisk canary version on github which should fix any boot issues after flashing. You need both the magisk zip and the magisk app installed to have full root

I try Magisk-Canary (after uninstalling Magisk v23 by renaming zip file to uninstall.zip and run it via TWRP) from https://github.com/topjohnwu/Magisk, the result is the same- first boot is Ok, Magisk app shows that it's installed (Magisk status 5d6d2417 (23015) version installed), but second boot gives me bootloop...

What ROM are you using?

I use Original stock ROM, that comes with the phone. XT1955-4_OCEAN_RETEU_10_QPOS30.52-29-7-6_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip file from ttps://mirrors.lolinet.com/firmware/moto/ocean/official/RETEU ( i just found it to get boot.img and patch it with Magisk, I didn't change original firmware , just unlocked bootloader.

I haven't used stock for over a year and I don't recall having any problems rooting or ever had a boot loop on rooted stock Q. Also I've never needed to patch a boot image to get root. I just reflashed stock firmware, installed all the apps I wanted and fast boot to recovery. Flash copy partitions zip and then flash Magisk. After reboot to system I install Magisk app and I'm done. Always worked for me. Rooted and no reboots.

I assume that you have Moto xt1955-4, correct? Which ROM you have installed then? At the time of Magisk installation , was it custom ROM or original stock ROM on your phone?

I have the usa model of the same phone xt1955-5 and have always had it rooted whatever custom ROM or stock firmware used at the time. I'm currently on AICP 11 official custom ROM but switch frequently from Arrow, Colt and other ROMs.

Skippy12359 said:
I have the usa model of the same phone xt1955-5 and have always had it rooted whatever custom ROM or stock firmware used at the time. I'm currently on AICP 11 official custom ROM but switch frequently from Arrow, Colt and other ROMs.
Click to expand...
Click to collapse
Hey Skippy, When I originally got the phone, I bought it outright from Cricket. A Supra, but still the same as G7 Power.. No payments. No years agreements. Now that it is no longer supported, I want to unlock the bootloader and install a custom rom. Setup ADB and went to Motorola's website for the unlock code. I get "Does not qualify for unlocking." For the above two reasons, I'm a bit miffed. Has anyone found a work-a-round for this? I got up at 6 AM. All day studying and learning how to do this. Only to get the message. "No you can't. Sorry. Notta". And with Motorola's piss poor support policy, it grinds my gears.

Danny3568 said:
Hey Skippy, When I originally got the phone, I bought it outright from Cricket. A Supra, but still the same as G7 Power.. No payments. No years agreements. Now that it is no longer supported, I want to unlock the bootloader and install a custom rom. Setup ADB and went to Motorola's website for the unlock code. I get "Does not qualify for unlocking." For the above two reasons, I'm a bit miffed. Has anyone found a work-a-round for this? I got up at 6 AM. All day studying and learning how to do this. Only to get the message. "No you can't. Sorry. Notta". And with Motorola's piss poor support policy, it grinds my gears.
Click to expand...
Click to collapse
I have the TMobile variant codenamed Ocean, so I'm not going to be much help on your question. I suggest you ask in the Moto g7 power discussion group on telegram. I'm sure someone there can let you know if the cricket variant is unlockable or not. Good luck

Skippy12359 said:
I have the TMobile variant codenamed Ocean, so I'm not going to be much help on your question. I suggest you ask in the Moto g7 power discussion group on telegram. I'm sure someone there can let you know if the cricket variant is unlockable or not. Good luck
Click to expand...
Click to collapse
Thanks for the quick response! I don't use Telegram, but I guess I better get signed up. I wish there was a repository of, an HCL of sorts, where people can refer to before buying phones to avoid these issues.

Question locked on bootloader after LineageOS install

EDIT: it's my fault for updating to Android 12. I managed to miss the giant warning on top of the LOS guide. sorry everyone.
LE2125-11 is the model
followed both pinned unlock guide and LineageOS official install guide applying latest packages (february), verifyed checksums, strictly obeyed everything and didn't skip any step (only add-ons were skipped).
after install, phone will always boot on bootloader, powering off and pressing other key combo (volumes + power etc) still lead to bootloader at the end, and after turning it off, it will restarts itself into bootloader! all without manual intervention. after unlocking bootloader i could boot perfectly to normal OS and allow usb debugging + confirming bootloader was unlocked.
the pc steps were done on Arch Linux. and if i press start, before going bootloader it shows a brief, thin white line

You can always go full stock using MSM Tools: https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/

_MartyMan_ said:
You can always go full stock using MSM Tools: https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
Click to expand...
Click to collapse
i prefer LineageOS over anything. thanks though, because now i have a last resort if i cant get the phone to boot LOS

glowyemmanuel said:
i prefer LineageOS over anything. thanks though, because now i have a last resort if i cant get the phone to boot LOS
Click to expand...
Click to collapse
After MSM, you can reflash Lineage then problem solved

S10e - impossibility to install Lineage OS

I need to install Lineage OS on this phone.
After multiple tries several months apart, I am still not in success.
Followed all internet tutorials and sites.
I don't want to install any G apps or any special root-things like magdisk..
I only want pure Lineage OS without any extra applications.
Way I tried and probably ended up like before:
Get newest official samsung ROM installed, update, enable usb debigging and oem, go download mode and go factory reset, get back in, sign in to wifi again, again enable develop. settings and usb debugging, go into download mode, take odin and install through the AP option the TWRP now that the phone is in download mode a 3rd time, supposed to be possible now with OEM unlock.
Most of the names on the way I don't understand, just follow tutorials.
I need to get to TWRP to then finally, as used to always, install Lineage from zip.
But I never get rebooted into TWRP recovery, just forver the samsung one, even when firmware is no longer there - after flashing in ap option the twrp tar again it never boots into TWRP afterwards.
Is there something else i must do? is not getting into oem unlock and flashing TWRP enough to get there?
And after, will the zip install finaly get me to have lineage installed?

Did you try the official guide?
https://wiki.lineageos.org/devices/beyond0lte/
I hope I picked the right phones, otherwise check devices overview.
Alternatively, perhaps this helps:
https://forum.xda-developers.com/t/...-a-graphical-installer-for-lineageos.4509995/
PS: Usually LOS doesn't do TWRP anymore but comes with its own recovery (a/b)

Why they don't do TWRP now?
I saw TWRP tuorial fot s10 on tutorials and it worked
Do I have to give up on TWRP way and od it with the adb commands from PC

frustrateduser118 said:
Why
Click to expand...
Click to collapse
It's because of this new double recovery scheme:
https://forum.xda-developers.com/t/help-understanding-a-b-partitions.3748003/post-75545902
https://source.android.com/docs/core/ota/ab
https://www.xda-developers.com/how-...ess-updates-affect-custom-development-on-xda/
EOD: It's safer, updating happens in the background, then just a quick reboot et voila.
frustrateduser118 said:
I saw TWRP tuorial
Click to expand...
Click to collapse
Yes, it's still there but perhaps you post a link to your guide (or ask there). To me it seems you had TWRP just in your RAM but not your phone?
As for me, I finally gave up on TWRP and use the "crappy" LOS recovery Have way more important things to waste my time on...
PS: Sorry to bring such "bad" news, wasn't too happy with that change myself

Great, I finaly made it work.
I followed the site with turotial on installation and did not try TWRP
First I had to install samsung ROM again
It turned out to still stay unlocked so went straight to download mode and this time flashed Lineage recovery sucesfuly with heimdall
Then it booted up and a half samsung sreen made it seem like there is trouble
but Lineage recovery launched
The adb load from PC did not work so i chose to instal zip from SD even there
Now Lineage is installed
Still don't know how much is randomness, luck and so on
But it's done and hopefuly repeatable

frustrateduser118 said:
hopefuly repeatable
Click to expand...
Click to collapse
I am afraid it is
Well, most of times: Far too often I forget some little prerequisite, too... so started a little text file with steps/reminders.

anyway glad for support sigmund
you re my friend now