Database Develop

Stuck in boot up screen

ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks

JWACK72 said:
ok, i am stuck on my boot up screen. i flashed a zip file xposed arm zip. after the reboot it will not pass the boot animation screen. now on my old Motorola phone, i would do the pwr + vol keys to boot back in to recovery. well this does no work on my X. any one have any ideas. I am rooted, unlocked, twrp was installed from play store, & i did do a back up. thanks
Click to expand...
Click to collapse
What device do you have, XT1095, XT1097, etc? And you are not able to boot into the bootloader using vol down + power correct?

It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP

JWACK72 said:
It was a 1096, now its trash. it would go into fastboot, but could not get into twrp recovery. its done. RIP
Click to expand...
Click to collapse
If it boots to fastboot, it's not dead. Just reflash the recovery and you're good to go.
Sent from my XT1095 using Tapatalk

Was there a resolution for this? I'm having a similar problem. I'm not sure how I got to this status, but here's what I'm dealing with:
Device: XT1095
Bootloader: Unlocked
Rooted, ROM - Resurrection Remix, TWRP
Turning on the phone reaches the RR bootsplash and proceeds to bootloop.
When holding down the power and volume down, it will enter fastboot.
When I try to open TWRP recovery, it'll show the blue TWRP screen and just sit there.
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks

bibbin said:
I have tried to reinstall TWRP, but that has no effect. I didn't want to manually flash another ROM or go back to stock because at least now it seems USB debugging is on and if I flashed a ROM I cant be sure I'd be able to turn it on. Do any of you pros have some ideas hove I can get back into my phone? Thanks
Click to expand...
Click to collapse
Do you have a USB-OTG device plugged in while trying to start TWRP? If so remove it, you can mount it after TWRP starts if this helps.
Have you tried a different build of TWRP? I'm currently using the one built by invisiblek, one of the CM devs for the victara. It was built and posted on December 8th and is here: http://www.invisiblek.org/twrp/twrp_2.8.7.0-0624b8bd_victara.img
Have you tried flashing the stock recovery to see if that will start? If it does, you could use the factory reset option there and then try reinstalling TWRP. (TWRP has a settings directory in /sdcard and maybe that is corrupted.)
There have been a few people posting with this problem but I've not seen a definitive fix for it.

Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.

bibbin said:
Thank for the quick response. No, I don't have USB-OTG inserted. It is using TWRP 2.8.7.1. No, I haven't tried installing the version you mentioned. What I did do was attempt to flash the pre-installed TWRP 2.8.1.0 via MOTO X TOOLKIT. It failed. I'm not very experienced at using ADB manually. As I mentioned, I've been reluctant to flash another ROM (custom or stock) because I don't want to get stuck with USB debugging inactive with no way to get in far enough to reactivate it.
---------- Post added at 04:32 PM ---------- Previous post was at 03:40 PM ----------
If I manage to install the invisiblek TWRP and it opens properly will I then be able to restore the backups created with TWRP 2.8.7.1?
If that's the case, I need to find a tutorial on installing TWRP manually via ADB, right? I usually install TWRP via TWRP Manager.
Click to expand...
Click to collapse
That's interesting, the TWRP Manager has never worked correctly for me although it's been a long time since I've tried it.
To flash manually, you actually need fastboot which is usually installed along with adb. If you open a command window, and type in fastboot and it runs, the rest is pretty easy. If it doesn't run, this thread has the 15 second ADB/Fastboot installer, select to install it system-wide: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Download the recovery image, rename the file to twrp.img, then open a command window in the folder where you downloaded it (type cmd then Enter in the address line at the top of the folder window.)
When the command window is open and the phone is in bootloader mode and connected to the computer with the USB cable, enter the command "fastboot device" (without the quotes) If everything is working it will list the serial number of your phone.
Then enter "fastboot flash recovery twrp.img" (without the quotes) to start the flashing process, ignore the size mismatch message. It will only take a few seconds to complete.
Use the volume down key to highlight recovery, then volume up to select it. Hopefully TWRP will boot up and you'll be good to go!

Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?

bibbin said:
Well, reinstalling TWRP didn't fix it. Thoughts? Anyone?
Click to expand...
Click to collapse
Reflash stock rom from fastboot.
Sent from my XT1095 using Tapatalk

UPDATE: Thanks all. Well, after fiddling around with various methods of reinstalling TWRP, I managed to get it reinstalled and all is back to normal now.

