Device ：Redmi K20 Pro Premier Edition 12+512
Recovery : TWRP 3.3.1-25 Unofficial by mauronofrio、2019.11.28. 11:21:04 Recovery switches to OrangeFox-R10.0_8-Stable-raphael.zip
ROOT : Magisk 20.1
Data partition file system: F2FS
Other tools : Riru 19.5 (Modules needed by EdXposed)
Xposed : EdXposed v0.4.6.0_beta
Gapps : open_gapps-arm64-10.0-pico-20191114-BETA.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"
}
The official flash pack for K20pro and K20 Premier Edition in MIUI 11 is the same.
——————————————The ROM below can enter the desktop normally——————————————
The bottom layer of the phone is not unlocked is miui_RAPHAEL_9.11.22_a4275df480_10.0.zip
After cleaning up the Data, System, and Cache in the recovery mode.
After downgrading Android 9 with fw-vendor_raphael_miui_RAPHAELS_V10.4.1.0.PFKCNXM_ff9fc7e2a8_9.0.zip, then flash into Havoc-OS-v2.9-20191008-raphael-Unofficial.zip and successfully enter the desktop
1126-113050 Havoc-OS-v2.9-20191008-raphael-Unofficial.zip
After cleaning up the Data, System, and Cache in the recovery mode.
After upgrading Android 10 with fw-vendor_raphael_miui_RAPHAEL_V11.0.2.0.QFKCNXM_e5247b38b7_10.0.zip , then flash in * .zip to successfully enter the desktop
1125-220509 ion-2.1.c-raphael-20191124-1233-UNOFFICIAL-Preview.zip
1126-115802 Havoc-OS-v3.0-20191113-raphael-Official.zip
1126-123645 Xtended-raphael-20191120-XQ-OFFICIAL-Release-v3.0.zip
1126-131835 EvolutionX_3.3_raphael-10.0-20191124-1904-OFFICIAL.zip
ColtOS-Beta-v5.3-Unofficial-20191123.zip
RevengeOS-3.0-Q-OFFICIAL-Stable-raphael-20191120.zip
syberia_raphael-v3.1-20191124-1743-OFFICIAL.zip
You can enter the desktop normally and use it, forget the screenshot.
——————————————The ROM below cannot enter the desktop normally——————————————
CARBON-CR-8.0-PAX-UNOFFICIAL-raphael-20191125-0436.zip An error 7 will appear indicating that it cannot be flashed.
BootleggersROM-Queue4raphael.4.7-MadStinky-Unshishufied-20191124-102820.zip
BootleggersROM-Queue4raphael.4.7-MadStinky-Unshishufied-20191124-161002.zip
BootleggersROM can be flashed normally but will stay in the boot animation, if there is time, I will try the new version 1126
[If other ROMs have been stuck on the boot animation interface, you can try to format the storage in recovery mode (this means that the data in the phone will be emptied).
But this method does not work for BootleggersROM]
2019.11.28. 11:21:04 Recovery switches to OrangeFox-R10.0_8-Stable-raphael.zip
BootleggersROM-Queue4raphael.4.7-MadStinky-Unshishufied-20191128-014826.zip Can enter the desktop and use normally
——————————————————————————End——————————————————————————
Now I have used Havoc 3.0 for more than a day. The Havoc beta version currently cannot use fast charging. It takes more than three hours to fully charge. MIUI can be fully charged using fast charging in about 45 minutes. In addition, it has been restarted a few times from time to time, and may be with EdXpoesd Or other Magisk modules are related.
Fingerprint of MIUI
MIUI 10.4.1.0 From factory
HTML:
Xiaomi/raphael/raphael:9/PKQ1.190616.001/V10.4.1.0.PFKCNXM:user/release-keys
Available through Google's SafetyNet .
MIUI 11 9.11.22 From the MIUI Forum Beta
HTML:
Xiaomi/raphael/raphael:10/QKQ1.190825.002/9.11.22:user/release-keys
Not available through Google's SafetyNet .
View attachment 4888153 View attachment 4888155 View attachment 4888157 View attachment 4888159 View attachment 4888161
reserved 1
reserved 2
Nice info bro. Appreciate it. From your opinion what is the best global rom for k20 pro premium?
You can add LOS17 to the list too.
2220209876 said:
Device ：Redmi K20 Pro Premier Edition 12+512
Recovery : TWRP 3.3.1-25 Unofficial by mauronofrio、2019.11.28. 11:21:04 Recovery switches to OrangeFox-R10.0_8-Stable-raphael.zip
ROOT : Magisk 20.1
Data partition file system: F2FS
Other tools : Riru 19.5 (Modules needed by EdXposed)
Xposed : EdXposed v0.4.6.0_beta
Gapps : open_gapps-arm64-10.0-pico-20191114-BETA.zip
The official flash pack for K20pro and K20 Premier Edition in MIUI 11 is the same.
——————————————The ROM below can enter the desktop normally——————————————
The bottom layer of the phone is not unlocked is miui_RAPHAEL_9.11.22_a4275df480_10.0.zip
After cleaning up the Data, System, and Cache in the recovery mode.
After downgrading Android 9 with fw-vendor_raphael_miui_RAPHAELS_V10.4.1.0.PFKCNXM_ff9fc7e2a8_9.0.zip, then flash into Havoc-OS-v2.9-20191008-raphael-Unofficial.zip and successfully enter the desktop
1126-113050 Havoc-OS-v2.9-20191008-raphael-Unofficial.zip
After cleaning up the Data, System, and Cache in the recovery mode.
After upgrading Android 10 with fw-vendor_raphael_miui_RAPHAEL_V11.0.2.0.QFKCNXM_e5247b38b7_10.0.zip , then flash in * .zip to successfully enter the desktop
1125-220509 ion-2.1.c-raphael-20191124-1233-UNOFFICIAL-Preview.zip
1126-115802 Havoc-OS-v3.0-20191113-raphael-Official.zip
1126-123645 Xtended-raphael-20191120-XQ-OFFICIAL-Release-v3.0.zip
1126-131835 EvolutionX_3.3_raphael-10.0-20191124-1904-OFFICIAL.zip
ColtOS-Beta-v5.3-Unofficial-20191123.zip
RevengeOS-3.0-Q-OFFICIAL-Stable-raphael-20191120.zip
syberia_raphael-v3.1-20191124-1743-OFFICIAL.zip
You can enter the desktop normally and use it, forget the screenshot.
——————————————The ROM below cannot enter the desktop normally——————————————
CARBON-CR-8.0-PAX-UNOFFICIAL-raphael-20191125-0436.zip An error 7 will appear indicating that it cannot be flashed.
BootleggersROM-Queue4raphael.4.7-MadStinky-Unshishufied-20191124-102820.zip
BootleggersROM-Queue4raphael.4.7-MadStinky-Unshishufied-20191124-161002.zip
BootleggersROM can be flashed normally but will stay in the boot animation, if there is time, I will try the new version 1126
[If other ROMs have been stuck on the boot animation interface, you can try to format the storage in recovery mode (this means that the data in the phone will be emptied).
But this method does not work for BootleggersROM]
2019.11.28. 11:21:04 Recovery switches to OrangeFox-R10.0_8-Stable-raphael.zip
BootleggersROM-Queue4raphael.4.7-MadStinky-Unshishufied-20191128-014826.zip Can enter the desktop and use normally
——————————————————————————End——————————————————————————
Now I have used Havoc 3.0 for more than a day. The Havoc beta version currently cannot use fast charging. It takes more than three hours to fully charge. MIUI can be fully charged using fast charging in about 45 minutes. In addition, it has been restarted a few times from time to time, and may be with EdXpoesd Or other Magisk modules are related.
Fingerprint of MIUI
MIUI 10.4.1.0 From factory
HTML:
Xiaomi/raphael/raphael:9/PKQ1.190616.001/V10.4.1.0.PFKCNXM:user/release-keys
Available through Google's SafetyNet .
MIUI 11 9.11.22 From the MIUI Forum Beta
HTML:
Xiaomi/raphael/raphael:10/QKQ1.190825.002/9.11.22:user/release-keys
Not available through Google's SafetyNet .
View attachment 4888153 View attachment 4888155 View attachment 4888157 View attachment 4888159 View attachment 4888161
Click to expand...
Click to collapse
Hello there Honestly Very nice work what u have done
i am not very expert in flashing roms and custom roms but apparently you are expert.
i have some questions for you i have bought K20 pro premium from china and now i am stack with locked phone using chinese rom
i have installed google play services and added my account and transferred my data but still have some Chinese stuff and get rid of and been searching if i can flash global rom and i would prefer official rom but i found out i had to unlock my phone and that will cause me not being able to use some high security apps like banking and google pay so now i am seeking an expert answer for these questions
1- what the real bad thing in using Chinese rom out of china (disadvantages from global rom i mean).
2- if i am willing to unlock my phone and flash official global rom what i will lose later as a result for unlocking my phone.
3- is there are a way to go around unlocking my phone so i can use every thing normally as my previous locked phone with global rom including using all kind of apps (pay and banking apps) and getting OTA updated for my phone.
finally thanks a lot i appreciate your help.
drphysics said:
Hello there Honestly Very nice work what u have done
i am not very expert in flashing roms and custom roms but apparently you are expert.
i have some questions for you i have bought K20 pro premium from china and now i am stack with locked phone using chinese rom
i have installed google play services and added my account and transferred my data but still have some Chinese stuff and get rid of and been searching if i can flash global rom and i would prefer official rom but i found out i had to unlock my phone and that will cause me not being able to use some high security apps like banking and google pay so now i am seeking an expert answer for these questions
1- what the real bad thing in using Chinese rom out of china (disadvantages from global rom i mean).
2- if i am willing to unlock my phone and flash official global rom what i will lose later as a result for unlocking my phone.
3- is there are a way to go around unlocking my phone so i can use every thing normally as my previous locked phone with global rom including using all kind of apps (pay and banking apps) and getting OTA updated for my phone.
finally thanks a lot i appreciate your help.
Click to expand...
Click to collapse
1. The international version has full Google services, and the Chinese version can use localized features such as nfc payment in China.
2. Switching the version will cause the internal data of the phone to be lost (restore factory settings), remember to back up the data. It may not be possible to update OTA in the third-party REC, and it can be completely updated.
3. You can apply for unlocking at http://unlock.update.miui.com, usually you need to bind your mobile phone to Xiaomi account for 168 hours to unlock. Some third-party ROMs can be installed via Magisk through safetynet or may require the magisk module to pass. Authentication, you can go to magisk topic posts to take a look.
Does anyone has worked camera?
I have installed EvolutionX_3.3_raphael-10.0-20191124-1904-OFFICIAL with MIUI 11 's vendor.
Everything looks great, but camera can't work.
Both stock and gcam(Urnux05) force close after start app & freeze seconds.
Also tried EvolutionX_3.5, stock camera switch to MI camera and shows "can't not connect to camera".
I have K20 Pro Premium Edition 12/512gb and using Havoc custom ROM (China firmware 11.0.5 as a base) and both ANX Camera and GCam port by Urnyx05 are working fine on my phone
So how to we go about flashing such roms on the Premier Edition? Flash as per normal?
lambstone said:
So how to we go about flashing such roms on the Premier Edition? Flash as per normal?
Click to expand...
Click to collapse
Same as the normal K20 Pro, you can use the same recovery and ROMs
salahmed said:
Same as the normal K20 Pro, you can use the same recovery and ROMs
Click to expand...
Click to collapse
The list on OP means full compatibility?
lambstone said:
The list on OP means full compatibility?
Click to expand...
Click to collapse
I don't know about the OP and it didn't contains a clear guide for everything, but as far as I tried on my phone, I know that evolution x, pixel experience, and Havoc custom ROMs works fine, also the official TWRP recovery works fine.
Did anyone try to overclock their display with the premium version?
salahmed said:
I don't know about the OP and it didn't contains a clear guide for everything, but as far as I tried on my phone, I know that evolution x, pixel experience, and Havoc custom ROMs works fine, also the official TWRP recovery works fine.
Click to expand...
Click to collapse
Can you provide the TWRP link to me ? I afraid wrong downlaod.
Thanks
salahmed said:
Same as the normal K20 Pro, you can use the same recovery and ROMs
Click to expand...
Click to collapse
So all K20 Pro custom roms and mods works in K20 Pro special edition?
I was going to buy one but had this question whether there will be a lack of custom rom options. Thanks for the calcification.
Guys i bought a premium edition, tested some of them roms, but didn't success to run the camera on android 10 roms.
On Crdroid pie version stock cam worked, now im on miui eu 11 stable everything working flawless. Dualspeaker mod from acervenky working, and 320kbs audio bitrate increase mod also working running both with miui now.
z1022 said:
Can you provide the TWRP link to me ? I afraid wrong downlaod.
Thanks
Click to expand...
Click to collapse
I use the official TWRP
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
salahmed said:
I use the official TWRP
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
Click to expand...
Click to collapse
Thank you
I want to share with you guys.
I finally success to run Evolution X 3.5-20191225 Android 10 rom. I used the twrp from op.
I was on miui V10.4.1.0.PFKCNXM before.
My procedure:
1-Twrp wipe data yes reboot to twrp again
2-wipe data/cache/dalvik+cache/system/storage/vendor don't reboot
3- flashed vendor from (raphael) V11.0.5.0.QFKCNXM
https://xiaomifirmwareupdater.com/vendor/raphael/
4-flashed Evolution X 3.5
5-wipe data yes
6-reboot (done)
7-setup than rebooted to recovery flashed magisk 20.1 (optional)
8-magisk installed dual speaker mod v4 from acervenky
Everything working flawless, anxcam is preinstalled and fully working. Dual speaker mod also working flawless.
A telegram group (only) with our device would be awsome if someone could create or invite if exists, we could share tutorials how we succeed to run something.
Related
Hi,
I can't get out of the bootloop of my Honor 7. Here below the history:
1) Unlock bootloader: Success
2) Install TWRP: Success
3) Install SuperSU 2.65: Fail
From this point i tried to recover from a new original rom with Multi-tool, but still bootloop. I also wipe all caches but still same issues. I don't know what to do as i have the feeling i tried everything already.
If someones could help me it would be nice. I still have access to bootloader (volume - & power) and I sometimes get access to TWRP but screen freezes, i can't go into any of the settings.
Thanks for your support!
Download full rom 121 if you are in LP or 320/330 if you are in MM.
Put the rom .app file into dload folder in the SDcard
Flash stock recovery,flash the rigth rom with vol+,+,vol-,+,pwr, the flashing will start automatly.
Upgrade to 180 or 330.
The files:
http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
Flamenawer said:
Download full rom 121 if you are in LP or 320/330 if you are in MM.
Put the rom .app file into dload folder in the SDcard
Flash stock recovery,flash the rigth rom with vol+,+,vol-,+,pwr, the flashing will start automatly.
Upgrade to 180 or 330.
The files:
http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
Click to expand...
Click to collapse
That won't work sadly, PLK-L01 is totally different than PLK-TL01H in terms of software.
The updates is also named differently compared to the European version, in the EU (and elsewere?) it's 180, 320, 330 etc. but on the PLK-TL01H it's 6.3.16, 6.4.1 etc.
Hi,
indeed Flamenaver the link you post is for PLK-L01 only.
Can i use one of these firmware instead which are original ones for PLK-TL01H?
http://emui.huawei.com/cn/plugin.php?id=hwdownload&mod=detail&mid=170
How does this VOL UP + VOL DOWN + Power works exactly? Do I need the press the 3 together until i see the upgrade starting or do I relesea as soon as I see HONOR Welcome Screen ?
Because it is not working if i keep the 3 pressed until something happens, because then it is restarting and restarting for ever.
On the other side, just pressing 3 for 10 seconds and couple of seconds after it powers on doesn't work neither.
Thanks for the support.
Tabithalos said:
That won't work sadly, PLK-L01 is totally different than PLK-TL01H in terms of software.
The updates is also named differently compared to the European version, in the EU (and elsewere?) it's 180, 320, 330 etc. but on the PLK-TL01H it's 6.3.16, 6.4.1 etc.
Click to expand...
Click to collapse
Try to install LP or MM full rom (no ota o zip roms),from stock recovery, with the standard process for your phone, is a universal unbrick procedure for soft_bricked phones.
I can't get access to stock recovery. I can reinstall Stock recovery from Honor Multi Tools but i can't get in it.
If i keep vol+ & Power or Vol+, Vol- & Power pressed i get onl the honor welcome screen bootloop, nothing else
Hi, I got into this mode in the end. Is this the Force update mode?
{
"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"
}
It was not easy to get in. Keep you informed in a couple of seconds what the results are.
Thanks
Tried twice already and always stuck at 90%...
sebastien_be said:
Tried twice already and always stuck at 90%...
Click to expand...
Click to collapse
If it's stuck at 90% it's not working, believe me, I've had the same problem, I tried to update SuperSU and it bricked. Had to factory reset it and update the phone to the newest version which currently is 6.4.1, THEN go through the process of installing TWRP, SuperSU etc.
If you can't get the updates via the "Updater" option in the options, try to manually downgrade/upgrade it and see if it appears. You have to do some fancy google-translate to chinese to find the update packages on chinese forums.
Why U don't try the Honor 7 Multitool and the huawei update extractor combo???
That must be work!
Hi,
this is the latest status: https://youtu.be/QsPOg4lKkSc
I'm already using Multi-Tools and extracted a PLK-TL01H stock rom. I then used the unbrick option in multi-tools and restores this stock rom. But even though it starts fine, i can enter my pin code but when the language screens comes in, it makes a weird noise and reboots.
I then went into TWRP which works fine and could wipe cache and wipe dalvik cache. But I'm still stuck with welcome crash.
Any idea what to do? As reminder:
1) Bootloader is unlocked
2) Bootloader screen works fine (fastboot works but adb doesn't)
3) TWRP screen also works fine.
Thank you!
Did you try with an older or an other stock rom?
Yes I tried these two versions;
PLK-TL01H-C01B201
PLK-UL-TL-CL_EMUI3.1_Android5.1_5.12.1
Actually this version: PLK-TL01H-C01B201 works fine but only without sim card and SD card. If one of these is inside then i get automated reboot after entering pin code. But if i reboot without these two, then the phone works fine (i can get access to wifi, menu, and so on...).
WEIRD!
Hi,
My Honor 7 is still bricked and i can't get out of it. I tried to unbrick by flashing the following files from a stock rom:
fastboot flash boot .\Unbrick\BOOT.img
fastboot flash cust .\Unbrick\CUST.img
fastboot flash recovery .\Unbrick\RECOVERY.img
fastboot flash system .\Unbrick\SYSTEM.img
The flash of these 4 files works fine. I then get the welcome screen where i can choose the language, HiCloud settings and so on. As long as i do not get out of the flight mode it seems to be stable. But when i enter the pin code of my simcard (amongst others), then i get a crash and reboot.
So i have the feeling that there are still some conflicts. In the stock rom there are many other IMG files. Shouldn't I also flash them? I have the following IMG files: 3RDMODEM, CACHE, CRC, CURVER, DTIMAGE, EFI, FASTBOOT, MODEM, etc etc.
I have the feeling that if i flash them all, then it might work fine. But all files do not have a specific partition, so i don't know how to flash them.
Thanks for the support!
sebastien_be said:
Hi,
My Honor 7 is still bricked and i can't get out of it. I tried to unbrick by flashing the following files from a stock rom:
fastboot flash boot .\Unbrick\BOOT.img
fastboot flash cust .\Unbrick\CUST.img
fastboot flash recovery .\Unbrick\RECOVERY.img
fastboot flash system .\Unbrick\SYSTEM.img
The flash of these 4 files works fine. I then get the welcome screen where i can choose the language, HiCloud settings and so on. As long as i do not get out of the flight mode it seems to be stable. But when i enter the pin code of my simcard (amongst others), then i get a crash and reboot.
So i have the feeling that there are still some conflicts. In the stock rom there are many other IMG files. Shouldn't I also flash them? I have the following IMG files: 3RDMODEM, CACHE, CRC, CURVER, DTIMAGE, EFI, FASTBOOT, MODEM, etc etc.
I have the feeling that if i flash them all, then it might work fine. But all files do not have a specific partition, so i don't know how to flash them.
Thanks for the support!
Click to expand...
Click to collapse
The main problem that you were on MM version (6.3.16-DEV edition of ROM, no official update) of ROM and you're trying to flash Lollipop (B201, 5.12.1). It means that your problems are probably caused by this. Try to flash 5.12.16 then OTA update to 6.1.1 (using WiFi if possible) and then rollback from Emui 4 to Emui 3.1 if you want use Emui 3.1 and Lollipop. it's up to you. It's possible that your will be able to use SIM card when you would update to 6.1.1 (MM)
Sent from PLK-TL01H
SOLVED!
Thank you Lucki_X and Inside!Out ! Indeed i was trying to flash with Android 5.0 while i was already on Android 6.
Consequently I used the unbrick option from Multi-tools by using this version PLK-TL01H_EMUI4.0_Android6.0_6.2.1(B634).zip
Now everything works fine. Can anyone tell me how to install SuperSU? Because it is due to installation of SuperSU through TWRP that it caused the crash. I installed SuperSU 2.65 BETA.
How to do and which version to install to avoid bootloop?
Thanks very much,
Sebastien.
Hi All,
any idea why i now only have 3,87GB available as internal storage?
sebastien_be said:
Hi All,
any idea why i now only have 3,87GB available as internal storage?
Click to expand...
Click to collapse
Probably because you have multiple ghost systems as a result of previous still in memory. Factory reset will help.
Thank you! This is also solved now (Factory reset in TWRP + Calvik & Cache Wipes)!
Last question: Any advice on how to install SuperSU? Because by trying to install 2.65 BETA it caused the bootloop earlier.
Is there any version to propose instead of another one?
Thanks,
To answer my question: There is only the v2.62 that is working with Honor7 ! I Tried 2.49 and 2.65 both creates startup bootloop. Hopefully this time i got a full backup made in TWRP, was pretty easy to comeback to a working version.
i have a similiar brick as you. Flashed from B201 to B352 via the OTA. Had a boodloop, tried to erase cache and factory reset.
Tried to unbrick my phone with multi tool (first with the B201 udpate.app - now with B634 update.app). Now i'm in a bootloop again. What can I do?
EDIT: I'm in the ROM now, but can't enable my SIM card and WIFI is also not working
What can i do?
Keeping it short:
This is the official STABLE global MIUI 11 Rom for Mi 9T
Official download links:
For rooted devices - Recovery full zip (2.3GB)
For stock unrooted devices - OTA upgrade zip (779MB)
Magisk Root without TWRP:
Objectives :
Have root using Magisk
Be able to install OTA from the settings without bootloops
Avoid boot loop
Very important :
Your phone has to have an unlocked bootloader
Your phone has to have stock recovery. TWRP WILL cause bootloop for root and/or OTA updates from system.
I like to have root with magisk and don't want to install TWRP because I want to be able to install OTA from system without boot loops. This guide will help you achieve this with ease.
Download the rooted boot image for your correct ROM version from here: https://mega.nz/#F!1kwETAwD!O5iPgAaocQ8WxfUK2V7RVA
Restart your phone in fastboot mode (hold vol-down and power buttons for a few seconds)
Flash the rooted boot image using fastboot. (fastboot flash boot Magisk_9T_Global_V11.0.1.0.PFJMIXM.img)* **
Reboot device (fastboot.exe reboot)
(install then) Open Magisk manager
Follow instruction shown in the magisk manager for adding necessary files (you might not need this)
*Download the latest Minimal ADB /fastboot and USB drivers for your device if you are having a problem with this.
** Using some data cables will result in your fastboot not seeing your device (showing < waiting for any device >). If you have this problem change your USB cable with another or use the one that comes with the device
I have attached the following root files:
V10.3.11.0.PFJMIXM (MIUI10) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T Magisk rooted boot image
Things to consider doing after the update:
Remove ads using this guide: https://miblog.co/miui-remove-system-ads/
Enable Android style notification (instead of the default MiUI one) from the notification settings
Disable option: “Settings / Additional settings / Privacy / Location / Scanning / WLAN scanning” to improve battery life
Use this guide to install Xiaomi Mi 9 Google Camera (GCam) (no root needed): https://miblog.co/xiaomi-mi9-google-camera/
Disable autostart for all apps excluding the ones you want to autostart to fix the battery drainage issue
{
"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"
}
Hey, quick question. I'm trying to install the new MIUI11 stock global ROM for my Mi 9T. The thing is, the phone's updater takes forever to download and the download itself even gets cancelled out of nowhere (my internet is pretty slow) Can I just download the 779MB OTA Upgrade zip you provided and move it to my phone and proceed selecting it from the updater app? Is it the same file you get as downloading it from the app? I'm on global, PFJMIXM version 10.3.11.0
Thanks!
Danielxgl said:
Hey, quick question. I'm trying to install the new MIUI11 stock global ROM for my Mi 9T. The thing is, the phone's updater takes forever to download and the download itself even gets cancelled out of nowhere (my internet is pretty slow) Can I just download the 779MB OTA Upgrade zip you provided and move it to my phone and proceed selecting it from the updater app? Is it the same file you get as downloading it from the app? I'm on global, PFJMIXM version 10.3.11.0
Thanks!
Click to expand...
Click to collapse
I'm not sure how the update app does the file check. Can you try it and report?
I know that if you're rooted, the OTA will fail to install and the update app automatically starts downloading the full ROM, which is pretty cool.
Kiwironic said:
I'm not sure how the update app does the file check. Can you try it and report?
I know that if you're rooted, the OTA will fail to install and the update app automatically starts downloading the full ROM, which is pretty cool.
Click to expand...
Click to collapse
Wish I could try it, but my update app miraculously decided not to fail this time, and I was able to update the phone normally. Maybe someone else could try it?
What im i do wrong if i get twrp while trying to boot miui? Installed Patched boot installed firmware cannot boot
Still Android 9, no?
SeriousX said:
What im i do wrong if i get twrp while trying to boot miui? Installed Patched boot installed firmware cannot boot
Click to expand...
Click to collapse
Flash the stock or rooted boot image and recovery for your device. It should work normally. That's my main reason to root without TWRP
robi10101298 said:
Still Android 9, no?
Click to expand...
Click to collapse
Yes
Kiwironic said:
Keeping it short:
This is the official STABLE global MIUI 11 Rom for Mi 9T
Official download links:
For rooted devices - Recovery full zip (2.3GB)
For stock unrooted devices - OTA upgrade zip (779MB)
Magisk Root without TWRP:
Download the rooted boot image for your correct ROM version from here: https://mega.nz/#F!1kwETAwD!O5iPgAaocQ8WxfUK2V7RVA
Restart your phone in fastboot mode (hold vol-down and power buttons for a few seconds)
Flash the rooted boot image using fastboot. (fastboot flash boot Magisk_9T_Global_V11.0.1.0.PFJMIXM.img)* **
Reboot device (fastboot.exe reboot)
(install then) Open Magisk manager
Follow instruction shown in the magisk manager for adding necessary files (you might not need this)
*Download the latest Minimal ADB /fastboot and USB drivers for your device if you are having a problem with this.
** Using some data cables will result in your fastboot not seeing your device (showing < waiting for any device >). If you have this problem change your USB cable with another or use the one that comes with the device
I have attached the following root files:
V10.3.11.0.PFJMIXM (MIUI10) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T Magisk rooted boot image
Things to consider doing after the update:
Remove ads using this guide: https://miblog.co/miui-remove-system-ads/
Enable Android style notification (instead of the default MiUI one) from the notification settings
Disable option: “Settings / Additional settings / Privacy / Location / Scanning / WLAN scanning” to improve battery life
Use this guide to install Xiaomi Mi 9 Google Camera (GCam) (no root needed): https://miblog.co/xiaomi-mi9-google-camera/
Disable autostart for all apps excluding the ones you want to autostart to fix the battery drainage issue
Click to expand...
Click to collapse
If I don't want root anymore I can install this via Twrp: Recovery full zip (2.3GB)rooted devices + V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
Is this right?
Drakar88 said:
If I don't want root anymore I can install this via Twrp: Recovery full zip (2.3GB)rooted devices + V11.0.1.0.PFJMIXM (MIUI11) global stable room - Global 9T stock boot image
Is this right?
Click to expand...
Click to collapse
Yes the full rom. But no need to flash boot, flashing the full image will automatically rewrite the boot image to a stock unrooted one.
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Kiwironic said:
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Click to expand...
Click to collapse
Do provide more details. I'm on stock miui (davinciin), with unlocked bl and would like to root tf outta this
geeknoob said:
Do provide more details. I'm on stock miui (davinciin), with unlocked bl and would like to root tf outta this
Click to expand...
Click to collapse
I wrote a guide and made some videos here :
https://forum.xda-developers.com/showpost.php?p=80835573&postcount=1
Updated the post because people using the guide while having TWRP will have bootloop . Please read the instructing carefully. You need a stock recovery for this root to work and for OTA to install from settings
Thanks for this guide, I couldn't get official TWRP to stick so that I could flash Magisk. I used your guide and now I have root. Many thanks
i need to ask.
when miui release a new update i usually update and after that i had to re flash the "recovery-TWRP-3.3.1-0916-REDMI_K20-CN-wzsx150" then again flash the magisk.
but this time i try to install it boot the recovery but when i go to the internal memory it appear a lot of weird folders and it won't allow me to paste the magisk to install it.
"+KPcZ3jsjybn9M850BgrhB"
3zitjokdIMQE++oQFL8PxA
9AmJcdRgO71ehKtIhWg3oB
9Y0e9H1NkAr4FMzOz9X,UD
882G73cfQNPbaXm2zAzXiD
---------- Post added at 11:34 AM ---------- Previous post was at 11:24 AM ----------
Jctatis said:
i need to ask.
when miui release a new update i usually update and after that i had to re flash the "recovery-TWRP-3.3.1-0916-REDMI_K20-CN-wzsx150" then again flash the magisk.
but this time i try to install it boot the recovery but when i go to the internal memory it appear a lot of weird folders and it won't allow me to paste the magisk to install it.
"+KPcZ3jsjybn9M850BgrhB"
3zitjokdIMQE++oQFL8PxA
9AmJcdRgO71ehKtIhWg3oB
9Y0e9H1NkAr4FMzOz9X,UD
882G73cfQNPbaXm2zAzXiD
Click to expand...
Click to collapse
NVM already fixed installed the twrp-3.3.1-0-davinci.img and flashed the magisk v.20
Kiwironic said:
Anybody who needed a root boot image, can send me the version of their ROM or send me the boot image from their phone and I'll root it for you using magisk. You can do that yourself as well by downloading the full ROM zip file, take the boot file and use magisk to create a root boot image. Can provide more details if you don't know how to do it.
Click to expand...
Click to collapse
Thanks for this! Would you be able to make a patched boot.img for V11.0.5.0.QFJMIXM? Please? Mi net is too bad to download the whole rom
galelouch993 said:
Thanks for this! Would you be able to make a patched boot.img for V11.0.5.0.QFJMIXM? Please? Mi net is too bad to download the whole rom
Click to expand...
Click to collapse
Just downloaded the whole ROM with no problem from:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Anyway, try with the following - patched from my Magisk Canary:
https://mega.nz/file/09M13QhI#4AXcEYviHw_1xyhCoDYZh_J41Iu58ulozuRJbhQZP6w
You can test just by temporarily booting to the patched image (if it boots ok, then you would really flash it):
fastboot boot boot-Magisk_Canary_20405-davinci_v11.0.5.0_QFJIMXM_aaab5b40c7_10.0.img
Download and install the corresponding Canary Magisk Manager e.g. app-release.apk, from:
https://github.com/topjohnwu/magisk_files/find/canary?q=
If you have a bootloop it could be due to the previously installed Magisk modules - you would need to disable them in TWRP:
/data/adb/modules
and to every subfolder add an empty file named "disable" (or delete the whole modules folder)
zgfg said:
Just downloaded the whole ROM with no problem from:
https://mirom.ezbox.idv.tw/en/phone/davinci/
Anyway, try with the following - patched from my Magisk Canary:
https://mega.nz/file/09M13QhI#4AXcEYviHw_1xyhCoDYZh_J41Iu58ulozuRJbhQZP6w
You can test just by temporarily booting to the patched image (if it boots ok, then you would really flash it):
fastboot boot boot-Magisk_Canary_20405-davinci_v11.0.5.0_QFJIMXM_aaab5b40c7_10.0.img
Download and install the corresponding Canary Magisk Manager e.g. app-release.apk, from:
https://github.com/topjohnwu/magisk_files/find/canary?q=
If you have a bootloop it could be due to the previously installed Magisk modules - you would need to disable them in TWRP:
/data/adb/modules
and to every subfolder add an empty file named "disable" (or delete the whole modules folder)
Click to expand...
Click to collapse
Ty very much for replying with a complete guide and files needed. I managed to get a boot.img for my version and patched it successfully with stable magisk manager. I'm very grateful for your efforts tho.
Btw, any special reason for using canary builds in your steps?
9
galelouch993 said:
Ty very much for replying with a complete guide and files needed. I managed to get a boot.img for my version and patched it successfully with stable magisk manager. I'm very grateful for your efforts tho.
Btw, any special reason for using canary builds in your steps?
Click to expand...
Click to collapse
Canary has some early fixes and features, but also some new bugs
E.g., for a long time, Canary has a new UI. It was buggy and with issues but now is already good and stable andI I like its new features
But just realized that V4A cannot install driver with yesterday's Magisk Canary 20401 so I returned back to Canary 20405
Edit:
Btw, you can try Magisk Manager Canary - install from the link in my previous post.
It should work with your stable Magisk
By using Stable Channel, you can always return to stable Manager 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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Downloads
Official Website
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
gapps (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partitions zip is crucial in order to prevent bricks. It only needs to be done if you're coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Only use TWRP version 3.3.1-0, it has an advanced option for recovery bootloop fix. Sorry for some hassles with TWRP. It is not ROM related but the version I use works 100% of the time.
My apologies for any confusion/problems flashing!
Preparation for A/B Roms:
01. Download TWRP version 3.3.1-0 (do not use any other version)
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use the terminal to boot the latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmware.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash GAPPS + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
SOURCES:
ROM: https://github.com/crdroidandroid
Changelog::
https://raw.githubusercontent.com/crdroidandroid/android_vendor_crDroidOTA/10.0/changelog_ocean.txt
Known issues:
<!-- list here -->
Visit official website @ crDroid.net
crDroid Community Telegram
Donate to help our team pay server costs
© 2020 GitHub, Inc.
XDA:DevDB Information
CrDroid, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/Rondeau79/android_kernel_motorola_sdm632
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest TWRP unlocked bootloader
Based On: AOSP, Lineage OS
Version Information
Status: Stable
Current Stable Version: QQ2A.200305.003
Stable Release Date: 2020-03-22
Created 2020-03-22
Last Updated 2020-06-23
Reserved
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
flash713 said:
Ahh the ole triple posts. Don't you just love it when that happens. lol. Hell of a job on this! Will Android 10 for Ocean device ever be able to have an enforcing kernel or no? Probably waiting for source for 10/Q before messing with all that stuff? I'm just curious and figured I'd ask.. Awesome work!!!! :good:
Click to expand...
Click to collapse
Thanks, this one was a tough task to get done. I don't mind a permissive kernel. I really don't dive too far into the Android system. I am a fan first and a developer second! I still really don't have an understanding of code and stuff. I just go with my instincts.
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
danny8 said:
I performed a 'dirty flash' coming from crDroid 5.12 (based on Android 9).
I did not delete my Google account from the phone prior to flashing. This is the first time I've had problems upgrading crDroid. I realize it's also the first time I've done a major increment to the underlying Android OS.
Upon first boot I saw the new boot animation (it looks great!) but the phone did not complete booting after about ten minutes. I interrupted the boot by holding the power key. I tried wiping data. Later, I also tried re-formatting data partition (including built-internal media). I also tried re-installing the most recent version of crDroid 5.12 with no success with that as well.
Suggestions regarding the best way to correct this would be helpful and appreciated.
In the meantime, I'll look around and trying some other things. I hope it might be corrected without having to resort to ADB / PC connection, but I'll try whatever I can.
I don't know if this result is considered "a brick" because I can boot into TWRP.
Click to expand...
Click to collapse
You are not bricked. When coming from one version of android to another a clean flash must be done. You can dirty flash after that. Wipe both boot slots and then go about flashing like normal. First boot takes a while. It won't boot without wiping the system partition.
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
D13Gho said:
Excuse my ignorance, where do I have to install the rom, gapps and magisk, in slot A or B? Thank you in advance (sorry bad English)
Click to expand...
Click to collapse
With the A/B partitions scene. When you flash a ROM it will be installed to the opposite slot. If you are on A then the zip will be installed to B and vica versa. Gapps are flashed after you reboot to recovery when you are on the boot slot the ROM was installed on same as Magisk.
Thank you, Rondeau79. I got it installed.
It looks great!
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Johnfoo19 said:
I've got every thing installed and running, but after setting up my apps (Chrome, messages, photos) app opening/closing is quite laggy. It become unusable after a couole hours.
Click to expand...
Click to collapse
Give it a little time to set in. Usually a fresh install takes a bit.
danny8 said:
Thank you, Rondeau79. I got it installed.
It looks great!
Click to expand...
Click to collapse
You're welcome.
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
cgrimm9 said:
pie had the option of changing colors in the display settings I am not a fan of blue I like black and red. is this in a future update it was the main reason i uninstalled the other android 10 roms
Click to expand...
Click to collapse
Go to display styles and wallpapers to change to colors.
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
n00b Samurai said:
Is there any way to set the position of the battery bar? like bottom of the screen or lower status bar because where default is top of screen you kinda miss half the bar because of the notch
Click to expand...
Click to collapse
Sorry there isn't, I can't change the base features of the ROM. However you can change the color and thickness of the bar and it's position on the screen.
You can always adjust the screen in order to account for the notch. It's in the developer settings.
barados742 said:
Has anyone had any issues with mobile data not working after installing this ROM? I was able to make calls and send texts (I have Sprint, phone: Moto G7 Power X1995-5). I reflashed it and OEM locked back to stock firmware since mobile data was not working. Also, I did not have SD card since I don't have one
Click to expand...
Click to collapse
You need an external sdCard for flashing ROMs. Wiping the user partitions properly is essential for a properly working ROM. If you just have internal storage then the installation of an OS won't be done right.
Thanks for the reply! I just bought an SD card and will try it tomorrow and will respond if it worked.
Good morning, guys I tried to install on my MOTO G 7 POWER 3/32 and the rom does not install says it is not compatible with the system. Any tips?
{
"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"
}
Code:
We are not responsible for bricked devices, dead SD cards,
thermonuclear war, or you getting fired because the alarm app failed. Please
do some research if you have any concerns about features included in this ROM
before flashing it! YOU are choosing to make these modifications, and if
you point the finger at us for messing up your device, we will laugh at you.
WORKING:
Decryption userdata with eu roms
Screen brightness settings
Correct screenshot color
MTP
ADB
Vibration
Sideload
To flash the TwrpDownload the recovery and copy to adb folder
Open terminal
Code:
fastboot flash recovery nameofrecovery.img
fastboot boot nameofrecovery.img
or
fastboot reboot with vol + to boot
Source Codehttps://github.com/geoanto555/android_device_xiaomi_gauguin
https://github.com/TeamWin/android_bootable_recovery
Prebuilt Stock Kernel
Thanks to TeamWin Recovery Project
all testers and developers
Thanks to Μιχάλης (chariPower) for the information(sideload)
Download Link-stwrp_gauguin_3.5.A10_05-01-2021
twrp_gauguin_3.5.A10_07-02-2021 fixed sideload and mtp
twrp_gauguin_3.5.A10_18-02-2021 fixed backup data error 255 (/data/extm)
twrp_gauguin_3.5.A10_05-03-2021 Fixed Mtp after format data & reboot recovery. (if the MTP does not open, try reboot in twrp again)
twrp_gauguin_3.5.1.A10_30-03-2021 fixed fastbootd
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success？i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
kien_vip said:
it’s first time i am using xiaomi phone. my device is RMN9P5G and waiting for unlocked. can i flash your recovery and install the latest stable EU rom in mifirm.net: V12.0.8.0.QJSCNXM immediately after unlock success？i’m worry a bit because some members report that internal, user data be encrypted and cannot access..
Click to expand...
Click to collapse
From my experience, the recovery cannot decrypt the stock ROMs, you have to flash a custom ROM (Arrow and Lineage are the only 2 right now), or flash a xiaomi EU ROM.
Copy the rom to sdcard or usb otg.
Format data
Reboot recovery
Flash rom.
With xiaomi eu decryption works...
Decryption on stock rom works if I hotboot TWRP (fastboot boot twrp.img). If I flash it, TWRP doesn't prompt me for a password when started and keeps data encrypted.
Hi there, thank you for the TWRP. Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
not for now. I will upload new version soon
ilyachelsea said:
Is there any chance to decrypt also user 999 for the Dual apps on the .eu ROMs?
Click to expand...
Click to collapse
twrp_gauguin_MI10TL-RN9P5G_MI10I_3.5.A10_18-02-2021_BL-L
Fixed backup userdata (error 255 for data/extm)
User 999 can be decrypted only with default password ( without pattern-pin-pass) for now.
Thank you, but my password is PIN, anyway the recent twrp can't decrypt user 999. It is the message in red: "Failed decrypt user 999"
Only without pin,pass,pattern can be decrypted user999
It's a pity. I intend to back up also user 999 to keep my dual banking apps with the access data. If I first remove the PIN, and backup user 999 with the TWRP, after restore I will have to set up access again. This kills the benefit of the decryption and makes backup of 999 useless.
Thank you anyway and I hope, NO PIN is the temporary requirement of this version.
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
devedel said:
Hello everybody! Last week I unlocked the bootloader of my gauguin and initially I tried the official TWRP Recovery released by TWRP official page but it didn't work correctly and I couldn't flash zips, so I tried this beta version released by geoanto555 and it worked smoothly, I flashed zips and I had root permissions... But last night the smartphone had the battery low and it turned off, when I connected it to the charger it automatically reboot in fastboot and I can only enter in recovery mode. Sorry but I'm new in the modding world and I don't know what to do.. First brick.. What I did wrong? Anybody can help me? Is there anything I can do or I have to buy a new phone? Thanks to who will answer . Good evening.
Click to expand...
Click to collapse
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
AnibalSP said:
If you have access to the recovery, or fastboot, you can flash the original firmware with fastboot, but watch out, for some reason, when i flash the original rom from Windows using fastboot, it crashes, but with Linux it just works
Click to expand...
Click to collapse
I'm trying to do this with XiaoMiTool v2.. Thanks
devedel said:
In my device the rom is still the original. Do I have to do it anyway? What can happen if I try to flash a custom rom? If I only do the factory reset will I lose also TWRP?
Click to expand...
Click to collapse
If you can boot to android, or boot to TWRP / Orangefox, you don't need to flash again miui stock
If you flash a second rom, the worst thing that can happen, is that the rom may not work, but you wipe the internal memory (dalvik cache and data) and it should be running again
If you loose twrp for some reason, you can flash it again with xiaomitoolv2, or with fastboot
I'd recommend to you to try rooting, installing roms and similars things in an old phone if you don't are confident / know what are you doing, you will learn a lot in a few days of tinkering.
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
devedel said:
View attachment 5257349
Anyone know what I need? I can't finish the installation of a official xiaomi rom to unbrick my device
Click to expand...
Click to collapse
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
fizzy900 said:
Hi,
Download the official stock rom
Dont use XiaoMiToolV2, instead use MiFlash (official tool). Works for me every time. Then connect your phone in fastboot and flash all, I use the clean all and lock option which relocks my bootloader but you could just clean all and leave the bootloader unlocked. Then you can start again
Click to expand...
Click to collapse
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
devedel said:
Hi, thanks for your advice.
Do you think it can works if usb debugging is off? I'm afraid I've disabled it the night the phone bricked.
I did wrong too many things but was my first try, tomorrow I'll buy a new Mi 10t lite and I'll try again, using more precautions.
Thank you all anyway, good evening.
Click to expand...
Click to collapse
Enabled debugging is needed for adb when the system is running. For fastboot it does not matter.
{
"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"
}
In the spirit of moving custom ROM development along for the 2019 Galaxy Tab A 10.1 [SM-T510], here's a build of LineageOS 19.1 I just created based on the latest OEM stock firmware and @AndyYan's latest LineageOS 19.1 GSI. It's very much a work in progress, but it should hopefully help blaze the trail for even more custom ROMs for this tablet.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and this one is based on the latest Android 11 release (T510XXU5CWA1).
Stock recovery will be replaced with my latest TWRP build for the SM-T510.
This is unofficial and unsupported, so the usual caveats apply. Since we don't flash the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.tar.md5 (Odin tarball)
lineage-19.1-20230403-UNOFFICIAL-T510XXU5CWA1.zip (TWRP update)
Build archives:
Android File Host
Change Log:
20230403:
Updated to LineageOS 19.1 GSI (20230323) with March 2023 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CWA1).
Includes TWRP v3.7.0 custom recovery built on AOSP 11.
20220918:
Initial release based on LineageOS 19.1 GSI (20220912) with Sept. 2022 security patch and GApps.
Based on the latest Android 11 OEM kernel and vendor partition (T510XXU5CVG2).
Includes TWRP v3.6.2 custom recovery built on AOSP 11.
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install custom ROM tarball (.tar.md5 file) to AP with Odin
If TWRP launches, factory reset with Wipe->Format Data and reboot to system. (Not necessary for incremental upgrades.)
From existing TWRP install:
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install, Install Image, select your update (.img file), and then swipe to install
Factory reset with Wipe->Format Data. (Not necessary for incremental upgrades.)
Reboot to system
Source:
android_device_samsung_gta3xlwifi
treble_build_los
Phh-Treble
Donations:
Your support is always appreciated! Just click here.
I'm leveraging a ton of work done by @AndyYan and @phhusson for Treble GSIs, so please show them some love here and here!
Reserved
Thank you dear @Magendanz very much for keeping my Old Youtube Tab Alive!
Quick Question, is an update from "lineage-18.1-20220417-UNOFFICIAL-T510XXU5CVB1.zip" to the new 19.1 Possible or do i have to update the base version first?
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
NJey90 said:
Good evening Mr. Magendanz,
i installed this ROM on my Samsung SM-T510 and my tab/back/home buttons are not in the middle/bottom position they are in the right corner (i had this issue also with another unffocial lineage Os 19.1 Rom for SM-T510)
How can i solve this ?
Click to expand...
Click to collapse
Is the task bare active? I have the same layout when it is. You can turn it off in settings, but research the bar, you might want to use it.
@Magendanz , I dirty installed it over my lineageos gsi, and it works great so far. One problem I see, and had with the gsi is that I have a notification to finish installation, but there is no way to get past the network selection. There is no button to either skip or continue. Is there a way to fix this?
Thank you for this - I know how hard it is given your other responsibilities!
Thanks Magendanz for this news!
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Thanks.
galoneta said:
Coming from LineageOS 17.1 (lineage-17.1-20200812-UNOFFICIAL-T510XXU3BTFN), what would be the sequence of steps for updating to this rom ?
Click to expand...
Click to collapse
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Magendanz said:
I recommend you download and install the T510XXU5CVG2 firmware, do a clean install with Odin...but intercept the restart by holding Vol Up & Down so that you reenter Download mode. Then, install this custom ROM with Odin and intercept the restart by holding Power + Vol Up to enter TWRP. From there, do a factory reset and reboot to system.
If you inadvertently miss the restart intercept and have to run through OEM setup, make sure to connect to the Internet and then enter Developer options to disarm Vaultkeeper. Don't try to flash anything else until you've verified the OEM Unlock is still on (but disabled).
Click to expand...
Click to collapse
Thanks Magendanz for this clarifying tutorial!
So you must first always update \ have the samsung base AND the custom recovery to a MINIMUM combination set? In this case the minimum "combo" set would be a samsung rom with android 11 as base (and recovery 3.6) right ?
Will try this sequence and give feedback as soon as possible.
Thanks again.
Hey there, just wondering -- does hardware video acceleration work on this build seeing as its based on a GSI? Thanks
I tried to flash this on T515 via twrp. Seems like it only detect and allow install on t510
Can you also make a variant for sm-t515?
Cheers and thanks
dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
lewmur said:
In the ten or so years I've been dealing with Samsung tablets and XDA, I must have seen this question asked at least a hundred times. "Can you make the wifi ROM work on the LTE version?" of whatever tablet or vice versa. And the answer is always "No." They are two different animals and normally the dev has one or the other. And it is very difficult to make a ROM for a device you don't have. And the same thing goes for tablets with the S Pen. They are NOT the same.
Click to expand...
Click to collapse
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
dissidius said:
of course mate i like your passion in explaining such things but i belive *i can be wrong of course* that i wasn't asking on a Xiaomi Poco thread..... this two devices are very much similar, smt510 twrp works correcly on smt515 for example. Just maybe the rom could also work with some little tweaks. Thanks
Click to expand...
Click to collapse
Yes, TWRP can work on both but recovery doesn't access the LTE modem. And, again, I'm stating MY experience from over ten years of having people ask the question about many, many SAMSUNG tablets only.
Has anyone successfully installed MindTheGApps on lineageos19? did you use an sdcard or adb or some other method? I don't have access to an sdcard but I am curious if this is the only way. I have not been successful in using adb..... yet!
This version of Lineage 19 already has Gapps installed. So MindtheGapps is not needed. Installing it using the tar ball and Odin means you don't need an SD card. Or have I missed something?
dissidius said:
Can you also make a variant for sm-t515?
Cheers and thanks
Click to expand...
Click to collapse
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
DingusestDingus said:
I installed this on my T515 via TWRP and it worked just fine. Haven't tried LTE though, but the os installed perfectly.
Click to expand...
Click to collapse
Scratch that, I restarted it and its now in a bootloop
This is the 2019 version. I can't get this to install. Bootloader is unlocked and tablet is rooted