Related
Hello I saw everyone facing issues in updating Xt 1942-1 to Android 9 pieso a person named Adnan shabir helped me in updating my phone which is Moto p30 note model no Xt1942-1 to Indian variant XT-1942-2 pie update steps are simple
First you have to download this firmware which is Android 9 pie with June security patch. Here is the link https://drive.google.com/file/d/1lLmDvX4R4o2Jqrhp1RQflap27jxe4hXS/view
Then flash one by one command given in the link below
https://del.dog/motofbrf.sh
Ignore second command which is fastboot -w and flash one by one using cmd or powershell make sure you have adb and fastboot driver installed and also copy fastboot and adb files to firmware folder.
If you don't have adb and fastboot files download from here :
https://download.highonandroid.com/file/Tools/fastboot.zip.html
After downloading everything connect USB cable to your phone and enable USB debugging in developer options make sure your bootloader is unlocked
Write adb reboot bootloader in cmd or powershell in powershell you to write "./" Before adb or fastboot then after restarting to bootloader check fastboot devices it will show your device then paste commands which are mentioned in above link one by one and you are good to go.
To avoid app crashes kindly factory reset your device after update.
Credits to Adnan Shabir and this group
Motorola One Power [chef]
https://t.me/MotoOnePower
i had hard brick my device after flash above method with wrong variant device. please can you help me please
pt917 said:
i had hard brick my device after flash above method with wrong variant device. please can you help me please
Click to expand...
Click to collapse
Did you manage to sort it and how?
yudestar said:
Did you manage to sort it and how?
Click to expand...
Click to collapse
yes i am
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Already tried power and minus option.when you connect to a desktop what does it say ?
Dokrak99 said:
Already tried power and minus option.when you connect to a desktop what does it say ?
Click to expand...
Click to collapse
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
That's bad.
Hold the power +/- longer then 15 seconds try both.
Second
Charge for about 10 minutes and try the same again.
Last drain it when down keep pushing the power button to flat it.hook it up on desktop and install miflashtools.or try power +/- again
Dokrak99 said:
Hold the power +/- longer then 15 seconds try both.
Click to expand...
Click to collapse
Same as:
LordRedstone05 said:
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
Click to expand...
Click to collapse
Dokrak99 said:
Charge for about 10 minutes and try the same again.
Click to expand...
Click to collapse
When I try to charge it it goes in the bootloop again until I disconnect it and the battery runs out.
Dokrak99 said:
Last drain it when down keep pushing the power button to flat it.
Click to expand...
Click to collapse
It goes on, shows this battery icon, that it's empty and goes off. This repeats until I release the button.
Dokrak99 said:
hook it up on desktop and install miflashtools.or try power +/- again
Click to expand...
Click to collapse
The miflashtool does nothing when I click on Flash with the images and scripts loaded. Power +/- does the same as before.
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Dokrak99 said:
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Click to expand...
Click to collapse
Thanks in advance
What should I do in this tool? The tool doesn't recognize my phone. It brings nothing since I cannot access Fastboot.
Well basically there is only one real option left . contact mi service center because mi don't support or they closed there download,edl support on there phones to prevent rom swapping .there is a edl cable with mtk support around but that's a long shot.because I never had a messed up phone like this.at least not one with mtk.without recognise you're desktop I don't see a fix in this to get in fastboot or flash it.
Download platform tools drop it on c:/ so c:/platform tools .install abd drivers package if you didn't have it.go in platform tools the top line and tick Cmd hit enter.try command : fastboot devices .try a few times if a number pops up you can try .fastboot reboot fastboot
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
TWRP bricked my redmi Note 9 too, but i had ADB Connection in the black Screen so i rebooted to Fastboot over ADB and reflashed the Stock rom
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
Did you find solution on this? Please answer bro i need your help
Jayson Galang said:
Did you find solution on this? Please answer bro i need your help
Click to expand...
Click to collapse
Unfortunately i haven't found a solution. I had to send it to a service center 2 Days ago. Sorry, that i couldn't help.
the right driver is mtk this is not adb nothing happens the this you could fixs is
go to the nearest techniciann beacause they need special tools to fix properly
Is your phone still bricked, If yes, I can provide link for the factory firmware recently released for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Communos said:
Is your phone still bricked, If yes, I can provide link for the factory firmware recently leaked for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
Click to expand...
Click to collapse
yow is that legit? Had my redmi note 9 bricked for a week now.
CruisaderX said:
yow is that legit? Had my redmi note 9 bricked for a week now.
Click to expand...
Click to collapse
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If it keeps restarting, you've made any wrong modification. You need to follow your steps back and try to unmake your modification.
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
If you are using V12.0.5.0 or higher, TWRP will not work.
If you want to use sp flash tool, you need to flash the stock rom preloader using V12.0.4.0 (or lower). (It will works perfectly with lower preloader binary version).
With an older preloader version, your phone will can receive DA files and accept flashing with NO auth.
Everything you need to do is plug your phone in usb (without press any key, if you press any key it will enter in EDL mode and requests authenticaion).
Here, are PRELOADER binaries for flashing: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221081/
Here, are DA files for flashing using flash tool: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209767/
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
[/QUOTE
Click to expand...
Click to collapse
I tried actually before after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting), I will call this state 1 brick. In state 1 brick you can still access fastboot mode normally. Then i tried to flash twrp hoping to just flash a rom to fix it leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot bootloader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi devices. Now I am stucked with a hard bricked note 9 with no way of fixing.
CruisaderX said:
i tried before actually after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting, I will call this state 1 brick. In state 1 brick you can still access fastboot mode. Then i tried to flash twrp hoping to just flash a rom leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot boot loader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi device. Now I am stucked with a hard bricked note 9 with no way of fixing.
Click to expand...
Click to collapse
You need to read every line and every word careful and follow only specific guide for your specific problem.
If you try to do anything you see, obviously you will cause more damages to your device.
Please, read my post again: https://forum.xda-developers.com/t/redmi-note-9-merlin-4-128-nfc-hard-brick.4201717/post-84379823
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Hi All, as this device is fairly new and there is not much clarity on things so, I decided to create a master guide as you see below. I am also attaching a PDF version of this guide as I have not formatted this XDA post to what I feel it should be like. You may download and follow that, I will keep updating things as I find.
Lets start
1. Unlock Bootloader1.1 Apply for Bootloader Unlock
Enable developer settings
Go to Settings>About phone/My device> All specs> Hit MIUI Version 8 times
Access Developer Settings from Settings>Additional Settings
Enable OEM Unlocking option
Now login to your desired Mi Account that you wish it to be associated with your device (Mi account should have a mobile number registered for OTP and verification sometime asked by MI flash unlock tool)
Your unlock bootloader wait time starts now. Wait for 7 days (168 hours from the time you added MI account) to unlock bootloader
1.2 Unlocking BootloaderSo you have crossed the wait period…. Now follow below to unlock assuming you have all the USB drivers for Mi devices (usually auto installed when you connect mobile)
Warning: All your userdata (including pictures and files) will be wiped out
Download official Mi flash unlock tool from this link: https://miuirom.xiaomi.com/rom/u1106245679/5.5.224.24/miflash_unlock-en-5.5.224.24.zip
Boot into Booloader: Power off your mobile then hold Volume Down + Power Button till fastboot bunny pops up
Open Mi Flash unlock tool downloaded in step 1
Sign in with same account that you used to sign in in Developer Settings in step 1.1.d. It may ask to verify your account with OTP. do it.
Click Unlock on the tool.
Your device will be unlocked and rebooted. Wait till reboot.
Congrats… you have an unlocked mobile device now
Now let’s go to Rooting your device for which we will have to flash TWRP to Mobile
2 TWRP Flash and Rooting2.1 TWRP Flash
Download and Install Minimal ADB and Fastboot for windows for this link: https://androiddatahost.com/wp-content/uploads/Minimal_ADB_Fastboot_v1.4.3.zip
Download unofficial TWRP (only one available as of writing this guide) from here: https://sourceforge.net/projects/xi....6.0_11-0_LOCAL-20220203-01-vili.img/download and rename it to twrp.img
Also download Magisk from below link: https://github.com/topjohnwu/Magisk/releases/download/v24.0/Magisk-v24.0.apk we will use it next section for rooting.
Rename the downloaded magisk file from magisk.apk to magisk.zip and copy it to your device’s storage
Copy the above twrp.img file to Minimal ADB and Fastboot folder (not necessary if you know some directory navigation using command prompt)
Boot mobile into bootloader (follow 1.2.b)
From your Minimal ADB and Fastboot folder open Cmd here.exe file to access the ADB tool
Connect your device to PC
Verify if device has connected successfully using the command below
Fastboot devices
This should return your device id
Now boot into TWRP using below commands
Fastboot boot “twrp.img” if you pasted twrp.img in minimal adb and fastboot folder
Fastboot boot “path to twrp.img” if you did not move it to the minimal adb and fastboot folder
Let the device boot to TWRP
In above step we just booted by TWRP which is temporary. Now let’s flash it to make it permanent:
Go to Advanced settings in TWRP and click Flash Current TWRP
Reboot to TWRP
2.2 TWRP Backup of Current Rom
You should have a working TWRP
Boot to TWRP and navigate to Backup section
Select all partitions and swipe to confirm
If you see error in backing up, uncheck Data and EFS partition backup
The backup should complete successfully
Have this backup copied to a PC for emergency wipout of your mobile
2.3 Rooting/Flashing Magisk
Go to Install in TWRP and select magisk.zip you copied in step 2.1.d
This will flash magisk and root your device. Now reboot to system from recovery
Once you have the device booted, rename the magisk.zip to magisk.apk again and install the magisk app on device
You may update if you see any updates to magisk or app
2.4 Passing Safetynet
Download this magisk module zip from here: https://drive.google.com/file/d/1QJHPpL4R8fcxjB35XbcpaCOipKzpvL2I/view?usp=sharing
Go to magisk app settings and enable Zygisk (beta) also enable Enforce Deny List
Select Hide the Magisk app and give any desired name for Magisk to hide its identity
Now go to modules page in Magisk app.
Select Install from source/storage option and chose the downloaded safteynet zip
Reboot
This will pass safetynet but still Indian bank apps won’t work. Keep following below for clear
Go to magisk settings and enter Configure DenyList
Add all the apps you want to hide magisk and root from (such as phonepe, Gpay)
Don’t leave any service from the selected apps unchecked
3. Flash EU RomWarning: All your userdata (including pictures and files) will be wiped out
A TWRP backup of current rom is recommended before following the next steps
You can see section 2.2 for the instruction on backup
Download Fastboot EU rom from here: https://androidfilehost.com/?fid=17825722713688263895
Extract all the contents in zip file to any normal folder
We will be using Bootloader/Fastboot mode. Boot into Bootloader: Power off your mobile then hold Volume Down + Power Button till Fastboot bunny pops up
Connect your device to PC
From the extracted folder Open windows_fastboot_first_install_with_data_format.bat(for windows).
You may execute appropriate similar named file if you are running Linux or MacOS
The EU rom flashing process will start. Hit “Y” on keyboard to accept Formatting
Wait patiently while the PC does its Job.
You may see a long pause post “writing Cust” command depending on PC configuration. You should wait for 5 minutes at least, then try hitting any letter key on your keyboard, the process continues this way.
You may hit letter key whenever you see unusual pauses during pushing of super partition file sparse sending 1 of 9 to 9 of 9
Wait till process finishes and reboots
For TWRP and Rooting you can follow the same guide in section 2.
Updating to Miui13/Android 12 EU Rom
Check out this guide to Update to Android 12
Happy Rooting… Njoy your device.
Lastly.. All the credit goes to respective owners, I have just compiled everything together and in an easy manner. PM me for credits.
Do let me know if you have any suggestions and corrections.
Thanks & Regards,
Abdus Saboor Asad
Reserved
Reserved
Much appreciated, good overview.
Will try when I get my bootloader unlocked.
Rammetje.b said:
Much appreciated, good overview.
Will try when I get my bootloader unlocked.
Click to expand...
Click to collapse
You are welcome.
sasaboor64 said:
You are welcome.
Click to expand...
Click to collapse
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram
Rammetje.b said:
Quick question if you allow me.
The unlock boot loader timer starts ticking even without hooking the phone up to the mi unlock tool? Just the dev options, OEM unlock and login to mi account is sufficient?
I remember I messed around with this when I tried to unlock my Poco F1 at the time.
Thanks
Bram
Click to expand...
Click to collapse
Good question... I think we should hook once, that's how I unlocked. But I feel it should work without hooking as well.
Anyone should test it and update for us the other way.
When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?
working on miui 13 android 12?
paulboqs said:
working on miui 13 android 12?
Click to expand...
Click to collapse
you may go through the last thread in my post for miui 13 related rooting. this guide is for miui12 rooting and there is no TWRP yet for miui13 for our device
at what point exactly will all my data be wiped?
yuukiw said:
at what point exactly will all my data be wiped?
Click to expand...
Click to collapse
the moment u hit unlock after your waiting period...
sasaboor64 said:
the moment u hit unlock after your waiting period...
Click to expand...
Click to collapse
is there a way to back upp all apps + data?
MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?
m38d1 said:
MIUI13 Android12 How to enter bootloader?
I'm try but FASTBOOT "orange" Showing?
how to enter bootloader? any driver or any solution?
Click to expand...
Click to collapse
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.
AwkwarddWhale said:
When i download the TWRP and boot into TWRP (through fastboot boot "twrp.img"), my touch screen will not work anymore. How could i fix this?
Click to expand...
Click to collapse
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.
Jctatis said:
did you found a solution?
this is the first time this happen to me since mi3, RHnote5,7, pocox3nfc, mi11tpro.
tactil isn't working as soon i ented the twrp.. and theres no orange fox for this devices.. shame.
Click to expand...
Click to collapse
There is no solution, there is no twrp for Android 12 / MIUI13 yet.
Well I did manage to make it work using a mouse otg. But it useless since theres no storage to flash
mm_rajesh said:
Please make sure you are having latest ADB installed on your machine. The best option is to install Android Studio . Secondly make sure to enable USB debugging .
You can reboot to fastboot through adb commands.
Once you are connected to ADB enter the command below.
ADB reboot Bootloader.
This will reboot to fastboot mode.
Fastboot devices
The above command shows whether you are on fastboot or not.
Now open the unlock tool and unlock your bootloader. Else if you are confident in recovering your device. use the command below
Fastboot flashing unlock
Hope the above helps.
Click to expand...
Click to collapse
thanks
The problem was the phone cable
This TWRP from the first post is Android 12 too?
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
I cant go to service center as my device is out of warranty
in google there is a pc program than can unlock bootloader of mediatek devices, search for it
Bro i cant access the bootloader, so unlocking it doesnt make any difference
I want to restore the bootloader.
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
Okay so first of all download "mtk client"
Than open the mtk client
It will give you instructions on how to connect your phone, take back of everything except system(super),vendor and userdata. Tap on flash tab there you'll notice a option called unblock bootloader tap on it and your bootloader will be unlocked
Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.
Manmeet_2008 said:
Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.
Click to expand...
Click to collapse
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .
Ok bro thanks for your help
tutibreaker said:
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .
Click to expand...
Click to collapse
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
try some sp flashtool that come with miflashtool , turn off phone and press volume- and plug the cable in , some type of mtk download mode
Ok bro i will try tomorrow
Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?
Manmeet_2008 said:
Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?
Click to expand...
Click to collapse
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first
tutibreaker said:
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first
Click to expand...
Click to collapse
Ok bro thanks for telling, will not use it for flashing
Did it work is it debricked?
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
You need to sSee this video,
Make sure Disconnect your phone battery then start flash
hookkrox said:
You need to sSee this video,
Make sure Disconnect your phone battery then start flash
Click to expand...
Click to collapse
You need to see the PM I've sent to you. You will find it here.
Start from BROM mode - that is always available. Then you can use mtktool to restore everything. I have an article about it on my blog, but I am not supposed to post it here... find it in my profile, or send me a PM for help.
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Sheist! said:
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Click to expand...
Click to collapse
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Edit:
I saw this in another thread, we have the same problem.
KMS45 said:
Hello to everyone,
So basically i read all the 10 pages of this thread and I have not found someone that have the same problem as me. I have the “bootloop” but the thing is that my phone is not even turning on. It is just booting and going back to the recovery menu. So I choose the reboot option but still coming back to the menu. I have already turned on the debug usb option because I used to be using it before my phone dies. I have a Xiaomi MI10 Lite 5G. I also tried the MiAssisstant but no succes because device not detected.
If someone have a solution without wiping all my precious data pls ?
Click to expand...
Click to collapse
KMS45 said:
Here is a video to understand what is happening when:
Reboot:
https://imgur.com/a/rB9QhSZ
Safe Mode:
https://imgur.com/a/X0KH5AD
Click to expand...
Click to collapse
mhegz said:
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Click to expand...
Click to collapse
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Sheist! said:
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Click to expand...
Click to collapse
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
mhegz said:
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
Click to expand...
Click to collapse
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Sheist! said:
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Click to expand...
Click to collapse
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
mhegz said:
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
Click to expand...
Click to collapse
Then ignore my steps, since they won't work on a locked bootloader. I will defer to others who have clues regarding a locked bootloader and a down system.
You COULD try to unlock it, but that would definitely wipe all your data:
"Unlocking the bootloader will wipe all data"
Get the unlock tool and instructions here, if you so choose anyway:
Apply for permissions to unlock Mi devices
en.miui.com
NOTE: that gives you unlock version 6.5.224.28 but it might/should prompt you after install to install the updated version since mine is 6.5.406.31 from April of 2022. When you run it, it makes you wait a week.
NOTE 2: It does state this warning, however:
"First, confirm that your device can be unlocked
Your device functions normally and not in a bricked, soft-bricked, bootloop state."
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
I am facing same problem my phone is stuck in recovery mode it keeps rebooting I have tried selecting safe mode recovery reboot but it keeps rebooting did you find a solution to this problem please let me know.Thank you.