Database Info

[GUIDE] Unlock/Root/Flash for Moto X Style/Pure

[SIZE=+3]Heisenberg's How-To Guide For Beginners[/SIZE]
{
"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"
}
[SIZE=+2]Moto X Pure[/SIZE]​
[SIZE=+1]Intro[/SIZE]
This thread will serve as a location for basic how-to guides for the Moto X Pure. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
[size=+1]Prerequisites[/size]:
You'll need a working adb/fastboot environment on your PC to get through some of these guides. Go here to download the Android SDK, which will give you most updated version of adb and fastboot. Scroll to the bottom of the page and find Other Download Options>SDK Tools Only, and grab the right version for your OS. While it's downloading create a folder in C:\ called SDK (C:\SDK). Once you've downloaded the zip you can extract it into your C:\SDK folder. Navigate to C:\SDK\android-sdk-windows and open SDK Manager.exe. In SDK Manager you need to install the following packages:
Tools> Android SDK Tools, Android SDK Platform-tools
Extras> Android Support Library
Once you have installed those, inside C:\SDK you should see some new folders, one of them will be called platform-tools, within that folder you should see fastboot.exe and adb.exe. I'll refer to this as your fastboot folder/directory or working folder/directory during this guide. To make sure adb is correctly installed, open a command prompt from within your fastboot folder (hold shift + right click, select open command prompt here) and issue this command:
Code:
adb version
If it returns a version number for Android Debug Bridge then you're good to go.
You'll find Motorla drivers here, download it and install, then reboot your PC.
You can test adb by connecting your device to your PC while booted into Android (making sure that adb/usb debugging is enabled in Settings>Developer Options) with the screen unlocked and issuing this command:
Code:
adb devices
It should return your device serial number, if so, adb is working.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume down) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
[SIZE=+1]Index[/SIZE]
How To Unlock Your Bootloader
How To Install A Custom Recovery On Your Device
How To Make A Nandroid Backup With TWRP Recovery
How To Root Your Stock Rom
How To Install A ROM with TWRP Recovery
How To Install A Custom Kernel With TWRP Recovery
How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System
[SIZE=+1]1. How To Unlock Your Bootloader[/SIZE]
Go into About Phone in Settings, click on Build Number 7 or 8 times until it says you have enabled Developer Options. Go back to Settings and enter the newly opened Developer Options section, scroll and click on the Enable OEM Unlock option.
Power off your phone then boot into fastboot mode (power + volume down).
Connect your phone to your PC via usb cable.
Open a command prompt from within your fastboot folder (navigate to where you have fastboot.exe located on your PC, shift + right click anywhere within that folder, select open command prompt here).
Check your fastboot connection by issuing this command:
Code:
fastboot devices
It should return your device serial number, if not you need to make sure your drivers are installed correctly.​
Once you've confirmed your fastboot connection issue this command:
Code:
fastboot oem get_unlock_data
It should return something like this:
Code:
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
Copy that code (with no spaces between the characters) and paste it somewhere for safekeeping, you'll use it in a minute.
Go to the Motorola bootloader unlocking page. You'll need to create an account with Motorola if you don't already have one. Once you're signed in you can scroll down to step 6 and paste the above code into the text field and hit the “can my device be unlocked” button.
Read the terms and conditions and accept them if you agree (you can't continue unless you accept).
Click the “request unlock key” button and an email with your unlock token will be sent to the email account that you signed up with.
Once you have retrieved the token from the email you can use it within the following command to unlock your bootloader:
Code:
fastboot oem unlock xxxxxxxxxx
(Replace the xxxxxxxx with your unique unlock token)​
Your bootloader is now unlocked!
Reboot with this command:
Code:
fastboot reboot
It's now safe to disconnect your usb cable.
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
[SIZE=+1]2. How To Install A Custom Recovery On Your Device[/SIZE]
Prerequisites: unlocked bootloader.
Download the recovery of your choice, here's TWRP.
Make sure you check the md5 to verify its integrity (where possible).
Place the file in your fastboot folder (this is where fastboot.exe is located on your PC).
Put the phone in fastboot mode and connect it to your PC via usb cable.
Open a command prompt from within your fastboot folder (shift + right click, select open command prompt here), and enter the following commands:
Code:
fastboot flash recovery <filename>.img
(Replace <filename> with the actual filename of the recovery, the recovery filename in the command will change depending on which recovery you're flashing)
Wait for the recovery to flash, it'll only take a few seconds, you'll get a finished message in your command prompt window once it's done.
It's now safe to disconnect your usb cable.
Don't reboot the phone normally, use the volume buttons to highlight recovery and press the power button to select it. This will stop the stock OS from patching it with the stock recovery in boot. Once you've booted into TWRP like this once, you can reboot normally.
[SIZE=+1]3. How To Make A Nandroid Backup With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A nandroid backup is a very important thing to have before installing any custom software on your device. It's basically a backup of your stock system that you can fall back on if anything goes wrong or if you just want your stock ROM back. You can also use the backup tool to create a backup of your favourite ROM set up exactly the way you like it. The backup you create can be easily restored using the restore tool in TWRP recovery.
All you need to do is enter TWRP recovery, select the backup option from the TWRP home screen, check the system/data/boot boxes, and swipe to backup. The process will take a few minutes.
[SIZE=+1]4. How To Root Your Stock Rom[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Please note: this method is only valid for Lollipop, do not use this method on Marshmallow. You can find a systemless root method for Marshmallow here, big thanks to @ivcarlos!
Download SuperSU to your phone.
Boot into TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to where you have SuperSU stored on your sd card and select it.
Swipe to install.
Once you've installed SuperSU you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button. That's it.
[SIZE=+1]5. How To Install A ROM with TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
Installing a ROM is a pretty straight forward and easy process. Before you install anything you should make a nandroid backup (instructions above).
Download a ROM and appropriate Gapps package and place on your device.
Boot into your custom recovery.
Perform a full wipe.
Select the wipe option from the TWRP home screen.
Select advanced wipe.
Check the system, data, cache, and dalvik cache options.
Swipe to wipe.
Install the ROM.
Select the install option from the TWRP home screen.
Navigate to where you have the ROM zip stored on your sd card and select it.
Swipe to install.
Most ROMs will run an installer script at this point but some ROMs have what is called an Aroma Installer which allow you to choose some install options before the script runs.​
You will also need to install the appropriate gapps package directly after installing the ROM.
Once you've installed all necessary zips you'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
[SIZE=+1]6. How To Install A Custom Kernel With TWRP Recovery[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
A custom kernel can open up a new level of control over your device, such as overclocking/underclocking, undervolting, changing governors, changing I/O schedulers, adjusting colour calibrations, adjusting sound calibrations, and many other options.
Download a kernel that is compatible with your current ROM.
Check the md5 to verify its integrity.
Enter TWRP recovery.
Select the install option from the TWRP home screen.
Navigate to the kernel and select it.
Swipe to install.
You'll have an option to wipe cache/dalvik and an option to reboot system. Wipe the cache/dalvik, hit the back button, and hit the reboot system button.
Once your phone has booted up you can use a kernel tuning app to change governors, I/O scheduler, clock speed, and other options. Some of the popular kernel apps are Kernel Auditor, Trickster Mod, No Frills, Kernel Tuner, and many more.
[SIZE=+1]7. How To Make Sure You Can Pretty Much Always Recover From An Accidentally Wiped System[/SIZE]
Prerequisites: unlocked bootloader, TWRP recovery.
There may come a time when you accidentally wipe your OS while trying to perform a basic cache wipe in recovery. Don't laugh, it can happen to the best of us. The best way to insure yourself against being stuck in recovery is to keep a ROM zip or a TWRP/CWM backup (a nandroid backup) on your sd card at all times.
This solution seems like common sense but apparently there are quite a few people out there who don't store a ROM or backup on their phone. You might think it's easy to just mount the OTG storage and copy a ROM across to your phone from your PC (which is definitely an option), but there's always a chance that you won't be near your HDD or sd card at the time, or it won't recognise your phone properly. Basically you need to insure yourself against Murphy's law.
Donate To Me

This will be very helpful to many thanks for taking the time to put this together!
Sent from my XT1575 using Tapatalk

Thank you so much for taking the time on the guide. There will be many who will use it in the years to come! I'm just about at the verge of needing to root so I can get some insight into my battery life woes

This is much appreciated. All I did on my LG G2 was root as I did not see any roms that interested me since the bootloader is locked. I haven't used TWRP in a couple of years, so all this will help me clear the old cobwebs in my head.

Thank you so much for this! Exactly the kind of information I need. Can I trouble you to maybe add one more section to your guide: What to do when there's an OTA update from the manufacturer (Motorola)? I have concerns like:
- Would being rooted prevent OTA updates? (Assuming stock ROM).
- Would I need to "unroot" the phone to get the update? If so, how to unroot the the phone?
- Is the process to root the phone again after the the update the same, or could it possibly change?
- Would I need to wait until root is confirmed for the new version before attempting to re-root?

You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?

Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery

elitemeat said:
You said to "Make sure you check the md5 to verify its integrity".
What does this mean and how would I do this?
Click to expand...
Click to collapse
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.

Oops

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
Thanks for your suggestions.
1. This info has been added.
2. This section is in the same place in all of my guides, I see no problem (and have had no problems) with its location. Anyone following a guide should read it first before attempting it anyway.
3. I've added inductions to download the zip directly to the phone, less mess.

emailrob said:
Thanks again for the guide. I went through this for my own unlock and root, so added a couple of minor things that will help noobs (and me!)
1. Add info on opening developer options, enabling ADB devices, and enable OEM unlock (in options screen)
2. Move this part to the start of the OEM unlock section : )
Please note: this will erase all user data from your device, it is best to do this before you really start using the device and installing apps or putting data on the internal storage
3. Add instructions to copy SuperSU zip file to internal storage and then flash in recovery
Click to expand...
Click to collapse
This is already covered here:
http://forum.xda-developers.com/moto-x-style/help/root-to-updates-t3200588

Oaklands said:
You can download an MD5 checker. They give you the MD5 checksum and you can compare when you run the utility. Just do a google search for md5 checker.
Click to expand...
Click to collapse
If you're on Windows, I highly recommend this one, I've been using it for ages: http://code.kliu.org/hashcheck/

I flashed SU and it didn't give me root, any suggestions?

mxpxboi said:
I flashed SU and it didn't give me root, any suggestions?
Click to expand...
Click to collapse
Have you enabled root for apps (and adb if you wish) in Developer Options?

Heisenberg said:
Have you enabled root for apps (and adb if you wish) in Developer Options?
Click to expand...
Click to collapse
I don't see root for apps in Developer Options.

mxpxboi said:
I don't see root for apps in Developer Options.
Click to expand...
Click to collapse
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.

Heisenberg said:
Ok. I don't have this device yet (I have to jump through a few hoops to get it in my country), hopefully one of our other helpful members can lend a hand with your problem.
Click to expand...
Click to collapse
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.

mxpxboi said:
Well thanks for your help anyway. I followed the steps to a tee, and no root. So I was a little confused.
Click to expand...
Click to collapse
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?

Heisenberg said:
It's a bit odd because this is definitely how to root this phone. Was the SuperSU flash successful in TWRP? Have you tried a second time?
Click to expand...
Click to collapse
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.

mxpxboi said:
It did flash successfully, I flashed the one it linked to UPDATE-SuperSU-v1.94.zip, I'm going to try the newest one BETA-SuperSU-v2.49.zip. I'll report back.
---------- Post added at 10:57 PM ---------- Previous post was at 10:44 PM ----------
That worked, I would update your post with this link BETA-SuperSU-v2.49
Now if I can figure out how to remove the bootloader unlocked boot screen.
All root apps except Titanium Backup seem to be working for me.
Click to expand...
Click to collapse
Cool, I've updated the link. There's a thread discussing how to remove that boot screen in the q&a or general section. Not sure about your Titanium problem, if you have root access it should work.

[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.

[RECOVERY][UNOFFICIAL] TWRP 3.3.1-0 - YU Ace YU5014 [Working]

{
"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 (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices, although it isn't dependent on a device being rooted prior to installation.
In my view you have already enabled Developer Options and unlocked bootloader. Also you have ADB drivers installed.
Note: This is not a port and the recovery is built from Omni Source. So you will not faces any issues (atmost). Everything you do to your smartphone is your responsibility and we (and I) are here to help you. Follow instructions properly to customize your device.
Important:
This recovery is based on November 2018 update. We have 3 updates (December 2019, July 2020 and October 2020) so TWRP will be overwritten. To fix this.
1. Either we have to update twrp OR
2. Root first then flash TWRP (this worked for me with December update but I highly doubt if it works with October 2020 update) OR
3. Someone share stock recovery of latest October update so I can update source and TWRP. You can PM me for instructions on this.
OEM Unlock
1. First enable OEM Unlock available in the developer settings.
2. Install ADB drivers and use this command to enter into fastboot mode.
Code:
adb reboot bootloader
or
use Power + Volume Up buttons after shutdown/power off. Then choose fastboot mode with volume key as navigation.​
3. Use the below command to unlock OEM.
Code:
fastboot oem unlock
Follow onscreen instructions.
4. For flashing TWRP go on reading.
Download:
1. AndroidFileHost
2. Github
Instructions:
1. Download the TWRP. Open Command Prompt (CMD) or Terminal and connect your mobile to PC using USB cable.
2. Enable USB Debugging, then type the below command and hit enter.
Code:
adb reboot bootloader
3. Use the below command if your device is recognized in the fastboot mode by issuing below command:
Code:
fastboot devices
If your device is not recognized then disconnect and reconnect the cable properly.
4. Now flash the img file you have downloaded from the link above and it is named as TWRP_recovery.img, use below command.
Code:
fastboot flash recovery TWRP_recovery.img
5. It takes few seconds to flash and after that you can enter Recovery mode by using below command.
Code:
fastboot oem reboot-recovery
6. It takes 5 - 10 sec at TWRP main screen and you need not worry about that.
7. TWRP will ask for Decryption password. Tap on cancel.
8. You have to Format Data if you want to access Internal Storage.
9. You have to flash Magisk if boot.img is not patched (I can extend this thread on this on user request).
10. To take back-ups you first need to Format, otherwise TWRP won't work to its potential.
Happy TWRPing.
Update: Android 10 GSIs are working. (Need update on Android 11)
Working:
1. OTG will recognize.
2. You can push or pull files between smartphone and PC.
Issues:
1. MTP wont work.
2. Decryption does not work. So take backups into Micro Sdcard.
3. You can post them here.
Need:
1. I need one or two testers to check whether this recovery is working (for me it is working) to its full extent and can flash GSIs. Working.
2. I have unlocked this device long ago so I forgot the command used earlier. Anyone of you can share that command to help others and also I will extent this thread from unlocking to flashing GSIs. (I know 3 commands but don't know which one I used)
Sources:
1. Minimal TWRP: https://github.com/minimal-manifest-twrp/platform_manifest_twrp_omni
2. YU5014 device tree: https://github.com/buddi56/android_device_YU_YU5014
TWRP Version: 3.3.1-0
Thanks to:
YU Team,
TWRP Team,
XDA Team.
Build Date: 19 Dec, 2019
Status: Stable
Made by: Me
Thread Created: 21 Oct, 2019
Last Updated: 23 March, 2021

Is it for indian yu ace 2gb 16 gb model.

rupeshmourya said:
Is it for indian yu ace 2gb 16 gb model.
Click to expand...
Click to collapse
I have made this TWRP with 2GB variant. Need testers for 3GB variant.
You can even flash GSIs with this recovery.

bro plz make custom rom for yu ace 2gb varient plz plzz
:good::good:
Naveen56 said:
Team Win Recovery Project (TWRP) is an open-source software custom recovery image for Android-based devices. It provides a touchscreen-enabled interface that allows users to install third-party firmware and back up the current system which are functions often unsupported by stock recovery images. It is, therefore, often installed when flashing, installing, or rooting Android devices, although it isn't dependent on a device being rooted prior to installation.
In my view you have already enabled Developer Options and unlocked bootloader. Also you have ADB drivers installed.
Note: This is not a port and the recovery is built from Omni Source. So you will not faces any issues (atmost). Everything you do to your smartphone is your responsibility and we (and I) are here to help you if something goes wrong. Follow instructions properly to customize your device.
Download:
https://drive.google.com/open?id=1T09QkNcDSe0mp7EjjMSK1aoc8303DjAI
Instructions:
1. Download the Unofficial TWRP. Open Command Prompt (CMD) or Terminal and connect your mobile to PC using USB cable.
2. Enable USB Debugging, then type the below command and hit enter.
Code:
adb reboot bootloader
3. Use the below command if your device is recognized in the fastboot mode by issuing below command:
Code:
fastboot devices
If your device is not recognized then disconnect and reconnect the cable properly.
4. Now flash the img file you have downloaded from the link above and it is named as TWRP_recovery.img, use below command.
Code:
fastboot flash recovery TWRP_recovery.img
5. It takes few seconds to flash and after that you can enter Recovery mode by using below command.
Code:
fastboot oem reboot-recovery
6. It takes 5 - 10 sec at TWRP main screen and you need not worry about that.
7. TWRP will ask for Decryption password. Tap on cancel.
8. You have to Format Data if you want to access Internal Storage.
9. You have to flash Magisk if boot.img is not patched(I can extend this thread on this on user request).
10. To take back-ups you first need to Forma, otherwise TWRP won't work to its potential.
Happy TWRPing.
Working:
1. OTG will recognize.
2. You can push or pull files between smartphone and PC.
Issues:
You can post them here.
Need:
1. I need one or two testers to check whether this recovery is working (for me it is working) to its full extent and can flash GSIs.
2. I have unlocked this device long ago so I forgot the command used earlier. Anyone of you can share that command to help others and also I will extent this thread from unlocking to flashing GSIs. (I know 3 commands but don't know which one I used)
TWRP Version: 3.3.1-0
Made by: Me
Thanks to:
YU Team,
TWRP Team,
XDA Team.
Build Date: 21 Oct, 2019
Status:
Beta (If I get testers then it will change to Stable)
Thread Created: 21 Oct, 2019
Last Updated: 21 Oct, 2019
Click to expand...
Click to collapse

kumardeepaksahu said:
:good::good:
Click to expand...
Click to collapse
You can try GSIs. They are working fine. Actually this phone is not mine and kernel source is not available too.
Tip:
Android 10 GSIs are booting up (if you flash) but they are unstable.
Android 9 GSIs are fine. You can use either AOSP or Descendant. They are working good.

How to root yu ace do you have any idea

rupeshmourya said:
How to root yu ace do you have any idea
Click to expand...
Click to collapse
You can follow guide from this post.

My device is not detecting in adb, some times detects while phone is on, but in fastboot it is not detecting, do you know how to connect adb in fastboot mode.

rupeshmourya said:
My device is not detecting in adb, some times detects while phone is on, but in fastboot it is not detecting, do you know how to connect adb in fastboot mode.
Click to expand...
Click to collapse
Check if you have enabled USB debugging from Developer Options, also you have to select USB File Transfer (not charging) when it prompts for USB Configuration.
If that does not work then reinstall ADB and Fastboot drivers.
Atlast try changing the USB cable.

Naveen56 said:
Check if you have enabled USB debugging from Developer Options, also you have to select USB File Transfer (not charging) when it prompts for USB Configuration.
If that does not work then reinstall ADB and Fastboot drivers.
Atlast try changing the USB cable.
Click to expand...
Click to collapse
It is connected while phone is on but in fastboot mode it is not detecting device. I already enabled usb debugging. And selected usb file transfer.

Plz give me corrects drivers for usb vcom preload and usb driver for windows 7.

rupeshmourya said:
Plz give me corrects drivers for usb vcom preload and usb driver for windows 7.
Click to expand...
Click to collapse
Why do you need them?
Latest Windows 10 update is enough.

I dont have win 10

rupeshmourya said:
I dont have win 10
Click to expand...
Click to collapse
Then either download Windows 10.
Tip: Windows 10 is still available to download for free from microsoft site. You can look into it.
Or
Download those drivers from a well known source.
You didn't even mention why those drivers are for?

Naveen56 said:
Then either download Windows 10.
Tip: Windows 10 is still available to download for free from microsoft site. You can look into it.
Or
Download those drivers from a well known source.
You didn't even mention why those drivers are for?
Click to expand...
Click to collapse
Those drivers are for connecting yu ace to pc in fastboot mode, my device is not connecting to pc in fastboot mode. I can not issue command in adb for flashing twrp. Adb not detecting my yu ace.

rupeshmourya said:
Those drivers are for connecting yu ace to pc in fastboot mode, my device is not connecting to pc in fastboot mode. I can not issue command in adb for flashing twrp. Adb not detecting my yu ace.
Click to expand...
Click to collapse
Keep your OS upto date and properly download and install ADB drivers.
And you dont need vcom drivers for ADB to work.

Naveen56 said:
Keep your OS upto date and properly download and install ADB drivers.
And you dont need vcom drivers for ADB to work.
Click to expand...
Click to collapse
My adb is working while the mobile is turned on but in fastboot pc not detecting my ace.

rupeshmourya said:
My adb is working while the mobile is turned on but in fastboot pc not detecting my ace.
Click to expand...
Click to collapse
Try another PC.
Or
check if you are in recovery or fastboot mode.
If adb commands are working then fastboot mode commands will also work.
Or
Download ADB drivers from official source (Google Developers site).

How to unlock bootloader..does OEM unlock command is enough for that?.. Also can you give me the links of the gsi roms

JEEVAMYIL said:
How to unlock bootloader..does OEM unlock command is enough for that?.. Also can you give me the links of the gsi roms
Click to expand...
Click to collapse
First enable the option OEM Unlock from Developer settings.
Then enter into fastboot mode. You can use either
Code:
adb reboot bootloader
or power off and press Power Button + Volume Down. Now you will be in fastboot mode.
Use oem unlock command (I forgot this so cannot share) and you are done.
You can get GSIs from here.
Note: ADB tools must be installed in your PC (PC is must). If you unlock your phone then it will erase all the data so do take a backup before proceeding.

[RECOVERY][TWRP][BV9100] TeamWin Recovery Project for Blackview BV9100

{
"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 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. 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.
This is a customised version of TWRP specifically for the Blackview BV9100!​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now voided.
*
* I am not responsible for bricked devices, a meteorite crashing into your house,
* dead SD cards or thermonuclear war, YOU are choosing to make these modifications,
* and if you point the finger at me for messing up your device, I'll just ignore you.
*
*/
What works?
* Basic functions (Boot, Touch, ADB, Mount (internal/external), etc)
* Data decryption
What's broken?
* You tell me.
IMPORTANT - Disable dm-verity with the following fastboot command, or the recovery won't boot!
Make sure you use the vbmeta.img from stock rom!
Code:
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
Downloads
Click here!
Device sources
Need help?
BV9100 Telegram Community

TWRP 3.5 - 28/02/2021
Download
Changelog:
Spoiler: Changelog
- Sync with latest TWRP changes
- Update encryption blobs
- Fix MicroSD/OTG mounting issue

Reserved #3

@bengris32
works but im unable to mount micro sd nor a usb stick in exfat nor making 2 partitions on one use (over 32gb) in 16k partitions less than 32 gigs.
may i ask how or where did you obtain the file?

mexamilian said:
@bengris32
works but im unable to mount micro sd nor a usb stick in exfat nor making 2 partitions on one use (over 32gb) in 16k partitions less than 32 gigs.
may i ask how or where did you obtain the file?
Click to expand...
Click to collapse
I didn't "obtain" the recovery, I made my own device trees for it, and built it from source.
As for the sdcard/usb mounting issue, I'll look into it.

@bengris32
Thanks for share
I noticed you are using BV9100_EEA_M860A_V1.0_20200430V19 in source files Where can i get BV9100 latest FW for non-EEA(non EU vs). Im on NON-EU version *NON-EEA* - notEU_BV9100_M860A_V1.0_20190910V2. Cant get my hands on their latest OTA updated FW. Maybe that's my problem? Does it even matter if its EEA on non EEA i mean they both run on same mk6765 platform.
There are 2 files i could find from official source, EU and non-EU versions, can be found here https://bbs.blackview.hk/viewtopic.php?t=532355 (version 20190910V2) kinda old but there is also the latest FW that goes OTA after u check for FW updates on bv9100. Blackview did not provide more recent updated one. Been working at it since Wednesday spending pretty much whole days figuring this out and back at it again atm

Not seeming to get this to work, but I'm not sure I know what I'm doing.
I took careful notes about what I did, anything look wrong wih the process?
First boot
► minimal set up then enable developer mode
(Settings 🞂 System 🞂 Advanced 🞂 About phone
▻ tap on "Build number" until unlocked, maybe 8 times
unlocks "Settings 🞂 System 🞂 Advanced 🞂 Developer options" menu
)
► In Developer options menu
▻ Select OEM unlocking (enter system password / pin)
▻ Turn on USB debugging (without cable attached)
► Connect USB cable
► On computer: "adb devices"
► On phone "Allow debugging" prompt comes up, allow it
► On computer: "adb devices"
▻ shows device "BV9100NEEA000..."
► Disconnect USB cable
► Power off phone
► Power on phone with volume down button pushed
► Connect USB cable
► On computer: "adb reboot bootloader"
► On computer: "fastboot devices"
▻ shows device "BV9100NEEA000..."
► On computer: "fastboot flashing unlock"
▻ computer shows "(bootloader) Start unlock flow"
▻ phone shows tiny text prompting for push volume up to allow
▻ push volume up
▻ computer shows "OKAY [ 23.545s]" (and some other stuff)
► On computer: "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img"
▻ using vbmeta.img from blackview forum link in post 6
▻ computer shows (about) OKAY ... sending ... OKAY ... writing ... OKAY
► On computer: "fastboot flash recovery recovery.img"
using recovery.img 3.4.0 linked from first post
▻ computer shows (about) OKAY ... writing ... OKAY
► On computer: "fastboot reboot"
▻ computer shows "rebooting..."
▻ phone shows tiny message about unlocked bootloader and delays boot 5 seconds
► Phone boots back into new system wizard
► Re-enable dev mode and reallow USB debugging
► On computer: "adb reboot recovery"
▻ seems to boot into an Android standard recovery, not TWRP
► Phone regular boot shows nothing different

neccowafer said:
Not seeming to get this to work, but I'm not sure I know what I'm doing.
Click to expand...
Click to collapse
What model of phone and FW are u running. I know u posted " BV9100NEEA000" but do u have the right FW on it that came witht he phone? There are 2 versions of this phone also FW files on official site are not updated to latest OTA update. Official FW for eu and non eu can be found here, but its old.
https://bbs.blackview.hk/viewtopic.php?t=532355 You can flash the older FW back and try again. If u have the original hardware FW on ur EU model phone then it could be possible for you
Ive made a post asking for the files, my message needs to be approved as a new registered user. You can bookmark the link below and wait for my post to appear and the files when and if they provide em.
official firmware - Page 2 - bbs.blackview.com
bbs.blackview.hk
Currently i reverted back to latest OTA stock FW till i get those new files.
I am at a standstill on the proper order to root and get twrp on this non eu model phone.
Magist guide says i need to flash to recovery partition (u need original to patch which i cant have without TWRP on the phone in the 1st place) Then there is another issue of getting TWRP onto the device before rooting which again u need the original vbmeta.img, i can do with a blank one but the problem comes to TWRP then setting an encrypted password provided by bengris32 which his twrp is for EU model of the phone. Headache
I'm on non EU FW, BV9100_M860A_v1.0_20200722V3
You can get SP Flash Tool thats needed to flash this phones FW, here https://spflashtool.com/ which has the latest version shown as V5.1924. There is also v5.2044 which i dont know how and where it came out, can be found here https://forum.hovatek.com/thread-13970.html @Hovatek seems reputable after me digging around for the past 3-4 days https://forum.xda-developers.com/m/hovatek.5636663/
Assuming you have MTK Drivers installed. if not https://forum.hovatek.com/thread-16640.html or find official site.
Open up SP Flash Tool,
Go to tab Download
Point Download Agent to where SP Flash Tool is installed to the file "MTK_AllInOne_DA.bin"
Load up you FWs scatter file in the 2nd box/line "Scatter-loading File.
***IMPORTANT! In the graph table below MAKE SURE U UNCHECK the preloader box. This will help getting TWRP as recovery later on.****
Klik box up top with green arrow that says "Download"
Phone is in off state.
Attach your USB cable to the phone, but NOT to the computer yet.
Hold VOLUME UP & DOWN at the same time then connect it to the PC.
On the SP Flash Tools you will see a long white bar on the bottom of the softwares window
It will turn RED then Yellow and will start flashing your phone.
You can RELEASE KEYS after you see the RED COLOR.
Once SP Flash Tools is done flashing a box will come up and say Done.
Close box, close SP Flash Tools.
Disconnect Phone from PC and Phone and u are on stock FW.
If u didnt uncheck the "preloader" box TWRP will not work on your phone

mexamilian said:
I'm on non EU FW, BV9100_M860A_v1.0_20200722V3
Click to expand...
Click to collapse
That's the same as mine: BV9100_M860A_V1.0_2020722V3, so I guess I'm waiting on BV to respond to your firmware update request.

neccowafer said:
Not seeming to get this to work, but I'm not sure I know what I'm doing.
I took careful notes about what I did, anything look wrong wih the process?
First boot
► minimal set up then enable developer mode
(Settings 🞂 System 🞂 Advanced 🞂 About phone
▻ tap on "Build number" until unlocked, maybe 8 times
unlocks "Settings 🞂 System 🞂 Advanced 🞂 Developer options" menu
)
► In Developer options menu
▻ Select OEM unlocking (enter system password / pin)
▻ Turn on USB debugging (without cable attached)
► Connect USB cable
► On computer: "adb devices"
► On phone "Allow debugging" prompt comes up, allow it
► On computer: "adb devices"
▻ shows device "BV9100NEEA000..."
► Disconnect USB cable
► Power off phone
► Power on phone with volume down button pushed
► Connect USB cable
► On computer: "adb reboot bootloader"
► On computer: "fastboot devices"
▻ shows device "BV9100NEEA000..."
► On computer: "fastboot flashing unlock"
▻ computer shows "(bootloader) Start unlock flow"
▻ phone shows tiny text prompting for push volume up to allow
▻ push volume up
▻ computer shows "OKAY [ 23.545s]" (and some other stuff)
► On computer: "fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img"
▻ using vbmeta.img from blackview forum link in post 6
▻ computer shows (about) OKAY ... sending ... OKAY ... writing ... OKAY
► On computer: "fastboot flash recovery recovery.img"
using recovery.img 3.4.0 linked from first post
▻ computer shows (about) OKAY ... writing ... OKAY
► On computer: "fastboot reboot"
▻ computer shows "rebooting..."
▻ phone shows tiny message about unlocked bootloader and delays boot 5 seconds
► Phone boots back into new system wizard
► Re-enable dev mode and reallow USB debugging
► On computer: "adb reboot recovery"
▻ seems to boot into an Android standard recovery, not TWRP
► Phone regular boot shows nothing different
Click to expand...
Click to collapse
Hi, this is because android restores the original recovery when the device boots, you must not let your device boot into android until you boot TWRP for the first time, repeat all of your steps, but when you "fastboot reboot", hold the volume up button to access the boot menu, then select recovery mode. Once your device boots into TWRP, it will automatically patch the rom to prevent the original recovery from being restored on boot up.

bengris32 said:
Hi, this is because android restores the original recovery when the device boots, you must not let your device boot into android until you boot TWRP for the first time, repeat all of your steps, but when you "fastboot reboot", hold the volume up button to access the boot menu, then select recovery mode. Once your device boots into TWRP, it will automatically patch the rom to prevent the original recovery from being restored on boot up.
Click to expand...
Click to collapse
I confirm on my non EU bv9100 M860A
kept holding like you said then typed fastboot reboot and still held a selection menu popped up with 3 option on black background, i released the key then selected recovery, pressed the vol down to accept then quickly release it and went back to holding volume up and son of the devil it worked thanks, now i go back to messing with magisk installation.
Question though,
once booted into recovery following what u just said above, should vipe data factory be done like other (lineageOS) require or not? if it work it works just maybe thats where i had my issue with no mount for microsd and external
@neccowafer i can link you the official FW so u can flash what i have?
Latest stock rom link of BV9100 - bbs.blackview.com
bbs.blackview.hk
get the non-EEA version and flash it follow your own steps you mentioned
EDIT: Just did wipe data button bottom right on button [WIPE] then did factory wipe.
How access to internal and MTP on reboot into recovery with buttons, still can get micro sd mount

Got a reply from official blackview admin
official firmware - Page 2 - bbs.blackview.com
bbs.blackview.hk
looks like there wont be any updates to A10 and over. Gonna be trying out different CFW and see how it does, i managed to get unofficial lineage-17.1-20201215 unofficial with test keys flashed

I just got one of these phones today and I'm having a bear of a time getting into it with adb to install TWRP and hopefully flash a new ROM. I tried to follow the detailed instructions from neccowafer (thank you for those!) earlier in this thread, but adb returns the device as unauthorized when in recovery mode.
This phone seems to have two recovery modes. One is accessed by booting while holding vol-down and the other is loaded when you boot holding vol-up and choose recovery from the menu.
In either recovery mode, I run adb devices and get
List of devices attached
BV9100EEA00016800 unauthorized
While booted to Android, I run adb devices and get
List of devices attached
BV9100EEA00016800 device
I'm becoming a bit frustrated trying to figure it out on my own, and it's been a few years since I did any custom bootloader or custom ROM stuff with Android, so any help would be very much appreciated.

@JeffJK I have factory mode on my down key and recovery mode on up, you wanna do up. my model is NEEA

mexamilian said:
@JeffJK I have factory mode on my down key and recovery mode on up, you wanna do up. my model is NEEA
Click to expand...
Click to collapse
Oh good to know! I got the same error noted above in the up key mode, the unauthorized thing from adb. Any idea why?

did u enable dev mode then enabled usb debugging, boot loader unlocked?
when u got ur phone out of the box, skip everything and dont sim in, just skip things, make sure u dont set any pass and dont encrypt device, enable dev mode then enable debugging by tapping on ur build in settings all the way on bottom in about. make sure oem unlock is also enabled and greyed out if u done already so.

mexamilian said:
did u enable dev mode then enabled usb debugging, boot loader unlocked?
when u got ur phone out of the box, skip everything and dont sim in, just skip things, make sure u dont set any pass and dont encrypt device, enable dev mode then enable debugging by tapping on ur build in settings all the way on bottom in about. make sure oem unlock is also enabled and greyed out if u done already so.
Click to expand...
Click to collapse
Ah, I did set the phone up. Should I wipe and start over?
EDIT: I did a factory reset and booted into Android to turn on debugging, and even without setting up anything on the phone, encryption was enabled in the security settings and adb still lists the device as unauthorized while in recovery mode.
EDIT 2: Also tried wiping /data from the recovery mode menu, which put out the below lines but still did not allow adb access even after a kill-server
Code:
Formatting /data. . .
Formatting /cache. . .
Formatting /mnt/vendor/nvdata. . .
Data wipe complete.

@JeffJK To remove encryption meaning you had twrp installed and made it work or stock os?
Boot into recovery Format data / factory reset This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
*DONT set any passwords for lockscreen, dont login to google, pay attention to not encrypt device when setting up. just basic skip u dont even need wifi or sim in phone
Dont forget to unlock ur bootloader before flashing or doing anything. Follow post #7 thats exactly how you would do it then read up on post #10 and #11 and it will work.
Also did you install USB drivers?
Get android usb drivers https://developer.android.com/studio/run/win-usb
if that didnt work try the one below,
https://forum.hovatek.com/thread-16640.html (need to register) you want the " Auto Mediatek USB VCOM Drivers Signed"
If you messed up you just flash your legit FW back to stock and follow post #7 10 and 11

mexamilian said:
@JeffJK To remove encryption meaning you had twrp installed and made it work or stock os?
Boot into recovery Format data / factory reset This will remove encryption and delete all files stored in the internal storage, as well as format your cache partition (if you have one).
*DONT set any passwords for lockscreen, dont login to google, pay attention to not encrypt device when setting up. just basic skip u dont even need wifi or sim in phone
Dont forget to unlock ur bootloader before flashing or doing anything. Follow post #7 thats exactly how you would do it then read up on post #10 and #11 and it will work.
Also did you install USB drivers?
Get android usb drivers https://developer.android.com/studio/run/win-usb
if that didnt work try the one below,
https://forum.hovatek.com/thread-16640.html (need to register) you want the " Auto Mediatek USB VCOM Drivers Signed"
If you messed up you just flash your legit FW back to stock and follow post #7 10 and 11
Click to expand...
Click to collapse
I couldn't get TWRP because adb still reads the device as unauthorized. I wiped the data while in recovery mode, booted to the"Welcome" screen, and when I skipped everything in the setup wizard, the settings still show encryption as enabled, and I had no option to enable or disable it at any point. Bootloader also still showed as unlocked. This seems like a very unusual problem! I have drivers but will try the vcom ones.

if u are able to get into adb and fastboot then u dont need the VCOM drivers.
On device use "Revoke USB debugging authorizations" in "Developer Options"
then reconnect to phone to cable then pc
@JeffJK
Would you do me a favor, my current connected device sn is 123456789ABCDEF.
I messed up with flashing some roms and wiped the nvnand partition without making a backup of official stock one( didnt know about nvnand till issues started happening), been working on fixing S/N and device connected via adb to stock, currently have tee key and google key in red as overlay, i know ways of getting rid of it but id rather have the original back.
need some structural info, you can replace last 5 number from your serial with XXXXX if u want. i have some files i managed to scrape up digging around on how tos, just clueless on how to get tee key/google key and serial back onto device with proper format.
go into your phones setting>system>advanced>About phone. Post what what you see in the following:
*SIM Status (sim slot 1) klik on in and scroll down to EID (mine says unknown) and post (hide last 4 or so numbers but include full length) i will need to know what to look for when flashing mine back to my phones original status
*Model & Hardware klik on it my says for Model: BV9100 Serial number says 0123456789ABCDEF (again hide last 4 or 5 so i have an idea of what i need to look for in my files)
*WI-Fi MAC address and Bluetooth address all i need from this is do they match or are different, also post last 2 digits/bits in wifi and bt addresses ( i need this for to figure if multicast)
I REALLY RECOMMEND you write this info down before messing with roms and flashing or ull end up like me with blank IMEI (managed to flash fix it), serial of 123456789ABCEDF(still cant fix), and a permanent tee key google key in red(still cant perma fix, have to always remove factorymode). you can watch tutorials on how to use "Mtk Droid Tool to backup your nvnand IMEI serial, make a scatter file on updated OTA latest update of stock BV9100 rom (its really well optimized after trying Lineage unofficial 17.1, HavokOS 3.12 (I have files and sources)
I do not know where the official source for MTK DROID TOOLS is (the latest version i have found is Mtk_Droid_Tool_v2.5.3B some say 2.5.3 I have both if needed source to https://forum.hovatek.com/thread-15665.html) (bitdefender total security says clean on my pc before i installed, it does run sluggish on 10850k with 128gigs ram on nvme) I do recommend u scan with your AV and upload it also to https://www.virustotal.com/gui/ and any other files you get just do be safe
Heres a little write up on how to do so as i cannot cause my phone doesnt have proper setup on stock after a mess up
"
Requirement : Your Google android device should be rooted.(Officially provided with source if u need, DONT root it via the mtk droid tools, there is an option. Go with magisk official https://github.com/topjohnwu/Magisk/releases/tag/v21.2 After you have TWRP installed from this thread, download the 21.2 magisk zip file and install inside twrp reboot and configure it)
Download and open MTK droid tools application.
Enable USB debugging mode on your device. Settings > Developer Option > Click USB debugging mode.
SKIP THIS UNLESS YOU HAVE ISSUES(let me know)Then connect your android smartphone to the computer. Your device will detect by MTK droid tools within few minutes. If your mobile phone is not detected, then you have to install USB drivers on your device first. Right click on the “InstallDriver.exe” and select “Run As Administrator” and then restart your computer to install USB driver.
Click IMEI/NVRAM to backup android IMEI and then click backup. Your android backup will be stored in BackupNVRAM folder.
Continue to the backup system, firmware, data and etc (Android ROM) select on Root, backup, recovery tab and backup tab. The process will finish within few minutes.
"

[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