Database Users

Power button got screwed

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.

Shield Pro - APX Mode

Hi all,
I have the Shield Pro, running 5.1, and it won't start
It was working fine yesterday, but when I got home from work this evening, it was unresponsive. The power light was stuck on, but would not respond to any controller input or, as far as I can tell, any USB input.
I pulled the power out, and plugged it back in, and the light came on instantly. No display on the TV. I plugged it into my PC, but Windows doesn't see anything attached (I have tried multiple cables). If I hold the power button for five seconds, the device just turns off. If I touch the power button even just briefly, the green light comes back on. I can't get into Fastboot or anything. There is no HDMI output at all.
This is, naturally, really quite annoying.
However, after having it hooked up to my PC via USB for a while (not sure how long, sorry!), my computer bleeped like it does when a new USB device has been discovered, and bingo! I now have an "APX" device, with no drivers installed.
So. Who knows about APX mode for this thing?

I'm pretty sure APX is a low level recovery mode.. I recall reading that elsewhere.
go to the developers nvidia site amd search on how to reflash via apx

yeah, I had to use it on my old LG Optimus 2X, back in the day. There's nothing on the nVidia developer site about using it though

unfnknblvbl said:
Hi all,
I have the Shield Pro, running 5.1, and it won't start
It was working fine yesterday, but when I got home from work this evening, it was unresponsive. The power light was stuck on, but would not respond to any controller input or, as far as I can tell, any USB input.
I pulled the power out, and plugged it back in, and the light came on instantly. No display on the TV. I plugged it into my PC, but Windows doesn't see anything attached (I have tried multiple cables). If I hold the power button for five seconds, the device just turns off. If I touch the power button even just briefly, the green light comes back on. I can't get into Fastboot or anything. There is no HDMI output at all.
This is, naturally, really quite annoying.
However, after having it hooked up to my PC via USB for a while (not sure how long, sorry!), my computer bleeped like it does when a new USB device has been discovered, and bingo! I now have an "APX" device, with no drivers installed.
So. Who knows about APX mode for this thing?
Click to expand...
Click to collapse
Apx mode ( and yes without drivers - couldn't even find around in Internet...) on pc ×device manager× shows me on my 500gb console when I removing internal shdd and connected with pc whiteout shdd (one day nothing to do and decide need open and have look what is inside in console...shdd, motherboard, cooler etc) . Another words sounds those symptoms very similar with my tests, but in my case that was mine experiments/investigations/discovery and your looks like you have some serious storage problem or kind of problem relaited with - can't read os or even bootloader which is on 500gb shdd or flash memory modul on 16gb.
Sent from my nokia 3310 using XDA Free mobile app

unfnknblvbl said:
yeah, I had to use it on my old LG Optimus 2X, back in the day. There's nothing on the nVidia developer site about using it though
Click to expand...
Click to collapse
after googling for a bit , i saw some references to the shield tablet, i think someone had an APX driver, maybe you could try that?

I could do, but APX mode is really, really dangerous. You need to know byte offsets and all that :S

unfnknblvbl said:
I could do, but APX mode is really, really dangerous. You need to know byte offsets and all that :S
Click to expand...
Click to collapse
if you know apx and you have all necessary stuff from Nvidia (which is not provided for public) you can replace internal drive or even ssd by installing bootloader, recovery, os etc straight on new drive from pc which is main factor why we can't swap them so easily, like 1 - 2tb drive or ssd - which would be fantastic ?. P.s. Something simular protection is for Xbox360 drives.
Sent from my Nokia 3310 using XDA Free mobile app

if that's the case you might have to send it for a warranty repair.. better not playing around if it's under warranty.

an idea for apx
move your shdd from shield and connect to pc then use this program(R-Studio 8.0) or other to restore date on u shdd I think it most work good luck
---------- Post added at 09:36 PM ---------- Previous post was at 09:22 PM ----------
I have tab p7500 and have this problem apx only jtag help me in apx mode you should now wish sbl for tegra x1 and have nvflash for shield pro sorey for my English the easy way use jtag or tray to restore data in shdd

would there be a way to just dd- flash a new recovery withthe hdd removed from the unit? I am having te same no logo, no bootloader issue and am trying to either find apx drivers (non-existent) or a workaround. There has to be a way.....

i have the same question. My intrest is more in tinkering with the tegra x1 exploit in order to get a different root solution not contingent on nvidias closed source crap. I'm running a 2015 foster model and it is getting increasingly difficult to find tutorials on that system specifically with the newer updates. +i am interested in learning the process to exchange the hdd and mopy and manipulate the widevine keys that don't work on mine after the forced 7.2.3 update that occured with all update sofware removed from my system that also fried my controller with a botched firmware update that is blacklisted and not mentioned on the internet except people asking and all replies deleted. you know general unfettered access to the system without the bootloaders say so . All of this should now be possible now that the real hackers have gotten involved and decided they want to promote this exploit for homebrew it has caused several low level apx drivers to popup in corners ive found myself in from time to time if somebody will just get them to do it for the shield tv instead of the shield tab and the switch it is proven to work.

Solved: 2nd Hand Galaxy S5 locked

Hi!
To make a long story short. I bought a second hand Galaxy S5 with a busted screen and heavily dented frame. I replaced the screen and the frame, screen works fine but after boot I found two problems:
Volume up/down don't seem to work (or the phone is blocked by the carrier?)
Phone is blocked via pattern
I contacted the previous owner but he doesn't remember his pattern (it took me two months until I found the parts I wanted and repaired the phone) and also doesn't remember his PIN. And since the volume keys don't work I can't enter neither in Recovery nor in Download mode.
The phone is being recognized in my computer, I tried to make the phone boot with adb but since it's locked it doesn't work. I guess the USB debug options is not switched on.
Is there any alternative method to make the phone boot into recovery? I'm fairly new with adb so is there is a way please post dumb-proof instructions :silly:
Thanks a lot in advance!

Just to double check you are using the correct key combo
Recovery: Volume Up & Home & Power
Download: Volume Down & Home & Power
I can't think of anything off hand, so would concentrate on trying to get those buttons repaired
Possible you have either dislodged something during the repair, or whatever damaged the screen / chassis did

*Detection* said:
I can't think of anything off hand, so would concentrate on trying to get those buttons repaired
Click to expand...
Click to collapse
Thanks for your reply!
Unfortunately this means removing the screen again, which won't survive with my basic tools, I guess I have a new door stopper now

Tasurinchi said:
Thanks for your reply!
Unfortunately this means removing the screen again, which won't survive with my basic tools, I guess I have a new door stopper now
Click to expand...
Click to collapse
Doesn't look like you need very advanced tools at all, a piece of plastic and a screwdriver
https://www.ifixit.com/Teardown/Samsung+Galaxy+S5+Teardown/24016
I had to do this with an S4 a few weeks ago, and it was very simple to get to the volume buttons without any issues, 1 minute job

*Detection* said:
I had to do this with an S4 a few weeks ago, and it was very simple to get to the volume buttons without any issues, 1 minute job
Click to expand...
Click to collapse
To remove the S5 screen you need first to warm it up with a heat gun, the AMOLED screen is very sensitive to heat and extremely thin, I'm quite sure that the new screen won't survive my removal attempt according to what I read in the web (to remove the old one I just used a hair dryer, since it was already broken I did not need to be much careful).
Additionally I used a strong 3M double sided tape to install the new one.
The sensors for the volume keys seem to be on the frame (according to my poor visual analysis), so if I need to buy a new frame (and probably a new screen) I may end up looking for a new S5 to get repaired...

Tasurinchi said:
To remove the S5 screen you need first to warm it up with a heat gun, the AMOLED screen is very sensitive to heat and extremely thin, I'm quite sure that the new screen won't survive my removal attempt according to what I read in the web (to remove the old one I just used a hair dryer, since it was already broken I did not need to be much careful).
Additionally I used a strong 3M double sided tape to install the new one.
The sensors for the volume keys seem to be on the frame (according to my poor visual analysis), so if I need to buy a new frame (and probably a new screen) I may end up looking for a new S5 to get repaired...
Click to expand...
Click to collapse
Just remembered as I was typing, you need a USB Jig, insert that into the USB port when the phone is powered off, and it forces the phone into download mode without the need for buttons
Either make your own (I did for the S4 with a dead power button) or buy for a couple £ on ebay
http://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/

*Detection* said:
Just remembered as I was typing, you need a USB Jig, insert that into the USB port when the phone is powered off, and it forces the phone into download mode without the need for buttons
Either make your own (I did for the S4 with a dead power button) or buy for a couple £ on ebay
http://www.xda-developers.com/need-a-samsung-usb-jig-build-your-own/
Click to expand...
Click to collapse
Wow, that's cool! Thanks for the tip! :good:

Good luck

Thanks! I just bought two in $bay, one for €3.99 and a second one for £0.99, just in case... I'll report here how it goes...

Tasurinchi said:
Thanks! I just bought two in $bay, one for €3.99 and a second one for £0.99, just in case... I'll report here how it goes...
Click to expand...
Click to collapse
Great, I ordered one from ebay but was going to take a week, so went to the town and bought the resistors and a cheap USB lead, made one while I waited, so I have a couple here now too
Yea let us know how you get on, if the volume keys are physically dead, I'm sure there will be plenty of apps you can use to remap volume to soft keys

I also ordered two because one is from HK, the other from Europe
(what does not rule out the possibility that the HK one arrives first)
Just thinking out loud, could it be that the carrier (Swisscom in this case) blocks a device in order not to enter in Recovery/Download mode? Is this technically possible?

Tasurinchi said:
I also ordered two because one is from HK, the other from Europe
(what does not rule out the possibility that the HK one arrives first)
Just thinking out loud, could it be that the carrier (Swisscom in this case) blocks a device in order not to enter in Recovery/Download mode? Is this technically possible?
Click to expand...
Click to collapse
No they don't have that low level access to stop buttons working before the ROM loads, they could block an IMEI, so the phone won't work on the network any longer, but not physical buttons
Download mode is available even if you wipe ROM & Recovery, nothing to do with the carriers

Ok, I got the Jig, plug straight into the phone and it boots in Download Mode!!
BUT!! I open Odin, flash the new 6.0.1 Firmware and after the reboot the S5 is asking for the pattern again!!
I guess I'm missing something with Odin, which one of the options sets the system back to its delivery status? Re-Partition?
Thanks a lot in advance for the help!
Cheers
T

Tasurinchi said:
Ok, I got the Jig, plug straight into the phone and it boots in Download Mode!!
BUT!! I open Odin, flash the new 6.0.1 Firmware and after the reboot the S5 is asking for the pattern again!!
I guess I'm missing something with Odin, which one of the options sets the system back to its delivery status? Re-Partition?
Thanks a lot in advance for the help!
Cheers
T
Click to expand...
Click to collapse
Check the "NAND Erase All" option, should wipe the phone back to factory settings

Did that, unfortunately the S5 now doesn't boot. It freezes at the start screen, I let it "hang" for 40 minutes, then removed the battery, press the power button for about 30 seconds, put the battery again and rebooted.
It's still hanging (15 minutes so far...)

Tasurinchi said:
Did that, unfortunately the S5 now doesn't boot. It freezes at the start screen, I let it "hang" for 40 minutes, then removed the battery, press the power button for about 30 seconds, put the battery again and rebooted.
It's still hanging (15 minutes so far...)
Click to expand...
Click to collapse
Did you flash the ROM again without that box checked, once you had done the wipe? Try that (Some people saying to flash a few times)
Next step I'd try firmware recovery with KIES
http://www.samsung.com/uk/support/usefulsoftware/KIES/
Try that, then if still having problems, try below
Flash the ROM with the PIT file for that model S5
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
PIT in PIT section
ROM in AP
Flash together
Uncheck the Wipe NAND box first, make sure repartition checks itself once you add the PIT file
Which model S5 is it ?

*Detection* said:
Did you flash the ROM again without that box checked, once you had done the wipe? Try that (Some people saying to flash a few times)
Click to expand...
Click to collapse
Thanks again for the help!
I didn't repeat the flash, I will try again tonight with the options you mention
*Detection* said:
Which model S5 is it ?
Click to expand...
Click to collapse
S900F

Sucess!!! After some troubles with Odin I used Kies3 and I could successfully get back to factory settings. And with 6.0.1 firmware!!!
Thanks for all the help! :good::good:

Tasurinchi said:
Sucess!!! After some troubles with Odin I used Kies3 and I could successfully get back to factory settings. And with 6.0.1 firmware!!! :-O
Thanks for all the help! :good::good:
Click to expand...
Click to collapse
Great
Pleased it worked

Bricked?? Nvidia Shield Would Not Update! Can I Solder/JTAG?

Hello,
I have tried the search feature to no avail in regards to following the appropriate troubleshooting steps to ensure that I can at least boot to fastboot, however I cannot boot into the fastboot menu.
These are the steps I have tried so far:
With only the Power, HDMI, and MicroUSB to USB connected
1) Disconnect the Power
2) Hold Nvidia Button Down
3) Reconnect the Power
4) Release Nvidia Button (~2 seconds)
5) Press and Hold Nvidia Button (~5 seconds)
again, I am still at a black screen with no output whatsoever.
I have also tried allowing a full power cycle (where the Nvidia TV is left alone for approximately 15 minutes)
I also tried the Nvidia chat support who suggested that I try plugging in the controller and pressing the A and B buttons simultaneously, etc. to no avail.
Is there anyway to force a fastboot interaction via console? I would just like to reflash to stock. Even if this method requires altering the hardware via soldering.

