I was using my Moto Z XT1650-03 for about three months. In that time I was using LineageOS 14.1 on it.
Today, I logged off of my computer and took my phone out where it out of nowhere suddenly started rebooting before powering off never to come on again. I have connected it to the charger, where it has not had any indicator light come on.
I am at a loss, and do not have any money to replace this phone should it have to come to that.
stef_nix said:
I was using my Moto Z XT1650-03 for about three months. In that time I was using LineageOS 14.1 on it.
Today, I logged off of my computer and took my phone out where it out of nowhere suddenly started rebooting before powering off never to come on again. I have connected it to the charger, where it has not had any indicator light come on.
I am at a loss, and do not have any money to replace this phone should it have to come to that.
Click to expand...
Click to collapse
Connect the phone to the pc, wait a bit if you're on Windows 10 and it should recognize it as something like qcom 8009 loader".
Ok
Windows did see it as a Qualcoom 8009
stef-nix said:
Ok
Windows did see it as a Qualcoom 8009
Click to expand...
Click to collapse
Great, you can try blankflash.
I revived my Z last month with it (it was also dead but got recognized by the PC).
I'll try to dig up the proper version when I get home and I'll put it here.
The Marionette said:
Great, you can try blankflash.
I revived my Z last month with it (it was also dead but got recognized by the PC).
I'll try to dig up the proper version when I get home and I'll put it here.
Click to expand...
Click to collapse
Here, try this one:
https://mirrors.lolinet.com/firmwar...118-23-13-6-5_15_release-keys-cid2_vzw.tar.gz
You mighz need to try sith several cables, though.
In my case, it failed with 3 third-party cables and then I tried the cable from the Xiaomi Mi 5 and it worked.
My guess is that you need a usb c cable from any smartphone ( Samsung, LG, Xiaomi, etc. ) as long as it's the one that came with the phone and not a third-party one.
After the program is done, you should be able to enter fastboot only by connecting the phone to the pc ( it won't start like regular fastboot because this will be an "emergency" variant of a fastboot/bootloader menu ) and flash a stock firmware ( flash a 7.1.1 firmware first since the blankflash I put here will place an older bootloader for Nougat ) .
If you use a blankflash which has an Oreo bootloader and it messes up, you won't be able to use an older version to undo it, so use the one I put before anything else.
The Marionette said:
Here, try this one:
https://mirrors.lolinet.com/firmwar...118-23-13-6-5_15_release-keys-cid2_vzw.tar.gz
You mighz need to try sith several cables, though.
In my case, it failed with 3 third-party cables and then I tried the cable from the Xiaomi Mi 5 and it worked.
My guess is that you need a usb c cable from any smartphone ( Samsung, LG, Xiaomi, etc. ) as long as it's the one that came with the phone and not a third-party one.
After the program is done, you should be able to enter fastboot only by connecting the phone to the pc ( it won't start like regular fastboot because this will be an "emergency" variant of a fastboot/bootloader menu ) and flash a stock firmware ( flash a 7.1.1 firmware first since the blankflash I put here will place an older bootloader for Nougat ) .
If you use a blankflash which has an Oreo bootloader and it messes up, you won't be able to use an older version to undo it, so use the one I put before anything else.
Click to expand...
Click to collapse
I think it's too late for that (flashing with this first), but I'll try anyways. Your link is 404ing btw and are you sure I should be flashing VZW firmware on to this thing? This phone was bought carrier unlocked.
stef_nix said:
I think it's too late for that (flashing with this first), but I'll try anyways. Your link is 404ing btw and are you sure I should be flashing VZW firmware on to this thing? This phone was bought carrier unlocked.
Click to expand...
Click to collapse
Well, crap.
I wanted to use this as a last resort but...
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
There's everything I went through to fix mine.
I'll try after work (We might have opposite time zone schedules). Chances are nothing happened in previous attempts using blankflash.
Please do hang tight
stef_nix said:
I'll try after work (We might have opposite time zone schedules). Chances are nothing happened in previous attempts using blankflash.
Please do hang tight
Click to expand...
Click to collapse
Again, if it's recognized as the qcom 8009 device, blankflash should work.
I had to use an actual OEM cable for the Xiaomi Mi 5 and a PC in my university library for it to suddenly work. Neither my laptop nor PC worked but the university PC miraculously did. Just keep trying with different cables and PCs/laptops.
Related
I followed the instructions provided at the MEGA UNBRICK something thread situated here http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108/
Anyway, when I hold the volume-up button for 10 seconds, followed by plugging the Onyx with the PC, the system does't detect the device. What can I do now? And is there any alternative method to unbrick a hardbricked phone? I urgently need help
If you installed the drivers and the computer is not reckognizing the device, that's bad news. How did you manage to accomplish that?
aredpanda said:
If you installed the drivers and the computer is nota reckognizing the device, that's bad news. How did you manage to accomplish that?
Click to expand...
Click to collapse
I don't know. And ijust in case if you were being sarcastic, I used the same computer to replace the recovery of this phone.
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
aredpanda said:
Im not being sarcastic. The problem with the Android modding scene is that people got too used to blindly following steps without really knowing how they are affecting their devices. In order to get better chances at getting help, you'll need to describe what and exactly how you were altering your phone.
Click to expand...
Click to collapse
I was using Bliss ROM with BluSpark kernel. Anyway, I downloaded 2 ROMS today, Sailfish OS and the stock H2OS for OPX. I wiped the phone and first flashed the Sailfish OS, but the phone was stuck in a bootloop which only was showing the oneplus logo and the text "Powered by Anrdoid". After that, I entered recovery, and did the normal pre-flash wipe again. This time I flashed the H2OS, but after I gave "Reboot to System", my phone just wont do nor display anything. Hardbricked, dead
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
aredpanda said:
Can you boot it into recovery? Your bat may be dead from extensively flashing stuff, so plug the phone to the power cable and press and hold VolDown+Power for some good 30s, then you can conclude your phone wont boot into recovery and maybe need an unbrick.
Click to expand...
Click to collapse
Yeah, it didn't boot into recovery
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
No, it doesn't
aredpanda said:
Does the led light up when you plug the phone to the wall? If it does let it charge for an hour before attempting anything else.
After that and before trying anything else, make sure driver signature check is off and test mode is on. This varies slightly for Windows 7/8 vs 8.1/10. Which version are you running?
Click to expand...
Click to collapse
I turned off the signature check, W8
If your led doesnt light when your phone is plugged to the wall, this is behind the hard unbricking procedure and your phone is indeed, dead.
Sent from my ONE E1003 using Tapatalk
This issue has been resolved via PM,
Can a mod please close this thread?
No idea what it could be besides corrupt firmware which I've never heard of happening before. The Qualcomm utility should work just fine. Leave it plugged in for an hour or two and see if anything happens
Did you install the qualcomm drivers? If not do it again carefully with driver enforcement off. It works like a charm. Have bricked my device twice as of now and it worked.
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
martonto said:
Hi guys!
I think I did something stupid while updating my XT1650-03 to Nougat.
What I did was manually flash stock nougat ROM (retbr) through fastboot, following the instructions within flashfile.xml, but, as I've read some bad things about the updated bootloader I stupidly decided not to flash it. The result is that it won't power up, even though I've tried: pressing power+vol. down; power; plugging the charger; fastboot commmands ( I was hoping it was just the screen that was off); to no avail.
I've noticed that when I plug the usb cable to the computer it plays that sound of connected devices.
Any suggestions? I'm probably going to have to take my device to authorised repair (off warranty, I know), but they usually take weeks to fix anything, so you guys are my best bet for now.
Thanks in advance!
Click to expand...
Click to collapse
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Manish54 said:
Don't even bother going to the service center. The same happened with my device and they refused to give me the warranty. Motorola voids it the moment you get the unlock code. So my device was dead for 3 months. And I fixed it few days back. The good news is that your PC is detecting the device.
I will post the solution with a new thread in few minutes.
Click to expand...
Click to collapse
Thank you so much for your reply, it's very much appreciated! I didn't think anyone would reply that soon
I'll wait for your thread!
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
So, I'm totally lost.
As I posted in the thread above, even though Manish54 has been very kind to help, that solution did not work for me, so I've been trying to find another way. The thing is, this issue is beyond my comprehension. I'm not new to flashing and stuff, but I am new to moto Z. I understand that I should've been more careful and also have read a bit more before starting to mess with a new device, so feel free to judge me .
For instance, I don't know what fsg.mbm, adspso.bin, BTFM.bin and oem.img are for, since my old phone didn't have those (or at least I didn't need to mess with those), and I also don't know it they're relevant to my problem. If anyone could point me to some info on that, it'd be greatly helpfull.
Besides that, I've found mentions to tools like qualcomm's BoardDiag and QPST QFIL, but I'm not really sure if they apply for my situation, or even if I can manage to adapt the guides I've found to work on the Moto Z.
Any help is very much appreciated!
Thank you!
Solved!
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Is there any way to solve it ?
Hillterpty said:
Is there any way to solve it ?
Click to expand...
Click to collapse
Did you even read the posts?
Ajuda
martonto said:
I managed to unbrick my phone.
If anyone needs it, the details are in the thread made by Manish54.
https://forum.xda-developers.com/mo...rick-moto-z-hardbricked-t3590133#post71876064
Click to expand...
Click to collapse
Amigo tb estou com o meu morto, me ajuda, qual o modelo do seu.
https://uploaddeimagens.com.br/imagens/sem_titulo-jpg--9130
hard brick moto z
Manish54 said:
There ya go
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-unbrick-moto-z-hardbricked-t3590133
Click to expand...
Click to collapse
hello friends, I'm with hard brick on the moto z xt1650-3
due to an update via ota, when my bootloader was unlocked I was in the android oreo (8.0), however I went back to 7.0, due to an update via ota, the device did not call anymore, I tried several blankflash and nothing, I am very annoyed at this, thinking of dropping my hand, I took some assists nobody can solve, I hope someone here can help me, at least inform me something that is useful to recover my cell phone.
my cell phone is still recognized as "qualcomm hs-usb qdloader 9008 (com3)
please join the telegram group:
https://t.me/motozz
Hey, my phone was dead two (brazilian xt1650-03), i spent three days struggling until i could bring him back. Thanks to the help in this forum. Your phone probably has the latest update opls27-76-51-7-july, so it must work:
first, you have to bankflash it with blankflash_OPL_27.76-51, its in the 30+ page topic tutorial here in this forum. Very important, must be in windows 7 or 8, with usb2.0
second, use this rom opls27-76-51-7-july-moto-z. it must work because its the last one. Its not brazilian, evething works fine but the netflix app didnt , but hey, at least our phone is alive again.
The secret is in the version of the firmware instaled before the brick, it must be the rom installed or latest to work
Steps:
1. Turn Off Any Virus Protection Software
2. Download MP26010j_00_0316.kdz To Flash Your Phone Back To Stock
3. Install LGMobileDriver_WHQL_Ver_4.2.0.exe
4. Next Install LGUP_Store_Frame_Ver_1_14_3.msi
5. Make Sure That You Have Your Phone Connected (Take Battery Out Then Put It Back In Hold Volume Up And Connect With Micro USB) So LGUP Can Be Able To Recognize It
6. Then Double Click UPPERCUT.exe to open up LGUP Now But Only Thing Is That Uppercut will try to verify just ignore and if it doesn't open up just open lgup from desktop and its going to view phone as unknown
7. Unplug Phone But Keep LG Download Mode On And Exit LGUP
8. Open LGUP First And Then Connect Phone Which Should Recognize Phone As MP260
9. Click Upgrade, Make Sure That Bin Is Checked And Select File MP26010j_00_0316.kdz To Flash And Click Start
10. Your Done! Video Coming Soon
Links: https://mega.nz/#!EZcURRSD!NF_5MU4dJUpTknRcPMQWFVoYo4ePsGkoA0ndkkzVsmI https://mega.nz/#!dFNWFZZa!Rl3P7tJs7J51TtjcnaLwR3RHgGdRSco8NcJ9yog86J0 https://mega.nz/#!oVNSnYTB!3y9-P4t_8P-lj5sCXhFjO0R8J3j4Z_US-XCjVGysgEI https://mega.nz/#!pAUgGAwC!j5d3C8pUdQR5XMpqWBgLDu2O3tE99yWNa2nwXud3OSo
The Only Thing Im Disappointed Is That Every Time You Reboot Phone or Turn It On It Keeps Saying Lock Bootloader But Just Press The Power Button To Continue Repeating The Process Does Not Remove That Message
I Made This Tutorial For Some People That Have Trouble With Apps That Detect Root
Phone dont turn on at all
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
shaneg79 said:
fyi u can get rid of the bootloader bootup annoyance by following the unlock bootloader instructions but instead of typing fastboot oem unlock type fastboot oem lock
Click to expand...
Click to collapse
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
New Optimus said:
If you lock the bootloader if you have custom recovery (twrp) and superuser you will not be able to boot
Click to expand...
Click to collapse
Correct but this thread was about removing root
shaneg79 said:
Correct but this thread was about removing root
Click to expand...
Click to collapse
ah, I thought that was in the original post or implied if completely unrooting.
New Optimus said:
Just a Heads up there is a new version out, as of 9/01/17
MP26010r_00_0817.kdz
download link
https://lg-firmwares.com/lg-mp260-firmwares/
Click to expand...
Click to collapse
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
meazz1 said:
Any link for the T-mobile variant?
I looked all over and reached the end of internet but couldn't find , lol!
Click to expand...
Click to collapse
Here
kc6wke said:
Here
Click to expand...
Click to collapse
Thanks
meazz1 said:
Thanks
Click to expand...
Click to collapse
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
meazz1 said:
Looked and saw two links for the newest kdz. I'm in the USA so TMO =north america.
But I 'm curios what TMI stands for, no info on that page of region listings.
Click to expand...
Click to collapse
Not sure about TMI, use TMO North America
I figured I'd post this here to, because I am thinking about getting this phone. It's $99 at metro pcs right now, that's really hard to pass up.
In a twrp+root thread there are some that cannot get root, with the last LG firmware update, so I'm guessing this is a soft brick as apposed to a hard brick.
So, had a question.
If in the case of the like 10% of the people that do this root, the phone won't root or bricks, if I get this phone and and that happens, is it possible to flash the phone via the LG program, with a KDZ file and go back to stock like in this thread? If so I will probably buy this phone tomorrow (crosses fingers the kdz trick will work)
From looking at the videos, it looks as if the LG program is similar to the Samsung Odin program as far as flashing goes, am I correct in this?
...
Sent from my [device_name] using XDA-Developers Legacy app
I know this thread has not been active for a while. However I have a Metro LG K20 Plus phone and want to change the firmware to T-Mobile. I have not been successful doing this as I always get invalid firmware, because LG UP recognizes the phone as a metro phone. Is there a way to succeed in getting the T-Mobile firmware on the phone?
thanks in advance.
Stoner101 said:
yesterday i rooted my k20 mp260 then this morning i wanted to revert back to stock and no root, i tried to unroot it but i didnt follow this cause i didnt find it til now,but i got rid of root and then i tried to update via ota and it went into twrp and then it was installing until it just went black, like it shut off now it doesnt power on. when i plug it in to pc it finds it but it cant install the driver. any help to try to Resurrect from the grave would be great
Click to expand...
Click to collapse
Did you find any answers to this? I have one that is bricked. It will not show up when connected to a computer at all
Virus warning from Avira in Uppercut
lg k20 plus soft bricked?
So I've searched high and low and have tried suggestion after suggestion with no avail. To start things off, I have a soft bricked LG k20 plus. Everything was working fine until the other day when I went to flash a kernel, and when the phone restarted, the screen was a dark grey/black color. I rooted the devices using massis method, removed SU and then rooted using Magisk. Like I said everything was working fine and for whatever reason I decided to try a different kernel. That's when it all went downhill. So now when I turn the phone on, the screen is still blank but it vibrates. When I've connected it to a computer, on my Mac it doesn't show up with ADB or FASTBOOT but in my device tree it comes up as LGE Android device. I borrowed my friends laptop since it runs windows, and my Mac is a dinosaur. ADB doesn't pick it up either, but in a USB hub it says the same thing, LGE Android device and lower down it comes up as TP-LINK. Now tryin to use LG Flash tools doesn't work, LGUP doesn't see my device, and when I tried to extract the KZD file, when I go to select it from the list there is no file to choose. Since I can't see anything on my screen, I can't tell if I'm in download mode, bootloader, etc, but in my device tree sometimes my phone will pop up an bootloader interface and I can use fastboot commands. When I was last able to see my screen, yes, USB debugging was on, I had a recovery, but since I can't see anything on my screen I can't seem to boot into recovery. If I could I would wipe cache and all. I think I may have read too many article and suggestions as to what to do because nothing seems to be working, and don't seem to find anything else related closely enough to my issue. Anyone have a clue as to where I should start? I'll have to give my friend back her laptop soon, and since my mac is so old, and the whole PC vs Mac feud, my computer won't be of much help. Any advice my hair strands would greatly appreciate before they rest are pulled out lol
hey as per my username i'm no good at this but i got this far. so I got all the files together did sd _shadow's guide unlocked bootloader etc., RSA method doesn't work for me so i am trying the regular fastboot option but my phone cant do fastbootd also my CPU is QUALCOMM
so can i run the flashfile.bat via regular fastboot or will it brick my phone.
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
purenoob said:
well forget it i hard bricked it living up to my name.hopefully ill get it fixed
Click to expand...
Click to collapse
bricked can mean several different things.
No sign of life?
Window PC?
sd_shadow said:
bricked can mean several different things.
No sign of life?
Window PC?
Click to expand...
Click to collapse
no sign of life, no power no charge, i'm on windows if plugged in its detected in the device manager.
can this be fixed by anyone i feel really bad, i know it's just a phone but ya know.
purenoob said:
if plugged in its detected in the device manager.
Click to expand...
Click to collapse
That is a sign of life
Is my device in EDL Mode?
sd_shadow said:
That is a sign of life
Is my device in EDL Mode?
Click to expand...
Click to collapse
in device manager it says quadcomm hs-usb qdloader 9008. so by the looks of this it's a candidate for EDL mode .
i don't want to mess up anymore i think ill give this to a technician. gonna be a while is it ok to let the battery die.
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
purenoob said:
came across a blank flash my phone is RETLA but the flash is RETBR does it matter ?
Click to expand...
Click to collapse
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
bootloader was unlocked before all of this happened, so does this mean i can use a android 10 back flash or use an android 11 one for avoid trouble again.
sd_shadow said:
If the bootloader is unlocked it should be fine.
Don’t worry about the battery, edl is very low power, battery can last weeks, and should still support charging
Click to expand...
Click to collapse
ok so now i'm getting this error.
Opening device: \\.\COM5 [ 0.002] Detecting device [ 34.509] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error [ 34.510] Check qboot_log.txt for more details [ 34.511] Total time: 34.514s FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
purenoob said:
YES!! finally i got it into flashboot mode i just had to hold the pwr button 10 sec and tried blackflash again.
now im gonna dl RSA to get the correct stuff for my phone.
Might be to early to say but Thank you so much for the help!. ill post back later to update you.
update: success on flash still on a11 dont care its working again money saved.
i Wanted to downgrade becuase since this update my YouTube at higher resolutions would stutter and some of my main games started to chug in certain places.
phone lil hotter etc you know the woes oh well its working now thanks a million thanks again.
Click to expand...
Click to collapse
Hey just reporting back i thought i could bear with android 11 but i just couldn't. Being really really carefull this time i managed to return to android 10.
Using the fastbootd method before i ignored it and flashed in regular fastboot. So this time i followed every step to a tee.
just wanted you too know and as all always thx sd_shadow.
Not sure how to proceed here. I had a very recent twrp installed, flashed a new ota firmware update as I have successfully a couple of times, phone restarted to twrp, I decrypted, it flashed the firmware fine then went to restart.
And that's it, completely dead, battery was at least 50% charged.
I can't enter recovery, power button held for one minute does nothing, vol+ and power, nothing, vol- and power, nothing, vol+ and vol- nothing.
Plugging in my charger, nothing, plugging into a laptop and pc, nothing. Took the back off and disconnected the battery and left it over night, nothing.
Bootloader was unlocked and usb debugging enabled.
Anyone have any other ideas what I can try here?
Also tried bridging the contacts for edl mode with battery disconnected and plugged it into USB but nothing.
Very tricky to do this though as you need 4 hands and it's possible I'm not making contact on both pins, purchased a cheap edl/deep flash cable as a last resort, if that doesn't work then I think it is toast.
Does your device have a file you’d an flash in edl (Eg. Firehose)?
Arealhooman said:
Does your device have a file you’d an flash in edl (Eg. Firehose)?
Click to expand...
Click to collapse
I may have found a couple of resources but I'm unsure of the procedure, is there any chance you could provide me with some information, I'm stumped on how to proceed.
Johnnio said:
I may have found a couple of resources but I'm unsure of the procedure, is there any chance you could provide me with some information, I'm stumped on how to proceed.
Click to expand...
Click to collapse
From what I gathered you need to find a special “firehose” or like file that allows yout o flash it in edl. You seem to have gotten very very lucky because from a simple Google search, I found firehose files. They may or may not work.
https://support.hiunlock.com/index.php?a=downloads&b=file&id=1133 I found this, but I think it may cost money (I don’t want to make a acc, but from browsing the website, it seems it costs 20 dollars, which is a barbain for a device). You are lucky it exists at all though. I do not vouch for the file or site though. You should o research on how trusted it is.
Arealhooman said:
https://support.hiunlock.com/index.php?a=downloads&b=file&id=1133 I found this, but I think it may cost money (I don’t want to make a acc, but from browsing the website, it seems it costs 20 dollars, which is a barbain for a device). You are lucky it exists at all though. I do not vouch for the file or site though. You should o research on how trusted it is.
Click to expand...
Click to collapse
Thank you, I will have a good read and look at other sources.
I'd love to know how the hell this happened, had the device for years now and flashing with zero issues.
Johnnio said:
Thank you, I will have a good read and look at other sources.
I'd love to know how the hell this happened, had the device for years now and flashing with zero issues.
Click to expand...
Click to collapse
Yeah, must have amde a small mistake, or ahd a corrupt file
“EDL is an interface of Qualcomm chipsets, used to flash fastboot ROMs. It is used for unbricking purposes so it is allowed on many phones but it's been locked down on most recent Android models.
The screen will appear black and it will appear that the device is turned off, but to verify that this is not the case, we need the tools in EDL mode. The most famous is QFIL (Qualcomm Flash Image Loader), a proprietary software, but on GitHub there are many alternative open source projects.”
https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ the beginning of this article explains edl mode very well
Arealhooman said:
https://www.thecustomdroid.com/qualcomm-edl-mode-guide/ the beginning of this article explains edl mode very well
Click to expand...
Click to collapse
Excellent, thanks again for your input.
Johnnio said:
Excellent, thanks again for your input.
Click to expand...
Click to collapse
Yep, reach out if you have more questions, and keep me updated with if you managed to save your device.
Arealhooman said:
Yep, reach out if you have more questions, and keep me updated with if you managed to save your device.
Click to expand...
Click to collapse
Will do
I am late here, but just want to add i also had same issue
And edl can be fix with xiaomi third party tools with little fee to provide you authorized rom flash to boot phone from edl