Deep TEST fot OPPO RENO ACE(unlock bootloader) - Oppo Reno Ace Questions & Answers

Deep TEST fot OPPO RENO ACE(unlock bootloader) - Oppo Reno Ace Questions & Answers

OPPO's official website provides users with an official way to unlock bootloader.
coloros link:
https://bbs.coloros.net/graphic?id=1498611
you need to install the deeptest.apk to submit unlock request.
The application must meet all the following conditions:
1. The time to market must be more than 3 months;
2. No application record within 60 days;
3. The last consecutive login time of the OPPO account on this machine exceeds 60 days;
4. The number of in-depth test users has not reached the quota limit;
5. Non-government enterprises and operators customize mobile phones;
6. Support mobile phones listed in mainland China.
Unfortunately, there are currently no available quota.But if you want , you have to register an oppo account,and login time should more than 60 days.

So does this mean we can install custom rooms?

So... Hey guys,
I just wanted to let everyone know that I was actually able to flash the GSI from the link below on my OPPO Reno Ace:
https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-10-0-quack-phh-treble-t3992559
I am super new to all this, but I decided to take the risk anyways because I really wanted to get away from ColorOS. Luckily it worked out to the point that the phone seems functional so far (just flashed it as of writing this).
Disclaimer: Do this at your own risk! I am not responsible for what happens to your phone for following what I did. Please think twice before trying! Also remember to back-up your phone first!
Before I continue on how I got it to work, I got the Reno Ace Gundam edition. Not sure if that makes a difference but I thought this should be mentioned. Also since I couldn't find a version of TWRP for the Reno Ace; I followed the instructions on how to flash without it.
Here are all the main links I used:
Walkthrough for Deep Test app: https://forum.xda-developers.com/find-X/how-to/guide-how-to-apply-deep-testing-pafm00-t3888013
GSI: https://forum.xda-developers.com/project-treble/trebleenabled-device-development/aosp-10-0-quack-phh-treble-t3992559
Flashing Instructions and "vbmeta.img": https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
Extra Links in case of weird trouble. Hopefully you won't need it:
Google Usb Driver: https://developer.android.com/studio/run/oem-usb#InstallingDriver
How to manually install Google USB Driver: https://visualgdb.com/KB/usbdebug-manual/
Useful Key Word: Kedacom USB Device
*** Backup your phone before going forward.
Getting the Deep Testing app:
Now first, you do need to sign-up for an OPPO account. The link from the OP will take you to their site and you can sign-up from there.
- You will be required to login to your OPPO account in order to use the app.
- The file you download is named "Reno Ace深度测试.apk".
- Add ".apk" to the end of the filename if it's not already there. DO NOT rename the file.
- Once logged into your OPPO account on your phone, you stay logged in so you don't need to worry about actively logging in everyday.
- Next, follow the instructions on how to use the app from the Deep Test thread.
- Keep trying until your submission gets accepted, then the hardest part begins: you...wait...
- Once approved, it took ~2 days for me to be able unlock.
Make sure you have ADB ready on your computer:
- There are plenty of guides on it, so I'll just leave a link here; honestly I forgot the specifics already: https://www.xda-developers.com/install-adb-windows-macos-linux/
Steps:
- Prepare your GSI: You can look for other GSI(s), but from my research it seems safest to get it from here first; before trying others: GSI thread
- This link explains what GSI are and how to choose which one to get.
- *Make sure to extract the ".img" file from the ".img.xz" zip file.*
- Download "vbmeta.img" from "Troubleshooting Tips" of the "Flash GSI without TWRP" section of the How to Flash GSI Guide.
-After you've extracted the ADB folder, keep the files (.img files) you intend to flash within the "platform-tools" folder.
*Noob tip lol: Clicking on the folder address and typing "cmd" is the quick way to open command prompt within the directory.*
- *** There are some unique steps for the Reno Ace, if not all OPPO phones, due to the Deep Testing app. ***
- After you get your approval, note that if you press the "Start Deep Testing" text you will be immediately put into fastboot mode. SO DO NOT PRESS IT NOW.
- Make sure you have OEM Unlock and USB Debugging enabled within Developer Options. Then connect your phone to your PC and set it to transfer files.
- On computer, open command prompt within the "platform- tools" folder. Enter the command "adb devices", when you see your device ID and "device" next to it, this means the phone has been connected. (If a prompt on your phone pop-ups, tap the "Always allow this computer to USB Debug" and "Allow". This is just what I did, not sure if it's necessary).
- Now go into the Deep Testing app on your phone, tap on "Queue status" and then "Start Deep Testing".
- You should see the images from this Oppo Find X tutorial, on your phone. Landing on the screen with the big green "Start" on top.
- Once you're here, enter "fastboot flashing unlock" into ADB and you'll move on to the next screen where you select "Unlock the Bootloader".
- After confirming, your phone will factory reset itself, and reboot into ColorOS again.
- Check to make sure your phone is connected to adb.
- From here on you follow "Flash GSI without TWRP" part of the How to Flash GSI Guide starting at step 2. If you have your ".img" files in the "platform-tools" folder then you can skip step 3.
- Before step 5 you need to flash the vbmeta: fastboot flash vbmeta name_of_vbmeta.img
Then flash the GSI ".img" file with fastboot -w flash system name_of_system.img.
(The comments there mentions that the "-u" is incorrect and should be "-w", which worked for me.)
* Important: without flashing "vbmeta.img" you'll be stuck in a boot loop because the phone prevents you from booting into the GSI. If this does happen, hold down Volume Down and Power until the phone vibrates to boot back into "fastboot mode". Enter "fastboot device" in ADB to confirm the phone is connected, and start over from step 4 in the How to Flash GSI Guide. *
- Once you finish step 6 your phone should boot into the GSI.
Hopefully this proves useful. I'm no expert, I simply found my way around things.
I honestly have no idea where to go from here, Magisk? LineageOS? If anyone can give me some pointers, that would be very much appreciated.
Things that are not working for me:
- Can't setup In-screen Fingerprint sensor

I got a twrp that works just finished rooting with help of the vbmeta above

Darktron13 said:
I got a twrp that works just finished rooting with help of the vbmeta above
Click to expand...
Click to collapse
Would you mind giving a link to the twrp you found? I was searching around for one as well, but I couldn't find anything I felt comfortable with.
Also did you also flash a gsi? If you did, I was wondering if your headphone jack is working. Mine doesn't work anymore; the phone seems to recognize it, but no headphone icon shows up and sound plays through the speakers only.

falsewind said:
Would you mind giving a link to the twrp you found? I was searching around for one as well, but I couldn't find anything I felt comfortable with.
Also did you also flash a gsi? If you did, I was wondering if your headphone jack is working. Mine doesn't work anymore; the phone seems to recognize it, but no headphone icon shows up and sound plays through the speakers only.
Click to expand...
Click to collapse
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.

Darktron13 said:
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.
Click to expand...
Click to collapse
Thanks for the quick reply. I think I know where that's from. I believe that it's from here:
http://www.romleyuan.com/lec/read?id=348
Let me know if it looks familiar. Great to know that it works!

falsewind said:
Thanks for the quick reply. I think I know where that's from. I believe that it's from here:
http://www.romleyuan.com/lec/read?id=348
Let me know if it looks familiar. Great to know that it works!
Click to expand...
Click to collapse
Yes looks familiar it should be that one the twrp itself has Chinese and English languages.
Formatting and wipe is working otg also haven't really tested alot also you can flash ozip stock rom with it if you plan on rooting the boot gets corrupted but with the vbmeta bypasses it.
if you plan on installing V4A don't do the magisk module will bootloop have to look for the rootless V4A. (also need AML and the sound is great)
also don't change to f2fs i did it and the phone make weird noises went back to ext4.

Darktron13 said:
Yes looks familiar it should be that one the twrp itself has Chinese and English languages.
Formatting and wipe is working otg also haven't really tested alot also you can flash ozip stock rom with it if you plan on rooting the boot gets corrupted but with the vbmeta bypasses it.
if you plan on installing V4A don't do the magisk module will bootloop have to look for the rootless V4A. (also need AML and the sound is great)
also don't change to f2fs i did it and the phone make weird noises went back to ext4.
Click to expand...
Click to collapse
Awesome! Thanks for the info, it will come in handy later on. Still just learning and getting familiar with all this.

A follow up after a couple of days of using phhusson's gsi.
Overall the phone is functioning very well. Generally smoother than on ColorOS.
Things to note:
- Battery life is good, same if not better than on ColorOS.
- Fast charge works. Full charge in around under 30 mins.
- Wi-fi works and Data works.
- Phone and Text work.
- Camera works.
- Headphone jack won't work until you go into the treble-settings (Phh Treble Settings) -> Qualcomm features -> and turn on "Use alternate audio policy"; then restart your phone. Then it will work again, although no headphone icons will appear. I don't use Headsets, so I couldn't test if that works as well.
- The phone will be rooted by default, so certain apps can't be downloaded, or used. (Root can be removed, but it doesn't seem like a good idea.) There are ways around this, but I didn't dive very deep into it.
Problems to note:
- In-screen fingerprint sensor can't be used.
- No auto-adjusting brightness.
- Brightness is a lot brighter than in ColorOS. Even lowest brightness is bright.
- Auto-Rotate is very sensitive and won't stay landscape when phone is flat on a table.
- Certain apps may not be full screen if you use the new gesture navigation. (Shadowverse)
- I didn't test Bluetooth or NFC. I don't use them much, or at all, so I'll follow up on that when the time comes and no one else has mentioned anything on them yet.
That should be all for now. Honestly very happy with the move. Hope this helps.
**Just an extra reminder that this is my experience with this specific gsi. **

