Develop Bugs

Well and truly bricked - desperate

Hi all,
I desperate need help. After an unsuccessful radio flash, my Desire won't even turn on. No response from any buttons or lights. Here's how it happened:
I'm relatively new to Android. I recently bought a Desire, to replace my Touch HD, which has seen about 25 different WM ROMs, over it's life.
I successfully rooted my Desire and had tried a few ROMs. I was sitting on the MoDaCo Custom ROM r17, which was all customised and running perfectly. I'd even used ADB to successfully update my wifi config to connect to my company LEAP-authenticated network.
I decided to flash the latest radio (32.37.00.32U_4.06.00.16_2), from this thread:
http://forum.xda-developers.com/showthread.php?t=687464
I entered Recovery using 'Fake-Flash';
I started flashing the radio image;
All the good messages were scrolling down the screen;
I kept one eye on the phone while I worked on my laptop;
I saw a message saying something to the effect of "Finished installing radio..." (sorry, I don't remember the exact wording);
The blue recovery menu had returned, with 'reboot device' as the default selection;
As I clicked the trackball, I saw another message appear under the 'finished' messages, which said "Writing rad " I guess it didn't have time to print the whole message, when I selected reboot.
The screen went blank then a graphic appeared in the middle (where the recovery exclamation mark and triangle usually appear), of a software box with a curved yellow arrow over it and the android icon peeking out from behind it. I left it for a while (already had that sinking feeling) then pressed the power button. It switched off and stayed there.
Since then, nothing that I've tried has received any response. Various combination's of button pushes, USB connection, removed SIM, SD and battery...nothing, not even an LED.
I've searched and haven't been able to find any solutions to this particular situation. Can anyone help, or am I totally bricked?
Regards, PF.

The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?

socktug said:
The radio update does 2 reboots to install it. The software box with yellow arrow is the default graphic used by the fake flash recovery as far as I know so that wasn't any real problem.
I know this might sound silly, but is the battery charged?
Click to expand...
Click to collapse
No question is silly under this circumstance!
Yes. I'd just taken it off overnight charge. 100%. If I plug the USB cable in now, there is no response from the LED.

Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty

socktug said:
Leave the charger plugged into it for about 5 minutes and see if there is any response to it. With the usb bricks it would take nearly 5 mins to register and the led to light up.
I know this isn't a usb brick, but I've not seen anyone with a failed radio flash that has caused the phone to totally die to the extent that it won't even switch on.
I take it you have tried the usual power and volume button combos etc?
I suppose if there is no quick fix for this, the fact that it's totally dead may go in your favour if you try to get it repaired/replaced under warranty
Click to expand...
Click to collapse
ok. The charger has been plugged in for 35 minutes and still no response.

Also don't want to sound patronizing, but have you taken the battery out and turned on with the back button helld?
Ignore me, just reread your original post.

the procedure u said sounds rite, thats whats ment to happen, when you flash a radio, only other thing that comes to mind is, sure the radio u flashed was for the gsm desire?

so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.

cgrec92 said:
so what youre saying is that your phone simply doesnt turn on, not for a second?
if you press the power button NOTHING happens?
are you sure your charger isnt broken?
have you tried charging it through your pc?
have you seen if its recognised through adb devices on your computer?
have you tried a new battery?
if your phone is simply dead, it must be a hardware problem, in which case you can probably send it off for repair and not have your warranty void as the whole phone will need to be replaced. they cant identify if you have voided your warranty if your device doesnt turn on.
Click to expand...
Click to collapse
Right first time. It won't turn on at all. It doesn't react in any way to any of the button combinations I'm aware of from rooting and flashing it. Nothing happens at all.
I live in an HTC household, so I've tried a number of chargers and cables, including the PC's USB port. I haven't tried another battery...but the incumbent battery was holdng a good charge and was 100% at the time. What's more, I remember that the phone can run on the charger without the battery.
Not surprisingly, adb devices shows no connected devices.
I think everyone is right, it's back to HTC. I *hope* you're right that they cover it under warranty. I'm going on the weekend, so I'll let you all know the result.
Thanks to all for your help.

I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck

Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.

peewster said:
Maybe a usb brick? No usb is no charging. So when you didn't had a full battery, it may be went wrong on that.
Try another battery, if you can get to one.
Click to expand...
Click to collapse
In the usb brick situation you can still charge. This isn't it!

socktug said:
In the usb brick situation you can still charge. This isn't it!
Click to expand...
Click to collapse
Ok i didn't know that.

If the phone doesn't turn on at all, you can maybe try sending it back to the shop for replacement. Chances are, they won't be able to know what happened, so you can pretend it just stopped working.
If it gets back to HTC, they probably won't bother to figure out what's wrong with the phone and just give you a replacement. Otherwise, they'll just send you the phone back and you won't have lost much (maybe postage costs?).

ash1684 said:
I think you can try to remove battery, leave the phone with no battery for 30 minutes and then try to insert battery and connect to usb without power it on to check if LED (and than the phone) is revived.
I had an Acer Liquid that gave me same problem, pratically when a flash on the radio go wrong, the device go in "protection mode". You must also check on the net if there is a protection mode on Desire too, and if there is a button combination to unlock it. I repeat: i just giving an idea becouse the same problem happened for me on an Acer Liquid, so i'm not sure if it's the same for the Desire.
Good Luck
Click to expand...
Click to collapse
Thanks for the suggestion. I left the battery out overnight. Then tried to activate it (all the usual button combos) with:
Battery out, USB cable plugged in;
Battery in, USB unplugged;
Battery in, USB in.
I scoured the 'net for anything on protection mode for the Desire...no luck. If there is one, it hasn't been posted yet.

I would just act stupid and try to return it under warranty!

I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.

Umbrella Corp. said:
I think it should be ok to RMA this, if its completely bricked there is no way of them knowing that you tried a different radio.
Click to expand...
Click to collapse
Yes, if it's totally bricked then just send it back to HTC and they will change it with no problems just same as acer done with my Liquid

All's well that ends well
Good news...
The HTC service centre were kind enough to replace my 'faulty' handset.
Re-flashed with r19 and radio updated (patiently) successfully.
Thanks all for your support.

Nice one. Glad it worked out for you

Bricked? Help?

I Really didnt even do anything. flashed cm7.0.2 few days ago
with pershoot kernel
been running fine. never overclocked etc.
just few hours ago my phone kept freezing and when i turn it back on it would show black screen, pulled battery rebooted and froze in bootscreen.
wiped dalvik cache wiped cache rebooted been working fine then froze again
same thing happened
repeated the process then forze again so i thought i would wiped the whole thing so did factory reset and it showed something like E:cant mount/recovery/cache or w/e
(i used gmethod to rooted the device.)
....i flashed miui on top of it then flashed kernel and those error popped up again
....i was scraed rebooted...htc logo
for like 10 min...pulled out the battery....now my phone wont turn on... any ideas?
i know the phone is done for real. when i plug into charger nothing comes up
when i turn it on nothing comes up
when i turn it on to hboot nothing comes up
does anyone know where i can get a new motherboard?
i voided the warranty by doing the spring mod
or new screws with void stickers.

It's possible the battery is having problems, i doubt it though, it seems as though youve hard bricked your phone.

does anyone know where i can get the motherboard or better
OEM htc g2 screws with void stickers?

eunkipark92 said:
does anyone know where i can get the motherboard or better
OEM htc g2 screws with void stickers?
Click to expand...
Click to collapse
Haha
Sent from my T-Mobile G2 using XDA Premium App

By the looks of things, any number of factors could be contributing to your Desires errors. However, it does seem like you've messed up the partitioning on the Desire Z internal memory and its giving you errors for it.
Try these steps.
1. Take the battery out and plug in your charger.
If the light doesnt come up try plugging your USB cable into your PC to charge.
If the light still doesn't come up your Desire Z is gone.
However, if the light does eventually come on, go to 2.
2. If any light comes up, then try turning it on.
If the screen turns on and you see ANYTHING besides black thats GOOD. go to 3
If the screen doesn't turn on there may be a motherboard issue.
3. Now if you can get it to turn on and not show black you should try this:
3a. Plug it into your PC then from there hold VOL DOWN and then navigate your way to Fastboot. It should say FASTBOOT USB or something like that.
3b. Flash a stable ROM onto your phone via your PC by going into recovery, mounting as storage then copying a ROM over. Then just flash the ROM onto your Desire Z and it should be fine.
If all this fails you should send it to a repair shop. There's no way you would get warranty to fix it at this point.

so ok i managed to get mini usb cable
When i conntected my phone to charger last night the orange battery light came on.
but nothing else.
when i clicked voulme down button then connected it to my computer it vibrated 5 times then green light came on.
And on my computer it showed up as Qualcom CDMA technologies MSM.
im searching everywhere to see if i can fix it. at this point any help would be appreciated.
I did notice that even though the phone wasnt turning on the phone was getting hot? (it wasnt connected to the charger obviously.)
when i did battery pull and leave it out it cools down. when i put it back in and turn it back on it gets hot after a while even though the screen and everything does not turn on.

Do this:
Pop out the battery and leave it for maybe 1 minute.
Then put the battery back in and see if the phone gets hot. If the phone does get hot skip passed 3 and 4.
Now assuming the phone doesn't get hot, plug it into your charger for about 5 minutes before turning the phone on. Try and get into Fastboot/Bootloader.
Once in your bootloader, just navigate your way to recovery and flash a new rom.
If the phone/battery gets hot it means its turned itself on as soon as the battery has gone and the phone isn't displaying anything. You should try just plugging the phone into the charger and turning it on. See if you get anything up on the screen. If you do then just jump into recovery and flash a rom.
Otherwise, if the screen always stays black regardless of what you do, send it in for repairs.

Aegishua said:
Do this:
Pop out the battery and leave it for maybe 1 minute.
Then put the battery back in and see if the phone gets hot. If the phone does get hot skip passed 3 and 4.
Now assuming the phone doesn't get hot, plug it into your charger for about 5 minutes before turning the phone on. Try and get into Fastboot/Bootloader.
Once in your bootloader, just navigate your way to recovery and flash a new rom.
If the phone/battery gets hot it means its turned itself on as soon as the battery has gone and the phone isn't displaying anything. You should try just plugging the phone into the charger and turning it on. See if you get anything up on the screen. If you do then just jump into recovery and flash a rom.
Otherwise, if the screen always stays black regardless of what you do, send it in for repairs.
Click to expand...
Click to collapse
yea it stays black no matter what i do,, but it does get hot though.

Farout.. you should really send it to a repair shop then. The reason why is because you can't do anything to the device without the screen on. You can try and hope for it to boot into HBOOT but you would have better luck sending it off on Warranty or to a phone repairs place.

Aegishua said:
Farout.. you should really send it to a repair shop then. The reason why is because you can't do anything to the device without the screen on. You can try and hope for it to boot into HBOOT but you would have better luck sending it off on Warranty or to a phone repairs place.
Click to expand...
Click to collapse
yae the replacement is already on their way

Haha thats brilliant. Don't brick this one lol.

Screen Replacement issues

I recently had a buddy get a screen replace from a place in the mall. The phone display and everything works, but one problem after all of that. It will not stay on and keeps bootlooping ect.... I did a factory reset and still no luck another weird thing is, when it is plugged in the battery will go from 80% down to barely nothing then quickly charges back up. The phone somewhat seems to stay on when it is plugged in. The phone started having these problems when the screen was replaced. Im confused. please help! Thanks!

sure its simple
pdubzzle83 said:
I recently had a buddy get a screen replace from a place in the mall. The phone display and everything works, but one problem after all of that. It will not stay on and keeps bootlooping ect.... I did a factory reset and still no luck another weird thing is, when it is plugged in the battery will go from 80% down to barely nothing then quickly charges back up. The phone somewhat seems to stay on when it is plugged in. The phone started having these problems when the screen was replaced. Im confused. please help! Thanks!
Click to expand...
Click to collapse
First thing first do a hard factory reset with the volume down and power button, not work then flash with lg flash tool the model numbers kdz all downloads and guides are posted. let it fully boot power down then fully charge, power up and down several times so the data files understand the new digitizer and resets all problems. Still dont work find screen replacement video via youtube once there whatch how to disassemble cause I am pretty sure it is one of the data cables or connections that is loose but you can never know with software and those are easier to do and less chance of permanent damage.
Or you can mail it to me and I fix her right up lol

[Q] Flashed ROM, worked perfectly, won't turn on now

So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?

NotRankin said:
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
Click to expand...
Click to collapse
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.

FoxyDrew said:
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
Click to expand...
Click to collapse
ok, I'll continue waiting, thanks for the info. I'll go ahead and flash CM11 and use that for awhile until HTC pushes their 5.0 out or if problems are fixed. Hopefully it won't take too much longer for the device to die...

2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.

NotRankin said:
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
Click to expand...
Click to collapse
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.

FoxyDrew said:
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
Click to expand...
Click to collapse
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?

NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
If theres still no charging lite? Possibly. You could try to charge the battery with a split charger. However thats last resort and can break your battery if it doesn't work.

NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
Or you could use your manufacturers warranty and send that baby back in for a fresh one. Claim a defect... Why? Because it is a defect. If you can't get it to boot with adb / rooted methods then their stock methods won't work nor detect anything. Besides, the worse they'll do is send your phone back the same way it got to them.
Also, if the others who ran into this issue could give feedback on if they modified screen resolution before the device kicked on CM12 that would be most informative.
Sent from my 710C using XDA Free mobile app

a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).

