Database Info

My own Mi 4c journey

My Mi 4c arrived yesterday. I bought it using donations that I received from various project (Samsung Galaxy Tab 2, Tab 3, Tab 4, OnePlus One, Xiaomi Redmi 2). It's seems for Chinese market: a lot of Chinese apps, incomplete English translation, no Google services. Fortunately, TWRP port already available for this device, so rooting and installing GApps is easy. Somehow I still want to keep the original recovery.
1. Boot to fastboot mode (VOL DOWN + POWER) to fastboot TWRP:
Code:
fastboot boot twrp.img
2. Flash SuperSU in TWRP
3. Flash Open GApps nano in TWRP
As you know, loading touchscreen firmware need times in TWRP. Just do other thing while waiting for it :laugh: The possible cause is firmware "ping-pong" issue when in kernel touchscreen firmware different between recovery and normal boot. But why loading a firmware so that long?
My device come with MIUI 7.1.4.0, unlocked bootloader. I just upgrade it to 7.2.1.0 without firmware update to keep the bootloader unlocked but use 7.1.6.0 kernel to boot it because no go with the new kernel (incompatible firmware?), MIUI logo forever. BEWARE: Don't upgrade your device to 7.2.1.0 using a standard method, your bootloader will be locked!
Attached Hardware Info report for my future reference if I decide to develop custom ROM/kernel.
@emfox, I'm with you :laugh:

MIUI 7.2.1.0 without firmware update.

how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....

tuanhung303 said:
how can you update to 7.2.1.0 version without firmware update?
btw, I think I will wait for Xiaomi EU or sMIUI, so I can flash them via twrp....
Click to expand...
Click to collapse
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.

I hope you can make modified rom 7.2.1.0 without bootloader.

ahmaman said:
I hope you can make modified rom 7.2.1.0 without bootloader.
Click to expand...
Click to collapse
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.

welcome aboard, my dear friend!

Looks to me, we got another developer. Good

ketut.kumajaya said:
Backup /system/lib/modules, download 7.2.1.0, inject a modified updater-script, flash it in TWRP recovery, restore /system/lib/modules, reflash SuperSU, reflash GApps.
Click to expand...
Click to collapse
omg... is that English? (j/k)
btw, welcome onboard , Xiaomi will release some kernel sources soon, looks like we will have more stable rom in future :laugh:

ketut.kumajaya said:
Uploading a big file always a problem for me. Maybe I'll create a proper instructions and script for it.
I confirm touchscreen "ping-pong" issue the source problem of TWRP touchscreen freeze on boot. If touchscreen driver found a different firmware version, it will flash a "proper" firmware and delayed touchscreen event initialization.
Click to expand...
Click to collapse
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them

Logic_ said:
Thanks for documenting your findings.
I can tell you I've never experienced the touchscreen bug since day one, I flashed Team Superluminal's TWRP 2.8.7.3 and I can press all buttons soon as I see them
Click to expand...
Click to collapse
yes, the version 2.8 does not have that bug, the version 3.0.0.2 has

Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!

wind99 said:
Happy to see Indonesian Developer who will contribute in Mi4C Section. really want to meet you in person if have any chance.
Greeting from Indonesia!
Click to expand...
Click to collapse
Still slowly check Xiaomi changes line by line https://github.com/kumajaya/android_kernel_xiaomi_msm8992/commits/libra-l-oss-kumajaya :laugh:

[ELITE KERNEL][Honor 8] For Build CxxB36x by HassanMirza01

