Database Info

[RECOVERY][4.4.4][TWRP] TWRP 2.8.1.0 for apexqtmo

TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.8.1.0_0001
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.img.md5sum
update.zip format (Recovery flashable/sideloadable):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip
md5: https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.zip.md5sum
ODIN compatible tarball format (ODIN):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.8.1.0_0001.tar.md5
Please let us know of any other issues. Also with any other issues, please include a copy of your recovery.log, and dmesg from the TWRP session.

Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app

falle21 said:
Thanks for your work TeamApexQ!
Sent from my SGH-T699 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nice...Will be building some twrp themes just for the Relay 4G....glad you guys built it as ive been pretty busy

The work around for the "failed" flash. Unmount system in the "mount" menu prior to doing any flashing of zips. Even I have to do this on the G2 with TWRP 2.6.3.4.
Sent from my LG-VS980 using Tapatalk 4

New build posted in the OP!
Will now flash old Android builds (I've tested with every build I could get my hands on.)

I've never used TWRP, how does it differ from CWM for Backups ?
Are my CWM "nandroid" backups cross compatible ? I have Carbon, Omni and CM11 backups ready to switch at any time for testing in .tar format.

No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app

REV3NT3CH said:
No twrp backups differ from cwm...however Philz can handle twrp and cwm backups...however and in my opinion twrp can do a lot more as a recovery than any other recovery...one thing you can do...and is a slight pain...is boot the backup with cwm or philz. flash twrp and re backup that ROM in twrp then delete the old one...repeat for all backups
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM

yohan4ws said:
hmm yea ... or switch between recoveries restore w/ cwm, install twp, reboot re-create backup .. repeat.
Is there a fix permissions in twrp ? and is usb mounting in windows ? I found I didn't have the functionality of either with the latest CWM
Click to expand...
Click to collapse
thats what i was refferring too for saving your backups and restorable via twrp....and yes to all the other questions...twrp can do so many things while in recovery...for example..say you downloaded a rom from phone and forgot to put it in root of sdcard...twrp has a file manager with copy and paste functionalities to do so...it supports adb sideloading, mounting for both windows and linux, permissions, much better and clearer wiping method...all touchscreen...very themable for example http://forum.xda-developers.com/showpost.php?p=45122951&postcount=1 i made this theme specifically for my htc rezound as well as many others...which ill more than likely port to the relay as it has to match screen dimensions for resolution...overall it just has a bulk of many great options for a recovery and is very easy to use and get used to

New build posted in the OP. Small bugfixes in this release. (Including some SELinux and settings fixes.)

Did something wrong. How to fix?
Magamo said:
TeamApexQ is proud to release TWRP (from our OmniToad builds) for general use.
Current release: 2.7.0.0_0002
Raw image (for heimdall/Crazy 'cat'ing):
https://googledrive.com/host/0B-v962-Q8Pd9VWtvN0VrTXlQaTg/apexqtmo_twrp-2.7.0.0_0002.img
Click to expand...
Click to collapse
I wanted to install this version of twrp on my apexqtmo using heimdall under linux.
I booted into "download" mode, connected my USB table to my linux box, and I then stupidly flashed the wrong twrp module by mistake (for a different phone).
Without realizing my mistake, I then rebooted. I ended up back in my OS, and then, using the Power Menu, I booted into recovery mode. I got the blue text saying RECOVERY BOOTING.... , but after that, the screen remained black.
From then on, I cannot boot into the normal OS, nor into "download" mode.
Even if I remove the battery and then perform a standard boot using the power button alone, I get the blue text saying I'm booting into recovery, and the dead, black screen shows up.
I want to boot into the OS or download mode, but I can no longer do either. No matter what combinations of Volume-Up, Volume-Down, Home, and Power that I press, I always get back to RECOVERY BOOTING...., and I can't get into download mode again, no matter what.
Did I brick my phone?
If not what can i do to fix it?
Thanks for any help.
.​

The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Sent from my Nexus 7 using Tapatalk

Nardholio said:
The only way to clear the reboot mode is to either trigger a different mode or complete the boot. If key combinations don't work, you can try to see if the device comes up in adb and then you can "reboot bootloader" failing that you can trigger download mode with a resistor on the usb port. Google galaxy s 3 jig to find out how to make one or buy one
Click to expand...
Click to collapse
Thank you very much!
... and I fixed it!!!!
Your adb suggestion led me to the solution ...
I tried adb, but it didn't work.
However, after that adb attempt, the usb cable was still plugged into my device from my linux box, and I noticed that the device was in some sort of boot loop. The device kept giving short vibrations every few seconds.
At that point, I tried one more key combination that I hadn't thought of before: with the cable still plugged in, I held down Volume-down and Home without pressing the Power button ... because I guessed that the existence of the boot loop means that power might already be on, which would cause the power key to be unnecessary.
And my guess was correct: I got into Download mode!
I flashed the correct version of TWRP, and now all is well.
Thank you again for providing the suggestion that led me to my solution!
Also, thank you for telling me about the jig. I'm now going purchase one anyway, just in case I screw up again in the future. I think I can get one for $8 or less (I'm too lazy and clumsy to try to make one on my own).
.​

