Database Info

Nextbook Ares 8A with Android 6.0.1 root solutions

UPDATE: Please read the updated information at the bottom of this post, on my new recommendation to use the easier method, SuperSU systemless, to patch your original boot.img. This is in my quick start guide at the end of it, also. You still need to read my info on getting setup, also.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have started this thread as a place to post a working root solution for this tablet.
https://www.walmart.com/ip/Nextbook...-System/122137749?variantFieldId=actual_color
This is a great Android tablet for the price. It features an updated Intel Cherry Trail quad core 1.92 GHz processor, 1gb RAM, 16gb internal storage. and Android 6.0.1 Marshmallow.
UPDATE: There is a newer version of the tablet with a manufacturing sticker date of September, 2017. Despite retaining the 8A model number, it has a slower, ARM processor and Android Nougat 7.1.1. Although it is quite snappy, It shows much slower benchmarks in AnTuTu and has a much smaller battery, about half the size. Also the boxes are about 2/3 the thickness of the older, 6.0.1 tablets.
The chances of rooting it are very slim. My solution will not work for it. Fastboot mode appears to be disabled on this and one other Nougat tablet that I own. I am returning the one I tested.
UPDATE: I now have root, a custom TWRP recovery and modified boot images for the Android 6.0.1 version of this device.
I would like to thank @vampirefo for his TWRP and original boot images, for without his work, this would not be possible.
PLEASE DO NOT CONTACT HIM ABOUT THIS HE WILL NOT PROVIDE ANY SUPPORT FOR IT, THAT WILL BE PROVIDED BY ME AND OTHER GENEROUS FORUM MEMBERS.
I strongly recommend, though that you donate to him, in his signature, for all of his hard work on this, even if it is a small amount. I asked him twice about this and he never responded, so please donate to him.
His original boot.imgs are modified to remove encryption and make the kernel permissive.
I unpacked them and removed dm_verity to remove the failed verification message, on boot then repacked them.
FILES ARE UP ON ANDROID FILE HOST
https://www.androidfilehost.com/?w=files&flid=197521
Choose the version of the tablet that you own. Go to settings, about tablet and scroll to the bottom and look at the first few numbers of the build number. For example: V1.2.0.
Do not use this on the 1.0.8 version of the tablet or you will loose sound, wifi and maybe bluetooth. If you have this version of the tablet and can provide me a twrp, backed up, original boot.img, I can modify it to work with your tablet. You can temp boot twrp, to do this (see below). As of yet no one has provided one to me for the 1.0.8 tablet version.
UPDATE 10/24/2017: I now have a I now have a 1.0.8 modified boot.img up on android file host:
https://www.androidfilehost.com/?fid=962021903579487577
Here is a twrp backup of the 1.2.0 rom, with userdata deleted to start fresh. It will boot to the Android setup screen. If you have any major, unexplained problems, I recommend starting fresh with this. It works great on either tablet version: 1.1.1 and 1.2.0.
https://www.androidfilehost.com/?fid=673368273298970542
UPDATE 12/15/2017: I have uploaded a pre-rooted TWRP backup of my original V1.1.1 tablet
https://www.androidfilehost.com/?w=files&flid=235141
TO PREPARE YOUR DEVICE:
UPDATED 12/3/2017: I now have found a Version 2.1.5 of the tablet and have uploaded an unrooted, TWRP backed up version of it. It also contains the original recovery so do not check that box when flashing it in TWRP unless you intend to replace TWRP with the stock recovery
https://www.androidfilehost.com/?fid=673791459329065002
This will be long and thorough, because I see so many people who have trouble with this because they don't have their computer setup properly from the get go.
This will help you get ready to be successful in applying this.
First and foremost, unlocking your bootloader will delete all userdata on the tablet so you need a good backup of important files. If you backup to an external sd card, I strongly recommend also copying the files to an external source such as your computer. You can do that through mtp or remove the card and place it in an sd card adapter and insert it into an sd card reader. I did not do this, even though I knew better and my sd card was corrupted in the process, so I lost the original twrp backup of the virgin, untouched system partition.
Secondly, if you are on windows you need the proper drivers for adb and fastboot installed on your system. Proper drivers are the number one issue I see with windows users. For this Intel device get them here:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Here are the steps to install adb and Intel drivers, in the proper order:
The best way to to set up adb and fastboot in windows is to install it system wide. Here is an installer to do this that works well:
https://forum.xda-developers.com/showthread.php?t=2588979
Install process for 15 sec adb:
1. Run it (Require administrator privileges)
2. Press Y/Yes to install ADB and Fastboot
3. Press Y/Yes to install ADB system-wide
4. Press N/No to skip installing Drivers
5. 15 seconds passed - finished!
6. Now install the Intel drivers listed above and here, again:
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
Third, enable developer options by going to settings, about tablet, and tap on the build number seven times to enable it.
Then go to developer options and make sure usb debugging is enabled. watch on the tablet screen for a popup dialog the approve usb debugging. check the box to always allow for this computer and hit ok.
Now, with the proper drivers installed, adb and fastboot properly installed, You need to test that it is functioning properly. This is done with the tablet booted into Android. If you used the adb I recommended, go to my computer, C drive and open the newly created adb folder. Left click in an open area of the folder to select it. then shift right click to open a contextual menu, then select: open a command prompt here. Once the command window is open, type:
Code:
adb devices
and hit enter:
you should see the device serial number listed. I am now doing this from linux, so it may differ,slightly:
adb devices
List of devices attached
YFGV1216059870 device
Sometimes you get starting daemon on port... and you have to type it again to see the device listed. If you don't see this, then your drivers or adb/fastboot aren't properly installed.
If you see your device, then type:
Code:
adb reboot bootloader
and hit enter. your device should now reboot to bootloader mode. once in bootloader mode, type:
Code:
fastboot devices
enter and you device should once again be listed.
the next step, is to unlock your bootloader. Warning: ALL OF YOUR USERDATA WILL BE DELETED, HENCE THE BACKUP CREATED EARLIER. YOU HAVE BEEN WARNED!
It has come to my attention that this is not clear: after unlocking the bootloader, all userdata will be deleted, like doing a factory reset.
Go into developer options and select OEM unlocking. This does not unlock your bootloader, it only enables the ability to do it from a fastboot prompt.
Now jump to the Quick Start guide for updated instructions:
Older, system mode method hidden, please use the instructions in the Quick Start Guide
Now, while still booted into bootloader mode, type:
Code:
fastboot flashing unlock
and hit enter to unlock your bootloader. All data will be deleted and the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader. Now type
Code:
fastboot reboot
t, to reboot the tablet and you should reboot to the android setup screen, You can set it up again if you want, but you will be deleting userdata later when you flash the modified boot.img, so keep this in mind.
So you may want to wait to unlock until I release twrp and the boot.img, so you can continue using the tablet.
UPDATE: The files are now live.
To summarize, the above steps are to prepare you for the next exciting adventure to come and to realize the full potential that a rooted device offers..................
To be continued.
THE FILES ARE NOW ON ANDROID FILE HOST. DOWNLOAD HERE:
https://www.androidfilehost.com/?w=files&flid=197521
Boot or flash TWRP Recovery and flash boot.img
These instructions are for Windows, for Linux you must type sudo before fastboot commands
Instructions: first make sure you read the instructions above to be sure you have the proper drivers and adb and fastboot are installed and tested before proceeding. Unlock your bootloader per above instructions. WARNING! DANGER WILL ROBINSON! THIS PROCEDURE WILL DELETE ALL USERDATA ON YOUR TABLET SO BE SURE YOU HAVE A BACKUP OF ANY IMPORTANT DATA.
First, unzip the files to a directory. I usually do it in C:\adb, and leave the SR2-SuperSU-v2.82-SYSTEMMODE.zip, zipped.
Now, left click in that folder in an empty spot, or where ever you unzipped it and select it. Now right click and choose open a command prompt here from the contextual menu. once the command window is open type
Code:
adb devices
, hit enter, to confirm your device is listed. Now type
Code:
adb reboot bootloader
and it should reboot to bootloader mode.
I recommend booting into twrp temp first so you can backup your original boot, recovery and system.
now:
Code:
fastboot boot Ares8A_recovery_twrp.img
enter and it should reboot to twrp temp. Don't choose read only after it boots. Once in twrp choose backup and hit select storage and choose micro sdcard. now swipe to backup. You can later install twrp permanently if you want to. To flash permanently:
From bootloader mode:
Code:
fastboot flash recovery Ares8A_recovery_twrp.img
UPDATE: See the the end of my updated quick start guide for updated info on a simpler method to patch your original boot.img with either systemless SuperSU or Magisk. I no longer recommend flashing my patched boot.imgs, but instructions are still provided here for historical reference and for the few who still want SuperSu in the unofficial, system mode.
I have hidden the older method here, but is still here for those who still want system mode SuperSU:
Now
Code:
fastboot flash boot Ares8A_111_boot.img
enter, for the 1.1.1 version, or
Code:
fastboot flash boot Ares8A_120_boot.img
enter, for the 1.2.0 version, to flash the appropriate boot.img
For the newer 2.1.5 version of the table:
Code:
fastboot flash boot unsigned-new.img
hit the enter key, to flash.
Next, again in bootloader mode issue:
Code:
fastboot format userdata
enter, and wait for a successful message in the command window and on the tablet. it will take a little while.
Next
Code:
fastboot format cache
enter, wait. Now
Code:
fastboot reboot
hit enter, and the tablet should reboot to the android setup screen where you can set it up. It will take some extra time to reboot, so be patient. You may see the boot animation for awhile. This will be booted unencrypted now without root. I recommend doing a backup again in twrp before rooting.
There has been some misunderstanding about the above. Your data is encrypted and will not be accessible it twrp, hence, the backup before you do anything with this tablet.
You must wipe the userdata, so a new, clean data partition can be created that is unencrypted. A factory reset is not enough. You will have problems if you don't format userdata in the above step to created a decrypted data partition.
Flashing SuperSu for root
For the v1.1.1 and v1.2.0 tablets:
Make sure you have the SR1-SuperSU-v2.82-SYSTEMMODE.zip on your ext sd card.
For the newer 2.1.5 you need a systemless version of SuperSU:
SuperSU-v2.82-201705271822.zip Get it at:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip Copy it to your external SD card.
When flashed, this systemless version will also patch your boot image for sytemless mode.
Furthermore, to install SR1-SuperSU-v2.82-SYSTEMMODE.zip, or SuperSU-v2.82-201705271822.zip, either boot twrp temp again, from bootloader mode issue:
Code:
fastboot boot Ares8A_recovery_twrp.img
, or if you already have it installed permanently and you are booted normally, issue
Code:
adb reboot recovery
enter to boot to it.
Next hit the install button in twrp and choose SR1-SuperSU-v2.82-SYSTEMMODE.zip or SuperSU-v2.82-201705271822.zip and swipe to confirm flash. after it is complete, go back to the main menu and choose reboot system. I choose not to install the twrp app before reboot.
Once rebooted, open the supersu app, making sure the following are selected in settings enable superuser, default access prompt or grant, enable su during boot, trust system user and enable pro, then go back and enable full content in logging. Next download a root check app to confirm root.
congratulations you should now be rooted! Now download a desired app that requires root and test to confirm you have no problems with root.
If you want an app that makes it easy to reboot in the various modes, I recommend Simple Reboot by Francisco Franco. It works great with this device and android version.
I was using Easy Reboot [ROOT] by Simone Luconi with my older, ares 8 with 5.1.1 and it had worked well.
Apparently it is not compatible with this device or rom. when I rebooted to recovery with it, I was not able to mount my external sd card and the card was corrupted on reboot. That is why I don't have a virgin, unrooted, copy of my system image now.
Good luck!
Here is a quick start guide for the already initiated:
https://forum.xda-developers.com/showpost.php?p=72970060&postcount=82
Here is a link to my post for some apps I personally find useful:
https://forum.xda-developers.com/showpost.php?p=72995672&postcount=112
Please report successes and problems on this thread, not to @vampirefo.
Thanks