[SOLVED] Stuck in "warning bootloader unlocked" screen. Device won't turn OFF.

[SOLVED] Stuck in "warning bootloader unlocked" screen. Device won't turn OFF.
Hi all,
I have a Moto G 2014 (Titan, XT1068).
I am not new to custom ROM-ing and Android hacking, had all 4 of my personal Android phones unlocked and rooted just fine - I usually know what I'm doing.
This here is my mom's phone and it's the first Moto G 2014 I attempted to unlock & root so far. I know the basics, but this particular device gives me headache...
All actions were performed on 07. October 2016 after carefully researching the latest HOW-TOs for the Moto G 2014 on XDA and other websites:
- I unlocked the bootloader using the official process from Motorola to receive the "unique key".
- I installed twrp-3.0.2-3-titan.img recovery.
- I downloaded SR1-SuperSU-v2.78-SR1-20160915123031.zip and placed it on storage.
- I booted into TWRP recovery, installed SuperSU and Wiped Dalvik+Cache, then rebooted.
Since then, I am stuck in the "warning bootloader unlocked" (WBU) screen and the device won't turn off.
If I press the power button and hold it for a few seconds, normally it turned the device off, but now it just reboots into the WBU screen, looping forever.
- I can still enter my fastboot by holding VOL-down + Power, get a adb connection with my Android SDK + platform tools on my Windows and issue adb and fastboot commands normally.
- I can still enter the recovery and do stuff with it normally.
Since this incident, I have also tried a normal Wipe (whatever the default wipe settings are) in TWRP, no change / effect.
I have no clue what to do next, other than wait for the battery to go empty that is, since I can't even turn the device off.
Some methodologically sound advice would be highly appreciated at this point. :good:
Thank you in advance.

You just can't flash the supersu file in twrp before flashing the supersu you need to flash roo.M.br.zip file in fastboot mode then you can flash the SuperSU.
The file available at stock firmware section.
---------- Post added at 09:48 AM ---------- Previous post was at 09:46 AM ----------
Flash the stock rom from fastboot mode then again root the device as i said it will solve the problem.

Prasourabha said:
You just can't flash the supersu file in twrp before flashing the supersu you need to flash roo.M.br.zip file in fastboot mode then you can flash the SuperSU.
The file available at stock firmware section.
---------- Post added at 09:48 AM ---------- Previous post was at 09:46 AM ----------
Flash the stock rom from fastboot mode then again root the device as i said it will solve the problem.
Click to expand...
Click to collapse
Is this roo.M.br.zip file included in the Stock Rom or is it the Stock Rom itself?
Or is there another general name for this roo.M.br.zip? Because I can't find it via the search function of the forum.
Anyhow ... in the meantime I will be downloading XT1068_TITAN_RETAILDSDS_5.0.2_LXB22.99-16.3_Easy_Installer.zip which is linked on the following thread:
- http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
- first URL for XT1068 labeled as "***NEW*** DOWNLOAD XT1068 5.0.2 LXB22.99-16.3 RETDSDS WITH STAGE FRIGHT FIX RETAIL DUAL SIM DUAL STANDBY (EU/INDIAN/GLOBAL) 26/08/2015 BUILD ***NEW***"
But I already had a look into the archive, nowhere to find a roo.M.br.zip is even similarly named file(s).
Could you be a little more specific or provide the correct XDA thread / link?
Also, the fact that "I can't just flash SU" it must be device specific, right?
Because on my other Android phones I just installed/flashed SU via recovery mod with no problems and that was it.
EDIT: also, according to this guide here, apparently you "can just install SU", if I understand correctly and it's more or less exactly how I proceeded (unless wiping cache/dalvik after flash was harmful):
- http://forum.xda-developers.com/moto-g-2014/general/guide-root-moto-g-2nd-gen-2014-t2874245

Here is the link of the page where yiu can find the file and the rooting guide
http://forum.xda-developers.com/moto-g-2014/general/root-root-moto-g-2014-android-t3255711