DESCRIPTION:
Hey guyz..... Me Hassan Mirza from Pakistan
Today am here with a new thread and I Have a good news for you....
As you know, The other methods are old now and also, in Nougat, there is root which needs to mount system each time you need to use it,,, so Today, your system mount and root problem solved... Phh or Magisk, you choose
Releasing Elite Kernel v2 ported from P9 Lite
Its PreRooted, System RW available for all time, Titanium backup works perfectly and Magisk work too for it to hide root
With this you can flash anything and see in SYSTEM ! VIPER...adaway no systemless...etc...
DISCLAIMER:
I will Provide correct info and help......All This you are gonna do is At your Own Risk... Damage to your device of any type is at your Own Responsibility,,, Don't point finger at me or I will Just Laugh at you...
Install:
1.) Download this Elite Kernel for Honor 8 CxxB36x v2
2.) Put in Root of SD Card.
3.) Flash this in Latest Recovery for Nougat.
4.) See if Superuser app installed, if not install Phh Superuser from google play.
5.) And you are ROOTED.
The file it's boot.img is based upon L04-C567B360, modded and signed for boot.
Its Adviced to remove pattern Lock and Fingerprint Lock before installing.... just adviced,,,
If you like, donate
Hit Thanks and Support me if you Like and get help from this thread...Thank you...
Changelog in 2nd post...
This is Based on Stock Huawei Kernel, Not compiled by Me...
Contributors:
@HassanMirza01 for doing all this
@phhusson for his wonderful work of making Phh superuser
@Telperion as he got my attention for doing this
Status:
Status: Stable
Stable Release Date: 2017-04-27
Created on: 2017-04-04
Last Updated on: 2017-04-27

CHANGELOG:
2017-04-04 Elite Kernel for B3xx by [email protected] v1: Initial release,
2017-04-27 Elite Kernel for B3xx by [email protected] v2: The Most wanted MagiskSU released with Proper Support,,, Use with Cautions...

This is all really good stuff.
Thank you for sharing your work
John

Guyz if this kernel didnot working, booting for you or crashing your settings app,,, send me the boot.img file of your own variant of Honor 8... I will see into it...

awesome! Thanks for your hard work on this! Will this work with the LineageOS build that @surdu_petru and team have been working on?

I think no.... Like Lineage 14.1 for P9 lite,,, we need to go to MM to install it... So lineage kernel according to my guess, works on MM based roms so Elite Kernel wont work with it :/

HassanMirza01 said:
I think no.... Like Lineage 14.1 for P9 lite,,, we need to go to MM to install it... So lineage kernel according to my guess, works on MM based roms so Elite Kernel wont work with it :/
Click to expand...
Click to collapse
So this doesn't work on nougat? I guess the support for magisk tells me it doesn't. Bummer.

If the kernel is based on B360 then it should work with N and not MM. The Lineage rom right now is using the stock N kernel with no changes to it. They are not building a N kernel inline with Lineage as there's no source code out for it.
I guess my question is, would it be possible to flash Lineage, and then flash this kernel over it?

my Kernel is on Nougat based ROM not on MM but someone should try it on lineage too.....and tell the result...

@HassanMirza01 -- kernel works and PHH SU works and can R/W /system/. One issue I noticed however is that "Revoke USB Debugging Authorizations" has disappeared from my Developer menu. On the Honor 8 with Nougat I frequently have to revoke and reset authorizations to get it to work properly. I was able to get it working again by flashing the stock boot and rooting with the linked zip.
Magisk, however, crashes the phone on installation attempt, even with SELinux set to permissive. It causes a reboot when 'setting up the environment' either through Magisk Manager or TWRP. It appears that the P9 Lite kernel must have proper loop support whereas the Honor 8 still doesn't even with tweaks. It was speculated that since on the P9 Lite Magisk wouldn't work on Nougat, but on the P9 Lite after flashing this kernel and flashing Magisk in permissive SELinux mode, it installed successfully, that a similar path might work on the Honor 8. Then again, perhaps something is workable.
Either way, thanks for looking into this. :good:
https://drive.google.com/file/d/0B0zE1Kk8sIB6eVplODFjaTh4Q0U/view?usp=drivesdk

i will release a next build soon for some bugs fixes.... also, magisk proper support is coming soon,,,

Here's a log of what happens when I try to flash Magisk.

bro send me recovery log,,, i cant understand the one you send above...

Here is a zipped boot.img for honor 8 frd-l19 C432b360

HassanMirza01 said:
bro send me recovery log,,, i cant understand the one you send above...
Click to expand...
Click to collapse
Unfortunately Recovery crashes before it can write what happened to the log. That kernel crash log up above is the closest info we can probably get.
I attached the TWRP log though anyway.

