Database Users

Odin flash crash, black screen

My galaxy s was hanging on boot (at the big S logo). This wasn't the first time and last time I had tried everything and reflashed. Yet this time odin crashed (windows gave me the 'Odin.exe stopped working' notification) and my phone powered off...
Now it won't give me anything, not download mode, OS or recovery (screen stays black, not even sure if the phone boots at all, hardware buttons also stay off)
Couldn't find anything usefull, any thoughts?
Cheers

Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing

mrjraider said:
Try the JIG to force it into download mode and try again. If odin crashes again, try flashin within windows safe mode. Sometimes it prevents crashing
Click to expand...
Click to collapse
Will that force the device to boot too? If thats true I will give it a shot this week, hopefully. See if i can get hold of one somewhere.
Thanks for the quick reply

tinyhitman said:
my phone powered off...
Click to expand...
Click to collapse
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode

xsenman said:
I Think this is the problem, you may have tried flashing when you had little battery charge and that will cause serious problems as bootloader would have failed.
your only option would be read the My Android Solutions about Problem:- Cannot enter Download or Recovery Mode
Click to expand...
Click to collapse
EDIT: I thought it was weird indeed that my phone powered off, since it had a full/near full battery (at least it told me)
Great thread ! Yet unfortunately none of the steps work for me up untill the JIG, I'll have to get hold onto one or make a homemade one (only got a single micro-usb at the moment, so that'll be a sacrifice) Havn't really got a lot of time on my hands but eventually i'll have to give the JIG a shot.
Realize that it seems like the phone isn't powered at all.
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Also: My volt-o-meter told me that my battery outputted 6+ volts... can't seem to reproduce at the time of writing this though....

tinyhitman said:
EDIT: no "usb device detected" notifications/sounds in windows when plugged in (for adb)
Click to expand...
Click to collapse
could be a USB cable failure (guessing) try
2) Problem:- Cannot connect to PC or Unknown Device, getting Code 43 or any other code or NO response when using USB cable in My Android Solutions

did you tried to remove the battery several seconds holding down the powerbutton and put it back again?
btw i also had issues with a galaxy note and a broken usb cable. screen was black because of an empty battery, you should try an other battery maybe a friends one

[SOLVED] A2017G Hard brick, Unauthroized ADB and DFU Only.

Hey guys,
Guess today it was my turn ****ing up.
I apparently have completely bricked my Axon 7 after trying to go from LOS 15.1 to stock oreo beta. The only thing I seem to be able to boot to is DFU mode and for some reason, if I press the Power button + Vol Down I will get stuck on the ZTE Logo and my PC will detect my phone through the ADB interface but every time I try doing something it says my device is unauthorized. Is there any way I can authorize the device whilst being completely bricked?
The only other thing I get is the unlocked bootloader warning screen. If I don't press anything the phone will be stuck there, if I select recovery the phone will simply shut down and anything else will result in a reboot. I have also tried a deep flash cable that that only results on the phone being stuck at the unlocked bootloader screen.
I cannot access the bootloader,
I cannot access EDL mode
I can access ADB, but device shows as unauthorized.
I can access DFU mode.
Any suggestions would be appreciated. I have looked at the Hard brick guide that involves taking the phone apart but that's not something I really want to do.
Thanks in advance.
Edit: My phone gets detected by MiFlash but every time I try flashing I get a cannot receive hello packet and object reference not set to an instance of an object.
ZTE axon 7 EDL tool detects it in ADB mode but says ERROR! NO ANSWER FROM PHONE!. Possibly since its not authorized with ADB.

Ouh....DFU? I think this thing is totally bricked.

I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?

Victor13f said:
I can access my phone in ADB. If only I could make it reboot to edl or something like that through ADB even though my device shows as unauthorized. That is the only problem why this thing is completely messed up.. ADB works but I can't do anything with it because my phone shows unauthorized. Does anyone know if there's a workround or a bypass for that?
Click to expand...
Click to collapse
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !

raystef66 said:
Hi Victor !
Like we discussed before there is nothing much left as to use the DFU unbrick-disassemble guide or buy something like this to be sure you tried everything.
Good Luck mate !
Click to expand...
Click to collapse
Thank you for your help . It's a risk you take when flashing phones.

Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.

stinka318 said:
Can you get custom recovery in it some recovery allow you to get in to EDM from there you can flash stock rom with Mi flash tool.......try to push both volume buttons at the same time don't touch the power button this might get you in to EDM.
Click to expand...
Click to collapse
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!

Victor13f said:
Hi. I cant get anywhere near recovery. When I press both buttons without the power button nothing happens. Thanks though!
Click to expand...
Click to collapse
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....