NotRankin said:
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
Click to expand...
Click to collapse
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.

FoxyDrew said:
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
Click to expand...
Click to collapse
So either I screwed something up or it was a screwed up phone in the first place (I'm inclined to believe this as it was frequently getting into a locked state where I'd have to force reboot it via the vol/power buttons). Guess I'll go for it, thanks!

Phone dead for no reason after years?

This entire forum is probably dead, but I'd like to ask anyway.
I've got the same problem as other people in this forum.
It has an unlocked bootloader, LineageOS 18.1 unofficial beta and it's rooted.
When plugging the Z5P in the charger, it doesn't turn on. I've removed the backplate and unplugged the battery and plugged the charger,
the phone LED blinks red with the off time of ~3-5 seconds. Previously the screen logo flashed for a very short time but now it doesn't even do that.
Now when I plug the charger in and then connect the battery the moment when the LED is red, the vibration motor reacts 3 times and the phone stays off.
Connecting to a PC and doing any steps above, the phone does not get detected by the PC, so obviously there's no way to use any recovery tools.
Is the Z5P finally dead/chip fried? Can I do something with a dead phone or the internal parts?

Vanta-Chan said:
This entire forum is probably dead, but I'd like to ask anyway.
I've got the same problem as other people in this forum.
It has an unlocked bootloader, LineageOS 18.1 unofficial beta and it's rooted.
When plugging the Z5P in the charger, it doesn't turn on. I've removed the backplate and unplugged the battery and plugged the charger,
the phone LED blinks red with the off time of ~3-5 seconds. Previously the screen logo flashed for a very short time but now it doesn't even do that.
Now when I plug the charger in and then connect the battery the moment when the LED is red, the vibration motor reacts 3 times and the phone stays off.
Connecting to a PC and doing any steps above, the phone does not get detected by the PC, so obviously there's no way to use any recovery tools.
Click to expand...
Click to collapse
If the motherboard is not totally dead then you could try the option with QPST tool to flash the stock ROM in download mode (QHUSB-9008) just search for, you should have a long curve learning to do so.
The device has to be detected this way, but it may work or not, depending on if the chip is really dead or not.
Vanta-Chan said:
Is the Z5P finally dead/chip fried? Can I do something with a dead phone or the internal parts?
Click to expand...
Click to collapse
In some countries is sold as spare.

