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
Related
Hai, view days ago i got bricked my phone, after i got replacement from distributor service center, this incident was started while my cell phone always hang randomly, then the bad things happened, my phone is no longer boot up, can't access twrp too,
I tried many trick to make my cell phone wake up but nothing happens,
I tried to flash with miflash (fastboot) with option clean all or clean and lock, it says error remote erase/write partition failed
I tried to flash with QFIL Download Qualcomm Flash Image Loader failed
Can't flash with command fastboot, all write failed
I tried with oem edl got error ACK Count don't match
I tried deep cable flash failed
I tried the last option with test point also failed
all also write/erase failed,
what i supposed to do to fix my phone
did you solve the problem? I guess i had the same...
I have a xiaomi mi a2 device which had bootloop all the time. I was not able to get into device at all. So in other words oem unlock and usb debugg was not active at all. I tried so many times to get into the phone just to activate those. Now since some other phones doesnt really need those to flash because they use different kind of flashing i asumed i wouldnt need those.
when i tried to flash using adb sideload which was available it couldnt flash it went to 47% and then it just failed or stopped with some message and 1.00x at the end. I did try couple of times without any luck. I was never awared that thus phone had project treble rom wich in turn have 2 partitions. I acted on impuls. Then i tried fastboot commands with error about failed not able to flash restriction. Then i found that you could flash using emergency download mode which is in my mind something lg has with shorting the pins. There you dont have any issues because emergency download mode in lg dont require any permission or any problem for you to make your degice alive again. You could do that how often you will.
now i assumed it was the same with mi a2 that it would write rom the same but automatically because in lg you need to flash particular files in order to make that method work. I did flash mi a2 in edl and it did flash but the result was catastrophic. I got message about some partition something while flashing was a success. Then i thought how can edl fail even if oem is locked. It shouldnt work like that. Then i tried and tried to unlick bootloader through fastboot but its impossible. From start it was impossible to activate those settings. Then now i figure it out that it must do something with project treble and those 2 partitions. Is there any way to make this phone alive again?? Is there any way to flash partitions and partitions table manually
P. S I flashed it with what i thought was the anwser about my problem. I flashed it with mi x6 recovery rom from xda which made whole situation worse. Now i dont even have adb option nor do i have option to roll back to stock.
Just for comparison, in google pixel phone you dont even need unlocked bootloader or anything for that matter to flash pixel phone as long the rom is stock rom. Adb sideload works flawlessly
Any help is appreciated
Hey!
So i'm making this post after battling over 4 days with my friends old oneplus 3t.
All started maybe year ago when my friend asked me for help because his oneplus had suddenly gone into a bootloop kind of state (he told me that the phone was in his pocket working fine and when he tried to use it next time it started acting up.) Before i could even help him he had already bought new iphone, so the oneplus stayed in his drawer until last week when i remembered it and started to try to fix it.
So first thing that i noticed was this message "The dm-verity is not started in enforcing mode and may not work properly", the message eventually went away and i got to a recovery mode and thought that this is gonna be easy, hooked the phone to pc and started adb and tried to sideload the official rom from oneplus site, but everytime i tried it went to maybe 47 %or 66% and failed eventually. So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
Downloaded Oneplus 3T unbrick tool v3.0, and qualcomm drivers (turned windows driver signature off) everything went great and the green text came in oneplus unbrick tool and i proceeded to start the phone in excitement and the circling bootlogo started and it just stayed there, nothing, and after while shut down.
Things tried now:
-Sideloading (many times with different roms) no success.
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
- Unbricktool v3.0 (Works like a charm everytime, but phone doesent still boot to os) no success
-recovery (wiped cache and all data many times) no success
My friend never flashed anything to this device, he doesn't even now how to do this kind of stuff.
Phone not dropped even once, is in a perfect condition and has all the original stickers even.
I have grown obsessed to fixing this phone, so any help is greatly appreciated :laugh:
onlyoneplusproblems said:
So i thought that ill try flashing original recovery.img, started fastboot and tried flashing and everytime "remote: Partition flashing is not allowed". Tried many times also oem unlock command and failed miserably, all i got was "remote: oem unlock is not allowed". Eventually trying every command from fastboot and adb i came to a conclusion that the device doesn't allow anything to be written to its storage (Tried of course flashing twrp, but same error).
-Fastboot (It recognizes the device everytime, but all other commands than "fastboot devices" end to an error"remote: something not allowed") no success
Click to expand...
Click to collapse
I haven't personally ever had to use the unbrick tool, so I can't help too much with the core problem. But what I can say, is that the steps I've quoted above (trying to flash recovery partition, etc.) are going to fail by design, since the bootloader is locked. This is the very purpose of the locked bootloader. The expected result is "remote: not allowed".
And as far as I am aware, you have to have a working OS and have "OEM unlocking" first toggled on, in the phone Developer settings. Otherwise (again, by design) the "fastboot oem unlock" command is going to fail.
Spontaneous failure of the phone to boot to OS, and dm-verity warning, to me probably indicates the OS has become corrupt/damaged. The damage is showing as a change to the system, therefore the dm-verity warning. Normally, I would tell you to flash the stock recovery image. But of course you have already tried that. Probably difficult to determine for sure. but spontaneous failure, and failure to flash recovery image (multiple times) may indicate a hardware failure such as bad emmc.
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authenticated mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
Click to expand...
Click to collapse
As redmi 9 is mtk based device so their is not any edl point...if you have authorized account then you can easily flash it without the device open
Just use older preloader.
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/
That I have an authorized account was a wrong information.
When I try to flash it with sp_tool the following error is displayed: STATUS_CRC_BROM_FAIL 0xC0060005
PeBeM said:
Hey together,
I bricked my phone, since I flashed the preloader.bin with ""SP_Tool" it does not boot anymore,
whether in device manager nor in other programs it is detected now.
I already had problems with installing "TWRP".
Maybe it all begun when Ifull wiped the device just after it [in recovery], what resulted in a bootloop.
Booting in recovery and fastboot was possible, but the touchscreen did not work anymore in recovery; multiple times i tried to install different roms and versions of "TWRP" via fastboot without success, but even this option is gone.
Is somebody out there who knows if it is possible to install a rom or at least boot the phone via edl again? [I have an authorized mi-account]
I know the two points [TM & ID] I have to connect, it seems to be simple but I am not sure if i do it right, at least my computer does not detect the phone.
And finally I created a little spark when I lost the grip with the paperclip i used to connect the two points, hopefully that was not the final deathsentence for the phone, but i do not think so may you can help me?
Best greetings!
Joel
[picture of the edl-points]
https://i02.appmifile.com/578_bbs_en/01/11/2020/ad52590657.png
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
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.