Telperion said:
Unfortunately Recovery crashes before it can write what happened to the log. That kernel crash log up above is the closest info we can probably get.
I attached the TWRP log though anyway.
Click to expand...
Click to collapse
Also another log, this one shows the beginning stages of the flash and where the crash happens. (Search Magisk in the text file)

Expected release date: when kernel source comes out.
Just to makes this clear, we have no proper loop support and thats why magisk will not work (just take the dmesg from the user above as example, it tries to create a new loop volume and directly crashes ..)
Regards

svardman said:
Here is a zipped boot.img for honor 8 frd-l19 C432b360
Click to expand...
Click to collapse
Bro i didnot find the boot.img in your provided zip... Just check the size of your uploaded zip...

HassanMirza01 said:
Bro i didnot find the boot.img in your provided zip... Just check the size of your uploaded zip...
Click to expand...
Click to collapse
My Bad, gonna fix it later on today,

Does the new version of TWRP thats released help this ?
I know i was finnaly able to just Flash TWRP > flash SUPERSU 2.79 to root and thats it ! no pre modfiied boot.img needed . perfectly working now

[PATCH] Post-install patch for GSI ROMs 2.0.0

Hello XDA, this patch is intended to fix issues that arise from using phh-based Treble GSIs. This patch aims to make
life bearable on these ROMs and to add the functions that are missing from EMUI 8 and the OpenKirin ROMs. With
this patch you can use any working Pie or 10 GSI and have a complete experience, having to do as few manual tweaks as
possible.
What this patch does:
- Restores offline charging functionality
- Fixes crash on Bluetooth/NFC section in settings
- Fixes headphone jack detection
- Fixes the missing apps in Play Store
- Fixes battery stats behavior by supplying a correct power profile
- Fixes the lack of Night Light in AOSP-based ROMs
Tested P GSI ROMs:
- AOSP 9
- LineageOS 16.0 (AndyYan)
Tested Q GSI ROMs:
- AOSP 10
- LineageOS 17.1 (AndyYan)
Tested R GSI ROMs:
none
Installation:
1 - Flash eva_amend_x.y.z.zip on TWRP
2 - Wipe cache
3 - Reboot
Download:
here
Source:
You can analyze the patch to see the source code.
Credits:
lo_ol, hi6250 community, Wattsensi

Changelog
Code:
2.0.0
- Removed redundant fixes
- NFC is now responsibility of the GSI. This NFC fix was wrong on so many levels I can't even begin to describe.
- All prior versions removed from Google Drive
1.1.0
- Add HWComposer fixes
1.0.0
- Initial release

This looks really promissing - thanks a lot! How about fixing the issue with wifi hotspot for P9? Would that be doable as well?

@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone. On my (much newer) Nubia RM3, I unlocked the bootloader, flashed recovery, flashed the GSI and tadaaa.
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you

Nightwish1976 said:
@Wattsensi The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Click to expand...
Click to collapse
Basically you shall first rebrand and upgrade to Oreo to get treble support, here is how:
https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2

@xaweryp Thanks a lot for the input, now I'm downloading the files necessary to rebrand and update to Oreo.
LE: just finished updating to Oreo.
Can I just flash an A only Arm64 GSI, or are there another steps? I have that new recovery (Pretorianos80 v4), but I think it cannot access the internal storage...

