Database Info

Twrp for the LG Aristo aka lv3

FOR METRO PCS AND T-MOBILE.
I have the Metro variant.
This is my version of the T.W.R.P custom recovery for the LG Aristo. It's a stable release but as always it is use at your own risk. The device's bootloader has to be unlocked to use this recovery as with all recoveries. To enter fastboot mode: with the device powered off hold volume down and plug in usb cable and you are in fastboot mode.
Code : fastboot flash recovery twrp.3.1.1.-0_lv3.img
WARNING:
The stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications after flashing twrp!
SOLUTION:
Flash a root such as SuperSU or phh-superuser. You should also flash no-verity-opt-encrypt.zip.
Prerequisites :
Enable OEM Unlocking and usb debugging in developer options!
• YOUR BOOTLOADER MUST BE UNLOCKED
- reboot into fastboot [ adb reboot bootloader ]
- fastboot oem unlock [ this is going to wipe your data ]
If you have problems with the device drivers installed , you will need to install lg bridge app from lg that contains the device driver
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=PWZO7A26B9UW
How to flash the recovery:
• BOOT INTO FASTBOOT MODE:
With your phone off, connect your usb cable to your phone while holding VOLUME DOWN to boot into fastboot mode or just type [adb reboot bootloader] in the adb terminal
• ONCE YOU ARE IN FASTBOOT MODE:
Open a command prompt and type "fastboot flash recovery <path_to_recovery.img>” without the quotation marks.
Example: fastboot flash recovery C:/Users/<username>/Desktop/recovery.img
• WHEN THE FLASH COMPLETES: (Takes about 2 seconds)
On your phone, unplug the usb cable and power it off by taking out the battery and putting it back in.
• BOOT INTO RECOVERY MODE FOR THE FIRST TIME
HOLD VOLUME DOWN + POWER until you see the LG logo and then temporarily release the POWER button, immediately pressing and holding it back down until you see the white prompt [factory reset] screen. You will NEVER release the volume down button in this process!
Use the hard keys to select "YES" and then "YES" again to boot into TWRP!
How to Disable encryption & flash super su
1. In TWRP, go to Wipe > Format Data. Enter the keyword ‘yes‘, in the provided space and enter. This will wipe the automatically encrypted filesystem, and decrypt it.
2. Once the wiping is done, reboot back into recovery. Go to Reboot > Recovery.
3. When the recovery boots again, connect your phone to the PC and Enable MTP(if it isn't already enabled) under the Mount section.
4. Transfer the downloaded ‘no-verity-opt-encrypt-3.1.zip’ and ‘SuperSU-v2.82 zip´ to your internal storage or EXTSD
5. Disconnect the device now.
6. Tap on Install. Now, navigate your phone’s storage and select ‘no-verity-opt-encrypt-3.1.zip’. Finally swipe the ‘Swipe to confirm Flash’ button on the bottom of the screen.
7. The flashing process will merely take a few seconds. And when it’s done, follow the same method to flash the root package – SuperSU-v2.82.zip
Wait 1 or 2 minutes after the zip files are done flashing then reboot system and PROFIT! Your phone may take 3-5 minutes to boot the first time and it might boot-loop once or twice at the Metro PCS splash screen but don’t worry this is expected.
All required files [supersu+dm-verify disable] can be found in this thread :
https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047 ‘’.
Notice: After the TWRP splash screen you will see the option to type in the password to decrypt the filesystem. just ignore it and hit the cancel button.
Recovery link : https://www.mediafire.com/file/wj1jhzjop2jchag/twrp.3.1.1-0_lv3.img
Please do not mirror download
Thank you
Device Tree : https://github.com/czarsuperstar/android_device_lge_lv3_omni
Kernel Binary : https://github.com/czarsuperstar/android_kernel_lge_msm8937
iPioneer Stock rom works on this recovery also.
Version Information
Status: Testing
Current Beta Version: 3.1.1-0
Beta Release Date: 2017-08-13
Created 2017-08-13
Last Updated 2017-08-13
http://paypal.me/czarsuperstar
Help the development.

What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)
With a theme applied

Good look, I'll flash this one in a few minutes.

Hopefully we can get a custom ROM. My laptop can't build nougat and above. Only 4 GB of RAM.