Is this still available? I can't download the APK from Oppo, I logged onto my 'heytap' account but the download link just brings me to my account information.

twgib said:
Is this still available? I can't download the APK from Oppo, I logged onto my 'heytap' account but the download link just brings me to my account information.
Click to expand...
Click to collapse
I've reply back on the other post about Oppo Reno which model you have Ive posted both apks

Darktron13 said:
I've reply back on the other post about Oppo Reno which model you have Ive posted both apks
Click to expand...
Click to collapse
Thank you so much! You're too kind!

Nice to see some progress on this phone it has so much power and potential!

Help
Darktron13 said:
Haven't install any gsi just have ColorOS 7.1 C.27 I cant remember where I got that twrp from all I know is a Chinese twrp think I found it on some baidu drive I was just waiting on approval from the in depth testing app.
Click to expand...
Click to collapse
Please can you share the twrp, I have the device but it is really hard for me to download it from baidu, if you were already kind to share it, you would help me a lot to test the phone, thanks in advance. Sorry for my English, it's not very good.

is there any info about what stock rom you're using? i was trying to install Phh's AOSP gsi thourh fastboot, the system-quack-arm64-aonly-vanilla.img , and only to get stucked at the OPPO logo, i'm using C26 curently

åˆ˜æ¬²æ°lol said:
is there any info about what stock rom you're using? i was trying to install Phh's AOSP gsi thourh fastboot, the system-quack-arm64-aonly-vanilla.img , and only to get stucked at the OPPO logo, i'm using C26 curently
Click to expand...
Click to collapse
ok, i figured it out. Ace is a System-as-root device,so i need to use a/b img files

I wanna root my phone

