Database Info

Unofficial twrp for Elephone u pro v3.2.1.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
Notice1:
U Pro has A/B partitions. to prevent issues its good to flash it in both slot, because i/we can not know on which partition you are
Notice 2:
This version only working on Eragon roms
Maybe soon I'll manage it to work on stock rom
Notice 3: Sdcard now working
DOWNLOAD
TWRP for 20180227 Base via Qfil Flashtools:
Go here : https://drive.google.com/file/d/1650peMjuk_WTFkxlufL84aJ6cMG5-g3q/view?usp=drivesdk
TWRP for 20180423 Base and newer:
Go here: https://drive.google.com/file/d/1vzDDVRl8vKMGzybVm_FYvufHlmOygOud/view?usp=drivesdk
INSTALLATION
if you use the old 20180227 Base you have to use Qfil Flashtools , because fastboot commands dont work in that Build.
we have a good guide of how to use FLashtools already
look here: https://forum.xda-developers.com/android/development/guide-elephone-pro-user-manual-t3775895
if you are on 20180423 Base and newer you can use fastboot commands
required : ADB and fastboot
enable usb debugging in developer settings.
do this:
Code:
adb shell
Code:
reboot bootloader
now we flash it in slot a
Code:
fastboot flash boot_a twrp.img
after that we flash it also in slot b
Code:
fastboot falsh boot_b twrp.img
Special thanks to
teamwin for this awesome custom recovery
@travis82 for his advices
And @skeleton1911 for his help

smartphone does not leave twrp
Thank you in advanced if you can help me.
Has given an error on startup and I can not restart system, restarting twrp

Givanildo01 said:
Thank you in advanced if you can help me.
Has given an error on startup and I can not restart system, restarting twrp
Click to expand...
Click to collapse
Join us on Telegram group
https://t.me/joinchat/GxIBOhKXi5I6bsNWOm6LFg
And for your problem it's because you are coming from stock rom and that's for the meantime not working because of data encrypted

How To Guide Persist Issue's! (Quick Guide)