[email protected] said:
Hopefully we can get a custom ROM. My laptop can't build nougat and above. Only 4 GB of RAM.
Click to expand...
Click to collapse
Either little thing is appreciated. We've got root, we have sources (rom and kernel), a fully functioning recovery, and lora's working on a rom. We're getting there.
Since I can't build a rom myself, so i've taken to working on a kernel because I've grown tired of how the kernel scales.

Great news. I might tinker around with kernel myself.

timba123 said:
No problems here. Thru Messis twrp i flashed your twrp. I tried xposed but too unstable. Tried pioneer rom with no problems. Also viper4android is working! Thanks much guys.
Click to expand...
Click to collapse
That's how I flashed it also it easier for setup imo

ninjasinabag said:
Either little thing is appreciated. We've got root, we have sources (rom and kernel), a fully functioning recovery, and lora's working on a rom. We're getting there.
Since I can't build a rom myself, so i've taken to working on a kernel because I've grown tired of how the kernel scales.
Click to expand...
Click to collapse
Maybe lora can pm @messi2050 and use his device tree to build for the Aristo.

Lineage OS Port
I fixed the shrill in phone calls. So far it's phone calls,mms,and mobile data. I'm uploading the back up now everything else has to be done to the fstab.qcom and I have to find the right files. That's why im uploading the backups cause 2 heads are better than one. Coming soon..

Nandroid backup LineageOS port
Research
https://www.mediafire.com/file/pcc0k...7D_1c53abf.zip
Very broken...

Didn't you have a Nandroid posted?

I did but I took it down. Its broken and cant be fixed by porting.

https://www.mediafire.com/file/pcc0...neage_ph2n-userdebug_7.1.2_NJH47D_1c53abf.zip

Figured out how to make the wlan.ko module when I get home I'll start working on that and post results.

Reserved

[email protected] said:
Figured out how to make the wlan.ko module when I get home I'll start working on that and post results.
Click to expand...
Click to collapse
How :cyclops: what's the current bugs ?

Vendor qcom opensource wlan prima
messi2050 said:
How :cyclops: what's the current bugs ?
Click to expand...
Click to collapse
I'm going to compile the kernel and make my own wlan.ko module so the port can be useable. I'm compiling lineage 13 right now I'm waiting on the finished build now. It takes 6 hours to compile on my laptop and if successful I'll post my work with the sources I'm using. I'll let you know.

I just got this phone on the 3rd so 27 days later I'm working on a lot. More than any other phone. I wish I can stop but I can't because of the motivation. OCD

