Database Users

touch2 hang on 3 color boot mode :(

hi all : i have one set of HTC MEGA TOUCH 2 that it hang on 3 color boot menu.
i can't do hardspl or flash any flash file on to it , plz help me what should i do ?

1) When the phone is off, press and hold the button VOLUME DOWN (left side of the phone).
2) While holding the volume button, you press short the ON / OFF button and let it go.
3) If you see a warning message on the display, release the VOLUME-button
4) Press the VOLUME UP button to perform the reset or press any other key to cancel the reset.
Good luck....

I have a HTC Touch2 that is tuck in the Bootloader.
I have removed the battery and attempted the hard reset, as soon as it comes on it goes straight to the bootloader screen.
If the phone is connected to the PC, it says USB in the white band.
If not is says serial.
No SD card fitted, no SIM card fitted.
Any ideas?

Flash with a stock ROM in USB-mode should work for you

I thought you could only flash via USB if the device has been Hard-SPL'd? and you need to have an activesync connection?

hogman said:
I thought you could only flash via USB if the device has been Hard-SPL'd? and you need to have an activesync connection?
Click to expand...
Click to collapse
Flashing with a stock ROM works without Hard-SPL, and as far as I know you can flash it when it says 'USB' in the bootloader mode. Correct me if Im wrong or else try...

To be honest, I fixed the phone without doing any of that. There seemed to be a problem with the USB port on the phone. I disconnected the battery and put some alcohol into the port (IPA!! not beer - lol) left it for a few seconds and then cleaned it out with compressed air. When I put the battery back in, it booted up fine.

wow... nice
why the usb-port?

strange...

hey guys, I see I have a problem from the damaged tape volume, so how can I make HR and enter bootloader

solved!
hogman said:
To be honest, I fixed the phone without doing any of that. There seemed to be a problem with the USB port on the phone. I disconnected the battery and put some alcohol into the port (IPA!! not beer - lol) left it for a few seconds and then cleaned it out with compressed air. When I put the battery back in, it booted up fine.
Click to expand...
Click to collapse
This man is my hero. I *very* carefully extracted a little bit of lint that was stuck right at the back of my HTC USB port in my touch2, with a drawing pin (tack for the americans).
While I would not reccomend using a pin, as it may damage the port, it fixed my phone right up, it now no longer gets stuck on the bootloader (tri-colour screen), and it also fixed a problem in which I got a reccurring error telling me to remove the USB headset as it doesn't work (or something to that effect) while nothing was actually plugged into it.
Thanks again, hogman!
edit: I can't figure out how to give you thanks rating or whatever it is, so this will have to do. Yes, I'm a noob!

ZE550KL fell in water. Hardware damage or hardbrick?

Hi everyone! I'm a noob which made a mess with a brand new asus Ze550KL: I accidentally tossed it inside the toilet (possible water damage).
More precisely, this is my problem, I hope someone may help me .
THE CURRENT SITUATION
Now it's totally dead. I don't know if it is a broken hardware problem or if it just hardbricked, and I don't know how to find it out since the device is toally dead (not turning on, not responding to POWER ON + VOLUME and not entering recovery/fastboot mode, no lights) except from the fact my pc recognizes it as "QHSUSB_BULK" when connected via USB, but can't browse the files inside nor do anything else). Also I think the battery receives energy when connected with the recharge cable to the wall, since the alternator gets hot like usual.
THE SYMPTOMS BEFORE SILENCE
I don't know if it helps you to know, but the dying process was this: The device fell in the water while turned on. I picked it up immediately and it seemes still working, but the touch screen was not reacting to my fingers touch. I immediately pulled out the battery and dried every reachable spot with a towel. I noticed that the water did not get inside the back case, so after a few minutes I tried to insert again the battery: as soon as the battery touched the electrical contacts the device started to vibrate like hell, so I immediately pulled it out again. I put the device in a hot place a few more minutes, than tried again with the battery: it didn't vibrate, I tryied to power it on and it could reach a logo screen with some words on the toop. Unfortunately I don't remeber if it was "Fastboot" or "recovery", but it must have been one of the two. It remained stuck on this screen, so i turned it off again.
The sequent day I had the bad surprise: it was totally dead. I put it in a warm place and waited a lor of days. After 2 weeks it's now still totally dead.
MY QUESTION
Before spending money I'd like to kwow if its just a software problem (hard brick due to cotact with water) or hardware problem, and in this last case what was damaged. How to do it? More precisely:
1) I read a lot of guides about unbricking but I couldn't find anything related to the ze550kl for the case it's totally dead, with no possibility to enter recovery mode or fastboot mode. Is there a way I can make a check-up via PC? How can I solve the "QHSUSB_BULK" problem (since i read some guides, but nothing related to ze550kl with screen not turning on at all).
2) In case it's hardware damaged, how can I understand what the water damaged precisely (in order to know if it's worth repairing or not)?
Thank you very much!!! :laugh:
EDIT (08/11/16):
Maybe I made one step towards the solution (if there's any). In fact I installed the qualcomm processor drivers on my laptop, so now it recognizes the devise as "Qualcomm HS-USB QDLoader 9008 (COM3)" when connected via USB. This means that I can connect to the device using QFIL (software used for unbricking via usb, explained here : androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable-qhsusb_dload_qpst_qfil/).
However the problem is that QFIL returns this error message when trying to download something on the device:
"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol
in QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)
in QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail
Finish Download".
Using google search I think it may be because also that part of the ROM which allows to download files on the device via USB is corrupted. Is that true? Do you have any solutions?
Thank you again!!!
Grazie!

