Related
!!! 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.
{
"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've been successful at porting over TWRP (Team Win Recovery Project) Recovery to the Pioneer XDP-300R Digital Audio Player! The recovery can be flashed directly over the stock recovery using Fastboot, or you can temporarily boot into it using fastboot.
First off, TWRP, replaces the stock recovery and allows users to backup and restore system, data, boot and other partitions on their player onto their storage or sdcards. It also can install superuser (root) access if you want that feature to allow editing and modifying of the system folder. That opens the door for additional mods.
You can also install Magisk, which is a systemless root feature that is a little safer since it does not touch your system folder, but instead patches the bootloader and then creates a layer above system that stores the mods and changes within the Magisk system in.
First off, I made system image, bootloader and recovery images of the stock 300R prior to going into this full swing. I had already rooted my device using Kingoroot but this is no longer needed and is much more safe now.
So you'll want to get the recovery first.
https://drive.google.com/open?id=1diqQ8LE-yG4b-WZFB_OPcQp2rDUp9BbV
The link in my google drive will take you to a folder where I have backups of my images. The TWRP recovery is located in the Recovery folder, along with the stock Recovery image.
Tools Needed:
Android USB drivers for ADB and Fastboot
ADB and Fastboot
Terminal or Command Prompt
Some basic knowledge on how to use these tools
Pre-Installation:
In android, go to Settings, and turn on Developer Mode. To do this, click Settings, then Device Information, then scroll to Build Number. Tap this several times until you unlock Developer Options.
Now, go back to the Settings Menu and go to the new Developer Options menu. Check the OEM Unlocking option to allow the bootloader to be unlocked.
Installation of TWRP:
1. Download the TWRP image and place it in the same folder as ADB/Fastboot tools.
2. Open a terminal or cmd prompt window and go to the folder in (1)
Code:
EXAMPLE: cd /android
3. Turn off the 300R. Then hold next track (the button closest to SD slots) and press power and let go while holding the next track button. A Penguin will appear on screen. Then let go, and plug device into computer.
4. In terminal, check to see if fastboot works.
Code:
fastboot devices
5. If it does not show a device, check your drivers! If you see a device, let's go forward!
6. Now we will install the recovery.
First we need to unlock bootloader:
Code:
fastboot oem unlock
If you are nervous, and want to verify it works, you can do a temporary test by typing the command:
Code:
fastboot boot TWRP-XDP-300R.img
This will boot directly into the TWRP recovery and will go away when you restart. But you can see if it works this way and mounts each folder correctly.
If you're ready to take the plunge, use this command:
Code:
fastboot flash recovery TWRP-XDP-300R.img
7. Once it flashes, you can always reboot into recovery by powering off. Then holding PREV TRACK (button closest to power) and power on. It'll show the penguin, and then load recovery soon after.
8. Once you see the TWRP screen youre good to go! I recommend making a System, Data, and Boot backup immediately so you have it ready. I also have the stock recovery in the folder for backup purposes too!
Root Access
When you exit TWRP, you have the option of installing SuperUser (root) access. You're welcome to install or decline it. I recommend using Magisk at this point, by looking up Magisk Manager and loading that onto your device. It'll also provide root access along with other goodies like Xposed, some adblocking stuff, and if you like, Viper4Android, and other mods.
To first start the process of Magisk, you need to unlock the bootloader. Go into Fastboot mode again on the phone, as described above, and go to command prompt:
Code:
fastboot oem unlock
This command will unlock the bootloader. In the future, you can lock it by replacing unlock with lock: fastboot oem lock
Magisk only installs correctly when you use the magisk zip file that can be downloading through Magisk Manager. This zip file needs to be flashed in TWRP Recovery. Once you do that, it'll patch the bootloader and allow Magisk to work correctly. You can verify by opening Magisk Manager in Android, and seeing if it is activated.
Once activate, you can click the menu on the left side of the Manager app, and click DOWNLOADS to find a list of modules available for use. Not all are compatible with the older Android Lollipop that is on XDP-300R, so be careful of that.
Magisk Modules
Some modules I use are:
Xposed Framework - another modding system - see below
LKT - tweaks to the kernel for battery management
Magisk Manager for Recovery Mode - Recovery command line manager (seems buggy)
SafeMode4Magisk - Boots into safe mode for disabling bad modules
Swap Torpedo - Optimizes Swap files for RAM management
Youtube Vanced - Themes and removes ads from Youtube
Greenify - adds additional features to Greenify app
Xposed Framework (now systemless using Magisk!)
Some modules I use are:
Amplify - Standalone app that needs Xposed for disabling or reducing amount of system wakelocks and alarms which greatly save battery life
Greenify - Standalone app that hibernates unused apps to save battery life and uses Xposed for additional features
Youtube AdAway - Removes ads from Youtube
BUILD.PROP MODS
The Drive Link at the top of this page has my modified build.prop in it. You can replace your existing build.prop with this if you want. Make sure you make a backup just in case!
Diverting sound away from Android OS to the DAC:
Open up BUILD.PROP in /System in your android device and look for PCM Offload
There are two lines there, that start with audio.offload...
Remove the Hash in front of each of them if they are present and that's it!
it should read:
Code:
#PCM offload
audio.offload.pcm.16bit.enable=true
audio.offload.pcm.24bit.enable=true
Also verify that this is enabled:
Code:
av.offload.enable=true
Hi ! Thank your for your work ! There are a version for the XDP-100R please ?
(sorry for my bad english)
HI, I'm thankful for your development. But is there any chances to reflash the firmware if something goes wrong?
A few days ago on my xdp300r part of the system spilled out and actually are system applications. Nothing can be installed on it, is there any possibility of restoring the original state? Restarting and recovery mode unfortunately did not help.
Thanks alot. I needed this so bad. A long time after I bought XDP300R I can only dare to use superSU to get root access and that's it. And now xposed and magisk are possible, Thank you soo much.
Hi thanks. I managed it fine. I used su as majisk would not install. Luckily I followed your advice and made a backup(I don't usually bother). I installed your build.prop and the pioneer would not boot. I have restored using twrp and changed my own build.prop so alright now. Thanks.
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
gavroche33 said:
HI GUYS.
I am trying to unlock my 300R.
When I execute 'fastboot oem unlock' I got DENIED message.
I am stuck. Is there any hope for my player?
Daniel
Click to expand...
Click to collapse
have you enabled the OEM unlock in the developer setting?
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Grazie mille per il tuo lavoro
gavroche33 said:
I do not have option like that. My player was cleared from data, but it is still locked. I cannot OEM unlock it
Any other way?
Daniel
Click to expand...
Click to collapse
Go to setting, to Device Information, to Build Number. Tap 7 times. You get Developer Options
Back up go to Developer Iptions, select OEM Unlocking.
Re-do OEM unlocking as described in OP
Hi,
I tried to follow this tutorial but my device is not show I checked the drivers!
But still the same, is it possible to had any help ?
Since we already have an open bootloader, is there a chance to make a newer android, I propose version 9 because in newer ones you lose the ability to play some formats, it would certainly give a second life for this model
Dear XDA forum readers/members,
I have an issue with my Pioneer XDP-300R. At this stage I can only boot into it with the TWRP (TWRP-XDP-300R.img) image provided in the first post. I also have downloaded the recovery files, including the (stock?) system image (system-noxposed.img).
When I try to flash the same image from within TWRP, I can only select the "boot" or "recovery" partitions. In this screen, there is no option to boot towards a "system" partition.
If I boot from a ZIP file containing the system-noxposed.img file, I obtain either a different error which complains about a META-INF and binary not found? , or I obtain an error which (of course) writes there is too little space to write a system image in a boot or recovery partition.
My question(s) is/are: Is there any method to flash a system image towards the system partition from within TWRP, and/or how to solve the "unknown chunk type" error?
Any help would be greatly appreciated.
EDIT: The issue has been solved, but there is another problem now. When the device would not boot TWRP anymore (as in: froze at TWRP logo) I decided to look at the partitions (with dd): Now, I had made the mistake of overwriting the very first boot partition, and now the device will not power up anymore. By all means and purposes, he is hard bricked now If there is anyone who would like to help, I'd be very grateful, assuming there are still options left.
Greetings from a new member in need of help
{
"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"
}
TWRP 3.3.1 + Root
This topic is the result of work mehanik6 (4PDA) my greetings to him
Tested on Android 9
1 - Remember that everything you do, you do at your own risk
2 - to install TWRP, we will have to unlock the bootloader, all data will be erased, Your device becomes out of warranty
3 - the you need to be installed adb driver For connecting your device to a computer (15 Second ADB Installer v1.5.3.zip)
How to install Best Android ADB Driver on your computer
How to Install Google USB Driver for Windows | ADB and FastBoot
installation
- download the archive delete_verity_key.zip without unpacking put on the sdcard (Attached file) delete_verity_key.zip (130.56 KB)
- download file Fix_vendor.zip without unpacking on the sdcard (Attached file) Fix_vendor.zip (347.64 KB)
- download file Magisk-v20.1.zip without unpacking on the sdcard (Attached file) Magisk-v20.1.zip (5.22 MB)
- download file adb.zip. unzip to your computer desktop adb.zip (22.02 MB)
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
-Enable “OEM Unlocking”
GO to Settings > Developer options on your Android device and enable the OEM Unlocking option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- allow unlocking of the bootloader
- Decompress a folder adb.zip
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
- copy and paste command [adb devices] (Check Device by Sending below Command)
Example of making sure to connect to the phone
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
If the device does not recognize the phone, it is on "fastboot" android adb interface
Installing [Google ADB Drivers] To Windows 7/8/8.1/10/XP/Vista
- download file Google ADB Drivers.zip
- unlock the bootloader
4
Code:
fastboot flashing unlock
- on the screen text appears, press the Volume + button (all data will be erased)
Attention
The following files(fileFix_vendor.zip+delete_verity_key.zip+Magisk-v20.1.zip) must be placed in an external card, because all phone data will be deleted
Then long press buttons (Power) to turn off the phone
- The bootloader is unlocked. You should see the Orange State (text).
Then turn ON the phone
one more time
- Enable developer options in Android
GO to Settings > Swipe down and tap on About Phone Keep tapping on the build number for 7 times
-Enable the USB debugging option
GO to Settings >System -> Developer options on your Android device and enable the USB debugging option.
when you plug the device into an PC, it will prompt you to allow USB debugging (as seen in the screenshot below).
- Open a command prompt inside a folder adb. right mouse button l menu, select to open a command window
1
Code:
adb devices
2
Code:
adb reboot-bootloader
3
Code:
fastboot devices
- Sew vbmeta.img (the error does not pay attention)
4
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
5
Code:
fastboot flash recovery recovery.img
-After completing:
*Long press buttons (Power) to turn off the phone And quickly Boot into TWRP (buttons Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRP
Changes will not be saved language and settings in (TWRP) Only after all stages have been completed
- Back to the section mount
And put a tick next to all sections on which are placed
- go to the section wipe
- click Format the Data
- In the terminal, Type "yes" and confirm (format action) by click the check mark in the lower right corner
- then you need to reboot again in TWRP
Boot into twrp buttons (Power + Volume Up )
By pressing the volume up selects: recovery mode
and pressing the( volume down) to start TWRPone more time
- Go to the section mount
And put a tick next to all sections on which are placed
Back to install
- Flash archive delete_verity_key.zip
- Flash archive Fix_vendor.zip
- Flash archive Magisk-v20.1.zip (Data again to not encrypt)
- Restart the phone
Like everything, use
NEXT
[GUIDE] CUBOT X19
I just rooted my phone and this guide was very helpful.
- After formatting your phone, boot into recovery through TWRP as my phone keeps bringing up the "no command" error screen if I use "Vol Up + Power"
- When that happens, hold power button for 10 secs, your phone will either turn off or reboot, flash TWRP again and continue.
Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.
Having issues: At the top of the screen its written in red letters as overlay: "TEE key not write Google key not write"
I already applied the "fix Orange state" fix.
Any ideas?
Actually I am using a CubotX19 S and finally I went back to stock rom. That fixed the issue.
However, when I flashed Stockrom I noticed at loading of MT6763 scatterfile, that there are 2 sections having "tee" in their names (see screenshot).
Maybe it would be enough to just flash one or both of those two sections.
I did not do any further research, but maybe this hint os of help for others .
BTW: my screenshot says "Download only" in the Droplist. Actually I flashed using "Firmware Upgrade"
best regards,
bul
where do i get the vbmeta file from?
brezzz said:
where do i get the vbmeta file from?
Click to expand...
Click to collapse
recovery.img + vbmeta.img in folder adb.zip above
or https://www.mediafire.com/file/owuv9h2444w264y/adb.zip/file
flashing vbmeta failed "this partition doesnt exist"
kusti420 said:
flashing vbmeta failed "this partition doesnt exist"
Click to expand...
Click to collapse
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
karim.a said:
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
hmm, i tried it just like it said, still cant see a vbmeta partition
karim.a said:
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
View attachment 5188523
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
also i saw someone say that this vbmeta is android 9 thing, but cubot x19 came with android 8.1, should it even have the vbmeta partition? how could i create that partition?
My friend kusti420, follow the instructions below, including upgrading the phone to Android 9 . If your phone has a android 8
Try the following at your own risk
You might have a problem partitioning the phone memory
format your phone
flash your phone
select : format all + download
the latest firmware for CUBOT X19 upgrade 2020-04-21
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.
I tried to flash vbmeta, but it did not do anything.
chartek1 said:
For one reason or another, my serial number of my phone is 0123456789ABCDEF and I can't flash the recovery, neither boot from it, nor flash the modified firmware with it.
Click to expand...
Click to collapse
How to find phones serial number or IMEI number
Step 1. Open the Phone app.
Step 2. Dial *#06# on the keypad.
Step 3. Details about your devices IMEI and serial number will automatically appear on the screen.
chartek1 said:
I tried to flash vbmeta, but it did not do anything.
Click to expand...
Click to collapse
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Trash, description on two pages, but no link to TWRP, much to do, nothing to get from./translate/
user132 said:
Successfully Installed TWRP 3.3.1 with SP tool what is did After selecting scatter file from stock firmware i replaced the stock recovery and edit the partition size in the scatter fie for recovery and changed the default path from sp tool default was Recovery-verified i switch it to the Recovery.img that i replaced it with.
Click to expand...
Click to collapse
How do i adjust the file?
karim.a said:
format your phone
flash your phone if model number CUBOT X19
the latest firmware for CUBOT X19 upgrade 2020-04-21
select : format all + download
format your phone
Then try again according to the instructions in the next topic
TWRP 3.3.1 + Root CUBOT X19
Click to expand...
Click to collapse
Should I tick the preloader? I have heared that it might brick the device.
chartek1 said:
Should I tick the preloader? I have heared that it might brick the device.
Click to expand...
Click to collapse
I tick the preloader? NOIf the current Firmware (Stock ROM) for the phone is android 9Instructions to InstallCharge the device battery up to 50%
Make sure you follow and download all the required files and flash tools on your PC.
Open the flash tool exe file to open the SP Flash Tool User Interface
Tap on the Download option and load both the download agent and the scatter text file in the scatter-loading section.
Once you load the file, click the Download button
To start the upgrade process of stock ROM on your Cubot X19, you need to turn off your device and hold the Volume Down and Volume Up key together and Connect your Phone to PC/Laptop using USB Cable (Keep the Volume Down and Volume Up button until your computer detects the phone.)
When the phone connects, your device will start upgrading the stock firmware
Wait for a few minutes, If you see a green button on your flash tool which means the upgrading process has been completed.
That’s it! You can reboot your Cubot X19
{
"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
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