@vampirefo has a solution, but has not released it. I'm not sure if it needs more work or testing before release? He has been quiet in this regard. It is my hope that he will reply with more relevant information about this.
I and maybe others, would be willing to give a donation, if that would help.
Thanks

Bootloader unlocking
WARNING! UNLOCKING THE BOOTLOADER WILL DELETE ALL OF YOUR DATA!
DON'T DO THE UNLOCKING UNTIL WE CAN REMOVE ENCRYPTION AND HAVE TWRP FOR BACKUP. YOU HAVE BEEN WARNED!
You can enable the ability for the bootloader to be unlocked with a setting in the developer options. Like I stated, it enables the ability to unlock it, but does not unlock it. On must use the command in adb, through a computer. make sure usb debugging is enabled in the developer options. In a command prompt issue adb devices to make sure your device is showing up. There will be a prompt on your tablet to allow this. Confirm this.
Now with the tablet off, boot into fastboot by hold the volume key down button and the power button at the same time. Also, you can type: adb reboot bootloader then hit enter to get into bootloader or fastboot mode.
Once in fastboot mode, open a command prompt in windows and type fastboot devices to confirm your device is still showing up. If my memory serves me correctly there will also be a security confirmation on the tablet, to approve.
To unlock the bootloader type: fastboot flashing unlock. All data will be deleted and (I believe,) the tablet will be re-encrypted upon boot, without encryption option removed from the bootloader.
I HAVE NOT TESTED THIS, AS I DON'T WANT TO DELETE DATA, UNTIL WE HAVE TWRP TO BACKUP AND ROOT.
6/7/2017 UPDATE: I HAVE UPDATED THE UNLOCK COMMAND. I HAVE UNLOCKED MY BOOTLOADER. AS I THOUGHT, ALL USER DATA IS DELETED (FACTORY RESET). I USED THE FIRST:
"fastboot flashing unlock" Unlocks the device. Allows flashing any
partition except bootloader-related
partitions
"flashing unlock_critical" Enables flashing bootloader-relate partitions.
all fastboot commands are listed by just typing fastboot, while booted into bootloader mode. My tablet is still running great with my bootloader unlocked. One more tiny step toward gaining root, however, there is still a long way to go.
Please post any additional info if I have something wrong, or left out any important steps.
Thanks

Geenify: How to grant permissions required by some features on non-root device?
I am currently using Greenify on my non-rooted device and it is working very well.
By using adb, one can grant it additional permission so it performs almost as well on an unrooted device. Here is a link for this:
https://greenify.uservoice.com/know...o-grant-permissions-required-by-some-features
I copied and pasted each command, one at a time, in the command prompt then hit enter, to enable each one.
In Greenify settings, I also have aggressive doze enabled, Automated hibernation enabled, Wakeup Tracker enabled and Quick action Notification enabled.

How to boot into stock recovery mode
To boot to the stock recovery through adb:
adb reboot recovery
You will see "no command" on the tablet.
Hold the power button and volume up for about 4sec then release the volume up, where you should go to the stock recovery screen.
You can also get to it without a computer. With the tablet shut down, hold the volume down power button until it boots to bootloader or fastboot mode.
Use the volume up or down button to toggle through the options: normal boot, restart bootloader, recovery mode, reboot, power off and ftm mode. Choose recovery and use the volume up and power button as before.
In addition you can get to the efi bootmanager by holding the volume up, power button when the device has been shutdown first.

