Database Users

[Q] DemiGod Crash Handler : Critical Error! Plzz Help Someone

my phone LG G2 D802 International Version was running perfectly fine i tried to flash another rom by LG FlashTOOL and in the first i got soft bricked on that fastboot screen i recoverd it by ADB (fastboot.exe)
fastboot erase recovery
fastboot erase laf
fastboot flash laf laf.img
and then i tried to reflash it then i got this mesg on screen
---------------------------------------------------------------------------
Critical Error!
---------------------------------------------------------------------------
DemiGod Crash Handler : Critical Error!
Press Key to Choose Dload Mode or Reboot
1) Volume up : Dload Mode.
2) Volume Down: Reboot.
If u choose Dload Mode.
please do following action.
1) Dload Mode. please Connect USB
2) Get the Ram Dump image using QPST Configuration.
-------------------------------------------------------------------------
Board Info
Rev. : 1.1 speed.pvs : 1.1 Serial : 01e862cf934fc622
Please Help me somebody ... i cant afford to buy new phone i just bought this phone a week ago ..

Having same issue ! XDA forum experts always helped me with every situation with my phones. Expecting help this time as well from you experts.

Same here, enyone can help, i stuck with the sam message, presing vol- just rebots, and vol+ sends message "jump to download mode" but i cant flash stock firmware

i have the same problem any help ??

I have the same issue too, can anyone help?

I heard that this can help you guys. Use the search option there and try to fix it. Actually i had the same problem few months ago, but for me mew motherboard was the solution... If you're device is under warranty send it saying it failed while taking OTA. Good luck...

lg g2 critical error
I have done a flash to my g2 32gb d802 and it suddenly entered into critical error not going into any of thefastboot mode or download mode even though it is giving me options.....please any one help me out to get my phone back to normal ........

PM me if you guys need help.

I had the exactly same problem, and I had to go to afterservice center to repair. Engineer told he would wipe everything and install new rom. but He failed to write rom so he simply changed mainboard.
At first I had thought about open my g2 and makes it go into qualcomm download mode by short-circuit.
the reason I didn't was my warranty was still available.
I tried every method to make it boot into recovery or download mode but I failed. In my opinion, you may try short-circuit method for last solution. In this situation, even linux doesn't mount rom's storage section. Only if you can make G2 recognized in Linux, G2 will revive.
good luck.

xmayhemreturnsx said:
PM me if you guys need help.
Click to expand...
Click to collapse
i still don't know what to do HELP

yassou92 said:
i still don't know what to do HELP
Click to expand...
Click to collapse
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. However, when you get the demigod error plug in you usb and click up and it should start download mode even though it doesn't show it.

xmayhemreturnsx said:
The best way to go if you do not have a warranty is to short circuit the board and get into Qualcomm ... 9006 mode. .
Click to expand...
Click to collapse
How do you short the pins? There's a guide here on xda but it's so difficult to undestand. I need to know how can I short the pins.
it should start download mode even though it doesn't show it.
Click to expand...
Click to collapse
No, it doesn't. I try to use flashtool but it doesn't recognize the phone. No download mode in any method I tried