It's weird, but I had the same experience with the blue "RECOVERY BOOTING" followed by dead phone as described a couple posts ago... and I was flashing the correct file, the twrp zip in the OP, from recovery (cwm 6.0.3.7). I did it twice and got the same bad result.
To get around the bad dead phone result, I held volume down and power for 15 seconds, got into download mode, and then selected volume down to allow the phone to boot normally. Once it did, I went to the Play store and installed an app that could flash another recovery (cwm 6.0.4.5). Which worked.
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Sent from my Nexus 5 using Tapatalk

reaper000 said:
I will try flashing the .img file and see if that works, but I'm kinda perplexed why the twrp zip didn't work from recovery...
Click to expand...
Click to collapse
You indeed have to flash the .img file, at least if you're installing from the command line using heimdall.
.​

Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Sent from my Nexus 5 using Tapatalk

reaper000 said:
Ended up successfully flashing the .img file with recovery tools app from play store. Thanks all!
Click to expand...
Click to collapse
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.​

HippoMan said:
Glad it worked.
Also, FYI: you can't flash a recovery from within recovery. This is why your earlier attempt to flash the .zip from within recovery didn't work.
As far as I know, you have to be in bootloader mode (also called "download" mode) in order to flash a recovery. You have to boot into that mode and use somthing like heimdall to install the .img file. There are also tools you can use which will flash a recovery from a .zip file, but they actually just extract the .img file from the .zip file and then load that .img file via bootloader mode.
.​
Click to expand...
Click to collapse
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.

Magamo said:
The .zip file provided here CAN be flashed from within recovery. What likely happened was a bad download.
Click to expand...
Click to collapse
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk

reaper000 said:
Yeah, was thinking bad download, but I dl'd it twice. And there was no MD5 checksum that I could see
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Actually, which version of CWM were you using to attempt to install this from? Likely significantly old versions were not set up to flash recovery properly.

[UNOFFICIAL][RECOVERY][M250X] TWRP 3.1.1

Hi guys!
I built TWRP [Ver: 3.1.1] from scratch for M250X (X=i,N etc.)
ONLY FOR TESTERS NOW!
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. 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 me for messing up your device, I will laugh at you.
*/
Supported Models:
LG M250X (X=i,N etc.)
Click to expand...
Click to collapse
Steps:
First, unlock your bootloader using this guide and access to fastboot is needed!
(1) Download the recovery image.
(2) Download Flashify.
(3) Flash Recovery using Flashify.
You are in TWRP!
NOTE: To boot into recovery with hardware buttons use this method. Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally. This is because LG phones are a bit different and they instruct the recovery (TWRP in this case) to automatically perform a factory reset of the phone by triggering the /misc wipe flag. I mapped /misc partition to a different partition (/pad) so TWRP doesn't perform a factory reset.
BUGS:
Mentioned in 3rd post.
XDA:DevDB Information
[UNOFFICIAL][RECOVERY][M250X] TWRP 3.1.1 , Tool/Utility for the LG K10
Contributors
pvineeth97
Source Code: https://github.com/PVineeth/android_device_lge_mlv5_recovery
Version Information
Status: Testing
Created 2017-08-26
Last Updated 2018-12-17

Reserved

Reserved