adb security confirmation
Unlike my Nextbook Ares 8 with 5.1.1, with this newer tablet which has 6.0.1, I have to reaffirm the security prompt on the device each time, despite checking the box: "Always allow from this computer".
Maybe this is because of the tightened security in Android Marshmallow? I'm not sure.
If there is a way around this each time, please let me know
Thanks
UPDATE: After I unlocked the bootloader and the tablet was factory reset, I no longer have to re-approve each time after checking the box: "Always allow from this computer"

Would love to see some break throughs with this device aswell. Cheers to any one working in it.

Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en

Giftlift said:
Is this relevant? It would seem they are the same device. twitter.com/srsroot/status/846663673645010944?lang=en
Click to expand...
Click to collapse
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.

martyfender said:
Don't try any of these one click root solutions. none work to my knowledge on android 6.01, (at least on this device) , and may install malware or pups on your host computer.
Click to expand...
Click to collapse
:good::good:

This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk

vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
I found this kernel building guide for arm and mediatek devices. would this be similar for Intel using the right repositories?
https://forum.xda-developers.com/android/software/guide-easy-kernel-building-tutorial-t3581057
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
This requires a lot of work.
1. Google kernel source.
2. Build bootable kernel
3. Unlock bootloader
4. Boot kernel with 5.1 ramdisk.
5. Use adb to pull boot.img and recovery.img
6. Download TWRP source modify source for intel
7. Make device tree
8. Unpack recovery.img use that kernel in your TWRP.
9. Make boot.img permissive, remove encryption repack and flash.
10. Flash TWRP.
11. Flash system mode SuperSU for root.
Sent from my LIFE X8 using Tapatalk
@vampirefo Thanks for taking the time to post this.
To familiarize myself with Linux, I created a persistent linux Mint 17.2 Mate 64 bit on a 32 gb usb thumb drive before I decide to commit my windows machine for a linux install.
I installed oracle jdk and android studio thinking this was the build environment needed to do this. the twrp compile forum makes no mention of what to do in this case. I must have been wrong? I don't think I need this to download and build android kernel sources and twrp source?
I'm now very doubtful about even tempting to do this. Yes, a lot of work just learning the basics of linux, let alone following the steps you give in your basic outline. I don't want to give up so easily, but the learning curve is steep.
So one just uses terminal commands to setup and download aosp and twrp git repositories and to make them? Also, is there any way to backup my device system, boot and recovery without root in linux or windows? I have used the adb pull command to backup the system directories to my windows computer, but don't know how to do it for other partitions, if possible.
Thanks
Click to expand...
Click to collapse
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

vampirefo said:
martyfender said:
All work is done in terminal, root is required to make backups.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse

martyfender said:
vampirefo said:
So I could uninstall android studio. Should I also revert back to openjdk? I see it mentioned in google docs on setting up a build environment.
UPDATE: I think I have now setup properly. Reverted to openjdk 8
I downloaded this: git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/x86/x86_64-linux-android-4.8
I found this: https://github.com/CM-CHT/android_device_intel_cherrytrail-common Would this be useful?
Thanks
Click to expand...
Click to collapse
No ideal, try it and see.
Sent from my LIFE X8 using Tapatalk
Click to expand...
Click to collapse

What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???

cjhudson101 said:
What would it take to interest @vampirefo in rooting this tablet and providing a nice clean ROM for the Ares 8A???
Click to expand...
Click to collapse
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk

vampirefo said:
For me to root and provide TWRP recovery, I would need the tablet.
Sent from my Life Max using Tapatalk
Click to expand...
Click to collapse
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?

cjhudson101 said:
My bad, I guess I misunderstood one of your posts where you said you successfully rooted the tablet, but were withholding the method...
What if I sent you one?
Click to expand...
Click to collapse
You didn't misread, I rooted my son's, he doesn't live near me, he is in college. He is using my laptop that I used, so all my source files are with him.
I need tablet to start over, I already know what to do but without tablet, I can't do it.
Sent from my Life Max using Tapatalk

Check your zip in the link, lets get vamp an 8a!
I just got one of these for $35, but now the closest walmart with it in stock is an hour away. Ill totaly send you one if I drive that way for any reason. Check your zip on brickseek ..... anyone?
slickdeals.net/f/10189248-nextbook-ares-8a-16gb-tablet-android-6-ymmv-35-bm?src=SiteSearchV2_SearchBarV2Algo1
it came with 6.0.1 on it

[GUIDE][TOOL][ROOT]Cubot Note Plus (MTK6737T) Root with Magisk V0.3