SubwayChamp said:
If the motherboard is not totally dead then you could try the option with QPST tool to flash the stock ROM in download mode (QHUSB-9008) just search for, you should have a long curve learning to do so.
The device has to be detected this way, but it may work or not, depending on if the chip is really dead or not.
In some countries is sold as spare.
Click to expand...
Click to collapse
Yeahhh, phone still doesn't get detected on PC, not really turning on. It's probably junk now.

Vanta-Chan said:
Yeahhh, phone still doesn't get detected on PC, not really turning on. It's probably junk now.
Click to expand...
Click to collapse
To send it to download mode (EDL) you have to open the back cover and test point two specific pins from the motherboard.

I just wanted to say that I got the EXACT same issue. I installed LineageOS 18.1 about 4-6 weeks ago and when I wanted to play around with the phone again a few days ago it wouldn't turn on or charge as Vanta-Chan mentioned.
It would be interesting to know if this simply happened because the phone is old, and to be honest the battery was already very bad at this point OR if this is because of installing LineageOS.
Because to be honest, that made me really scared of installing Lineage on other devices... I was thinking about doing it on my main phone (Samsung Galaxy S10) in the near future, but this has left me really scared.

Reading the issues y'all are experiencing reminds me of my old Xperia Z3, didn't want to turn on at all. Vibrated a few times with no display... No charging, led blinking with charger connected but PC won't detect...
The fix for my part was changing the battery, which did make it work. So most likely the same case and it's the battery, and trust me. Those knock off batteries are trash, didn't show correct battery %, and died after a few days... So had to get a new "original" one, no issues with the battery till this day