You need to connect (Depending on your Model), either a MicroUSB, (2015, 16Gb, Pro / 2017 Pro), or a Male Type "A" to Male Type "A" (2017, 16Gb) between the Shield TV, and some Computer. I prefer to use a Netbook running Win7. But, This should be equally valid for Linux, and Mac.
So with you PC / Netbook turned on, and connected to the Shield TV via USB. Leave the USB style plug in the Shield and if possible yank the Brick (Wall Wort), instead.
Start a Two beat count.... 1... 2... 1... 2... (It would work better if you had a Clock that had a Second Hand.) But once you have this 'beat' drop in the Wall Wort on count Two. And THEN tap the Power Button, hold this for Three counts, than release (Pro Uses might note the SSHD will start to wake at this very moment), and immediately re tap, and hold the Power Button till you enter the Recovery Mode.
This is a very time sensitive attack, and 2/3s of the time will land you at the nVIDIA Logo. (Where available), and your only option here will be to start over again. Or boot completely into Android, and use
$ adb reboot recovery
To force the Device to reboot into recovery mode.

Ichijoe said:
You need to connect (Depending on your Model), either a MicroUSB, (2015, 16Gb, Pro / 2017 Pro), or a Male Type "A" to Male Type "A" (2017, 16Gb) between the Shield TV, and some Computer. I prefer to use a Netbook running Win7. But, This should be equally valid for Linux, and Mac.
So with you PC / Netbook turned on, and connected to the Shield TV via USB. Leave the USB style plug in the Shield and if possible yank the Brick (Wall Wort), instead.
Start a Two beat count.... 1... 2... 1... 2... (It would work better if you had a Clock that had a Second Hand.) But once you have this 'beat' drop in the Wall Wort on count Two. And THEN tap the Power Button, hold this for Three counts, than release (Pro Uses might note the SSHD will start to wake at this very moment), and immediately re tap, and hold the Power Button till you enter the Recovery Mode.
This is a very time sensitive attack, and 2/3s of the time will land you at the nVIDIA Logo. (Where available), and your only option here will be to start over again. Or boot completely into Android, and use
$ adb reboot recovery
To force the Device to reboot into recovery mode.
Click to expand...
Click to collapse
I appreciate your reply but again I am not getting any output what so ever after attempting to apply an update to the Nvidia Shield TV. Is there any procedure to force the device to flash even over hardware?