Prasourabha said:
Here is the link of the page where yiu can find the file and the rooting guide
http://forum.xda-developers.com/moto-g-2014/general/root-root-moto-g-2014-android-t3255711
Click to expand...
Click to collapse
Sorry for not understanding your answer at first.
Obviously you were refering to two different things in one post and I was a little confused.
- RESTORING THE STOCK-ROM BASED ON MARSHMALLOW / ANDROID 6.0 HAS BROKEN THE BOOTLOOP IN THE UNLOCKED BOOTLOADER WARNING.
The other issue was obviously that you catched what I wanted to do originally, which was to ROOT the device.
- DOWNLOADING AND FLASHING THIS "root-titan-M-BR.zip" IN THE THREAD YOU SPECIFIED ENABLED ME TO FLASH SUPERSU AFTERWARDS WITHOUT PROBLEMS.
Obviously I can now go on doing what I initially intended, which is installing CM13 on my mom's phone.
I almost thought I had bricked the phone for good.
Thank you for your support. :good:

TWRP 3.2.3-1 for Pixel 3 XL

ADB does not work! On the Pixel 3XL, TWRP takes a while to boot up. Be patient, it will boot!
Note, I don't own a Pixel 3 XL, just the regular Pixel 3 (blueline). I personally won't be able to fix ADB. If you have some talent with init scripts and fixing ADB, feel free to work on it and submit a patch.
MTP does not work in TWRP on the Pixel 3 and will not work until we have time to update the TWRP MTP implementation. You will either have to transfer files while in Android or use a USB OTG cable and a thumb drive.
Pixel devices have 2 "slots" for ROMs / firmware. TWRP will detect whichever slot is currently active and use that slot for backup AND restore. There are buttons on the reboot page and under backup -> options to change slots. Changing the active slot will cause TWRP to switch which slot that TWRP is backing up or restoring. You can make a backup of slot A, switch to B, then restore the backup which will restore the backup of A to slot B. Changing the slot in TWRP also tells the bootloader to boot that slot.
The zip install method installs TWRP to both slots.
Installation:
If you already have TWRP installed: Download the latest zip and install the zip using TWRP.
If you do not already have TWRP installed: Download both the img and the zip. Copy the zip to your device. You will need to have fastboot binaries and the correct drivers installed. Power off your device completely. Hold volume down and turn on the device. Your device should now be in the bootloader. Connect the device to your PC. Open a command window and run the following command from the proper location:
fastboot boot path/to/twrp.img
This will temporarily boot TWRP on your device. If you are using a lockscreen pin/pattern/password and do not get prompted to enter your passord, reboot to the bootloader and try again. Go to install and browse to the zip and install the zip. If you are currently rooted, you will need to reflash the stock boot image before installing TWRP. After installing the stock boot image, follow the instructions for installing TWRP. Once TWRP is installed, you will need to reflash root.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
3.2.3-0: Initial release for the Pixel 3 devices
3.2.3-1: Fix touch when TWRP is installed on the 3 XL
Pixel 3:
https://twrp.me/google/googlepixel3.html
https://dl.twrp.me/blueline/
Pixel 3 XL:
https://twrp.me/google/googlepixel3xl.html
https://dl.twrp.me/crosshatch/

Reserved!

Thank you. [emoji5]
Sent from my Pixel 3 XL using Tapatalk

Thank you so much so appreciated what you do brotha. Grateful
Sent from my Pixel 3 XL using Tapatalk

hello, after flash twrp, bootloader enter reason shows "combo key", and cant enter nomal OS. How to solve it?

jiao322528 said:
hello, after flash twrp, bootloader enter reason shows "combo key", and cant enter nomal OS. How to solve it?
Click to expand...
Click to collapse
Did you flash it? The instructions say specifically to not flash TWRP using fastboot.
If you accidently flash TWRP to your device using fastboot instead of temporarily booting the image, you will need to download the latest factory image for your device and reflash the boot image.
Click to expand...
Click to collapse
You need to fastboot boot twrp.img, then use the twrp_installer.zip INSIDE TWRP to install correctly.
If you can't boot, flash the stock boot.img to boot_a and boot_b and you should be back to normal.
---------- Post added at 12:11 AM ---------- Previous post was at 12:05 AM ----------
I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.
This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.
Others having this issue?

Yup. You have to wait for a modified boot.img/kernel I totally forgot about that
PewPewK said:
Did you flash it? The instructions say specifically to not flash TWRP using fastboot.
You need to fastboot boot twrp.img, then use the twrp_installer.zip INSIDE TWRP to install correctly.
If you can't boot, flash the stock boot.img to boot_a and boot_b and you should be back to normal.
---------- Post added at 12:11 AM ---------- Previous post was at 12:05 AM ----------
I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.
This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.
Others having this issue?
Click to expand...
Click to collapse
Sent from my Pixel 3 XL using Tapatalk