!!! YOUR WARRANTY IS NOW VOID !!!​
THIS TOOL IS FOR CUBOT NOTE PLUS ONLY.
neither I nor the XDA Forum is responsible for your phone brick or your cat triggers an atomic apocalypse. YOU has been responsible for your phone and you are doing everything at your own risk.​
This is a tool for rooting the CUBOT NOTE PLUS ONLY.
NOTE: THIS TOOL IS IN ALPHA STAGE
RoCuNo+_v0.3 is online.
Downloads see post 2
This tool can root your Cubot Note Plus and patch your boot.img for working with Magisk.
this tool can make this in seperate steps or All-In-One. For now the bootloader must stay UNLOCKED for root to work.
A guide to doing this by yourself with adb is also in this post.
NOTE: ALL YOUR DATA GET LOST. SAVE YOUR IMPORTANT DATA FIRST. (Videos, Pictures, Music and all you can save.)
What this tool can do:
Unlock/Relock your Bootloader
Root/Unroot your Cubot Note Plus (Unroot dont work for now)
[*]Make a Dump of your Boot Partition as boot.img
Install MagiskManager-v5.4.3 and Magisk-v14.0
Please download the attached zip and unzip it somewhere and rightclick on RoCuNo+_V*.bat and start as Administrator.
Read all carefully and choose your option. Follow the instructions on screen STEP BY STEP!!!
Better way is to choose the AIO because that makes all for you except a few steps.
Downloads see post 2
GUIDE
OEM UNLOCK + ROOT + MAGISKMANAGER APP
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. go in RoCuNo+ Directory on PC
08. press Shift + Right Mouse Click
09. Open Command Prompt here
10. type
Code:
adb reboot-bootloader
11. type [ODE]fastboot oem unlock[/CODE]NOTE: ALL YOUR DATA WILL BE DELETED
12. press VOL+ Button on phone to oem unlock
13. type
Code:
fastboot flash boot patched_boot.img
14. type
Code:
fastboot reboot
15. if you have unlocked your bootloader, make your setup
16. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
17. enable "USB DEBUGGING" (Go to "Menu --> Settings --> Developer Options")
18. type
Code:
adb install -r -d -g MagiskManager-v*.*.*.apk (set the Version numbers for *)
OEM LOCK
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. go in RoCuNo+ Directory on PC
08. press Shift + Right Mouse Click
09. Open Command Prompt here
10. type "adb reboot-bootloader"
11. type "fastboot oem lock"
12. press VOL+ Button on phone to oem lock
13. type "fastboot reboot"
UNROOT
01. make sure you have installed ADB drivers
02. enable "Developer Options" Menu ("Menu --> Settings --> About Phone" tap "Built Number" 7 times.)
03. enable "USB DEBUGGING" and "OEM UNLOCKING" (Go to "Menu --> Settings --> Developer Options")
04. enable "UNKNOWN SOURCES" in "Menu --> Settings --> Security"
05. connect USB cable to PHONE and then connect to PC
06. make sure all Drivers are installed.
07. Download SP Flashtool and Firmware for Cubot Note Plus
08. Start SP Flashtool and choose the MT6737T_Android_scatter.txt from the Cubot Note Plus Firmware Folder.
09. Turn off the Cubot Note Plus.
10. Click on Downloadbutton and connect the Cubot Note Plus to PC.
NOTE: ALL YOUR DATA WILL BE ERASED. MAKE A BACKUP IF YOU NEED.
11. After Flashing is complete, reboot Phone.
Old Guide
Save your data.
Connect your phone to PC and make sure all drivers are installed. (Boot up to normal system, recovery and fastboot to get sure.)
Open a CMD Prompt on your PC and switch to Directory where you have unzipped the RoCuNo+. (e.g. C:\Users\YourName\Desktop\RoCuNo+ or You can go to RoCuNo+ folder and Shift+Rightclick on empty space and click "open Command Prompt here".)
Type:
Code:
adb reboot-bootloader
Than:
Code:
fastboot oem unlock
NOTE: ALL YOUR DATA WILL BE DELETED
Press VOL+ on Phone if asked
wait for device for unlock
Type:
Code:
fastboot reboot
Setup your phone until you come to system.
Enable "Developer Options" Menu. Go to Menu --> Settings --> About Phone and tap Built Number 7 times until a message appears that you are now an Developer.
Enable USB DEBUGGING and OEM UNLOCKING in Menu --> Settings --> Developer Options.
Enable UNKNOWN SOURCES in Menu --> Settings --> Security
Copy MTK-Engineering-Mode.apk and MagiskManager-v5.4.0.apk on your and install this to apps.
open the MTK-Engineering-Mode app tap on MTK Settings and swipe to Log and Debugging.
Tap on User2Root and than the Root button.
NOTE: UNPLUG AND RECONNECT YOUR PHONE. DONT CLOSE THIS APP OR DO SOMETHING ON THE PHONE. YOU LOSE YOUR ROOT IF YOU DO SOMETHING.
Go back to CMD Prompt on PC and type:
Code:
adb root
adb shell dd if=/dev/block/mmcblk07p of=/sdcard/boot.img
Now open MagiskManager app and tap the Install button.
Choose to inject in boot.img
Point Magisk to the boot.img.
after Magisk has succssesfully patched the boot.img it will copy it to /sdcard/MagiskManager/patched_boot.img.
Copy your boot.img from sdcard AND the patched_boot.img from sdcard/MagiskManager to the RoCuNo+ folder on your PC.
Go to CMD Prompt and type:
Code:
adb reboot-bootloader
than type:
Code:
fastboot flash boot patched_boot.img
when flashing is ready, type:
Code:
fastboot reboot.
on phone go to MagiskManager app and check if Magisk and Root are on green state.
You succssesfully have rooted your Cube Note Plus.
Take care of the boot.img and the patche_boot.img in case we need them on some day.
DONT RELOCK YOUR PHONE BECAUSE YOU CANT WRITE ON /SYSTEM PARTITION WITH LOCKED BOOTLOADER. (for now.)
I hope that helps many people with his/her phone and maybe someone can make TWRP or a Custom Rom for our phone. Now the Door is Open.
if someone found better solution for some tasks here please let us know.
Changelog
RoCuNo+ v0.3
Delet the Unroot Section because it doesent work for now.
update Magisk Manager App to 5.4.3.
Update Guide.
Update patched_boot.img.
RoCuNo+ v0.2
complete rework.
all should now work.
now the original verified-boot.img from Cubot is implemented. so root and unroot works now.
ive patched the original verified-bood.img with magisk so no boot.img dump has to be made.
the tool now detects what state you are and boots the state needed for his job.
only magisk manager app has to be installed on device and the tool do this for you.
the tool detects if you are already oem unlocked or not. so if you already unlocked you dont
need to do that again. it also detects in witch state your phone and boots the right mode.
Credits to XDA-Developer Schwester_Gabi (https://forum.xda-developers.com/member.php?u=5264039) and the Flampinko.IT Team ([email protected])
you can use this tool on your own risk but its not allowed to share this tool in other forums or blogs or something. but you can write about this tool and link
than over to the XDA-Developer Forum under (https://forum.xda-developers.com/android/general/guide-cubot-note-plus-mtk6737t-root-t3695272)
it is also not allowed to copy the code or change anything in this programm. Only Schwester_Gabi or the Flampinko.IT Team is allowed to change the code.
If you have any Ideas to implement in this tool than post it over to XDA-Developers Forum (https://forum.xda-developers.com/android/general/guide-cubot-note-plus-mtk6737t-root-t3695272)
or send us an Email ([email protected]). If you like our work please make a donation to help us.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ZXVV3MZX2NVK6
please respect the developers work and stick to the rules.
Credits and special thanks to:
topjohnwu for the awesome Magisk
themonsterit for MTK-Engineering-Mode App
Schwester_Gabi for finding the way and coding the RoCuNo+ programm
all the people who write solutions for problems that i read to find the way too root.
XDA-Developer Team to giving us such a great Platform to share our stuff with the world.

Cubot Note Plus Stock Rom:
V8:
Mirror 1
V7:
Mirror 1 / Mirror 2
SP Flash Tool for Cubot Note Plus Stock Rom:
Mirror 1 / Mirror 2
Cubot Note Plus Stock Scatter File for flashing:
Mirror 1 / Mirror 2
RoCuNo+_v0.1(Alpha):
Mirror 1 / Mirror 2
RoCuNo+_v0.2:
Mirror 1 / Mirror 2
RoCuNo+_v0.3:
Mirror 1

Problems:
i got some problems with dumping boot.img. the partiton size is 16M and the dd dump is also 16M but if i try to flash it back fastboot says the file is to large for partition. thats why unroot doesent work for now. Magisk patch the boot.img and resize them to 8M. than flashing works fine and all works. if someone can point me in the right direction would be very nice. if you have some questions please write here or pm me.
if someone can make a scatter file for this phone or had the scatter file it would be nice to share so we can try to backup the phone with SP Flash Tool. thanks.
if you found some bugs please tell it here so i can fix it.

Nice

Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)

Matthius said:
Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)
Click to expand...
Click to collapse
not now. i hope that someone can make an TWRP or CWM for the Cubot and share it with us.

Matthius said:
Thanks for this great work, worked flawlessly. Just wondered, now we've got this root, is there any custom recovery we can install for it? (I realise many things will be available through Magisk's modules already, but still just wondered.)
Click to expand...
Click to collapse
did you use the RoCuNo+ Programm or have you done all by yourself ? what do you use ? step by step or the AIO routine ?

Schwester_Gabi said:
did you use the RoCuNo+ Programm or have you done all by yourself ? what do you use ? step by step or the AIO routine ?
Click to expand...
Click to collapse
I had already unlocked the bootloader myself prior to this, looking for a way to root it before I saw this article (I gather this is the first available root method for this device), and also manually installed MagiskManager and the MTK-Engineering-Mode apk's and from then on I used the ruCuNo+ bat to complete it.
I followed stage 6, then 7, then 3. Pointed the Magisk to the original boot img, got it patched, sent it to PC and flashed the boot image with ADB. After turning on the phone, Magisk ended up with two green ticks so everything was good to go.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Matthius said:
I had already unlocked the bootloader myself prior to this, looking for a way to root it before I saw this article (I gather this is the first available root method for this device),
Click to expand...
Click to collapse
yes it is. i searched over a week to find a root solution but nothing found. so i make it by my self and want to share this with the world :highfive:
Matthius said:
and also manually installed MagiskManager and the MTK-Engineering-Mode apk's and from then on I used the ruCuNo+ bat to complete it. I followed stage 6, then 7, then 3. Pointed the Magisk to the original boot img, got it patched, sent it to PC and flashed the boot image with ADB. After turning on the phone, Magisk ended up with two green ticks so everything was good to go.
Click to expand...
Click to collapse
thats also a way :good: maybe i implement this for users who already unlockt the bootloader. then the the phone must not be factory reset again. :good: thanks for telling me this way i dont think of bevor

Schwester_Gabi said:
yes it is. i searched over a week to find a root solution but nothing found. so i make it by my self and want to share this with the world :highfive:
thats also a way :good: maybe i implement this for users who already unlockt the bootloader. then the the phone must not be factory reset again. :good: thanks for telling me this way i dont think of bevor
Click to expand...
Click to collapse
No worries, great work - hopefully, we may see some custom recovery to come in the future from someone. Wish this phone actually had its own page on XDA, but I doubt it has enough widespread support for that, who knows.

