Database Info

[Q] Can't access download mode and no backlight

One of my friend tried to root his phone using odin and a firmware for version 9023 while he has a Nexus S GT-i9020t. I've been looking for some hours, and I couldn't find any solution for that problems.
This post has similar symptoms, but still no answer: http://forum.xda-developers.com/showthread.php?t=1436199
Symptoms
- No backlight at all (seems to be a problem version amoled vs slcd, as I could read)
- Screen is upside down (but buttons, keyboard, etc still react correctly, only the screen display is upside down, so you get to have two phones next to each other to press the right buttons...)
- Can't get into download mode to flash using Odin and the correct firmware. When you hold both volume buttons and plug the USB cable, you get the first attached image. Green lines, nothing else.
What it can do
- Phone can get into the bootloader, but screen is very dim, as you can see in the second screenshot
- Phone can boot normally, you may take screenshots, place phone calls (while guessing numbers), receive phone calls, but the screen backlight stays off, so it's pretty hard to read anything. Tried to get to the display settings to play with the luminosity, without success.
- No problems using adb to send commands to the phone, or using fastboot to flash the device.
What i've tried
1. Downloaded original firmware image from Google, and tried flashing the device using fastboot. Tried 2.3.6 and 4.0.4 for Nexus S worldwide (i9020t) - over here: https://developers.google.com/android/nexus/images . Still no backlight.
2. Tried the One-Click Unbrick for Samsung devices. Installed drivers and everything, the tool return the result Success, but still can't access download mode, or fix the problem.
It looks like the graphic part of the phone is messed up, and i've got no idea on how this could be possibly fixed.
Any help would be greatly appreciated !

I think your AMOLED Screen just died or is going to die. If it is still under warranty, get it replaced. If not, look on ebay and buy a replacement screen. Its a do it yourself procedure. Or take it to a phone repair shop and they'll do it for you.

It's not under warranty anymore, it's 1 year and 2 months old.
I doubt the screen died, since problems started when he installed the wrong firmware. Can a bad firmware cause physical damage to the screen ?

xperia xz display(black screen) not working (randomly) help me.. please..

1.
First, the current situation is that the screen does not come on while the power is turned on.
If you look closely, the light of the screen comes out, but it is a black screen.
So when I press the power button several times, I sometimes see the screen once, and when it is bad, the screen keeps blinking only on the black desktop.
No matter what I did, it was not restored, I disassembled it, pushed the battery part for a while, then contacted me again, and the screen started to come out again! However, after about three hours, the symptoms began to appear again. Now I keep repeating this phenomenon and just use my cell phone.
2. ((First things I did.))
I used the flashtool to update my stock firmware. Soon after I knew the wrong thing, I put the firmware over again. I tried to get the firmware for my country. Then I was disappointed to see that the TTA-VOLTE I wanted was still not working. So I decided to install Android 9.0 (Pie) and install TWRP and install it as WIPE. It was the beginning of all these.
Since then the above symptoms have been manifested and the stock firmware does not work even if you do anything
please... save me... :crying::crying:

Galaxy S7 Frozen, stuck in Recovery Mode. Strange Android warning screens?

Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!

bigblkyj said:
Hey everyone, I'll start by saying I'm new to these forums, so go easy...
I've had an S7 (Verizon SM-G930V) for probably 3 years, recently it randomly glitched/locked up (screen had strange color bars through what I was looking at) phone restarted and then was stuck in a boot loop. It's never been wet or dropped hard and is in really good shape. I shut it off and attempted to re-start with the same results... Got a new S20+ so I at least have a device, but I'm determined to get the lost month on the old S7 back since I had a backup from early Feb.
I tried a new battery since that was mentioned, didn't change anything, however in messing with trying to get the phone to boot have discovered a few strange message screens and behavior...
1. Phone will eventually stop responding to key presses, have to pull battery connector, wait, then it will re-boot, but every time the blue 'Recovery Mode...' is displayed. If I touch nothing, it will boot and start 'installing updates' but eventually lock and restart. At one point it made it as far as the Verizon screen, then died.
2. I can get the phone to to into the recovery menu and it will respond to commands. I've tried restart normally, boot to safe mode, and shut down phone normally, all of which result in the same restart and recovery mode message and then the lock during the update.
3. I have successfully made it to the download mode screen a few times, but don't have the knowledge of what needs to be done there and which files I would need to upload to it to make that work. (phone was totally stock rom) It had recently updated to the latest version available from Verizon which I think was 8.0?
4. Now I have found a new error screen which I have not seen before... The little Android guy has X's in his eyes and a large yellow sign with ! in it says 'No Command' and then the phone restarts? It also during that finally responded to being plugged in via USB charging, however normally it shows no signs of charging other than being warm and actually charging the battery (verified with a meter)
5. When the phone is on, it gets warm quite quickly (it's still split open and the tin covers are warm, but not hot)
Hopefully someone can help out. I wouldn't say there's anything too critical on there, but there are some pics I'd really like to have back :crying:
Thanks everyone!
Click to expand...
Click to collapse
If what you've described is correct, all of the solutions involve flashing the stock firmware which will of course wipe the device.
Were your photos not stored in a folder on the SD card?
There is a chance you can recover the device using Samsung Kies with the emergency recover option but if you've encountered the "no command" screen it's not looking good.

Unfortunately I did have an SD card installed, but I normally kept my camera pics on the phone's memory, since I have had an SD card fail as well and lost everything on there.
So this took an unexpected turn yesterday pretty much right after posting this... I've been messing with the phone, unplugging the battery each time, and have managed to get into different menus which kept making me think that something still had to be working if I could do that. Well, after leaving the No Command message on the screen it magically booted into the Recovery menu with (finally) the option to wipe the cache partition, which I did and rebooted normally. Believe it or not, it booted normally and into the OS like nothing ever happened?!
I instantly plugged it into my PC and ran Smart Switch which started taking a backup! About 25% though the device restarted again and was really warm to the touch on the RF covers inside. Bummer...
So I figured heat was now the issue for some reason... I waited for it to cool and then reinstalled the SD card and figured, if I could get it to boot long enough, the SD card is a quicker transfer and I'd just use ES File Explorer to try and do a photo dump to the SD card and see how far it would get. It actually made it all the way through and gave me enough time to grab some other stuff before getting hot and restarting again.
I believe the overheating is being caused by my opening of the device though... Currently I have the antennas removed and the speaker so that I'm able to quickly access the battery connector (which BTW seems to be the trick here to this working) But inadvertently, without the larger wireless charging coil in place, it relieved the pressure on the motherboard and broke the thermal paste connection between the chipset and the copper heatsink (I didn't tear it down further to check, but I can hear the 'sticking and peeling' when you press down on it).
I think what I'm going to do is apply pressure with a chip clip or something similar (non conductive) and see if I can grab a backup again before it restarts. After the cache wipe the phone seems to understand that it's plugged in and charging now which is a new thing as well...
Sorry for the long winded posts, but if this at all helps even one person with the same situation as I have, maybe that'll be worth getting lost in here