pvineeth97 said:
Hi guys!
I built TWRP [Ver: 3.1.1] from scratch for M250X (X=i,N etc.)
ONLY FOR TESTERS NOW!
Disclaimer:
Supported Models:
Steps:
First, unlock your bootloader using this guide and access to fastboot is needed!
(1) Download the recovery image.
(2) Download Flashify.
(3) Flash Recovery using Flashify.
You are in TWRP!
NOTE: To boot into recovery with hardware buttons use this method. Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally. This is because LG phones are a bit different and they instruct the recovery (TWRP in this case) to automatically perform a factory reset of the phone by triggering the /misc wipe flag. I mapped /misc partition to a different partition (/pad) so TWRP doesn't perform a factory reset.
BUGS:
Mentioned in 3rd post.
XDA:DevDB Information
[UNOFFICIAL][RECOVERY][M250X] TWRP 3.1.1 , Tool/Utility for the LG K10
Contributors
pvineeth97
Source Code:https://github.com/PVineeth/android_device_lge_mlv5_recovery
Version Information
Status: Testing
Created 2017-08-26
Last Updated 2017-08-26
Click to expand...
Click to collapse
This also works for M250E?

abhiramb2k said:
This also works for M250E?
Click to expand...
Click to collapse
M250X (X also includes E).

But Flashify needs root permisson to do that. There is no root for M250n for now ;/

EnderPBO said:
But Flashify needs root permisson to do that. There is no root for M250n for now ;/
Click to expand...
Click to collapse
Go to this:
https://forum.xda-developers.com/lg-k10/how-to/guide-bootloader-unlock-t3662742
Then after unlocking the bootloader, rooting can be easier, I doubt.

any updates? worked for anyone?

Bump - anyone sorted root yet?

Let's work together for unlocking strategies.

abhiramb2k said:
Let's work together for unlocking strategies.
Click to expand...
Click to collapse
Are you working on unlocking the K10 bootloader (M250Ds)? Do you have this model?

Link is broken, I can't download the file, please help!
Thanks!!

rucafer00 said:
Link is broken, I can't download the file, please help!
Thanks!!
Click to expand...
Click to collapse
Unlock the bootloader first. I already built TWRP. I will build it again once bootloader is unlocked.

pvineeth97 said:
Unlock the bootloader first. I already built TWRP. I will build it again once bootloader is unlocked.
Click to expand...
Click to collapse
How can I unlock bootloader? Is it possible?

Hello, I have a LG K10 2017 m250f and I am 3 months waiting for some news on whether you will receive twrp or root this terminal, someone has an idea if there will be ?, or cell phone change?

Link isn't working
pvineeth97 said:
Hi guys!
I built TWRP [Ver: 3.1.1] from scratch for M250X (X=i,N etc.)
ONLY FOR TESTERS NOW!
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. 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 me for messing up your device, I will laugh at you.
*/
Supported Models:
Steps:
First, unlock your bootloader using this guide and access to fastboot is needed!
(1) Download the recovery image.
(2) Download Flashify.
(3) Flash Recovery using Flashify.
You are in TWRP!
NOTE: To boot into recovery with hardware buttons use this method. Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally. This is because LG phones are a bit different and they instruct the recovery (TWRP in this case) to automatically perform a factory reset of the phone by triggering the /misc wipe flag. I mapped /misc partition to a different partition (/pad) so TWRP doesn't perform a factory reset.
BUGS:
Mentioned in 3rd post.
XDA:DevDB Information
[UNOFFICIAL][RECOVERY][M250X] TWRP 3.1.1 , Tool/Utility for the LG K10
Contributors
pvineeth97
Source Code: https://github.com/PVineeth/android_device_lge_mlv5_recovery
Version Information
Status: Testing
Created 2017-08-26
Last Updated 2017-08-26
Click to expand...
Click to collapse
Link isn't working

nihat2003 said:
Link isn't working
Click to expand...
Click to collapse
It seems that pvineeth97 website vineethp.me is no longer up.
I might be wrong but i think the file to download is something built from the source code on his github:
github.com/PVineeth/android_device_lge_mlv5_recovery
I do not understand how to do this correctly though or what steps to take it with.

ShakespearesDroid said:
It seems that pvineeth97 website vineethp.me is no longer up.
I might be wrong but i think the file to download is something built from the source code on his github:
github.com/PVineeth/android_device_lge_mlv5_recovery
I do not understand how to do this correctly though or what steps to take it with.
Click to expand...
Click to collapse
I will upload the file.