OPPO Reno Ace Twrp.7z
1 file sent via WeTransfer, the simplest way to send your files around the world
we.tl
[这是color7 可以用的twrp 如果你们可以进去下载的话

xdsfh said:
OPPO's official website provides users with an official way to unlock bootloader.
coloros link:
ColorOS 12_话题_OPPO手机官方社区
ColorOS 12延续“无边界”设计理念，为你带来更懂你的智慧操作系统！
bbs.coloros.net
you need to install the deeptest.apk to submit unlock request.
The application must meet all the following conditions:
1. The time to market must be more than 3 months;
2. No application record within 60 days;
3. The last consecutive login time of the OPPO account on this machine exceeds 60 days;
4. The number of in-depth test users has not reached the quota limit;
5. Non-government enterprises and operators customize mobile phones;
6. Support mobile phones listed in mainland China.
Unfortunately, there are currently no available quota.But if you want , you have to register an oppo account,and login time should more than 60 days.
Click to expand...
Click to collapse
URL not found

Related

[AIO] Prepare your device (and your knowledge) for any GSI

Preliminary operations/infos
First of all: what's Treble?
Find it out here.
How do I obtain my bootloader unlock code?
GO HERE, FAST!
Huawei officially ceased the unlocking service.
How do I get Treble on my device?
At the moment of this write down, EMUI it's still in private BETA.
The only chance to obtain it it's to follow this guide CAREFULLY.
What if I want to revert to EMUI 8/5?
Follow the steps described in the guide to get treble on your device using EMUI 8 files if you want to revert to EMUI 8, or EMUI 5 if you wish to revert to it.
The road it's long...
So, you're sitting there, not understanding why there are so much ROMs in this section and why you shouldn't use the ones appearing in Treble-Enabled Device Development since you worked so hard to get Treble on it.
Let's try to answer a universal question.
What's the difference from the "standard" GSIs and the ROMs in this section?
Well, the ROMs here were made keeping an eye on the "optimization per-platform" concept, basically tracking down some proprietary stuff inheriting them under /system .
**WHAT FOLLOWS ARE PERSONAL OPINIONS**
I honestly think, that we should cut off this approach.
Inheriting stuff under /system has no more sense.
Am I saying that what I did till now had no sense?
Yes.
The whole Treble concept relies on moving away from system, any vendor related stuff.
So why in the hell should we inherit proprietary stuff in our system partition again?
When we have other ways to don't mess with it?
The only stuff that still "deserves" to have something to do with /system it's the Huawei Camera.
Everything else, belongs to /vendor.
Furthermore, our goal, as developers and users, should be to track down specific-platform bugs and report them.
Co-operation is the sake of open-source and the key to success in a wonderful GSI experience for everyone.

Is my device ready to use a "standard" GSI?
Pretty much.
Huawei doesn't ship any overlay under /vendor in our PRA, because it's inherited in EMUI under /system.
But, you can follow this guide, to include the needed overlay to be fully GSI-ready.
Also, you need this thread too to fix offline charging on your Huawei device.
Known Bugs on GSI and "specific-GSI"
NFC has been an annoying issue all along the development process on some Huawei devices.
But this flashable zip, seems to solve the issue on our PRA.
Indeed it needs more testing.
Available tools/software for your PRA
ADB and Fastboot
TWRP
MindTheGapps
Huawei Camera Magisk
OEMInfo (TWRP backup)
HuRU
Stock Ramdisk (ramdisk partition)
Stock Recovery (recovery_ramdisk partition)
Specific-GSI available
Lineage OS https://forum.xda-developers.com/p8...t/rom-lineage-os-huawei-p8-lite-2017-t3787193
CrDroidhttps://forum.xda-developers.com/p8.../rom-crdroid-4-2-huawei-p8-lite-2017-t3785615
AospExtendedhttps://forum.xda-developers.com/p8.../rom-aospextended-5-4-huawei-p8-lite-t3778938
AOSPhttps://forum.xda-developers.com/p8...ent/rom-aosp-r23-huawei-p8-lite-2017-t3779115
Resurrection Remix 6https://forum.xda-developers.com/p8lite/p8-lite-2017-development/rom-rros-pra-t3774444
SlimRom 8
AICP
Specific GSIs are now discontinued.
Go to the Treble Enabled Development sub to get some ROMs to flash!
NOTE:
This ROMs will be discontinued in a couple of weeks, since the installation of the overlay (previously highlighted in the paragraph "Is my device ready to use a "standard" GSI?") will give access to a full fledged GSI experience without the need of specific GSIs.
Custom kernels
Labyrinth

Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
If this isn't clear enough, please, check this contribution.
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
From 16.6 version, Magisk it's fully working.
Please, refer to this thread for a correct installation.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
adb logcat > file.txt
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer

Hey you!
If you're reading this message I want you to help this community.
Share your thoughts about this posts or post your un-answered questions below.
The more we share, the best experience we'll get.
Also, please respect my work.
If you do integrate some of this infos in your thread/website or whatever, add me in the credits.
Furthermore, feel free to join us at @GSI_HI6250 on Telegram, we're funny people, I swear.
Is this non-clear somehow?
Or you just need help?
Fill the help form below.
Device Variant:
Device Firmware:
Is your device rebranded?:
How frequently this issue happens?
Is this happening now?
Describe the issue:
Describe steps to reproduce the issue:
Attach logcats/full bugreports as described on the paragraph "How to report bugs"
Or simply join the telegram group.
Peace.

Dil3mm4 said:
Kaioken reserved
Click to expand...
Click to collapse
Super Saiyan reserved
Lol

Dil3mm4 said:
Disable encryption to use Adoptable Storage (or just because you can)
open /vendor/etc/fstab.hi6250
make a backup just in case
find "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
remove ",fileencryption=aes-256-xts:aes-256-cts"
factory reset via stock recovery
Playstore download pending fix
Access https://play.google.com/apps/testing/com.google.android.gms/join
Apply for the beta
Update Google Play Services to the beta
Profit
Magisk keeps crashing?
Turn off its "Check for update feature" and praise for the arrival of a new Magisk version.
How to report bugs
Boot problems:
Please do dump /splash2 partition and sys/fs/pstore content via adb pull in my TWRP.
Quirks on booted system:
Please take a full bugreport when the bugs happens via Developer Options
or
adb logcat > file.txt
send file.txt to the developer
Click to expand...
Click to collapse
THAT WORKED. FINALLY 8.1 WITH BOOTLEGGERS GSI, 128GB micro SDXC as INTERNAL. I AM HAPPY
for beginners:
boot after working rom in twrp
go in advanced
go to file manager
go to /vendor/etc/
open file "fstab.hi6250" (after copying with and having a recovery of it, open with notepad++ or something else)
there should be a line with: "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inlinedata,inlinexattr wait,check,fileencryption=aes-256-xts:aes-256-cts"
erase the part: ",fileencryption=aes-256-xts:aes-256-cts"
save
erase the original fstab.hi6250 file in vendor/etc
and put the new fstab.hi6250 file in
reboot in bootloader
flash stockrecovery.img
reboot recovery
factory reset in stock recovery
reboot
DONE.
now you can see the SD card as internal and use for apps.

Need your help
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them

Mister746 said:
Hey OP,
Thanks for all your work. Really a big fan.
There is a problem I've noticed on most of the treble roms. After using apps for a while, they begin to FC.
Love your roms and would like to continue using them
Click to expand...
Click to collapse
Updated last post, please submit the infos needed via that form.
Thanks.

Hi, i am experiencing a weird bug on every GSI, specifically, snapchat video recording is fine and smooth, but after tapping on the "send" button it says "failed to add" and doesnt even give a chance to resend the same snap. It happens on all treble roms i've teted so far (i tested every specific GSI for PRA, and some openkirin and otger ones). @dill3m4 do you have any idea how to fix it? I hope there is a way to do a flashable zip or something like the NFC fix. Once i get back home (2-3 days) i will post some logs, in the meantime, can someone please confirm if the issue persists, and gather logs? ?

can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/

jedtan025 said:
can i use this method in stock firmware(rooted) because i cant see any fstab file in vendor/etc/
Click to expand...
Click to collapse
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?

neondragon1909 said:
Just making sure but you are on emui8 right? Also are you checking with a file manager in Android or are you searching in twrp?
Click to expand...
Click to collapse
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file

jedtan025 said:
im searching in twrp bro. bro question. im using pra lx2 oreo firmware. and im wanna go back to nougat. it is possible? i got the firmware now but dont know how to flash nougat. dload failed. and i cant use hurupdarer bcos nougat firmware only has 2 zip file
Click to expand...
Click to collapse
I couldn't find the file using TWRP either. Had to use root explorer to find and edit the file. As for hurupdater, I'm not sure if it's the same for your region, but for pra-la1 there were 3 files.
And as for the the 2 files, I successfully flashed using the updater with only the update.zip so try updating anyway. If that doesn't work, use the eRecovery

Update:
Added Magisk news;
Added stock PRA ramdisk

UPDATE:
Added Offline Charging Fix in post #2
Added references to Treble Enabled device development;
New Huawei Magisk Camera;

Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.

cyprian99 said:
Hello,
I'm having problems finding the download links in the guide to obtain Treble, I've searched here and clicked on the link to the guide but there i can't find it eather.
Click to expand...
Click to collapse
Obtain what?
Treble roms?

Yay! Emui 8.0 has arrived on my c432 pra-lx1 (b360) . Everything is perfect.

The guide to get treble is unclear, how can the very first step be to download update.zip? I did and now i have a trojan, thanks a lot

How to unlock bootloader? Now the Huawei site is unavailable
Wysłane z mojego PRA-LX1 przy użyciu Tapatalka

[Treble GSI] [Umidigi One Max] GSI Experiments

Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10
Apparently it works as shown here: https://forum.xda-developers.com/showpost.php?p=80319007&postcount=13 credits to @4ctiv_
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Tethering doesn't work with data ON !
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
NFC doesn't appear at all. There is a fix with magisk tho ! See here (NFC4PRA)
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone

Make sure to check out my guide on installing GSIs at https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521/

I downloaded system-arm64-ab-gapps-su.xz, extracted the file, booted into TWRP, did a full wipe, and installed "image" system-arm64-ab-gapps-su.img. TWRP asks which partition to install it to. I selected "system". However, after install I go to reboot, and TWRP complains there is no OS. Am I missing something?
I did a complete backup in TWRP of all important partitions first (nvram, modem, system Etc.), so going back to my stock setup was not difficult. Those trying this, backup all important partitions from TWRP on to microsd!

For everyone, make sure you download AONLY images, not AB !

_cab13_ said:
Now that the Umidigi One Max has TWRP, it is now very easy to flash GSI ROMs.
I will try to keep track of different GSI that works (or not !) here, alongside with bugs. Testers are welcome !
I highly recommend GSI based off phhhuson's work, as he did great job to fix MTK issues. Some other GSI may work better. We definitely need testing !
10 Q Beta
Beta 4 : Probably not working, as our device is not system-as-root (but is VNDK isolation compatible)
Still needs testing
9.0 Pie
phhusson's AOSP :
Everything works as expected. Notification bar is of the wrong size, may need to create a patch for it. Wifi access point doesn't work.
Camera is good ! All cameras are recognized. Fingerprint sensor OK. Torch not working under 15% like in stock, this seems like a hardware thing.
Ongoing calls and SMS will not work first boot. Just reboot and it'll work.
Magisk 19+ doesn't show root prompts. Fix here
Pixel Launcher crashes, but it seems that it's the only google app that doesn't work. Google Phone works.
ctsProfile doesn't pass. Using MagiskHidePropsConfig fixes the issue, but choosing "vendor fingerprint" bootloops
Testers needed
8.1 Oreo
Testers needed
Do not hesitate to post what you find or your testing.
NOTE : Installing a GSI can be done via 3 methods : TWRP Image Flash, SP Flash Tool, or fastboot (needs unlocked bootloader)
For the first two methods, unlocked bootloader is not required ! TWRP can be flashed via SPFT aswell.
Enjoy your beautiful and modded phone
Click to expand...
Click to collapse
I posted this in another forum, but for the life of me I do not know what is causing this issue. I installed RR rom located here:
https://get.resurrectionremix.com/?dir=gsi/
system-190120-arm64-aonly-vanilla-nosu.img
I also install, Gapps (pico), and Magisk.
It runs great, for the most part. However, if I start streaming a video from any app or start streaming music, after a short amount of time my Umidigi One Max:
A.) Announces, "Powering Down"
B.) Boots directly into TWRP
C.) If I reboot, it again boots directly into recovery. Almost as if the partition became corrupted.
D.) Try to recover a backup I made in twrp, reboot, again boots straight into recovery.
E.) If SP Flash can communicate with the phone, I can usually push all the stock images back to the phone. If not, I have to push the images via fastboot with my Ubuntu PC.
If I do any other CPU intensive task under a GSI ROM, it doesn't have this issue, only when I stream video. I haven't tried any games to see if it causes this behavior.
I have tried multiple GSI Roms located here too, same problem:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
I do not believe the device is overheating, it's usually around 32-34C from the TWRP menu at that point. I really like the RR Rom, but if I cannot figure out what is causing this, I'll have to stray away from GSI for now.
As a sidenote, this issue of the device suddenly powering down after starting to stream a video, does not happen with the stock ROM. I am kind of at a loss on this one.
Weirdest thing I have experienced running a custom ROM.

