Related
Hey ... I have A BIG problem. My power button on my HTC TyTN got screwed. And I don't know how to fix it. Tried dissassembling and the button isn't as elastic as the other ones.
So - any underlay or whatever. Could it help? Anyone who had the same problem?
I checked it ... and the button [the small black thing] doesn't "click" ... so - what can I do with that? My warranty has expired few days ago.
Or, is there another way to get into the bootloader except OK + Power + Softreset? I wanna flash new ROM (which I really need, this one is kinda weird) and I'm afraid of doing it (just for sure if I brick the phone).
You have to take the plunge and flash the unit using RUUwrapper.
Another alternative is using MTTY.exe (or another terminal too over a virtual USB connection) to place the phone in bootloader mode among other things.
If you know how to use JTAG (I'm just learning about this), then you have nothing to wory about.
But ... it has to be connected to activesync. And if thar ROM will be bad (won't boot) or flashing fails, I won't be able to connect phone to RUUwrapper.
Or can mtty put "dead" phone into bootloader?
pajousek said:
Or can mtty put "dead" phone into bootloader?
Click to expand...
Click to collapse
Yes it can. I do not remember the command right now.
NB: A 'bricked' phone will always be in bootlader mode anyway.
You can run the terminal command "r2sd all" (this works on Charmers/Magicians) (so you'll have to look up your variant) to back up the current ROM to the M2 card (using a RAW writing method) in MTTY.exe (or any other suitable terminal program).
Well, I'm still a bit scared that mtty won't put the phone into bootloader.
And can you please explain me this? "NB: A 'bricked' phone will always be in bootlader mode anyway."
If i have bad XIP or whatever, it just has white screen and nothing happens. Will mtty be able to put phone into bootloader even after this?
Same problem Here
Hi Friends,
I screwed my HTC Hermes power button while trying to fix its earlier problem.
Now to turn the backlight on ..i changed the settings and I can now use any button to bring it out of Sleep mode....
I used a program available on this site to enter bootloader.
However, the problem remains when "power button" is to be pressed.
Any advice on how to get over the "Press power button" to start the ROM flashing....
Has it just popped off the board slightly?
Does it click with some applied pressure in a particular area?
I just yesterday repaired the power button on my hermes, it had popped out from the PCB on one side.
Bit of soldering managed to re-attach the metal outer case of the switch to the PCB, all seems to be working again.
DarK501 said:
Has it just popped off the board slightly?
Does it click with some applied pressure in a particular area?
I just yesterday repaired the power button on my hermes, it had popped out from the PCB on one side.
Bit of soldering managed to re-attach the metal outer case of the switch to the PCB, all seems to be working again.
Click to expand...
Click to collapse
Its completely come out of the PCB... I tried but doesn't work for me...
Also, further damage has been done as the Battery connector has come off the PCB......
Phone is completely off now. Will keep you posted.
Hi,
I have a rooted NST, everything was fine. For the last few weeks I did not use it, as I was moving.
A few days ago, I have reactivated it. After charging it for a while, it worked flawlessly again. With one exception: In the upper right corner instead of the battery indicator it showed a battery with a question mark in it. I look at the battery status in Nook Color Tools, it said "unknown battery error" (or similar).
Today I wanted to use it again, but it does not do anything anymore. It still shows the screensaver image, but won't boot despite being fully charged (at least it was hanging on the wire for a few days, so it should be charged). Long pressing the power button does nothing, the "n" button does not do anything either.
If I attach it to my PC it shows very strange behavior: It won't mount any drives, but if I go to device manager, it will show an device called "OMAP 3630". The device is marked with a yellow exclamation mark in device manager.
After about 1 second, the device disappears from device manager, accompanied by the windows sound for "device disconnected". After another 1 second, it reappers, together with the "device connected" sound, then it disappears again, reappears etc. This goes on indefinitely.
Do you have any tips on how to revive the device? I don't even know where to start, as I don't even seem to be able to initiate a reboot. I would not mind losing any data, nothing irreplaceable on the device.
Thanks a lot in advance!
rhhd
Press and hold power botton for 10 seconds then release it and hold again to reboot nook .
Likely restoring with 8 missed boot solve your problem .
boot with noogie Image and apply ur backup .....and if u cant boot with noogie Image ... it's Hardware Issue ... repair it if warranty cover
also maybe ur charger damage ur nook battery .... try steps above
good luck
When it says OMAP3630 that's the ROM bootloader in the TI processor trying to boot over USB.
If it's bouncing up and down that quickly, it's clearly hitting an error at an early stage.
Do you have any bootable SD cards like noogie or ClockworkMod?
Try them, see if it boots up.
Yes I still have a bootable image (the one I used to root, I think it was clockwork), but I do not know how to even initiate a reboot. As I said long pressing the power button does not help.
Did you try just putting the SD card in?
If it's cycling in the boot loader it may not need to be reset.
Yes I tried that, it makes no difference.
Also if I put the card in and then plug the device into my computer it makes no difference.
Well, get out the T-5 Torx driver, open it up and disconnect the battery.
if u still under warranty go and replace it better to do somethiing void ur warranty ........anyway ....last question .....when u connect ur nook to pc ,indicator led become green or orange?????
try follow renate instruction......she the only one expert here and the one can give u support (all credits goes to her)
good luck
Sent from my NOOK using xda app-developers app
the light becomes green when connected to the PC or the charger.
Okay, I will open the device and disconnect the battery. I can only do this when I get back from a business trip in a week though.
Are there detailed disassembly instructions anywhere?
Thanks again!
if u still under warranty ....... dont assembly ur device may it void warranty ....just check if it boot or not ....if not then send it back for replacement .....if ur warrantt not cover so , follow steps tha renate told u
good luck
Sent from my NOOK using xda app-developers app
I dont live in the US so a warranty exchange would be complicated. Probably not worth it for a device of this price class.
Also, B&N are famous for their aweful warranty policies, where you have to give them a credit card number before they take the device, and then they decide at their discretion whether they think it is a warranty case. If not they will charge your credit card and send you a new one.
I found a nice disassembly video on Youtube, just waiting for the Torx screwdriver I bought on Ebay to arrive (and for me to get back from my trip).
I've taken my Nook apart so many times that I no longer forget to pull the SD card out before I try to slide apart the case.
Try to connect your device with USB cable in a computer.
Then you will able to hear the connect/disconnect sounds (and when your nook is on or off).
Now, try to press the power button for a while (and you'll hear when it shutdown).
I´m my case, my NSTG was stucked in "Rooted Forever" screen (noogie.img boot) and was necessary to press power button some times and hold. Before, I´ve tried to disconnect the battery, but the screen don´t changed (stayed in "rooted forerver" even without battery).
good luck
Before you open it, hopefully the battery is drained by now. Insert bootable SD card and connect to charger one last time. Maybe will boot after about 15-30 minutes of charging. Good Luck.
Hi,
I just came back from my trip. I opened the device, disconnected the battery.
Upon reconnecting, the device would not boot, but it was clear right away that something had changed: When connecting to the PC the on/off behavior was gone. Also, now the charging light would be orange.
After charging over night the device now works perfectly again, even the strange "? battery" symbol is gone.
Thanks for the help everyone!
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.
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)
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