Nightwish1976 said:
@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone. On my (much newer) Nubia RM3, I unlocked the bootloader, flashed recovery, flashed the GSI and tadaaa.
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you
Click to expand...
Click to collapse
Nightwish1976 said:
@Wattsensi Hi. I'm the new owner of an old P9 (EVA-L09) and I would like to install an Android 10 GSI ROM. The only problem is it feels much more complicated than on my other phone.
Click to expand...
Click to collapse
Hello. This device is abandoned, we're pretty much 1 or 2 developers working here. Yeah, I agree about the phone being complicated. It has so many quirks compared to my Galaxy S7 where everything just works out of the box.
This phone is not newcomer friendly, but with effort you can get through.
You can indeed install an Android 10 GSI but it's a poor user experience. Your choices are limited with this device, right now we have no working camera or NFC on 10. If you don't care running an older version of Android but still secure you can try @MSe1969's LineageOS 16.0 builds which incorporate the latest security patches and are updated monthly.
That ROM is designed to be used without GApps so keep that in mind.
Nightwish1976 said:
On the P9, I managed to unlock the BL, flashed TWRP and I'm contemplating what GSI should I flash. The treble checker app said the phone is not Treble compatible. It also shows as A-only ARM64.
Can you please guide me on what to install or point me towards a guide?
Thank you
Click to expand...
Click to collapse
First of all, do you have your unlock code in hand? You will need it when you perform the needed rebranding procedure. This will reflash your phone with a Chinese ROM so you can OTA-update to Oreo, which introduces Treble functionality into the device. Rebrand, update to Oreo and flash the latest (as of 09/2020) 8.0.0.550 firmware. Then flash the needed network patches to make your radio work, and then decrypt and install TWRP.
First, go there:
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
The second post contains upgrade instructions and be careful. Cheers!

Updated the patch. Now NFC functionality is responsibility of the GSI and removed useless stuff.

Android 11 Red Magic Rom [FLASHGUIDE]

Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!

nalin_s3 said:
Thanks for the update.
I have been planning to upgrade my Red Magic 3 to Android 10 (CN rom) for quite a while now. And its good to know A11 beta has arrived too.
Have you tried fps games on this device like pubg mobile, cod etc? Do they work properly ?
Also, I haven't even unlocked bootloader on my device. Can you proivde a better guide, to completely switch from global rom (stock) to A11 (beta) or A10 CN rom (stable).
Need links / guide for following items -
- Unlock bootloader
- Link of working twrp and steps to flash (should I change recovery after installing this beta?)
- Gapps and Magisk link (As I can't run this device without Google services).
It will be a huge help for me to get started.
Take your time with it (no rush).
Thanks in advance!!!
Click to expand...
Click to collapse
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!

Perseo99 said:
Hey!
No problem at all. I let you here two guides to migrate to the cn rom and even a gsi
Be careful and aware about what you are going to do, It's not specially difficult but you have to get ready all the files and tools in case of brick or bootloops.
Enjoy the flashing!
Click to expand...
Click to collapse
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ??

nalin_s3 said:
Thanks for the links. I am planning to update to stable A10 version for now.
I have few questions it be a huge help you could clear some of my doubts -
1. After unlocking bootloader I have to install TWRP (for gapps to run). So should I install TWRP after flashing CN rom ? or before ?
I am asking this because I read in some guides that only CN rom is custom recovery capable.
2. If you have run A10 stables before, does OTA updates require to be installed via TWRP only ?
Will I loose Gapps and Root access if I updated the ota directly from settings? And will every rom flash with TWRP clear my installed apps ?
Thanks in advance for helping!!. ?
Click to expand...
Click to collapse
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.

Perseo99 said:
Hello again!
I saw a post where leipnacht provides a link to the public beta of Android R. (I let you here a drive link to download it faster).
I flashed it and it's working properly on my device. There is some bugs, but the most part of the things works without problems (Personally, I didn't face any bug itself (only a low noise with the vibration by the moment), but there are some comments in the page of bbs nubia about some problems with other things.
The previous conditions from where I update to Android R Red Magic Rom were using a GSI in the Android 10 chinese version of the rom. So, the steps I followed are:
1. In the recovery, wipe data, cache and dalvik. Also, format data.
2. Flash in the Android 10 TWRP the Android R rom.
3. Flash this NikGapps Package , Magisk Debug and DFE (Encrypt disabler in order to be able decrypt data in the recovery). I also flashed Permissive_5 but I think there is no need to do it.
4. Boot and enjoy.
I will attach all the files and some screenshots for those who want to take a see to the rom. Personally, I feel no changes in this version, but, as always, the performance is great and it runs really smooth. It's a beta version, so I hope more changes in the future.
P.D. In order to get safetynet passing, I used HideProps Config magisk module. There is no big issues with it, and everything is fixable
P.d.2. This rom has antiroll-back active, so if you want to go back to previous version, you will have to use the unbrick tool
Click to expand...
Click to collapse
Can you check your pm??

There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool

jepoyxxv said:
There's no problem in flashing but take note there's no going back i mean you cant downgrade it anymore using unbric tool even if you flash rom using cmd it will not work my rm3s now is bricked theres no tool or method that can fix it right now. Unless someone make a new unbrick tool
Click to expand...
Click to collapse
I already went to 11 and flash to 3.11

But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me

jepoyxxv said:
But how did you flash android 10 3.11 in rm3s no matter what tool i use i cant fix my rm3s from being bricked by flashing android 11 beta can you tell me what did you do did you flash it manually in command prompt please help me
Click to expand...
Click to collapse
If you are in 11 beta and want to downgrade..just simple flash global version and again flash 3.11 done

What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.

jepoyxxv said:
What did you use to flash global rom lastweek i successfully installed android 11 beta and use unbrick tool to go back to global but i got bricked. And i cant fix it anymore.
Click to expand...
Click to collapse
I just flash global from otg and tham again 3.11

walkwitmeinhel said:
I just flash global from otg and tham again 3.11
Click to expand...
Click to collapse
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.

[email protected] said:
Could you please tell me where to download the 3.11 rom. I am not aware that this rom exists. Is this a CN or global rom? Thanks for your reply.
Click to expand...
Click to collapse
http://ui.nubia.cn/rom/detail/64

Oh! Didn't expect that. I just post this for Red Magic 3 device users. I don't know how RM3S actually works. Have you tried the unbrick tool from chinese version? Or just flashing the global rom from recovery is enough?

Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
Let's see. Here is a link for Red Magic 3S unbrick tool. Download the non-eu ones.
If you have a Red Magic 3 with Red Magic 3s software, I will provide you the link to the other unbrick tool.
Also, you can try flashing the global rom from the stock recovery included in the package of the A11 rom that you have download.

Thanks for replying my bro.. my device is rm3s i already use rm3 and rm3s unbrick tool.. downloading fire hose programmer and image was successfully but.. my phone is still corrupted... And one thingg i dont have twrp install in my rm3s thats why its hard for me to fix it.. can you please guide or teach me how to flash stock recovery using global rom i know how to use cmd and adb

jepoyxxv said:
Wait is there a chinese unbrick tool cn. version for red magic can you provide me a link.. unbrick tool 3/3s.global by jerry is not working anymore if you got brick by android 11 beta rom...
Click to expand...
Click to collapse
So then, It's not a problem of the unbrick tool, that is actually working properly. The thing is that you didn't know how to do a correct process to migrate from cm rom to global...
The first thing you should do is reboot the phone into fastboot mode (power+vol. Down). Then, connect the phone to the PC and type the next commands in the cmd:
Code:
fastboot devices
in order to see if your device is being recognized
Code:
fastboot oem nubia_unlock NUBIA_NX629J
to unlock the bootloader
Code:
fastboot flashing unlock
in order to make your phone able to boot with a modified software. In the moment you will enter this command, you will see a screen advising you about your data (it'll be erased once you accept to unlock flashing).
After that, you can reboot your phone, that will show you an screen advising you that the bootloader is open. Accept and continue without problems.
Tell me if you have been able to make your phone boot.

Perseo99 said:
Well, I will go in order:
1. You have to flash first in the stock recovery the Android 10 CN rom and then flash the custom recovery. There is no twrp avaible for global rom. Once in the custom recovery, you can flash Gapps and Magisk (in android 10 there is no need of DFE file, the recovery is able to decrypt data properly.
2. You don't need to get worried about OTAs, there is no a constant software update work by nubia for this device, but in case of update, you would flash the rom from the offcial page, with magisk and gapps again and be sure you keep the custom recovery.
Click to expand...
Click to collapse
Required in CN A10 + twrp A10, or maybe from CN A9 + twrp A9 to be able to flash

[ROM][T320][T325][Android 13] Unofficial LineageOS 20.0 Nightlies Tab Pro 8.4 Wifi/LTE (mondrianwifi/lte)

I'm not responsible for any damage to your device of any sort.
By flashing this, you take responsibility of anything that happens.
Process at your own risk!
If you want to check - please make backup. Better to store all partitions.
What works
audio
bluetooth
brightness
call/LTE (mondrianlte)
camera
DRM
OTA
video
wifi
wifi display
What doesn't work
Back camera preview : wrong rotation on preview in default app Fixed build 20221204
SELinux Fixed build 20221130
Instructions:
0. Patched TWRP for FOTA : mondrianwifi / mondrianlte
1. Factory reset if coming from another ROM.
2. Install ROM
3. Install GApps (optionally) [Recommended BiTGApps ARM 13]
4. Install Magisk 25.2 (optionally)
Sources & Changes:
Device tree mondrianwifi
Device tree mondrianlte
Kernel tree
Vendor tree mondrianwifi
Vendor tree mondrianlte
TWRP tree mondrianwifi
TWRP tree mondrianlte
Download:
Downloads: mondrianwifi / mondrianlte
Note to users: I'm not responsible if you brick your tablet. See the disclaimer above.
Contributors
LineageOS team for source code.
@retiredtab for helping make mondrianwifi to work on Android12
@khalvat for its work on porting msm8974 to Android12 (https://github.com/LineageOS-UL)
@pocketrule, @bierma32, @Yxo 6o6uka for willing to test WIFI builds and leaving feedback
@bmwdroid for willing to test LTE builds and leaving feedback
ROM OS Version: 13.0
Version Information
Status: Nightlies
Created 2022-11-27
Last Updated 2023-01-05

THX @phoval for the New LOS 20 Version.
Installed this as update over the Version 20221010 without issue's.

FOTA update notification works .

New build: SeLinux is enforcing

Perfect !!!
Amazing !!
Thank you @phoval !!!

Hello, good job.
Thank you @phoval

Installed and runs smooth. Sound, video & wifi works. Excelled work.

Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers

@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204

cwokel said:
Amazing, the previous versions made my tablet very slow, but this one seems to run well. Great job! Thanks to the developers
Click to expand...
Click to collapse
bierma32 said:
@phoval since I've installed the zram_ boot.IMG runs the ROM with out lags and crash's.
Thanks again for your work.
I will update today to the last Version 20221204
Click to expand...
Click to collapse
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz

@chkdsk90
Charge your battery to 100% and try another clean install, format also system and data .

chkdsk90 said:
my tabelt is still slow, even with this built. i did a factory reset. even my battery is draining extremely.
@bierma32 what is zram_ boot.IMG. can you provide me that file? can i flash it in twrp?
greetz
Click to expand...
Click to collapse
Provide logcat.
zram boot img was alpha kernel for test.
The changes are includes since 2nd december build.

how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar

chkdsk90 said:
how can i flash the patched TWRP? Odin doesn't recognize the twrp file because its a .img file and not .tar
Click to expand...
Click to collapse
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.

pocketrule said:
You can download an official tar file, flash it in odin, reboot to recovery and from there you can update twrp.
Click to expand...
Click to collapse
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file

chkdsk90 said:
And why is the link to a patched twrp? What exactly is patched? What is fota?
Sorry for the questions. I only know the Normal twrp. tar file
Click to expand...
Click to collapse
It's patched for FOTA. A simple internet search reveals, that fota stands for "Firmware Over-the-Air" 😉️ I.e. you can download and update the rom directly from the rom itself. If you (always) download and flash the rom manually / separately, you don't need the patched rom.

One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?

If I get a app not responding message and I hit wait it will repeatedly pop up despite the app responding again (dirty flash). Otherwise first impressions of this rom are good.

Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today

cwokel said:
One detail: the taskbar at the bottom does not disappear when I open an app, neither the three virtual bottons. Tried all configuration without result. Any hints?
Click to expand...
Click to collapse
Just disable it in system > buttons. It's customization during first setup.
You can enable gesture navigation too.
jacomail95 said:
Just asking, any plans or chances for mondrianlte to get an A13 build? I've got that device running an unofficial LOS A11 build (the latest OS available for it), and it still has official TWRP support as of today
Click to expand...
Click to collapse
If someone can find me one to buy?