Yeah it happened to me sometimes as well... The phone goes straight into recovery and then never goes to system again. I haven't found the cause of it.

Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)

phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.

w1lh3lm3d said:
Did you try the NFC fix for the one pro (I got it from the umdigi forum one Pro and then the thread custom ROMs)
Click to expand...
Click to collapse
I posted a fix that works. Here it is if you didn't see : https://forum.xda-developers.com/p8...pment/flashable-nfc-kirin655-devices-t3811916
tomprc said:
phhusson's AOSP is mostly good. But I noticed the wifi often gets disconnected and has performance issue too.
Click to expand...
Click to collapse
I don't get any performance issue. The only issues is that some ongoing calls doesn't come, and sometimes 4G totally glitches out. Other than that it's pretty much all.

@ _cab13_
i cant find the vendor folder in twrp in the mount section or in the file manager.
what have i done wrong? ok i started from scratch and then it worked porfectly
thx you for your work and help

Engineering mode access or work around
On the 9.0 ROM I cant seem to access engineering mode via the keypad, I need to sort the handset speaker out. Is there any other way to access it or some way of tweaking the voice settings through the shell?
Any help would be appreciated.

Please help
I'm trying to get the new phh Android q to boot and and I'm a newbiew

Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )

On Phh's 9 v119 Is the headphone jack sensor working for anyone. (If so how)

4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
Click to expand...
Click to collapse
did you use the a only or ab image?

I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!

seiyria said:
I've tried flashing multiple android 10 GSIs from the phhusson GSI wiki list.
I've tried phhusson's AOSP ROM, CAOS, Lineage 17.1 and POSP. It seems like they all freeze at the splash screen and get stuck loading forever (confirmed, I left it on all night last night). I've tried disabling force encryption, I've tried not installing magisk. Not really sure where to go from here with Android 10.
I've also tried Android 9 with much more success: it boots, it works, but the only thing I can't seem to get is NFC. Has anyone found a way to get NFC to work on any android version with this device? Or do I have to go back to stock android 8?
Thanks!
Click to expand...
Click to collapse
I'm in the same boat bro. I've just tried both the latest phhusson AOSP 10 ROM as well as an older version of the same ROM, and both time I get caught in a loop after install. Completely wiped beforehand, tried installing with and without Magisk/Disable-Force-Encryption. Going to have to bring it back down to Android 9. I wonder how 4ctiv_ got it working?

