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

[pls hlp] Unable to Root OnePlus 7 Pro

Hey Guys,
hopefully its okay to post my request here.
I am stuck rooting my OP7 Pro.
As you can see on below screenshots this where I try to start:
I have a GM1913 and I am on Oxygen OS 10.0.5.GM21BA:
I folowd this guide including the video tutorial: https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
Unfortunately I am unable to gain root.
Either I am ending up in a boot loop or I am able to boot into android but root is still missing and Wireless LAN isnt working.
These are the TWRP Files I was working with:
{
"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"
}
The Files 3.3.1-0 to 3.3.1-4 aren´t working anyway. after flashing them, I am just back at the bootloader. Only the unofficial 76 Version is working to get into TWRP.
If I am able to get into twrp, I´ll do the following:
1) flashing original boot.img to Slot A and Slot B (from here: https://androidfilehost.com/?w=files&flid=294300)
2) flashing the TWRP Zip File (only to the "active" Slot)
3) flashing Magisk 20.4 (also tried 20.1)
And then either I am stuck in a bootloop or in Android Wlan is missing and Magisk still not working.
Can please someone help me pointing at what I am doing wrong?

Wait a sec. If you have unlocked bootloader please boot to fastboot and do command: fastboot boot twrp_file_name.img on the latest TWRP that you can find: https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
Latest version and files you need are:
TWRP 3.3.1-79 Unified Unofficial Q by mauronofrio
TWRP 3.3.1-79 Unified Unofficial Installer by mauronofrio
after you boot to this recovery go and install recovery installer zip and later flash also package with Magisk 20.4
Voilla you have root + latest TWRP

Well.... just WTF?
Just done it as described by @SkubiDoo and it works...
So was the issue using old TWRP Files?
Anyway - Thank you very much for your help!

Looks like mate better to stick with this mauronofrio version.

root pixel 3a

Hi all
I acquired a Google pixel 3a.
I unlocked the bootloader, but can't root it with magisk manager.
So developer option enabled as well as debugging.
I downloaded the corresponding factory image to extract the boot.img
So I put it on my phone for the patch with magisk manager.
Then I transferred it to the platformtools folder of the SDK.
The pixel does not restart I have to flash the original boot.img.
PS: bootm.img and the file patched by magisk.
I did "./" because I'm on win 10
My build version QQ2A.200405.005
Thank you

What happens when you reboot after magisk boot image is flashed? I've read sometimes need to flash other boot area, in your case flash to boot_b.

dkryder said:
What happens when you reboot after magisk boot image is flashed? I've read sometimes need to flash other boot area, in your case flash to boot_b.
Click to expand...
Click to collapse
it doesn't start, that's why I reflash the original boot.
how to flash on boot b?

The command should be listed along with the others when you issue just fastboot. Or Google search. I've never had to use it so I don't have it in my memory

jerome8 said:
it doesn't start, that's why I reflash the original boot.
how to flash on boot b?
Click to expand...
Click to collapse
Can you just read FAQs???
Flash b - fastboot flash boot_b boot.img

St.Noigel said:
Can you just read FAQs???
Flash b - fastboot flash boot_b boot.img
Click to expand...
Click to collapse
I tried everything but A and B it doesn't work.
On the B I do it restarts normally but I am not rooted.
Maybe I should flash on A and B?
{
"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"
}

Try fastboot flash boot --slot all magisk_patched.img
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:10 PM ---------- Previous post was at 08:09 PM ----------
Or whatever you named the image
Sent from my [device_name] using XDA-Developers Legacy app

This also works in Android R
Sent from my [device_name] using XDA-Developers Legacy app

thank you it worked I flash the 2 boot A and B.

OTA still working?

I don't do OTAs maybe somebody else can help
Sent from my [device_name] using XDA-Developers Legacy app

Android 12 Beta GSI

Has anyone tried installing the Android 12 beta GSI using the Essential provided vendor and boot images for Android 11?
This phone is my daily driver and I am hoping to try it out over the weekend. Wanted to see if anyone had tried already.
Thanks!

There's a GSI link in MATA Releases TG group.
https://downloads.statixos.com/gsi_gms_arm64-exp-SPB1.210331.013-mata.zip
{
"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"
}

Darkside1984 said:
There's a GSI link in MATA Releases TG group.
https://downloads.statixos.com/gsi_gms_arm64-exp-SPB1.210331.013-mata.zip
View attachment 5316695
Click to expand...
Click to collapse
any per-requisites to installing this rom? thkq.

I tried installing the official Google Android 12 GSI and it did not boot. I reverted back to stock. Will give the statixos version a try later.

The StatixOS "release" successfully boots Android 12, but it does not recognize the sim card slot... just thinks the sim slot is empty.
That said, the MATA zip file from StatixOS includes: boot.img, system.img, and vendor.img.
Reboot to bootloader
fastboot getvar current-slot (for this example, let's say it is "slot a")
fastboot flash vendor_b vendor.img
fastboot erase system_b
fastboot flash system_b system.img
fastboot flash boot_b boot.img
fastboot set_active b
fastboot -w
Reboot
NOTE:
The system.img included in the StatixOS zip file is the Google "gsi_gms_arm64-exp-SPB1.210331.013-7333779-0cf2eba2" system.img... apparently renamed.
The vendor.img and boot.img are the files that allow Android 12 to boot.
The Essential vendor-QQ1A.200105.088.img and unsigned-new.img (the boot file) do not allow Android 12 to boot. This could be an Android Verified Boot issue. The Google beta includes vbmeta.img, which removes the AVB requirement... but Essential doesn't have a vbmeta partition.

The StatixOS "release" was updated on 23 May.
Android 12 boots, but the sim card slot is still not recognized and Settings/Mobile network is grayed out.
I have tried a couple of other sim cards without success.
So, thanks to the dev at Statix for doing this work.
Release notes and changelog would be helpful.
If the sim card problem is an issue for the A12 Beta GSI build, it hasn't been flagged by Google... but in the OnePlus 7T forum there is this: "Phone app force closed . Sims detected but mobile is not working (data+phone call)" .
https://forum.xda-developers.com/t/android-12-beta-gsi.4279087/post-85041521
If the problem is in the vendor/boot files, then comments from the dev would be great.

beta 2 is out ..
devs of StatixOS have also released an update at
https://downloads.statixos.com/Android%20S%20mata/gsi_gms_arm64-exp-SPB2.210513.007-mata.zip
big thanks to them

potatohead said:
beta 2 is out ..
devs of StatixOS have also released an update at
https://downloads.statixos.com/Android%20S%20mata/gsi_gms_arm64-exp-SPB2.210513.007-mata.zip
big thanks to them
Click to expand...
Click to collapse
Did you try it out?

How do we install?

hammer7t said:
Did you try it out?
Click to expand...
Click to collapse
potatohead said:
beta 2 is out ..
devs of StatixOS have also released an update at
https://downloads.statixos.com/Android%20S%20mata/gsi_gms_arm64-exp-SPB2.210513.007-mata.zip
big thanks to them
Click to expand...
Click to collapse
Did it solve SIM problem ?

potatohead said:
beta 2 is out ..
devs of StatixOS have also released an update at
https://downloads.statixos.com/Android%20S%20mata/gsi_gms_arm64-exp-SPB2.210513.007-mata.zip
big thanks to them
Click to expand...
Click to collapse
Didn't work, I tried it

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: