[Custom ROM] [K-ROM-Universal] [Root+Xposed] V. 1.0 - EMUI 8.0.0.
This ROM is based on:
Huawei Firmware EMUI 8.0.0. and Kangvip ROM M8.828
It was developed and tested on this device:
Huawei P8 lite 2017 (Prague)
Model Number: PRA-LX1
EMUI 8 Build Number: PRA-LX1 8.0.0.394(C432)
- OTA updated
- free device, without branding, with root and
- TWRP recovery
The following mods have been integrated and activated:
- Call Recorder
- KangVip Advanced Settings
- Xposed
Whether the rom will work on provider branding, or another firmware version, can be
I don't guarantee, however, it should work on all free Huawei/ Honor devices with EMUI 8.0.x.
I successfully tested it on the Mate 8, the Honor 6x and the Mate 10 Lite.
Please create a backup of your data with the Huawei data backup.
The ROM will be installed as if you wanted to restore a TWRP backup.
Before the ROM installation, please create a TWRP backup for emergencies!
Recommended by me:
- kernel
- ramdisk
- system
Prerequisites:
- TWRP Recovery
- Firmware 8.0.0.394(C432)
- The device must be completely set up.
- Please perform a Google Account synchronization.
You are familiar with the matter and have already used TWRP Recovery is installed and
a backup is created on the ExtSd. The attached TWRP is mandatory. It is fully functional.
Lets go:
Instructions how to install the bootloader(OEM lock) and the Factory Reset Protect (FRP-Lock)
and ADB, can be found here in the forum. See also "Unlocking with DC Unlocker".
Instructions:
1. Install TWRP:
The download also includes ADB-Fastboot.
Simply copy the complete directory into your computer and run MAF32.exe from there.
The recoverys are already included.
ADB command for TWRP:
fastboot flash recovery_ramdisk twrp.img
2. Rom-Installation:
Unzip the download "2018-12-05-Universal.K-Rom.EMUI.8.0.zip" (1.15 GB).
The backup folder created in this way 2018-12-05-Universal.K-Rom.EMUI.8.0
into the TWRP-Backup folder copy to the ExtSd and only the system partition restore.
3. Advanced Wipe: Dalvik Cache and Cache
4. Rooting with Magisk 17.1 (18 not tested)
5. Reboot
6. Install Magisk modules.
7. Reboot.
Do not flash the kernel from the download. It's from the B390.
Thread update: 2017-12-14:
The pre-rooted stock magisk kernel is now available for download, as TWRP-Backup: "2018-12-14-rootet.magisk.kernel.B394"
Good luck!
....and remember: A Custom ROM is never as perfect as a Stock ROM.
You have to teach it something in between.
Developer:
"Kangvip" Huawei Development [Team HRT]
“G.Man." Huawei Root & Custom Roms [Team HRC]
Many thanks to:
Kangvip,Team HRT, Cris- (Android-Hilfe.de), Chainfire,
Stephen (Stericson) + Jmz Software, Team Win RecoveryProject, Pretoriano80 (TWRP), team MT,
and Huawei Technologies Co., Ltd 华为技术有限公司
WARNINGS:
If all this has worked with my device, it doesn't mean it works with everyone else. Follow the instructions
exactly to prevent damage. The execution is your risk.
NOTE:
Despite careful preparation, I cannot guarantee that no damage to the device or operating system will
occur as a result of the implementation of this manual and therefore accept no liability for any damage
or malfunction to hardware or software! If you are still unsure, follow these steps: Only follow the
instructions if any of the conditions mentioned (model number, Android version, etc.) apply to you or
your device. Read instructions carefully and completely, look up unknown terms. Check downloaded
files for viruses. Make a backup of important settings and data. Do not follow the instructions,
if you don't know what you're doing.
So good to see you back ! Thank you
Hi,
I'd bricked my device pretty bad with the trebble roms.
It now awakened again to live with DC PHOENIX.
Back to good old EMUI. Is still the best.
:good:
G.Man. said:
Hi,
I'd bricked my device pretty bad with the trebble roms.
It now awakened again to live with DC PHOENIX.
Back to good old EMUI. Is still the best.
:good:
Click to expand...
Click to collapse
Even openkirin's gsi ? Havoc 2 works on my prague for 3 months w/o problems (Wirmpolter's gsi hi3660 mate 9 thread).
I test your rom now...
Nice evening (and EMUI)
Hi i have a B360 version firmware, the latest for my branded phone. Can i install your ROM whit this version? If yes i have to restore only image partition or others?? Sorry for my English
The system is for the 394. With the kernel (into my twrp backup) it also works on the 390. Otherwise not.
Sorry, I made a mistake in the manual and confused the installations steps. I have corrected that now.
G.Man. said:
Sorry, I made a mistake in the manual and confused the installations steps. I have corrected that now.
Click to expand...
Click to collapse
With the new manual, it boots! It works perfectly now.
Xposed not tested, magisk 18.1 does not work, 17.1 (provided by you) works.
Let's debloat and tune it... A huge thanks for this rom !
actinhic said:
Let's debloat and tune it...
Click to expand...
Click to collapse
I'm glad you were successful. Remember when tuning that it has only a stock kernel.
I have the rom now 4 weeks in operation. Everything runs perfectly.
I can't get it to work , keep bootlooping at huawei bootanimation screen...
Managed to make it work , but I can't pass basicIntegrity and CTS from SafetyNet
hexxr said:
I can't get it to work , keep bootlooping at huawei bootanimation screen...
Click to expand...
Click to collapse
Roote again with magisk 18.
hexxr said:
Managed to make it work , but I can't pass basicIntegrity and CTS from SafetyNet
Click to expand...
Click to collapse
A positive result is not possible with this rom. Maybe you are lucky if you uninstall xposed. In "system/framework", delete "XposedBridge.jar" and reboot.
Hi, has anyone tested XPosed, and does it work?
I tested xposed and I confirm it works (if you're still interested).
The ROM performs very well, nice (magisk and xposed out of the shell and Kangvip settings) there is one, big drawback although I'm only 90% sure: it sets FRP to lock. @G.Man. (OP) do you know something more (is that correct, how to avoid it) ?
That's not a problem. In the developeroptions, activate oem unlock and usb debugging and the frp is unlocked.
thanks for your prompt reply; unfortunately oem unlock is disactivated and grayed out (usb debug is activated)
Repeat the oem unlocking with the huaweicode.
first of all thanks for the support!
I can repeat the bootloader unlocking with the huawei code but my problem is only the FRP lock: phone is correctly unlocked. Do you confirm I should do what you're suggesting ?
Related
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
HOW-TO Root, Install Custom Recovery (TWRP) and Restore Stock ROM guide: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 8.1)
- V05_20181029: http://forum.cubot.net/viewtopic.php?f=21&t=2357&sid=60b6f72a20ca3fbe3fad47d8791714ee
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Stock (Android 7.0)
- V19 171030: http://forum.cubot.net/viewtopic.php?f=21&t=1563
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
- V14 170719: https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
Flash Tool
- SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.1.1 by @MDSDev : https://mega.nz/#!UF1DgYAD!WKWhCyXdFxfAKwRfpWF1Lsm_zLC4vt0-mMK4rMHzfqc
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
Extras (Root-Only):
Customization
- Xposed Framework (not available on Nougat yet): http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
Alberto96 said:
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
HOW-TO Root, Install Custom Recovery (TWRP) and Restore Stock ROM guide: https://docs.google.com/presentation/d/1NJcDBkLk8zMwyv2BTqRjn2NB_ZOWKjP1fRpSVr44Oxk
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 7.0)
- V14 170719: https://mega.nz/#F!YIt2UKLL!E2PGw3IJ_KeCuVwXhstdFw
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
- None yet.
Flash Tool
- SP Flash Tool for Windows and Linux: http://www.needrom.com/download/sp-flash-tool-v5-1640-2/
Recovery:
- TWRP: Working link required, the one from @megthebest online is gone.
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
Extras (Root-Only):
Customization
- Xposed Framework (not available on Nougat yet): http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
Click to expand...
Click to collapse
Hey didn´t you read replies in your device review thread?
Twrp not working on nougat (api24) that device!
Also since a few weeks xposed support for nougat!!
Greenif seems to be useless on nougat duo the fact it use dura speed app etc.
SuperSu also not working with v14 installed instead "we" use Magisk by flashing boot.img
which is possible to flash by device own "updater" without any additional tools.
here are all needed files
Both old twrp for Anroid 6 + useful tools tested by me
https://forum.xda-developers.com/showpost.php?p=70426723&postcount=6
and here is how to really root the cheetah with v14 (nougat) + recovery advice and useful tools
https://forum.xda-developers.com/showpost.php?p=74099611&postcount=46
My provided downloads working without register somewhere else! Most are direct downloads from source :good:
toBsucht Psp said:
Hey didn´t you read replies in your device review thread?
Twrp not working on nougat (api24) that device!
Also since a few weeks xposed support for nougat!!
Greenif seems to be useless on nougat duo the fact it use dura speed app etc.
SuperSu also not working with v14 installed instead "we" use Magisk by flashing boot.img
which is possible to flash by device own "updater" without any additional tools.
here are all needed files
Both old twrp for Anroid 6 + useful tools tested by me
https://forum.xda-developers.com/showpost.php?p=70426723&postcount=6
and here is how to really root the cheetah with v14 (nougat) + recovery advice and useful tools
https://forum.xda-developers.com/showpost.php?p=74099611&postcount=46
My provided downloads working without register somewhere else! Most are direct downloads from source :good:
Click to expand...
Click to collapse
I haven't because replies were not clear enough, a bit confusing and not ordered at all.
Be free to write here a detailed and more ordered post so that I can link it to the first post.
P.S.: never quote the first post. Thank you
Just one quick question, I'm in a dilemma...
I'm preety familiar with MTK chipsets and flashing, but I need to know this. Planning to root my Cheetah 2 on Nougat using Magisk I patched my boot image, but to flash it via fastboot I need to unlock bootloader so that is a no (don't wanna lose all my data).
So, if I use SP Flashtool to flash the patched boot image is there a possibility to end up in a bootloop, since I didn't unlock bootloader?
Thanks in advance.
EDIT
Never mind, tried and succeeded with SP Flashtool, no need to unlock bootloader. I wasn't able to flash boot.img via fastboot, it required unlocked bootloader.
toBsucht Psp said:
Hey didn´t you read replies in your device review thread?
Twrp not working on nougat (api24) that device!
Also since a few weeks xposed support for nougat!!
Greenif seems to be useless on nougat duo the fact it use dura speed app etc.
SuperSu also not working with v14 installed instead "we" use Magisk by flashing boot.img
which is possible to flash by device own "updater" without any additional tools.
here are all needed files
Both old twrp for Anroid 6 + useful tools tested by me
https://forum.xda-developers.com/showpost.php?p=70426723&postcount=6
and here is how to really root the cheetah with v14 (nougat) + recovery advice and useful tools
https://forum.xda-developers.com/showpost.php?p=74099611&postcount=46
My provided downloads working without register somewhere else! Most are direct downloads from source :good:
Click to expand...
Click to collapse
The steps above worked for me. Im currently runnig android 7 v14 stock rom rooted..?????
And twrp works great.
Update
Ok, so this thread needs to be updated.
New working TWRP 3.1.1-1 for Nougat by MDSdev:
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Some new official rom (V19 171030), however on Android 6.0:
CUBOT_6143C_CHEETAH_2_V19_20171030
nlooooo said:
Ok, so this thread needs to be updated.
New working TWRP 3.1.1-1 for Nougat by MDSdev:
https://www.needrom.com/download/twrp-3-1-1-1-mdsdev/
Some new official rom (V19 171030), however on Android 6.0:
CUBOT_6143C_CHEETAH_2_V19_20171030
Click to expand...
Click to collapse
Whoops. Updated.
I found a V19 n0 release (Nougat 7.0) from the official CUBOT forum so i linked that one instead.
Alberto96 said:
Whoops. Updated.
I found a V19 n0 release (Nougat 7.0) from the official CUBOT forum so i linked that one instead.
Click to expand...
Click to collapse
I think it's the same one, but I don't know why it's been marked as 6.0 release.
V19 is Android 7.0. The biggest change for me compared to v14 is option for Voice over LTE!
todoss said:
V19 is Android 7.0. The biggest change for me compared to v14 is option for Voice over LTE!
Click to expand...
Click to collapse
I know, i flashed it yesterday. However on needrom it is marked as 6.0 release.
Natalie07 said:
The steps above worked for me. Im currently runnig android 7 v14 stock rom rooted..
And twrp works great.
Click to expand...
Click to collapse
As android 7 update was released the old (6) twrp faild till twrp 3.1.1 was released for our device. Early birds installed patched boot.img. Now it is working i don´t like to go deeper into why a tut was wrong
Anyhow you maybe came from 6 and don´t like how hardware button are setup. For me i did not like to press fingerprint button to hide recents so i was searching for an solution.
https://play.google.com/store/apps/details?id=flar2.homebutton
You can use free version to do so.
Really nice extra is, it can enable multitask windows (split screen).
To remap menu button, premium is needed.
Then you can remap menu e.g. to turn on flashlight without have need to unlock phone.
Thanks for V19 = android 7 tip
Here are more useful tools for the phone also packed into a rom :
https://forum.xda-developers.com/android/general/cubot-cheetah-2-nougat-aroma-t3732579
Android Oreo 8.1 now available: http://forum.cubot.net/viewtopic.php?f=21&t=2357&sid=60b6f72a20ca3fbe3fad47d8791714ee
The CUBOT A5 is just a Cheetah 2 running on Oreo 8.1. Firmware tested on my device. Enjoy.
hey..yeah!
Any experience on rooting? How about power draining, since nougat firmware used more power as 6.0?
Let´s see at the moment i´m to lazy to update (backup, etc.)
My device is now an A5
but suprise suprise..twrp not working even if bootloader is unlocked
Also i note it is slower in charge ~20% - 1h
Wifi seems to connect less well. Mobile data quick tile always bright even if permant mobile data is set of in developer mode.
Faster in start up, seems like fingerprint sensor improved.
Not sure if someone can install 8.1 from internal storage if stock firmware is present. I used format option since i had to fix some bugs. No emei loss by doing, so guessing it was a bug of flash tool which is now updated as well. However better backup emei xD
fake ?
Alberto96 said:
Android Oreo 8.1 now available: http://forum.cubot.net/viewtopic.php?f=21&t=2357&sid=60b6f72a20ca3fbe3fad47d8791714ee
The CUBOT A5 is just a Cheetah 2 running on Oreo 8.1. Firmware tested on my device. Enjoy.
Click to expand...
Click to collapse
this is not cheetah 2
jeff a.marquez said:
this is not cheetah 2
Click to expand...
Click to collapse
Same device, different name. Just a marketing thing probably
ill try flash in cubot cheetah 2
how to fix imei ill try thru sn writter but always failed
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
smooth rom but the imei of my phone missing
jeff a.marquez said:
how to fix imei ill try thru sn writter but allways failed
---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------
smooth rom but the imei of my phone missing
Click to expand...
Click to collapse
Well, you used "Format all and download" option in sp flash tool instead of "Fimware upgrade". You also didn't perform nvram partition backup, which is recommended.
Next time you'll probably read the OP more carefuly.
nlooooo said:
Well, you used "Format all and download" option in sp flash tool instead of "Fimware upgrade". You also didn't perform nvram partition backup, which is recommended.
Next time you'll probably read the OP more carefuly.
Click to expand...
Click to collapse
yeah but the charging time 1 of my problem just why i downgrade into 6.0 now im using 6.0 rom miuipro 10
---------- Post added at 07:10 AM ---------- Previous post was at 06:50 AM ----------
jeff a.marquez said:
yeah but the charging time 1 of my problem just why i downgrade into 6.0 now im using 6.0 rom miuipro 10
Click to expand...
Click to collapse
bro do you have twrp recovery source of oreo for root
It will work really, if I Flash my cheetah 2 with the A5 firmware? I flashed yesterday the v19 official firmware and the camera don't work properly. There is no manual focus on the main camera.
tozsomak said:
It will work really, if I Flash my cheetah 2 with the A5 firmware? I flashed yesterday the v19 official firmware and the camera don't work properly. There is no manual focus on the main camera.
Click to expand...
Click to collapse
I flashed it about a month ago. Just choose 'Upgrade Firmware' in SP Flash Tool.
android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
a offical oreo 8.1 firmware with google play for power m3:http://www.mediafire.com/file/qev79...2B32.Neutral.8.1.V01.01.20190118user.zip/file
The firmware is working. One problem: after installation in TWRP package OpenGapps the system crashes. I couldn't find the replacement option (arm64, 8.1). Energy saving is good. Root access - Magisk.
P.S.: Build OpenGapps UNOFFICIAL is suitable for installation and works after components are updated (for example, with Yalp Store or Aurora App Store, F-Droid & etc.)
P.P.S.: If someone decides to install the firmware - must first make a backup of the NVRAM!!! Because the firmware will have to be installed with formatting and the nvram section will die. After flashing the firmware, it must be restored from the saved backup.
For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179
Hai_Duong said:
For me I got Problems with the display.. Its kinda over saturated.
If someone can explain the rights step to flash this rom would be nice. I cant install twrp over the Flash tool i used this for flashing twrp:
https://forum.xda-developers.com/android/general/cube-power-m3-tablet-twrp-img-t3772179
Click to expand...
Click to collapse
Take my version TWRP specifically for Oreo (the same in Russian how to install and patched Magisk boot.img to obtain root-rights): hire.
The saturation of the screen is comfortable for me, Occasionally settings of installed programs fly off.
TWRP Oreo
patched boot
config.gz in /proc fs
wangyiling said:
android oreo 8.1 firmware leak for alldocube power m3 ,guys who own the pad have a try!and give a bug reply post.
alldocube power me oreo 8.1 firmware(0621)
Click to expand...
Click to collapse
running linux kernel was configured to have /proc/config.gz. The configuration for this is found in
General setup
[*] Kernel .config support
[*] Enable access to .config through /proc/config.gz
with oreo 8.1...
treble checker reports device to be supported by Project - only with A-partition.
did anyone tried out to switch to GSI image?
cmarxmeier said:
tried out to switch to GSI image
Click to expand...
Click to collapse
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
wangyiling said:
also some one can try this new power m3 8.1 firmware
Click to expand...
Click to collapse
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH
ViAlexSt said:
Theoretically, should be suitable all the firmware from this theme and some of this. But we need TWRP support Treble, if I understand correctly (I tried the project on another device, everything was already done).
Treble works. As an experiment, I launched Omni 8.1. Started, but gives error 'com.android.phone has stopped'. The system image installed through fastboot (my TWRP isn't able to install to the system partition). The bootloader must be unlocked.
AOSiP Pizza Alpha [EXPERIMENTAL] - wi-fi, sound work, phone don't.
[9.0.0] ArrowOS (Android 9) - very quite good, but again the phone module. Need a system.img way to rebuild, or looking for a fix. In the firmware theme this is the main question. And in general, I liked the firmware, fast response and fast touch interface.
Click to expand...
Click to collapse
ViAlexSt said:
I already have this version installed. The work of the Treble Project checked on it. Firmware international, Google applications available, fixed some bugs. The installation also requires restoring the nvram partition.
Here's an updated TWRP 3.2.1-0 x64 for Oreo with support for the Treble Project (my port from Infinix X571): AFH
Click to expand...
Click to collapse
nice
wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.
cmarxmeier said:
Firmware brings up DualWifi again - 5GHz stopped working in former version.
EngineerMode.apk seems to be removed from priv-app's in this release - restoring manually from old image did not help - app crashes.
No easy way to set IMEI on device without MTK EngineeringMode.
Click to expand...
Click to collapse
for imei restore ,i think mtk sn write tool will do some help
wangyiling said:
for imei restore ,i think mtk sn write tool will do some help
Click to expand...
Click to collapse
mtk sn write tool did the job. - shows up with correct IMEI and VoLTE 4G.
patched boot.img with magisk
- works like a charm so far.
Looking forward to check USB-C Port with Icy Box to get Ethernet/HDMI device listed on USB-Bus.
wangyiling said:
https://megaup.net/6u3i/Y5352.CUBE.T1001.MID.2+32.Neutral.8.1.V01.01.20181210user.zip
also some one can try this new power m3 8.1 firmware .
it's not beta .
Click to expand...
Click to collapse
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...
fraddy91 said:
Someone does have TWRP recovery for this one? Trying to port old one, but getting buggy rotated recovery...
Click to expand...
Click to collapse
Compile yourself by adding the lines:
# TWRP
......
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
Or Phils recovery.
First of all i want to thank every developer who made it possible for us to experience such cool things on which they spend their sleepless nights , endless hours for which "thank you " is just not enough. I want to aware beginners that what they enjoy in their hand, the smooth satisfying hassle-free seamless experience on phones is result of rigorous hours of hardworking consisting several phases of development (coding , porting , patching etc ).
Always Respect Developers
I am Tech enthusiast. Following this community since last year. Reading and learning about software development.
Here in this post i have contributed nothing. i am just sharing their work with their credits and also making it easier for you guys to follow the instructions and and procedure for entering into the new horizons of customization.
Realme is working really hard to push its development community to compete with MI. If this post will help it to grow it stronger even in 0.1% i will be happy
Note: upgrade device to latest firmware.
Step:1 Unlocking Bootloader
Here you can find full procedure of unlocking written by @Sun Lee
https://c.realme.com/in/post-details/1101401810746212352
Step:2 Installing Twrp
https://sourceforge.net/projects/realme1/files/twrp-9.0/
use adb commands for booting into recovery(this version requires adb commands otherwise manually entering through hard keys is always recommeded.)
Flashing instruction for are:
https://www.xda-developers.com/how-to-install-twrp/
step:3 Installing custom rom
Read and follow procedure carefully as given in OP
https://forum.xda-developers.com/realme-1/development/rom-lineageos-17-1-t4107019 OP By @Invincible-Venom and his whole team
optional : Rooting
you can download magisk manager . it is most widely used and trusted su manager with tons of modding modules.
but always look up to exceptions and NOTE from rom maintainers. In case of latest lineage 17.1 you can only use magisk 20.1 , magisk 20.3
this guide is for very novice kids who are new in this world . i would recommend you to know basic things before doing any stuff written above.
Step:2 Installing Twrp
https://sourceforge.net/projects/realme1/files/twrp-9.0/
i will recommend you download this version of twrp as you will need this for only stable custom rom made by @Invincible-Venom (again thank-you sir)
Click to expand...
Click to collapse
Once again read LineageOS 17.1 post for TWRP instructions.
note: dont reboot to twrp from cmd , it can soft brick your device . always perform it manually through keys.
Click to expand...
Click to collapse
This is ColorOS 5/5.2 issue. In ColorOS 6 the only way to enter recovery (after unlocking bootloader) is using command. So modify this statement.
In case of latest lineage 17.2 you can only use magisk 20.1
Click to expand...
Click to collapse
They can also use Magisk v20.3.
Naveen56 said:
Once again read LineageOS 17.1 post for TWRP instructions.
This is ColorOS 5/5.2 issue. In ColorOS 6 the only way to enter recovery (after unlocking bootloader) is using command. So modify this statement.
They can also use Magisk v20.3.
Click to expand...
Click to collapse
ok brother
Ishan303 said:
ok brother
Click to expand...
Click to collapse
Once check you are using Lineage 17.3 and other numbers for 17.1.
correct Lineage version numbers.
Hello,
I have a question, is it possible to root without flashing any custom rom? I'd like to stay with the current rom but have SU privileges. Is it possible with this phone right now?
luccifyer said:
Hello,
I have a question, is it possible to root without flashing any custom rom? I'd like to stay with the current rom but have SU privileges. Is it possible with this phone right now?
Click to expand...
Click to collapse
Yes you can!
Ishan303 said:
Step:2 Installing Twrp
https://sourceforge.net/projects/realme1/files/twrp-9.0/
use adb commands for booting into recovery(this version requires adb commands otherwise manually entering through hard keys is always recommeded.)
Click to expand...
Click to collapse
Correct this, booting to recovery via hard keys isn't possible in the latest Frimware ( ColourOS 6 ). update it correctly. Hard keys are only possible in ColourOS 5.0/2
Realme stopped support for Realme 1 on unlocking bootloader, In depth test app fails to submit application,
If anyone found a solution please share!
There is a problem while rooting and installing TWRP recovery on the MI 10 Pro 5G (German-Version ROM Global). If you try to install TWRP you will not be able to get into the recovery. If you try (Vol up + Power) you`ll only able to start the MIU-Recovery.
Also I got some problems to get google pay to work, but this way works for me.
Before we start the disclaimer " I'm not responsible for any damage / bricking / ... If this way fails on your phone"
How to install MIU 12 EU CMI to get Dual-SIM, MIU Phone-App,...
You need:
- an unlocked boot loader
- a working ADB on Win / Mac / Linux
- TWRP I took this one HERE
- a custom ROM I took the weekly EU-ROM because I want Dual-Sim, the regular MI-Caller and the other cool stuff. You could find it HERE take the one for MI 10 Pro!! Alternativ MIU 12 ROM (tested)
MIU 12 EU stable Vers: 12-10 get it here
1 Step:
connect your phone to your computer and copy your "new" ROM to the device
2. Step:
Power off phone > hold Vol down + Power and reboot in Fastboot-Mode
3. Step start TWRP in a different way
fastboot boot "link to your TWRP Recovery"
EXAMPLE: fastboot boot C:\Users\neunzehn\Desktop\ADB\TWRP\recovery.img
now you boot TWRP from you computer without installing, so if anything goes wrong you are able to plug of and reboot in Fastboot.
4. Step flash ROM
DON`T UNPLUG YOUR PHONE!
choose your preferred language in TWRP and flash the ROM you put on the Phone before
5. Step
Reboot your Phone.. it will stuck /reboot (don't get nervous let it happen for e few times)
Press " Volume up + Power" you get the MIU Recovery choose " Wipe Data"
6.Step
Wait that your phone boot is complete , in my case it tooks 10 Min... after that you got your Custom-ROM
How to root without losing Bank-Apps, Safety-Net
You need:
- an unlocked boot loader
- a working ADB on Win / Mac / Linux
1. Step:
connect your phone to your computer and copy your Magisk v20.2 to your device IMPORTED only use Magisk 20.2 you can get it HERE
2. Step:
Power off phone > hold Vol down + Power and reboot in Fastboot-Mode
3. Step start TWRP in a diffrent way
fastboot boot "link to your TWRP Recovery"
EXAMPLE: fastboot boot C:\Users\neunzehn\Desktop\ADB\TWRP\recovery.img
4. Step flash root
DON`T UNPLUG YOUR PHONE!
choose your preferred language in TWRP and flash the Magisk.zip you put on the Phone before
5 Step reboot
Reboot your Phone. After Reboot start the Magisk-App and disable "automatic-update / search for update" and make the safety-net test.
Done...
PS: In 8 years of flashing I never have seen this behavior, don't ask me why this is actually the best way to get a stable CR on your phone. I tried this way on 3 MI 10 Pro 5G bought in Germany (Telekom, Media Markt, Ebay) with the awful Global ROM
CREDITS go to: XDA and MIU for ROM and TWRP
Article UPDATES:
06/25/20: Link to TWRP was broken > corrected
06/27/20 added workaround to root
07/02 added stable 12 MIU EU-ROM (all languages are supported)
Interesting, must then be specific to the German edition of the phone as I didn't get this with my (Global) Mi 10 Pro !
Following your description it seems as if flashing TWRP does not work, what are the commands you used ? It should be "fastboot flash recovery <twrp_file.img>"....
As an idea: what would happen if you boot TWRP as in your step 4, then copy the TWRP file to the phone and install TWRP from TWRP ?
Thanks, nice to know, i even got my phone from mediamarkt in germany.
Could you please tell me, is the phone encrypted after you've flashed Xiaomi.eu?
AND, is google pay working?
thx
s3axel said:
Interesting, must then be specific to the German edition of the phone as I didn't get this with my (Global) Mi 10 Pro !
As an idea: what would happen if you boot TWRP as in your step 4, then copy the TWRP file to the phone and install TWRP from TWRP ?
Click to expand...
Click to collapse
I also tired this, but it produced a boot loop an " Chinese-Letters"
Flash-User said:
Thanks, nice to know, i even got my phone from mediamarkt in germany.
Could you please tell me, is the phone encrypted after you've flashed Xiaomi.eu?
AND, is google pay working?
thx
Click to expand...
Click to collapse
You have to encrypt it at the first boot via your MI-Account , Yes Google Pay works for me and also Postbank, Moneese, and im able to "disable" the Exposure Notification Framework ( the discussion on SWR / WDR / NDR in Germany about GPRD / Security of the Covid-STuff)
neunzehn77 said:
If you try to install TWRP you will not be able to get into the recovery. If you try (Vol up + Power) you`ll only able to start the MIU-Recovery.
Click to expand...
Click to collapse
it's been like this for years now, just google "twrp replaced by stock recovery xiaomi reboot" you'll find lots of reddit posts of this happening.
i only do this once when buying a new device so sorry I don't remember exactly which one but there are two ways to reboot after installing the recovery and one of them prevents the device from overwrite the recovery, if I remember correctly
1- run "fastboot reboot" and hold volume up
2- hold power and vol up until the device reboots and boots to recovery
on another note, this section is for development not tutorials and general discussions
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Thank you neunhzehn77 !!! U saved my day
Now folks let me tell you something...
I´m not new to rooting phones anyway and i did try several ways to get the xiamomi.eu custom rom on my Mi 10 Pro.
I failed every single time.
Then asking neunzehn77 for specific help on my flashing situation in a private chat.
This guy explained to me some of the "super-partition-features-issues" and cleared his guide for me.
What can i say... i truly folled his guide step-by-step and i´m now on xiaomi.eu beta MIUI 12 rom in no time.
And again thank neunzehn77 for saving my MIUI-Rom-experience for good.:victory:
underlines said:
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Click to expand...
Click to collapse
If you follow your guide, you will lose essential-stuff like some Banking-Apps, Google-Pay,... and some more. I tried your way on a "German MI 10 Pro 5G" and get random boot-loops... maybe there is an unknown difference between CN ,EU, Global Versions. I don't know... for me your guide isn't working... but maybe that's a way for CN/US bought MI`s
In my case its better to leave the Super-Partition untouched, to get unwanted effects.
Thanx for sharing Mate...
neunzehn77 said:
If you follow your guide, you will lose essential-stuff like some Banking-Apps, Google-Pay,... and some more. I tried your way on a "German MI 10 Pro 5G" and get random boot-loops... maybe there is an unknown difference between CN ,EU, Global Versions. I don't know... for me your guide isn't working... but maybe that's a way for CN/US bought MI`s
In my case its better to leave the Super-Partition untouched, to get unwanted effects.
Thanx for sharing Mate...
Click to expand...
Click to collapse
Thanks for this valuable feedback. I have to put up a warning for EU users then.
Can you remember what exactly it was that lead to errors or problems? And which TWRP did you use? xiaomi.eu's modified one or LR.Team's?
Also, how exactly did you flash magisk?
On my CN CMI I also had all these problems, when touching the super partition. That's common as soon as you modify the super partition: https://xiaomi.eu/community/threads/twrp-and-system-problem.56103/
Do you remember what exactly you did differently from my guide in order for you to make it work? I could incorporate that into the AIO Guide on XDA.
underlines said:
Won't happen if you follow my guide. My friend in Switzerland tried it with the Global Mi10Pro without issues
https://youtu.be/uM1dBptUBd8
Click to expand...
Click to collapse
Hello, does your friend in Switzerland have 5G working ? I happen to be in Switzerland too (carrier : Sunrise), everything works smoothly but 5G... Thanks for your answer.
AFAIK all custom ROMs based on CN, so no 5g..
@neunzehn77 I have a question for you. I just unlocked the bootloader of my Mi 10 (yes not the pro, but the principle is the same). I bought it through Orange in Belgium and it is the Global version, I suppose it must be similar to yours. I see that you didn't format or wipe when flashing a new ROM and all other guides I find do format /data. Isn't this necessary when going from the official ROM to a Xiaomi.EU ROM? The problem with your workaround would then be that the ROM you put in your storage would be gone. I am used to flashing Oneplus devices, but this is something else... It really confuses me.
sithlord512589 said:
Now folks let me tell you something...
I´m not new to rooting phones anyway and i did try several ways to get the xiamomi.eu custom rom on my Mi 10 Pro.
I failed every single time.
Then asking neunzehn77 for specific help on my flashing situation in a private chat.
This guy explained to me some of the "super-partition-features-issues" and cleared his guide for me.
What can i say... i truly folled his guide step-by-step and i´m now on xiaomi.eu beta MIUI 12 rom in no time.
And again thank neunzehn77 for saving my MIUI-Rom-experience for good.:victory:
Click to expand...
Click to collapse
Hi, I'm on the verge of trying to flash xiaomi.eu ROM on my Mi 10 (Global - Belgium) and rooting it afterwards. The problem is that I'm a bit afraid of getting an error or a bootloop and not knowing how to recover from it. I'm not familiar with Xiaomi because I always had a Oneplus device before. How did you fix it? Did you format /data like other guides suggest? Or did you just "dirty flash" xiaomi.eu on top of the stock ROM like in this workaround guide?
Marcoziezo said:
Hi, I'm on the verge of trying to flash xiaomi.eu ROM on my Mi 10 (Global - Belgium) and rooting it afterwards. The problem is that I'm a bit afraid of getting an error or a bootloop and not knowing how to recover from it. I'm not familiar with Xiaomi because I always had a Oneplus device before. How did you fix it? Did you format /data like other guides suggest? Or did you just "dirty flash" xiaomi.eu on top of the stock ROM like in this workaround guide?
Click to expand...
Click to collapse
No no.. when you switch to custom you have to start all over. So wipe and format(make cloud backup ?)
marcel112 said:
No no.. when you switch to custom you have to start all over. So wipe and format(make cloud backup ?)
Click to expand...
Click to collapse
I used the latest LR team TWRP (3.4.2B wzsx150 from june 23) and it worked out fine with my global (European) version of the Mi 10. So this workaround is not needed anymore I guess.
1) I fastboot flashed this TWRP version
2) Booted to TWRP
3) Formatted /data
4) Rebooted to TWRP to be able to acces the internal storage
5) Transferred and flashed the Xiaomi.EU stable build of August 10th
6) Rebooted to system.
Everything is working fine, I am rooted using Magisk 20.4 with some modules and even swift installer is working great.
Cheers
Marcoziezo said:
I used the latest LR team TWRP (3.4.2B wzsx150 from june 23) and it worked out fine with my global (European) version of the Mi 10. So this workaround is not needed anymore I guess.
1) I fastboot flashed this TWRP version
2) Booted to TWRP
3) Formatted /data
4) Rebooted to TWRP to be able to acces the internal storage
5) Transferred and flashed the Xiaomi.EU stable build of August 10th
6) Rebooted to system.
Everything is working fine, I am rooted using Magisk 20.4 with some modules and even swift installer is working great.
Cheers
Click to expand...
Click to collapse
just remember, on android 11, you cant use normal magisk 20.4.
You need to use canary builds.
Also Android 11, twrp cant decrypt using pincode... you need to set up , gesture
Is imei repair and qcn file output for mi 10 pro?
badaas said:
AFAIK all custom ROMs based on CN, so no 5g..
Click to expand...
Click to collapse
Just saw this.
Maybe this is the reason that the EU rom does not have 5G working.
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