PewPewK said:
Did you flash it? The instructions say specifically to not flash TWRP using fastboot.
You need to fastboot boot twrp.img, then use the twrp_installer.zip INSIDE TWRP to install correctly.
If you can't boot, flash the stock boot.img to boot_a and boot_b and you should be back to normal.
---------- Post added at 12:11 AM ---------- Previous post was at 12:05 AM ----------
I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.
This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.
Others having this issue?
Click to expand...
Click to collapse
It was partition issues. I changed boot a to b, of course it is black...now everything is ok, but same problem as yours. Thank god!

PewPewK said:
Did you flash it? The instructions say specifically to not flash TWRP using fastboot.
Click to expand...
Click to collapse
Where? I think you mean ADB. How else are you going to flash it?
edit: I see what you mean. Boot, then flash with the booted TWRP. NEVER MIND...CARRY ON.
---------- Post added at 07:42 AM ---------- Previous post was at 07:27 AM ----------
I installed TWRP successfully and was able to boot into it, but it appears the touch screen is unresponsive when I do this? I can turn the screen on and off, and TWRP will show the lock symbol and decrypt screen, but it's completely unresponsive to touch inputs.
This does NOT happen when I use `fastboot boot twrp.img` only when I used the installed TWRP.
Others having this issue?
Click to expand...
Click to collapse
Yup. Same problem. This also happened on the P2/P2xl. You needed to flash a custom kernel as well. We'll have to wait for that. Until then, do all of your flashing during the "booted" TWRP.
edit: so yeah, pretty much what @freddienuxx said. I'm not having a good morning guys.

It's seems everything is working properly on the Pixel 3 but not the 3 XL.

non responsive touch on p3xl 128gb
bootable working fine

If I recall the pixel 2 XL was the same if you were on stock kernel but touch was fine with a custom kernel. At least we can put magisk on

A start in the right direction. Thanks Dees_Troy!

Reuben_skelz92 said:
If I recall the pixel 2 XL was the same if you were on stock kernel but touch was fine with a custom kernel. At least we can put magisk on
Click to expand...
Click to collapse
i flashed magisk 17.3 in TWRP but now when i set a pin it says incorrect pin when i try to unlock (but still unlocks the phone) and it also wont let me use a fingerprint.
given i have decrypted... i cant even add a finger print to unlock.

Reuben_skelz92 said:
If I recall the pixel 2 XL was the same if you were on stock kernel but touch was fine with a custom kernel. At least we can put magisk on
Click to expand...
Click to collapse
You can have Magisk without TWRP.

virtyx said:
non responsive touch on p3xl 128gb
bootable working fine
Click to expand...
Click to collapse
same here

Nice work (and just in time, lol) @Dees_Troy
I'm "supposed" to get my Pixel 3 XL on Monday. I'll be happy to work with you after I get settled in, if someone else hasn't joined your party before then :good:

No Touch here either
Is this a widespread issue or is it just a few of us?
Sent from my Pixel 3 XL using Tapatalk

I also have no touch on 3XL 128gb. TWRP works fine when I boot it through fastboot but after I install it (and reboot) the touch stops working.