Link Off
Favor atulizar link pois está offline.
Download the recovery image. - OFF

pvineeth97 said:
Hi guys!
I built TWRP [Ver: 3.1.1] from scratch for M250X (X=i,N etc.)
ONLY FOR TESTERS NOW!
Disclaimer:
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired. 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 me for messing up your device, I will laugh at you.
*/
Supported Models:
Steps:
First, unlock your bootloader using this guide and access to fastboot is needed!
(1) Download the recovery image.
(2) Download Flashify.
(3) Flash Recovery using Flashify.
You are in TWRP!
NOTE: To boot into recovery with hardware buttons use this method. Power off the device > press and hold Power + Volume Down buttons simultaneously > keep pressing them until the LG logo shows up > when the LG logo shows up, let go of the buttons for 1 second and then press them again. A factory reset menu will show up. Select "Yes" two times to "wipe" your device. Don't worry, this will actually NOT wipe your device. It will boot into recovery normally. This is because LG phones are a bit different and they instruct the recovery (TWRP in this case) to automatically perform a factory reset of the phone by triggering the /misc wipe flag. I mapped /misc partition to a different partition (/pad) so TWRP doesn't perform a factory reset.
BUGS:
Mentioned in 3rd post.
XDA:DevDB Information
[UNOFFICIAL][RECOVERY][M250X] TWRP 3.1.1 , Tool/Utility for the LG K10
Contributors
pvineeth97
Source Code: https://github.com/PVineeth/android_device_lge_mlv5_recovery
Version Information
Status: Testing
Created 2017-08-26
Last Updated 2017-08-26
Click to expand...
Click to collapse
Would it be possible to install your recovery through the official K10 2017 (M250Ds) recovery?
***Am I afraid to ruin him, at some risk by trying this?

ROOT BLU R1 PLUS - R0051UU ROM 6.0 V13 - MT6737m

Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Thanks to @lopestom for all his help and porting TWRP to this device
Thanks to RootJunky for FRP Unlock.img
Thanks to Larry Miller for testing with his device
This has been done to Three 16 G devices and One 32 G device to date
WARNING:
Code:
[B][COLOR="red"]
DO NOT FLASH RECOVERY WITH SP FLASHTOOL AS IT
COULD BRICK DEVICE!![/COLOR][/B]
For use SPFT you need special file. So here's the best way is using ADB-fastboot to unlock bootloader, flash FRP Unlock.img and recovery!!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users:
Code:
[B][COLOR="Red"]MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC![/COLOR][/B]
This method uses adb and fastboot commands to achieve root
Before any actions: copy all that you need from SDcard internal to PC!
If you want backup calls, messages, contacts (different by goggle contatcs or if you can record all the contacts in your google contacts account directly through the contacts application).
For backup, use any application from google play! Save in your PC! After all the processes you can restore them using the same application that you used.
- Instructions to PROCESS:
1. On phone open setting
about phone, tap 7 times in build number
Enable Developer Options
Enable USB Debugging
2. On PC search the folder of adb and fastboot minimal ( included in zip to install }
Unzip and Place unlock.img , recoveryTWRP.img and SR3-SuperSU-v2.79-SR3-20170114223742.zip in adb and fastboot minimal folder
Open adb terminal
Code:
adb devices
to ensure connection
Code:
adb reboot bootloader
Code:
fastboot flash frp unlock.img
Code:
fastboot oem unlock
( Confirm with volume up select on phone )
Code:
fastboot flash recovery recoveryTWRP.img
Fastboot will show image flashed but due to BLUs locking of device fastboot reboot will not function
So ….
Unplug device , Hold power off until device turns off
Hold Volume up and Plug device back into PC ,
Continue to hold volume up until TWRP boots fully
Select Wipe , Select Format Data ( don’t worry if any errors show )
Reboot TWRP Recovery
Select Mount , Select Mount USB Storage
Open Device on PC , Move SR3-SuperSU zip to device external_sd
Unmount
Select Install
Select external_sd
Select SU zip and install in TWRP
Select Reboot System
Phone May reboot several time do not interrupt boot
Unlocked bootloader and TWRP
xposed arm v89 has been tested and works , Gravitybox 6.5.3 has been tested and works
Download link
TWRP_Root_R1_Plus.zip
mirror: TWRP Root R1 Plus.zip
William Smith
XDA:DevDB Information
[TUT] Unblocking & Unlocking - Installing TWRP - ROOT, Kernel for all devices (see above for details)
Contributors
lopestom, donnasbrt1
Source Code: https://forum.xda-developers.com/android/general/blu-blu-vivo-kernel-sources-t3767993
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2018-09-18
Created 2018-09-19
Last Updated 2018-09-24

