Related
I would firstly like to apologise in advance to all the members in here that are gurus. (I get paranoid when it comes to things that I describe bellow)
So I have just bought and received my mi4c, but as I am sure a great deal of people in this forum, I am experiencing certain things I do not like. What am I referring to you may ask? Primarily the massive amount of Chinese bloatware + unstable google services.
I have done a bit of my homework but I got stuck and came here. So here is the list of things that I am trying to do:
Install international rom (http://xiaomi.eu/community/threads/5-10-8.28692/) for gapps and removal of bloat
root
custom recovery (twrp)
So here is the challenge.. I do not know in what order to do them. I also found this thread here (http://forum.xda-developers.com/mi-4c/development/flash-twrp-using-flashify-app-pc-dev-rom-t3230355) which is basically root + recovery but it asks you to use a developer rom, wouldn't that be pointless if I am going to flash the international one?
Can someone please point me in the correct direction
Thanks in advance.
The rom from xiaomi.eu has to be flashed with TWRP - so you have two choices:
1. boot or flash TWRP via fastboot and after that flash the Rom from Xiaomi.eu
or if you do not want to mess with drivers and computer and fastboot:
2. use the built in updater app to change to the chinese/english stock developer! rom found here (dev version has root built in) - after that flash TWRP via an app like flashify (play store) - flash Xiaomi.eu within TWRP
i chose the 1. Variant and did only BOOT TWRP (fastboot boot .....) and did not permanently flash it at this time - so i could make a nandroid backup of the complete stock ROM - including the stock recovery first ! If you go this way too - do a backup of the ESF partition too because this one contains your IMEI and MAC Adress infos - can help to have this backup in the hand if something fails. If you have an OTG cable you can directly backup to an external USB Stick (must be FAT32 formatted !). I found this was the best solution for me before permanently flashing any other ROM.
Be aware that if you boot TWRP (temporarily or permanent flashed version) the touch sometimes simply does not work (in a few cases the power button did not work too). Solution: wait two or three minutes until the touch begins to work.... i used the TWRP (DEV Variant of the recovery) found here. Because the touch begins to work a little faster (sometimes it works instant).
since the last 2 weeks i stick with the sMIUI ROM (its a "slimmed" Xiaomi.eu ROM) you can cook your individual slimmed variant here. And you can read a little about it here.
Hope this helps you....
Andiii said:
The rom from xiaomi.eu has to be flashed with TWRP - so you have two choices:
1. boot or flash TWRP via fastboot and after that flash the Rom from Xiaomi.eu
or if you do not want to mess with drivers and computer and fastboot:
2. use the built in updater app to change to the chinese/english stock developer! rom found here (dev version has root built in) - after that flash TWRP via an app like flashify (play store) - flash Xiaomi.eu within TWRP
i chose the 1. Variant and did only BOOT TWRP (fastboot boot .....) and did not permanently flash it at this time - so i could make a nandroid backup of the complete stock ROM - including the stock recovery first ! If you go this way too - do a backup of the ESF partition too because this one contains your IMEI and MAC Adress infos - can help to have this backup in the hand if something fails. If you have an OTG cable you can directly backup to an external USB Stick (must be FAT32 formatted !). I found this was the best solution for me before permanently flashing any other ROM.
Be aware that if you boot TWRP (temporarily or permanent flashed version) the touch sometimes simply does not work (in a few cases the power button did not work too). Solution: wait two or three minutes until the touch begins to work.... i used the TWRP (DEV Variant of the recovery) found here. Because the touch begins to work a little faster (sometimes it works instant).
since the last 2 weeks i stick with the sMIUI ROM (its a "slimmed" Xiaomi.eu ROM) you can cook your individual slimmed variant here. And you can read a little about it here.
Hope this helps you....
Click to expand...
Click to collapse
Thank you for your response just 1 thing I do not understand, is there a difference between the developer rom and the international 1 I mentioned? and when you say I can flash it using the the updater app to flash the dev rom (it sounds easier to me + safer) do you know how to do this? (is it this : "You can also use Mi PC Suite to flash the ROM "?)
YES the Rom you posted is a "Custom Rom" and is not officially (Xiaomi). Thats why the website says:
Unofficial International MIUI / Xiaomi Phone Support
the original (official) Xiaomi Rom - Stable and Developer - for Mi4c is only available in Chinese and english language and is translated by the community Xiaomi.eu and optimized (removed chinese apps that wouldn't work for you anyway)
How to install stock android 6.0 on Mi 4c?
I am getting an Mi4c, straight from China, but don't want the heavy MIUI lagging the performance. I would like to intstall the stock android. How can I do it? Also :-
1. Will the edge tap and other features work outside of MIUI?
2. Will Google play services be installed alongwith the stock android ROM?
I'm newbie to the rooting scene......please be little comprehensive in explanation :angel:
Cheers!!
drevankar said:
I am getting an Mi4c, straight from China, but don't want the heavy MIUI lagging the performance. I would like to intstall the stock android. How can I do it? Also :-
1. Will the edge tap and other features work outside of MIUI?
2. Will Google play services be installed alongwith the stock android ROM?
I'm newbie to the rooting scene......please be little comprehensive in explanation :angel:
Cheers!!
Click to expand...
Click to collapse
As far as i know there's no announcement for android marshmallow update for the Mi4c yet. Neither for Miui nor for CyanogenMod (CM).
... I guess CM is what you meant with "stock android".
There's just an unofficial build for CM and I guess as long it's not official there won't be edge tap support for the device.
And you have to flash google apps by yourself.
The reseller ROM they ship with 77.00.44 is total trash. I chose to keep the Chinese dev ROM as there are several Mi apps I like to use in conjunction with Gapps. It is playing very nice with my battery now.
I bought a Nextbook Ares 8 whose stock rom is:
Model : NXA8QC116
Android Version : 5.1.1
Build # : V2.0.3
Kernel version : 3.10.62-x86_64_byt
As with all of my Android devices, I always have to have a custom recovery and device must be rooted.
And upon googling around, there's not much discussions/forums in installing custom recovery and root for this device.
I came across @vampirefo's Root Nextbook Ares 8, TWRP Recovery, Disable encryption
His thread is specifically for the Nextbook Ares 8 with stock Android 5.0. But, despite his warning, as I really needed TWRP and root, I went ahead and did his steps. I was successful in installing TWRP. But, unfortunately, his modified boot.img did not work with my Ares 8 5.1.1 stock rom. My tablet was stuck in the Nextbook logo.
Good thing is I made a TWRP backup of my stock 5.1 rom, including the original boot.img. Unfortunately too, the stock boot.img won't work with unlocked bootloader. Still bootloop.
So I edited the original 5.1 boot.img so it works on unlocked bootloader/custom recovery. I also modified it to remove the force encryption.
I flashed my modified boot.img and my Ares 8 booted normally. So i am happy with TWRP installed and a rooted Stock Ares 8 5.1.1 rom.
I am posting here the modified boot.img (with encryption removed) and a TWRP backup of the Rooted and Unencrypted Stock 5.1 rom so others may try (at their own risk).
DISCLAIMER:
As much as this worked for my device doesn't necessarily mean it will work for you. It's totally your choice if you did what I did and use the files I posted on this thread. I will not be held responsible if you f#@ked up your device. It's totally your responsibility.
Click to expand...
Click to collapse
Requirements:
1) Nextbook Ares 8 with 5.1.1 stock rom. NOTE: The modified boot.img attached is for the stock 5.1.1 It won't work properly with other roms. If you are using a custom rom at the moment, go back to your TWRP backup of stock 5.1.1. If you don't have a backup, you could try the TWRP 5.1.1 backup posted below.
2) TWRP installed (using @vampirefo's method)
IMPORTANT NOTE: Make a backup of all your important data. Unencrypting your device will wipe your data partition.
Steps:
1) Read disclaimer above. If you're ok with that, go to step 2. Else, leave this thread, and go elsewhere.
2) Head over to @vampirefo's thread to install TWRP. Root Nextbook Ares 8, TWRP Recovery, Disable encryption
3) Don't reboot your device as the unmodified stock boot.img wouldn't work with unlocked bootloader and @vampirefo's modified boot.img will not work with our stock 5.1.1 rom.
4) Boot to TWRP. Making a system backup is highly recommended (but not necessary).
5) Download, place on your sd card and install via TWRP the attached file Ares8_5.1_modified_boot.img.by.greatbal.zip (just like a normal zip file flashable via TWRP)
6) Reboot your device after successful installation.
7) Enjoy.
Suggestion:
Install SuperSU via TWRP for a better Android experience.
==================
TWRP Backup of Stock 5.1.1 Rom
This is the TWRP backup of the stock Ares 8 5.1.1 rom. It's pre-rooted and removed force encryption. It's working on my device. You could try it on your Ares 8 version.
DISCLAIMER:
As always, TRY AT YOUR OWN RISK. Make sure you have a backup plan if anything goes wrong. Don't blame me if you mess up your device and you forgot to make a backup of your working rom.
Click to expand...
Click to collapse
Steps:
1) Download Ares8_Stock_5.1_rooted_unencrypted.2016-11-08--TWRPbackup.zip
2) Extract the zip file.
3) Transfer the Ares8_Stock_5.1_rooted_unencrypted.2016-11-08--TWRPbackup folder you extracted to your sd card. Place it inside the TWRP/Backups/[Your Device] folder. Mine it's TWRP/BACKUPS/NXA8QC116/ folder.
4) Boot to TWRP.
5) In TWRP: Wipe>Advanced Wipe. Wipe dalvik-cache, cache, data, system.
6) In TWRP: Restore>Choose "Ares8_Stock_5.1_rooted_unencrypted.2016-11-08--TWRPbackup"
7) Reboot after successful restoration.
NOTE: the TWRP backup already has the modified boot.img, so you don't have to install the Ares8_5.1_modified_boot.img.by.greatbal.zip
You may also be interested with Remix OS 2.0 ported for the Ares 8. Please visit this link.
Click to expand...
Click to collapse
===================
Credit goes to @vampirefo for his work in bringing TWRP and root to Nextbook Ares 8.
Thx, 101% percent working on my Nextbook Ares 8 running on Android 5.1.1 out of the box. and now i'm very happy, after trying a lot of modified roms of vampirefo this stock 5.1 rom is still the best for our Ares 8 tab.
Sent from my ASUS_Z00ED using Tapatalk
Tuzuriro said:
Thx, 101% percent working on my Nextbook Ares 8 running on Android 5.1.1 out of the box. and now i'm very happy, after trying a lot of modified roms of vampirefo this stock 5.1 rom is still the best for our Ares 8 tab.
Sent from my ASUS_Z00ED using Tapatalk
Click to expand...
Click to collapse
Good to hear it worked for you. IMO, I also think this 5.1.1 is the best rom for Ares 8, compared to the other roms I've tried. Much better by a mile!
For one thing, the speaker volume is a lot louder than the other roms.
I have a question I just got a nextbook ares 11a with 5.1 and wanted to root it I read that ares 8 is the same to root it
stickman1981 said:
I have a question I just got a nextbook ares 11a with 5.1 and wanted to root it I read that ares 8 is the same to root it
Click to expand...
Click to collapse
There is a thread re Ares 11 rooting and installing TWRP. I've read that it is very similar to Ares 8 rooting. maybe you could visit their thread so they can help you better.
I still get the boot IMG signature verification failed upon reboot but everything else is working great. Like you I started with stock 5.1.1 and downgraded to vampires 5.0. how do I remove this annoying Sig. verification failed message?
OT. If anyone is interested, I ported Remix OS 2.0 to Nextbook Ares 8.
Im sorry but may I ask what OT is and would you mind helping me understand how to fix this. I really appreciate your twrp backup and all your time and effort in creating the working 5.1.1 backup. Thanks to vampirefos as well for all of your work as well.
After trying a lot of different rom. I was successful thanks to your guidance. Thanks a lot :good:
roy.garlington said:
I still get the boot IMG signature verification failed upon reboot but everything else is working great. Like you I started with stock 5.1.1 and downgraded to vampires 5.0. how do I remove this annoying Sig. verification failed message?
Click to expand...
Click to collapse
Yes, that's the downside of unlocking bootloader and installing a custom recovery. You are always reminded upon reboot. It's an issue on other devices as well when you unlock the bootloader unofficially. Examples are Motorola, HTC, Nexus, Oppo, etc...
It's a small price to pay for being able to install a custom recovery, rooting and being able to play around with custom roms, IMO.
roy.garlington said:
Im sorry but may I ask what OT is and would you mind helping me understand how to fix this. I really appreciate your twrp backup and all your time and effort in creating the working 5.1.1 backup. Thanks to vampirefos as well for all of your work as well.
Click to expand...
Click to collapse
OT = Off Topic. hehe. Off topic because I posted a link to a port of Remix OS 2.0 I made for Ares 8, whixh has nothing to do with this thread. Just in case somebody is interested to try and want something to play around with.
As of now, there is no way of getting rid of that nag screen reminding you that your bootloader has been unlocked or custom recovery has been installed. We have to live with that nag screen and press Volume Up everytime we reboot our devices. This is an issue with some other devices as well when bootloader is unlocked unofficially.
nguoiduatin196 said:
After trying a lot of different rom. I was successful thanks to your guidance. Thanks a lot :good:
Click to expand...
Click to collapse
good to here I was able to help you go back to Stock 5.1.1
BTW, since you are into changing and trying out roms, you may also want to try Remix OS 2.0 for Nextbook Ares 8 NXA8QC116 just something to play around with.
greatbal said:
good to here I was able to help you go back to Stock 5.1.1
BTW, since you are into changing and trying out roms, you may also want to try Remix OS 2.0 for Nextbook Ares 8 NXA8QC116 just something to play around with.
Click to expand...
Click to collapse
I do not want this change. But I will save your links ^^. I believe that after this I will need to it: P
Thanks man :highfive:
nguoiduatin196 said:
I do not want this change. But I will save your links ^^. I believe that after this I will need to it: P
Thanks man :highfive:
Click to expand...
Click to collapse
Ok.
Works perfectly. Thank you.
NeuralMonk said:
Works perfectly. Thank you.
Click to expand...
Click to collapse
good to here I was able to help you go back to Stock 5.1.1
BTW, if you're up to it, you may also want to try Remix OS 2.0 for Nextbook Ares 8 NXA8QC116 just something to play around with.
I spoke to early. No sound on the device either through the speaker or earphone jack. I have not tried attaching a bluetooth yet. If I plug the earphone in, I hear the "pop" of the electric on the jack, but no sound.
NeuralMonk said:
I spoke to early. No sound on the device either through the speaker or earphone jack. I have not tried attaching a bluetooth yet. If I plug the earphone in, I hear the "pop" of the electric on the jack, but no sound.
Click to expand...
Click to collapse
What's the model number of your Ares 8? What was the original Android version it had? If the model number and the original android version matches mine, you shouldn't have that problem. I didn't touch the rom in any way. it is the stock rom.
BTW, did you flash just the modified boot image? Or did you flashed the TWRP backup?
FYI, you cannot use the modified boot image posted above with other roms. You should use the stock 5.1.1 your device had originally. If you are using other custom roms, it won't work properly. you could try to flash the complete TWRP backup of the stock 5.1.1 posted on the original post.
Requirements:
1) Nextbook Ares 8 with 5.1.1 stock rom. NOTE: The modified boot.img attached is for the stock 5.1.1 It won't work properly with other roms. If you are using a custom rom at the moment, go back to your TWRP backup of stock 5.1.1. If you don't have a backup, you could try the TWRP 5.1.1 backup posted..
Click to expand...
Click to collapse
greatbal said:
What's the model number of your Ares 8? What was the original Android version it had? If the model number and the original android version matches mine, you shouldn't have that problem. I didn't touch the rom in any way. it is the stock rom.
Click to expand...
Click to collapse
Model: NXA8QC116
Android Version: 5.1.1
Should be the same. I am wondering if I removed something from the cache that is missing. I need to look at this in more detail. Maybe this weekend.
greatbal said:
BTW, did you flash just the modified boot image? Or did you flashed the TWRP backup?
Click to expand...
Click to collapse
TWRP is in the recovery slot.
Modified boot image is the last flash via TWRP zip file install.
Thanks for your help.
NeuralMonk said:
Model: NXA8QC116
Android Version: 5.1.1
Should be the same. I am wondering if I removed something from the cache that is missing. I need to look at this in more detail. Maybe this weekend.
TWRP is in the recovery slot.
Modified boot image is the last flash via TWRP zip file install.
Thanks for your help.
Click to expand...
Click to collapse
Ok. If you're coming from another custom rom like I708Q or Batville Rom, do a fresh install of the TWRP Backup. Wipe>Advanced Wipe. Wipe dalvik-cache, cache, data, system, and then restore the TWRP backup (System+Boot). You don't even have to install the modified boot image as it is already included in the TWRP backup.
Good luck. I hope you will be successful as this 5.1.1 rom is really the best for our Ares 8, based on experience. Specially the louder speaker volume. Other custom roms, very soft speaker volume.
The Remix OS 2.0 rom is also nice. Loud speaker volume and quite stable. That is, if you're into the "Windows-style UI" and willing to learn the ins-and-outs of Remix OS.
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
dark_prince said:
You have to flash Developer version of the rom which is not out yet. The otherwise-rom package will always lock your bootloader and wont let u access the recovery after (thats why bootloop). CM14 supports F2FS, MIUI8 is still upon the old ext4.
I have the same brick as yours for now and I'm downloading the old 6.12.8 developer version bootloader flashable file to get out of this mess. MIUI is nothing fascinating and they break something with every new update. I'll go back to MOKEE until Android 7 gets stable enough.
Click to expand...
Click to collapse
Thanks for your reply. That surprises me that there still isn't an miui 8 developer ROM out yet for this device. Probably shall never come in that case.
Good to hear that f2fs is supported by cm14 though. Will certainly be running this once I receive my new cases to replace the girly pink cover my mi4c currently houses
danbrown162 said:
Hi Guys,
Got my Mi4c unlocked and rooted running cm14 however, when I try and flash an MIUI 8 rom via TWRP the device goes into a bootloop.
I am new to Xiamoi devices (Nexus user) am I missing something? Is there a patch to flash after a rom to prevent bricking?
I'd really like to try MIUI again but don't want to go through the hassle of unbricking my device and reflashing/rooting it.
Many thanks!
p.s Does MIUI 8/CM14 support f2fs?
Click to expand...
Click to collapse
Just flash miui 8 from xiaomi.eu ones. It supports flashing via twrp.
I have the GM1910 version of the OnePlus 7 Pro
Ok so I had a stock OOS 10.3 on the 7 Pro I just bought used, went home and was super excited to get a custom rom installed. From my previous experience back in the day, I knew to USB Debug, OEM unlock, Advanced Reboot for convenience and followed the Havoc Custom ROm guide that said to:
1. Download the ROM, TWRP Installer, GApps, Magisk.
2. Wipe Data, Dalvik.
3. Flash the ROM, TWRP Installer (Use Unofficial Q compatible version, starting at 3.3.1.575).
4. Reboot to Recovery.
5. Flash the ROM, TWRP Installer again.
6. Reboot to Recovery.
7. Flash GApps (Optional), Magisk (Optiona).
8. Reboot and Enjoy.
Never Wipe System or Vendor partition.
After doing so, I first ran into an issue with Fastboot Mode being indefinitely stuck, but fixed that with a TWRP 3.3.1-75 version I downloaded, and was able to boot TWRP. After that, and following the guide above, I noticed it was stuck on the Havoc boot animation. I waited a good 20 minutes before realizing its likely never going to boot. I rebooted twice after that, waiting 10 more minutes each for a total of about an hour, thinking "Hey maybe it takes time". Nothing. I then tried flashing NikGapps for Android Q compatibility as latest Gapps on the OpenGapps website allows up to Android 9. I realized afterward that it was a n00b mistake so I downloaded and flashed the Beta Android 10 Beta Pico OpenGapps and Magisk Canary that also failed.
After that, I started searching around for finding a way to return to stock Android 9 to start over, thinking Android 9 had more stable support, so I downloaded and fastboot flashed the Android 9.5..11 GM21AA - Direct Download, but while showing the OnePlus stock boot animation, it freezes and then the device turns off entirely.
I'm currently waiting for the 9.5.13 Repack (taken from the Collection of Unbrick Tools thread) to finish downloading to see if I can use MSM tool to restore stock Android 9 and kind of start over. I would prefer to root / custom rom Android 9. I have no clue what I'm doing now, but honestly recall it being so easy back in the day before this A/B partition stuff and I would have considered myself to be not so much a n00b, but at least quite "experienced" but I guess thats completely irrelevant now hey!. Can someone please guide me on how I can fix this and get a custom rom booting? Thank you very much!
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
imatts said:
Update: I managed to restore to Android 10 using the Decrypted Oxygen OS 10.3 ZIP from the "Collections of brick tools" linked above, then rooted that stock OOS using the standard guide. I got Havoc Android 9 working prior but ran into tons of bugs so I just decided to stick to stock for now.
Click to expand...
Click to collapse
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
tech_head said:
Unless there is something specific you need with a custom ROM, I'd stay stock and root.
I have EdXposed installed and can tweak most things.
I really need ad blocking and some basic customization.
I don't need a full ROM to get what I want.
Click to expand...
Click to collapse
I would have agreed with you yesterday, but I've used the phone for a few days and cannot stand the insanely rounded corners so I tried finding a work around. So far reducing screen height and getting rid of Oxygen OS's software rounded corners is the way to go but stock OOS doesnt give you the option, I'm hoping a custom rom will. Currently in the midst of flashing RR Android 9
Which boot slot are you trying to flash the rom on and have you tried flashing other roms? I know I've tried flashing havoc a few times and no go. I'm using blissrom right now and it works great until I get the rom I'm building and configuring and have data and messaging working lol
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