UBL & ROOT Realme C15 RMX2180_11_A_85 - Realme C15 Guides, News, & Discussion

This step work on my devices firmware version RMX2180_11_A_85
file boot.img and vbmeta.img inthis post
how to ubl
instal IndepthTest-C11-C12-C15 and open
click start and wait for it to appear start in the depth test and click
on fastboot mode open cmd
fastboot flashing unlock (enter)
fastboot reboot (enter) press vol up or down for unlock bootloader
how to root
click install in magisk manager select patch file point to the original boot file
the boot patch file is in the download folder
copy file boot patch & vbmeta img to folder flatfrom adb
go to fastboot mode
adb reboot bootloader (enter)
fastboot flash boot magisk_patched.img (enter)
fastboot -–disable-verity -–disable-verification flash vbmeta vbmeta.img (enter)
fastboot reboot (enter)

Work at my c12 l, but use platform tool

rudiyansahreder said:
Work at my c12 l, but use platform tool
Click to expand...
Click to collapse
Thanks for report ,,work UBl and root ,,

mine doesnt say magisk_patched.img when i install magisk into the boot.img what will i do?

wakohoxi said:
mine doesnt say magisk_patched.img when i install magisk into the boot.img what will i do?
Click to expand...
Click to collapse
Check in the download folder to the patch img file

Thanks

bass_deso said:
copy file boot patch & vbmeta img to folder flatfrom adb
Click to expand...
Click to collapse
that "flatfrom" is i.е. "root folder", right?..

Does this really work on realme c15? I have installed the in-deph test application but the application always exits

Maaf sebelumnya.
cara mendapatkan stock boot.img gmn? Lupa back up.. terus udh ganti costom rom.. bootloop

apps dont work on c15, crashes each load

Baik sekali
Minta rooter

Related

error on ascend P6