More in info: Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Link of Stock ROM - TWRP - TWRP Backup - Lineage 14.1 (almost bug free)
Click me post #13
.

lopestom said:
Unlock Bootloader and Root BLU R1 Plus
Yes it has been done
Click to expand...
Click to collapse
This is too late for me. I returned this phone long ago.

Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?

Donphillipe said:
Add one more 32G device, very happy now, this has been in the closet waiting for root and today it comes to life! Can't thank you enough!!! Works great!!!
---------- Post added at 12:53 AM ---------- Previous post was at 12:20 AM ----------
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
both of them have built in part of there install, a series of commands that remove other root, But is best to remove su before flash majisk. From the superSU app. in the menu is option to full remove superSU. Do that, then reboot make sure it is ok. Then try magisk. Note that it 'should' work, but it seems you will be first to try it.

Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: https://android.gadgethacks.com/how-to/magisk-101-switch-from-supersu-magisk-pass-safetynet-0177578/
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.

The factory image I downloaded must be corrupt or something else is wrong. I tried flashing the factory image I downloaded "Blu_R0051UU_MT6737M_V13_REPAIR" and I received the error: ERROR: SBROM_DOWNLOAD_DA_FAIL (2004)
I still can boot to TWRP but I have no backup image in this format. If anyone has a factor or TWRP to share, please let me know.

Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.