Depends on if you have a 16Gb or not...
Let's put it this way, if you have a 16Gb it's pretty a wrap. If you have a Pro then you have a few options. Like ripping the SSHD out of it, and attaching it inside a PC running Linux. Or at the least a PC running a live install of Linux.
Which is critical to maintain your private keys. Everything else can be discarded. But, not those DRM Keys. Not if you plan on ever using anything that will need Widevine L1.*
Now that is wholy your choice to make. Either way you will probably want to down that Torrent, which is a backup of someone else's Shield TV. It WILL reserect your Device. But, if you haven't managed to recover your own Keys you will not be able to rewrite them back later on. And, the upshot of that will be the loss of all Widevine L1 Services. e.g. Amazon, Netflix etc...**
*https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
**https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23

Ichijoe said:
Depends on if you have a 16Gb or not...
Let's put it this way, if you have a 16Gb it's pretty a wrap. If you have a Pro then you have a few options. Like ripping the SSHD out of it, and attaching it inside a PC running Linux. Or at the least a PC running a live install of Linux.
Which is critical to maintain your private keys. Everything else can be discarded. But, not those DRM Keys. Not if you plan on ever using anything that will need Widevine L1.*
Now that is wholy your choice to make. Either way you will probably want to down that Torrent, which is a backup of someone else's Shield TV. It WILL reserect your Device. But, if you haven't managed to recover your own Keys you will not be able to rewrite them back later on. And, the upshot of that will be the loss of all Widevine L1 Services. e.g. Amazon, Netflix etc...**
*https://forum.xda-developers.com/shield-tv/general/guide-migrate-to-ssd-hdd-size-satv-pro-t3440195
**https://forum.xda-developers.com/showpost.php?p=67426622&postcount=23
Click to expand...
Click to collapse
I have the 16GB model and I am not sure what would be the best way of resurrecting my device upon a bootloader that is corrupt.