superchilpil said:
No Touch here either
Is this a widespread issue or is it just a few of us?
Click to expand...
Click to collapse
Ariel_PR said:
I also have no touch on 3XL 128gb. TWRP works fine when I boot it through fastboot but after I install it (and reboot) the touch stops working.[/QUOTE
It will be that way until custom kernels come around. It was the same way for pixel 2.
Click to expand...
Click to collapse

TWRP reverts back to MI Recovery 3.0 every single time

So, I have a Global version Mi 9.
Since the Global Beta is now gone, I want to use Xiaomi.eu ROM.
I unlocked bootloader, I flash TWRP, then I even flash the Disable Force Encryption, but every single time I reboot, the recovery reverts back to MI Recovery 3.0.
What am I doing wrong ?

AFAIK, MIUI installs her own recovery after a reboot.

I always download ROM and enter TWRP to flash ROM !
Currently speaking, MI9 TWRP without the other TWRP mod, such as OrangeFox to ensure TWRP won't be replaced by Mi recovery after OTA updated.
I see a magisk app - "TWRP A/B Retention script" may be current solution to help you keep TWRP after OTA but it must be flashed again after OTA updated every time.
Ataemonus said:
So, I have a Global version Mi 9.
Since the Global Beta is now gone, I want to use Xiaomi.eu ROM.
I unlocked bootloader, I flash TWRP, then I even flash the Disable Force Encryption, but every single time I reboot, the recovery reverts back to MI Recovery 3.0.
What am I doing wrong ?
Click to expand...
Click to collapse

You do not understand.
TWRP is NOT replaced after OTA, it is replaced after rebooting, immediately, after flashing it, before I can even upload the .zip file with the custom ROM to install it.

Ataemonus said:
You do not understand.
TWRP is NOT replaced after OTA, it is replaced after rebooting, immediately, after flashing it, before I can even upload the .zip file with the custom ROM to install it.
Click to expand...
Click to collapse
After flashing twrp, are you using fastboot boot twrp? If so, you need instead to use buttons, not the fastboot commands. Flash twrp, then hold vol up and power together until the phone reboots and vibrates, then let go of power but keep holding vol up. That should make twrp stick

reg66 said:
After flashing twrp, are you using fastboot boot twrp? If so, you need instead to use buttons, not the fastboot commands. Flash twrp, then hold vol up and power together until the phone reboots and vibrates, then let go of power but keep holding vol up. That should make twrp stick
Click to expand...
Click to collapse
Exactly.
1) Boot into fastboot
2) fastboot flash recovery twrp.img
3) fastboot reboot (immediately after device reboot, in black screen, hold VOL+ button)
4) TWRP logo will appears

Yes, I can boot to TWRP, but one time only. I use the volume up button after flashing to enter TWRP.
I need to format the data partition, before I upload the .zip file, and after I format the data partition and I reboot the phone, no more TWRP, MI Recovery 3.0 again.
In the end, I managed to install the xiaomi.eu ROM, but only by pushing the file into the tmp folder and not rebooting after I format the data partition.
Strange how MIUI enforces their own recovery software over TWRP, I had no such issues with the Mi 6, two years ago.

Ataemonus said:
Yes, I can boot to TWRP, but one time only. I use the volume up button after flashing to enter TWRP.
I need to format the data partition, before I upload the .zip file, and after I format the data partition and I reboot the phone, no more TWRP, MI Recovery 3.0 again.
In the end, I managed to install the xiaomi.eu ROM, but only by pushing the file into the tmp folder and not rebooting after I format the data partition.
Strange how MIUI enforces their own recovery software over TWRP, I had no such issues with the Mi 6, two years ago.
Click to expand...
Click to collapse
Which twrp you using?

I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825

Ataemonus said:
I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
Click to expand...
Click to collapse
Yep, that one should deffo be fine, not sure why it's not sticking and you're having the issues, sorry bud

As I said, sorted in the end, now on Xiaomi.eu 9.8.1.
Must have been the latest MIUI beta 9.6.27 that was so ... aggressive with the recovery software

Ataemonus said:
I tried pretty much all I could find, but settled on 3.3.0-35 from here : https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825
Click to expand...
Click to collapse
Install twrp twice in fastboot

having a similar problem, can't install TWRP, the fastboot flash works, no errors, but when I log in ON+VOL UP it comes always MI recovery

claudioita said:
having a similar problem, can't install TWRP, the fastboot flash works, no errors, but when I log in ON+VOL UP it comes always MI recovery
Click to expand...
Click to collapse
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.

sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
You used twrp for Mi9TPRO or mi 9?
Is your link correct?

claudioita said:
You used twrp for Mi9TPRO or mi 9?
Is your link correct?
Click to expand...
Click to collapse
I am using a Mi 9 (Cepheus), and the TWRP that I am using is from Mauronofrio, version 3.3.1-52. The post to that TWRP is here.

sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
no it does not work
---------- Post added at 09:15 PM ---------- Previous post was at 08:46 PM ----------
sangbuana said:
Try this.
- Reboot to fastboot
- Flash TWRP
- Disconnect USB cable
- Press and hold Vol+ and power button until TWRP boots
I followed the guide posted here.
Click to expand...
Click to collapse
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?

Bit late so not sure if the issue is still prevalent, but did you try flashing TWRP from within TWRP itself?
That's what I did, flashing TWRP within fastboot, then rebooting to enter TWRP (I use buttons for this), then moving the TWRP img to internal storage and use the install function within TWRP to flash the image.

[RECOVERY][UNOFFICIAL][ROOT] TWRP for Galaxy A70

