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:
#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 ROM
* 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.
*
*/
Bugs
You tell me ;D
Install guide
See #2
Downloads
3.6.0_9-2
Source Code
https://github.com/omnirom/android_bootable_recovery
https://gitlab.com/TipzTeam/oppo-msm8937/recovery_device_oppo_A57
Donations
https://paypal.me/TipzTeam
Install guideFirst-time installation (Windows)
Power off your device
Press and hold Power, Vol +, Vol - while plugging your OPPO A57 into your computer
Unzip the file you've downloaded
Open MiFlash and select the extracted directory
See if your computer has detected you device. If so, click flash.
Wait until it say "Done".
Unplug your device. Press and hold Power Button, Vol +, Vol - until you feel a vibration and then the oppo splash screen
You should now be in the recovery.
First-time installation (Linux)
Install edl
Power off your device
Press and hold Power, Vol +, Vol - while plugging your OPPO A57 into your computer
Unzip the file you've downloaded
Check lsusb and see if your computer has detected you device.
Run the following command in Terminal:
Code:
edl qfil <qfil_package_path>/rawprogram0.xml <qfil_package_path>/patch0.xml <qfil_package_path>
Unplug your device. Press and hold Power Button, Vol +, Vol - until you feel a vibration and then the oppo splash screen
You should now be in the recovery.
For others
Extract the "recovery.img" file from the file you've have downloaded
Push the file to your device
Power off your device and boot into recovery mode
Click on "Install", then "Install Images"
Find the new recovery image and click on it
Select "Recovery" and swipe the bar at the bottom
Reboot into Recovery once the flash is done
Is this project treble enabled?
If yes, can you tell me the ways to install Gsi?
maharjanujwol said:
Is this project treble enabled?
If yes, can you tell me the ways to install Gsi?
Click to expand...
Click to collapse
No, this phone doesn't have any ROM.
Update for fully English version coming soon!
need A57 stock recovery image file. please anyone?
engr. mkhalid said:
need A57 stock recovery image file. please anyone?
Click to expand...
Click to collapse
Why would you want that?
TipzTeam said:
Why would you want that?
Click to expand...
Click to collapse
Do u have the unofficial version of twrp for oppo a57?
ninja711 said:
Do u have the unofficial version of twrp for oppo a57?
Click to expand...
Click to collapse
This is unofficial, wdym?
New TWRP update!
3.5.2_9-0 (Sep 12, 2021)
TWRP 3.5.2
Download
New TWRP update!
3.6.0_9-0 (Dec 25, 2021)
TWRP 3.6.0
Update to Android 9.0
Support vendor partition
Fix ramoops
Support NTFS
Add logcat support
Download
New TWRP update!
3.6.0_9-1 (Jan 24, 2021)
Fix decryption after Android Pie update
Allow wiping of vendor partition
Rename Modest to EFS
Download
New TWRP update!
3.6.0_9-2 (Jan 25, 2021)
Fix SD Card after Android Pie update
Allow rebooting to EDL mode and bootloader mode
Download
tipzrickycheung said:
Allow rebooting to EDL mode and bootloader mode
Click to expand...
Click to collapse
So we can now boot into fastboot mode the commands doesn't seem to work.
Everything except a few returns something like "remote command not found".
Code:
fastboot devices
works fine & shows the connected device but
Code:
fastboot oem device-info
doesn't.
Is it because the device doesn't have fastboot binaries or something like that?
impawstarlight said:
So we can now boot into fastboot mode the commands doesn't seem to work.
Everything except a few returns something like "remote command not found".
Code:
fastboot devices
works fine & shows the connected device but
Code:
fastboot oem device-info
doesn't.
Is it because the device doesn't have fastboot binaries or something like that?
Click to expand...
Click to collapse
This device has its bootloader commands removed, which is a build flag of LK (Little Kernel, used on almost all QCOM device).
We can't compile our own for the A57 since it has secure boot on.
大家有A57刷机包吗
Hi @tipzrickycheung , thank you for TWRP.
I saw a screen on Telegram where you installed Magisk too. But if I try to install magisk.zip or to flash a patched boot.img from EDL, I get stuck in a boot loop and have to reinstall a stock rom.
Tupolef said:
嗨 @tipzrickycheung,谢谢你使用 TWRP。
我在 Telegram 上看到一个屏幕,你也安装了 Magisk。但是,如果我尝试安装 magisk.zip 或从 EDL 刷入已打补丁的 boot.img,我就会陷入引导循环,不得不重新安装一个 stock rom。
Click to expand...
Click to collapse
你做完了吗?我现在也发生这种情况,一旦安装了 magisk.zip,它就会卡在“当前映像(启动/恢复)已被破坏,无法启动...”
oddhw said:
你做完了吗?我现在也发生这种情况,一旦安装了 magisk.zip,它就会卡在“当前映像(启动/恢复)已被破坏,无法启动...”
Click to expand...
Click to collapse
I went back to a Stock Rom and I didn't find any other solution. It wasn't my device, so I will not try again.
Related
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
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?
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/July patch)
- Touch not working when installed
- Please report any other bugs
Install guide:
Installing is currently not recommended because touch is not working on the installed version!
1. Install fastboot tools from google's sdk on your PC
2. Enter fastboot mode from adb
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 03.08.2019
- Initial Release
Source code:
https://github.com/Schritti/device-sony-mermaid
https://github.com/Schritti/device-sony-ganges
If you like my work, press thanks
I would appreciate your Donation
Thanks to:
@MartinX3 for helping me developing the TWRP
@Oshmoun for providing device trees for Ganges and Mermaid
@naoki2010 for Testing
XDA:DevDB Information
TWRP, ROM for the Sony Xperia X10 Plus
Contributors
Schritti, MartinX3, Oshmoun, Marijn
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-08-03
Created 2019-08-03
Last Updated 2019-08-05
Reserved
Reserved
Woohooo!
First!
My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.
sickkside13 said:
My computer is down at the moment but I have a question does this supports the North American unlocked variant i3223? I looked at your sources and I don't see the i3223 variant.
Click to expand...
Click to collapse
All variants are supported
I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?
clothtalklp said:
I am having the worst time trying to get this device (i3223 variant) into recovery or into fastboot mode so I can boot into recovery via adb. The device is pattern locked and wasnt adb enabled before hand. I can get to where the light flashes blue after holding vol up while inserting usb but screen is blank then goes to a charging screen. I want to erase and test on this device. Its been a couple days and drivers are correct emma doesnt work and the sony companion wont recognize the device only that its locked. any help?
Click to expand...
Click to collapse
It's normal, that the screen is black in fastboot mode. If the LED is Blue then it's alright.
When you're in fastboot mode (Blue LED) check the windows device manager, you might install the driver again for fastboot. If it shows a device called "Android" you have to right click it and install the correct driver.
I just got the phone unlocked so i will boot into TWRP and install it and debug the touch. I have the feeling that it might be just missing file.
I just tested the installed version of TWRP and touch works just fine. The TWRP on itself is little slow. Decryption is broken and we see just bunch of junk folders in internal storage as expected.
But decryption shoudlnt be an issue after i bake TWRP into my AOSP images.
Rebooting into OS is totally broken and even cleaning misc doesnt help. Boots to TWRP all the time. Again most likely just an issue that it was not installed in boot.img right away but had to be added.
So about unlocking - my device/version isn't supported to unlock. Any hints?
mad-murdock said:
So about unlocking - my device/version isn't supported to unlock. Any hints?
Click to expand...
Click to collapse
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.
Haxk20 said:
You cant unlock bootloader. Thats just it. Did you buy the device from carrier ? If so they have usually not unlockable devices.
Click to expand...
Click to collapse
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.
mad-murdock said:
bought it used super cheap, wanted to play with it and maybe help a bit with development. but määä - seems like not.
do you think the device might become unlockable with a future firmware update? i am more a oneplus user and have little experience with sony.
Click to expand...
Click to collapse
Sadly I do not think so. We would love another dev helping on SonyOpenSourceDevices or even custom ROMs but sadly if the phone is not unlockable there is nothing you can do sadly. I heard stories of people having carrier phones sim locked and after unlocking that they were able to unlock BT so you could possibly try that if the phone is locked to 1 carrier. If not then there i s really nothing you can do. I'm sorry.
Hi,
first off a big thank you!
I would like to root my xperia 10 plus I4213. I tried to do my homework before posting here, but since I am not knowledgeable on the subject, can someone confirm that these are the right steps:
1. Enable in phone third party apps, unlock developer settings, enable adb.
2. Boot in fastboot mode. That can be done in terminal, not by using buttons as it used to.
3. unlock bootloader . My understanding if that now, that can be achieved either via terminal or via windows newsflasher program.
4. Flash recovery from this thread
4. Boot into system and install magisk manager .
5. Install via recovery Magisk zip.
6, Boot into system and use magisk manager to enable root and set settings.
Should I install latest magisk 20.1 or an earlier version?
Thank you.
Problem with TWRP
Why is the device memory data encrypted even though the device doesn 't have a password?
reintal said:
Why is the device memory data encrypted even though the device doesn 't have a password?
Click to expand...
Click to collapse
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.
Haxk20 said:
That is how your internal storage looks like when encryption is just Ffkjgh up.
This recovery dont have any updates and well its just broken for now. sadly.
Click to expand...
Click to collapse
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.
reintal said:
It sounds sadly 'cause in that case it is not possible for me to install magisk on the standard firmware and I cannot use gpay anyway.
Click to expand...
Click to collapse
We are mainly focus on making AOSP 10 stable now and TWRP is not on top of the list to fix now. And TWRP doesn't support Android 10 yet so we can't even begin.
Unfortunately realme has not allowed us to unlock boot-loader on android 10 so instead we go back to pie.
IMPORTANT! -- YOU NEED AN SD CARD
HTML:
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* 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.
* Your warranty will be void if you tamper with any part of your device / software.
First download the P2Q zip from https://download.c.realme.com/osupdate/P2Q.ozip
Although it says pie to q we can flash it from q.
And the Q2P rollback from https://download.c.realme.com/osupdate/Q2P.zip
Place all on sd card
turn phone off
hold volume button down and power button until phone turns on
in recovery go to INSTALL FOR STORAGE
then sd-card
Flash P2Q FIRST
After rebooting to the Q beta go back to recovery
now flash Q2P
After rebooting you should have pie
Next follow the instruction from realme to unlock your bootloader at https://c.realme.com/in/post-details/1134295513231785984
Next download adb and fastboot binaries either at: https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/ or at here https://www.xda-developers.com/install-adb-windows-macos-linux/ if not working
download twrp at https://twrp.me/oppo/realme3pro.html and put in adb & fasboot directory
after installation go on your phone and unlock developer settings (setting, aboutphone, then tap build 7 times)
enable usb debugging
connect phone to pc via usb 2.0 cable
on pc run: adb reboot bootloader
phone should go to bootloader
Next run: fastboot flash recovery recovery.img
but replace "recovery.img with the file name of the twrp you downloaded, for example: fastboot flash recovery twrp-3.3.1-2-RMX1851.img ":
Next download vbmeta image from https://drive.google.com/open?id=1-aEYcAW3BUAmsdsvjGTC1MWQ2Dwui_Mw and then put in adb & fasboot directory
Next try: fastboot --disable-verity flash vbmeta vbmeta.img
IF it doesnt work do: fastboot flash vbmeta vbmeta.img
use volume buttons to change to recovery then press the power button
Done.
now flash any rom you want
Final note - If something doesn't work and your phone is bricked try here: https://forum.xda-developers.com/realme-3-pro/how-to/guide-to-stock-rom-stock-recovery-t3940604
Realme UI for realme 2 pro
Bro my phone is realme 2 pro I rooted my phone and installed TWRP and I flashed oneplus os on android '9pie can go to the realme ui, I am already I have android pie, realme ui can support to the realme 2 pro?? Please reply to me
After flashing the p2q zip can I flash directly the latest coloros ozip available from realme website or is it just the q2p zip which can be flashed
Help me i cant go back to color os, when i installed q2p.zip my phone bootloop on realme white logo, i try 3 time to download and install again but still bootloop. Please help me
Gigaga663 said:
Help me i cant go back to color os, when i installed q2p.zip my phone bootloop on realme white logo, i try 3 time to download and install again but still bootloop. Please help me
Click to expand...
Click to collapse
Have you tried flashing latest android q rom?
khannz7 said:
After flashing the p2q zip can I flash directly the latest coloros ozip available from realme website or is it just the q2p zip which can be flashed
Click to expand...
Click to collapse
just q2p to go back to pie
what rom? you have link to download lastest android q rom?, i just flash android q rom from realme comunity
---------- Post added at 06:00 PM ---------- Previous post was at 05:44 PM ----------
Gigaga663 said:
Help me i cant go back to color os, when i installed q2p.zip my phone bootloop on realme white logo, i try 3 time to download and install again but still bootloop. Please help me
Click to expand...
Click to collapse
Mr-JGlynn said:
Have you tried flashing latest android q rom?
Click to expand...
Click to collapse
what rom? you have link to download lastest android q beta rom?, i want go back from realme ui os to color os, i cant unlock bootloader in realmeui os, then i use this method flash android q Beta (p2q) then rollback with (q2p) but when i flash q2p my phone bootloop then i flash p2q again from recovery, you have sollution to help my phone go back to color os? (right now my phone still in android q beta(p2q))
* sorry if my english so bad
Cant unlock bootloader
Cant unlock bootloader after following all your steps.
I am tired of this mobile.
Searched all solution but no luck.
Please give solution.
Its showing fastboot error, too many links. then stucked in chinese logo and number 6-10 something..
Hello !
I tried to root my Oukitel WP15 by following the magisk method
I downloaded the official rom of the oukitel WP15 on the official website and I patched it by my phone with the apk.
After that, I disabled the bootloader security and flashed the boot partition.
But after restating my phone, I'm currently blocked in a bootloop
Orange state
Your device has been unlocked and can't be trusted
Your device will boot in 5 seconds
And my phone is no longer detected by adb nor fastboot
If someone have an idea ?
Thanks in advance,
try to restore boot and vbmeta via flashtool. it's saves me from red state (wp15 too).
vxsw said:
try to restore boot and vbmeta via flashtool. it's saves me from red state (wp15 too).
Click to expand...
Click to collapse
If only my wp15 was detected by my computer. Since I got stuck on this boot loop my wp15 always reboot and is connected and disconnected again and again
adb and fastboot is not a pc. it must be detected by pc even when powered off. check in devices via device manager. if it exists - that's enough for flashing. install mtk usb-com drivers (by manual of flashtool) and flash it, but check only boot.img and vbmeta.img and do not use "format" only "download". after flashing it must be accessable via fastboot.
n.b. if it ask to remove battery:
- unplug your phone
- setup flash tool and click "download" button
- power off phone
- on unplugged phone, hold both volume buttons and hold power button too (three buttons at once).
- hold it all >15 seconds and ignore any phone activity, just hold.
- release power button only (keep holding both volumes)
- plug your phone (still keep holding both volumes)
- now flashing process must start and you may release any buttons.
p.s. of course I mean boot.img and vbmeta.img from original firmware, downloadable via vendors download center https://oukitel.com/pages/download-center (select wp15 manually)
vxsw said:
adb and fastboot is not a pc. it must be detected by pc even when powered off. check in devices via device manager. if it exists - that's enough for flashing. install mtk usb-com drivers (by manual of flashtool) and flash it, but check only boot.img and vbmeta.img and do not use "format" only "download". after flashing it must be accessable via fastboot.
n.b. if it ask to remove battery:
- unplug your phone
- setup flash tool and click "download" button
- power off phone
- on unplugged phone, hold both volume buttons and hold power button too (three buttons at once).
- hold it all >15 seconds and ignore any phone activity, just hold.
- release power button only (keep holding both volumes)
- plug your phone (still keep holding both volumes)
- now flashing process must start and you may release any buttons.
p.s. of course I mean boot.img and vbmeta.img from original firmware, downloadable via vendors download center https://oukitel.com/pages/download-center (select wp15 manually)
Click to expand...
Click to collapse
Yes okay but I was waiting that my wp15 is out of battery to shutdown because the buttons does nothing and when I plug it again it go again in this boot loop so IDK how to,,,
Lunalunea said:
I was waiting that my wp15 is out of battery to shutdown because the buttons does nothing and when I plug it again it go again in this boot loop
Click to expand...
Click to collapse
discharging 15000 battery by boot loop? not sure if serious.
as I've remember, when I tried to shutdown my phone by holding power button while it was in red state, it would not power off, just rebooting. it goes power off when I tried to flash it via flashtool. it jus immediately powered off when I'd click "download" button in flashtool. so try it, then by manual from above. and when you would hold volumes and power - ignore any phone activity, even it would restart continuously. just hold >15 seconds (20 for sure), release power button and plug in pc. anyway, even if you could not power off it, just try to flash as I wrote before, just exclude "power off" point.
Hi, mates, I am a new Oukitel WP15 owner.
Is there any safe root method for our new baby?
di0nko said:
Hi, mates, I am a new Oukitel WP15 owner.
Is there any safe root method for our new baby?
Click to expand...
Click to collapse
Post your own topic
anyone found a working twrp img for oukitel wp15? or a GSI install method for this model?
Lunalunea said:
Yes okay but I was waiting that my wp15 is out of battery to shutdown because the buttons does nothing and when I plug it again it go again in this boot loop so IDK how to,,,
Click to expand...
Click to collapse
Have you find how to install twrp? I can't flash the partition, i get error, "partition not exists
Asqq said:
anyone found a working twrp img for oukitel wp15? or a GSI install method for this model?
Click to expand...
Click to collapse
gsi installs flawlessly, but not all gsi are compatible. I use a phhusson's 11.0 v313 and it works fine enough.
also I know, what (at least) one man tried to use 12+ phhusson's builds and got fail. I'll suggest what it's some boot compatibility issue and will not work properly with otiginal oukitel boot of android 11.
vxsw said:
gsi installs flawlessly, but not all gsi are compatible. I use a phhusson's 11.0 v313 and it works fine enough.
also I know, what (at least) one man tried to use 12+ phhusson's builds and got fail. I'll suggest what it's some boot compatibility issue and will not work properly with otiginal oukitel boot of android 11.
Click to expand...
Click to collapse
Can you give more details about install? i can't find and flash a twrp. When i try to flash a random oukitel img recovery, it say "partition not found" and if i use the command to directly boot on recovery, the androids keeps boot loop
On my bv9100 work an oukitel k9 twrp img and i have on it GSI 18, Andy Yan version, i wanted to try on oukitel wp15 too but i can't flash anything, I still get the error partition
you do not need twrp or any similar. just upload gsi to fastbootD via fastboot command from adb tools.
I strongly recommend you to read about treble project and partition structure it really help in understanding of all of this. just english is not my first language and I'd not sure what I can explain all of this exactly and correctly. but ok, I'll try, but I'm not sure what this thread is correct place for this, I'll suggest to go here https://forum.xda-developers.com/t/oukitel-wp15.4402253/ seems it'll be a bit more right place.
@Timmmmaaahh! Cannot delete
Why ?
Lunalunea said:
@Timmmmaaahh! Cannot delete
Why ?
Click to expand...
Click to collapse
No, deletion of threads/posts is avoided because it generates 404 errors. We lock (and void, if needed) them instead.