so first you have to no encryption then erase and format data
flash android 10 arm 64 a without gapps build (image) to system i use havoc 3.5 and everything exept nfc works
then install gapps (it failed for me so i had to resize system in twrp and install gapps again
last step is to flash the custom phhson magisk
then just reboot wihout wipping

Thank you so much for your work...
Hi, I'm a long time Android user and I used to code apps, if I can be of any help please let me know but I'm now disabled wheel chair user with dystonia so I find it extremely difficult to type now so I use voice to text... I really enjoy using the umidigi one max it has the storage and usability of a much more expensive phone, also functionally for me the wireless charging and NFC make my life so much easier as I find cables akward and payments at shops much easier.
I read about the Treble programmea while ago and recently read this article and if it is possible to get the NFC working on this update, I will be so greatful as it will extend the life of this great phone for me.
Good luck with your work and thank you in advance.
4ctiv_ said:
Just booted from Android 10 GSI 200 c. by PhhTrebble without any problems (flashed latest stock before). Just to let you guys know Will update bugs and working stuff tomorrow.
[Update]
Missing features
_________________
NFC missing and magisk patch did not work for me
Media playback in for exampel youtube/instagramm/reddit etc. not working in apps but in browser it workes.
Bugs:
_________________
Sometimes apps crash
SD-card "has to be formated to use" // I did not try formating yet
Sometimes Youtube playback fixes itself if you tab out and go back to the video or if you open the help page of YT (top right corner question mark symbol) and go back to the video
Be aware that the 200.c phh gsi i used is still in development but as you can see it is totally capable to use as daily driver
[UPDATE 2]
- Missing features is still NFC
- In PHHSolution "AOSP 10.0 v211" mediaplayback got fixed (Tested with "system-quack-arm64-aonly-gapps.img.xz" )
Click to expand...
Click to collapse

Ulefone Armor 3W/3WT

Hello everyone.
This is my first thread, I hope not to break any rules.
Ulefone launched the new Armor 3W and 3WT, like our 3 and 3T, it does have the exact same look and same specs except for the CPU and RAM, our 3 and 3T have the P23 and 4GB of RAM, the new Armor 3W and 3WT have the P70 and 6GB of RAM.
Does any of you had the change to get one and test it out?
I'm curious if the TWRP available to 3 and 3T are compatible with the new 3W/3WT.
Thank you!

Have you found out anything yet?

Jim1348 said:
Have you found out anything yet?
Click to expand...
Click to collapse
Not yet, already bought the Armor 3WT from Banggood and they'll ship on October 13 if not mistaking.
I was hoping for someone that once they have the new 3W and 3WT they will test if the tools available for Armor 3 and 3T will be the same for Armor 3W and 3WT.
It's exactly the same models except for the CPU, RAM and OS, 3 and 3T have Oreo 8.1 and the Armor 3W and 3WT have Pie 9.0.

I'm waiting to buy a 3w also by Aliexpress. I'm searching to see bootloader, twrp and root unlock issue but it's hard to find. I don't know if because it is still launch ..... I hope that in the near future someone can unravel these mysteries

After almost a month of use I found many bugs software related but didn't find fix yet... Bluetooth keeps randomly disconnecting (I think this is Pie related and not Armor 3WT), the build in "firewall" doesn't work on stopping apps from access the internet, and neither does the build in "power saver" feature, regardless of having such apps on whitelist some of them keeps getting killed in background

I have had the Armor 3W for about a month now, after purchasing it as a replacement ffor my previous Armor 3 which wasn't too happy with 80kg landing on it from a height of around a metre. (Didn't break anything externally, just started behaving very oldy!)
The only issue I have found so far is that after a random period of time (from hours to days) the proximity and light sensor stop working. This is frustrating when making/receiving a call due to the screen not turning off. (Yes, some people still use mobile phone to make phone calls! )
I do not believe this to me a hardware issue as it is resolved, at least temporarily, with a power cycle.... (Think Roy from "The IT Crowd": Have you tried turning it off and on again?) It also sems to have been a semi-common on a number of other phones running Android P.
The proximity calibration app, I thought had worked as initially it seemed better, but the sensors have resorted to their old ways.
I have emailed Ulefone Support, but due to previous experience I won't be holding my breath, blue is not really my colour.
Has anyone else experienced this issue with the Armor 3W/WT, and if so does anyone have a solution?
TIA,
Damien

Just got my own Armor 3WT and can confirm the proximity sensor issue. After about a day it stops working and gets stuck on 0 distance which causes the in call screen to go black. Reboot fixes it as mentioned above. For me the built in firewall or "network manager" works as intended from a few short tests. My build number of the rom is "Armor_3WT_RF1_EEA_V01_20190919-1954". Bluetooth also seems to work fine however i have only tested it with an OBD scanner and not for audio or wireless headphones...
Any news about twrp? All i could find are some fake websites with no download link. The bootloader unlocks with "fastboot flashing unlock" which does a factory reset and i tried booting the UMIDIGI S3 Pro twrp as the specs looked pretty close (same soc and ram and resolution) but it does not boot into recovery at all.

