OZIP's FOR RMX2001«Android 10»ㅤㅤ ㅤㅤㅤㅤ ㅤㅤㅤㅤㅤㅤㅤ Click Here
«Android 11»*Team Drive Gone Will Find And Update
Need Help?
Contact Me On Telegram
-GROUP LINK-
Awesome!! Can I dirty flash ui2?
Android 11 update (C12 Global) failed, why?
Not flashing ui 2
Ferbir88 said:
Android 11 update (C12 Global) failed, why?
Click to expand...
Click to collapse
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
xdriv3r said:
Not flashing ui 2
Click to expand...
Click to collapse
u cant flash it by stock recovery read other comment reply
unique_sandesh said:
it cant be flashed directly u should flash ozip using custom recovery but after flash , flash patched vbmeta too otherwise u got brick for more info ask in ofiicial realme 6 main telegram group
Click to expand...
Click to collapse
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Ferbir88 said:
I tried not working (bootloop). I lfashed patched vbmeta. I installed it with custom recovery
Click to expand...
Click to collapse
tell meyour all process sir , and they also need format
unique_sandesh said:
unique_sandesh said:
tell meyour all process sir , and they also need format
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
unique_sandesh said:
tell meyour all process sir , and they also need format
Click to expand...
Click to collapse
First, I flashed stock b.53 firmware with SP flashtool and I update with stock recovery to b.65. For the second time I need root the firmware and patch vbmeta, because missing the custom recovery without this step.( orange fox recovery)For the third Time I flash the c.12 firmware with custom recovery, and reboot to bootloader from recovery than I patch c.12 vbmeta. For the last Time I reboot and the end result bootloop
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
unique_sandesh said:
ofc it will not boot untill u format data , u need to format data . give these cmd fastboot -w , fastboot erase userdata
Click to expand...
Click to collapse
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Ferbir88 said:
Thank you very much now It works, but I want to ask you: Why can not i enter in recovery Mode? I tried the power on and volume down combination, but the phone enter only fastboot mode with "oplus verification failed" message. If I do a factory reset under the Android, the phone load the recovery, until resetting.
Click to expand...
Click to collapse
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
unique_sandesh said:
from rmui 2.o we only get in fastboot mode. for recovery give this cmd fastboot reboot recovery, , and ignore that oppo verify failed msg
Click to expand...
Click to collapse
Thank you very much!
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
were the same situation and i dont know what to do. Please help us.
which is the process 4 install? im on rui 1.0
Kodize said:
which is the process 4 install? im on rui 1.0
Click to expand...
Click to collapse
using custom recovery
Rollback With Custom Recovery
This Method Only For Realme 6/6i(indian)/6s _____________________ RMUI2.0 TO RMUI 1.0____________________________________________ This Method For Downgrading From F2Fs Based Custom Roms ⓿ Flash Latest TWRP (Gofaraway One) ❶ Go to manage partitions And Select...
telegra.ph
Jegwaar said:
Hello everyone don't know why but i didn't get realme ui 2.0 update I'm stuck on B.65 for RMX2001 and as i recall i once rooted it unlocked bootloader but i relocked it and unrooted it to with all its ROM and Recovery set to default and i exited In-depth test too but i didn't get 2.0 update last updated version is B.65 so i wanna know if i download the file mentioned above and install it will it work.... Please reply
Click to expand...
Click to collapse
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
unique_sandesh said:
keep unlockd your bl and use spft for flashing rui 2 make sure you selected download only in spft while flashing here is the latest decrypted firmware link https://t.me/rmx2001_clouds/7
Click to expand...
Click to collapse
Hi guys, did someone do this ? i'm in the same situation after rolling back to B55 using stock recovery, now stuck on B65, no update coming.
Bootloader is unlocked, when i flash a C18 firmware with SPF phone bootloop in fastboot mode.
Only flashing a B65 firmware with SPF to get phone boot corretly.
I just need to known if this method is tested with the given C19 firmware ?
Many thx.
Related
my honor 4x che1-l04 syddenly stop working when i press the power button it shows honor logo and went off also i never flash any custom recovery also only acessable option is fastboot&rescue mode
my boot loader is locked but i managed to get boot loader key from honor care
after that i unlock boot loader and flash the phone from fastboot mode but it didnt work at all
all files mean recovery,boot,system.img flashed properly no issue but it didnt worked
last version of my phone is marshmallow build no is Che1-L04C675B520
please help me
gilmaan azmi said:
my honor 4x che1-l04 syddenly stop working when i press the power button it shows honor logo and went off also i never flash any custom recovery also only acessable option is fastboot&rescue mode
my boot loader is locked but i managed to get boot loader key from honor care
after that i unlock boot loader and flash the phone from fastboot mode but it didnt work at all
all files mean recovery,boot,system.img flashed properly no issue but it didnt worked
last version of my phone is marshmallow build no is Che1-L04C675B520
please help me
Click to expand...
Click to collapse
Do you have the marshmallow update pacakage(one you downloaded to update the phone to marshmallow) if you have then extract it and place the dload folder inside a memory card and place it in your phone, then while switched off press power+volume up+volume down all at once and wait until your phone vibrates then leave the buttons and let the software do the work. Hope it helps:good:
SumitGupta2442 said:
Do you have the marshmallow update pacakage(one you downloaded to update the phone to marshmallow) if you have then extract it and place the dload folder inside a memory card and place it in your phone, then while switched off press power+volume up+volume down all at once and wait until your phone vibrates then leave the buttons and let the software do the work. Hope it helps:good:
Click to expand...
Click to collapse
i did it brother but it didn't work
only one thing in my phone work is fastboot and rescue mode i also use dc phoenix it also didn't help me at all
dc phoenix show me that it need che1-l04 b126 stock Rom which i didn't find anywhere also on official site
gilmaan azmi said:
i did it brother but it didn't work
only one thing in my phone work is fastboot and rescue mode i also use dc phoenix it also didn't help me at all
dc phoenix show me that it need che1-l04 b126 stock Rom which i didn't find anywhere also on official site
Click to expand...
Click to collapse
Download it from here http://download-c.huawei.com/download/downloadCenter?downloadId=53693&version=167605&siteCode=in. Btw I have no idea what dc phoenix is.
gilmaan azmi said:
i did it brother but it didn't work
only one thing in my phone work is fastboot and rescue mode i also use dc phoenix it also didn't help me at all
dc phoenix show me that it need che1-l04 b126 stock Rom which i didn't find anywhere also on official site
Click to expand...
Click to collapse
If you have unlocked bootloader just flash twrp version for your device and download any MM version Fullrom.zip using firmware finder and flash it through twrp.
Before flashing new rom wipe all partitions from twrp.
miststudent2011 said:
If you have unlocked bootloader just flash twrp version for your device and download any MM version Fullrom.zip using firmware finder and flash it through twrp.
Before flashing new rom wipe all partitions from twrp.
Click to expand...
Click to collapse
i unlocked the boot loader also flashed the twrp recovery
but its not booting in twrp recovery both by power button + volume up and through fastboot command
gilmaan azmi said:
i unlocked the boot loader also flashed the twrp recovery
but its not booting in twrp recovery both by power button + volume up and through fastboot command
Click to expand...
Click to collapse
May be you are using wrong version twrp.
miststudent2011 said:
May be you are using wrong version twrp.
Click to expand...
Click to collapse
i am using TWRP_3.0.3-0_N_cherry its for honor 4x
gilmaan azmi said:
i am using TWRP_3.0.3-0_N_cherry its for honor 4x
Click to expand...
Click to collapse
Then try this process first flash stock recovery and then use dload method and check whether it recovers or not.
miststudent2011 said:
Then try this process first flash stock recovery and then use dload method and check whether it recovers or not.
Click to expand...
Click to collapse
i did it but dosent work
i also use the huawei multi tool it also dosent worked
one thing i noticed that when i flash cust file it shows failed : remote(command not allowed )
also cache is not wiping through fastboot mode it shows the same failed : remote(command not allowed )
i think its a soft brick situation because it boot in fastboot and rescue mode also it show honor logo and went off
i dont know what to do i flashed every single official rom from b161 to b520
and also flashed twrp it also didnt work
please help me
gilmaan azmi said:
i did it but dosent work
i also use the huawei multi tool it also dosent worked
one thing i noticed that when i flash cust file it shows failed : remote(command not allowed )
also cache is not wiping through fastboot mode it shows the same failed : remote(command not allowed )
i think its a soft brick situation because it boot in fastboot and rescue mode also it show honor logo and went off
i dont know what to do i flashed every single official rom from b161 to b520
and also flashed twrp it also didnt work
please help me
Click to expand...
Click to collapse
Just only flash stock recovery not all images and try dload.
You can't flash cust with fastboot and also you can't wipe cache with fastboot
miststudent2011 said:
Just only flash stock recovery not all images and try dload.
You can't flash cust with fastboot and also you can't wipe cache with fastboot
Click to expand...
Click to collapse
i flashed stock recovery but it dosent boot in recovery mode
also it tried dload method but dosent work
what is the reason, that the phone flashed recovery properly but not booting in recovery mode
gilmaan azmi said:
i flashed stock recovery but it dosent boot in recovery mode
also it tried dload method but dosent work
what is the reason, that the phone flashed recovery properly but not booting in recovery mode
Click to expand...
Click to collapse
Are you flashing the ROM version which you were before bricking your device.
What is the android version you were before.
miststudent2011 said:
Are you flashing the ROM version which you were before bricking your device.
What is the android version you were before.
Click to expand...
Click to collapse
yes last version of my phone is marshmallow build no is Che1-L04C675B520
and i am flashing the same but didnt work
miststudent2011 said:
Are you flashing the ROM version which you were before bricking your device.
What is the android version you were before.[/Q
yes last version of my phone is marshmallow build no is Che1-L04C675B520
and i flashed the same but it didnt work
dont know what i am donig wrong
every procedure i followed is correct
Click to expand...
Click to collapse
miststudent2011 said:
Are you flashing the ROM version which you were before bricking your device.
What is the android version you were before.
Click to expand...
Click to collapse
yes last version of my phone is marshmallow build no is Che1-L04C675B520
and i am flashing the same but it didnt work
dont know where i am going wrong
gilmaan azmi said:
yes last version of my phone is marshmallow build no is Che1-L04C675B520
and i am flashing the same but it didnt work
dont know where i am going wrong
Click to expand...
Click to collapse
There was a similar case which I helped him to solve the issue but dont remember the build number that helped him.
Check my previous posts you can find the guide and build number.
miststudent2011 said:
There was a similar case which I helped him to solve the issue but dont remember the build number that helped him.
Check my previous posts you can find the guide and build number.
Click to expand...
Click to collapse
which post sir
same issue
I'm facing exactly same issue, Any help welcome.
gilmaan azmi said:
which post sir
Click to expand...
Click to collapse
did ur issue get fixed? please post updates.
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Tyche303 said:
I rooted my phone but didn't really like it while having my banking apps on it. So I tried to get back to normal but ended up wiping everything, even the OS, off of my phone. I am trying to get it back to normal. I followed one guide on here which gave me an android 10 ROM but I was unable to update it to the latest version. The link for that guide is: https://forum.xda-developers.com/mi-a2/how-to/guide-official-stock-android-10-t4033835. I didn't install the force encrypt or the magisk because I don't wanna root it. I just want it back to how it was before the root. So I am wondering if there is a way that I can get back to normal now. Thanks in advance for any advice.
Click to expand...
Click to collapse
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
KevMetal said:
well what is the problem ? if it booted and you didn't flash magisk you are on stock. ...what exactly do you want ? to lock the bootloader or remove twrp custom recovery too ?
Click to expand...
Click to collapse
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Tyche303 said:
The ROM was an earlier version of android 10. But I am unable to install the latest updates for android 10 OTA. It's working but I would like to be able to receive updates again. If there is another ROM that would give me those results I would be fine with flashing that too.
Click to expand...
Click to collapse
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
Awesome, thanks! I will try that later tonight or tomorrow.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
So I downloaded a fastboot file from here :https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
The miui flash program wouldn't work for me. On the website you linked me there was a method that used twrp to flash it. But when use twrp I can't see any of the zip files in twrp. I've tried three different ones from the link I just shared here. Not sure what the problem is.
KevMetal said:
the most likely issue is your recovery ... take the stock recovery from a fastboot stock rom and flash that with fastboot
also make sure to flash stock rom in both slot A & B then updates will work
go to this website
https://www.getdroidtips.com/xiaomi-mi-a2-stock-firmware/
download a PIE stock rom that is a FASTBOOT version ... download miflash ...follow instructions to flash it using miflash in fastboot mode
then boot & set it up ...it will start offering updates by itself
your problem right now is that you flashed stock rom in only one slot and you have a custom recovery so that is why it can't update
Click to expand...
Click to collapse
nevermind, I have gotten it to work. Thank you for your help
Tyche303 said:
nevermind, I have gotten it to work. Thank you for your help
Click to expand...
Click to collapse
okay glad you came right
half the fun is figuring this stuff out
Hi, today I tried using the Realme Flash tool for X2 Pro but it bricked my phone. Based on the flash tools error logs it shows this
"~~Medium~~ UnZipFloHelper Delete temp file exception:The process cannot access the file 'C:\Users\Michael\AppData\Roaming\realmeFlashTools\temp\system.img' because it is being used by another process."
seems like a windows problem but I cant find any reference on the web. I tried restarting my PC but it didn't solve my problem.Any suggestions how to fix this? thank you!
Realme flash tool decrypt and extract the ofp to C:\Users\Michael\AppData\Roaming\realmeFlashTools \temp .This seem to be windows permission issue .
Try to run as administer the realme flash tool and try again. Also you can flash unpacked ozip trough fastboot manually, It will be very similar to flashing with realme flash tool .
or965 said:
Realme flash tool decrypt and extract the ofp to C:\Users\Michael\AppData\Roaming\realmeFlashTools \temp .This seem to be windows permission issue .
Try to run as administer the realme flash tool and try again. Also you can flash unpacked ozip trough fastboot manually, It will be very similar to flashing with realme flash tool .
Click to expand...
Click to collapse
Thank you it worked! I tried run as admin the flash tool and deleted .IMG file it also seems that an Virtual image program is holding to it so I disabled it.
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
Hi, ( if your problem is not resolved at this time )
If you want you can try this procedure
Enter fastboot
- don't know if a fastboot erase " boot + system + vendor" can help
Flash stock recovery
Enter recovery and format data
Reboot bootloader
Flash full stock rom ~5Gb ( not the OTA ~3GB) with the realme flash tool
LoVerMaKi said:
Hi, ( if your problem is not resolved at this time )
If you want you can try this procedure
Enter fastboot
- don't know if a fastboot erase " boot + system + vendor" can help
Flash stock recovery
Enter recovery and format data
Reboot bootloader
Flash full stock rom ~5Gb ( not the OTA ~3GB) with the realme flash tool
Click to expand...
Click to collapse
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
did you fix your phone?
i am at same problem here please please please answer me.
please share the procedur to fix if you have fixed
PETER.PARKER said:
i have a same problem here. but i cant flash stock rom on fastboot flashing img files will loop back into bootloader and realme flash tool says "CANNOT FIND CENTRAL DIRECTORY" PLEASE HELP ME
Click to expand...
Click to collapse
Hi,
Flashtool says some error that not relevant. If the rom is not adaptable for the phone, the error msg is not really clear.
Here is some link. I cant help you more.
You need to dl the c27.ofc (full stock rom).
rom and flash tool
ofc extractor
Option 1 try flash the c27 with flashtool.
Option 2
. Extract the ofc with MCT OFP Extractor .boot in flashboot and flash the boot/recovery (maybe try all img one by one if it pass) i use google for the correct syntax for each img file
. try boot in recovery et format data
. Reboot in fastboot and reflash the ofc with flashtool
You need to experiment to find the correct proces for your problem.
Hf gl
LoVerMaKi said:
Hi,
Flashtool says some error that not relevant. If the rom is not adaptable for the phone, the error msg is not really clear.
Here is some link. I cant help you more.
You need to dl the c27.ofc (full stock rom).
rom and flash tool
ofc extractor
Option 1 try flash the c27 with flashtool.
Option 2
. Extract the ofc with MCT OFP Extractor .boot in flashboot and flash the boot/recovery (maybe try all img one by one if it pass) i use google for the correct syntax for each img file
. try boot in recovery et format data
. Reboot in fastboot and reflash the ofc with flashtool
You need to experiment to find the correct proces for your problem.
Hf gl
Click to expand...
Click to collapse
I downloaded and flashed that c27 rom with realme flash tool it successfully completed the flashing process but nothing new it loops back into bootloader im literally pissed rigt now
Detail info about my problem "https://forum.xda-developers.com/t/...evice-state-unlocked-secure-boot-yes.4330817/"
Rinku390 said:
I have installed oxygen os built 4 in my x2 pro device but i didnt like the interface so i decided to return to realme ui and i have installed realme ui2.0 on my device thrugh twrp custom recovery but after install it suddenly switch off and it goes to a boot loop. now i can't enter into my recovery mode, i can't flash twrp, i can only enter in fastboot mode. please give any solution , i need my phone to back like normal...
Click to expand...
Click to collapse
i am facing same problem,is your problem resolved ,please help
JKD23 said:
Thank you it worked! I tried run as admin the flash tool and deleted .IMG file it also seems that an Virtual image program is holding to it so I disabled it.
Click to expand...
Click to collapse
Please tell me how you did?
Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks
forget this..i've got ROOT check the other thread !
How do you fix it?
simika said:
forget this..i've got ROOT check the other thread !
Click to expand...
Click to collapse
How did you managed to fix this?
by reading lol.. check the other thread all written
For reference to whoever that are confused about where to look for the solution.
ROOT GAINED !!!!
THIS METHOD WORKS on both: POCO M3 Pro / Redmi Note 10 5G hey guys.. wonderful news.. been trying here and there and IT WORKS FINALLY i gained root of POCO m3 Pro 5G ! i'll write in steps how it works and post all files i've been using...
forum.xda-developers.com
Download the vbmeta and flash it via fastboot to get rid of the dm-verify.
simika said:
by reading lol.. check the other thread all written
Click to expand...
Click to collapse
Could you reference a link or give me a little how to?
I tried a lot now:
- Installed a new Firmware trough Fastboot
- Using MsmDownload Tool
nothing helped so far.
So it would be great if you could assist in any way.
simika said:
Hey guys.. just updating you all
in all of my (previous ) test to get my patched boot.img
i've got this initial msg on my boot :
dm-verity corruption
your device is corrupt.
it can't be trusted and my not work properly.
press enter button to continue.
Or, device will power off in 5s.
(written in white)
NOW i tell that it didn't happen after bootloader unlock (so it was unlocked and all good no problem )
but honestly i don't remember if that happened when i tried to upload official rom through Miflash !
Anyway is there any way to remove this? I re installed ( clean install ) official Rom and it's still there, locked bootloader back and it's still there tried some
fastboot oem enable_dm_verity
i'm also warning new user that you might get this msg at boot !
thanks
Click to expand...
Click to collapse
I done everything but my phone doesn't unlock so now I have the dm-verity warning and I can't do a clean flash with Miflash. Also Miflash Unlock doesn't work. What I can do now?
if you can enter in fastboot mode, reflash stock boot and vbmeta
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
How can I do? Miflash says:
error:Writing 'crclist' FAILED (remote: 'not allowed in locked state')
bro you have relock bootloader, this is a fatal error. the only way is try to unlock with an mtk tool that do this via pc. you can find on internet. search unlock all mtk devices. i think there a link also on xda
Just realized that the M3 thread, my phone is a M4.
.
@simika how are you sending this question?
1. Hello friends, there are two ways to fix this problem, first you need Root, I read your Root tutorial, your tutorial is very good, and after using Root, you need to download any file manager, give Root Permissions, you need to backup your baseband, nvram nvdata nvcfg backup and save, you also need an MTK Bypass, you can search for MTK Auth Bypass Tool through Google, you also need to use SP Flash to flash the machine, you need to download the official firmware package, which can be downloaded from xiaomirom.com , download the corresponding version, use SP Flash to read your firmware package, after the reading is completed, choose to format all and download, wait for completion, press the power button after completion, you will find that the error has disappeared, but the baseband is lost, But you have backed up. Boot through fastboot to unlock the BL lock, perform fastboot flash nvram ....... fastboot flash nvdata ....... fastboot flash nvcfg ....... Fastboot reboot reboot. Congratulations The baseband is back, I'm a novice, my instructions are not comprehensive, such as where is the baseband location, but I have too many characters, I will list the baseband location. 2. Replace a new motherboard, all mobile phone problems are all solve.
Hope to help you.
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
Thanks. This worked on my Umidigi A11 phone.
xdadev_user11 said:
Thanks. This worked on my Umidigi A11 phone.
Click to expand...
Click to collapse
nice!
hello i got the same problem today, my phone is redmi9a can some help me regarding to this error ?
i had this problem even though i never unlocked my bootloader so i couldnt flash anything to fix it. but when i got the miui 13 update it fixed it for me
wetito said:
if you can enter in fastboot mode, reflash stock boot and vbmeta
Click to expand...
Click to collapse
What if you cant enter fastboot?
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Ifuckinghatemyselfandall said:
Hello, i have a redmi note 9,
I was using lineage OS from here https://t.me/HelioG85_Updates/265
Custom firmware, custom opensource vendor
I wasnt able to boot into the recovery today for some reason, i was using the recovery from here https://t.me/HelioG85_Updates/268
In a moment of genius, i decided to get this app https://play.google.com/store/apps/details?id=net.mxbi.reboot and used it to boot to the recovery , now my device is bricked, doesnt enter fastboot or the recovery , and i cant turn the device of meaning i cant flash with sp flash tool
My bootloader is unlocked. i do not have a xiaomi account anymore
I have my imei and nvdata backed up, so i should be fine on that regard
Please do help me, This is the only phone i have and i cannot get a another one . If you help me i will be forever greatfull to you, Please help me i am desperate
Click to expand...
Click to collapse
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
flairepathos.info said:
So sp flash tool will lock your phone to engineer mode if it turns off follow this instruction:
prepare sp flash tools to only flash recovery (the one you want to boot into)
then click the download button to start flash
then wait for phone to get to boot( when image appears, before it gets to reboot plugin your phone to pc)
sp flash tools will flash then when done make sure you reboot to the custom recovery
then if you can access your system from recovery , look next to build.rop for recovery or rebootfromrecovery.p
copy the file somewhere
edit in notepad to clear everything, save it then use the edited one to overwrite
Click to expand...
Click to collapse
I am going to try the mtk bypass tool, is that going to work? if not i am going to try your instructions, however it did not boot into the recovery even after reflashing , i have tried that before with the twrp app
It cannot detect the device, it isnt in device manager either, i am getting scared
edit: actually it gets detected in device manager as "usb serial device (com4)" when i hold the power button, volume up and volume down at the same time, when i do that, the device stays with a black screen
SP flash tool still does not detect it
it seems to be disconnecting while in this state
Please help, i cant turn the device off
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Ifuckinghatemyselfandall said:
sp flash tool says STATUS_EXT_RAM_EXCEPTION i was trying to flash miui 12.5 R i will try flashing 12.0.5 q since thats what people are using
Click to expand...
Click to collapse
You need to flash the SAME miui version present on the device first.
VD171 said:
You need to flash the SAME miui version present on the device first.
Click to expand...
Click to collapse
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
It is now giving me "error status error" please help
Ifuckinghatemyselfandall said:
But i do not know which version was present before, i was using a custom rom when it bricked...
I do think it was running 12.0.6 EEA Q
i am trying to flash miui 12.0.5 global, will that be okay?
Click to expand...
Click to collapse
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
VD171 said:
Certainly, mixing files from different miui versions, bricked your device.
You need to flash the correct miui version to fix the partition table.
And then, you can flash another miui version using fastboot.
Click to expand...
Click to collapse
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Ifuckinghatemyselfandall said:
No, this is not waht bricked my device, i rebooted to a custom recovery while on a custom rom and thats when it happened
Click to expand...
Click to collapse
Custom recovery will never brick a device.
VD171 said:
Custom recovery will never brick a device.
Click to expand...
Click to collapse
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Ilovethewholeworldbutme said:
You dont seem to understand what i am saying, It does not if you disable boot verification, which i did , please reread the post
Click to expand...
Click to collapse
Just flash the full stock miui again.