Donphillipe said:
Tried a different laptop, a couple of new cables and the error is still the same (see above) using the latest version of Flash Tool (v5.1828.01) to download the supposed stock ROM found online (http://www.mediafire.com/file/25su5934zm65vgb/Blu_R0051UU_MT6737M_V13_REPAIR.zip). I also deselected everything in Flashtool from the scatter file except "system" and it still would not load. Note that the only way to put the phone in a state that will communicate with the flash tool is to first hold the vol up and power button for a long time and keep holding them in until the BLU logo disappears and the TWRP menu appears. Here you select Reboot and then Power Off and only then will the flash tool try to communicate with the device when you plug the USB cable in. That's when the long red bar moves across the footer of the screen with 100% and a little later the error messages I named above occurs. Looks like I'm bricked unless I can find a kind soul to share a TWRP backup.
Click to expand...
Click to collapse
Larry Miller has also supplied a TWRP backup for this device ..thanks Larry
TWRP backup
Donphillipe said:
I installed SuperSU without thinking. Is it too late or is it possible to install Magisk instead?
Click to expand...
Click to collapse
With Supersu installed you can install Magisk and after remove suspersu......
Donphillipe said:
Just tried to uninstall SuperUS and it no longer boots, locks up at the BLU screen. I was following these steps: link
Should have made a backup when I had the chance. Oh, well it's like they say, live and forget and forget again.
So I guess I'll cross my fingers that this factory image I downloaded is not full of malware and is on the up and up.
Click to expand...
Click to collapse
After removed Supersu or Magisk the ROM can't start because have Custom recovery installed and made modified system option..... So in this case need install again supersu or magisk!
At all times it is necessary to think in safety not to have a bricked device.
Then for the uninformed users: MAKE A BACKUP OF THE ROM WITH TWRP AND COPY FOR YOUR PC!
Sent from my BLUBOO Xtouch using XDA Labs

Fixed, can't thank you enough!

Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
---------- Post added at 03:25 AM ---------- Previous post was at 03:10 AM ----------
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.

I no have the device in my hands. So you can install old version of magisk v15 or v16?
So if you need more information so you can enter here: BLU Development Team
Donphillipe said:
Wiped the phone and did a full restore, everything looked good. I rebooted to TWRP tried to install Magisk V 17, 17.1 and 17.2 and all of them fail install with error;
! Boot image patched by unsupported programs
! Please restore stock boot image
Updater process ended with ERROR : 1
Error installing zip file xxxxxx
Also fails SafetyNet check, not sure if it is supposed to or not. This is after restoring from the TWRP image supplied above and without rooting with SuperSU.
Click to expand...
Click to collapse

More in info on device R1 Plus
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this

donnasbrt1 said:
For anyone having issue with root or device issues .
If you can return to twrp and select power off this will allow required selection for so flashtool .Or if bootloop press and hold button combo and insert USB during power down of bootloop . Button combo for preloader is volume up and then power button then plug in device
Stock ROM here
https://www.mediafire.com/download/nbm2vt2dne5s2pc
TWRP
https://www.mediafire.com/download/hjmjpgepfbnjy7h
TWRP Backup
https://www.mediafire.com/download/eaxx8fla8a9a247
Lineage 14.1 (almost bug free)
https://www.mediafire.com/folder/fqqj9hqqascs0/Lineage 14.1 R1 Plus
Lineage has bug in OFF charging animation phone charges just no animation and rear camera macro focus
No other bugs have been found at this time
Xposed does work with this build v89-sdk25 arm
Thanks to Lopestom and Larry Miller for there support with this
Click to expand...
Click to collapse
Hello, which driver did you use? I can't get download mode work right

When loading bootloader ..power off device ...press volume up ..then power ( at the same time ) then plug device into pc ..device should load ..then device should flash .. do not flash preloader or imei issues may result

Any update on the progress lineage 14.1 on this phone? I use it for a day waa bit laggy

Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more

donnasbrt1 said:
Not at this time Lineage 14.1 was a test run for the device and I have not had time to finish yet and am also working Resurrection Remix right now .Camera porting has been a bit tricky as there are alot...alot of simlinks on stock rom for camera functions . I will have more time soon to work on it a bit more
Click to expand...
Click to collapse
Any update or ETA? I might put off a phone purchase if a build with a working camera comes along.... P.S. Another annoying bug I face is that videos don't play in some apps e.g. google photos, WhatsApp statuses and on Snapchat. Videos on Youtube and Facebook play fine. Fingers crossed for some good news! Wishing you a happy holiday season!

You can allways run stock rooted with xposed and gavitybox until bugs are worked out. Just a thought .Happy holidays to you also

+1 32G successful
Thanks for this! Waited for so long for a method.
Now: since I'm kinda newbie to root, I'm doubtful on how to detect custom kernels to flash based on this device model. Or is it possible to flash whatever?
I need something like 'ElementalX' or related.

Galaxy F23 5g twrp recovery built and working

+Galaxy F23 5g
twrp recovery built and working. But being replaced by stock recovery after booting to system.
Screenshots attached.
xda article: Galaxy F23 5g
code name: m23xq

pinakini said:
This is great news. May we expect custom rom in future.
Click to expand...
Click to collapse
Yes, once the recovery is ready without bugs. I have been busy recently and so no progress has been made yet.
Some pics of the recovery are attached.
Bugs to be fixed:
1) After booting to recovery the touch starts responding only after approx 1 minute.
2) If you lock the screen in recovery the recovery stops eesponding to touch.
3) Cannot mount system partition. So problem with flashing roms.
4) Stop automatic replacement of twrp with stock recovery after boot to system.

Can you upload the sources and device tree so that someone else can continue the work on it ?

xdadev2022 said:
Yes, once the recovery is ready without bugs. I have been busy recently and so no progress has been made yet.
Some pics of the recovery are attached.
Bugs to be fixed:
1) After booting to recovery the touch starts responding only after approx 1 minute.
2) If you lock the screen in recovery the recovery stops eesponding to touch.
3) Cannot mount system partition. So problem with flashing roms.
4) Stop automatic replacement of twrp with stock recovery after boot to system.
Click to expand...
Click to collapse
How long is it going to take to build it though? My phone's practically dead after Android 13 update... Wishing to get TWRP...

Kim Jae Ha said:
How long is it going to take to build it though? My phone's practically dead after Android 13 update... Wishing to get TWRP...
Click to expand...
Click to collapse
Why is your phone dead after Android 13 update ? Works fine for me.