I think your forked... The only way it could possibly be done would be to pull the ROM Chip, and clone this in a not so dissimilar fashion, and then flash a working 'Image' back onto it. Before resoldering said Chip back onto the Mainboard.
Again, Not something just anyone could do.
Look I have no idea how old your Shield is, or if you still have, or have ever had any Warranty Rights to begin with. Assuming that you still had any of these 'Rights'. I would recommend playing dumb, and attempt an RMA, and pray that it works out.
If that also fails, then I guess you are what is termed as being SoL...

Ichijoe said:
I think your forked... The only way it could possibly be done would be to pull the ROM Chip, and clone this in a not so dissimilar fashion, and then flash a working 'Image' back onto it. Before resoldering said Chip back onto the Mainboard.
Again, Not something just anyone could do.
Look I have no idea how old your Shield is, or if you still have, or have ever had any Warranty Rights to begin with. Assuming that you still had any of these 'Rights'. I would recommend playing dumb, and attempt an RMA, and pray that it works out.
If that also fails, then I guess you are what is termed as being SoL...
Click to expand...
Click to collapse
Thanks Ichijoe I tried to also to boot into recovery using alt + print screen + i (on an external keyboard) in order to restore the device however this did not work.
I wanted to pull the ROM chip but I don't know of any software available to allow such a feat. Does anyone have any information on utilizing J1D1 or J1D2?