Hello, Before we get started this is a quick TLDR guide and you do this at your own risk, If you DM me and your phone doesn't work I will laugh myself to sleep. (This shoulden't do that unless your stupid!).
If you have issues such as sensors not working like Auto Rotate, Proximity, Auto Brightness, Etc (Use a sensor testing app to confirm) [Make sure your 100% sure it's not due to damage].
Then you need to flash the persist.img, Some how or at least in my experience its become corrupted, normally you would just flash via fastboot the stock files and you should be good to go but Xiaomi doesn't let you flash these because you should not ever have too. The last option was to use EDL but that seems complicated for a issue with some sensors.
Now thanks to a few guides on XDA (Can't find the right one or I would link it here) and some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Messing with the persist partition is not recomended and may break stuff as its never ment to be tampered with so if you can't use pay anymore Don't blame me!
You do so at your own risk!
1. So Grab your firmware IE latest from your chosen region
2. Grab the extracted persist.img and load your recovery
3. Then select persist img and select it from storage (SD Card)
4. Make sure you pick flash to persist (On OrangeFox it was Persist_IMAGE for me)
5. Flash it and reboot
6. Check your sensors and they should be working!
Now you don't have to spend hours looking online your welcome!
Please thank the individuals that found this and not me I'm just a risk taker and have money to replace it if I Break it.

UnfixableExploit said:
Can't find the right one or I would link it here)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
XDA Search in This forum
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86002353
UnfixableExploit said:
some other Xiaomi user posts the quickest way is just to use a recovery to flash the img, now I've tried coping the backup persist partition (PersistBak) and it did not help me nor did using recovery to dd the image to the persist partition, but flashing via OrangeFox did the trick,
Click to expand...
Click to collapse
https://forum.xda-developers.com/t/problem-proximity-sensor-vayu.4366935/post-86137755

I believe I used the one from the Xiaomi Mi 8, I didn't know we had a vayu guide...

And when I looked for one online quoting XDA it never showed up.

Question Device bricked, possibly damaged super partition?

When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
Fastboot Enhance shows I have a super partition 11.5GB in size:
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?

Hello. I have an idea as follows. if you need to do that, look for a rom specifically for flashing super.img, not a rom that contains a lot of images like this

bubugugu said:
When attemping to flash the india A9 rom, "FAILED (remote: 'No such file or directory')" is encountered, the device is half bricked
I'm using this guide:
How to flash India version rom on rmx3560 (80W)
This is a simple tutorial English is not my native, so if anyone can add more explanation or answer question i will very appreciate Before flash, you must have adb and fastboot. Now follow the step Enable devloper option and enable oem unlock...
forum.xda-developers.com
View attachment 5769945
According to this Google, "system" , "vendor" and "product" belongs to a dynamic partition inside super partition
Implementing Dynamic Partitions | Android Open Source Project
source.android.com
View attachment 5769943
Fastboot Enhance shows I have a super partition 11.5GB in size:
View attachment 5769965
I then tried to create / delete the logical partition and encounter "Could not open super partition" error:
View attachment 5769959
Does this mean I have a corrupted super partition?
I tried the following command, it didn't solve the issue:
fastboot erase super
fastboot flash super super_empty.img (file is from A9 zip)
Will flashing a "super.img" solve the issue here? Can anyone upload the dump file?
Any ideas?
Click to expand...
Click to collapse
Did you every solve this? I'm having the same problem.

How To Guide [TB-J716F] Flashing Pseudo_Global firmware (many languages inside)

If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Good Luck !

f1tm0t said:
If you not like ZUI firmware - you can flash Pseudo_Global to your tablet. I've tested this way and sharing it here.
Pseudo_global fw was built on ZUI, it has A11 inside and you never can to get some system updates - no one is doing them.
Your data will gone away.
YOU ARE WARNED !
And so:
I've tryed this on ZUI 14.0.127 with unlocked bootloader and active slot _a. Active slot can be checked with
Code:
adb shell /bin/getprop ro.boot.slot_suffix
and answer must be _a
If not, you need change boot slot with command in fastboot mode:
Code:
fastboot set_active other
And now you can reboot in EDL mode and start to flash all needed partitions from unpacked archive Pseudo_ROW_J716Fl.7z
You need unpacked ZUI 12.6.211 from lolinet https://mirrors.lolinet.com/firmware/lenovo/Tab_P11_Pro_2021/TB-J716F/ for working with QPST Partition Manager.
How it looks you can see in this video:
You must flash ALL partitions archive contains. Files in Add.rar not need, it for any case.
MANDATORY ! After flashing you need at first to boot in recovery and make reset to factory settings, it will format userdata. Without this action you can't boot.
Spoiler: IS
View attachment 5783891View attachment 5783993View attachment 5783995
Good Luck !
Click to expand...
Click to collapse
It was exactly what I was looking for and trying for days, but following your tutorial I still couldn't, it didn't turn on, I had to upload the rom 12.6.211 again. I wanted to leave it with multiple languages.

augustobfe said:
still couldn't, it didn't turn on
Click to expand...
Click to collapse
OK, I will re-check it in 2-3 days. Although I think you did something wrong.

f1tm0t said:
will re-check it in 2-3 days
Click to expand...
Click to collapse
Dude, I have some bad news for you. Your hands are crooked. That needs to be fixed.
My method works without fail. It only takes half an hour.
Try it again.
Spoiler: Look this:

[Solved] Doogee S89 - TWRP?

Hi,
A quick one. I'm having a problem rooting the phone. I've been attempting to follow a tutorial that suggests to root is simple just go to recovery mode and install magisk.zip ... however, not that simple. The device doesn't seem to find it.
So trying the manual way but can't seem to find an image for TWRP for my device. Any assistance appreciated.
----
Extra Info.
As suggested my main goal is to root the device, I really don't mind how. I'm not wedded to a given method.
KingRoot failed
KingoRoot failed (no Linux version :/)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Yep that's why I'm here. I believe there's a way to get an unofficial TWRP but I've no clue how. That said if anyone knows how I could root without it, that would be great too. I can't seem to locate boot.img
Thanks for responding.

Compile a suitable TWRP at your own:
Compile TWRP for Your Device
www.xda-developers.com

first step, as always, unlock bootloader. for rooting, no TWRP required, you're reading the wrong guide. official Magisk has installation instructions on github.

alecxs said:
first step, as always, unlock bootloader. for rooting, no TWRP required, you're reading the wrong guide. official Magisk has installation instructions on github.
Click to expand...
Click to collapse
It says get a copy of boot.img or init_boot.img. I can find neither. All indications are that I need root access to find it so that I can root.
Thanks for engaging.

use mtkclient to get boot.img

Turns out didn't need to do that.
Grab the rom from
Firmware,Service
Firmware,Service
www.doogee.cc
Extract.
Use the boot.img and the vbmeta.img. According to the magisk instructions from github (buried slightly), use don't use [_x] just `boot`. Seems to autofind the correct partition.
Not sure how to lock up the bootloader when done though as it leaves the device in an error state

AffectedCacti said:
Not sure how to lock up the bootloader when done though...
Click to expand...
Click to collapse
You don't!

AffectedCacti said:
Turns out didn't need to do that.
Grab the rom from
Firmware,Service
Firmware,Service
www.doogee.cc
Extract.
Use the boot.img and the vbmeta.img. According to the magisk instructions from github (buried slightly), use don't use [_x] just `boot`. Seems to autofind the correct partition.
Not sure how to lock up the bootloader when done though as it leaves the device in an error state
Click to expand...
Click to collapse
Lucky, your phone has stock firmware direct from the manufacturer. Just a reminder that you need to patch vbmeta.img when rooting with magisk if your stock firmware contains vbmeta.img, otherwise you will be soft bricked, I had this happen to me, luckily SP flash tool was able to reflash vbmeta in brom, since I had no access to fastboot.
If you have access to fastboot you can accomplish this with:
Code:
fastboot --disable-verification flash vbmeta "C:\path\to\vbmeta.img"
If you do not like I did a blank image will work, you can create it with:
Code:
python avbtool.py make_vbmeta_image --flags 2 --padding_size 4096 --output vbmeta_disabled.img
Here is a link to avbtool.py which only requires python to run: https://1drv.ms/u/s!AvFNhY9dpwLfhf5TJ3xmoYCQqYfHOA?e=aGLyqu
Make sure to replace the padding size with the size of your image. Then you can flash that blank image using whatever flash tool your processor comes with, for me it was SP Flash tool because I have an MTK processor.
I guess if you have your stock firmware and a manufacturer provided flash tool, it doesn't really matter if you brick your device though. Anyways, Cheers!

Wasn't sure what the hell vbmeta was in all fairness, but I did this along with the instructions provided by Magisk.
Thanks for the heads up!
I don't think Doogee provide a flashing too but it seems that they provide the roms, which naturally, includes a copy of the vbmeta.img.