Team Win Recovery Project 3.x, or TWRP3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
[I]#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this recovery
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/[/I]
I’d recommend to read everything in this post, if you care about your expensive phone.
Let’s start with the installation process
If you already unlocked your bootloader, start with step 3.
If you are already rooted, start with step 4.
If you already installed a previous version of TWRP, start with step 4.
If you already have TWRP installed and just want to root, start with step 5.
First you need to unlock your bootloader. You can do so by enabling developer settings first, enable oem unlocking, then shut down your phone, hold volume up and down at the same time and while holding them plugin your charger. Your phone now should show a green screen with instructions to unlock the bootloader. Just follow them and after the unlocking your data should get wiped. After that your device will boot up and land in setup screen. Do not setup anything, just skip as much as possible, because your phone will get wiped again. Enable developer settings and make sure oem unlocking is greyed out and enabled. (If it does not show up, connect to a network first!)
Now you need to overwrite vbmeta partition, so you can flash third party partitions. Download vbmeta.tar then go into download mode on your device. Put vbmeta.tar to AP in Odin, click start. This should finish pretty quickly, so pay attention when your device reboots, because you need to boot into recovery (Hold power and volume up after the screen turns black). When booted into recovery, wipe your data and reboot normally into system. Now you can setup your phone as usual and make sure oem unlocking is still greyed out and enabled!
Time to flash recovery. Download (link is at the end of this post) the latest version as zip and extract it. You should end up with one single file named recovery.img. Pack it as tar with 7zip or any other compression tool you prefer. This packed tar file should only contain recovery.img and nothing else, also make sure the name is still recovery.img, otherwise Odin will refuse to flash it. In Odin put the tar file in AP and simply hit start. Congrats you now have TWRP installed!
(Optional) You might have lost root access by flash TWRP if you followed this standard guide for rooting. If you did lose it and want to gain root access again (you can also root your device with this method, even when you never rooted your device), download the latest Magisk Manager from the canary channel and install the apk to your phone.
If you are on stock:
Push the recovery.img file you just download for TWRP to your phone. Open Magisk Manager and hit install and patch a file. Select recovery.img and Magisk should start the patching process. Once Magisk is done, boot into TWRP. Backup your boot partition first and afterwards go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
If you are on an AOSP based rom:
Reboot to TWRP. Create a backup with boot partition. Reboot back to system, then open Magisk and hit install and patch a file. Locate the TWRP backup folder and look up your backup you just created. Select boot.emmc.win for patching. Once Magisk is done, reboot back to TWRP. Go into install and then hit install image on the bottom right of the screen. Select /sdcard/Download/magisk_patched.img and install it to boot. Now reboot and Magisk should work. If you run into issues after this, go into TWRP and restore the boot partition you backed up previously.
So that was the easy part. The hard part is to completely read these following points!
Encryption/Decryption
Decryption works on this TWRP release, but only partially. That means you have to open the Settings Application first on your phone and disable a feature called strong protection. You can find it in Settings->Biometrics and security>Other security settings. It doesn’t matter when you disable it. Flash TWRP first and disable it, fine. Disable it and flash TWRP afterwards, fine. Never disable it, also fine, TWRP just fails to decrypt your data, but won’t do any harm. When this feature gets turned off, the device will generate a key which doesn't require any authentication for decryption, currently only this allows TWRP to decrypt the data partition successfully. This only applies to stock roms though, if you are using an AOSP based rom, then you don't have to do any of this.
Disabling decryption
Disabling decryption will create many problems. First TWRP will refuse to unmount system partition and thus you might run into problems flashing various zips. So I advise you to not disable decryption. If you still want to disable it you have to open terminal in TWRP and type in "stop servicemanager" everytime you want to unmount the system partition.
Backup and Restore
Because of encryption it's more complicated to backup your data partition.
If you want to backup data you have to make sure TWRP successfully decrypted your internal storage, otherwise you will run into problems backing up.
Restoring is even more complicated. Every time you set up a rom, new crypto keys will be generated and you can't backup these. That means if you want to restore data you have to restore the whole rom first excluding data. Format data partition completely, boot it up, then go back to TWRP and restore data. You will lose your internal storage, so I'd recommend you move important stuff to external storage.
Developers specific details
Sources
https://github.com/Grarak/android_device_samsung_a70q-twrp
https://github.com/Grarak/android_device_samsung_a70q
https://github.com/Grarak/android_bootable_recovery-1
Recovery image size
For some reason the ramdisk has a size limit, so I used LZMA compression to get its size down as much as possible.
During kernel compilation you will run into a DTC error. Apparently Samsung didn’t bother to update their DTC source in the kernel and you have to use their precompiled binary. I edited my kernel sources to automatically use their dtc binary.
Credits
Device tree of Redmi Note 7 Pro (https://github.com/TeamWin/android_device_xiaomi_violet). Helped a lot!
Topjohnwu for the detailed installation guide (https://topjohnwu.github.io/Magisk/install.html#samsung-system-as-root)
TWRP Galaxy S10 thread for describing System-as-root pretty well
(https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856)
Downloads
https://github.com/Grarak/android_device_samsung_a70q-twrp/releases (Also changelog)
Note The download is a zip file, unpack it and you will get the recovery image. To flash it in Odin pack it as tar with 7zip or a compression tool of your liking.

reserved

nice work, I'll buy the phone in this 2 days to start some works.

Thanks bro ?
Screenshot please

thanks alot ! development can start on this phone ! (i confirm twrp work)

BK☑️ said:
thanks alot ! development can start on this phone ! (i confirm twrp work)
Click to expand...
Click to collapse
Which version do you have?

devilhunter47 said:
Which version do you have?
Click to expand...
Click to collapse
TWRP version is 3.3.1
actual firmware is A705FNXXU3ASG6_A705FNOXM3ASG6_BTU (july security patch) (United kingdom)
prev. firmware was A705FNXXU1ASE4_A705FNOXM1ASE4_XEF (may security patch) (France)
edit 1 : the ui freeze completly when phone is booted up , had to flash all back
i'm going to flash A705FNXXU1ASD1_A705FNOXM1ASD1_BTU (april security patch) (United kingdom) and see if it boot correctly...
edit 2 : cant flash previous firmware due to 'security reasons' ,i flashed back stock recovery, it doesnt freeze anymore, i guess we will have to wait for a custom kernel

cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?

MTP
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
MTP doesnt work in this build
edit: it work in this build thanks
---------- Post added at 09:38 PM ---------- Previous post was at 09:30 PM ----------
kristiansja said:
cant you use this to flash GSI images and then use magisk? or does that not bypass the boot image problem?
Click to expand...
Click to collapse
i dont think this build is made for treble roms, so probably not

BK said:
MTP doesnt work in this build
Click to expand...
Click to collapse
Uploaded the wrong version. Fixed

Grarak said:
Uploaded the wrong version. Fixed
Click to expand...
Click to collapse
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
BK said:
lemme check
Click to expand...
Click to collapse
edit : it work now thanks!

Thanks dev! Astonished at the progress you've made despite Sammy's carelessness

BK☑️ said:
lemme check
---------- Post added at 09:57 PM ---------- Previous post was at 09:52 PM ----------
edit : it work now thanks!
Click to expand...
Click to collapse
With July security patch?

Okay, so can anybody else see if system or system images backup crashes TWRP?

FriendlyNeighborhoodShane said:
Okay, so can anybody else see if system or system images backup crashes TWRP?
Click to expand...
Click to collapse
yep , i tried backups yesterday but twrp crash when backing up system.img
---------- Post added at 09:04 AM ---------- Previous post was at 09:01 AM ----------
devilhunter47 said:
With July security patch?
Click to expand...
Click to collapse
i was refering to MTP , the link been fixed, MTP work now , but phone crash after boot up , or just wont boot at all, i were also stuck in prenormal RMM, thats why it wouldnt boot

Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse

Kernel source A70Q
Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?

BK said:
Grarak said:
FAQ
twrp reboot itself when transfering files and freeze forever , have to flash whole firmware again everytime
Click to expand...
Click to collapse
Seems to be a kernel problem. Probably have to wait for Samsung to update their sources.
BK said:
i found kernel sources from there https://github.com/Qiangong2/android_kernel_samsung_a70q , is this the source you worked with?
Click to expand...
Click to collapse
No
Click to expand...
Click to collapse

Grarak said:
FAQ
When TWRP can't work with Magisk, then what's the point of this?
TWRP can work with Magisk, if the firmware you have is compatible. (Read first post).
But yes, right now there are no reasons to have TWRP installed, but you have to start development somewhere and having a working custom recovery is a pretty good first step.
Click to expand...
Click to collapse
i contacted the guys from Samsung Opensource Center for kernel and platform source release, ill see what they say...

How to install TWRP can anyone tell step by step....