Related
I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing
slplsnphx said:
I was trying to install a custom recovery (twrp) by several different methods, with absolutely no luck (but that's another secondary issue at this point) and i screwed something up. Not exactly sure but i think the last thing I did was:
using "Rashr - Flash Tool" i think i went to "flash kernel from storage" then flashed boot.img.
now the phone goes immediately, directly into fastboot even without being connected to computer.
so i tried getting into the stock recovery by holding "volume down" and "power" until lg logo, releasing the reholding until factory reset screen. after choosing yes 2 times i get a
"boot certicification verify" or something message for about a second then it goes to this screen (sorry but apparently i haven't had enough posts on the forums to include clickable links.)
h**ps://drive.google.com/file/d/0BwQdFsCQ9KZVaGM1eWdJb25WVVU/view?usp=sharing
Click to expand...
Click to collapse
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
amin44 said:
if u still have acces to fastboot use this or u see many disk at windows use srktool http://forum.xda-developers.com/lg-g2/development/tools-srk-tool-useful-toos-lg-root-twrp-t3079076
Click to expand...
Click to collapse
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.
slplsnphx said:
ok, i do have access to fastboot (actually, as soon as i power it on, it immediately is in foastboot mode, even without being connected to computer). i tried using srktool's repair tools via fastboot. it seems like it's working (ie phone shows that it receives command) but that's it. does it take a loooooong time or something?
btw, i can also get into download mode by holding "vol up" while plugging into computer. so, i tried using srktool utilites via download mode and nothing.
also, i just noticed that while connected to computer in download mode, in device manager it shows G2 under "portable devices" with an exclamation point on it.
Click to expand...
Click to collapse
are u sure u do not have franken phone open battery cover and see model written inside motherbord
amin44 said:
are u sure u do not have franken phone open battery cover and see model written inside motherbord
Click to expand...
Click to collapse
I haven't taken the back off (yet) but all indications are that it's an AT&T (D800).
What part of my description makes you think that it might be a franken phone?
Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?
audit13 said:
Did you try connecting the phone in download mode or fastboot to the LG Mobile Support Tool and performing an upgrade recovery?
Click to expand...
Click to collapse
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.
Is it recognized by the program in fastboot mode?
Here's the program I was referring to: http://www.lg.com/ca_en/support-mobile/lg-LGD803
Even though the program says it is for the 803, I used it to recover my international d802.
slplsnphx said:
not sure what you mean by "lg mobile support tool". i googled it and found and installed "lg pc suite". is that the same thing?
nevermind that last question. i found and installed and tried the upgrade recovery tool but for some reason the phone wont go into download mode anymore. when i power it up whith ""vol +" help down, it shows download mode for a second, but then goes right into fastboot mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
amin44 said:
http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404
Click to expand...
Click to collapse
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?
ok, so likei said my phone is indeed in fastboot mode, connected to computer via usb (shows up in device manager as "android device > USB modem phone port". using srktool, i can send commands to the phone (command shows up on phone but thats it.....doesnt matter what command, it just sticks there until i unplug the phone then srktool shows the operation competed and phone shows
https://drive.google.com/file/d/0BwQdFsCQ9KZVSVg3OTZLcXV0N0E/view?usp=sharing
but none of operations actually complete on the phone.
slplsnphx said:
Thanks for the reply! But when I have phone connected to USB in fastboot, it shows up in device manager as "android device > USB modem phone port". Is that method the right fix for my situation?
Click to expand...
Click to collapse
that method fix for all situation
amin44 said:
that method fix for all situation
Click to expand...
Click to collapse
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?
slplsnphx said:
ok i shorted the capacitors, and eventually have gotten to where i can get into twrp. i assume that is serious progress, but what do i need to do next?
Click to expand...
Click to collapse
flash stock ROM via download mode or flash custom ROM via twrp.
the first choice (stock ROM) is better
thanks for the responses!!
before i saw your reply, i flashed the stock .tot firmware and now i have my phone back.
but, before all this started, it was lollipop(5.0.2) and now it's Jellybean(4.2.2). i bought phone on ebay, so im assuming that it got lollipop via an ota update. so now i'm looking into flashing it back to lollipop. what's the easiest method to install stock lollipop?
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Xluk3 said:
HI everybody, I have a very big problem with my zuk. Trying to solve a problem about network, I thought to come back to stock via fastboot. But given that I was tired doing so many tries, I wrongly flash a zip file via fastboot instead of use adb, so the phone didn't turn on anymore. I must say first of all that it isn't my first phone, so I'm not a newbie. The real problem is: When I plug Zuk into my Pc( Windows 10) it isn't recognized as qhsusb_bulk ( It could be easy to solve the problem) but as "unknown usb device (Device Descriptor Request Failed)". I try to plug the phone pressing every button like Vol+ and power, Vol- and power but nothing to do. I' m already in Test Mode on Windows 10 and I deleted every Zuk or Qualcomm Drivers. Anyone can help me?
Thank you
Ps: Even If the screen is always off, Is there a way to boot into fastboot mode with hardware keys?
Click to expand...
Click to collapse
Not that I know,do you have the stock recovery or twrp?
I have the exact problem with my new zuk z1. Any idea is appreciated. The nice phone seems lost now.
Seems like you'll have to restore your zuk to the zui version again. Do you have qrst and zui version downloaded??
The service port never pops up
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Setup.zuk said:
I do have the qpst and the zui rom. The main obstacle is that qualcomm service port never pop up.
Click to expand...
Click to collapse
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Nikosstamatiou said:
try this:
start QFIL from the QPST folder
Click browse on the programmer path row and select prog_emmc_firehose_8974.mbn from the directory where you unzipped the QPST ZUI ROM
and then click browse on the search path row and select the xml file + the other patch file which comes after it.
When thats done, make sure phone is off and then hold vol+ while you are inserting usb cable into phone and QFIL should then detect phone,
you may need to select port in the QFIL program and be quick with it, took me a few tries before I got it right so just take out the cable
and turn off and try again if you fail to make them connect.
Not only you need to select comport, you also need to press the download button aswell as soon as possible or else phone will continue booting as normal.
If everything went well then you should have ZUI loaded onto your phone and you are met with Chinese language as default.
On the first screen you are met with, just press the button in the bottom (on screen), then press cogwheel (which is the settings),
scroll down to yet another cogwheel in here which should be below a lock icon, then press second option in here and then the top option
to change language to english incase you cant make out the chinese and you should be good to go
Click to expand...
Click to collapse
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Tarsa said:
So i am having the same problem. The phone is not being recognized by the software. That is the whole problem. Any ideas?
Click to expand...
Click to collapse
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
mikarbach said:
Actually, I think the problem is, that it will not reach the fastboot mode, due to the non-stop process of system-updating and boot-loop. I can observe for a very short time the message 'systemupdate will be installed' and then the screen becomes black again. This procedure is repeating every time. I will wait till the battery is empty and see, whether the boot with Volume-+--USB-cable will work.
Click to expand...
Click to collapse
PLease do update me if you manage to fix it. This is getting very frustrating
I have the same problem, caused after a cyanogenmod update... Did someone fix this??
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
I've tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
CarlosAir said:
Another hard bricked Z1 here.
QFIL recognizes the phone (as Qualcomm 9008 etc.). So I am able to click Download, but after a few seconds, it fails with these errors:
Code:
[...]
Sending NOP
NOP: Fail Code: 9
Unable to send FireHose NOP, Device is not in Firehose mode !
Download Fail:System.Exception: Failed to send Firehose NOP to the phone.
in QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()
in QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)
Download Fail:FireHose Fail FireHose Fail
Finish Download
If tried many many times, and many different things. Still no luck .
I'd appreciate if anyone could input some new ideas of other stuff to try. Thanks
Click to expand...
Click to collapse
No idea, my device is actually dead.
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
CarlosAir said:
Aw .
I don't want to lose hope, but everything I've tried so far has failed. :| , and I don't know what else to try.
Click to expand...
Click to collapse
Try another cable, another USB slot, another pc/laptop
mikarbach said:
No idea, my device is actually dead.
Click to expand...
Click to collapse
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
t.h.i said:
try to flash cos 12.1 with qfil.
its there somwhere on 4pda forum(search there).
Sent from my Z1 using XDA-Developers mobile app
Click to expand...
Click to collapse
Of course I have tried this, with two different computers and two different USB cable, both actually working on my N5X. But the point is, that I do not reach the point, that qfil recognizes the phone. Also not with the trick of starting with power-button/USB-cable. It constantly tries to reboot and with adb I get a message 'not authorized' .
---------- Post added at 11:17 AM ---------- Previous post was at 11:05 AM ----------
carlese said:
So guys if I try to flash unofficial CM 13 do I risk bricking the device for good???
Click to expand...
Click to collapse
I think in my case the after the first successful CM13-snapshot-installation was two fold:
1. I have not enabled USB-debugging and do not have had connected it to my computer after the first CM13-installation.
2. Due to some unknown reason the automatically update via CM itself has boot looped.
The second point is not a real problem, I think. I have had a bootloop many times before with other phones, as well as with the Zuk, but I was always able to resolve the problem with adb. I think the first point was the problem, so adb wasn't possible, due to authorization problems. The reason why qfil does not work, I really do not know exactly, but qfil in fact was not able to recognize the phone.
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
alexisdance said:
I have the same problem. Totally bricked.
No charge, no PC recognise, nothing.
I tried with QFIL but the PC does not recognise the port.
I don't know what else I can do. Any ideas?
Thanks!
Click to expand...
Click to collapse
Sry, no I do not have
Hello!
I have dealt with this sort of problem before and have successfully un-bricked my friend's device. I will be posting a guide to solve this problem soon.
Hang-on!
Hello!
As title says i bricked my Axon :crying:
I followed http://forum.xda-developers.com/showpost.php?p=68738854&postcount=100 (and the german one that linked to this one) but couldnt do the fastboot unlock.
So i couldnt finish this and my phone required a pin number to start android: bootet and started up but wanted a pin code to start/enter system.
Wasnt able to fix that with googling for answers so i went back to edl mode and rewrote my backup boot/recovery images with axon7backup.
Had no errors with that but it wont start now:
After the ZTE Logo the display goes black but it connects as "handset diagnostic interface (DFU) (ComX)" to my computer.
I fiddled around with driver installing etc and forced the HS-USB QDLoader 9008 on it but no luck, axon7backup/root can not connect.
When i did the actual flashing yesterday it never connected with the hold both vol-keys and connect usb way either, always had to reboot into edl via adb.
I cant boot anything else (no twrp/recovery) it just goes to the diagnostic interface mode.
Thanks in advance
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Starvirus said:
you can try to get into adb mode with this:
- power off your device
- hold the vol down key while plugin in the usb-c cable (connected to your pc)
- keep holding
- you should get a white box with FTM factory test mode
- you are free to use adb again - so you can get into edl mode as well....
for pin part that'S normal while unlocking your device encryption gets deleted and you have to abort and factory reset your device in twrp....
Click to expand...
Click to collapse
Thanks. I tried it but it wont go to FTM. Only goes to diagnostic com port.
It seems i cant even turn it off. The little red light on the front is on the whole time .
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
adb don't show your device?
Starvirus said:
sadly the disadvantage of a built in battery, so you have to wait till the battery is empty and try my instructions then....if it's not realy off it won't work, the mode you are currently in you usually only reach if you switch it on while holding both volume buttons, the edl mode is sadly not reachable with a key combination directly on G models.
Click to expand...
Click to collapse
Oh ok. I expected ftm to work from vol-down and power-button till restart.
@adb: sadly no connection possible since it goes straight to Comport Connection.
Edit:
Couldnt make that work. It was off and i connected the usb. So it showed me the loading battery picture where i cant do anything. held the vol-down the whole time. But as soon as it had some battery it went straight to comport-connection again
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
nsabir said:
i have the same exact problem :'(
Have u been able to fix it?? I'm in a situation that i cant even send it to ZTE to fix it :'(
Click to expand...
Click to collapse
Hi,
couldnt fix it myself so i had to send it in.
Unless some tool/rom was released in the last few months to fix it yourself i would guess your device is bricked.
Hi I have almost the same problem, I tried to unlock bootloader and now I don't have the recovery, I can boot and use my mobile but I can't restore it or update it because I don't have the recovery
I try whit axon7tool to restore the recovery but I got a error.
MaxRink said:
im sorry to say, but ur device is bricked to a degree where you would need ZTEs Flashtool to fix it. Unfortunately we dont have that tool, so you might have to send it in
Click to expand...
Click to collapse
Hi, do you have any idea, if there will be such a flashtool to work with DFU mode? I'm thinking that there are a lot of guys have bricked their devices (including me).
((
Hey!
Z2 owners that like to mess around with their phones are prone to get f#ked. I was there and I faced the problem some of you probably did - a hard brick. There are a ton of tutorials on how to fix it, but I believe I found a new way that doesn't envolve resetting it. I have only tried with twice on my phone, so I'm really looking forward to know if it's universal!
Scenario - Your phone has a black screen. The notification LED is on. If you hold the power button it flashes the ZUK logo and it vibrates. If you identify with this scenario, go forward!
1 - To turn off your device (if you haven't already), press the power + volume up. The phone will vibrate, flash the ZUK logo, turn off the LED and turn it on again. Continue holding both buttons. When the LED turns off again, REMOVE your fingers from both buttons right away. If done correctly, it won't come back again and the LED will be off
2 - Hold both Volume Up and Volume Down at the same time. Connect to the computer. You should encounter your Fastboot mode (with your baseband and other info blank).
3 - Go to your email and redownload the bootloader unlocker. Yes, remember that file? Use it. You can use one of those unlock bootloader tutorials online, but if you know what you're doing, here's the command:
fastboot -i 0x2b4c flash unlock unlock_bootloader.img
4 - Right after that, run this other command
fastboot -i 0x2b4c oem unlock-go
That's it. You should be able to go to the recovery (flash it again just to be sure). Try it out and tell me how it goes.
not working...phone is gettin turned off...but holding up and down..then connecting is doin nothing..it just keeps on going on and off again
This method worked for me,thank a lot of,great trick
Sent from my Redmi Note 3 using Tapatalk
you my friend, are a god among men, i owe you a beer.
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
vardhan21 said:
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
Click to expand...
Click to collapse
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
paps2k3 said:
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
Click to expand...
Click to collapse
hey thnks bro...i successfully enabled 9008 port and flashed firmware
thanku so much
Where were you man I have to cut my wire and format my phone for flashing new firmware
My phone don't show the led light
No button combination works
I was restoring twrp backup and the next boot...And i was bricked
It shows diagnostic mode 900E
Please help
Finally done
vardhan21 said:
fastboot mode conncted and flash unlockbootloader.img file..but not boot mobile shows error msg .my bootloader is unlocked any suggestion plz
Click to expand...
Click to collapse
Had the same problem and first i went to download mode by following the the below link
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/
then i downloaded the stock firmware and followed this guide
https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/
Both of them helped.:good::fingers-crossed: hope they work for you
Please tell me the process for recover from hard brick, because zukfans.eu is no longer available.
paps2k3 said:
Same thing happened to me..followed this link https://zukfans.eu/community/threads/how-to-unbrick-zuk-z2-from-diagnostic-port-900e.2856/ as my phone showed 900E mode in Qfil ...followed and unbricked..mine bootloader also showed as unlocked
Click to expand...
Click to collapse
What is the process??? Please tell me here because zukfans.eu is not accessable
Rit2005 said:
What is the process??? Please tell me here because zukfans.eu is not accessable
Click to expand...
Click to collapse
Hi ..very sorry..not using z2 plus for a long time..I forgot the process what I did..I followed the steps mentioned there.
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
me too
waiting, someone pls
LeandroFarias said:
waiting, someone pls
Click to expand...
Click to collapse
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed).
That is the points
vinod3362 said:
That is the points
Click to expand...
Click to collapse
What?
me too. after i reboot my poco m3. it came to black and wont boot up. i google everything, the only need to flash is to modified the firehose. badly needed.
KaMyKaSii said:
My M3 was working perfectly. I put it to restart and then it didn't turn on anymore. It is now only recognized as "Qualcomm HS-USB QDLoader 9008" on Windows. I opened the phone and with some magical combination (remove/connect flat cables from the battery and display, connect the USB cable, press volume keys and short the test points) it started in fastboot. So I was able to flash the "fastboot ROM". Unfortunately, on the next boot it still does not turn on normally. Has anyone succeeded in repairing the Poco M3? In Mi Flash is requested an authenticated account to flash through it, is it worth paying someone to provide the account? Does anyone have the contact of someone who makes cheap? Any help is welcome, thank you!
Click to expand...
Click to collapse
how do you get into fastboot?? i tried mine but it wont boot in fastboot. i'm stuck in QDLoader.
did someone successfully recover their bricked poco m3 ?
gasleak08 said:
did someone successfully recover their bricked poco m3 ?
Click to expand...
Click to collapse
nothing yet. we need firehose to bypass miflash authentication. or drain the battery then press vol down + power for 10secs.
KaMyKaSii said:
I kind of managed to get my Poco M3 to start on Android (but it's not fully fixed). Are you Brazilian too? Call me on telegram
Matheus
You can contact @MatheusCoelho1998 right away.
t.me
Click to expand...
Click to collapse
can u tell me how?mine too?
my phone has bricked with UBL condition and i flash whole partition with twrp and magisk to solve the heating problem now its alive again
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Minoda86 said:
I just wait till the battery totally discharge and then plug in the charger,sofar been through this problem for 2x,the first one for 2 days and 5 days for later because the battery was full.
This happens when Im restarting the device and now even there is a new update,Im still scare to update my device to the latest firmware incase it wont boot again.
Should I try to update or nah,guys?
Click to expand...
Click to collapse
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
I did update it and now my phone wont boot at all,after the battery hits 1%,it just wont do anything and its been 2 weeks,pc does detect it as qualcom loader but flashing without auth wont work,Im just waiting for firehose file for this stupid phone.People with auth asking for $30 for fixing it but without guarantee that it will work,what a joke.
So did you fix your phone?
yankee77 said:
do not try to update it... i tried 3 times their own ota update broke the phone os which makes it unable to go to recovery or fastboot. i will try and see if i can update firmware and fix itself
Click to expand...
Click to collapse
Yeahhh,my phone finally boot up!
But sadly the latest update failed to install.Guess I should just wait until someone patch the firehose file and try not to update until then.Fingercross!
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
vinzikidz said:
i fixed the deadboot issue. but it wont fix the restart deadboot. try to flash every region and version firmware both recovery and fastboot. the problem still there.
Click to expand...
Click to collapse
how did u fix deadboot can you elaborate? how did you flash from edl ?
gasleak08 said:
how did u fix deadboot can you elaborate? how did you flash from edl ?
Click to expand...
Click to collapse
sorry, there's is no tutorial for this and it has a quite process. you just need to throttle the proc temperature of your phone board using hot blower or any device you have. while your phone is in high temp. both pin board and battery is in unplug hold vol down then put back the board pin and battery pin at the same time. it will vibrate and fastboot will be fine.
Guys this is my procedure to turn on the phone:
I can make it turn on Android after messing with the battery and sub-board cables but this is just a workahound, trying to turn it on normally through the power button always makes it turn on in edl mode
But opening the device voids the warranty, so anyone who has access to a repair center is better off asking for the warranty
What to do:
1. Disconnect the battery cable and the secondary board cable.
2. Connect charger.
3. Hold the power button.
4. Connect the secondary board cable and quickly connect the battery cable.
5. Release the power button when the device vibrates.
It doesn't always work the first time, you may need several tries to get it
VID_20210514_152510.mp4
drive.google.com