pandorarob0t said:
Thanks Ichijoe I tried to also to boot into recovery using alt + print screen + i (on an external keyboard) in order to restore the device however this did not work.
I wanted to pull the ROM chip but I don't know of any software available to allow such a feat. Does anyone have any information on utilizing J1D1 or J1D2?
Click to expand...
Click to collapse
This is getting oh so over my head now. So take it for what it's worth. But, as I understand it One would need an EEPROM Programer, and the "Software" would just be written as a RAW Data. Again not entirely, not unlike taking a certain 'Raw' backup that someone tossed up to the Net as a Torrent File. For bricked Pro users.
Pulling the ROM Chip off the Board is not something just anyone can do without destroying the Chip, the Mainboard, or both. The EEPROM Programmer is also an additional cost, of which I would have no clue. Needless to say, in the long run it's just unfortunate as it is, to just get a new Shield.

pandorarob0t said:
Hello,
I have tried the search feature to no avail in regards to following the appropriate troubleshooting steps to ensure that I can at least boot to fastboot, however I cannot boot into the fastboot menu.
These are the steps I have tried so far:
With only the Power, HDMI, and MicroUSB to USB connected
1) Disconnect the Power
2) Hold Nvidia Button Down
3) Reconnect the Power
4) Release Nvidia Button (~2 seconds)
5) Press and Hold Nvidia Button (~5 seconds)
again, I am still at a black screen with no output whatsoever.
I have also tried allowing a full power cycle (where the Nvidia TV is left alone for approximately 15 minutes)
I also tried the Nvidia chat support who suggested that I try plugging in the controller and pressing the A and B buttons simultaneously, etc. to no avail.
Is there anyway to force a fastboot interaction via console? I would just like to reflash to stock. Even if this method requires altering the hardware via soldering.
Click to expand...
Click to collapse
let's try this way :
unplug your power cable of the shield tv
plug your lan cable on your shield tv ( be sure DHCP on your local network is turning on)
plug your new shield controller on the usb port of the shield
plug the power cable and DON'T TOUCH THE CONTROLLER for 1 minute
now hold down home button and left button ( on the X) for 3 seconds
normally you can see the blue signal of the controller 3 times. this mean the procedure working good ( if not retry till it work)
now let your shield working around 2 hours ( depend of your download speed)
afetr this time, normally the shield finish downloading the update and restart... now you normally can see the screen

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