so somehow i install an apk which is a game and the following day in my pocket i felt that my phone restarted by itself (maybe because the pressure in my pocket clicked restart lol) and after that i thought it was a regular restart but 20 mins has gone it is still booting but the booting look like it is updating rom..... so maybe i thought drain the battery and it will all be good on the next charge.. but unlucky it was bootloop.... huhu.. so i did what the youtubers do test point is the only way.. so when i try the test point 1st my computer keeps on searching for software update when QHUSB_BULK and when i canceled it it became a Qualcomm HS-USB 9008 but there was a caution sign.. miflash could not read it it says code 52..
what to do?
sry no pictures.. but atleast i gave all the details..
ty
Here are two link I found to flash ROM on locked bootloader.
Read carefully and do it on your risk.
If your device in warranty then it's better to take it to xiaomi service center.
Flashing guide's.
1. http://en.miui.com/thread-835254-1-1.html
2. http://en.miui.com/thread-720781-1-1.html
See if those work for you, I am not sure internal data will be retain or not but it should help you out to flash ROM.
Related
I flashed twrp, but the device got bricked, then I put the phone into fastboot then I typed "fastboot reboot fastboot" and it didn't enter that mode, it got into Redmi logo screen and then it turns off buy itself. it has that bootloop. and now I can't make it to enter to fastboot again to flash it. I can't do anything
it's a redmi 9 lancelot
Bring it to your dealer,when u cant enter nothing than its hard bricked i think(tell me if i am wrong)and as far as i know this can only be solved by a certified seller,but not 100% sure.
One thing from me to you.
Dont flash unstable software on your phone when u not know what u do,in special MTK devices.Good luck.Cheers!!!!
-CALIBAN666- said:
Bring it to your dealer,when u cant enter nothing than its hard bricked i think(tell me if i am wrong)and as far as i know this can only be solved by a certified seller,but not 100% sure.
One thing from me to you.
Dont flash unstable software on your phone when u not know what u do,in special MTK devices.Good luck.Cheers!!!!
Click to expand...
Click to collapse
I bought it on a kiosk in my country so it's gonna be harder to find someone. I thought it was gonna be a way to force to enter to fastboot, but it's impossible. I know there are some guys that can fix it by teamviewer
omg, what did u just do?
i am waiting for the official of twrp because theres a huge possibility of bricking your device.
before you do anything to your device you must read many articles on how to recover it. also read all the comments below the articles because some users have their experience installing the software.
back to the topic:
after you bricked your device you were able to go to fastboot but something went wrong because you soft bricked your device then you want to go to fastbootd.
thats was the wrong move you did to your device.
note: if theres a bootloop or something went errors after installing custom rom and you can able to access fastboot. this is the only thing you need to do, use miflashtool and install default firmware.
some users flashing the meta if theres a bootloop on their device, but for me the very secured step is flashing default firmware in his compatible tools like miflashtool.
search shas post to unbrick your device. try it since your device got bricked.
mhark.moby said:
omg, what did u just do?
i am waiting for the official of twrp because theres a huge possibility of bricking your device.
before you do anything to your device you must read many articles on how to recover it. also read all the comments below the articles because some users have their experience installing the software.
back to the topic:
after you bricked your device you were able to go to fastboot but something went wrong because you soft bricked your device then you want to go to fastbootd.
thats was the wrong move you did to your device.
note: if theres a bootloop or something went errors after installing custom rom and you can able to access fastboot. this is the only thing you need to do, use miflashtool and install default firmware.
some users flashing the meta if theres a bootloop on their device, but for me the very secured step is flashing default firmware in his compatible tools like miflashtool.
search shas post to unbrick your device. try it since your device got bricked.
Click to expand...
Click to collapse
Youre so right,nice written!!!
mhark.moby said:
omg, what did u just do?
i am waiting for the official of twrp because theres a huge possibility of bricking your device.
before you do anything to your device you must read many articles on how to recover it. also read all the comments below the articles because some users have their experience installing the software.
back to the topic:
after you bricked your device you were able to go to fastboot but something went wrong because you soft bricked your device then you want to go to fastbootd.
thats was the wrong move you did to your device.
note: if theres a bootloop or something went errors after installing custom rom and you can able to access fastboot. this is the only thing you need to do, use miflashtool and install default firmware.
some users flashing the meta if theres a bootloop on their device, but for me the very secured step is flashing default firmware in his compatible tools like miflashtool.
search shas post to unbrick your device. try it since your device got bricked.
Click to expand...
Click to collapse
I had tried that twrp before, the new thing I did was to flash a new rom, then the rom got stuck in the logo, so i asked the creater how could i solve it? He told me to flash permessive. That's why I installed twrp. But i saw twrp wasnt working. I went to fastboot to flash my software, but as you told me i went to fastbootd too. I took it to repair. I hope the can do something
try to hard reset Bro.
fastboot reboot fastboot is wrong. fastboot reboot bootloader is right.(op)
I decided to exchange it for a Redmi note 9s since I saw the development is better for that cellphone, even xiaomi mitool v2 is showing me an official twrp recovery and magisk root. Im just waiting to unlock my bootloader. btw is this a MTK device too? i heard mtk devices gets brick easily as it happened with my redmi 9
RodrySmoke said:
I decided to exchange it for a Redmi note 9s since I saw the development is better for that cellphone, even xiaomi mitool v2 is showing me an official twrp recovery and magisk root. Im just waiting to unlock my bootloader. btw is this a MTK device too? i heard mtk devices gets brick easily as it happened with my redmi 9
Click to expand...
Click to collapse
No idea why all have problems with MTK devices.
I SAY IT AGAIN AND AGAIN,YOU MUST REALY KNOW WHAT YOU DO ON THIS SOC,I HAVE SOME PHONES WITH MTK SOC AND I HAVE FLASHED AND BRICKED IT LIKE REDMI 9 NEARLY HUNDRED TIMES BUT HAVE NEVER A DEAD DEVICE AND I TEST MY THINGS AND ALL WHAT I SEE WHICH INTERESTING.
To your phone:
It have a Snapdragon 720G on board,not realy a killer but hey its Quallcom.Cheers!!!!
yeah, I do think the problem was because the twrp was bad, and I didn't flash the rom expectantly when I knew it, it was bad. that's my lesson I learnt, everytime it doesn't boot properly, I'm gonna flash the stock rom again
admin3453 said:
I flashed twrp, but the device got bricked, then I put the phone into fastboot then I typed "fastboot reboot fastboot" and it didn't enter that mode, it got into Redmi logo screen and then it turns off buy itself. it has that bootloop. and now I can't make it to enter to fastboot again to flash it. I can't do anything
Click to expand...
Click to collapse
Disable authorization and unbrick your Redmi 9
Now you can unbrick your device even if the redmi logo not coming..just go to below link and follow their steps.... https://megafon929.github.io/mtk For more information and how to do follow the below post...
forum.xda-developers.com
Hello! My phone became bricked out of nowhere and i have no idea how to get it to boot again. I am not sure what exactly could have caused it, it happened when i unlocked my phone in the morning and the phone shut off when i touched the screen, it tried to reboot for some time then it went straight into fastboot and i have tried everything i could to get it out but i didn't succeed. The phone responds to some fastboot commands, unless they involve writing, in which case it either returns: "command write failed (no error)" or gets stuck at the writing phase and does nothing. I tried QFIL and MiFlash and both failed as well (MiFlash also reads different physical memory usage in every log), i will include screenshots for refference.
Or is there any chance that the issue is caused by the flash? The phone is around 2 months old so i could try and get it repaired. The phone was running Resurrection Remix 8.6.9 with Englezos kernel and Magisk. It is the first time i faced such a severe issue so if there is any information i left out, feel free to point it out and i'll provide what i can.
Thanks in advance for any help!
Hi, same goes happened to my 9T, ive tried so many flash toos but didn't works,
Last flasher i tried is xiaomi flash tools but its required user id and password account that only available for service center.
Finally i sent my phone over, that is the best option
Hey i spend today a lot of time to tried to fix my bricked Redmi Note 10 5G.
I just wanted to unroot my phone but i did something wrong.
First problem i have is the dm-verity corrupt.
So i read and tried this
https://forum.xda-developers.com/t/...g-bricked-but-has-access-to-fastboot.4366655/
Without succes i flashed the right firmware for my device many times but the dm-verity corrupt is still there and then i keeps hanging in the redmi boot logo.
But i dont know how but now i also got my bootloader locked so now i cant flash any thing.
And the dm-verity corrupt and keeps hanging on the redmi bootlogo.
So i hope some one have an solution for me and can help me and fix my phone.
u have made a common mistake. u have flashed firmware with miglash, without change default option to flash all. you have select flash all and lock. so yout phone is hard bricked. i think theres a guide to solve this. search on this forum
wetito said:
u have made a common mistake. u have flashed firmware with miglash, without change default option to flash all. you have select flash all and lock. so yout phone is hard bricked. i think theres a guide to solve this. search on this forum
Click to expand...
Click to collapse
Hey thanks for the reply
i know i made a mistake and i search and tried anything what i thougt it is maybe a solution on this forum.
Bun without any succes and because my bootloader is locked now i cant do anything in the fastboot.
i dont know how to unlocked now.
Because the bootloader is locked now i think i have the Guarantee now but if the i boot the phone the dm-verity corrupt message is still there and then it keeps hangin on the redmi logo.
So if there is no way to fix it i think go trie it to bring it to the store where i bought it 2 months ago.
i think you can solve using mtk spflash tool
look here, u can find the solution
Soft Bricked Phone
Hello, I need help. I tried to flash back to stock firmware using mi flash tool but it said error and it failed. I tried to flash again and then it didn't detect the device. It rebooted on its own and now it's stuck on bootloop with black...
forum.xda-developers.com
Hey thanks for the
wetito said:
i think you can solve using mtk spflash tool
look here, u can find the solution
Soft Bricked Phone
Hello, I need help. I tried to flash back to stock firmware using mi flash tool but it said error and it failed. I tried to flash again and then it didn't detect the device. It rebooted on its own and now it's stuck on bootloop with black...
forum.xda-developers.com
Click to expand...
Click to collapse
Hey thnks gor this guide but i cant get it found it in the sp flash tool.
I dont get my phone in the BRom mode to find it so im stuck there tried servel of times when it power of to get my phone BRom mode how dos the screen look if its in BRom mode ?
By pressing the vol + vol - and pwr button when its off id ont get it in the BRom Mode.
Also i googled the sp flash tool to download it so maybe i dont have tight one do you have mabe some links for me?
Or is there maybe a other way to fix my phone?
try this tool. seems very good. but i didn't never used. so you had to try by yourself. it have many interesting and usefull function
Home - Tool All In One
TOOL ALL IN ONE This tool support 67 different devices of some different OEMs. DOWNLOAD CHANGELOG XDA THREAD OTHERS PROJECTS
toolaio.tk
wetito said:
try this tool. seems very good. but i didn't never used. so you had to try by yourself. it have many interesting and usefull function
Home - Tool All In One
TOOL ALL IN ONE This tool support 67 different devices of some different OEMs. DOWNLOAD CHANGELOG XDA THREAD OTHERS PROJECTS
toolaio.tk
Click to expand...
Click to collapse
That also didn't work do i go to reseller today and hope i hot a new one of the gonna fix it.
Becuase the bootloader is locked again warrenty only the dm-verification message is there.
Do gonna say i updated my phone and now its not booting anymore.
Or do you or maybe some one do have an tutorial program or tool to fix it.
Download ROM for your phone and extract to desktop. Reboot to fastboot and open flashall.bat. it should run firmware through and reflash phone completely. Boot phone and on boot screen keep pressing power so phone can boot and bypass DM Verity error. Once booted reboot into fastboot again and enter fastboot oem cdms. Reboot phone and DM Verity should be gone.
passion8059 said:
Download ROM for your phone and extract to desktop. Reboot to fastboot and open flashall.bat. it should run firmware through and reflash phone completely. Boot phone and on boot screen keep pressing power so phone can boot and bypass DM Verity error. Once booted reboot into fastboot again and enter fastboot oem cdms. Reboot phone and DM Verity should be gone.
Click to expand...
Click to collapse
we repeats same anawers continuosly.i dont understand why some users decide to mod their devices, if they dont know how to use Google, and don't understand how to follow the flashing guides step by step. and finally after flashing custom rom, they ask how back to stock
wetito said:
we repeats same anawers continuosly.i dont understand why some users decide to mod their devices, if they dont know how to use Google, and don't understand how to follow the flashing guides step by step. and finally after flashing custom rom, they ask how back to stock
Click to expand...
Click to collapse
Get what you are saying, think there is at least 8 threads on same topic.
Hey thanks for the answers and the things i could tried to fix my phone.
im not a noob with rooting and flashing android phones before i do flasshong or rooting and the other stuff i always read and check the xda forum before i do.
With other android phones that i had before i made some misstakes before but like a bootloop or something else that the phone not was booting but always i can fix the phone.
So the problem what i had with my Redmi note 10 5G and not one solution that i found on xda or something that maube could fix the problem nothing could fix it.
So i a couple of week ago i went to the reseller and they send it to a repair center.
I think the coudnt also fix it because the did a boardswap.
I think if they cam fix it with a tool or software and reflashing the phone they did.
Now i wait some time before i go rooting or flashing stuff on my phone i hope there will be good twrp so thning go musch easier in the future to fix stuuf like (DM-VERITY Corruption.
twrp is not necessary. fix dm-verity is easy. the are MANY MANY MANY post where is explained how to do. root new phones is dofferent but not complicated. magisk works fine if installed following the latest guides. it's impossible damage mainbord after a root procedure. sure you didnt follow the guides with attention. i have rooted my global phone many times without problems. simply you have made a bad flash of vbmeta or product partition. you made a big mistake, cause this devices can be rooted without brick
Good afternoon,
I had bricked this Redmi Note 9 and it was stuck on bootloop, I tried to sort this a while ago and gave up.
After looking through the forum i followed instructions how to place a new ROM onto the device, Once i was doing this someone unplugged my phone and now it is stuck on dm-verity corruption.
The Fastboot does no longer show the bunny it only states FastBoot.
I need major help on this urgently can anyone advise
Try this:
[VBMETA][IMG][PATCHED] VBMETA Image Partition: Disabled verity & Disabled verification for MERLIN (Xiaomi Redmi Note 9 / Xiaomi Redmi 10X 4G)
PATCHED VBMETA.IMG for MERLIN by VD171 For what do I need it ? If you try to flash any custom partition, your device can bricks or gets in bootloop. This patch with disabled verity and disabled verification avoid it and need to be flashed once...
forum.xda-developers.com
I have looked at your information but this does not help me.
It seems that whilst it was trying to flash it was unplugged which has switched the USB Debugging off, Therefore i cannot get into the phone via USB
Unless someone can advise otherwise i believe this phone is now finished and will never work again.
Gutted!
BigR1992 said:
I have looked at your information but this does not help me.
It seems that whilst it was trying to flash it was unplugged which has switched the USB Debugging off, Therefore i cannot get into the phone via USB
Unless someone can advise otherwise i believe this phone is now finished and will never work again.
Gutted!
Click to expand...
Click to collapse
No one device is "finished" while their parts are working fine.
Damage due to misuse are totally reversible.
What would you suggest then?
Just flash any stock miui rom.
I managed to get past the corruption.
However i am now met with two bootloops, Followed by safemode and then the error NV DATA CORRUPTED
Just format/erase nvdata.
How do you do that?
BigR1992 said:
Good afternoon,
I had bricked this Redmi Note 9 and it was stuck on bootloop, I tried to sort this a while ago and gave up.
After looking through the forum i followed instructions how to place a new ROM onto the device, Once i was doing this someone unplugged my phone and now it is stuck on dm-verity corruption.
The Fastboot does no longer show the bunny it only states FastBoot.
I need major help on this urgently can anyone advise
Click to expand...
Click to collapse
I had the same issue. This video is what fixed my phone from hard bricked. Don't forget that volume up + volume down must be pressed together, and it must be plugged in whilst pressing the buttons. It's also used to detect the driver. You have to be quick when you see MediaTek. Follow the instructions and you'll see. Python must be installed from the Microsoft Store as the version provided is outdated. Good luck bro. Sorry you had to wait months for someone to experience the same problem. I'm fighting with dmverity right now. lol.
Recently hard bricked my x7 max and while using MTK/SP tools gettings errors so need someone to help. I have seen so many people with same issues but no details troubleshooting guide here and also on YT.
Steps i took
Unlock bootloader(with stock rom and RUI4, Android 13, latest update)
Installed TWRP(found one twrp that actually worked but i was not able to backup the rom, showing errors while taking backup, error 255)
I thought i can revert on stock using SP tools so moved ahead
Once in TWRP, i installed Project elixir ROM and rebooted to bootloader, phone got dead.
I tried VCOM,linusb,SP flash tool and MTK Authbypass (brom waiting , maybe some issue in detect)
Today tried again(Somehow Brom was ok, but didnt get Authbypass message)
Tried multiple times but now it show error (image attached)
Need further assistance.
Didnt know how bad all these custom rom installing has become. In my days it was cool and fun without getting any errors( i was taking about 2015/2017....)
Kind of same thing happened to me 2 days ago. Trying to root the device and everything was fine until I restarted the phone. After that it just got hard bricked total black screen no realme logo, fastboot or recovery. Had to go into EDL mode and flash the offical rom. In my case there was no error in the mtk bypass tool and everything flashed without any errors. This time the phone booted normally and straight went to realme recovery mode and from there I just wiped the userdata and this time it got stuck in orange state(no realme animation logo). Although this time I could access the fastboot, so tried to install twrp but after flashing, nothing happened same stuck in orange state warning. After this again I tried to flash using mtk tool and after doing that everything remained same but I couldn't access fastboot anymore. The funny story is now I cannot even flash using mtk tool anymore. So, everything is ****ed, I don't think customer service can fix this, would be better to buy a new phone.
My experience with realme phone specially with mtk processor has been extremely bad , I faced errors after errors. Earlier I had redmi note 7 pro and it was excellent in terms of flashing roms and all. So many times I had bricked the device but could fix it no issues.
Anyway as I didn't faced this error I don't know how to fix this. I also used this exact same version also. Try using https://saransaro.com/SP_Flash_Tool_v6.2216_Win.zip . And see if this works.
Also, don't flash the scatter file of firmware after a.22 as it doesn't work for some reason . I used the a.22 one it worked fine.
Please let me know if you were able to fix it or not.