Related
MIUI 8 GLOBAL BETA 6.8.11 reported for DOOGEE DG700
Requirements:
Stock 4.4 KK firmware installed on the phone
Custom recovery
A working brain ... and some patience!
Credits:
All credits go to team ARGN for crossporting MTK6592 to MTK6582 and updating their ported rom here
Me for porting from Gionee M2 to DG700
Feautures:
Cross ported from the latest MIUI8 xiaomi.eu release for Redmi Note. (credits go to team ARGN)
DG700 rom uses as base TEAM ARGN crossports from MTK6592 to MTK6582.
Working: dual sim 3g (using dual sim control apk), wifi, bluetooth, gps, camara, sdcard, and everything else.
No chiness apps
All gapps preinstalled as system apps.
Enhanced camera pics quality (must be enabled in camera settings).
Repartitioned internal storage to 6G, custom carliv touch recovery (using stock kk firmware in the downloads at the end of the post).
Xposed and xposed modules working.
Many more ...
Known bugs:
Theme apk SOMETIMES FC's, but themes are working.
NVRAMWARNING wifi bug, easilly fixable (search xda or google for fix), wifi works just ok even with the NVRAMWARINING bug.
Battery capacity will be shown only at 3100mah, even so battery life is far more superior than the actual R25 lollipop firmware for DG700. (I get about 3 days with wifi / data on, moderate usage of the phone on the current MIUI8 based on kk rom)
Custom recovery CTR touch NOT WORKING. USE HARDWARE KEYS!
Installing
Download DG700_MIUI8_beta_global_6.8.11.zip (link at the end of the post), copy it on the sd card.
Download Stock R14 firmware linked at the end of the post (the attached build INCLUDES CTR custom recovery and repartitioned internal storage to 6G), unzip the archive and flash it with sp flash tools.
After flashing R14 go directly to recovery, DO NOT BOOT into android.
Once in recovery take the following steps:
1. Wipe and Format Options > Clean to Install a new rom ... wait for the recovery to wipe system, data, go back to the main menu
2. Install zip > Choose zip from storage/sdcard1 > browse for DG700_MIUI8_beta_global_6.8.11.zip and select it, install and wait for the installer to finish, go back to the main menu
3. Reboot system now, when asked to install su / root phone, select NO! (if you want to root the phone later you can install Chainfire SU binaries from the recovery, and than SU app from the market)
Wait for the rom to load, for the first time it will take some time ... be patient.
If you are not on stock KK THIS WILL NOT WORK! After flashing R14 firmware you will loose the IMEI's. Follow the guide frome here to restore the IMEI's:IMEI REPAIR / RESTORE /BACKUP
Customizing ... well ... the sky is the limit ... I use Plak to remove titles from the hotseat / launcher icons (as you cans see in the attached screenshots) and MIUI Tweaks for status bar (notification bar) customization ...
IF ALL GOES WELL or IF YOU ENCOUNTER ANY PROBELMS PLEASE POST BACK!
If this post helped you hit the Thanks button!
ENJOY!
Downloads:
DG700 R14 Stock KK with CTR and repartitioned internal memory: DOWNLOAD LINK
DG700 MIUI8 xiaomi.eu global beta v6.8.11: DOWNLOAD LINK
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
You will need to use spflash tool and the stock rom attached in my first post in order to install (flash) kitkat. Search google or xda for a tutorial on how to use spflash tool.
Have in mind that this is an advanced process and many things might go wrong if you don't have experience with flashing the whole android on your phone.
I think that at some point even doogee had a tutorial at their site showing how to upgrade from kitkat to lollipop (see here: http://www.doogee.cc/download.php?ProId=41). It is the same process only you need to format the whole phone before flashing and instead of flashing lp use kk images and scatter attached by me. If you're not sure what you are doing do some research first ... there are lots of great tutorials on the net for spflashtools and mtk6582 phone. Also have in mind that for some newer DG700 models it is impossible to flash kitkat because of some drivers issues ... or so it was stated on the 4pda.ru dg700 thread.
Hey @tvladan,
thanks a lot for this thread!!!
My experience and feedback:
All went smooth until I booted with the Miui installed. Because the IMEI problem I was not able to log into android (use than play store) nor Miui and the system would not let me go any further until I could by magic.
IMEI
I could not log in (system need unique phone ID such IMEI) so I needed to get the apks and move/save on the sdcard to be installed.
I could not restore the IMEI with MTK which was suggesting a reset in order to fix it and I had no clue how to reset (not reboot).
Mobile uncle. I made a IMEI backup but even if the app was restoring without problem, it really did not do anything also after rebooting
Chameleon: the only app that did something although not permanent. I'm working to fix it
Nvram error: fixed with no issue as on this thread
MIUI: it is definitively a nice designed UI although the one I personally do not prefer. It is flexible if you want to do things as developers allow you which is on my opinion sometime to strick if we consider we all are looking for a rooted phone and than we are bond by the UI. For sure there are some features that are useful as were some I really appreciate from the stock ROM. One example: I agree that moving app to the SD card might slow down the system and use more battery but now that I've achieved a 6GB rom I'm using all of it for the app and just marginal cache/data will be saved on the SD....
@tvladan: If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
gipsea said:
Hey @tvladan,
thanks a lot for this thread!!!
If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
Click to expand...
Click to collapse
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
gipsea said:
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
Click to expand...
Click to collapse
LP moves a little slower than kk. Nothing to worry about. Regarding battery life there is a 12 -24 hours difference from lp to kk, kk lasting longer. If you install xposed framework on lp it will move a LOT slower. If you do not need xposed I recommend R25 LP. Also I have no knowledge of TWRP being able to backup nvarm. I might be wrong. All you can do is try different methods until you succeed. It is a devious and annoying process but when you get it right you'll be satisfied. Also after lots of hours fking around with this phone I really stand by the steps posted in my previous post as to how to repartition / root / repair imeis the fastest way!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
tvladan said:
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
Click to expand...
Click to collapse
About #4), flash TWRP. I have used the one posted by @NaturalBornCamper on his thread on step 11
If the TWRP for KK is different please post
I'm working on R25
Next fun step, R14
Thanks
It is the same twrp, works on kk and lp. You have the right one. For r25 it does not matter on what you are now, the spflashtool needs to format all the phone in order to install r25.
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
gipsea said:
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
Click to expand...
Click to collapse
All you can do is try to restore via twrp ... temp imei restore should be erased at reboot.
Thank you for this very Good rom. it's better than the stock KitKat
Do you have any resurrection remix for this device or any marshmallow based on KitKat kernel..please
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
tvladan said:
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
Click to expand...
Click to collapse
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
zidane01 said:
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
Click to expand...
Click to collapse
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
tvladan said:
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
Click to expand...
Click to collapse
Ok thank you...then I better stick with kitkat even do some applications stopped supporting it.
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
tvladan said:
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
Click to expand...
Click to collapse
Thank you for the tip but I will stick with my beloved dg700 until it dies or I die.. Lol
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)
- 20170817: https://mega.nz/#!AccyiLQZ!PEw2A4W1Knw8FEINv22G4l95DmBmxdJ4hiXgYinwOyg
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Firmware Upgrade" instead.
Previous Releases:
None yet.
Flash Tool
- Latest SP Flash Tool for Windows and Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.1.1 by @jemmini : https://mega.nz/#F!IN82DJRJ!TXUcWim6hc_oZW-_eXl4Dg
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
Thanks for this thread. A little feedback on tinkering with this phone so far:
1. Stock ROM has a few FreeMeOS related packages which I am skeptical of in the latest ROM. One of these are a com.zhuoyi.* package which have been known for malware in other devices. I removed all the FreeMe OS related stuff such as themes since I don't trust them and Launcher3 can't use them anyway.
2. TWRP is in Russian. Not too hard to change the language but a little annoying. If the TWRP folder on the internal storage is removed then the language resets.
3. If you have TWRP installed and you perform a factory reset, you get stuck in TWRP and you can't boot into system. The only way to get out of that situation is to flash the stock recovery.
4. If you install a third party Gapps Package or remove Gapps, it seems to make Google Play Services crash constantly.
Hello,
I got the phone from China and I live in India. Unfortunately for every sim I put in, I get emergency calls only error.
Hope there's a fix that you know so that I can use it here.
Thanks.
stephendt0 said:
Thanks for this thread. A little feedback on tinkering with this phone so far:
1. Stock ROM has a few FreeMeOS related packages which I am skeptical of in the latest ROM. One of these are a com.zhuoyi.* package which have been known for malware in other devices. I removed all the FreeMe OS related stuff such as themes since I don't trust them and Launcher3 can't use them anyway.
2. TWRP is in Russian. Not too hard to change the language but a little annoying. If the TWRP folder on the internal storage is removed then the language resets.
3. If you have TWRP installed and you perform a factory reset, you get stuck in TWRP and you can't boot into system. The only way to get out of that situation is to flash the stock recovery.
4. If you install a third party Gapps Package or remove Gapps, it seems to make Google Play Services crash constantly.
Click to expand...
Click to collapse
How did you overcome 4th problem if you got rid already.
Happening to me too.
T3h said:
How did you overcome 4th problem if you got rid already.
Happening to me too.
Click to expand...
Click to collapse
I actually don't have this issue anymore - I think a newer version of Gapps solved it. Also, there are some system apps you can't remove or it causes issues. I can't use Google assistant though, I need to get that solved.
Hi how i can check that lock or unlock the bootloader?
stephendt0 said:
Thanks for this thread. A little feedback on tinkering with this phone so far:
1. Stock ROM has a few FreeMeOS related packages which I am skeptical of in the latest ROM. One of these are a com.zhuoyi.* package which have been known for malware in other devices. I removed all the FreeMe OS related stuff such as themes since I don't trust them and Launcher3 can't use them anyway.
2. TWRP is in Russian. Not too hard to change the language but a little annoying. If the TWRP folder on the internal storage is removed then the language resets.
3. If you have TWRP installed and you perform a factory reset, you get stuck in TWRP and you can't boot into system. The only way to get out of that situation is to flash the stock recovery.
4. If you install a third party Gapps Package or remove Gapps, it seems to make Google Play Services crash constantly.
Click to expand...
Click to collapse
Hey,
I got a firmware upgrade and now it seems like I'm stuck in the problem that you've listed in #3.
How can I install the stock recovery, I don't seem to get it.
Edit : Never mind. I sorted it out. Just used the SP flash tool and flashed as usual as mentioned in OP.
I had removed the battery while flashing, so that it doesn't go to twrp.
Now new stock rom was downloaded from their official site and running new new firmware. The root and twrp is gone. I should be able to load the custom recovery and install supersu without any issues a by following procedure stated in OP.
T3h said:
Hey,
I got a firmware upgrade and now it seems like I'm stuck in the problem that you've listed in #3.
How can I install the stock recovery, I don't seem to get it.
Edit : Never mind. I sorted it out. Just used the SP flash tool and flashed as usual as mentioned in OP.
I had removed the battery while flashing, so that it doesn't go to twrp.
Now new stock rom was downloaded from their official site and running new new firmware. The root and twrp is gone. I should be able to load the custom recovery and install supersu without any issues a by following procedure stated in OP.
Click to expand...
Click to collapse
Yes that's right.
That said, I'd recommend grabbing the newest firmware and debloating it yourself. I don't have this phone anymore (digitiser failure).
Hello, guys! I bought this cell phone but it has given me green screen when I run the videos from the instagram stories or some other videos. Was this happening to you, too? I think of flashing the rom to try to solve the problem.
Hello,
recently i got a Mi Mix 2S and i immdiately started the unlock bootloader process. (I guess i was lucky with only 72 hours wait time)
i plan to try out several rom's. Also xiaomi.eu.
- i'm somewhat confused regarding wiping before flashing because of different instruction here on xda and on xiaomi.eu. On xiaomi.eu they write 'NEVER wipe system and persist' and on xda (at least for the aosp based rom's) always install stock miui AND wipe also system afterwards. Doesn't wiping system removes stock miui anyway?
- what does this 'vendor' on flashing stock miui (firmware + VENDOR) mean? Or can i just take the suitable rom package for miMix2S from miui.com and flash it in TWRP?
(my MiMix2s is original with global rom)
- after the bootloader is unlocked, is the information stored in the bootloader ? because i assume that aosp rom's doesn't have a xiaomi/Mi Account login section (unlike xiaomi.eu rom), so there after unlocking there is no need to have xiaomi account informations in the system?
Thanks in advance. Great community here!
First of all, you need to go in Wipe and Format Data before you flash anything cause data is encrypted on mix 2s (THIS WILL WIPE ALL THE INTERNAL STORAGE AS WELL, SO MUSIC, PICTURES AND VIDEO ARE DELETED, IF YOU DON'T HAVE AN EXTERNAL DRIVE TO STORE THIS DATA IT WILL BE DELETED, YOU CAN ALWAYS TRY LAZY FLASHER WHEN YOU INSTALL A NEW ROM TO DISABLE ENCRYPTION)
To flash VENDOR+FIRMWARE since I use MIUI chinese version I don't need to do it but normally you go to https://firmwarefile.com/ to download the last firmware and flash it (I forget if it's through recovery or fastboot but it's probably fastboot)
The information it's store, so going from custom rom to another it's pretty easy, however if you decide to go back to miui like I did you will need to reflash twrp through fastboot after flashing the rom and it will ask you your mi account password to start using the rom.
Hope it was helpful and readable cause my english it's far from perfect.
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