i have a error on ascend P6 its stuck on android logo and in recovery its shows the error i attached a pic. i tried the dload option for software but it doesnt work , please help . i got this phone like this condition only . i dont know history .
missime said:
i have a error on ascend P6 its stuck on android logo and in recovery its shows the error i attached a pic. i tried the dload option for software but it doesnt work , please help . i got this phone like this condition only . i dont know history .
Click to expand...
Click to collapse
Does it have an SDcard in it with a rom in /dload? It sounds like it may be looking for this. Get a card in it and do a force reset (volume up/down pressed and power button pressed .
stuartggray said:
Does it have an SDcard in it with a rom in /dload? It sounds like it may be looking for this. Get a card in it and do a force reset (volume up/down pressed and power button pressed .
Click to expand...
Click to collapse
yeah its loaded in . it just goes to recovery .
P6_firmware(P6-U06,Android_4.2,Emtion_UI,V100R001C00B107,Normal,05011RJP)
this is the zip i have extracted it dload/update.app
is there any other way to load it ?
any adb command to psh the update.app file atleast . coz in recovery its taking adb drivers .
missime said:
any adb command to psh the update.app file atleast . coz in recovery its taking adb drivers .
Click to expand...
Click to collapse
any solution for this error?
in fast boot mode, using adb to flash every *.img file to phone.
Code:
adb wait-for-device
adb.exe reboot bootloader
fastboot.exe flash fastboot fastboot.img
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash batt batt.img
fastboot.exe flash cache cache.img
fastboot.exe flash crc crc.img
fastboot.exe flash curver curver.img
fastboot.exe flash efi efi.img
fastboot.exe flash md5rsa md5rsa.img
fastboot.exe flash modemimage modemimage.img
fastboot.exe flash userdata userdata.img
fastboot.exe flash verlist verlist.img
fastboot.exe flash system system.img
fastboot.exe flash cust cust.img
fastboot reboot
vagraxy said:
in fast boot mode, using adb to flash every *.img file to phone.
Code:
adb wait-for-device
adb.exe reboot bootloader
fastboot.exe flash fastboot fastboot.img
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash batt batt.img
fastboot.exe flash cache cache.img
fastboot.exe flash crc crc.img
fastboot.exe flash curver curver.img
fastboot.exe flash efi efi.img
fastboot.exe flash md5rsa md5rsa.img
fastboot.exe flash modemimage modemimage.img
fastboot.exe flash userdata userdata.img
fastboot.exe flash verlist verlist.img
fastboot.exe flash system system.img
fastboot.exe flash cust cust.img
fastboot reboot
Click to expand...
Click to collapse
how did u flash the system img...it say its too big..any suggestion please

[ROOT/MAGISK] OOS 10.0.14 Magisk patched_boot.img GLOBAL

For future use or other versions like OOS EUROPE,INDIA, etc. , you can patch your own boot.img with my tool here
But for now just follow the instructions
Boot.img patched with MAGISK 20.4 on OOS 10.0.14 HD65AA (GLOBAL)
Only for OOS 10.0.14 Global!!!!
Enjoy!
Instructions:
reboot to fastboot
Code:
adb reboot bootloader
Code:
fastboot boot magisk_patched_10_0_14.img
let it boot and check if u have root
if u got root then reboot to fastboot again
Code:
adb reboot bootloader
Code:
fastboot flash boot magisk_patched_10_0_14.img
When finished type
Code:
fastboot reboot
patched boot.img download: https://drive.google.com/file/d/1wZ2TyIi0uUfbRTxPYK_imURBVjHqaA_f/view?usp=sharing
stock boot.img download: https://drive.google.com/file/d/1R90vvdJEe6NkL2FdqSvuxtk18SmWHYUc/view?usp=sharing
It's still telling me "Root access is not properly installed on this device". I have an unlocked bootloader and OOS 10.0.14 HD65AA (GLOBAL), is there something I'm missing?
EDIT: tried a different root checker and I'm fine. Please disregard.
daaper said:
"Root access is not properly installed on this device"
Click to expand...
Click to collapse
Install Magdisk Manager
Thanks and much appreciate for the patched file!
Hello. No internet after booting.

[GUIDE] How to root it

First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
REMEMBER TO TEST EVERYTHING ON YOUR DEVICE IN THIS PART BEFORE CONTINUING!!!!!
IF YOUR PHONE DIDN'T BOOT OR BOOTED BUT WITH MALFUNCTION STOP NOW AND REBOOT IT, MAYBE YOUR STOCKROM WASN'T CORRECT OR SOMETHING ELSE...
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Thanks a lot for sharing your experience!
Has there been anyone else who managed to root this device?
I really want to buy one but first I want to make sure I will be able to root it from day 1. I don't like to use an unrooted phone
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
ReneZeiss said:
I bought my device last Black Friday and rooted it this week with this guide.
I’ve downloaded my boot.img from Lolinet and googled how to unlock a bootloader of a Moto phone.
I’ve also enabled oem unlock in developer settings.
It’s not so difficult.
The bonus tip from the OP is very helpful. Only rename Magisk is not enough. Also hide the manager to pass the safetynet test.
Click to expand...
Click to collapse
Amazing tips. I think in the end we are free to root it without screwing the device for good
Thanks!!
Ok, I got mine yesterday, and today I successfully root it.
It worked flawlessly!!
Thanks for the guide and advices!!
Root now si possible with twrp, new update thanks @seba_3567
MrZeroXD said:
First, I assume you know what root, fastboot, SafetyNet, bootloader, adb is ( SEARCH FIRST BEFORE DOING THESE STEPS! ) and you know the risks of rooting a device!
Me nor the XDA guys are responsible for bricked devices, nor any damage to you and/or your device.
So, after that, let's dive into the steps of rooting it
First of all is to download your stock android image ( in case something goes wrong plus the boot.img needed for this process )
You can download your stock image the way you want, you can use lolinet etc, just make sure it matches your device!
So, open the image you downloaded, extract the boot.img file and put it on the phone's internal memory, then download Magisk Manager ( I personally used GitHub to download.... ) and open it.
Now, select 'Install' ( the one that says Magisk, not the manager ), go to 'Select and Patch a file'
Navigate and select your boot.img, then wait for it to complete, after that, you'll see a file in the Download folder on the phone called 'magisk_patched.img' grab this file and put it on the computer.
The next step is that you'll need to unlock your bootloader ( I'll not cover how to do that here, but a quick search on ' how to unlock Motorola bootloader' should help ), but be aware that it will format your phone ( you'll lose any saved data, so pay attention! )
After, put the phone in fastboot mode again ( vol minus + power button ), then on the terminal window you're using fastboot, run this command:
fastboot boot magisk_patched.img
( I assume you put the magisk_patched in the same folder you're running fastboot ( Windows case ) )
After that your device will normally boot, install Magisk Manager and check if it "says" installed and displays the version.
If so and your device runs fine, reboot again to fastboot then run on the terminal window:
fastboot flash boot magisk_patched.img
This will make the root persistent after reboots
Now as you expected, you're rooted
A bonus tip:
Safetynet will fail! To fix that, open Magisk Manager, then go to it's settings, then tap to enable "MagiskHide" and then tap "Hide Magisk Manager" type a new name for the Manager and boom, that's it, now SafetyNet will work ( In my case it did hehe )
I'm new to English, learning alone, so any mistyping etc tell me and I'll fix it
Also I'm new to XDA too hihi
Click to expand...
Click to collapse
yes or yes I must download the full firmware, can't find the boot.img directly?
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
pmb6000 said:
Hi, I root the G9+ with your guide and now it's rooted, thank you for post it. I want to change te system fonts, I have some visual impediments and I need a fonts with more contrast and bold. I try with Fontster, HiFonts, Zfonts, and many more. I grant root privileges to these via MagiskManager, but without any success. It's normal that? any idea why? The rootchecher confirm that the phone it's rooted. Please can help me? Thank you and please excuse my poor english
Click to expand...
Click to collapse
I think u'll need to port your custom fonts as Magisk Modules, since you can't change system files directly ( even with root ).
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
taboelephant said:
Hi, I'm new to rooting the phone, I managed to unlock the bootloader, I did everything as in the description except the last step because the fastboot boot magisk_patched.img command did not work. So I copied the magisk file to the adb folder and typed: fastboot flash boot C: \ adb \ magisk_patched_INTjS.img. My phone touchscreen has stopped working. I'm very worried. Is it possible that I used the wrong stock image version or did I do it wrong? Now I wish the phone would just work
Click to expand...
Click to collapse
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
MrZeroXD said:
So maybe your stock was wrong, if ' fastboot boot magisk_patched.img ' failed then u can't force ( fastboot flash ) the installation since it'll probably cause problems...
I suggest you try to download your stock rom and re-flash the boot partition, if no lucky, try using ' Lenovo rescue and smart assistant ' and hope it works again...
Click to expand...
Click to collapse
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
taboelephant said:
Yes, I tried to enter this command but it said that it cannot find the file magisk. Tomorrow I will try to install the stock rom with RSD Lite if that's the right decision, with the help of this website: https://www.androidinfotech.com/moto-g9-plus-odessa-android-10/. If that doesn't help, I will have to give it to repaired because I won't be able to handle it myself.
Click to expand...
Click to collapse
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
MrZeroXD said:
Sincerely I would suggest using the Lenovo tool, it's simple to use, and guaranteed to pick the correct rom.
Click to expand...
Click to collapse
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
taboelephant said:
OK I wiil try tomorrow reapir it with this lenovo tool, I wish it will help.
Click to expand...
Click to collapse
It's should work since it's an official tool, any news tell us. Good lucky buddy.
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
taboelephant said:
Lenovo tool does not work although my model exists its: G9 plus XT2087-2 error that appears: Unable to match tche appropriate firmware. Some key information cannot be read from the device. You can find my stock room here:
https://mirrors.lolinet.com/firmware/moto/odessa/official/. Its RETEU or RETEU_PL version: XT2087-2_ODESSA_RETEU_10_QPA30.19-Q3-32-50_subsidy-DEFAULT. I am from Poland, so it could be RETEU_PL. How can I install this stock room if the lenovo tool doesn't work?
Click to expand...
Click to collapse
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
MrZeroXD said:
So, I've a code that I use on my Linux box, it should work in windows too, but all of your stock rom ( bootloader.img ; got.bin; recovery.img ; etc ) must be in the same folder as fastboot.exe
Here's the code
Spoiler
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash radio_a radio.img
fastboot flash radio_b radio.img
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash recovery_a recovery.img
fastboot flash recovery_b recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
taboelephant said:
Room that I will download should I unpack to adb folder or where? Is it safe to install it yourself or is it better to go to a local phone repairer? It may be hard to find someone who knows what to do.
Click to expand...
Click to collapse
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
MrZeroXD said:
Yeah, as I said, u need to unpack it to the folder where you see the ' fastboot.exe ' file, and then copy all the spoiler commands I sent, put the phone in fastboot mode, and open the cmd in the folder where fastboot.exe and your extracted rom is, then paste and run the spoiler commands and you're good to go, remember that it'll take a while since it'll re-flash all your system.
Click to expand...
Click to collapse
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
taboelephant said:
Ok I will try this method in the evening when I have free time, thank you for your help and sorry for my lack of knowledge. I'm also afraid that when I install the wrong room, usb debugging will turn off, although the theoretical version number is correct.
Click to expand...
Click to collapse
No prob, we're all learning, and all you need to fix a device that doesn't boot, is an unlocked bootloader, since u can re-flash, I did this on a few devices ( moto x4 ; moto G5s ; moto g9+ ) and succeeded on repairing those...

Question After install TWRP stuck in fastboot

hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
numbawon said:
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
Click to expand...
Click to collapse
so what can i do? i dont have stock recovery,and twrp recovery dont start, what fastboot command can i try to repair? only what i have its global rom downloaded from nubia homepage but i dont now how to flash stock rom and repair all this i try miflash tool,but mi flash tool not support zip formats
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
numbawon said:
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
Click to expand...
Click to collapse
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Merlousek said:
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Click to expand...
Click to collapse
Several of us are in the waiting game for the unbrick tool at this point.
i try bumper what you send me but another im stuck here
Merlousek said:
i try bumper what you send me but another im stuck here
Click to expand...
Click to collapse
I'll see if I can get it all extracted for you and post it someplace. I've not done it myself, I just knew where the information was.
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Merlousek said:
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Click to expand...
Click to collapse
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
numbawon said:
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
Click to expand...
Click to collapse
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Merlousek said:
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Click to expand...
Click to collapse
Just use fastboot. Forget mi tool.
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do you means?
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
you mean this fastboot commands?
and flash all files from stock recovery in fastboot?
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do youmeans?
fastboot flash system system.img
fastboot flash recovery recovery.img
like that?
another error when i try flash all files from fastboot
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Merlousek said:
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Click to expand...
Click to collapse
Nice job!
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
What TWRP did you install? Make sure you're downloading a TWRP that's available for this device. So far, to my knowledge, there isn't a TWRP recovery for this device yet.
Hello there, how did u just unlock bootloader by fastboot command? didn't use OEM unlock option on dev setting?
Btw can you share me your twrp that you used?
I need it so badly my rom bugged stuck at google account setup

Question Root OXYGEN OS 13 MT2111_11_F.11 ?

Is there any way we can root MT2111_11_F.11 because for me fastboot appears to be missing as when i try volume down and power it just keeps on restarting after a see the fastboot screen for 0.01secs.
I tried using adb reboot bootloader as well but didn't work.
You should use adb reboot fastboot instead. Note that this mode doesn't allow to unlock bootloader if it is locked. But if bootloader was unlocked earlier, you may use flash command to flash patched boot.img
Code:
fastboot flash boot boot.img
go to github magisk, get apk install it on your phone, download your Full OTA, extract it via payload.bin extractor and take out boot.img then patch boot.img using magisk and do fastboot flash boot magiskpatchedboot.img
Original boot.img for oos f11 to patch
penguinus said:
You should use adb reboot fastboot instead. Note that this mode doesn't allow to unlock bootloader if it is locked. But if bootloader was unlocked earlier, you may use flash command to flash patched boot.img
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Button combination = Fastboot Logo flashes for a split second, Phone instantly restarts to system, no access to bootloader therefore impossible to use flash commands
adb from system > reboot to bootloader = exact same as above.
Not bootloader, but userspace fastboot (fastbootd) mode. The command is
Code:
adb reboot fastboot

Categories

Resources