Hi, Guys. I have the Realme 7 pro. I did install the realme 2.0 ui with A11 in it. OK. everything was ok. Then I went back to the A10 realmeui 1.0 version of the software. The phone hard Bricked. Does not get in to the system. Does not get in to the recovery and the fastboot mode. I dont know what to do anymore.
I can only enter edl mode but I don't have an authorized id
If you could access fastboot mode, you could flash recovery and ROM from it, in case you have the bootloader unlocked. Otherwise you may manage to flash something from EDL mode using QFIL tool - firmware files and XMLs can be extracted from OFP firmware using extractor tool, but I suppose you may need some patched firehose binary file (I tried it with the one extracted from OFP, but it didn't work). Otherwise, you may try sending it to Realme service for reflashing or try to find some chinese/indian guy with credentials for MsmDownloadTool - I saw they charge about 5-20$ for doing that remotely...
qfil doesn't work, I've managed to solve the problem.
LEANDROMENDES said:
qfil doesn't work, I've managed to solve the problem.
Click to expand...
Click to collapse
Good to hear that you managed to solve it. Can you share some details about what you did, so that it can be helpful to somebody who will face the same issue?
I am in a similar situation with the only difference being that fastboot is working for me and i have unlocked bootloader.
i would greatly appreciate it if you told me how you managed to unbrick your device
Related
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
Hello everyone. A couple of days ago, I bricked my huawei mate 10 pro BLA-AL00 by flashing the wrong firmware. After a few days of experimentation, I was able to revive the phone by flashing the board software back onto the phone. Now the problem is that I am on a super early build of emui and it seems like its the stock factory software with a bunch of debugging programs on it. I am having some trouble updating the firmware to android 8. I downloaded this exact firmware file: https://androidhost.ru/bzx
I am having some trouble figuring out what files I need to flash. There is a main dload folder after extracting the files, but if I try to copy that onto a usb drive and flash it using the dload method, my phone will once again brick itself. I have tried flashing the all_cn firmware file using TWRP recovery, but that also bricks my device and puts it into a bootloop. I have also tried using the huawei update file extractor software and tried manually flashing the firmware using fastboot commands, but once again will just end up in a bootloop. Am i doing something wrong? I would really appreciate any help. Thanks
Hi,
I'm in the exactly same case. Did you manage to fix it?
iBen68 said:
Hi,
I'm in the exactly same case. Did you manage to fix it?
Click to expand...
Click to collapse
I finally managed to figure everything out after days of research and testing. You must download the BLA-AL00 8.1.0.351 full ota firmware from pro-teammt.ru and extract the update.zip folder. Next, I used MRT Dongle 3.19 cracked to flash the firmware. https://www.gadgetsdr.com/mrt-dongle-latest-crack/ To activate the program, you must use the keygen provided to generate a activation code after pasting in your device id. The device id can be found by opening the mrt program for the first time. Paste in the activation code found by the keygen into the activator and the program should open. Next, click on hw flasher and put your phone into fastboot mode. Make sure your bootloader is unlocked. I assume it is unlocked as you only flashed the board firmware. Under write flash click on the 3 dots near the bottom of the page, select the update.app file you extracted before, and click on start. Don't worry if it says fail for the first few commands. It should successfully flash everything else. Once this process is finished, your phone should reboot. We need to do one final step and write the oeminfo back into the phone. Put your phone back into fastboot mode by plugging in your phone and holding down the power and volume down buttons. In MRT, click on update hw soft_ver, select huawei mate 10 pro, and click on start. After flashing, your phone should reboot normally now into an operating system!!!
Thank you for your answer ! My Mate 10 Pro is BLA-L09, how did you know you have to use this specific firmware (BLA-AL00 8.1.0.351 full ota firmware) for your BLA-AL00? I guess I should use BLA-L09 full ota but which version?
iBen68 said:
Thank you for your answer ! My Mate 10 Pro is BLA-L09, how did you know you have to use this specific firmware (BLA-AL00 8.1.0.351 full ota firmware) for your BLA-AL00? I guess I should use BLA-L09 full ota but which version?
Click to expand...
Click to collapse
It took me a very long time and a large amount of downloading to figure out the exact firmware I needed to use. I just downloaded a bunch of version and see if it would flash onto my phone. Finally, the 8.1.0.351 firmware worked! For the bla-l09, im not too sure the exact version needed. I would experiment around and try a bunch of different full ota firmware from pro-teammt.ru Maybe you could flash the bla-al00 firmware and rebrand the phone? Im not too familiar with rebranding, but I know its possible.
I have tried with BLA-L09 8.0.0.115 firmware then my phone has reboot in a better factory version (EMUI 8 instead of EMUI 5), but still in factory mode, with the developpers apps. I've done the hw soft_ver update, but it still boot on this factory version. I've tried to flash another firmware (still BLA-L09 but another version), and now my phone stays shut down. I cannot even see it on my COM port. I've tried to use test point, I can hear the USB plug computer song but nothing happen. Phone no detected, black screen, no vibration. I've tested all the possible key combinaison (volume up, volume down, power button), still nothing .
Any idea of a last chance?
I was so close thank to your help!
Update 2021.01.24: I consider the problem mentioned here as solved, since it can be resolved with MTK Bypass explained in the Guides Section. BE CAREFUL however to ONLY choose "Download Only" from the dropdown box in SP Flashtool! DO NOT select anything with "Format" in it, else you will lose S/N, MACs and IMEIs!
--- Original post ---
Hi, I have hard-bricked my new Realme 6 while trying to root it with Magisk. At the moment I am stuck in a bootloop at the power-on logo (realme in white letters). The boot animation (yellow realme letters) does not appear, instead the phone reboots after ~35 seconds. The bootloader says "Orange State".
I can NOT enter fastboot nor recovery mode by any key combination. Holding Power and Vol- makes the string RECOVERY MODE appear for a split second in the lower left part of the screen, however nothing happens afterwards.
I can power down by holding Power and Vol+ an releasing them immediately after the screen goes blank.
Holding Vol- and Vol+ while the phone is off and connecting USB makes a USB serial device appear on a windows machine for about 1-2 seconds before it disappears again.
I am very thankful for any hints on how to unbrick the device.
Here's what I have done in detail to mess up the phone:
1. OTA-Update to the latest OS in my region (EU11.A.48)
2. Unlocked the bootloader with the realme In-depth Test app (everything fine so far)
3. Download stock firmware RMX2001EU_11.A.48 ozip from realmeupdater.com
4. Unzipped with gnu unzip (content was readable, no extra decrytion tool for the ozip needed?) and extracted boot.img
5. Installed Magisk Manager and uploaded boot.img to the phone
6. Patched boot.img with Magisk Manager (and if I remeber correctly DIDN'T UNCHECK Preserve AVB 2.0/dm-verity)
7. Certainly FORGOT to do anything with vbmeta.img
8. Did NOT erase cache and userdata
9. Flashed patched boot.img directly and WITHOUT --disable-verity or --disable-verification
10. Rebooted the phone.
Am I correct that my problem is the AVB/dm-verity part?
Why does the modified boot.img affect the recovery (I thought they were seperate)
Can I try something with SP Flashtool?
I do have a second intact device that I didn't dare to touch yet, if that helps resolving the issue (e.g. for SP Flashtool readbacks).
As said any advice is highly welcome. Please ask I you need any more information to help.
I did that too... Magisk patched boot .img process of rooting is the risky process , I bricked my device, got it into red state.. tried thick and thin to revive using various flash tools, unable to do it, finally went to a shop , got it fixed, go-to a good repair shop, if you go to the service center, they will say replace motherboard for 5 k , I hope it helps, do traditional unlock bootloader TWRP recovery then flashing Magisk zip method for rooting process.
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Yes, you are right , red state means that, I guess bcoz, I may have formatted it and ran again unlocked bootloader but it showed unlocking failed, but I thought that I had previously unlocked it so it should be unlocked but I forgot to do that app thing process of deep test again, and I was on Android 10 latest and patched boot img of previous version using magisk, now I understand what mistake I made, I should have used boot IMG of current version of a 10 , but still I am afraid of doing this magisk method of rooting by patching boot IMG bcoz repair cost me 800/- , and I found out on YT that the latest version of a 10 of my device doesn't readily allows twrp and flashing zip of magisk.... Plus there are half baked info on important things, this is new device for me, I have had rooted Samsung and Lenovo, but rooting this is kind of tricky, bcoz it's still new, I think.... Want to try .... But I m afraid.... Tried fastboot method of TWRP flashing but can't replace stock room, so I guess I can't root .....
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
cmfan said:
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
Click to expand...
Click to collapse
Thnx man, I have rmx 1825 , but the process would be same for my device, I would have to search for it...
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
daeSundae said:
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Click to expand...
Click to collapse
I think there is no Emergency Download Mode in Realme devices.. pls guide ...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
daeSundae said:
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thnx that's a life saver, I am afraid to go forward with the device, this is promising, I will try, I found out that the new version c17 os Android 10 I am unable to root by twrp magisk zip flashing method, twrp isn't installing, there's an .ofp extracter, but it gives virus with software, unable to do, even talked on WhatsApp and gave him Gmail id, will try this method , I wanted the SP flash tool method, it's simple and can readily restore the stock rom... Thnx Sundae.. daesundae ... What kind of name is that...?? .. chuckles...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
cmfan said:
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
Click to expand...
Click to collapse
I saw everything that You posted, incidentally the YouTube video on this is on rmx1825 , thnx, whatever you posted it helped..
Hi guys, I did something very stupid, flashed the wrong boot.img and ended up completely bricking my device. I tried changing the active partition to see if it would boot, that didn't help.
I was on the latest august update of official android 11 . Then I found a boot.img I found online, but apparently it wasn't from the exact same rom. The phone booted but no WIFI.
It wouldn't allow me to flash any update through settings - system update hence I decided to try to use a fastboot rom....tried that, but the process when I hit flash_all.bat gives a lot of FAILED (remote: Flashing is not allowed for critical particions) or FAILED (Error reading sparse file)....what am I doing wrong?
I can't do anything except get in fastboot.
Is there any way I can get the phone to work agan? Needless to say that as the idiot I am the whole phone is wiped so this doesn't matter anymore. As long as I can get it to work.
Please advise and thanks (The phone is OP7T Pro ME european).
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
leginhee said:
You can use this tool: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
Click to expand...
Click to collapse
Thanks the problem is i can't get it to start qualcomm edl. I power off, press both vol buttons and conmect to usb but nothing happens. What am i doing wrong?
Qualcomm edl Mode is just a blackscreen
"I can't do anything except get in fastboot."
Your Bootloader was unlocked ?
You can try fastboot reboot edl.
Or you can find a ROM that works, extract all images and flash all of them.
I have a similar problem.. kind of. I just flashed a rooted boot to my phone but there is no wifi at all, and since i dont have a SIM card im not getting any updates. the Boot.img came from the oneplus software update and i did the payload dumper. Since I have rooted it ive lost the wifi capabilites. (its the 7T pro me international.)
Hi, is there a possible way to flash with Huawei Smartphone Multi Download?
When I reboot to edl, the drivers are working fine (I unlocked the bootloader this way). When I open the app, load in the flash file and click Scan&Download, the phone isn't being detected. I tried huawei, mediatek and qualcomm edl drivers, but I still can't get the phone to show up.
The only way for the phone to actually show up is to boot into fastboot, but you can't flash every partition with that. It just says fastboot download fail.
So is there a way to get this program to work with the phone?
UPDATE
I used IDT and it worked.
If someone wants the firmware file, it's here.
WARNING! That is some kind of testing firmware. Look up how to update a huaewi phone manually to get regular firmware.
Sucharek 233 said:
That is some kind of testing firmware
Click to expand...
Click to collapse
that is the official Huawei board software.