Had to start over with the build. Malformed recovery fstab ( I used the one from twrp lol I forgot that lineage doesn't accept those kinds). I'll let you know what happened(if it's built correctly and flashes and boots) in the morning.

[email protected] said:
Had to start over with the build. Malformed recovery fstab ( I used the one from twrp lol I forgot that lineage doesn't accept those kinds). I'll let you know what happened(if it's built correctly and flashes and boots) in the morning.
Click to expand...
Click to collapse
Take your time. You've been busting buns getting all this done.
We all appreciate every little bit everyone has done.

[GUIDE][ROOT] How to root Cubot Note Plus with Magisk

Code:
Your warranty is now void!
I'm not responsible for any bricks/data loss
In this guide I will show you how to root your CUBOT NOTE PLUS using Magisk.
Make sure you back up all your files. Because everything will be lost.
1. Unlock your boot loader
01. Download Minimal ADB and Fastboot and the Universal ADB Drivers and install them somewhere
02. Enable Developer Options and enable USB Debugging and OEM Unlocking
03. Connect your Phone via USB to your PC
04. Open the MAF32.exe (in newer Versions: cmd-here.exe) in your Minimal ADB and Fastboot folder or run the Shortcut in your Start Menu
05. Type
Code:
adb reboot bootloader
Your Phone should reboot into bootloader
06. Type
Code:
fastboot oem unlock
All youre files will be deleted!
07. Follow the OnScreen Information on your phone (Press the VOL+ button on your phone)
2. Flash patched boot image
1. Download the patched boot image here: https://mega.nz/#!L3IWka7Y!pSR9MPdGdfWxXAZPcBMx_ysyF1CQ2VNVE9w3Uy11X7A. (patched with magisk v18.0)
2. Put it in the same folder as Minimal ADB and Fastboot.
2. type
Code:
fastboot flash boot patched_boot.img
3. Restart your phone and install the Magisk Manager App.
[/I]
If I made any mistakes or forgot something please correct me!

theres an update out. V14_20200820 with "minor bug fixes"
question to those how have a rooted quest... does it stay rooted when you install that update?
edit: okay normal way update does not work, becouse of custom twrp recovery... does anyone know where the downloaded ota-update file is located... i cant find it... (need to flash it with twrp)...

I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?

veretragna said:
I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?
Click to expand...
Click to collapse
That happens when flashing TWRP. The guide says you should boot TWRP.

Garyyy said:
That happens when flashing TWRP. The guide says you should boot TWRP.
Click to expand...
Click to collapse
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.

veretragna said:
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.
Click to expand...
Click to collapse
The TWRP Version isn't made by me. I know that it wont work when flashing it. Does your phone gets listed in the weird "artifact mode" when you type fastboot devices?

A couple of questions. Does this work with the V12 firmware? I also got the faulty bootloader screen with the artifact lines. Thinking that reflashing one of the original firmware files might fix it.
Pity that there isn't much going on for this phone as far as custom firmwares, recoveries etc go. It's a decent bang for your buck in terms of specs but a lot of wasted potential without some good custom roms.

veretragna said:
But when I try to reboot my device into fastboot mode, it just hangs with weird artifact line on the screen, and nothing happens. That's why I flashed it. At least TWRP is installed and boots, but screen is not accepting touches.
Click to expand...
Click to collapse
I did exactly the same, weird atifact screen is unreadable for me it appears after unlocking bootloader , my Note Plus hung at boot to ,reflashed stock rom and recovery all good now artifact line stays till phone finishes boot as bootloader loader remains unlocked. :good:

Steve8262 said:
I did exactly the same, weird atifact screen is unreadable for me it appears after unlocking bootloader , my Note Plus hung at boot to ,reflashed stock rom and recovery all good now artifact line stays till phone finishes boot as bootloader loader remains unlocked. :good:
Click to expand...
Click to collapse
For me the artifact screen appears before doing the unlocking bootloader step and when it's on that screen, the device doesn't respond to ADB at all, so I cannot actually continue and root this device. I tried reflashing the stock firmware and even that didn't help. I'm honestly starting to regret purchasing this phone.
Does anyone else with this device ever use it for USB tethering or WiFi hotspot? First device I've ever had that actually loses power while it's plugged in. I can plug the phone into my computer, activate USB tethering, and it'll lose about 15% of battery every hour. I can keep the phone plugged into the wall, activate WiFi hotspot, and it'll lose about 10% of battery power every hour. This device is a bad joke.

Phenom2122 said:
A couple of questions. Does this work with the V12 firmware? I also got the faulty bootloader screen with the artifact lines. Thinking that reflashing one of the original firmware files might fix it.
Pity that there isn't much going on for this phone as far as custom firmwares, recoveries etc go. It's a decent bang for your buck in terms of specs but a lot of wasted potential without some good custom roms.
Click to expand...
Click to collapse
The patched boot image is from the V12 firmware. I also had the artifacts but I was able to continue anyways.

Hey thanks for replying man. For me, ADB gets stuck on "detecting devices" and doesn't actually pick up my device at that point. But I have contacted the shop regarding the battery and charging issues and they have told me that my device is faulty and I'm picking up a replacement tomorrow. So hopefully I'll be able to do this soon.
I've just been kinda depressed about my purchase. I could've bought a Nokia 2 for just a little bit less and I would've been guaranteed quality. But I took a gamble on this 'Cubot' device with specs that were too good to be true for the price. It's a nice phone but it's battery and charging sucks balls. And I knew that it shipped with Android 7.0 but I thought that there would at least be an update to Android 7.2.1. I dunno, I'm just disappointed. My S4 Mini seems to kick this thing's ass in terms of battery power. And my S4 Mini is 6 years old, still on its original battery and has literally half the processing power and two thirds the RAM. I just needed this device for its 4G capability because my S4 Mini is the 3G model. I might sell it at a loss and pick up a MiFi router and new battery for my S4 Mini instead.
These phones are a huge missed opportunity. They pack some great specs for the price but offer a crappy, limited version of Android with no custom firmwares to be seen. Maybe if the battery thing works out and I can actually use this phone as a Wifi hotpot without it dying, I'll look into how to port a custom firmware to it. I think Slim or Carbon are in order, if they still exist.
Thanks for the reply dude. Maybe I'll have a different attitude to this phone once I have my replacement.

veretragna said:
I installed TWRP and tried to install root, but TWRP just doesn't allow to swipe and unlock the screen, seems like the screen does not accept touches. If I press the Power button, it turns the screen off and on, TWRP becomes locked and needs swipe to unlock, but screen still does not accept touches. WTF?
Click to expand...
Click to collapse
Adb a different twrp

Garyyy said:
Code:
Your warranty is now void!
I'm not responsible for any bricks/data loss
In this guide I will show you how to root your CUBOT NOTE PLUS using Magisk.
Make sure you back up all your files. Because everything will be lost.
1. Unlock your boot loader
01. Download Minimal ADB and Fastboot and the Universal ADB Drivers and install them somewhere
02. Enable Developer Options and enable USB Debugging and OEM Unlocking
03. Connect your Phone via USB to your PC
04. Open the MAF32.exe (in newer Versions: cmd-here.exe) in your Minimal ADB and Fastboot folder or run the Shortcut in your Start Menu
05. Type
Code:
adb reboot bootloader
Your Phone should reboot into bootloader
06. Type
Code:
fastboot oem unlock
All youre files will be deleted!
07. Follow the OnScreen Information on your phone (Press the VOL+ button on your phone)
2. Flash patched boot image
1. Download the patched boot image here: https://mega.nz/#!L3IWka7Y!pSR9MPdGdfWxXAZPcBMx_ysyF1CQ2VNVE9w3Uy11X7A. (patched with magisk v18.0)
2. Put it in the same folder as Minimal ADB and Fastboot.
2. type
Code:
fastboot flash boot patched_boot.img
3. Restart your phone and install the Magisk Manager App.
[/I]
If I made any mistakes or forgot something please correct me!
Click to expand...
Click to collapse
Does this method work with the Cubot P20 too ???

frank808 said:
Does this method work with the Cubot P20 too ???
Click to expand...
Click to collapse
No, because it is the boot image from the cubot note plus.

... dont want to open a new topic.
is there root option for the new cubot quest out there allready?

tko said:
... dont want to open a new topic.
is there root option for the new cubot quest out there allready?
Click to expand...
Click to collapse
You can probably follow the same steps. But you need to patch the boot image yourself. You can get the firmware for your phone on cubots website.

Garyyy said:
You can probably follow the same steps. But you need to patch the boot image yourself. You can get the firmware for your phone on cubots website.
Click to expand...
Click to collapse
the firmware i have.
but how do i patch the boot image?

tko said:
the firmware i have.
but how do i patch the boot image?
Click to expand...
Click to collapse
Install the Magisk Manager, press Install and choose BootImage. Than flash the patched boot image with fastboot.
Edit: On latest Manager it is called "Select and Patch a file" than select the boot image which is somewhere in the firmware.

Garyyy said:
Install the Magisk Manager, press Install and choose BootImage. Than flash the patched boot image with fastboot.
Edit: On latest Manager it is called "Select and Patch a file" than select the boot image which is somewhere in the firmware.
Click to expand...
Click to collapse
okay i did that, but the i get a bootloop with the patched boot.img
btw, the original img is ~32mb and the patched only 9mb
this seems strange.

tko said:
okay i did that, but the i get a bootloop with the patched boot.img
btw, the original img is ~32mb and the patched only 9mb
this seems strange.
Click to expand...
Click to collapse
Maybe try with a different version of the manager. Maybe report that issue in the Magisk thread.
Edit: Maybe Magisk returns only a patched ramdisk. Try and flash the patched image as ramdisk. If you have a ramdisk image, try to patch and flash that instead.

Garyyy said:
Maybe try with a different version of the manager. Maybe report that issue in the Magisk thread.
Edit: Maybe Magisk returns only a patched ramdisk. Try and flash the patched image as ramdisk. If you have a ramdisk image, try to patch and flash that instead.
Click to expand...
Click to collapse
okay if i could find a earlier version... , i would like to try it with 18.0
edit: found it... will try now.
crap, now the app does not give me the option to patch... no popup, no button, ...
edit2: okay, i cant use an older version, when i "install/patch" the app always first wants to update to the newest version.

TWRP for Umidigi A1 Pro

This is a thread for installing TWRP on the Umi A1 Pro
Code:
/*
* Your warranty is now void.
*
* I am 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 ROM
* 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.
*/
Download:
TWRP 3.2.1-0: Here
Steps to install TWRP
First of all, you will be required to unlock your bootloader.
Activate OEM Unlocking in developer settings
Activate USB debugging in developer settings
Now, open a terminal, if on Linux, or command prompt if on windows, and enter the following:
Code:
adb reboot bootloader
Code:
fasboot oem unlock
Follow the onscreen instructions to unlock your bootloader. THIS WILL WIPE YOUR DEVICE!!!
Once this is complete, it will go back to the fastboot screen.
Now, from within your terminal/command prompt, navigate to the folder where you have downloaded the above recovery.img to.
Enter the following command once there:
Code:
fastboot flash recovery recovery.img
This will flash TWRP to your device, overwriting the stock recovery.
Once this is complete, there will be a screen telling you how long it took etc. Now you need to hold down your volume up button, and power button. Keep holding these until you reach the menu for recovery, fastboot or normal mode.
Select Recovery.
This will boot you into TWRP
You will have to go through the setup of the whole android system again, but its worth it you now have TWRP to install the Custom ROMs that will be coming shortly
Have Fun!

Is this twrp good for treble GSI install?

I'm assuming this TWRP doesn't have the encryption issue? The one I currently have keeps flagging for a password.

peetee0007 said:
I'm assuming this TWRP doesn't have the encryption issue? The one I currently have keeps flagging for a password.
Click to expand...
Click to collapse
This one is asking for password as well.

Does it actually work with your own password? Only way around it now is to wipe data and reboot into recovery before encryption takes place. Pain in the rear.

I can't get the Twrp flash to work. It stays with the old recovery mode no matter what.
Here's my story. I've managed to apply this correctly once to my phone before, but due to me messing around with system file I've soft-bricked my phone and had to flash the official stock rom for it, I picked the C390_FE_K8B_UMI_20180601_1838 cause "Hey, higher number should mean more recent." I'm not sure what was the version of the phone when it was brand new and now it seems that the phone is completely immune to rooting.
Any idea what I've might done wrong when unbricking my phone?
----------------------------------------------------------------------------------
I managed to get it to work again, turns out I had to let the wireless update take place, then after a couple fails with the "adb reboot bootloader" command I read the list of stuff that gets thrown into cmd when you just do adb. Reading the commands I saw a "adb reboot-bootloader" so I do that one, gets me to the fastboot screen and then I'm able to proceed along with the guide.
Moral: If you have to unbrick the phone by flashing the original rom into it, let the wireless update take place before attempting anything else with the phone.
Thanks for the twrp recovery, now I just gotta defeat the encryption.

Awesome work! How did you figure out how to get USB to work?

I will try this but can you share what custom roms can i use on this twrp/phone?

blitzlee06 said:
I will try this but can you share what custom roms can i use on this twrp/phone?
Click to expand...
Click to collapse
You can flash pretty much most of these GSI ROMs.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list

stevea76 said:
You can flash pretty much most of these GSI ROMs.
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
Click to expand...
Click to collapse
how to check if im using the right architecture and partition style?

blitzlee06 said:
how to check if im using the right architecture and partition style?
Click to expand...
Click to collapse
64-bit quad core, ARM Cortex-A53= arm64bit ,bbut doen'st mean camera or other feature will work out of the box...

Diomorgan said:
64-bit quad core, ARM Cortex-A53= arm64bit ,bbut doen'st mean camera or other feature will work out of the box...
Click to expand...
Click to collapse
how about the partition style?

blitzlee06 said:
how about the partition style?
Click to expand...
Click to collapse
Arm64 A only

[TEST][Recovery] realme u1 twrp recovery

Team Win Recovery Project 3.x, or twrp for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface*
Prerequisites
1. Unlocked bootloader.
Bugs
1. You Tell Me
Instructions
1. Go to the fastboot mode.
2. Download the*recovery.img*and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
[
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
TWRP RECOVERY
{Mod edit}
XDAevDB Information
TWRP For Realme U1
Contributors @KSUBROTO
Version Information
Status:*Beta
Based on :*TWRP
Disclaimer:- This project hasn't been tested and flash at your own risk.

Thanks

Send me Bugs List

Will it work on RU1 pie?

dheva02 said:
Will it work on RU1 pie?
Click to expand...
Click to collapse
You Can Try

dheva02 said:
Will it work on RU1 pie?
Click to expand...
Click to collapse
You Can Test

What custom ROMS are supported on Realme U1 and which among those is best for privacy and stability concerned users?

Deepakk88 said:
What custom ROMS are supported on Realme U1 and which among those is best for privacy and stability concerned users?
Click to expand...
Click to collapse
No Custom ROM For Realme U1

What can i expect if i go ahead an install Linegae OS anyway, will it work reasonably well or will it be full of bugs and i face the risk of bricking my phone? I have no programming knowledge at all but I want to ger rid of or limit google's and other giants endless spying.

Deepakk88 said:
What can i expect if i go ahead an install Linegae OS anyway, will it work reasonably well or will it be full of bugs and i face the risk of bricking my phone? I have no programming knowledge at all but I want to ger rid of or limit google's and other giants endless spying.
Click to expand...
Click to collapse
I think Gsi Lineage Less Bug No Reason bricking your device

Did you tested it ?

CorcRoazBa said:
Did you tested it ?
Click to expand...
Click to collapse
I didn't Test Because I don't Have device But Some people It Work

CorcRoazBa said:
Did you tested it ?
Click to expand...
Click to collapse
I didn't Test Because I don't Have device But Some people Say It Work

Urgent help
I have hard bricked my device, even motherboard is dead. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM.

Deepakk88 said:
I have hard bricked my device, even motherboard is dead. Phone is in waranty. What should i say to realme support so they won't be able to tell that I tried to install custom ROM.
Click to expand...
Click to collapse
Just Brick Flash Stock rom flash it fix

I told them that the phone failed to start after a software update. They repaired it in 2 hrs and gave it back. So the motherboard was not fried as I thought.
What happened was that the TWRP recovery you provided has not worked, my device failed to get in to TWRP recovery after I have re-started the phone, So, I tried to flash with other TWRP versions that some people linked to in their posts on Realme U1 on other websites. None of them worked and after sometime my phone went in to bootloop, I got it in to fastboot screen by holding down the power and vol down button and tried various fastboot commands, none of them fixed the bootoop. I finally gave the command 'fastboot oem reboot -recovery' then it switched off the phone.

Deepakk88 said:
I told them that the phone failed to start after a software update. They repaired it in 2 hrs and gave it back. So the motherboard was not fried as I thought.
What happened was that the TWRP recovery you provided has not worked, my device failed to get in to TWRP recovery after I have re-started the phone, So, I tried to flash with other TWRP versions that some people linked to in their posts on Realme U1 on other websites. None of them worked and after sometime my phone went in to bootloop, I got it in to fastboot screen by holding down the power and vol down button and tried various fastboot commands, none of them fixed the bootoop. I finally gave the command 'fastboot oem reboot -recovery' then it switched off the phone.
Click to expand...
Click to collapse
Wait 2 minutes Twrp Work Only Work Color OS 5
Try This one For color os 6 pie https://forum.xda-developers.com/an...overy-unofficial-twrp-rmx1831-realme-t3947909

Hello sir
Sir please provide Realmi U1 costom recovery

Thread closed as the OP is no longer member of XDA.
@CyberJalagam Thanks for the heads-up.

[RECOVERY][STOCK]TWRP 3.3.1-0 UNOFFICIAL

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.
THIS RECOVERY IS FOR STOCK ROM AND WILL NOT WORK ON CUSTOM ROMS
Code:
#include <std_disclaimer.h>
/*
*
* 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 using 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.
*
*/
Bugs:
- The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode or flash the twrp.img, boot the device, reboot into bootloader and flash the original boot.img back, before booting into twrp.
You can also "fastboot reboot bootloader" in the blue fastboot mode.
This is a bootloader bug, maybe it gets fixed with the stock Q bootloader.
- Decrypt is not working for now (Is probably because the current stock firmware is still on May security patch - will be fixed with June patch)
- Brightness is a little bit buggy
- Transfering files to the external SD card will cause the phone to reboot
- Installing is not working yet, only booting.
- Please report any other bugs
Install guide:
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode
3. Unlock your bootloader
4. Run "fastboot boot twrp.img" in command line
6. Enjoy it
Optional (if you want to install it):
1. Boot from it (see the guide above)
2. Go to advanced -> Install recovery ramdisk
3. Choose the twrp img
4. Wait
5. You can now boot it with vol- and power button
If it keeps booting into TWRP and not System try
Code:
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
Download
Changelogs:
3.3.1-0 25.06.2019
- Fixed brightness bug
3.3.1-0 20.06.2019
- Adding logcat support
- Adding support to install TWRP to ramdisk
- Trying to fix brightness bug (seems to be not working yet)
- MTP probably fixed (needs reports)
3.3.1-0 19.06.2019
- Initial release
Source code:
https://github.com/Schritti/device-sony-kirin
https://github.com/Schritti/device-sony-ganges
If you like my work, press thanks
I would appreciate your Donation
XDA:DevDB Information
TWRP, ROM for the Sony Xperia 10
Contributors
Schritti, MartinX3, Oshmoun, Marijn, SODP Team
ROM OS Version: 9.x Pie
ROM Firmware Required: Stock Pie Firmware
Version Information
Status: Beta
Current Beta Version: 3.3.1-0
Beta Release Date: 2019-06-19
Created 2019-06-19
Last Updated 2019-06-25

Reserved

Reserved

First!
Woohooooo!

Thanks @Schritti, he helps me root my device

on my device (i3123), it shows a black screen.

ToastedToast said:
on my device (i3123), it shows a black screen.
Click to expand...
Click to collapse
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"

thanks！
bug report:
the file name in SDcard folder shows abnormal. please see attached pictures. (not only in windows explorer anf command line, but also in phone.)

wang4632 said:
thanks！
bug report:
the file name in SDcard folder shows abnormal. please see attached pictures. (not only in windows explorer anf command line, but also in phone.)
Click to expand...
Click to collapse
Thanks for the report.
That's due to the not working decryption of the internal storage, already on the bug list

It did not work on I4293
Thank you for customizing TWRP
But,I have a black screen with I4293 I have
Would you like to customize it

naoki2010 said:
Thank you for customizing TWRP
But,I have a black screen with I4293 I have
Would you like to customize it
Click to expand...
Click to collapse
Afaik I4293 is a Xperia 10 Plus. This TWRP is only for the normal Xperia 10.
I am already working on a TWRP for the 10 Plus.

under latest version I3123_Customized US_1317-7745_53.0.A.6.92_R8A, TWRP /sdcard decrypt doesn't work, however external storage is fine.
EDIT: realized that is already on the bug list

I wonder when it can work with costom rom???
Has the project been stopped?
I really need to flash third party rom..???

does it work on the i3113?

Hello, did the state of decryption change ?
If not, are you missing something ?

Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
How can I get out of the black screen I get from making this mistake?

Would someone plaese so kind and write down a step by step installation guide for a noob?

any twrp for xperia 5?

Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
Hi, thanks for all your work first of all!
I have rebooted into fastboot mode via ADB command line but after running "fastboot boot twrp.img" in command line, it says okay, and then I get the same problem, a black screen. My phone is a normal Xperia 10, not plus.
Could you please help me?
---------- Post added at 03:16 PM ---------- Previous post was at 03:01 PM ----------
Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
Schritti said:
Read the OP
"The "fastboot boot twrp.img" doesn't work, if you use the hardware buttons to open the blue fastboot bootloader mode. Only use adb, twrp or the android system to reboot into blue fastboot bootloader mode"
Click to expand...
Click to collapse
Hi, thanks for all your work first of all!
I have rebooted into fastboot mode via ADB command line but after running "fastboot boot twrp.img" in command line, it says okay, and then I get the same problem, a black screen. My phone is a normal Xperia 10, not plus.
Could you please help me?