stinka318 said:
The screen will be blank untill you plug in USB cable to flash on mi flash tool then you refresh button on the computer screen....
Click to expand...
Click to collapse
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!

Victor13f said:
The moment I plug in any cable the screen turns on automatically. I've tried everything at the phone won't go into EDL. Thanks though!
Click to expand...
Click to collapse
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable

Choose an username... said:
Nothing, you'll have to use my guide for that (the one that raystef linked). Otherwise try entering FTM mode (Power and Vol-) but it's surely not gonna work. If it does, you'll see a screen with a square that says "FTM", and you'll be able to do " adb reboot edl" and flash stuff from there.
Unbricking by disassembing the phone is the most reliable method; an EDL cable just might save you the hassle but it's not guaranteed to work; some phones won't accept it for some reason. In this case just follow the guide unless you want to try your luck with an EDL cable
Click to expand...
Click to collapse
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!

Victor13f said:
Hello. Thank you for your advices, it is as I feared.
I have however already bought another Axon 7 which I'm using at the moment, and I have plans for mine since it was only bought new about 8 months ago and I believe I could get a replacement for a fee even if its bricked to fault of my own. So I will try that since I'm not in a rush.
This thread can be closed.
Cheers!
Click to expand...
Click to collapse
In that case you can just pretend that the phone got in that state by itself, it's not too morally correct but some people here pulled it off...

twice now i have gotten an axon 7 into this state. while mine have been a2017u models, i dont know that they are different than yours in that regard.
What worked for me the first time was letting the phone completely die. Being unable to boot into anything, it was somewhat a task to actually make it die, so i kept powering it on (which merely made the red led indicator come on). i did this over and over again over the course of a day at work whenever i noticed it had powered off.
eventually, the phone had no response at all. then, i plugged it up to my laptop, and left it, convinced i had killed it. a dialogue popped up after a minute or two on the phone screen saying to charge the phone by plugging it up. i had no access to fastboot or EDL mode prior. once i got that 'plug in to charge' screen, i switched it to the wall charger, and left it to charge a bit (50-60%) from that state, then, i unplugged it again, and somehow, i managed to get edl mode to work by unplugging it and pressing all three buttons and holding them (typical edl boot).
once there, i reflashed via MiFlash an earlier build. i rolled back using MiFlash as far back as i could. in the process, i lost my imei and serial, which i have yet to successfully recover, but i did get out of DFU pergatory. the imei thing seems to be caused by going back to MM which i did on both of my IMEI-less a2017u boards, but im only guessing. my dd axon 7 is the only one of the three boards with imei and serial, so maybe MM is a bad idea. lol.
The first time i recovered from DFU, i did it inadvertently by letting the phone die and then flashing in EDL mode as well. (i left it for a few weeks as i had given up on it.) after it died completely, and i plugged ut up to the computer and had the same experience, I flashed the beta oreo build for a2017 using miflash. the screen had stopped responding. and i ended up doing a RMA. I now know the screen response thing was bc of a faulty EDL file of B15. (happened again to another of my axon, so i retraced my steps and realized it was when i flashed b15 that it died) . the fix if your screen ever stops responding, but isnt physically damaged? re-flash via EDL a different file. it may take a few tries, but eventually a build will work. for me, it was Marshmallow. I still do not know for certain, but that possibly is what killed my IMEI. but hey, it boots and the screen works.
I genuinely hope posting my idiocy in toying with axon 7s has helped someone out there.

Zte maven 3 z835 Help

I know how QHSUSB_BULK is used because I had a brick but what happened with my cell phone is that when I flashed it I stopped recognizing it. uninstall everything to start again and when I connected my cellphone, QHSUSB_BULK did not appear anymore. I think I install a rom that is not.
When QHSUSB_BULK did not appear, my computer recognized as UNKNOW DEVICE. but when installing the drivers I only recognized the Qualcomm HSUSB QDLoader 9008. because the android is still in UNKNOWN DEVICE. USB \ UNKNOW USB \ VID_0000 & PID_0000.
There is no recovery, no FTM, no load, no turn on.
I can not switch to EDL mode
Start Sending Programmer
Download Fail: Unable to download Flash Programmer using Sahara Protocol
Download Fail: Sahara FailSahara Fail
Finish Download
I can not flash again,
Would the emmc be damaged or did it lose its format?
Excuse my english, I'm using google.

Sorry about that, what's your Compilation number?

nvizync said:
Sorry about that, what's your Compilation number?
Click to expand...
Click to collapse
V1.0.0B13 BBversion Z835H01