Meitei said:
I just wanted to say that I got the EXACT same issue. I installed LineageOS 18.1 about 4-6 weeks ago and when I wanted to play around with the phone again a few days ago it wouldn't turn on or charge as Vanta-Chan mentioned.
It would be interesting to know if this simply happened because the phone is old, and to be honest the battery was already very bad at this point OR if this is because of installing LineageOS.
Because to be honest, that made me really scared of installing Lineage on other devices... I was thinking about doing it on my main phone (Samsung Galaxy S10) in the near future, but this has left me really scared.
Click to expand...
Click to collapse
Old devices turn to act erratically, unpredictable behavior can appear.
Just one thing I can sure you, I flashed LineageOS (although is not my preferable one) in an uncountable number of devices, never had an issue like that. If you follow all the steps indicated by the developer, you wouldn't have any troubles at all being on this device or another one.

Thanks for the replies... I might change the battery then, if it doesn't cost that much to let someone do it for me.

UPDATE:
I had some time today and somehow decided to play around with my Z5 Premium.
Now... I might should open another thread if necessary, should this get too much out of hand based on the threads topic, since my issue may be more different than I thought.
Previously I couldn't get it to turn on anymore after the battery died, charging as well wouldn't work and I would get that LED blinks for a short period of time when I would try to charge it.
So for whatever reason I decided to charge my phone again and at the same time pressing the power button + volume down... I tried that previously, but today it worked!
What happened was: I got the charging screen + red LED light over and over again and once I stopped holding the buttons it would start to boot again into a similar screen I got when installing LineageOS 18.1, with the only difference being that I had the battery symbol showing up as well as only seeing half of the screen (left side) since the right side was buggy only showing vertical black and white lines (which I had happened previously installing LineageOS after booting into TWRP)
My phone is now fully charged and I was able to turn it on and everything looks fine so far, except for the colors especially red which looks really dark since installing LineageOS 18.1
Now, this seriously has me worried about installing Lineage on my main Samsung phone. Because right now I feel like this has something to do with me installing a new OS on my phone...
Kind regards
Meitei
edit: grammar