Hello users of this funny phone ...
I have a questions
did You tried apply any ROOT ? like KINGROOT or any familiar without TWRP ?
this smatphone have indicator led ?? ( and blinknig on received unread mails/sms/ and other events ?
what about quality of pictures ? in daylight and flash light and speed of focus ?
Thx for answers .

noki_tel said:
Hello users of this funny phone ...
I have a questions
did You tried apply any ROOT ? like KINGROOT or any familiar without TWRP ?
this smatphone have indicator led ?? ( and blinknig on received unread mails/sms/ and other events ?
what about quality of pictures ? in daylight and flash light ?
Thx for answers .
Click to expand...
Click to collapse
I personally didn't try KINGROOT because the last time i tried it was annoying to deal with and remove. I did look into patching the boot.img with magisk to avoid the need for twrp but first we need the stock rom download which ulefone does not provide yet (probably because the phone is so new). It has a RGB led on the top right. Pictures of the front camera are poor but usable in high light and the back camera is good with flash or light and "medium" when darker. By that i mean that you are able to see the general things in the image when dark but don't expect to be zooming in or reading text without flash.
Another thing worth noting is just how LOUD the speakers are. Watching videos indoors on the lowest volume is already slightly too loud when the room is quiet and notifications/calls are also extremely loud anywhere above the lowest setting. It is much louder than any other phone i ever tried.
EDIT: The camera does allow manual controls of everything including shutter speed with another manual camera app.

Thx a lot for this information ,
has RGB led , but its working as indicator of messages or only for battery power loading ?
when ROOT will be available I will buy this phone probably ... (this is mandatory requirement with all my smartfones , i cant imagine have smartfone without ROOT)
aaa one more question i forgot
how sim cards and exernal memory is applyiable ? SIM + SIM + MemoryCard ,
or hybrid SIM + SIM / SIM + MemoryCard

noki_tel said:
Thx a lot for this information ,
has RGB led , but its working as indicator of messages or only for battery power loading ?
when ROOT will be available I will buy this phone probably ... (this is mandatory requirement with all my smartfones , i cant imagine have smartfone without ROOT)
aaa one more question i forgot
how sim cards and exernal memory is applyiable ? SIM + SIM + MemoryCard ,
or hybrid SIM + SIM / SIM + MemoryCard
Click to expand...
Click to collapse
Charging and messages with selectable color. I agree about root however the phone was just too interesting to wait for root. I mostly need it to delete the gapps and google services as i don't use them so i can live with it for now. It has 2 sim cards and a micro SD card each in their own connector under the metal plate on the back so all 3 at once are possible.

Thx again , now all is clear for me ..
i see one minus of this phone "rubber" around a case ... i hope so its properly mounted "glued" I have NOMU S30 mini now ... and after 1 year of using starting get away from corners

Ulefone Armor 3W/3WT TWRP custom recovery + ROOT
Hello there. We did custom recovery and root for 3W/3WT but idk how to attach files here and I can't insert links because I haven't 10 posts. How can I share it?

Safg13 said:
Hello there. We did custom recovery and root for 3W/3WT but idk how to attach files here and I can't insert links because I haven't 10 posts. How can I share it?
Click to expand...
Click to collapse
try tu use spaces
w w w . g o o g l e . c o m
www.google.com

Ulefone Armor 3W/3WT TWRP custom recovery + ROOT
Instructions:
1. Flash recovery.img via spflashtool or platformtools.
2. Boot to TWRP.
Touchscreen is not working properly in TWRP on our gadgets. You need to use OTG cable and mouse. Skip enter password form. Default language is russian so you can choose your in options.
3. Install disable force encryption and magisk (if you need root) via TWRP.
4. Boot to system. Enjoy.
Download link (merge go ogle together)
drive.go ogle.com/open?id=1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC

Safg13 said:
Instructions:
1. Flash recovery.img via spflashtool or platformtools.
2. Boot to TWRP.
Touchscreen is not working properly in TWRP on our gadgets. You need to use OTG cable and mouse. Skip enter password form. Default language is russian so you can choose your in options.
3. Install disable force encryption and magisk (if you need root) via TWRP.
4. Boot to system. Enjoy.
Download link (merge go ogle together)
drive.go ogle.com/open?id=1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
Click to expand...
Click to collapse
Thank you so much! This works great!
Here is a clickable download link: https://drive.google.com/drive/folders/1J0HlsJYTyJUGAHjIXYMDUXye4DD9kEAC
For anyone following these are the steps i did (assuming you unlocked bootloader already):
1. Copy both zips to external sd as internal storage wont work at first
2. adb reboot bootloader
3. fastboot flash recovery recovery.img
4. unplug usb and hold power button until screen turns off
5. let go of power button, count to 2, press and hold power button and volume up together until screen turns back on
6. let go of power button when screen turns on but keep holding volume up until you see TWRP screen
7. as above post said, cancel password and swipe to enter main menu and then one square above the bottom right to enter the language menu
8. flash both zips from external sd card
9. format data (not wipe but format to get rid of encryption) - i rebooted after flashing the zips and had to go back to recovery again to format the data !THIS DOES A FACTORY RESET!
10. reboot to system this will cause it to be set up as new
11. reboot to recovery again, this time there should be no password and in install you should be able to see internal storage of the phone
12. flash magisk / anything else you want
Also do you mind me asking... How did you manage to make this recovery? As far as i understand the stock boot.img is needed to port twrp or have things changed now?

Thank you for your feedback and more detailed instructions. I was only a tester, the work was done by nemo-nemo from 4pda. But how i can understand you need to use your stock firmware from ulefone mega storage. I got a problem when was working with twrp stuff. Tee key and google key red text in upper right corner. I have restored the IMEI's but google key still is not ok. I checked solutions for other ulefone phones but they dont work. Maybe android 9 is a reason. If anyone know something about it pls reply. Sorry for my english

Safg13 said:
Thank you for your feedback and more detailed instructions. I was only a tester, the work was done by nemo-nemo from 4pda. But how i can understand you need to use your stock firmware from ulefone mega storage. I got a problem when was working with twrp stuff. Tee key and google key red text in upper right corner. I have restored the IMEI's but google key still is not ok. I checked solutions for other ulefone phones but they dont work. Maybe android 9 is a reason. If anyone know something about it pls reply. Sorry for my english
Click to expand...
Click to collapse
Aha. I did not know about any such ulefone mega storage existing although i have seen this kind of thing before when working with a no-name chinese tablet. I thought that the firmware simply wasn't released yet as there was no download link on ulefone page. Sadly i do not know anything about tee key or google key, it just worked for me. Hopefully someone else can help you with that.

ml11ML said:
Aha. I did not know about any such ulefone mega storage existing although i have seen this kind of thing before when working with a no-name chinese tablet. I thought that the firmware simply wasn't released yet as there was no download link on ulefone page. Sadly i do not know anything about tee key or google key, it just worked for me. Hopefully someone else can help you with that.
Click to expand...
Click to collapse
There is official ulefone storage for firmware, just merge me ga together
me ga.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!piQ1CQDB

Safg13 said:
There is official ulefone storage for firmware, just merge me ga together
me ga.nz/#F!t64QzRxA!SxZFFl3WrgujTaFshrFuKA!piQ1CQDB
Click to expand...
Click to collapse
Thank you, i'm sure this will be very useful. By the way.... I tried remounting system as rw and it doesn't allow me to do that. I read online that this might be due to a "secure kernel" but can't get much more info. Do you know how one could solve this and modify the files in system partition? Maybe there is some flashable .zip patch to enable it?
EDIT: It works in TWRP just not in android. I suspect this is due to apps trying to remount /system but the phone actually has files in /system/system/ (2 folders one in another).
EDIT2: Don't try to restore a twrp backup if you have any important data, for me it caused the phone to go black screen and reboot as soon as it goes past the first few seconds of the Orange State logo to try and load the system.

Latest Android 10 - unsupported/Unknown format from Magisk

Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!

MarSOnEarth said:
Hi,
New PH-1 owner here. Just got the phone new from Amazon. It was on 7.1.1. Immediately it upgraded to 9.0, and then to 10, build QQ1A-200105.32 with Feb. security updates. Impressive! After reading through some (a lot) of the material collected about the phone, I decided that at first I'd only root it (i.e. without installing TWRP) with Magisk. After getting familiar with the two rooting guide ("[GUIDE] Rooting your Essential PH-1" and "[Guide] How to Install TWRP & Root Essential PH-1(Method 2)") I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
So, that's the status, and I'll welcome any and all advise on the above, but in the meantime, a question:
1 - If I flash this ('4.4.166-stock-twrp-mgk181.img') image will I loose Android 10,or the ability to have later upgrades?
Thanks!
Click to expand...
Click to collapse
First, TWRP doesn't work well with latest stock ROM (QQ1A.200105.032), if you'd like to use TWRP, you should use one level down (QQ1A.200105.007)
Second, there's no more upgrade for this ROM, Essential stopped support it, and Feb update was the last one.

Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks

MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?). So, not much interest in TWRP, just root.
Regarding 4.4.166-stock-twrp-mgk181.img: what Android version does it have, and when installed, can it be upgraded?
Thanks
Click to expand...
Click to collapse
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.

chanh2018 said:
Maybe I don't quite clear about your question, but why do you use that TWRP file?
I always use the official one from TWRP
https://twrp.me/essential/essentialph1.html
And regarding to Google update, as long as you don't use custom rom + microg then I believe you always get updated from Google Play store for your apps.
Click to expand...
Click to collapse
Ah, yes! My interest in 4.4.166-stock-twrp-mgk181 image is because, a) I failed to get root with Magisk, and b) this is a `fastboot` image that's already rooted (notice the mgk181 part of the name), BUT because it was made in January of 2019, I think (if it does, and I know too little to know that) it contains older version of Android, hence the question about whether I will be able to update from it.
Thanks

MarSOnEarth said:
Thanks for your reply. For now, all I would love is to get root and not loose the ability to get future updates from Google (I do understand Essential is toast, but with Android 10 Google will provide many updates, right?).
Thanks
Click to expand...
Click to collapse
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.

MarSOnEarth said:
I actually followed this write up, and it :crying:FAILED.
I tried both ('PH1-Images-QQ1A.200105.032.zip', and 'PH1-OTA-QQ1A.200105.032.zip') Essential provided images and with both Magisk (v. 20.3 and MMgr. v. 7.5.1) failed with "Unsupported/Unknown image format"
Click to expand...
Click to collapse
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.