Usually, when your phone's got water inside it anyhow, you'd best bury it in rice for about half a day or so.
But considering you've done that all, you'd better get professional opinion instead.

up! (pls see "edit" chapter in 1st message)

Locked out of EDL, ROM, and recovery

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.

Z5C will not charge at all

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

M30s does not boot - stuck at very first screen

Hi all,
my Gylaxy M30s rebooted itself yestarday, and now is stuck at the very first screen (the one showing "SAMSUNG Galaxy M30s" in the center and "Powered by android" at the bottom).
Vol down + power results in a reboot attempt (screen goes black, vibration), but the phone is stopping at the same screen again.
I am not able to turn the phone off.
Switching from Vol down to Vol up immediately when screen goes black does not enter recovery mode.
Vol down + power while charging sometimes leads to the charging symbol being shown on the screen, but without the percentage in the middle.
Charging over night did not help.
The phone cannot be connected to a Win PC.
Any suggestions what I can try?
Thanks,
Alchemist

Try volume down+volume up and while pressing those buttons, plug your phone into your computer. Tell me the results of that.

Nothing happening...

I mean trying those combinations immediately after using power+ volume down to reboot.

What did you do with your phone? Died suddenly when normally using?

Yes, phone died during normal usage.
Ah, I see - a screen comes up warning me that downloading a custom OS might harm the phone.
Also, the PC makes this "USB connected" sound when I then press Vol up, but I do not see a new drive connected, I think.
I am slightly optimistic now?

Press volume up.Then install Samsung usb drivers(search on Google)

Ugh, just wanted to do this, but now the phone is completely dead. No response to any button or charging. Will hang it on the charger for a few hours, but my optimism is gone...

OK, now it works again. I am in the screen with the colourfull stuff and the phone waits for some download.
Driver is installed on PC. Is there anything supposed to happen - the phone is still not accessible via PC, or is it?

Install Odin (search in Google 'odin samsung' and download)
Download stock firmware(android os) at www.samfw.com , after downloading you will see files like AP-M505xxxxxxx.tar.
Select, from the stock ROM AP-M305xxxxx.tar for AP in odin CSC-M305xxxxx.tar for CSC, and so forth then click start .

OK. All data will be lost, right? Is there some way to access the internal storage to rescue some files before flashing the new firmware?

Sorry to tell you that you cannot have data restored bad news for you sorry

Sorry. If you only see one file(make sure it is .tar or .tar.md5 file) after you extracted the .zip firmware, install it to the AP slot.

Any chance I could fix this issue with tools like dr.fone, UltFOne, ReiBoot?
I do not have any experiences with these - no idea if the just want to make money with desparate customers? ...

These could possibly brick your phones even more ( anyways flashing with Odin could also brick your phone). However, it in some cases can fix your device.
If you HAVE to have your data back and you don't mind paying, visit a service center and tell them: 'Hey my phone died and i HAVE to have the data back '.(I know, your warranty is expired probably, but they might still do the things for you with paying.)(if those stores closed during lockdown then I don't know any way to fix it.)

OK, another thing I have observed: The screen goes black after about 30 sec to 5 min when not charged - the shorter it was charged, the quicker the screen goes black. Buttons do nothing when screen is black. When reattached to charger, phone tries to boot and is then stuck at said screen - no button pressing needed for the phone to try to start. The longer the phone has been without charger, the longer it takes until the phone tries to boot.
Maybe it's just the battery that is dead - or would the phone with a dead battery boot normally when attached to charger?

If that is the case, open up your phone, put in a replacement battery, and try to boot up(yes, you need to. it will be a frustrating process.). Your phone could be having a faulty battery and nothing else, to cause this issue.

Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..

Mystic_Jamdam said:
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Click to expand...
Click to collapse
Truth to be told: The guy in the repair shop opened the phone and wanted to change the battery - when he saw that water must have come into the phone, corroding the motherboard. So yeah, all data lost, but... no backup, no mercy. I now have set up a NAS for all computers and devices in our family... ;-)

If it really is a hardware problem then the quality must have been really bad.