Progressive Situation on screen

Hello guys! There is a progressive issue on my phone which i couldn't be sure of the source of it.
I was using my phone with enes' ultimate nougat romhttps://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-ultimate-nougat-s8-port-t3681259 for over a year now. It was working like a charm.
Then recently some horizontal lines started to show up. At full brightness lines are gone, but as i lower the brightness lines comes and covers almost all of the screen and after some time of usage with low brightness lines dissappear.
And a couple days ago while browsing on chrome suddenly all of the horizontal parts of screen started to shift up and down(like the url tab which is located up top shifted to the all the way down) then screen went black. After a day it opened by itself as if nothing happened, working fine. Later on same thing happened. I tried to open dowload mode and recovery, phone was responsive as it was vibrating and notification led blinking, but screen remained black and flashed with fade lines. Interestingly i am able to see my files on the computer and odin is detecting the phone.
I have searched about the issue but couldn't find a valid answer to this, some said it's the screen, some said it's the hardware(graphical unit), some said it's software. Can you guys give me your opinions? Thanks.
(btw i tried to upload firmware via odin but odin did not even pass setup connection step)

I will try to answer all the problems of XZ2 :)

Hi , i have working with more than 100 xz2 phones , i got many problems and fix it (google and xda) , so I think I can help you to fix your problem with xz2 asap if u ask me in this post
My exp :
Flash
Unlock
Root
and some small problems...

[deleted]

sinommo said:
Hi , i have working with more than 100 xz2 phones , i got many problems and fix it (google and xda) , so I think I can help you to fix your problem with xz2 asap if u ask me in this post
My exp :
Flash
Unlock
Root
and some small problems...
Click to expand...
Click to collapse
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.

mohhom said:
Hello,
My wife's Sony Xperia XZ2 Compact with model number H8324 has an issue with booting or maybe the launcher getting stuck in a loop after getting to the lock screen for a split second.
The phone seems to boot like normal and gets to the lock screen, we are even able to punch in one or two digits of the 4 digit pass code. Then it goes into a loop of the notification bar and back button flickering. From then on the phone is not responding except for the power button which brings up the normal "Turn off, Reboot, and Lockdown" menu. The issue just started out of nowhere yesterday morning and we haven't been able to fix it yet. We haven't done any rooting or custom rom flashing, it's running the official Sony software but it's out of warranty.
Here's a video showing the issue. The video shows the whole boot process but the link takes you to the last part after the logos.
We would love to get some files off it so if there is a way anyone can help us with that we'd prefer it over a hard reset.
Things we've already tried
Turning the phone off and on again
Unlocking the phone in the split second the lock screen works, this is just too short to swipe up and then put in four digits.
Rebooting the phone
Booting while charging
Booting into safe mode (this has the same issue)
Connecting the phone with USB to a pc, the phone is recognized by Windows, but it doesn't share it's filesystem with Windows.
Connecting the ADB to it, alas usb debugging is not yet enabled on the phone
Trying to get into recovery mode, we haven't been able to get into the recovery menu. Googling seems to indicate it might be holding volume up + power button when the phone is off but then it doesn't seem to do anything at all.
We're currently trying to run out the battery of the phone to see if that will resolve the issue on it's own.
If anyone has any idea, we would love to hear it.
Click to expand...
Click to collapse
I think u just need to reinstall rom file with newflasher and stock rom , did u tried it ? with newflasher newest version , u still can keep the personal files and flash stock rom for the phone , then i think this phone will run normal again
If u dont know how to do that , reply comment here , but u should turn off the phone to keep battery well , if u can't turn off the phone , try to press and hold volume up button + power button within 5 sec , phone will vibrate 3 times and totally off

Is there a way to get a stock recovery if somehow the recovery has been deleted?