Matthius said:
No worries, great work - hopefully, we may see some custom recovery to come in the future from someone. Wish this phone actually had its own page on XDA, but I doubt it has enough widespread support for that, who knows.
Click to expand...
Click to collapse
Yes. custom recovery for the phone would be great. if I knew better, I would make one myself. but I've read a lot. maybe I'll try it in future to make one.
i think this phone dont get his own page. but maybe the Cubot vendor get his own where we can put all related Cubot threads together in his own sub section. :good:

i got a error after "fastboot oem unlock" -> "FAILED (remote:Unlock operation is not allowed)". i think, bootloader is not unlocked, what can i do?
oops: had forget "OEM UNLOCKING in DevMenu"

spunky1a said:
i got a error after "fastboot oem unlock" -> "FAILED (remote:Unlock operation is not allowed)". i think, bootloader is not unlocked, what can i do?
oops: had forget "OEM UNLOCKING in DevMenu"
Click to expand...
Click to collapse
yes. that was the point. :good:

I think the sequence in the Guide is a bit wrong. In the Guide I read:
Schwester_Gabi said:
...
Type:
Code:
adb reboot-bootloader
Than:
Code:
fastboot oem unlock
NOTE: ALL YOUR DATA WILL BE DELETED Press VOL+ on Phone if asked wait for device for unlock...
... (this comes now after)
Enable USB DEBUGGING and OEM UNLOCKING in Menu --> Settings --> Developer Options
...
Click to expand...
Click to collapse
If I follow this I get (in very small fonts) as another user here in this thread:
Unlock failed...return to fastboot in 3s
Click to expand...
Click to collapse
And no unlock of the bootloader seems possible.
Because first I need to do OEM UNLOCKING in the Dev. Options, which seems very clear. Only after I can fastboot oem unlock
What I further not quite understand in this post, is it either the Guide or the Batchfile I have to follow? Or is it a mixture of both what I need to do?
As I think the Batchfile cannot enable the Developer Tools in the System, or?
Lastly and most important: on my phone I don't see a mmcblk07p only a mmcblk0p7, so this throws an error:
Schwester_Gabi said:
...
adb shell dd if=/dev/block/mmcblk07p of=/sdcard/boot.img
...
Click to expand...
Click to collapse
I guess that mmcblk0p7 is ment, so I did a dd with mmcblk0p7, and I let patch this file with Magisk to the file: patched_boot.img
But here I am very not sure and if I flash now a wrong img-file with this:
Schwester_Gabi said:
...
fastboot flash boot patched_boot.img
...
Click to expand...
Click to collapse
I strongly guess that is it with my new phone
So could you please confirm that it was just a typo in the first post here?
How can I know which of these files in /dev/block is the boot.img?
Thank!!!

francwalter said:
I think the sequence in the Guide is a bit wrong. In the Guide I read:
...
Type: Than:
If I follow this I get (in very small fonts) as another user here in this thread:
And no unlock of the bootloader seems possible.
Because first I need to do OEM UNLOCKING in the Dev. Options, which seems very clear. Only after I can fastboot oem unlock
Click to expand...
Click to collapse
For this Problem the batch says first enable dev options and OEM unlock and than go to next step.
francwalter said:
What I further not quite understand in this post, is it either the Guide or the Batchfile I have to follow? Or is it a mixture of both what I need to do?
As I think the Batchfile cannot enable the Developer Tools in the System, or?
Lastly and most important: on my phone I don't see a mmcblk07p only a mmcblk0p7, so this throws an error:
I guess that mmcblk0p7 is ment, so I did a dd with mmcblk0p7, and I let patch this file with Magisk to the file: patched_boot.img
But here I am very not sure and if I flash now a wrong img-file with this:
I strongly guess that is it with my new phone
So could you pleas confirm that it was just a typo in the first post here?
How can I know which of these files in /dev/block is the boot.img?
Thank!!!
Click to expand...
Click to collapse
Yes. Its a typo. You can flash it.
Btw i am on the way to rework the whole Programm for better use and better instructions. Give me some time because iam very busy at the moment. But I will update it soon.
And remember its an 0.1ALPHA for now. So its not perfect :angel:

Oh Great! It works
Thank a lot for your work!!!

As a noob, I did not get what to do after installing the Magisk manager. So I have it installed, but it shows no root. How can I then install the root?
I used the "RoCuNo+_v0.2.bat" in admin mode and although I got through the unlock and root, I am stuck on what to do on Magisk in the phone.
I was able to root my galaxy tab, but perhaps I am too noob for these instructions?
(Btw while booting I get the "this phone is unlocked and cannot be trusted" text)

Ran into a bit of an issue here, I received an official OTA so I uninstalled Magisk by clicking uninstall within the APK, now my phone is stuck on the boot logo. I've tried to flash the original boot img, but I can't get into the system to confirm flashing it on the device. It displays under <adb devices> but when issuing the <fastboot flash boot> command it says <waiting for any device> and nothing occurs.
Not sure how to proceed without wiping the whole thing. Anything I can try?

So I did a factory reset and used the "RoCuNo+_v0.2.bat" again as follows:
First enabled developer mode, USB Debugging unknown sources, OEM unlock
Then ran the tool:
1 - unlock bootloader - success
3 - root - success
5 - install magisk - here the phone first boots, then it erases data, then does again all the "setup your phone, wifi, accounts etc"
"Orange state - this device is unlocked..." appears in the boot
Magisk is not installed in the apps.
OEM unlock is greyed out (but enabled)
So the tool worked differently, or I am missing something.
Perhaps there are new versions of this phone?

...aaaand it's rooted.
I did everything again using the adb -command instructions.
So did not use the .bat tool.
Used the step-by-step instructions.
Thanks a lot! Finally I can use macrodroid properly.

"device is corrupt" solution guide for Nubia Red Magic 3 / 3S

Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android 9 again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Looks like you've been using another cell

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.

kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
give me something i can contact with u in to help u

RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
[email protected] u can contact me here sir

I need some help,
Last time i updated my phone to 5.09 cn rom after that when i got bugs i tried to downgrade to 3.34 and i bricked my phone , then i use unbrick tool and get back to asia version but now my phone doesnot have the charging animation in power off mode and also fastboot device is can't get the device in win7/win 10. I also tried 2-3 times by reflash the cn rom and again back to asian version.
Need help any guide please.
Thanx in advance..
I forgot to mention that adb is working, bootloader is unlocked, i can access bootloader by using keys and adb reboot-bootloader command, but can't get device in device manager in fastboot mode , i can also access 9008 mode and recovery mode. Everything working fine but i have that two issue now, also i have my device in 5.11cn rom now.

kalaan10 said:
hi and thank you for your hard work
last time I installed Red Magic 3 V5.11 (official version) chinese rom, then I thought I need google play store so i wanted to downgrade my rom with the help of nubia red magic 3 unbrick tool which was working fine before Red Magic 3 V5.11 (official version) but at this time when i try to downgrade then it shows your devices is corrupted and will not boot ..... since then i tried each and every possible way to recover it but I don't have any technical knowledge so i'm unable to solve the problem so its my humble request to you please help me sir ....... i don't know how to flash rom through pc please guide me and help me.
Click to expand...
Click to collapse
I think I encountered this problem also when going from Android 11 (V5.11) to Android 10 (V3.34). What worked for me is the tool posted on nubia bbs.
It's on chinese but I put some screenshots on this link to be able to use it.
Red Magic 3 - Mediafire
To use the tool, put your Red Magic 3 on fastboot mode.
How to boot on Fastboot
1.) Turn off your NRM3.
2.) HOLD Volume down and power
3.) Your NRM3 should boot on fastboot
And for google play store, I'm currently using 5.09 and successfully root it with g-apps. Flashing magisk and g-apps is working ong V3.34 and V5.09.