I ain't no expert but there is a tool that you can buy and you plug it in your phone that will send you str8 to recovery mode or download mode, Idk if you are willing to pay like 10$ I think its not that mush to get it its a useful tool

HorrorBest said:
I ain't no expert but there is a tool that you can buy and you plug it in your phone that will send you str8 to recovery mode or download mode, Idk if you are willing to pay like 10$ I think its not that mush to get it its a useful tool
Click to expand...
Click to collapse
Probably you are referring to the EDL cable (it costs around 4 USD), I have it, and it worked with a defective device with a volume button not working properly. I have to add that on devices with locked bootloader it can be more useful that with devices with unlocked bootloader that have many more possibilities to send it to any mode you want without the need to open the back cover.

Meitei said:
UPDATE:
I had some time today and somehow decided to play around with my Z5 Premium.
Now... I might should open another thread if necessary, should this get too much out of hand based on the threads topic, since my issue may be more different than I thought.
Previously I couldn't get it to turn on anymore after the battery died, charging as well wouldn't work and I would get that LED blinks for a short period of time when I would try to charge it.
So for whatever reason I decided to charge my phone again and at the same time pressing the power button + volume down... I tried that previously, but today it worked!
What happened was: I got the charging screen + red LED light over and over again and once I stopped holding the buttons it would start to boot again into a similar screen I got when installing LineageOS 18.1, with the only difference being that I had the battery symbol showing up as well as only seeing half of the screen (left side) since the right side was buggy only showing vertical black and white lines (which I had happened previously installing LineageOS after booting into TWRP)
My phone is now fully charged and I was able to turn it on and everything looks fine so far, except for the colors especially red which looks really dark since installing LineageOS 18.1
Now, this seriously has me worried about installing Lineage on my main Samsung phone. Because right now I feel like this has something to do with me installing a new OS on my phone...
Kind regards
Meitei
edit: grammar
Click to expand...
Click to collapse
If the ROM in this case, LOS was built specifically for your device model, and it comes from a trusted source shouldn't damage your device in any way. How custom ROMs work with all the variants should make a difference on how they look, just, apparently. Anyway, check that your battery is not draining, or it is damaged in some way.

SubwayChamp said:
If the ROM in this case, LOS was built specifically for your device model, and it comes from a trusted source shouldn't damage your device in any way. How custom ROMs work with all the variants should make a difference on how they look, just, apparently. Anyway, check that your battery is not draining, or it is damaged in some way.
Click to expand...
Click to collapse
I got the ROM from the thread right here: https://forum.xda-developers.com/t/rom-beta-lineageos-18-1-for-the-xperia-z5-premium.4202705/
The battery isn't the best anymore, but I feel like it improved a little bit since installing Lineage.
The phone was charged to 100% on Saturday and currently, it's at 50%. And nothing looks damaged