IronRoo said:
As I understand it Google will push some updates/security patches for Android via Play store but not everything, you still need updates from your manufacturer (which we now won't get) so you likely won't have all security patches, for this you need an up to date custom ROM like LineageOS (only at ver 9 pie currently) or maybe use the GSI (see Android 11 preview thread) but that is still in development at the moment so probably not suitable for daily use due to bugs & missing features.
Click to expand...
Click to collapse
True. Eventually, a proper custom recovery, like TWRP, might be essential (har, har) years down the road (although I only now am coming down from a Moto X (first gen, 2013) that between AFWall and XPrivacy I managed to keep on stock firmware all along), but now I need to get this phone prepped up for daily use, and that means getting root first of all (and from kt-Froggy's note I shall... I see now where I goofed).
I appreciate your input. Thanks!

kt-Froggy said:
I don't use TWRP, but I do have root, so if that's enough for you, see the steps below. Magisk version that you mentioned (v.20.3 and MMgr. v.7.5.1) works perfectly.
Since you are already on Feb update (the latest and the last one from Essential), you don't need the OTA zip. You only need the "PH1-Images-QQ1A.200105.032.zip" - the full fastboot image. Make sure you download and install the ADB/Fastboot from Essential website on your PC - it comes bundled with the Windows driver linked on their Developer page. Also make sure you have a good USB cable (do NOT use the one that comes with the phone!), and avoid using USB3 ports on your PC (use USB2 instead).
1. Extract boot.img from PH1-Images-QQ1A.200105.032.zip.
2. Install Magisk Manager, if not installed already.
3. Copy the extracted boot.img to the phone, then patch it with Magisk.
4. Copy the patched boot.img to PC.
5. Reboot the phone into bootloader.
6. Run the command "fastboot flash boot <your_patched_boot>.img" from your PC.
7. Reboot the phone.
8. Enjoy the root access.
Click to expand...
Click to collapse
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!

MarSOnEarth said:
Thanks! From the above, it looks like I messed up on the very first step; I was giving Magisk the whole PH1-Images-QQ1A.200105.032.zip file and not the boot.img extracted from it. Oops!
Click to expand...
Click to collapse
That was my suspicion from how I read your post... ? Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.

kt-Froggy said:
That was my suspicion from how I read your post... Yeah, you need just the boot image extracted from the zip. The process is really simple, and it's been working for me with no issues, apart from one specific laptop where I was consistently getting errors for no apparent reason, so I just used other PCs.
Click to expand...
Click to collapse
OK, that worked splendidly. Thanks!

Getting apps on a Xiaomi Redmi Note 9 Pro 5G

Hi ! I got a Redmi Note 9 Pro 5G from someone who couldn't use it since it's a chinese model that doesn't support Google services. I unlocked the bootloader and installed Xiaomi's EU ROM but this phone isn't Google Play Protect Certified so I can't get apps. I'm sorry guys for this newbie thread but I'm a bit confused with my next step, I could try another OS but Google might remain inaccessible, maybe someone have some experience with this model or know what else might work ?
Thanks for any insight you might have !

Use Yalp Store instead of Googe Play Store:
Yalp Store (Android)
Download any of Google Play's APKs
yalp-store.en.uptodown.com

-Wildberry- said:
Hi ! I got a Redmi Note 9 Pro 5G from someone who couldn't use it since it's a chinese model that doesn't support Google services. I unlocked the bootloader and installed Xiaomi's EU ROM but this phone isn't Google Play Protect Certified so I can't get apps. I'm sorry guys for this newbie thread but I'm a bit confused with my next step, I could try another OS but Google might remain inaccessible, maybe someone have some experience with this model or know what else might work ?
Thanks for any insight you might have !
Click to expand...
Click to collapse
U could try installing a custom rom that comes with gapps
Don't know if it's gonna work but it's worth a try

As far as I know, for the stock rom of this model, you just need to download & install the Google Play Store apk in order to run Google Play.

Curious to hear if you found a way to install gapps as I have nearly the same problem with my Chinese version. Came with gapps installed, but latest MIUI update disabled it and I don't have any exp flashing anything! Seriously need help in NYC!

Leorick1 said:
Curious to hear if you found a way to install gapps as I have nearly the same problem with my Chinese version. Came with gapps installed, but latest MIUI update disabled it and I don't have any exp flashing anything! Seriously need help in NYC!
Click to expand...
Click to collapse
I experienced the same - after update v12.0.3, Gapps stopped working. I then searched for solutions and was able to flash it back with ROM version before the update. What I did was:
1. Enable the Developer Options on your Redmi Note 9 Pro 5G.
Go to Settings>My Device>All Specs>Tap 5 or 6 times on the MIUI Version/ Build Number until you see a pop message that shows you “You are now a developer”.
2. Head to the Settings>Additional Settings>Developer Options>enable USB Debugging and OEM Unlock.
3. Go to Settings>Developer Options>Mi Unlock Status and then:
a.Agree to Permission
b.Click Add account and device
c.Turn off wi-fi and use mobile data
d.Your device will be "binded"
3. Using a computer download Mi Unlock tool. In my case I downloaded it from https://www.gizmochina.com/2020/02/11/download-xiaomi-mi-unlock-tool/:
a. The version I first downloaded is miflash_unlock-en-3.5.1128.45.
b. Install it. In my case, the USB driver for my device was also installed.
Another website to download the unlock tool is https://en.miui.com/unlock/download_en.html. This is the version miflash_unlock-en-5.5.224.24. In my case, it was the first version installation where my USB driver was installed. But the second version was the one I used to unlock.
c. Run the unlock tool.
d. Enter you Mi Account credentials. You may need to enter the code sent to the Phone number registered to your Mi Account.
4. Power off your device. Long press the volume down and power button until you see the Fastboot screen. Connect your Device to the PC and then:
a. Click Refresh. Unlock tool shall now show your device and then click unlock.
b. After a short while, you will be advised to unlock after few days, in my case it's 7 days. (It is important at this point that you already creatde a Backup and copy it to your computer. Copy separately the DCIM Folder).
5. After the waiting period:
a.Power off your device. Long press the volume down and power button until you see the Fastboot screen. Connect your Device to the PC.
b. Run the unlock tool.
d. Enter you Mi Account credentials.
e. Click Refresh. Unlock tool shall now show your device and then click unlock.
6. Download Mi Flash Tool. In my case, its MiFlash20210226. unzip and install it.(Note: download the Mi Flash Tool in advance so you have it ready. You may download it same time when you download the unlock tool).
7. Download the Rom Version before the update. I downloaded it from https://xiaomirom.com/en/rom/redmi-note-9-pro-5g-mi-10t-lite-gauguin-china-fastboot-recovery-rom/. In my case, It is a history Fastboot Rom since it is a rollback. It is gauguin_images_V12.0.11.0.QJSCNXM_20210219.0000.00_10.0_cn_01867c5953.tgz. Unzip it and place it in drive C of your computer. (Note: download the Rom Fast Boot in advance so you have it ready).
8. To prevent anti roll back error, I edited all the .bat files. I renamed them to .txt and deleted a portion that restricts roll back. In my case, I deleted the portion after the 2 lines that starts in "fastboot %* getvar..." The portion that I deleted starts with "::check anti_version" and followed by 4 lines of "if..". After delete, you will see that all the lines now start with "fastboot %* only. I then rename it back to .bat. You may want to check out this youtube video:
8. Run the Mi Flash tool and then:
a.Power off your device. Long press the volume down and power button until you see the Fastboot screen. Connect your Device to the PC.
b. Click Refresh. MiFlash tool shall now show your device.
c. Click Select button and find the folder of the ROM in your Drive C. VERY IMPORTANT: at the bottom of the flash tool window,you must select "Clean all" before you click flash button.
6. Wait patiently while flashing. After flashing (about more than 500+ seconds) your device will reboot. Note that the flash tool may say error (something about lock) but in my case, flashing was successful even if it said error. Your device will now reboot. MIUI may take a while to load. Wait patiently. You may need to register again using your MI credentials. It may be in chinese text but you will know because it is shown first after boot. After that, it will all be setting up like its a new phone (you can now choose English language).
IMPORTANT ADVISORY: It is important that you create a Backup and copy it to your computer. Unlocking already deletes the data of your phone. After flashing, you may copy it back to MIUI>Backup Folder>All Backup and use it to restore your contacts and other settings. Also always make sure your phone battery is 80% full if not 100% when unlocking or flashing. In my experience, China Rom is still best to use for Redmi Note 9 Pro 5G because it maximizes the use and features of your phone.Other ROM (India or Global may cause bugs and camera issues). Only caveat is, you can no longer update your MIUI. As the updated MIUI is the one that stops the Gapps from running in the first place. After all this, you will appreciate how unique, special and one of a kind phone is Redmi Note 9 Pro 5G.
UPDATE JUNE 1 2021:
Guys, just right now, after checking, my phone showed MIUI 12.5 as available update. Fingers crossed, I updated my Redmi Note 9 Pro 5G to MIUI 12.5 (v12.5.2.0), and like a blessing from heaven, all my doubts, fears and worries of not being able to use GMS are gone. After updating with v12.0.3 before, all my Gapps stopped working. But with this update, you just have to go to Settings, Accounts and Sync, Basic Google Services (this is new) and just enable it. And just like that, all that nightmare about Redmi Note 9 Pro 5G China rom not allowing google apps is gone. MIUI 12.5 is so smooth and awesome, so feature-rich. For me, sticking to China Rom (english language though) is still the best for China rom phones for you to be able to maximize and enjoy all its features. Flashing other roms may cause bugs and camera issues. Salvation has come! I have no idea about other models but I think K40 also has available update already.

-Wildberry- said:
Hi ! I got a Redmi Note 9 Pro 5G from someone who couldn't use it since it's a chinese model that doesn't support Google services. I unlocked the bootloader and installed Xiaomi's EU ROM but this phone isn't Google Play Protect Certified so I can't get apps. I'm sorry guys for this newbie thread but I'm a bit confused with my next step, I could try another OS but Google might remain inaccessible, maybe someone have some experience with this model or know what else might work ?
Thanks for any insight you might have !
Click to expand...
Click to collapse
I experienced the same - after update v12.0.3, Gapps stopped working. I then searched for solutions and was able to flash it back with ROM version before the update. What I did was:
1. Enable the Developer Options on your Redmi Note 9 Pro 5G.
Go to Settings>My Device>All Specs>Tap 5 or 6 times on the MIUI Version/ Build Number until you see a pop message that shows you “You are now a developer”.
2. Head to the Settings>Additional Settings>Developer Options>enable USB Debugging and OEM Unlock.
3. Go to Settings>Developer Options>Mi Unlock Status and then:
a.Agree to Permission
b.Click Add account and device
c.Turn off wi-fi and use mobile data
d.Your device will be "binded"
3. Using a computer download Mi Unlock tool. In my case I downloaded it from https://www.gizmochina.com/2020/02/11/download-xiaomi-mi-unlock-tool/:
a. The version I first downloaded is miflash_unlock-en-3.5.1128.45.
b. Install it. In my case, the USB driver for my device was also installed.
Another website to download the unlock tool is https://en.miui.com/unlock/download_en.html. This is the version miflash_unlock-en-5.5.224.24. In my case, it was the first version installation where my USB driver was installed. But the second version was the one I used to unlock.
c. Run the unlock tool.
d. Enter you Mi Account credentials. You may need to enter the code sent to the Phone number registered to your Mi Account.
4. Power off your device. Long press the volume down and power button until you see the Fastboot screen. Connect your Device to the PC and then:
a. Click Refresh. Unlock tool shall now show your device and then click unlock.
b. After a short while, you will be advised to unlock after few days, in my case it's 7 days. (It is important at this point that you already creatde a Backup and copy it to your computer. Copy separately the DCIM Folder).
5. After the waiting period:
a.Power off your device. Long press the volume down and power button until you see the Fastboot screen. Connect your Device to the PC.
b. Run the unlock tool.
d. Enter you Mi Account credentials.
e. Click Refresh. Unlock tool shall now show your device and then click unlock.
6. Download Mi Flash Tool. In my case, its MiFlash20210226. unzip and install it.(Note: download the Mi Flash Tool in advance so you have it ready. You may download it same time when you download the unlock tool).
7. Download the Rom Version before the update. I downloaded it from https://xiaomirom.com/en/rom/redmi-note-9-pro-5g-mi-10t-lite-gauguin-china-fastboot-recovery-rom/. In my case, It is a history Fastboot Rom since it is a rollback. It is gauguin_images_V12.0.11.0.QJSCNXM_20210219.0000.00_10.0_cn_01867c5953.tgz. Unzip it and place it in drive C of your computer. (Note: download the Rom Fast Boot in advance so you have it ready).
8. To prevent anti roll back error, I edited all the .bat files. I renamed them to .txt and deleted a portion that restricts roll back. In my case, I deleted the portion after the 2 lines that starts in "fastboot %* getvar..." The portion that I deleted starts with "::check anti_version" and followed by 4 lines of "if..". After delete, you will see that all the lines now start with "fastboot %* only. I then rename it back to .bat. You may want to check out this youtube video:
8. Run the Mi Flash tool and then:
a.Power off your device. Long press the volume down and power button until you see the Fastboot screen. Connect your Device to the PC.
b. Click Refresh. MiFlash tool shall now show your device.
c. Click Select button and find the folder of the ROM in your Drive C. VERY IMPORTANT: at the bottom of the flash tool window,you must select "Clean all" before you click flash button.
6. Wait patiently while flashing. After flashing (about more than 500+ seconds) your device will reboot. Note that the flash tool may say error (something about lock) but in my case, flashing was successful even if it said error. Your device will now reboot. MIUI may take a while to load. Wait patiently. You may need to register again using your MI credentials. It may be in chinese text but you will know because it is shown first after boot. After that, it will all be setting up like its a new phone (you can now choose English language).
IMPORTANT ADVISORY: It is important that you create a Backup and copy it to your computer. Unlocking already deletes the data of your phone. After flashing, you may copy it back to MIUI>Backup Folder>All Backup and use it to restore your contacts and other settings. Also always make sure your phone battery is 80% full if not 100% when unlocking or flashing. In my experience, China Rom is still best to use for Redmi Note 9 Pro 5G because it maximizes the use and features of your phone.Other ROM (India or Global may cause bugs and camera issues). Only caveat is, you can no longer update your MIUI. As the updated MIUI is the one that stops the Gapps from running in the first place. After all this, you will appreciate how unique, special and one of a kind phone is Redmi Note 9 Pro 5G.
UPDATE: JUNE 1 2021
Guys, just right now, after checking, my phone showed MIUI 12.5 as available update. Fingers crossed, I updated my Redmi Note 9 Pro 5G to MIUI 12.5 (v12.5.2.0), and like a blessing from heaven, all my doubts, fears and worries of not being able to use GMS are gone. After updating with v12.0.3 before, all my Gapps stopped working. But with this update, you just have to go to Settings, Accounts and Sync, Basic Google Services (this is new) and just enable it. And just like that, all that nightmare about Redmi Note 9 Pro 5G China rom not allowing google apps is gone. MIUI 12.5 is so smooth and awesome, so feature-rich. For me, sticking to China Rom (english language though) is still the best for China rom phones for you to be able to maximize and enjoy all its features. Flashing other roms may cause bugs and camera issues. Salvation has come! I have no idea about other models but I think K40 also has available update already.

Database Info

welcome