I got into this error after I had previously recovered into qhs_usb9006_bulk mode from a hard bricked D801, by shorting the capacitors on the main board. After entering qhs_usb9006, I used srk tools 2.1 for my phone, and after they finished, I tried entering download mode, only to get into this error. I really don't know what it is to say about this. Everything turned wrong with this phone, it went from simply failing a .kdz, to stock .tot, to hard brick, and now to this error, whereas it should've just enter the download mode, as for the 99,99% of the others. Any help would be really appreciated. Thanks.
L.E. I shorted the capacitors again (the one i the middle, like I did the first time, when i got into 9006 mode. 5000 and 5004 didn't work for some reason). This time I got into dload mode, which is 9008. I'll try to recover the phone from here, with this method:
http://forum.xda-developers.com/lg-g2/general/fix-unbrick-lg-g2-stuck-qualcomm-hs-usb-t2933830

i had this problem while trying to return to stock. Fixed it by following this guide http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404 . it needs some hardware tampering though. i tried and tried but i cant flash the phone any other way. the way i understand this is due to bootloader being corrupt.

I installed autorec from playstore solved all the problems

Than you! autorec worked for me too

Can someone post a KK baseband for D801 (T-Mobile)? I'm on D80120a software version with unknown IMEI and baseband (the phone is a D801 refurbished into D802, I more than hardbricked it by flashing wrong .kdz, got it recovered through shorting pins, 9008 mode, got download mode, D80120a stock, root, twrp, after a very long and painful process of about 1 month). Now I have to make use of QPST, but I have to obtain a valid baseband first. Of all links I've stumbled upon, only 5% or less of them are still working, so I only have one flashable modem, in twrp recovery, which corresponds to D801 jb version.
http://downloads.codefi.re/autoprime/LG/LG_G2/G2_modems
cloudyfa kk_baseband_D801 only make my phone restarts like crazy.
I'm simply stuck and pray for some devine help.
Thank you.

Weird enough, I flashed a canadian modem and I got both baseband and IMEI. Why did I do that in the first place? Because I remembered that before all these things happened to my phone, the baseband was M8974A-AAAANAZM-1.0.190082, which corresponds to D803. So I said to myself what can happen by flashing the wrong modem? Boot loop, easily fixable with the phone in it's current state. But again, after 1 month of trouble with the phone, I'm back to what exactly started it in the first place: phone seem to work OK but it has 2 huge problems: WiFi extremely weak (2 meters away and a wall or 5 meters away and no wall a and I lose the signal in both cases; the 2nd is wit the GPS - 20-30 meters error). No idea how should I adapt the radio to Europe region (by keeping the canadian one and change the settings, if it's even possible/fixable this way or if this even does make any sense).

I had to do a hard brick fix to get it into the QSUSB mode to flash TOT.

Have you tried using LG Support tool to put it back to stock?
Sent from my LG-F350K using XDA Free mobile app

Hard brick SM-N910F

Tried installing custom recovery didn't work out like I had hoped now im stuck with a phone that isn't detected by odin or kies but by MiFlash
Please tell me there is something I can do to fix it or get it to some sort of working order..? Is there a jtag tool or usb jig I can use?
Update - I found out the phone was still under warranty so I sent it away to be repaired. It was repaired and I now have a working phone !

ylmcc said:
Tried installing custom recovery didn't work out like I had hoped now im stuck with a phone that isn't detected by odin or kies but by MiFlash
Please tell me there is something I can do to fix it or get it to some sort of working order..? Is there a jtag tool or usb jig I can use?
Click to expand...
Click to collapse
What have you done to reach that state? I know that you're desperate but you must give some details if you want help.

It was given to me with 5.1.1 installed however it failed mid process and while on 5.1.1 it kept freezing and acting weird such as boot with weird errors and they only appeared after it was updated, I decided to root it with odin and it never fully rebooted after the was root applied. I finally got it to boot to stock and rooted and decided to install a custom recovery which was twrp while selecting the recovery it said if its a wrong location it will brick, with this in mind I checked the model with the one on their site and it seemed to make sense and applied it.
This caused the original problem which made it boot straight to download mode with it saying it could not normal boot. I then googled the problem and one said the pit was corrupted and downloaded the correct file. I then applied this through odin with stock firmware and it refuse to flash. At the time I was thinking a restart on the device would help, but it resulted in not booting at all and not being detected....
It does not light up or make a vibration when its connected or powered on if there is any solution it would be great...

Can anyone help or point in the right direction?

Hard brick SM-910F
Hello! If this is the good recovery for the N910F he would have from start.
Try to boot via the recovery flight up + home + power.
If you TWRP flash a custom in a first time rom

[email protected] said:
Hello! If this is the good recovery for the N910F he would have from start.
Try to boot via the recovery flight up + home + power.
If you TWRP flash a custom in a first time rom
Click to expand...
Click to collapse
Nothing however the pc did detect a new driver called qualcomm hs-usb qdloader 9008

ylmcc said:
Nothing however the pc did detect a new driver called qualcomm hs-usb qdloader 9008
Click to expand...
Click to collapse
qualcomm emergency download mode. is it called.

Tunestwo said:
qualcomm emergency download mode. is it called.
Click to expand...
Click to collapse
Anything I can do to get some sort of os on the phone now?

in this case via Odin tries to reinstall the tar of the official rom N910F .

ylmcc said:
Anything I can do to get some sort of os on the phone now?
Click to expand...
Click to collapse
Can you tell us if you can get on recovery screen, either TRWP or stock, or download mode.

You could try installing these drivers:
https://www.androidfilehost.com/?fid=24499762636000789
Reboot just in case and try to connect your device again.
(In download mode, with the key combination)

mangui said:
Can you tell us if you can get on recovery screen, either TRWP or stock, or download mode.
Click to expand...
Click to collapse
The phone does not display or respond when the keys are pressed, just a black screen..
Battlehero said:
You could try installing these drivers:
https://www.androidfilehost.com/?fid=24499762636000789
Reboot just in case and try to connect your device again.
(In download mode, with the key combination)
Click to expand...
Click to collapse
Chrome detected a virus in the rar

ylmcc said:
The phone does not display or respond when the keys are pressed, just a black screen..
Chrome detected a virus in the rar
Click to expand...
Click to collapse
Really? I just scanned it with VirusTotal and it is clean.
Virus Total Results
32Bit.exe scan results
64Bit.exe scan results

Battlehero said:
Really? I just scanned it with VirusTotal and it is clean.
Virus Total Results
32Bit.exe scan results
64Bit.exe scan results
Click to expand...
Click to collapse
I'll download it again but windows defender detected it too.
Edit - Yep did it again, here is a link to a photo of what I get but from virus total I don't get why its being flagged perhaps false positive ??

Update
Found a jtag service that is cheap will update once I get it back...

sm-n910f
I got a brick note 4 and i want to fix it
I search over the internet for this solution and found a method
Sd card repair boot but it did not work at all
I need help
thank you in advance

Bricked A2017G B03 - help please

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).
((

Help sort of "bricked" phone to unbrick!

My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!

manav113 said:
My Asus Zenfone Max Pro M1 is stuck on the screen," Powered by Android". I have neither rooted nor unlocked the bootloader. I had received the error of "Your device is corrupted" and had followed the guide to remove that. For a month, my phone lagged and had a drop in battery. Restarting it has caused it to not work.Now, it's showing no signs of starting. Any help will be sincerely appreciated!
Click to expand...
Click to collapse
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.

P53mutant said:
download 059 fastboot rom[search in forum you will find 059 fastboot rom. it is in-(how to use flashtool thread)]
unzip it.
connect your phone with pc as in fastboot mode.
double click on flashallAFT.bat or .cmd file from fastboot rom folder.
059 fresh installtion will be donw by this although you will lose all your data so please backup if possible.
after that if u still have that 'your device is corrupt' error follow my thread . corrupt state fix command dosnt mess with your system whatsoever. so either u deleted some files accidently or it got deleted during update. dont blame any buddy regarding that.
Click to expand...
Click to collapse
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.

manav113 said:
Thanks for Replying bro. TMy phone is not going to any mode ie neither fastboot nor recovery. Its only showing Powered by Android whatever combinations I go with.I am thinking to try the QFIL s/w.
Click to expand...
Click to collapse
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.

P53mutant said:
go for qfil then but use 059 qfil otherwise 130 qfill u will lose your persist,factory,fsg partition. doownload 059 fastboot rom . it is combined fastboot qfill rom. use it same as other qfill rom but choose here ww_no-nfc_no-fsg raw program.
btw your device showing powered by android that means u can go into fastboot mode and recovery mode both. just press and hold power button untill u see restart of ur screen. as soon as u see that press violume up along with power key. u will def get acess to fastboot mode.
Click to expand...
Click to collapse
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?

Try asus service center

manav113 said:
Didn't worked.. QFIL s/w was not able to detect the port even after connecting the mobile.. Tried to completely discharge and recharge hoping it would work.. Now, its not even recharging.. Nothing works now..Feels like a motherboard problem now..Should I rebuy the 4GB version or look for another mobile?
Click to expand...
Click to collapse
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.

98har**** said:
Try asus service center
Click to expand...
Click to collapse
No response. They said they aren't able to fix it. Can give 1k for the lcd screen.. :crying:

P53mutant said:
motherboard issue not lead to sudden death of phone. did u encounter random reboot before every 10-20 mins if not no worry.
for qfill u have to turn off your phone and press vol + and vol - together and have to connect your hpone with pc. check device manager of pc it will show port and comt device 2-3 mins after successfull qualcomm diag port driver installation.
Click to expand...
Click to collapse
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.

manav113 said:
Didn't had any random reboot stuff. I thought voltage fluctuations might have affected it. I had charged it at the Airport the same day the phone gave up. The QFIL software was not able to detect port even while pressing vol+ and vol- .Service Centre tells me its a PCB problem and are asking 3k for repair. Looks like a new phone is somewhere in the line for future.
Click to expand...
Click to collapse
well good riddance

Hardbricked to Qualcomm USB 9008

Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.

DarthVader said:
Really hoping someone can help me out here. I have a Nexus 6P, Non-BLOD. Yesterday, after clean flashing the latest version of EvoX, while setting some things up, device randomly crashed. No Shut down animation or anything. Just black screen. Tried turning it on via Power Button and then Power And Volume Buttons but nothing works. Connected it to PC and see it's Detected as Qualcomm USB Bulk (9008) in Coms and Ports. Did some research and found out I have to flash via QFIL. And this is where I am stuck. I tried several versions, but it doesn't flash/gives Shara error. I tried reinstalling driver. I also read a guide here. But the Firmware link is dead and it says to flash via MiFlash, something I can't even try since the Link in the OP is dead. I tried some different versions of QFIL but all of them give a Sahara Communication error. Now I'm pretty much at a loss on what to do. I'd really like to fix my 6P. And I would appreciate anyone taking the time to point me in the right direction, or help me fix it. Thanks in Advance.
Click to expand...
Click to collapse
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace

hk1271 said:
Same thing happened to me in the same ROM (Weird) .. but i managed to flash the qfil successfully .. but still phone doesnt boot up .. here's what you should do ... try to hard reset the phone until you hear the disconnecting sound from pc . Ready all the necessary flash in the qfil and as soon as u hear the device connected hit the download button .. it will flash without the sahara protocol error . Be quick ! tell me if that fixed ur problem . Peace
Click to expand...
Click to collapse
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.

DarthVader said:
Thanks. Can you share the files you used please? I can't for the life of me, find the correct download files. There was a Nexus6P_Unbrick by TenFar but all the links are down.
Click to expand...
Click to collapse
I used another qfil firmware
https://drive.google.com/file/d/1PixuumVVzxBKUsQ88X3AJ21Hsi2mV3Zq/view
Here is the link .. you can find the firehose and all files in the firmare folder . Best of Luck

I have a similar situation where I am unable to power on the phone in any way, and I am only able to communicate with the qualcom USB 9008 driver.
I am following your instructions using the firmware files you provided (thank you!) and I can see an attempt is being made to download the files before sahara error occurs.
I don't think I enabled developer options when my Nexus 6P was working and wondered if sahara error is due to that.
I was wondering if you had previously enabled developer options by tapping on the build number several times, once the operating system booted and if that is a critical step in being able to recover the Nexus 6p from this hard bricked state where I am stuck in EDL 9008 mode, and unable to access bootloader, and volume+power keys do not do anything...I feel like I'm screwed (and already moved on) but using time these days to learn about android devices!
thanks!