I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now

cacaocaca said:
I had problem about less charger mA on 3 charger and cables so strange , so today i did buy another cable and same thing less mA like 100 should be 3000 , so i did use one charger adapter rampow for try , when i did put charger less again but the screen get blocked and reboot , when it restarted i did see that if i put to charger again also with orginal charger and cable will block screen and reboot so i did try to reset and install Europe & Asia: V212 , when did get 100% will show that " Device is corrupt. It can't be trusted and will not boot " ,this happen if you put one not original cable or charger i did discovery ,now the problem is if i put the cable on laptop for flash install roms windows will not detected the new hardware of red magic so how can i fix that now
Click to expand...
Click to collapse
Have you tried to on the developer options and turn on USB debugging on your Red Magic 3?

How can I activate the debug if just show me that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance

Maybe it hardbrick

RZaR2001 said:
give me something i can contact with u in to help u
Click to expand...
Click to collapse
can u help me too pls

cacaocaca said:
How can I activate the debug if just show me that View attachment 5173669
I can just enter in recovery mode , emerg recovery mode and edload but I can t do nothing if windows will not detect the device, this it happen when I did use the charger not official, it just ridiculous, I did use the charger rampow for iPhone android without problem while in this phone did happen that just because Nubia want steal money for the assistance
Click to expand...
Click to collapse
I think you should try service centre once.

jhonangelo30 said:
can u help me too pls
Click to expand...
Click to collapse
Okay pm me

3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school

johnbrinan1 said:
3
Sir i have the same thing. Im using rm3 when i bought this its already flash on global rom. So im curious because its box is Chinese text but it's global rom so i flash to china rom and its success but suddenly i figure it out that chinarom doesn't have google so i flash again to global rom then suddenly it corrupt after the flash. I tried those method like that unbrick tool non.eu i follow the steps very well but when it comes to the part that cmd will pop 'downloading port 4'
It says that faile and un identified and it says that please check your status or what. I'm humble asking for your help because this is my only phone and i need this for my online school
Click to expand...
Click to collapse
don't worry it can be fixed

RoseRahman said:
I think you should try service centre once.
Click to expand...
Click to collapse
My phone was in assistance and now it come back and work fine , no more device corrupt and no more slow charger , they did exachange the motherboard on my phone , if you will not ear the sound while plug the device to windows this mean problem motherboard maybe like me

leipnacht said:
Sharing this guide seems quite late but since xda red magic threads taught me a lot about the rooting and corrupted stuffs, I think it would not hurt to return something back to this community.
This is my attempt to compile people's responses that helped other people here which are scattered around forums.
Myself included also tinkered a lot on this device and literally go back here on this guide to lessen headaches.
EDIT: Tested a lot of times with V5.08 and V5.09 Android R versions
REMINDER: Tested on Android 9, no clues yet on Android 10 and 11
WHEN TO USE?
Use this guide to restore your phone to boot in Android OS again normally without wiping data, retaining your apps, games intact
Requirements:
- Windows computer. NOTE: Done this using Windows 10, so I'm not exactly sure if latest ADB works the same on Windows 7.
- Nubia Red Magic 3 or 3S battery charge should be at 50% above at least.
- You need a USB cable to connect your phone to PC. XDA Users reported better with USB 2.0 port
NOTE: Can be used also on 3S. I just don't have 3S so I haven't tested it on actual 3S.
Download latest the ADB (Android Debug Bridge) from Android Developers site.
1.) Go to https://developer.android.com/studio/releases/platform-tools
2.) Click Download SDK Platform-Tools for Windows.
3.) Click the checkbox beside 'I have read and agree with the above terms and conditions'
and click DOWNLOAD ANDROID SDK PLATFORM-TOOLS FOR WINDOWS
*Current version as of December 12, 2020
platform-tools_r30.0.5-windows.zip
4.) Create a folder in C:\ Drive and name it ADB. Extract platform-tools_rxx.x.x-windows.zip inside ADB folder.
*NOTE: rxx.x.x on platform-tools_rxx.x.x-windows depends on the current version available on Android Developers site.
5.) On your Windows desktop, press the Window logo button on your keyboard, type 'cmd'. Right-click on Command Prompt and click Run as administrator.
7.) On command prompt, type 'cd c:\ADB' and press Enter. *type without quotes *DO NOT CLOSE Command prompt!
8.) Connect your Nubia Red Magic 3 or 3S to a USB 2.0 port.
9.) Wait for Windows to install drivers of your phone. If a CD Drive showed up on "This PC / My Computer", double-click on it and install the driver.
10.) Type 'adb reboot bootloader' and press Enter. *type without quotes
11.) Go back to your command prompt. Type 'fastboot devices'. It should show your phone's serial number and a 'fastboot' word. This means your PC can properly communicate with your Nubia Red Magic 3. *DO NOT CLOSE Command prompt!
12.) Get your ROM ready. Download from these official links if you haven't already.
IMPORTANT: Try to remember the specific version of ROM your Red Magic has.
Because for example if the currently installed is Android 11 (R) but you used the lower version say Android 10 or 9, flashing will proceed but it will not boot to Android OS
For Global, Europe and North America versions:
REDMAGIC 3 Global ROM flash instructions - REDMAGIC (Global)
Want to flash your REDMAGIC device? Here's how. NOTE: Please proceed with caution.
global.redmagic.gg
Chinese version:
Nubia Red Magic 3
http://ui.nubia.cn/rom/detail/62
Nubia Red Magic 3S
http://ui.nubia.cn/rom/detail/64
13.) Extract the zip file to any folder you want. Get inside it and copy the following:
* parameter.img
* boot.img
* recovery.img
* splash.img
* dtbo.img
* vbmeta.img
* NON-HLOS.bin
* dspso.bin
14.) Continuing from the step above, paste the files you copied to ADB folder you created from step 4.
15.) Go back to your command prompt. And type and press Enter the below commands one by one:
fastboot oem nubia_unlock NUBIA_NX629J
fastboot erase parameter
fastboot flash parameter parameter.img
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase splash
fastboot flash splash splash.img
fastboot erase dtbo
fastboot flash dtbo dtbo.img
fastboot erase vbmeta
fastboot flash vbmeta vbmeta.img
fastboot erase modem
fastboot flash modem NON-HLOS.bin
fastboot erase dsp
fastboot flash dsp dspso.bin
Recommended read:
Why erase is important: https://android.stackexchange.com/questions/161103/what-fastboot-erase-actually-does#161115
*Disconnect the USB-C cable from your NRM3/3S
16.) Your phone still on fastboot, press volume down to choose "Reboot to recovery mode" and press power button to confirm.
17.) Your phone should boot to recovery. On the recovery Main Menu, press volume down to choose 'Wipe Data', choose Wipe cache and also User partition.
18.) After the wipe is successful, copy the ROM zip file to your USB flash drive. Insert your USB Flash drive to your OTG USB-C adapter. Then finally insert it to your Nubia Red Magic 3/3S USB-C port.
19.) Your phone still on recovery, select "Choose Update Package" and specify the ROM zip file in your USB OTG device.
20.) Wait for the system installation to finish.
Alternatively, you can view the guide's pastebin. Plain and simple layout especially when you are just using data on your phone
Solution for Nubia Red Magic 3 / 3S "device is corrupt"
Click to expand...
Click to collapse
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?

ZephyrOne said:
Hello, thanks for your contribution I practiced it 100 but it did not work, I hope you can help me, I have a global nubia rm3S, I had android 9 but I wanted to change to android 11 ch, when updating by OTG it worked without problems, but I did not open an application of my work so I had to try to return to android 9 global, but after the update reached% 100 it restarted and I stayed in DEVICE CORRUPT, now I don't know what to do, I already tried with your method and everything Apparently it is perfect, it does not make an error in anything and I have communication from the adb it gives me my serial number and the drivers are perfect, what can I do?
Click to expand...
Click to collapse
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.

