Related
Hello everyone, just get frustrated right now my brand new 5X Half-Bricked after trying to flash stock fastboot firmware of the A1 through EDL with mi flash. just over excited of this devices, as i'm not a new one on this stuff and things, so that i ignoring some post said that the mi A1 rom won't run/boot compatible with 5X. (some interesting post right here about 3 Variants Hacked Bootloader http://en.miui.com/thread-840402-1-1.html)
I put whole things needed togather (fastboot firmware of A1, and Mi5X, also Twrp and some of unbrick zip from the thread above) so i was thinking when everythings gone crazy and bad i just need to reverting back to stock fastboot firmware of MI5X and everything works fine.
i do backup my QCN file so the worst thing i losted the imei and baseband i just need to restore that backup. Then i start the stupid things with proud.
flashing the Mi A1 sucessfully without any error on mi-flash then power it on boom, as i predicted it won't be as easier and simple as that step. some error text appeared on my screen some related to bootloader things, okay i just go into fastboot and unlocking with type "fastboot oem unlock" done with success and thats also said in terminal. okay then i rebooted (no panic at all), so the warning text still, then appeared your system has been destroyed, okay than i put the mi A1 recovery and flashing that through the fastboot, its said error no such partitions "recovery"??? (bit panic here) but trying to type "fastboot boot tissot.img" (tissot the codename of A1) its boot and send me into recovery, flashing some A1 rom for 5X from xda still won't boot at all (start panic here ).
so everything i try here flashing stock miui also won;t even boot and see the homescreen. I give up and OK i just need to flash the stock 5X through EDL, rebooting to edl and then flashing the stock 5X and success flashing done without any error, so i rebooted but its only stuck at MI logo then restart itself (really PANIC), so i get into recovery (stock MIUI) and mybe wiping whole data and cache will help, but there's no changes still restart/rebooting itself , okay i need to flash again this time i downloding Develover versions, and put the devices into edl through test point this time (as now the bootloader are relocked after flashing the stock one).
after flasing done the device still won't even boot at all just stuck at MI logo, now i really need help anyone any advices will really help, thanks
SH1M4BD3 said:
Hello everyone, just get frustrated right now my brand new 5X Half-Bricked after trying to flash stock fastboot firmware of the A1 through EDL with mi flash. just over excited of this devices, as i'm not a new one on this stuff and things, so that i ignoring some post said that the mi A1 rom won't run/boot compatible with 5X. (some interesting post right here about 3 Variants Hacked Bootloader http://en.miui.com/thread-840402-1-1.html)
I put whole things needed togather (fastboot firmware of A1, and Mi5X, also Twrp and some of unbrick zip from the thread above) so i was thinking when everythings gone crazy and bad i just need to reverting back to stock fastboot firmware of MI5X and everything works fine.
i do backup my QCN file so the worst thing i losted the imei and baseband i just need to restore that backup. Then i start the stupid things with proud.
flashing the Mi A1 sucessfully without any error on mi-flash then power it on boom, as i predicted it won't be as easier and simple as that step. some error text appeared on my screen some related to bootloader things, okay i just go into fastboot and unlocking with type "fastboot oem unlock" done with success and thats also said in terminal. okay then i rebooted (no panic at all), so the warning text still, then appeared your system has been destroyed, okay than i put the mi A1 recovery and flashing that through the fastboot, its said error no such partitions "recovery"??? (bit panic here) but trying to type "fastboot boot tissot.img" (tissot the codename of A1) its boot and send me into recovery, flashing some A1 rom for 5X from xda still won't boot at all (start panic here ).
so everything i try here flashing stock miui also won;t even boot and see the homescreen. I give up and OK i just need to flash the stock 5X through EDL, rebooting to edl and then flashing the stock 5X and success flashing done without any error, so i rebooted but its only stuck at MI logo then restart itself (really PANIC), so i get into recovery (stock MIUI) and mybe wiping whole data and cache will help, but there's no changes still restart/rebooting itself , okay i need to flash again this time i downloding Develover versions, and put the devices into edl through test point this time (as now the bootloader are relocked after flashing the stock one).
after flasing done the device still won't even boot at all just stuck at MI logo, now i really need help anyone any advices will really help, thanks
Click to expand...
Click to collapse
I think you should not unlock the bootloader using the command fast boot OEM unlock,you should go to http://en.miui.com/unlock/ here and download the app to unlock it, and when you flash a new rom which is not miui,you must keep it unlock,do not fastboot OEM lock,that will cause it can not go into system and stuck in logo
linjike said:
I think you should not unlock the bootloader using the command fast boot OEM unlock,you should go to http://en.miui.com/unlock/ here and download the app to unlock it, and when you flash a new rom which is not miui,you must keep it unlock,do not fastboot OEM lock,that will cause it can not go into system and stuck in logo
Click to expand...
Click to collapse
Nope, that's the basic things and i really know how it works, As for now i''ve no ways to go / reach the homescreen at all, so i can't put my mi account in setting and linked the device into my acccount, its useless using the miunlock tools. And i can only do that commands right after i converted mine to A1 firmwares.
hi, finally, i know what problem you met, because i have met the same problem, the solution is ,you go to the fastboot ,first unlock the devices, then fastboot reboot,then you find you go to the system, then you go back to fastboot,and last ,you need to use the miflash to flash the rom,and it should work fine now,it seem when you are locked,the miflash can not really work
Last news, damn lucky bastard i'am got replaced units, lets see does we'll have some aosp goodies soon..
linjike said:
hi, finally, i know what problem you met, because i have met the same problem, the solution is ,you go to the fastboot ,first unlock the devices, then fastboot reboot,then you find you go to the system, then you go back to fastboot,and last ,you need to use the miflash to flash the rom,and it should work fine now,it seem when you are locked,the miflash can not really work
Click to expand...
Click to collapse
Hi, it happened to my mi note 3. But not able to unlock in fastboot or mi unlock tool (prompted me adb been blocked by other program) . It's good if you able to help me. Thanks in advance.
Sent from my Redmi Note 4 using Tapatalk
samgcw said:
Hi, it happened to my mi note 3. But not able to unlock in fastboot or mi unlock tool (prompted me adb been blocked by other program) . It's good if you able to help me. Thanks in advance.
Click to expand...
Click to collapse
Use the mi unlock tool ,you can only unlock the phone when you are in fastboot mode,,turn off the phone,press the power and volume down bottom simultaneously,and you will be in fastboot mode
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/
I was just installing Twrp on my Redmi note 9, But it then got stuck on redmi logo, I successful;yy unlocked bootloader but then twrp so it got stuck on logo, It keeps looping and does not turn off, Unable to go to fastboot recovery and not normal system, as it was under warranty so i took it to the service center they kept it for one day, now they are saying that its vbmeta chip or img is once modified and now can't be repaired, and they also said unlocking bootloader has void warranty.
ABLOLX said:
I was just installing Twrp on my Redmi note 9, But it then got stuck on redmi logo, I successful;yy unlocked bootloader but then twrp so it got stuck on logo, It keeps looping and does not turn off, Unable to go to fastboot recovery and not normal system, as it was under warranty so i took it to the service center they kept it for one day, now they are saying that its vbmeta chip or img is once modified and now can't be repaired, and they also said unlocking bootloader has void warranty.
Click to expand...
Click to collapse
Everything you need to do is relock bootloader and flash the stock miui again and you got warranty back.
Did you try to follow my guide ?
[GUIDE][UNBRICK] How unbrick your bootloop in MERLIN after flashing TWRP (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
If you try to flash the file misc.bin your device can be in bootloop forever, please follow this guide to fix it. It works with: - Xiaomi Redmi Note 9 - Xiaomi Redmi 10X 4G Method 1: Once your device is on the black screen, plug it on USB (try...
forum.xda-developers.com
i have the same problem
my pc isn't detecting my phone at all and i can't enter fastboot mode or shut it down
As linked by @VD171 you have to delete the misc partition created by the incompatible TWRP, so do:
1 - turn on your phone, your screen probably is black, but connect to your pc and do:
adb devices
2 - it should detect the device, then do:
adb reboot bootloader
fastboot devices
fastboot erase misc
after that you should be able to restart to fastboot mode again
so yeah dsu loader plop No valid system found. cant unlock bootloader, recovery not booting. nothing
I'm in the same, no recovery, no system and bootloader blocked, already tried flashing different stock roms which are supossed to be signed by Moto and nothing works, can't wipe userdata, can't unlock bootloader, can boot imgs. I think the only solution would be to to a blanflash but I can't find a way to boot the device into EDL mode neither, did you find any solution?
Ar-Dinthalion said:
I'm in the same, no recovery, no system and bootloader blocked, already tried flashing different stock roms which are supossed to be signed by Moto and nothing works, can't wipe userdata, can't unlock bootloader, can boot imgs. I think the only solution would be to to a blanflash but I can't find a way to boot the device into EDL mode neither, did you find any solution?
Click to expand...
Click to collapse
[SOLVED] Recover Moto G50 from hardbrick state (stuck in EDL)
Hallo Moto Users😃 Last few days, it was a nightmare to find some ready and working solution on hardbricked Motorola. After 5 or 6 days finally bootloader screen appeared😎 Just to mention - until one week ago I was just and only Samsung user for...
forum.xda-developers.com
Check this out. U may only need to start from booting into edl mode
My phone stuck at miui logo after using dsu sideloader. i reset the phone and thought it is the problem of dsu sideloader but when i use the offical android dsu loader, my phone stuck miui logo again and i need to reset again. Why does it happen?Anyone have similar experience?
I think the reason is that i remove some system apps with universal android debloater.