I've been facing several bugs... Like half side of screen not working if unlocked with fingerprint... A lot of lag... Bluetooth disconnecting at random times and wifi not connected randomly... Plus I want to flash a Custom Rom or GSI on it... So I need TWRP...
Please make a build... I'll be very thankful to you...

....

xdadev2022 said:
Yes, once the recovery is ready without bugs. I have been busy recently and so no progress has been made yet.
Some pics of the recovery are attached.
Bugs to be fixed:
1) After booting to recovery the touch starts responding only after approx 1 minute.
2) If you lock the screen in recovery the recovery stops eesponding to touch.
3) Cannot mount system partition. So problem with flashing roms.
4) Stop automatic replacement of twrp with stock recovery after boot to system.
Click to expand...
Click to collapse
How can i get this recovery for My Samsung F23 5G.

Question samsung a536E stuck on bootloop

hello everyone, today i tried to flash twrp on my phone (rooted with magisk and running stock samsung rom), the flash was successful and i was able to boot into twrp but i coudnt access my storage or anything else, so i saw a guide saying to change the filesystem to ext2 then ext4, after i did that i could access most of the other folders but not the storage foldier as it still showed 0mb. i thought i just need to reboot my device to fix the issue but now im stuck on a bootloop. i cant poweroff the device since no button combination is currently working. is there anything i can do to power it off or do i have to wait a few days till the battery drains to 0?
[RECOVERY][UNOFFICIAL] TWRP for Galaxy A53 5G (Exynos)
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...
forum.xda-developers.com
this is the link i used to flash twrp except i didnt follow the wipe instructions because i dont want to use a custom os.
and if nothing else works and i have to wait a few days till it drains to 0, will i be able to boot back into samsung's recovery mode or is this device hard bricked?
help will be greatly appreciated.

This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.

sandsofmyst said:
This phone doesn't have the nice feature of holding the power button for force off so that is a negative here.
I don't think you should have edit:changed the partition types. If that was necessary it would be a ridiculous thing for other Android roms to have to do. Its all Android so should have worked without that.
Its unlikely that anything new will result from a cold boot verses a warm boot. Worth a shot I suppose but don't hold your breath. Expect nothing new.
If its stuck without Odin, fastboot, ADB, all buttons not doing anything, can't ingest and do something from sd card, can't show up via USB on computer, etc with nothing at all then its totally finished since nothing can be done. Consider it a loss and learn from it.
I'd like to also state that there are for some reason people who supposedly bring roms over to devices and they don't have the device so therefore don't really know if it works or not. You have to be careful about the guides you follow. I've seen someone try with a device that could not be unlocked ever for anyone and that person thought it would work. Live and learn.
Click to expand...
Click to collapse
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.

floppen22 said:
hello, i was able to boot the phone into twrp and do a factory reset, i had to time the vol up + power button at exactly the time when the screen went black and it worked!. but now i have a question, if i want to get twrp again and i dont plan to flash a custom rom like it says in the guide, how do i get twrp to recognize my storage? and do you flash twrp before installing an os or after because ive done it after installing the os.
Click to expand...
Click to collapse
yeah so it seems like the issue isnt with changing the file system or anything because i installed twrp again and tried rebooting and i got the same bootloop issue, but if i flash a rom then ill lose twrp like it happened last time so i dont understand what im supposed to do

you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.

beanbean50 said:
you have to format data in twrp otherwise it won't see your storage folder.
once formatted reboot to twrp then reboot to system, it should reboot to stock rom and the set up pages.
Click to expand...
Click to collapse
wipe>format data>type yes>reboot to recovery. i did that and still cant reboot to system bootloop issue persists

yes you did it correctly this time, is there anyway to undo your 'filesystem to ext2 then ext4'?

or maybe you have to flash the custom kernel to get it all up and running again

beanbean50 said:
or maybe you have to flash the custom kernel to get it all up and running again
Click to expand...
Click to collapse
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash

floppen22 said:
how do i do that? the kernel folder in the guide doesnt have any tar or .img file to flash
Click to expand...
Click to collapse
it's a zip file so it should flash in twrp

beanbean50 said:
it's a zip file so it should flash in twrp
Click to expand...
Click to collapse
yes i was able to boot into my phone after flashing the kernel. thank you so much.

Try a different version of TWRP I remember this happened to me before and I installed a different version and it was fine