leipnacht said:
I see you upgraded to Android 11 CN then downgraded to Android 9 again. You need the TWRP from baidu guide regarding downgrading from A11.
Here's the link. Google Drive - TWRP from Baidu
DM me if you're having problems with TWRP.
Click to expand...
Click to collapse
Hello thanks for your help, the problem is that I do not enable oem unlocking in the system. Do you know if twrp can be installed without that option?

[UNOFFICIAL]TWRP 3.6.0 for Infinix Zero 8/8i X687/X687B

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project, or TWRP for short, is a custom recovery built with ease of use and customization in mind. Started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of features. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.​
Rich (BB code):
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or
you are getting fired because the alarm app failed. Please do some research if
you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me
for messing up your device, I will laugh at you.
Key Features:
Custom Firmware installation
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Backups of partitions in TAR or raw Image format
Ability to choose which partitions to back up and which to restore
Restore backups from internal storage, external SD storage or OTG devices
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Partition wiping
File Manager(copy, move, rename, delete etc)
Terminal access
ADB Root Shell
Onscreen keyboard
Easy selection of internal/external storage
and more...
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. TeamWin call this scripting engine OpenRecoveryScript.
Working
Decryption
MTP
fastbootd
USB OTG
Not Working
Decryption in Android 12
If you encounter any that are not listed, do let me know here
Download
For Infinix Zero 8 X687 https://androidfilehost.com/?fid=17825722713688252724
For Infinix Zero 8i X687B https://androidfilehost.com/?fid=17825722713688253090
Instructions
Unlock Bootloader
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash recovery TWRP.img
See this guide for flashing GSI
Credits
TWRP Lead Developers:- Dees_Troy, bigbiff and Captain_Throwback
@mastersenpai05 for initial TWRP at here
@kusti420 for all the testing
@lopestom for helping a lot in decryption
Sources
TWRP Sources
TWRP Gerrit Instance
TWRP Website
Device Tree

Pro

mastersenpai05 said:
Pro
Click to expand...
Click to collapse
indeed

can it work for x687b

flash done
but when install any file like disable dm_verity got error...
and when install update.zip got error .. the file for x687b and the phone seen as x687
can i change that ?

Neutrino656 said:
flash done
but when install any file like disable dm_verity got error...
and when install update.zip got error .. the file for x687b and the phone seen as x687
can i change that ?
Click to expand...
Click to collapse
Take screenshot and give recovery.log with below command
adb pull /tmp/recovery.log
Thanks

here it is
recovery.log - dcb6c593
Starting TWRP 3.5.2_10-MASTERSENPAI-48d9d47e on Thu Aug 12 13:55:58 2021 (pid 357) RECO - dcb6c593
controlc.com

How to unlock bootloader ?

Blacxx said:
How to unlock bootloader ?
Click to expand...
Click to collapse
You need to enable the developer option to activate OEM unlock and USB Debugging
To enable the developer option, Go to your Settings -> About phone -> Now tap on the Build Number 7-8 Times until you see a toast message “You are now a developer!“
Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to the computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command windowadb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloaderadb reboot bootloader
Once your phone reboots into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers correctly installed.
Now enter the command given below to verify whether your device is been connected properly to PC."fastboot devices"
This command will list the connected devices. If your phone’s serial number shows up, you are good to go and may continue. If the phone is NOT listed, this indicates that your drivers are not installed correctly. To keep the setup, you must fix your drivers to list your device under fastboot devices.
If the phone is recognized by the command above, proceed to boot into bootloader by tapping down the volume down button on your phone and select the BOOT TO DOWNLOAD MODE option with power key. Now you can unlock the bootloader with the following command: Remember that this step will wipe EVERYTHING off the phone."fastboot flashing unlock"
Notably, if this command does not work you can try to use the below command:"fastboot oem unlock"
You will get a confirmation on your Android device’s screen, Navigate to yes and hit the Power button to unlock the bootloader of your device.
Once the bootloader is unlocked, your smartphone will automatically reboot into bootloader mode.
Now again you can enter the command to reboot your device to the system "fastboot reboot"
Your Android device will now reboot and during this, all data will be erased.
That’s It!
That’s all you have to do to unlock the bootloader

Neutrino656 said:
here it is
recovery.log - dcb6c593
Starting TWRP 3.5.2_10-MASTERSENPAI-48d9d47e on Thu Aug 12 13:55:58 2021 (pid 357) RECO - dcb6c593
controlc.com
Click to expand...
Click to collapse
Same specs right?

mastersenpai05 said:
Same specs right?
Click to expand...
Click to collapse
yes
the changes in device name and fingerprint

Neutrino656 said:
You need to enable the developer option to activate OEM unlock and USB Debugging
To enable the developer option, Go to your Settings -> About phone -> Now tap on the Build Number 7-8 Times until you see a toast message “You are now a developer!“
Go back to settings -> Now you need to enable the OEM Unlock by going to Settings -> Developer Option and Enable OEM Unlock and USB Debugging
Download and Extract the Downloaded ADB fastboot Zip file on your PC.
Now connect your phone to the computer using USB Cable.
When you connect your Phone to Computer, please wait until all the drivers get installed.
In your ADB fastboot folder open a command prompt window by pressing Shift Key + Right Mouse Click
Now type the command in your command windowadb devices
If you see a pop up to allow USB Debugging on your phone, Click OK
Now type the command below to reboot your phone to bootloaderadb reboot bootloader
Once your phone reboots into bootloader, make sure your phone shows the bootloader locked and then type the command below to make sure fastboot drivers correctly installed.
Now enter the command given below to verify whether your device is been connected properly to PC."fastboot devices"
This command will list the connected devices. If your phone’s serial number shows up, you are good to go and may continue. If the phone is NOT listed, this indicates that your drivers are not installed correctly. To keep the setup, you must fix your drivers to list your device under fastboot devices.
If the phone is recognized by the command above, proceed to boot into bootloader by tapping down the volume down button on your phone and select the BOOT TO DOWNLOAD MODE option with power key. Now you can unlock the bootloader with the following command: Remember that this step will wipe EVERYTHING off the phone."fastboot flashing unlock"
Notably, if this command does not work you can try to use the below command:"fastboot oem unlock"
You will get a confirmation on your Android device’s screen, Navigate to yes and hit the Power button to unlock the bootloader of your device.
Once the bootloader is unlocked, your smartphone will automatically reboot into bootloader mode.
Now again you can enter the command to reboot your device to the system "fastboot reboot"
Your Android device will now reboot and during this, all data will be erased.
That’s It!
That’s all you have to do to unlock the bootloader
Click to expand...
Click to collapse
Its need driver ?

Blacxx said:
Its need driver ?
Click to expand...
Click to collapse
Infinix Zero 8i USB Driver for Windows (Official Mobile Driver)
Download the official Infinix Zero 8i USB Driver for your Infinix Mobile. We also provide all other Infinix Mobile drivers for free.
gsmusbdriver.com

Neutrino656 said:
Infinix Zero 8i USB Driver for Windows (Official Mobile Driver)
Download the official Infinix Zero 8i USB Driver for your Infinix Mobile. We also provide all other Infinix Mobile drivers for free.
gsmusbdriver.com
Click to expand...
Click to collapse
Ok thanks bro

Neutrino656 said:
here it is
https://controlc.com/dcb6c593
Click to expand...
Click to collapse
Thanks, will fix it later. I am somewhat busy right now. If you get any other issue too, please do let me know with logs.

sure

Neutrino656 said:
sure
Click to expand...
Click to collapse
Here is the update.zip flashing fixed build. https://oshi.at/seHmaB
Test it and let me know.
also, in recent Android versions, disabling dm-verity needs to flash vbmeta.img like fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
So don't use that dm-verity disabler
Thanks

