I have an A2017U. Earlier I EDL flashed @jcadduono's B19. But now, when I use VolUp+Power, it goes to stock recovery and reboots. So I can't factory reset the phone. And I don't have TWRP either. I also can't boot into the stock ROM by just holding power, stock recovery appears for a second and then the phone turns off. When I hold VolUp+VolDown+Power I get a black screen and a solid red light, which is supposed to be EDL. But MiFlash doesn't detect the phone.
What the hell am I supposed to do to recover, when I'm locked out of all the modes I can use to get out of this mess?!
Thanks!
Always replace recovery with twrp when flashing. If you can get to test mode - vol down + power - you can adb reboot edl.
@lafester: Do you mean the FTM screen? Is that test mode? I've seen it before but I've always thought it was 100% useless. I've never heard of anyone flashing from that screen. What about DFU? When I press VolDown+Power the stock recovery screen just flashes for a second and the phone shuts off. Same thing when I press VolUp+Power. I simply don't see how flashing a stock EDL can brick the phone, MiFlash reported it was successful. No errors at all. But now, I can't get back into EDL. Just a solid red light and a black screen. MiFlash wont read it, neither will Axon7Tool. I think the issue is that my data and cache partitions are F2FS, stock recovery can't read them, so it just shuts down. I had this issue before, but eventually the ROM booted and told me to factory reset. So I did and all was dandy. No luck this time around.
Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!
AnonVendetta said:
Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!
Click to expand...
Click to collapse
I run Oreo bootstacks and EDL works fine.
If you cant enter recovery or EDL mode, you will have to try with a deep flash cable (very low chances of it working) or follow this guide https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
So did you try it? Yes, ftm screen is test mode. You also need to tell us what device manager is saying when you are in edl mode.
lafester said:
So did you try it? Yes, ftm screen is test mode. You also need to tell us what device manager is saying when you are in edl mode.
Click to expand...
Click to collapse
he has a black screen with a red light, that's DFU
EDL only blinks a red light once
thats a 4th category brick
AnonVendetta said:
Another thing I've noticed, is that when I reboot to EDL, I get a black screen and a solid red light. I was previously running AEX Oreo, I have heard that the Oreo bootstacks can screw with EDL. Before Oreo I got a black screen and a red light that blinked once and turned off, then I was able to EDL flash. I have read that if I let the phone fully discharge (by allowing the red light to drain the battery completely), then maybe I can try something else in a few hours once that is done. But what? really need some help here.
Thanks!
Click to expand...
Click to collapse
Have fun using my guide! ?
He has a u version. Most likely not bricked.
lafester said:
He has a u version. Most likely not bricked.
Click to expand...
Click to collapse
crap, i overlooked that. Maybe @kitcostantino knows more? Honestly I never understood what was his problem or what he did to fix it, but it was on an U and it looked exactly like DFU...
Only time I ever had a dfu issue was with the very first Chinese beta. I was able to get into test mode and then boot into edl.
So, no access to FTM, otherwise my issue would be solved and I wouldn't be posting. I let the battery drain all day by letting the red light burn through it, I had figured that letting the battery drain would be the equivalent of short circuiting the pin that @Choose an username... speaks of. No power in the circuits=reset. I got it to where the red light either does blink, or stays on for a moment and turns off. But EDL and other tools doesnt recognize the phone either way. I read some of the 4th category brick guide, it says you need to disassemble the phone. But I am no good with hardware, if I take it apart then it will very likely not go back together in one piece. So I would like to avoid that. I also don't have the money to pay a technician, I prefer to fix my own problems. I bought my A7 new from NewEgg, it came with SquareTrade insurance. Maybe I should call ZTE and try to get a warranty repair? I can just tell them I was repairing via EDL from a bootloop, when it all went bad. Don't need (and probably shouldn't) mention TWRP, etc.
I have 3 QUSB__BULK entries under "Universal Serial Bus Devices" in Device Management. Normally, it would show up in "Ports" category, if EDL was working properly.
Just dropped a private message to @kitcostantino to see if here can post in the thread.....
Volume + and - plug USB cable at the same time may work......
@stinka318: Already tried that before you posted. Same as before.
If you still have your warranty, then I'd send it back to ZTE if you can't get it to come back to life.
@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....
AnonVendetta said:
So, no access to FTM, otherwise my issue would be solved and I wouldn't be posting. I let the battery drain all day by letting the red light burn through it, I had figured that letting the battery drain would be the equivalent of short circuiting the pin that @Choose an username... speaks of. No power in the circuits=reset. I got it to where the red light either does blink, or stays on for a moment and turns off. But EDL and other tools doesnt recognize the phone either way. I read some of the 4th category brick guide, it says you need to disassemble the phone. But I am no good with hardware, if I take it apart then it will very likely not go back together in one piece. So I would like to avoid that. I also don't have the money to pay a technician, I prefer to fix my own problems. I bought my A7 new from NewEgg, it came with SquareTrade insurance. Maybe I should call ZTE and try to get a warranty repair? I can just tell them I was repairing via EDL from a bootloop, when it all went bad. Don't need (and probably shouldn't) mention TWRP, etc.
I have 3 QUSB__BULK entries under "Universal Serial Bus Devices" in Device Management. Normally, it would show up in "Ports" category, if EDL was working properly.
Click to expand...
Click to collapse
You have another problem there. Right click on the QUSB_BULK and Uninstall device. If you were on DFU it would show up as ZTE Handset Diagnostic Interface.
If you ever used Zadig then that's your problem. If not, it's worth trying anyways
Choose an username... said:
crap, i overlooked that. Maybe @kitcostantino knows more? Honestly I never understood what was his problem or what he did to fix it, but it was on an U and it looked exactly like DFU...
Click to expand...
Click to collapse
just to clarify, what i have had success with,is letting the phone completely die, then charging with my laptop (which is lower power than a QC or standard plug) until i get the 'connect charger' message. at that point i charge using my Quick Charge oem brick and cable. after that, for whatever reason, EDL works for me again. Prior to that, point, DFU mode was all i could get. no recovery, no fastboot, no EDL. Just solid red light after holding the EDL mode key combo (vol +, vol -, power). but no Qualcomm 9008 whatever it is, ive done this a couple of times. its always trying to go stock, but something had failed.
while it makes no sense to me, id say its worth a shot. boot into what you have at that point, which is only DFU mode, and simply let the phone die. if it powers off, power back on, and let it die completely. then plug up to a computer usb port, let it charge until you get that message, and after you charge above 30-40% min, EDL to something else. i must also say somewhere in my mis-adventures, i killed the imei on not one but two a2017u boards, so something does not like going back to MM. at that point, i had a bad download of b15 that was breaking touch functionality, so i flashed back to MM. The board flashed fine, but serial and imei went bye bye.
[posted for the greater good...this was a pm. ]
AnonVendetta said:
@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....
Click to expand...
Click to collapse
Dude, it may seem daunting, but this is one of the easiest phones to disassemble i have owned. grab some guitar pics, a magnet (for screws), and something like the top to the axon 7 box, and a relatively high quality phillips precision screw driver. the trickiest parts are the speaker grills, the fingerprint cable, and separating the back. the screws beneath the tape/speaker screen material i just didnt put back in my axon phone that has been taken apart. if ya have warranty, ya may as well send it in. i presently have not one but two boards that are without an IMEI. i keep my second axon in an easy to disassemble state as i didnt put the screws that are under the adhesive and speaker grills. i can board swap it in about two minutes now as ive done it like 20 times. it really isnt bad man. watch jerryrigeverything's video and its a piece of cake.
however, if you want to use warranty and not have to pay ($79) to ZTE to use Passport warranty, dont take it apart. if ya take it apart and fail, worst case scenario, ZTE will charge ya $80.
Square Warranty i know nothing about.
critical step on drain/trickle charge/edl is to just let it charge by itself on the oem usb cable to the computer until you get the 'plug in....' screen. just going over it in my mind trying to be certain i mentioned everything i did. in both instances, i was on stock.
AnonVendetta said:
@try5890: I still have the standard warranty, as well as SquareTrade insurance. But if there is a way out of this that doesnt involve hardware disassembly (which might make things worse), then I'd rather go that route instead. It's Sunday anyway, so I'll have to wait til tomorrow to call either ZTE or SquareTrade. If there is a chance of resolving it before then.....
Click to expand...
Click to collapse
No need to open your device, just follow this guide.
Related
My Nexus one won't turn on. I tried flashing RADIO 32.24.00.22U_4.03.00.21_2 that I downloaded from Modaco.
After it failed to install showing the error message like
"Multiple Radio images"
and a few others I try to reboot it.
when trying to reboot it there showed a picture of a android and a orangish arrow and a box.
Help...I think I bricked it.
Help?
Please?
Can you get into boot loader? Hold down the track ball, then power on, and keep holding down the track ball...
Also, try holding down the "volume down" toggle button while powering on if the track ball method doesn't work...
If both don't do anything but take you to that same screen, let it sit on that screen for a bit, say 10 minutes just in case...
If still nothing, see what happens when you plug your phone into your computer with the data cable, is it recognized? If so, can you get ADB to recognize it?
Jackasaur said:
Help?
Please?
Click to expand...
Click to collapse
can u get to the recovery image? if u can, its not bricked.
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Jackasaur said:
well I tried plugging it into the computer, I tried the wall charger, and nothing seems to work. The LED doesn't come on, and the button combination doesn't work. So I think it's dead for good. :C Before everything got screwed All I saw was a box and an arrow pointing at a android. Which I think meant it was unboxing. I then thought it froze so I tried to take the battery out, and after that it didn't turn on anymore. No LED, no recovery, no nothing. :C Quite sad.
Click to expand...
Click to collapse
This part takes a few minutes. I am not totally sure what is happening at this point but I'm assuming it's not good to remove battery during this. Mine sat on that screen for a few min and then finished.
Try to boot up with volume down button held. Then use volume arrows to choose recovery and hit power.
uansari1 said:
Why the f are so many people intent on taking their batteries out while the phone is updating? I'm not saying that led to the bricking...but it probably didn't help.
Click to expand...
Click to collapse
Everyone expects everything to be instant these days... "Uh oh! The screen isn't doing anything, it's been at least 20 seconds! I could just wait and leave it for a few minutes like all the guides say to do. Or I could take my battery out...how could that hurt, right?"
For me it took a good 3-4 minutes on the screen with the arrow and the box.
Anyways, if you can't get to the recovery then you might be buying a new N1.
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Bleh. I'll just have to wait and see. I'll contact HTC.
tomsan84 said:
ahh it took like 5 minutes for me, I have to admit I was a little worried since you dont see status bars or anything, but like said, the guides warn for this.
I cant imagine that removing the battery broke it though, he should be able to load a recovery image
I feel sad for him so bumping
Click to expand...
Click to collapse
If you remove the battery during the period he did, which is when the phone is actually flashing the radio ROM, yes removing the battery can and likely did break it for him. There are 2 ways to brick an Android device, while flashing a radio ROM and while flashing an SPL...
OP, have you tried any of the button combos we have recommended? Have you tried putting your battery in the phone, then without turning it on, putting it on the charger to see if it can charge the battery at least (you said it wasn't even turning on, which is likely because you have a dead battery)... charge the battery first, then try the button combo's we recommended.
And please, when you report back, and not to sound like an ass, do so clearly and systematically (I can't tell from your posts what did or didn't happen, and whether you tried anything we suggested, nor what the current state of the phone is)... so, please use this format to make it clear to us trying to help:
Battery: Charged or Wouldn't Charge (LED will come on if it is charging)
Trackball+Power: Booted into boot loader, yay! or Went to the damn box
Volume down+Power: Booted into fast boot! or Went to the damn box
And remember, you have to hold down the button, either trackball or volume down, then press the power and keep holding down the trackball or volume down until it either goes to boot loader or it goes to the box screen... you might want to even wait for a minute on the box screen(if it goes to that) while holding down the button to make sure it can't get into boot loader...
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Jackasaur said:
Okay so I took the battery out, put it back in, and tried charging it. The Battery LED did not come on, so I'm guessing it's not charging.
The Trackball+Power did not work.
The Volume down+Power did not work.
I think I most likely broke it, due to the fact that I took the battery out while it was flashing the radio ROM onto the phone. I kinda did it on a impulse, which is my fault. So do you think it'd be possible if I did contact HTC they'd send me a swap, and not be able to make my phone work or turn on, and everything will go on as if I "broke" it and not unlock it or anything?
Click to expand...
Click to collapse
It sounds like you have a true brick... disruption of the radio ROM flashing causes lots of bricks, and did so for you.
It is pretty common, at least with T-Mobile with the G1, to call them up and tell them your phone asked you to update, and while updating it froze and won't turn on or charge anymore. Not sure if HTC will handle it the same as T-Mobile did, but if they do they will just send you a new unit, you send the old one back, and you are back up and running... they might ask that you send it to them first, but there is no way for them to test if it was rooted/unlock boot loader if it can't be powered on, so you should be fine.
Sweet. So I called HTC, and they said they'll repair it, but I asked for a swap instead, so I'll be getting one by either Wednesday, or Thursday. Good stuff! I'll tell you all how it goes. :] Now I am stuck with my Nokia N95. Thanks for all your help.
Did you tell them you have an unlocked bootloader?
uansari1 said:
Did you tell them you have an unlocked bootloader?
Click to expand...
Click to collapse
he doesnt have 2 tell em
lightforce said:
he doesnt have 2 tell em
Click to expand...
Click to collapse
Yeah, he doesn't have to tell them... but they don't have to cover his phone either.
If they find out it's unlocked after the fact, they can charge you to repair the phone.
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something? Does HTC have alternatives ways of checking?
Eclair~ said:
How exactly will they know he unlocked the bootloader if the device cannot even properly turn on, unless htc has other methods of being able to "restore" the phone, then he should be rather ok. Am I not looking into this deeply enough? Can the phone turn on with a new battery or something?
Click to expand...
Click to collapse
That's my point man.. I don't know. All they have to see is that open padlock and they can deny the claim.
So last night I hard bricked my nexus 4. its rooted, with cyanogenmod 10.1 ROM, and ive never had any issues with this phone. I have no idea what happened, but I sent a text message to someone, and it powered itself down. it was fully charged when this happened, so I know its not the battery. ive done some research, and its a true hard brick. no bootloader, no recovery, I just get a red/orange flashing light if I hold down the power button. google said im still under warranty, and they will still replace it even with it being rooted. My question is, is it possible to fix without having to get a replacement, or JTAG? If anyone has had any success, please help.
And like I said, I was only sending a text. I have no idea why it bricked, it restarts itself once in a while randomly, but this time it didn't turn back on.
Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?
exb0 said:
Try plugging it into the wall for about 5 minutes then try turning it on again. If it doesn't work, RMA it. Why would you risk your warranty and JTAG it?
Click to expand...
Click to collapse
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.
sinndissension said:
No, I DONT want to JTAG it. im looking for alternatives. if its possible to fix a hard brick without JTAG or using my warranty. If at all possible, I want to fix it, because I have a lot of pictures and everything on there that I would like to get out of it. I don't want to lose them. JTAG is my last resort if I cant get it replaced, but they said they would. I want my stuff off it though.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.
exb0 said:
http://forum.xda-developers.com/showthread.php?t=2347060
This is your last hope. If it doesn't work, RMA it and request for your data to be saved. Not sure if they can do it, but just ask.
Click to expand...
Click to collapse
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
Nope. It's different.
sinndissension said:
thank you I really appreciate it. im gonna try it out and see if it works.
This might be a noob question, but ive never heard of download mode. is it the same as recovery mode on the nexus 4?
Click to expand...
Click to collapse
You can compare it too fastboot mode.
gee2012 said:
You can compare it too fastboot mode.
Click to expand...
Click to collapse
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
Did you press volume down first and then the power button both for a few seconds to get into fastboot mode?
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, or the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone knows of that I didn't just list, my last option is JTAG.
sinndissension said:
yep. ive done EVERY combination of holding down the buttons, no response. when I plug it in to a laptop, the laptop beeps, like the USB connection sound, but the nexus doesn't show up on the computer. I know the computer recognized what kind of phone it was, cuz the first time I plugged it in, I got a pop up message saying "installing qualcom drivers", or along the lines of that. other than that, NOTHING has worked. If theres ANY fix for this, id like to give it a try, cuz ALL my stuff is on there.
Click to expand...
Click to collapse
Try charging it for a while and try again in a few hours or better yet tomorrow. Sometimes that helps bro. If that doesn`t help you`ll have to take it in for repair an maybe they can salvage your data if they are wiiling to do that. Good luck.
I think it's just your battery(RLOD) instead of a brick.
See this:
http://forum.xda-developers.com/showthread.php?t=2250454
I wouldn't be worried about your files stored on your phone because I think Google has more work to do than search in peoples pictures. What I would worry about is your warranty since you have a custom rom, unlocked bootloader and root...
Sent from my Nexus 4 using xda app-developers app
Well, found out it WAS a hard brick. Google replaced it with my warranty. For some reason they returned my money before I even got the chance to send the broken nexus 4 back. Didn't even mail it. So I'm assuming I don't have to send it back. So I'm gonna JTAG the hard bricked nexus, and hopefully it'll work again.
Thanks everyone for your help.
sinndissension said:
ok so if the nexus 4 wont go into download mode, or fastboot, or anything else, I have no choice but to RMA it right? cuz the ONLY response im getting from it is a red/orange flashing light when I hold down the power button. other than that, nothing happens.
Click to expand...
Click to collapse
You may not be doing it right. When I get the flashing light on mine it means I forgot to let go of the power button fast enough. When it vibrates, let go of power button immediately but keep pressing the volume. Does your phone vibrate a few seconds prior to the flashing light?
Sent from my GT-P7510 using xda app-developers app
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.
sinndissension said:
Nope. The ONLY time it has any sign of life is if the charger is connected to it and I hold down the power button. If it's NOT connected to the charger, pressing the power button does absolutely nothing. I can't go into recovery mode, download mode, on the bootloader. I've tried charging it overnight, (and part of the next day) left it off the charger for over a week, it shows up as "Qualcomm-something" when I plug it into a computer, but I can't do ANYTHING with it connected to a computer either, and after I got my replacement, I tried taking out the battery and putting it back in. There was still no change......I've literally done EVERYTHING short of JTAG. Trust me, I searched all over google, and XDA, and tried everything. As far as I know, hard bricking is rare, but it happens. And it just happened, to happen to me. So unless there's a solution someone know of that I didn't just list, my last option is JTAG.
Click to expand...
Click to collapse
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?
Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted
Mashed_Potatoes said:
Weird. I've had the "red light of death" 2 hours ago because i didn't put the phone on the charger and it had like 4%. Pressing Volume down + power got it to enter fastboot and i was able to start the phone normally so it's charging booted
Click to expand...
Click to collapse
ok...that has nothing to do with a hard brick. That just means your phone was dying.
dominiqueovalle said:
so i have the same problem. was about to tweet with full battery so my question is what did you end up doing? Did you fix it or abandon it?
Click to expand...
Click to collapse
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?
sinndissension said:
Ok, I got mine replaced because it was still under warranty, and normally, the manufacturer cant tell its rooted or unlocked if its a true hard brick, (rooting and unlocking voids your warranty.) So i got mine replaced.
If your NOT under warranty still, your ONLY option if you want to fix it is JTAG. Google it, it costs about 50 bucks on average, but its cheaper than a Nexus 4. Research JTAG before you try it though. Or you have to buy a new one. I still have my only one, and i basically use it for parts for my newer N4.
Is it a true HARD brick, or just a soft brick?
Click to expand...
Click to collapse
its a hard brick. ive tried it all bought a new battery installed it etc. ive looked up jtag and i have the money but idk if i should do it. do you recomend it? i have no experience doing anything like it and im planning on getting the iphone 6 in the fall but i cant stand not having a phone till then especially since high school starts soon.
But the reason im sure its a hard brick is cuz when it shut down the battery was like 50 and charging and it froze for 25 seconds or so then shut down and refuses to boot or show any signs of life now except a blinking or solid red light but its not the red light of death because i replaced the battery therefore i came to the conclusion that it is hard bricked.
i know ive said alot of unecessary information but my question is do you think i should buy the jtag thing? do you reckon its easy to do? or maybe i could pay an experienced professional to do it?
thanks for the reply btw
So first some back-story, I'll get right into it. I recently dropped my phone in some water. As soon as possible I dried off the outside, and let it sit. That was the only thing I could do at the time, I had no rice, no tools to open up the phone, anything. I ended up with a solid red light, and everything unresponsive.
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new. However, this isn't the point of the thread.
It appeared my cleaning helped quite a bit. Upon re-assembling and plugging in, I immediately got a charging sign on the phone. However, after trying to power on, I got no response. Additionally, The charging signal went out after about 20 seconds, and the whole phone became unresponsive again. I can do this process as many times as I want, but the same thing happens every time.
So I tried a different approach. First I hold down both volume rockers plus the power button, and plug it in while holding them down. This puts the phone into "download mode" However, once in download mode the phone is, again, unresponsive. After plugging into my laptop, my computer recognizes the phone, but not as "Nexus 4," but as "Full JellyBean on Mako."
Is there anything I can do about this? I've heard about drivers being able to be installed when in download mode, but I would not know what these are, where to get them, or how to install them. I really don't mind if my phone never works 100% again, I doubt it would. I just want to be able to get into the storage so I can recover some of the files I lost.
It's also probably worth mentioning I have not gotten a solid red light after the clean. Once in a while I will get a blinking red light after plugging it in, but after less than a minute it stops and goes through the charging/stop charging phase I'm so familiar with. Any help at all would be appreciated, and thanks in advance.
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
DrFredPhD said:
The charging block and/or battery could be wrecked, for safety reasons and because it will probably become faulty soon you should change the battery anyway. If the charging block is broken flashing your phone could fail. It's also possible the board was irreparably damaged, but it's probably worth a try as the parts aren't too expensive.
Click to expand...
Click to collapse
After trying to figure more things out, I kept it plugged in for a while. It appears my battery actually holds at least a pretty good charge, as the indicator is full when I plug it in now. However, I don't know what you mean when you say charging block.
Also, I seemed to determine my power button isn't working either. I always thought no response to pushing it meant there was something else going on, but I am able to put it into "download mode" by just holding down the volume rockers and plugging it in. Is there a way to turn on the phone another way besides the power button? Also if not, will buying another power button fix the problem? I don't want to buy one then later figure out the reason it wasn't turning on was just a board problem, and not a problem with the button itself.
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
26694484 100
DrFredPhD said:
You can short the power button with a screwdriver or something should turn the phone on., By charging block I mean the secondary board that the micro usb port is a part of, it can be replaced fairly easily if necessary.
Click to expand...
Click to collapse
With a screwdriver? Enlighten me, I'd have no idea how to do that. If I had a faulty charging block, then my phone wouldn't be able to charge correct? My phone was plugged in for a while in download mode, and it gained a full charge from a relatively low charge. I also took the block apart and cleaned any corrosion, so I think that's still functional.
Some more progress, upon further attempting to turn the phone on, I was able to get it into fastboot mode. When plugging into the computer it is recognized, but as just "Android." I will type out what information is displayed here, minus serial number, as a new member cannot submit links in posts apparently.
FASTBOOT MODE
PRODUCT_NAME - mako
VARIENT - mako 8GB
HW VERSION - rev_11
BOOTLOADER VERSION - MAK0230d
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1700.98
CARRIER INFO - None
SERIAL NUMBER -
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - locked
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Another update, just in case anyone is still listening..
Str1ngcheese said:
Also, fastboot at the top (as far as I know) usually says "Start" or "Recovery Mode," but mine says "Restart bootloader." When I try switching with my volume buttons, nothing happens.
Click to expand...
Click to collapse
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Str1ngcheese said:
Another update, just in case anyone is still listening..
This no longer applies, for some reason I am able to switch through all modes, incliding "Start, Power Off, Recovery Mode, and Restart bootloader."
Click to expand...
Click to collapse
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Monotoko said:
Now that you're at this point, have you attempted to flash the phone with a stock image? I'd be weary of what the other poster said though and ensure your USB connection is holding steady because you don't want it dying half way through a flash because then you'll have a brick.
Click to expand...
Click to collapse
I have tried actually. I used the Nexus Root Toolkit v1.8.0 to try and flash it. At first it wouldn't find the device, but through device manager I manually installed the usb_driver onto the phone. After this, the toolkit was able to find the phone. I attempted to flash the image, but it ended up staying in fastboot mode. The program then suggested I try to enable "force flash," which I did, and this time it was never able to finish because the phone tried to restart, but went through that "charging to unresponsive" state I described in my first post.
Upon trying to flash it normally again, it looks like maybe the phone has to be unlocked to do this properly? I then tried to unlock with the same program, but in order to do that, I need the power button to confirm I actually want to unlock the phone. So yet again, I need that power button working.
Any ideas/suggestions/solutions would be amazing.
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
opssemnik said:
Jellybean on mako means that your phone is in lgnpst/qcpnst mode. Looks like something failed to start and made the bootloader trogger that mode
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Soo, any suggestions?
Str1ngcheese said:
Soo, any suggestions?
Click to expand...
Click to collapse
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
opssemnik said:
clean all the contacts with alcohol (not the normal one, the other that i dont remember the name).clean all the corrusion that you can find,let your phone charge for some hours and try again
Click to expand...
Click to collapse
I've already done that.
Str1ngcheese said:
The next day I got some tools to open her up. There was pretty extensive corrosion to the motherboard, so using some alcohol I cleaned it all off, rinsed it, and let it dry. I also took apart everything else and cleaned any corrosion. The inside looks brand new.
Click to expand...
Click to collapse
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Str1ngcheese said:
I've already done that.
Problem is the power button doesn't work, and the flashing fails. It looks like the flashing fails because the phone isn't unlocked. To unlock, I need the power button. Kinda stuck.
Click to expand...
Click to collapse
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
opssemnik said:
the golden contacts on the power button / mobo could be damaged, do a little short till phone turns on
Click to expand...
Click to collapse
How would I go about doing a short?
Str1ngcheese said:
How would I go about doing a short?
Click to expand...
Click to collapse
touch in both pins, something that passes electric current(like a yarn,wires, copper wire, something that passes electrical current).its basicly what the power button does.
In my persistent attempts to put a custom rom on this device, the following sequence occurred:
- Phone suddenly not recognized by PC in any mode: normal, recovery, or fastboot. It would not even charge from the USB port, no reaction at all from the phone or PC that the connection is made. Other devices using the same port and cable work correctly.
- Phone unresponsive to a wall charger while it is powered on. Similar to the above description, the phone does not recognize that it is pulled into a charger at all while it is powered on. However, at this point the
- Phone is responsive to a wall charger after turning it off. The screen shows the charging icon on screen and the LED is red, meaning the phone recognizes the micro-USB connection when it is powered off, but only via the wall charger, still sees nothing when connected to the PC.
With the above criteria I decide to let the device completely discharge its battery, hoping that a full empty to full charge will reset whatever is happening. It takes about 3 days to go completely dead ... moving from screen need-charging image, to only the red LED, to absolutely no response when pressing the power button.
Now I have a phone that is completely unresponsive to any button press, as expected since the battery is completely drained. Unfortunately, it no longer responds to the wall outlet at all. Meaning it won't charge in any way. Used multiple chargers, multiple wall sockets, multiple cables, gave it compliments, etc.
At this point the phone is totally and completely dead and unresponsive to any charging. Any thoughts or help?
apsommer said:
In my persistent attempts to put a custom rom on this device, the following sequence occurred:
- Phone suddenly not recognized by PC in any mode: normal, recovery, or fastboot. It would not even charge from the USB port, no reaction at all from the phone or PC that the connection is made. Other devices using the same port and cable work correctly.
- Phone unresponsive to a wall charger while it is powered on. Similar to the above description, the phone does not recognize that it is pulled into a charger at all while it is powered on. However, at this point the
- Phone is responsive to a wall charger after turning it off. The screen shows the charging icon on screen and the LED is red, meaning the phone recognizes the micro-USB connection when it is powered off, but only via the wall charger, still sees nothing when connected to the PC.
With the above criteria I decide to let the device completely discharge its battery, hoping that a full empty to full charge will reset whatever is happening. It takes about 3 days to go completely dead ... moving from screen need-charging image, to only the red LED, to absolutely no response when pressing the power button.
Now I have a phone that is completely unresponsive to any button press, as expected since the battery is completely drained. Unfortunately, it no longer responds to the wall outlet at all. Meaning it won't charge in any way. Used multiple chargers, multiple wall sockets, multiple cables, gave it compliments, etc.
At this point the phone is totally and completely dead and unresponsive to any charging. Any thoughts or help?
Click to expand...
Click to collapse
I had this issue when trying to flash GreenKernel. Turned out I messed up on a step and flashed it the wrong way. Check my posts in that topic.
Wenro said:
I had this issue when trying to flash GreenKernel. Turned out I messed up on a step and flashed it the wrong way. Check my posts in that topic.
Click to expand...
Click to collapse
Thank you for the response, I was about to throw the phone away. Can you be a little more specific? I see your post here regarding a rebooting loop with red light flashing. However, I don't have any response from the phone whatsoever ... nothing on the screen, or led in top right. It does not accept a charge from 1A or 2A source, it is literally a paper weight right now. I need to "jump start it" or something of this nature. It won't charge at all.
apsommer said:
Thank you for the response, I was about to throw the phone away. Can you be a little more specific? I see your post here regarding a rebooting loop with red light flashing. However, I don't have any response from the phone whatsoever ... nothing on the screen, or led in top right. It does not accept a charge from 1A or 2A source, it is literally a paper weight right now. I need to "jump start it" or something of this nature. It won't charge at all.
Click to expand...
Click to collapse
Probably the phone looks dead but does get charge - it's just not showing it with the LED.
I believe Snapdragons are close to impossible to hard-brick - the chip itself has a ROM with EDL burned into it and that can always be used to bring it back from zombieland, if you have the right tools. But if you are lucky enough, then service mode would still be available even without hunting for the EDL stuff.
First, power the phone off for real with the hidden button near the SIM tray - and leave it off.
Then, install Flashtool and use it to flash a stock ROM, as described for instance here. When flashing, choose flashmode instead of fastboot and follow the instructions.
HTH,
Antonio
antonio.galea said:
Probably the phone looks dead but does get charge - it's just not showing it with the LED.
I believe Snapdragons are close to impossible to hard-brick - the chip itself has a ROM with EDL burned into it and that can always be used to bring it back from zombieland, if you have the right tools. But if you are lucky enough, then service mode would still be available even without hunting for the EDL stuff.
First, power the phone off for real with the hidden button near the SIM tray - and leave it off.
Then, install Flashtool and use it to flash a stock ROM, as described for instance here. When flashing, choose flashmode instead of fastboot and follow the instructions.
HTH,
Antonio
Click to expand...
Click to collapse
Thank you for the response. I pressed the hidden button in the SIM tray for 10 seconds, 3 times in a row. Downloaded the latest "Emma" Sony Flashtool ... and nothing happens. The software does not recognize any Sony device plugged into the computer. Checked the USB cable, it's good. The computer, and the Sony flash software, do not recognize the device at all. It will not turn on in any way, and it does not appear (based on the screen and LED) to accept a charge at all. It truly seems bricked at this point. Any thoughts?
apsommer said:
Thank you for the response. I pressed the hidden button in the SIM tray for 10 seconds, 3 times in a row. Downloaded the latest "Emma" Sony Flashtool ... and nothing happens. The software does not recognize any Sony device plugged into the computer. Checked the USB cable, it's good. The computer, and the Sony flash software, do not recognize the device at all. It will not turn on in any way, and it does not appear (based on the screen and LED) to accept a charge at all. It truly seems bricked at this point. Any thoughts?
Click to expand...
Click to collapse
I don't know what method is used by Sony Emma, sorry. But simply connecting the phone won't surely be enough if there is no software on it that answers to USB requests from your PC.
How about trying with the tool I suggested you? Let the phone off, download a stock firmware and start the flashing in flashmode instead of the standard fastboot mode (just follow the on screen instructions).
If that does not work, the only thing that's left is EDL mode. I've found no documentation for Z5 Compact, unluckily - but any decent repair shop should be able to resurrect it.
Antonio
antonio.galea said:
I don't know what method is used by Sony Emma, sorry. But simply connecting the phone won't surely be enough if there is no software on it that answers to USB requests from your PC.
How about trying with the tool I suggested you? Let the phone off, download a stock firmware and start the flashing in flashmode instead of the standard fastboot mode (just follow the on screen instructions).
If that does not work, the only thing that's left is EDL mode. I've found no documentation for Z5 Compact, unluckily - but any decent repair shop should be able to resurrect it.
Antonio
Click to expand...
Click to collapse
I downloaded the flashtool you linked, and also the XperiFerm and latest Z5C drivers as mentioned in the tutorial. The drivers do not have an exe. I can not manually install the drivers because the device is not recognized by the PC at all, it does not show in the Device Manager. Moving forward ... downloaded and installed the Sony Xperia Companion software, it also does not recognize the device at all. The flashtool you linked also does not see the device at all.
23/016/2019 00:16:53 - INFO - Device disconnected
There is no flashmode or fastboot mode possible, the device does not respond to any buttons, any charge, or mean glances. Any last thoughts before I cut my losses and throw it away for a XZ1 compact?
apsommer said:
There is no flashmode or fastboot mode possible, the device does not respond to any buttons, any charge, or mean glances. Any last thoughts before I cut my losses and throw it away for a XZ1 compact?
Click to expand...
Click to collapse
Don't throw the phone away!
I fear I was not explicit enough:
1. keep the phone off and disconnected
2. click on the Flash icon, choose the firmware
3. choose flashmode
4. press volume down and only then connect it to the PC
If even this alternative service mode has been wiped, then the only possibility left is EDL. For that, I'd go to a repair shop.
Antonio
apsommer said:
I downloaded the flashtool you linked, and also the XperiFerm and latest Z5C drivers as mentioned in the tutorial. The drivers do not have an exe. I can not manually install the drivers because the device is not recognized by the PC at all, it does not show in the Device Manager. Moving forward ... downloaded and installed the Sony Xperia Companion software, it also does not recognize the device at all. The flashtool you linked also does not see the device at all.
23/016/2019 00:16:53 - INFO - Device disconnected
There is no flashmode or fastboot mode possible, the device does not respond to any buttons, any charge, or mean glances. Any last thoughts before I cut my losses and throw it away for a XZ1 compact?
Click to expand...
Click to collapse
Hi,
Power off the phone : press volume up and power button. Wait 3 vibrations (if not, the phone is powered off).
Press first the volume up and plug the phone with the usb cable into your computer. If you see the blue light you can use Flashtool, if not... it's dead (for me)...
How to use Flashtool is another thing, blue led is essential.
You'd rather throw it away for a Xz2 compact and install Omnirom. You can find some used ones for good prices.
antonio.galea said:
Don't throw the phone away!
I fear I was not explicit enough:
1. keep the phone off and disconnected
2. click on the Flash icon, choose the firmware
3. choose flashmode
4. press volume down and only then connect it to the PC
If even this alternative service mode has been wiped, then the only possibility left is EDL. For that, I'd go to a repair shop.
Antonio
Click to expand...
Click to collapse
Thanks, Antonio. Step #4 causes no reaction in the phone, or the Flashtool. The software does not recognize the device and the phone remains unresponsive. It truly seems hard bricked to me. I live in Mexico ... this device is rare even in the US, the guys will have never seen it, and their approach to EDL is as good as mine. I'm pretty frustrated with this dead phone, I think it's time for a new one and to mark this as a lesson learned.
Raphos said:
Hi,
Power off the phone : press volume up and power button. Wait 3 vibrations (if not, the phone is powered off).
Press first the volume up and plug the phone with the usb cable into your computer. If you see the blue light you can use Flashtool, if not... it's dead (for me)...
How to use Flashtool is another thing, blue led is essential.
You'd rather throw it away for a Xz2 compact and install Omnirom. You can find some used ones for good prices.
Click to expand...
Click to collapse
Thank you. No blue light under any button combination, charging cable, outlet, software, mean glances, etc. My next one is XZ1 or XZ2 ... I'll take your advice into consideration, the XZ2 has better specs but of course its +$100. I like to think of myself as a capable engineer, but destroying this Z5C has made me pretty hesitant to attempt the same process on a new phone. Everyone seems to agree that hard bricking this device is near impossible, however I beg to differ as look at this dead one on my desk.
apsommer said:
Thanks, Antonio. Step #4 causes no reaction in the phone, or the Flashtool. The software does not recognize the device and the phone remains unresponsive. It truly seems hard bricked to me. I live in Mexico ... this device is rare even in the US, the guys will have never seen it, and their approach to EDL is as good as mine. I'm pretty frustrated with this dead phone, I think it's time for a new one and to mark this as a lesson learned.
Click to expand...
Click to collapse
Ouch - a real pity.
It really seems you succeded in wiping out all possible accesses for the Sony bootloader. Do you mind me asking how you managed that? I'd like to avoid doing the same mistake.
Qualcomm EDL mode is surely there, but you will need to open the phone and the software for that approach is not freely available (or at least I was not able to find it).
Antonio
antonio.galea said:
Ouch - a real pity.
It really seems you succeded in wiping out all possible accesses for the Sony bootloader. Do you mind me asking how you managed that? I'd like to avoid doing the same mistake.
Qualcomm EDL mode is surely there, but you will need to open the phone and the software for that approach is not freely available (or at least I was not able to find it).
Antonio
Click to expand...
Click to collapse
I don't remember the exact sequence, but "fastboot erase" was used on the "bootloader" and "recovery" partitions, then the phone was unplugged. This left the system with no start sequence ... when I depleted all the battery charge it simply wouldn't respond to anything and has since been lifeless. I'll pry it open and take a look at the internals just for fun and to get one last squeeze of value from it. I also plan to bash it with a hammer which will be particularly satisfying.
apsommer said:
I don't remember the exact sequence, but "fastboot erase" was used on the "bootloader" and "recovery" partitions, then the phone was unplugged.
Click to expand...
Click to collapse
You can safely overwrite boot, but never ever touch the bootloader. The bootloader is responsible for starting all the various programming modes, as well as passing on execution onto the kernel start during normal boot.
BTW, I don't think there is any reason at all for erasing partitions - when you overwrite them with your own data they will end up being clean anyway.
I also plan to bash it with a hammer which will be particularly satisfying.
Click to expand...
Click to collapse
While I can understand your frustration, that would be quite silly. Even if it has no value to you, it's still recoverable for anyone with the skills and tools - try to sell it instead, if anything it could be used for spare parts.
Antonio
antonio.galea said:
You can safely overwrite boot, but never ever touch the bootloader. The bootloader is responsible for starting all the various programming modes, as well as passing on execution onto the kernel start during normal boot.
BTW, I don't think there is any reason at all for erasing partitions - when you overwrite them with your own data they will end up being clean anyway.
While I can understand your frustration, that would be quite silly. Even if it has no value to you, it's still recoverable for anyone with the skills and tools - try to sell it instead, if anything it could be used for spare parts.
Antonio
Click to expand...
Click to collapse
Yes, I learned my lesson with "fastboot erase bootloader". I'd be happy to sell it for parts, what website would you recommend for listing it?
apsommer said:
Yes, I learned my lesson with "fastboot erase bootloader". I'd be happy to sell it for parts, what website would you recommend for listing it?
Click to expand...
Click to collapse
I'm trying to find out more information about the emergency recovery mode for Z5C - I might be able to find out a way to recover your phone. If I'm successful (be warned, it's a big if - so please don't count on it), you could sell it as a working phone instead of as a brick.
First problem, I don't know how to enter EDL mode on the Z5C: but I hope an EDL cable could work. I've ordered one for testing, since it's an useful tool for recovering a lot of other phones too - it will take a while to deliver, so don't hold your breath. You could also join me in my experiments (after all, you have nothing to lose) by ordering one yourself (you can find cables for as low as 3$).
Second problem, the software tools. Given the ubiquity of Qualcomm chips, apparently there are quite a few available. In the opensource arena, I've found those:
https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md
https://github.com/openpst/sahara
https://github.com/bkerler/edl
Third problem, finding the signed binaries you have erased from your phone. I guess they can be extracted from my own device quite easily - they are on eMMC after all.
For an in-depth discussion of EDL mode, geared towards its (in)security, I've been reading Aleph Security articles here.
Antonio
apsommer said:
Thank you for the response, I was about to throw the phone away. Can you be a little more specific? I see your post here regarding a rebooting loop with red light flashing. However, I don't have any response from the phone whatsoever ... nothing on the screen, or led in top right. It does not accept a charge from 1A or 2A source, it is literally a paper weight right now. I need to "jump start it" or something of this nature. It won't charge at all.
Click to expand...
Click to collapse
Hey again, sorry for late reply. Work...
My issue seems totally unrelated to yours. My problem was that I was doing the flashing wrong, instead of just flashing the entire .zip I flashed boot file etc and this is what started the issues with not taking charge, BT wasn't working, wifi etc. But I had more juice in the phone since you want to have quite a bit before doing flashing, but I read your post about discharging it.
If you can't revive it, don't fear rooting and flashing, just make sure to read and to take all steps necessary. I kinda messed up my Z1C and I didn't do any changes to my Z5C until recently. Well, maybe a year now, just because of that occurrence.
antonio.galea said:
I'm trying to find out more information about the emergency recovery mode for Z5C - I might be able to find out a way to recover your phone. If I'm successful (be warned, it's a big if - so please don't count on it), you could sell it as a working phone instead of as a brick.
First problem, I don't know how to enter EDL mode on the Z5C: but I hope an EDL cable could work. I've ordered one for testing, since it's an useful tool for recovering a lot of other phones too - it will take a while to deliver, so don't hold your breath. You could also join me in my experiments (after all, you have nothing to lose) by ordering one yourself (you can find cables for as low as 3$).
Second problem, the software tools. Given the ubiquity of Qualcomm chips, apparently there are quite a few available. In the opensource arena, I've found those:
https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md
https://github.com/openpst/sahara
https://github.com/bkerler/edl
Third problem, finding the signed binaries you have erased from your phone. I guess they can be extracted from my own device quite easily - they are on eMMC after all.
For an in-depth discussion of EDL mode, geared towards its (in)security, I've been reading Aleph Security articles here.
Antonio
Click to expand...
Click to collapse
Wow, you're a true engineer, never give up! Consider my phone part of your testing devices. Please confirm this is the correct EDL cable to purchase for the Z5C: EDL cable for all Qualcomm phones ... It will take a few weeks to get in my hands.
apsommer said:
Wow, you're a true engineer, never give up!
Click to expand...
Click to collapse
Hello, got my cable - but I've not been able to make it work so far. It could be because I need Windows and specific drivers, I'll look into some more. But yes, when it's fun I never give up
Antonio
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
No fastboot or custom recovery ?
Then no theirs nothing really to do
Maybe a battery replacement would boot it up
Sent from my ONEPLUS A6010 using Tapatalk
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
easyxpress said:
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
Click to expand...
Click to collapse
Nope it's just a chip on a circuit board
Sent from my ONEPLUS A6010 using Tapatalk
easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
twistyplain said:
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
Click to expand...
Click to collapse
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
easyxpress said:
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
Click to expand...
Click to collapse
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
twistyplain said:
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
Click to expand...
Click to collapse
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
what happened to TWRP ? thats stock recovery
will it enter fastboot mode ? if you can get into TWRP their is a chance of off loading your userdata to a PC
easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Sent from my LeMobile Le X526 using XDA Labs
twistyplain said:
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Click to expand...
Click to collapse
Sorry bad news.
As twistyplain said, your phone is absolutely fried, and there is no solution.
It's definitely no brick, that is a hardware issue... Most likely shorted solder connections. The same thing happened to two of our X727s, we have one left that still works.
I highly recommend buying a seemingly unbrickable Xiaomi phone. Their budget models are awesome and of course their flagships are awesome. Everyone in my family has Migrated to Xiaomi . I currently have Android 10 working flawlessly.
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
easyxpress said:
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
Click to expand...
Click to collapse
If you are in China and located in a large city or tech industrial area you should have plenty of shops that repair at the component level.
Your phone could very likely be repaired by a shop that has a hot air rework soldering station with an electron microscope.
We used to have these types of places in the US but they have all gone out business, replaced by board swappers, who charge a lot. I would suspect that you could get it repaired in China for 100 yuan or less.
I worked in Beijing for 3 months, about 18 years ago and these types of places were everywhere.