Related
Hello, (complete n00b here)
Several days ago I've tried to flash a 6.0 MM (from 5.1) to my LG G4 H815 phone. There was no option to do it automatically so I proceded to do it manually via flashboot.
I hard-bricked it to oblivion as in black screen, no response whatsoever.
While investigating @ the internet I've managed to understand I could get it fixed via quadcomm drivers (mode 9008).
Tried various "fixes" for H815 but was getting safari download errors. For some reason I tried a LS991 fix and it worked. When I started the phone it showed no logo but just a secure booting error 1006.
Still, could enter firmware download so I began to flash a lot of KDZ firmwares with no success.
LGUP shows my model : H81510H.
While in fastboot mode there is a note below (wasn't there the first time) with codes : 633 B46 or something like that.
While flashing anything it ALWAYS STOPS at 9% with a tot anti-rollback error. While flashing the code changes briefly where one can read smth like : LGLS991ZVA ver. 6.0
Managed to download some KDZ for that exact model, SAME ERROR. Tried to find / flash LS991ZVA with no success in finding a TOT file.
Also, managed to get ADB drivers up and it shows unauthorized in listing (LS991). Fastboot does not detect my device even in fastboot mode @ phone.
Please HELP!
Longbranch said:
Hello, (complete n00b here)
Several days ago I've tried to flash a 6.0 MM (from 5.1) to my LG G4 H815 phone. There was no option to do it automatically so I proceded to do it manually via flashboot.
I hard-bricked it to oblivion as in black screen, no response whatsoever.
While investigating @ the internet I've managed to understand I could get it fixed via quadcomm drivers (mode 9008).
Tried various "fixes" for H815 but was getting safari download errors. For some reason I tried a LS991 fix and it worked. When I started the phone it showed no logo but just a secure booting error 1006.
Still, could enter firmware download so I began to flash a lot of KDZ firmwares with no success.
LGUP shows my model : H81510H.
While in fastboot mode there is a note below (wasn't there the first time) with codes : 633 B46 or something like that.
While flashing anything it ALWAYS STOPS at 9% with a tot anti-rollback error. While flashing the code changes briefly where one can read smth like : LGLS991ZVA ver. 6.0
Managed to download some KDZ for that exact model, SAME ERROR. Tried to find / flash LS991ZVA with no success in finding a TOT file.
Also, managed to get ADB drivers up and it shows unauthorized in listing (LS991). Fastboot does not detect my device even in fastboot mode @ phone.
Please HELP!
Click to expand...
Click to collapse
H81510h is os version it is still at 5.1 I think....what may help is plug your phone in with lgup and drop the battery out of it then closes of LG up put battery back in and start LG up and find kdz that matchs your phone and make sure that it doesn't have anti rollback.....
stinka318 said:
H81510h is os version it is still at 5.1 I think....what may help is plug your phone in with lgup and drop the battery out of it then closes of LG up put battery back in and start LG up and find kdz that matchs your phone and make sure that it doesn't have anti rollback.....
Click to expand...
Click to collapse
Hello and thx for reply. I tried to do what u've said. It did something (I was looking for a while back). When I plug the cable back in, my windows 7 immediately installs quadcomm hs-usb driver (9008) and my phone acts as if it was dead. LGUP cannot find it in that state. I've been trying to QFIL the "proper" soft but it continues to pop different errors (using different QFIL versions). Either saharafail or some sort of download fail.
LGUP still presents an error (if I decide to "fastboot" it) @ 9% 0x2000, TOT antirollback version is smaller than device version.
How can I make sure I've got the proper KDZ without ANTI-ROLLBACK?
Longbranch said:
Hello and thx for reply. I tried to do what u've said. It did something (I was looking for a while back). When I plug the cable back in, my windows 7 immediately installs quadcomm hs-usb driver (9008) and my phone acts as if it was dead. LGUP cannot find it in that state. I've been trying to QFIL the "proper" soft but it continues to pop different errors (using different QFIL versions). Either saharafail or some sort of download fail.
LGUP still presents an error (if I decide to "fastboot" it) @ 9% 0x2000, TOT antirollback version is smaller than device version.
How can I make sure I've got the proper KDZ without ANTI-ROLLBACK?
Click to expand...
Click to collapse
This may help........
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
stinka318 said:
This may help........
https://forum.xda-developers.com/lg-g5/development/uppercut-lgup-loader-g5-variants-t3511295
Click to expand...
Click to collapse
Thx again. Uppercut shows H81510H as LGUP did. Is it possible that it's somehow write-protected?
It confuses me, since during the firmware update on my phone, I get this small box below the picture showing wierd codes : 633A Bxx and when I'm trying to flash my phone, the code gets longer with LS991ZVA v6.0 and more other. It then stops.
Funny thing is, when I got the phone I couldn't even connect to the LG bridge to update it at all. I've managed to do it bugging the MTP protocol but THAT on the other hand prevented me from copying stuff / FLASH my phone to MM 6.0. Had to factory reset it back then and all went back to "normal" = LG couldnt detect my device but I could copy photos or stuff from it.
NOW, when my phone is bricked, LGbridge DETECTS my phone (in fastboot), downloads the newest KDZ update BUT cannot install it (same thing as in LGUP). Hence my question : is it somehow write-protected?
Longbranch said:
Thx again. Uppercut shows H81510H as LGUP did. Is it possible that it's somehow write-protected?
It confuses me, since during the firmware update on my phone, I get this small box below the picture showing wierd codes : 633A Bxx and when I'm trying to flash my phone, the code gets longer with LS991ZVA v6.0 and more other. It then stops.
Funny thing is, when I got the phone I couldn't even connect to the LG bridge to update it at all. I've managed to do it bugging the MTP protocol but THAT on the other hand prevented me from copying stuff / FLASH my phone to MM 6.0. Had to factory reset it back then and all went back to "normal" = LG couldnt detect my device but I could copy photos or stuff from it.
NOW, when my phone is bricked, LGbridge DETECTS my phone (in fastboot), downloads the newest KDZ update BUT cannot install it (same thing as in LGUP). Hence my question : is it somehow write-protected?
Click to expand...
Click to collapse
Have you tried to eset it by pushing power and volume own then when you see bootsplash then release power button and hen quickly push the power button again....
But in your case push power and volume down within the count or 20 then release power then push power button again and see what happens and then try the same thing on volume up......
Thanks for the reply.
I did what u've said. Despite no logo I tried to release power button for a second just after the screen's brightness goes up (I also get a small vibration @ start). Everytime I get secure booting error 1006 after a few seconds.
On the other hand when I did that with volume UP button there was no error but there was nothing aswell until I release power button in which case I got the secure booting error. All of the above tries were done with no USB connection with anything.
Longbranch said:
Thanks for the reply.
I did what u've said. Despite no logo I tried to release power button for a second just after the screen's brightness goes up (I also get a small vibration @ start). Everytime I get secure booting error 1006 after a few seconds.
On the other hand when I did that with volume UP button there was no error but there was nothing aswell until I release power button in which case I got the secure booting error. All of the above tries were done with no USB connection with anything.
Click to expand...
Click to collapse
Do try with usb s well it may do something r do nothing......
Can't tell atm since I gave it to professionals. I'll wait and see how it'll turn up. Thx for all the effort tho, was nice to tinker with a lil help
@Longbranch did you solve this problem ? I'm in the same state but my phone model is H810, everything else is the same as yours.
Nope, not really. I gave it back to the reseller and my money got returned luckily.
The professionals I refer to above did install a specific firmware for the ls991 type. Firmware ZVB I think. The only one appliable apparently. Anyways, as I suspected the ls991 type is for the US and therefore it didn't work in my country in EU. My sim card wouldnt work with it. Besides, without the sim card, the phone decided to freeze and die after several minutes every time I turn it on. Swapped for LG G5 and it's working flawlessly up until this day.
good for you, what i don't understand is that it's a h810 model but now identify as ls991 does that mean you can convert it just by a Qfil flash? I may try another model flash if can't find a suitable Rom for it
Longbranch said:
Nope, not really. I gave it back to the reseller and my money got returned luckily.
The professionals I refer to above did install a specific firmware for the ls991 type. Firmware ZVB I think. The only one appliable apparently. Anyways, as I suspected the ls991 type is for the US and therefore it didn't work in my country in EU. My sim card wouldnt work with it. Besides, without the sim card, the phone decided to freeze and die after several minutes every time I turn it on. Swapped for LG G5 and it's working flawlessly up until this day.
Click to expand...
Click to collapse
Chebhou said:
good for you, what i don't understand is that it's a h810 model but now identify as ls991 does that mean you can convert it just by a Qfil flash? I may try another model flash if can't find a suitable Rom for it
Click to expand...
Click to collapse
Yes! That's what I and neutrondev telling everyone :
do not use qfil without the knowledge about the result!
The only working firehose file available out there is for the ls991 and that means if you use it it will turn your device into a ls991 without any way to get back to your previous device model!!
.
Sent from my LG-H815 using XDA Labs
@steadfasterX since I have done it already is there any way to get it working even as an LS991 ?
here is what i did till now
the reason for using Qfill is that it went dead after flashing an H810 rom .
after that when it's in download mode it doesn't allow me to flash the ls911ZV5 ls911ZV6 ls911ZV6_12 roms that i found ( it says LS991ZVA )
so i went in fastboot and flashed boot/aboot/recovery....img extracted from the ls911ZV6 rom then it accepted the rom in download mode
but it is stuck in a hard bootloop ( reboots when it is getting in recovery but still has download mode yet no fastboot as before)
any thoughts ?
Chebhou said:
@steadfasterX since I have done it already is there any way to get it working even as an LS991 ?
here is what i did till now
the reason for using Qfill is that it went dead after flashing an H810 rom .
after that when it's in download mode it doesn't allow me to flash the ls911ZV5 ls911ZV6 ls911ZV6_12 roms that i found ( it says LS991ZVA )
so i went in fastboot and flashed boot/aboot/recovery....img extracted from the ls911ZV6 rom then it accepted the rom in download mode
but it is stuck in a hard bootloop ( reboots when it is getting in recovery but still has download mode yet no fastboot as before)
any thoughts ?
Click to expand...
Click to collapse
Yes it's possible. You can boot a h811 H815 or any other rom you like. Even LOS!!
Great right? BUT you are bounded to the ls991 modem and so you need to be in a sprint network to use telephony. That means the phone is now useless outside the US .
And you wrote you tried ls911 ROMs? I hope you meant ls991
I work on a fully working experience on every network though. Checkout my proof of concept for unlocking the bootloader thread
I can go into details on IRC if you like.
..
Sent from my LG-H815 using XDA Labs
@steadfasterX thank you for keeping up with me ! ( btw what room on IRC ?)
for now I have used Qfill again and got fastboot working again and flashed TWRP ( not sure where ! ) so when the phone is off and i plug the usb it boots to twrp ( but it doesn't in recovery )
normal boot will show "secure boot error 1002"
then i flashed twrp img to recovery partition using twrp but it didn't work in recovery ( still reboots after showing Recovery Mode loading screen )
also tried to load some roms on the device to try them but I got error "file too large for filesystem " when copying them .
atm I don't know the state I'm in and what should be next ?
btw here are the recovery log and dmesg
Chebhou said:
@steadfasterX thank you for keeping up with me ! ( btw what room on IRC ?)
for now I have used Qfill again and got fastboot working again and flashed TWRP ( not sure where ! ) so when the phone is off and i plug the usb it boots to twrp ( but it doesn't in recovery )
normal boot will show "secure boot error 1002"
then i flashed twrp img to recovery partition using twrp but it didn't work in recovery ( still reboots after showing Recovery Mode loading screen )
also tried to load some roms on the device to try them but I got error "file too large for filesystem " when copying them .
atm I don't know the state I'm in and what should be next ?
btw here are the recovery log and dmesg
Click to expand...
Click to collapse
Np we can bring you back to life but as already said without cell service. That's the price for the firehose and unlocked feeling you have now.
Did you found and read my thread here?
https://forum.xda-developers.com/g4/general/bl-unlock-unlock-bootloader-proof-t3648288
There you will find some more info and also the IRC details how you can find me. I'm online from Monday to Friday mainly.
It's much easier to talk in chat then here. once all the details are known I will provide a full guide.
.
Sent from my LG-H815 using XDA Labs
Hello there I had just unlocked the bootloader yesterday and flashed an Oreo ROM without updating base bands and now my device doesn't boot up it just shows the bootlogo and turns off again in less than a second it doesn't even charge, good thing is I am able to go to edl mode I guess but then when I tried qfil and mi flash to flash stock rom i m getting the sahara cannot detect com port handle error and the system cannot find the file specified error in mi flash please help its just been a week since I got this phone
Solution
Chin_hebbar said:
Hello there I had just unlocked the bootloader yesterday and flashed an Oreo ROM without updating base bands and now my device doesn't boot up it just shows the bootlogo and turns off again in less than a second it doesn't even charge, good thing is I am able to go to edl mode I guess but then when I tried qfil and mi flash to flash stock rom i m getting the sahara cannot detect com port handle error and the system cannot find the file specified error in mi flash please help its just been a week since I got this phone
Click to expand...
Click to collapse
I've used MiFlash Tool, and the problem was fixed. Sahara Error occurs when you take to much time to flash after booting to EDL, you only have few seconds to flash util the port is closed for writing. QFIL takes around 20 to 25 seconds in caching the files so use MiFlash and It'll flash. Best way to do it is:
1. Install and setup MiFlash for flashing.
2. Open MiFlash and select your Firmware's folder.
3. As soon as you connect the phone refresh miflash and hit flash.
If everything goes well you'll flash will be successful else try again.
I tried doing as fast as a could too on mi flash and it would come up as trying to connect to com4 port something in the status and would eventually come back to same error in the picture.
Chin_hebbar said:
I tried doing as fast as a could too on mi flash and it would come up as trying to connect to com4 port something in the status and would eventually come back to same error in the picture.
Click to expand...
Click to collapse
I need to flash Baseband for Oreo. Please guide me
windows 10 problem
Chin_hebbar said:
Hello there I had just unlocked the bootloader yesterday and flashed an Oreo ROM without updating base bands and now my device doesn't boot up it just shows the bootlogo and turns off again in less than a second it doesn't even charge, good thing is I am able to go to edl mode I guess but then when I tried qfil and mi flash to flash stock rom i m getting the sahara cannot detect com port handle error and the system cannot find the file specified error in mi flash please help its just been a week since I got this phone
Click to expand...
Click to collapse
I face this problem in windows 10.
first uninstall zuk drivers and qfill and disable driver signature enforcement (Google it how to do it) then install zuk drivers and qfill use original cable and your phone will get flashed
Balaji Sriram said:
I need to flash Baseband for Oreo. Please guide me
Click to expand...
Click to collapse
Follow the instruction from this post
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/zuk-z2-baseband-flashing-guide-t3715121
Do not listen to anyone telling you to use miflash, only use qfil otherwise you WILL encounter other issues because qfil is the only way to reach the deeper partitions that mi is unable to... Other issues may range from no volte, calling or signal problems etc its just easier to do it right the first time.
Hello!
I'm at a complete loss right now.
I keep getting issue after issue, after I solve one, another one seem to appear.
I'm trying to flash my Z2 plus via QFIL using the firmware provided in this link. I've tried the first link, 2.0.093 and the last link, 2.5.104.
I have an unlocked bootloader, and rooted phone. I use the ALL IN ONE tool to boot into edl mode, and immediately start attempting to download through QFIL (Through Port: Qualcomm HS-USB QDLoader 9008 (COM###).
I've tried using the latest QFIL and the 1.0.0.2 version as well but they give me different errors. The latest version gives me:
"Download Fail:FireHose Fail:FHLoader Fail. The system cannot find the file specified."
No amount of googling has come up with a suitable answer to what the heck this actually means.
Trying the 1.0.0.2 version I get a Sahara protocol error:
"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
a QC.SwDownloadDLL.SwDownload.QphoneMSSaharaDownloadArmPrg(Ulnt64&version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download"
(if it looks wonky I had to type it up)
I'm at a complete loss at this point. Took me two night to get to this point, I'm amazed I haven't bricked my phone yet. But my goodness I just want SOMETHING to work...
If anyone needs more info I can probably provide it.
Thanks everyone!
enasong said:
Hello!
I'm at a complete loss right now.
I keep getting issue after issue, after I solve one, another one seem to appear.
I'm trying to flash my Z2 plus via QFIL using the firmware provided in this link. I've tried the first link, 2.0.093 and the last link, 2.5.104.
I have an unlocked bootloader, and rooted phone. I use the ALL IN ONE tool to boot into edl mode, and immediately start attempting to download through QFIL (Through Port: Qualcomm HS-USB QDLoader 9008 (COM###).
I've tried using the latest QFIL and the 1.0.0.2 version as well but they give me different errors. The latest version gives me:
"Download Fail:FireHose Fail:FHLoader Fail. The system cannot find the file specified."
No amount of googling has come up with a suitable answer to what the heck this actually means.
Trying the 1.0.0.2 version I get a Sahara protocol error:
"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
a QC.SwDownloadDLL.SwDownload.QphoneMSSaharaDownloadArmPrg(Ulnt64&version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download"
(if it looks wonky I had to type it up)
I'm at a complete loss at this point. Took me two night to get to this point, I'm amazed I haven't bricked my phone yet. But my goodness I just want SOMETHING to work...
If anyone needs more info I can probably provide it.
Thanks everyone!
Click to expand...
Click to collapse
You want to specifically flash indian zui ?
venom0207 said:
You want to specifically flash indian zui ?
Click to expand...
Click to collapse
Well, I suppose anything that would work. Do I have to come from a specific build or can I just simply flash to something new entirely? My previous rom was a AOSP AEX Build for 8.0 (or 8.1, not sure) and that was fine.
I ask because I tried to TWRP flash a couple of roms (separately) to try, but I get the bluescreen error (which I gathered had to do with an outdated kernel?) and bootloops.
The solution seemed to be to flash the ZUI2.5 (Indian stock rom), but as I've struggled for the past few days, I just can't seem to get it working.
Did I miss something?
Thanks.
Do this ..
Flash 1.9 zui (that will lock bootloader )
Boot it and than again flash zui 3.5.3** something that will upgrade the zui version and finally boot into that zui and go to update app ...
There you will see zui 4.0.199 update download and install that update ...
After doing all this ... Unlock boot loader and flash twrp then flash custom rom .. This is what i do every time ..if i stuck inbetween
venom0207 said:
Do this ..
Flash 1.9 zui (that will lock bootloader )
Boot it and than again flash zui 3.5.3** something that will upgrade the zui version and finally boot into that zui and go to update app ...
There you will see zui 4.0.199 update download and install that update ...
After doing all this ... Unlock boot loader and flash twrp then flash custom rom .. This is what i do every time ..if i stuck inbetween
Click to expand...
Click to collapse
I tried 1.9, but I still get the FH Loader error.
"Download Fail:FireHose Fail:FHLoader Fail. The system cannot find the file specified."
This has been the error that stopped me in my tracks. I just can't seem to get past this error.
Immensely frustrating...
enasong said:
I tried 1.9, but I still get the FH Loader error.
"Download Fail:FireHose Fail:FHLoader Fail. The system cannot find the file specified."
This has been the error that stopped me in my tracks. I just can't seem to get past this error.
Immensely frustrating...
Click to expand...
Click to collapse
Wait do this then
Install again the usb drivers of Qualcomm and zuk .. try this ... May be drivers are not fully installed on system
After all this faffing around, I finally got it to work....
Using miflash tool...
Sigh. Thanks folks for the help.
Hi everyone. My Redmi note 5 pro is not turning on, it just gets stucked at the "redmi" logo. I tried disconnecting the battery but that didn't work. Since I can enter fastboot mode I also tried to flash the fastboot miui 12 rom with Miflash but an error appears saying "error flashing partition - write protected" (my phone has bootloader already unlocked). Even in EDL mode I couldn't flash the rom since it doesn't let me authenticate in my xiaomi account and miflash gets stucked at "edl authentication". Can you help me to unbrick my phone? Thank you.
nico.fiaba1 said:
Hi everyone. My Redmi note 5 pro is not turning on, it just gets stucked at the "redmi" logo. I tried disconnecting the battery but that didn't work. Since I can enter fastboot mode I also tried to flash the fastboot miui 12 rom with Miflash but an error appears saying "error flashing partition - write protected" (my phone has bootloader already unlocked). Even in EDL mode I couldn't flash the rom since it doesn't let me authenticate in my xiaomi account and miflash gets stucked at "edl authentication". Can you help me to unbrick my phone? Thank you.
Click to expand...
Click to collapse
Same thing happened to me and another one of my friends who owned redmi note 5 pro last week. Trust me I literally tried everything, but sadly I had to go for a new phone. The xiaomi service center told me the motherboard needed to be replaced which would cost 4-5k plus the screen would need to be replaced ( if you have even a couple screen cracks ) which would cost another 2-3k. Even then I would advise to go for a new phone.
Still sus how so many RN5 pro are getting the write protected error out of nowhere in the past 15 days. I did see a couple more posts about the same here.
Hi, I have the same problem. So I did enter EDL with the two pins on the mainboard, but when I try to flash miui 12 with QFIL (Qualcomm Flash Image Loader) I get authentication error. Even if I used a patched firehose programmer file. I tried 3 different patched firehose programmer files.
Does someone have a working patched firehose programmer file for Xiaomi Redmi Note 5 Pro?
So If we do not find a working patched firehose programmer file or a xiaomi developer who share his account for 5 min then I think we are not able to solve this problem..
ralaud said:
Hi, I have the same problem. So I did enter EDL with the two pins on the mainboard, but when I try to flash miui 12 with QFIL (Qualcomm Flash Image Loader) I get authentication error. Even if I used a patched firehose programmer file. I tried 3 different patched firehose programmer files.
Does someone have a working patched firehose programmer file for Xiaomi Redmi Note 5 Pro?
So If we do not find a working patched firehose programmer file or a xiaomi developer who share his account for 5 min then I think we are not able to solve this problem..
Click to expand...
Click to collapse
Search it on XDA forum there are links and explanation how to use it.
Tip: use MI flash tool (start with version from 2018 and than newer....)
Same thing happened to me in the last week of may, I even posted a thread here for help and my phone is even stuck on fastboot logo, sadly i couldn't find any solutions. If you find any solutions please reply to this post and help a brother.
Warvid said:
Same thing happened to me in the last week of may, I even posted a thread here for help and my phone is even stuck on fastboot logo, sadly i couldn't find any solutions. If you find any solutions please reply to this post and help a brother.
Click to expand...
Click to collapse
Did you end up solving the issue? I am also facing the exact same issue.
Hi there,
I recently bricked my Redmi Note 9 Pro trying to reflash the original rom under TWRP. It was a Global version (joyeuse) originally.
It simply is stuck on a bootloop (Redmi logo showing up for 1sec then rebooting) so can't access fastboot or recovery mode.
After many hours of research, I kinda came to the conclusion that there is no way of flashing the rom in EDL mode without an authorized MI account for MI Flash Tool.
I'm still asking though : is there any trick to bypass it or flash the original rom without using an authorized account on a Qualcomm-based device ?
Cheers !
AkilisUi said:
Hi there,
I recently bricked my Redmi Note 9 Pro trying to reflash the original rom under TWRP. It was a Global version (joyeuse) originally.
It simply is stuck on a bootloop (Redmi logo showing up for 1sec then rebooting) so can't access fastboot or recovery mode.
After many hours of research, I kinda came to the conclusion that there is no way of flashing the rom in EDL mode without an authorized MI account for MI Flash Tool.
I'm still asking though : is there any trick to bypass it or flash the original rom without using an authorized account on a Qualcomm-based device ?
Cheers !
Click to expand...
Click to collapse
There's no trick and it cannot be unbrick as of now even mi service center can't flash fw through edl. Your only option are: 1.)Mi Service Center (they'll replace the board it'll cost you $120 USD like you bought a second hand of the same unit). 2.) Sell the parts to make profit and buy a new phone. 3.) Set aside and wait for available unbrick solution. You cannot avail services from indian and russian guys almost all their services are scam. That's all you can do and I can share.
Facing s similar issue. Looking forward to a solution..
I'm able to access both recovery and fastboot. Only issue is that i accidentally locked the bootloader while tinkering with it on mi flash unlock.
Apparently accessing EDL mode is the only way to get past this (based on hours of extensive google research, lol).
As of now I couldn't find any solution.
In my theory it can be unbrick in two methods:
1st method is bypassing authentication (server hack or modified mi flashtool).
2nd method is modified firehose programmer file.
We can use other flashtool programs like (Xiaomi Fire Tool, Chimera, and other paid apps to flash) but we need a modified firehose for that.
If someone else has the solution please help us unbrick our phones. May be we can donate instead of buying from someone else we don't even trust and letting them access our computer that's too risky.
Moreover, I asked xiaomi support, In our case they won't help us for them our bricked phones are trash. We are helpless.
In case someone has time to help patch these files for us. I got these files from latest firmware: (Joyeuse Global). I will donate my money instead of availing service.
Firmware:
joyeuse_global_images_V13.0.1.0.SJZMIXM_20220804.0000.00_12.0_global
Source:
https://c.mi.com/global/miuidownload/detail/guide/global/miuidownload/index
Hello, I have my redmi note 9 pro (joyeuse) working again. After days of deep searching in the web for fix I almost got out of my mind.
If you have no other choice you can pay someone for authorized flash just make sure your phone can enter into edl mode stably. I was very skeptical and have trust issues but my only choice is: give it a try.
AkilisUi said:
Hi there,
I recently bricked my Redmi Note 9 Pro trying to reflash the original rom under TWRP. It was a Global version (joyeuse) originally.
It simply is stuck on a bootloop (Redmi logo showing up for 1sec then rebooting) so can't access fastboot or recovery mode.
After many hours of research, I kinda came to the conclusion that there is no way of flashing the rom in EDL mode without an authorized MI account for MI Flash Tool.
I'm still asking though : is there any trick to bypass it or flash the original rom without using an authorized account on a Qualcomm-based device ?
Cheers !
Click to expand...
Click to collapse
Hi, have you tried holding lower volume button and power button at the same time, that will make the phone go to fastboot mode. After that download XiaomiAdbFastbootTools and open it. It should automatically point you to Fastboot tab. In Fastboot tab under Image: 1. select ROM folder( oh forgot to mention to download FASTBOOT image for your phone's model before this) and for method put clean install and then just click on flash ROM and done.
Good luck from someone who has bricked a phone like you for at least 20 times lmao
Mumi32 said:
Hi, have you tried holding lower volume button and power button at the same time, that will make the phone go to fastboot mode. After that download XiaomiAdbFastbootTools and open it. It should automatically point you to Fastboot tab. In Fastboot tab under Image: 1. select ROM folder( oh forgot to mention to download FASTBOOT image for your phone's model before this) and for method put clean install and then just click on flash ROM and done.
Good luck from someone who has bricked a phone like you for at least 20 times lmao
Click to expand...
Click to collapse
Hey,
My phone is hard bricked, meaning that I don't have access to fastboot or recovery anymore. My only option was getting rid of the back cover, unplug the battery and short-circuit the pins with a pair of tweezers to access edl mode (which I did), then install the original rom with an authorized account (don't have + cannot find) or bypass the authorization or mayber with a modified firehose (I tried to find one, but didn't succeed as mentionned by gfchhhh earlier).
So I my brother gave me a spare phone that will clompetely do (redmi note 10 pro actually) !
Thanks for your time tho !
This happened to me in 2020 when I bought the phone after the release and I tried to install the Curtana ROM on a Joyeuse device, so I bricked the phone by mistake!
Thankfully, I found some shady Telegram group with people that offered EDL service from India (I think...) with official MI Flash tool from authorized service provider (supposedly they were the owners of the account). At first, I was skeptical and I tried different ways to service the phone, but couldn't find any so I delved into the shady realm of a remote service provider.
From my experience, the dude in question that offered the service seemed very rude because he probably didn't speak English very well. I paid him 30€ through PayPal beforehand, which I know it was a risky move. We agreed on a date to fix the phone remotely, but he wasn't punctual and I had to wait a couple of days for him to respond.
He connected via TeamViewer, he asked to download the MI Flash Tool (I don't remember the name fully), and asked me to put the phone in EDL with a paperclip or tweezers. Then I remember him logging in his Mi service account, sending a repair request (i think), and after a couple of minutes, he copied and pasted what looked to be a very long 2FA single use code (two factor authentication) to begin the flashing.
The process took about 30~60 min or so, of which I didn't remove my eyes from the computer at any moment to check if he was going to do pesky things through the remote access. After the long wait, the phone booted and I got my phone working.
I have never again tried to root the phone until today, because I have a severe problem with the audio interface and I need to modify some system files.
Wish me luck!