HemanthJabalpuri said:
Here is the update.zip flashing fixed build. https://oshi.at/seHmaB
Test it and let me know.
also, in recent Android versions, disabling dm-verity needs to flash vbmeta.img like fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
So don't use that dm-verity disabler
Thanks
Click to expand...
Click to collapse
can i flash it via recovery or i must flash via fastboot

i have disabled verity and verification before
is that ok or i have to do it again ..
every time i flash a file

Neutrino656 said:
can i flash it via recovery or i must flash via fastboot
Click to expand...
Click to collapse
You can flash recovery in either fastboot or existing cuatom recovery or in rooted rom.
For vbmeta, only use fastboot mode with above command.
Also as long as vbmeta is not back to stock(i.e., when you flash stock rom) you don't need to flash again and again.
Flashing once is enough.
Thanks

[GUIDE][RMX3381] Unlock Bootloader, Root Realme 8s 5G [UNOFFICIAL]

Hi Guys!
Since there is no deeptest.apk available for our device to unlock bootloader, we came up with another method to unlock bootloader unofficially!
Deeptest apk is now available link is in comments section
In this guide I'll tell you how to unlock bootloader, root with magisk on your Realme 8s 5G (RMX3381)
Code:
/*
* This Guide is tested and working
* However I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about unlocking and flashing TWRP
* before flashing it! YOU are choosing to make these modifications.
*/
1. UNLOCKING BOOTLOADER:
Requirements
PC or Laptop
Internet connection
Realme 8s
USB cable
Working Brain
Take a backup of your data since it'll be wiped
Go to About phone > Version and tap build number 7 times
Go to Settings > advanced settings > Developer options and turn on OEM unlocking and USB debugging
STEPS
Install Python from windows store
Install USBDk
Download this and extract : https://github.com/bkerler/mtkclient/archive/refs/heads/main.zip
Now open command prompt or powershell in that folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked
Due to realme's limitations you still can't access fastboot after unlocking via this method
2. ROOTING YOUR DEVICE:
Install This Magisk apk
Download patched boot image and copy to the mtkclient-main folder in pc
Now in pc type python mtk w boot,vbmeta boot.patched,vbmeta.img.empty hit enter
Then power off your phone and connect usb while holding both volume buttons (and don't leave them)
Now disconnect and reboot phone
Now open magisk
Credits:
Me (@pritish1998) for Unlock and Flashing guide
B Kerler fot MTKClient
Stock boot Image (to revert root)
If you face any issues contact me here

If anyone wanna test TWRP you can reply me here!

Deeptest Apk is now available
You don't need the above steps to unlock bootloader now:
- Enable OEM unlocking and USB debugging from developer options
- Then install this apk : DeepTest
- Submit application
- After submission, Click on 'start Indepth test' to boot into Fastboot or Bootloader
- Now connect your realme 8s to Platform tools or Bugjaeger to execute these fastboot commands
fastboot flashing unlock
- Press vol buttons as per shown in phone fastboot mode
- After confirming unlock, type fastboot reboot & Done!!
NOTE : This apk seems to work only with devices with RUI 2.0 based on COS 11 like realme 8 and 8s, it won't work on device based on COS 11.3 like realme 8i

Is there any custom rom available for this device?

Wahmed178 said:
Is there any custom rom available for this device?
Click to expand...
Click to collapse
At this moment , No. However I have twrp, need a tester for that.

Now connect your realme 8s to Platform tools or Bugjaeger to execute these fastboot commands..
Please explain this Sir, Do i need to install these tools in PC or adb is enough after booting into fastboot.

Manoj Raina said:
Now connect your realme 8s to Platform tools or Bugjaeger to execute these fastboot commands..
Please explain this Sir, Do i need to install these tools in PC or adb is enough after booting into fastboot.
Click to expand...
Click to collapse
Well the whole point of making this guide is… you cannot access fastboot in this device unless you have registered for unlock in deeptest apk.. which wasn’t available at the time of making this guide …and for unlocking u needed to follow this whole procedure and its mandatory to have a pc for it to work

pritish1998 said:
Well the whole point of making this guide is… you cannot access fastboot in this device unless you have registered for unlock in deeptest apk.. which isn’t available yet for it. … and for unlocking u need to follow this whole procedure and its mandatory to have a pc for it to work
Click to expand...
Click to collapse
I just didn't understand that connect your realme 8s to Platform tools or Bugjaeger..
Could "fastboot flashing unlock" command can executed in adb? If no... Please give link to that platform tools or Bugjaeger

Manoj Raina said:
I just didn't understand that connect your realme 8s to Platform tools or Bugjaeger..
Could "fastboot flashing unlock" command can executed in adb? If no... Please give link to that platform tools or Bugjaege
Manoj Raina said:
I just didn't understand that connect your realme 8s to Platform tools or Bugjaeger..
Could "fastboot flashing unlock" command can executed in adb? If no... Please give link to that platform tools or Bugjaeger
Click to expand...
Click to collapse
ok so u applied via deeptest I’ve given in the comments section? U can use bujarget to use that command
Click to expand...
Click to collapse

Manoj Raina said:
I just didn't understand that connect your realme 8s to Platform tools or Bugjaeger..
Could "fastboot flashing unlock" command can executed in adb? If no... Please give link to that platform tools or Bugjaeger
Click to expand...
Click to collapse
Also if u are on telegram just contact me there in the group

anything on twrp ?
I'm trying to find it so that magisk stable could be flashed easily , but it appears this device is quite rare
plus magisk boot image you provided, what version it supports ?

pritish1998 said:
Hi Guys!
Since there is no deeptest.apk available for our device to unlock bootloader, we came up with another method to unlock bootloader unofficially!
Deeptest apk is now available link is in comments section
In this guide I'll tell you how to unlock bootloader, root with magisk on your Realme 8s 5G (RMX3381)
Code:
/*
* This Guide is tested and working
* However I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about unlocking and flashing TWRP
* before flashing it! YOU are choosing to make these modifications.
*/
1. UNLOCKING BOOTLOADER:
Requirements
PC or Laptop
Internet connection
Realme 8s
USB cable
Working Brain
Take a backup of your data since it'll be wiped
Go to About phone > Version and tap build number 7 times
Go to Settings > advanced settings > Developer options and turn on OEM unlocking and USB debugging
STEPS
Install Python from windows store
Install USBDk
Download this and extract : https://github.com/bkerler/mtkclient/archive/refs/heads/main.zip
Now open command prompt or powershell in that folder
Now type pip3 install -r requirements.txt and hit enter
Now type python mtk e metadata,userdata,md_udc hit enter - This command wipes data
Then power off your phone and hold both volume buttons and connect usb cable (DON'T LEAVE THE BUTTONS, KEEP THEM HOLDING THROUGHOUT THE PROCESS) - This boots device into BROM mode
Now type python mtk da seccfg unlock This will unlock the bootloader (If you face waiting for device issue then unplug the device and plug in the device again with holding volume buttons, also don't leave the buttons)
After this unplug your phone and turn it on (It'll show your device dm verity corrupted and first boot might take 20-25 mins, don't panic)
Now your bootloader is unlocked
Due to realme's limitations you still can't access fastboot after unlocking via this method
2. ROOTING YOUR DEVICE:
Install This Magisk apk
Download patched boot image and copy to the mtkclient-main folder in pc
Now in pc type python mtk w boot,vbmeta boot.patched,vbmeta.img.empty hit enter
Then power off your phone and connect usb while holding both volume buttons (and don't leave them)
Now disconnect and reboot phone
Now open magisk
Credits:
Me (@pritish1998) for Unlock and Flashing guide
B Kerler fot MTKClient
Stock boot Image (to revert root)
If you face any issues contact me here
Click to expand...
Click to collapse
Does this work on realme 8 5g