isaac ballesteros said:
V1.0.0B13 BBversion Z835H01
Click to expand...
Click to collapse
Ok, you need to charge your device, at least 70%, even if no logo, sign of life, or whatsoever is need to be showed, then remove the battery, wait at least 5 or 10 minutes, put the battery back and inmediatly connect the usb cable holding vol down, so that way, you gonna force your phone to boot into FTM mode, don't be scared, that happened to me also, trying to flash a V1.0.0B13 with V2.0.0B10, and with this way i successfully make my phone come back to life again.

nvizync said:
Ok, you need to charge your device, at least 70%, even if no logo, sign of life, or whatsoever is need to be showed, then remove the battery, wait at least 5 or 10 minutes, put the battery back and inmediatly connect the usb cable holding vol down, so that way, you gonna force your phone to boot into FTM mode, don't be scared, that happened to me also, trying to flash a V1.0.0B13 with V2.0.0B10, and with this way i successfully make my phone come back to life again.
Click to expand...
Click to collapse
No charge, no FMT but i will try it.

isaac ballesteros said:
No charge, no FMT but i will try it.
Click to expand...
Click to collapse
I know, it can be scary but try, even if it's all black

i have blank screen too how to fix?

xt1641 LATAM Hard Brick Alone

Hi Everyone!
I have an XT1641, which previously had a charging pin problem.
At the Last week, it started to reboot only many times until it suddenly shut down and didn't light anymore.
When plugged into a charger, the white light flickered.
Since I thought it was still a charging pin problem, make the change.
The cellphone works seemed to restart, but it continues with the same problem.
Sometimes the bootloader works ( Power + Vol -) and sometimes No.
I already tried everything. Install ROM STOCK, I made it blankflash (none worked "waiting for firehose to get ready" ).
It seems to be a firmware or similar problem, but I can't find the solution.
Previously, you never had a custom ROM installed, or root, or anything; at this cellphone
Thank you!
PD: SORRY FOR MY ENGLISH

How did you try for installing stock rom? Check usb drivers installed in your pc

przvlj said:
How did you try for installing stock rom? Check usb drivers installed in your pc
Click to expand...
Click to collapse
By Fast Boot (when it worked).
Now, after a week of turning it off, the cell phone turned on again without problems.

Phone Completely Dead Black Screen

I don't know what has happened... I took the phone off my charger at about 80%, was playing on it for a little bit and then restarted the phone.... the next moment I look at it, it is just a black screen. It is completely dead, pushing or holding power button does nothing (held for minutes multiple times), holding volume buttons & power button does nothing, plugging in to charger does nothing. It seems to be completely dead.
I have no idea why, it was working fine until I selected restart and was dead a few minutes later. Completely normal usage prior to that.
Anyone have any suggestions for what I can do to get this phone turned back on at all??
Nubia Z17 NX563J
Kind of a pain that these are completely sealed units...

I've just seen some posts about the Nubia Emergency Tool. If I plug my phone into the PC it does show up as "Qualcomm HS-USB QDLoader 9008" device so it looks like the emergency tool might work with it.
But does that mean it will flash my phone and I will lose all data on it?
There was nothing wrong with it just before, is there no other way to recover the data?

bunta126 said:
I've just seen some posts about the Nubia Emergency Tool. If I plug my phone into the PC it does show up as "Qualcomm HS-USB QDLoader 9008" device so it looks like the emergency tool might work with it.
But does that mean it will flash my phone and I will lose all data on it?
There was nothing wrong with it just before, is there no other way to recover the data?
Click to expand...
Click to collapse
How long have you used your phone? Better to replace the battery as one of my phones behaves the same way. Just replace the battery and that's it.

Tims Fong said:
How long have you used your phone? Better to replace the battery as one of my phones behaves the same way. Just replace the battery and that's it.
Click to expand...
Click to collapse
But the battery is not replaceable...?

bunta126 said:
But the battery is not replaceable...?
Click to expand...
Click to collapse
[NX563J][Project Treble][Android 10-11-12-13][GSI][AB]
Whats about magisk it Boot no more gsi after Flash magisk use this:https://github.com/ExpressLuke/phh-magisk-builder/releases/download/08-12-2020/magisk-v21.1-phh.zip
forum.xda-developers.com

bunta126 said:
But the battery is not replaceable...?
Click to expand...
Click to collapse
you need special usb cable i got same problem long time before
for edl mode

Update: I managed to get the bootloader and recovery working using the Nubia Emergency Tool. The system would not boot and even a dirty flash of the same ROM I was using would not make it boot. I could reinstall the ROM however and the phone is now working fine again.

So, I rebuilt my phone with a completely different ROM on Android 13, and today the same thing has happened: I chose to restart my phone and it has gone black and won't turn back on again.
It has been running perfectly fine on the new ROM until today, why would this same problem reoccur? I suppose battery is likeliest issue... although maybe there is something I'm doing to break the system?