So i recently got a free upgrade to a inc 2 by turning my og inc in under warranty for a blow speaker (for the third time) and i naturally rooted it and installed a nice miui rom. Now about a month later im out of town for work and the screen has died. The phone is still operational, but the screen is black.
I am wondering if this could possibly a firmware issue? i have tried pulling the battery and booting into recovery but the screen is 100% useless. the touchscreen still seems to work, i can unlock it and answer calls ect...
My hunch is that its a hardware problem, but i'd like to try and flash it back to stock if possible to eliminate the possibility of a rom issue.
Does anyone know a way to flash a rom onto it without the use of the screen?
Can i use the HTC sync tool to set it back to stock like i could with the OG incredible?
Any help is much appreciated, i'm pretty desperate here.
if it was me, I'd flash it back to stock using a ruu file, then do a warranty claim, cause then if it's a firmware/software issue the ruu will fix it. There's a thread somewhere around that has instructions to do that, give me a minute...
Edit -found it! Here ya go- http://rootzwiki.com/topic/1579-how-to-restore-to-stock-from-alpharevx-incredible-2-vivow-only/page__st__53
Sent from my Incredible 2 using xda premium
ok, so my new issue is that if i flash the ruu, and the screen still doesn't work, i'll be stuck at the setup wizard right? then i won't even be able to use google voice to make calls from my laptop. i guess ill have to wait till i get home, this would be so much easier if my pos nextel work phone had service out here in wyoming.
Yea, that's a tough one, I definitely wouldn't flash an RUU for the exact reason you bring up.
One option, although it isn't without it's own challenges, would be to try to install a VNC server on your phone, so you could then connect to and use it through a desktop computer. You could probably install it easy enough through the Android Market web site. Here's one: https://play.google.com/store/apps/details?id=org.onaips.vnc
If you download the Android SDK (http://developer.android.com/sdk/index.html), connect your phone to your computer, open a command prompt and run ddms, it'll bring up the Dalvic Debug Monitor. Here, you can go to Device>Screen Capture and it'll bring up a window showing the screen of your phone. There's a refresh button which will refresh the screenshot. It'll be a little hit or miss, but you should be able to reference the screenshot to tap on your blank screen to open the VNC app, hit the start server button, and then see what IP/port it's listening on.
Once you get the VNC server running and connect, you should be able to use the phone fairly easily, although if the screen is dead even during boot (no initial boot screen, no display in h-boot) it would seem like a hardware problem and there's probably not much you can do about it.
ChrisDDD said:
Yea, that's a tough one, I definitely wouldn't flash an RUU for the exact reason you bring up.
One option, although it isn't without it's own challenges, would be to try to install a VNC server on your phone, so you could then connect to and use it through a desktop computer. You could probably install it easy enough through the Android Market web site. Here's one: https://play.google.com/store/apps/details?id=org.onaips.vnc
If you download the Android SDK (http://developer.android.com/sdk/index.html), connect your phone to your computer, open a command prompt and run ddms, it'll bring up the Dalvic Debug Monitor. Here, you can go to Device>Screen Capture and it'll bring up a window showing the screen of your phone. There's a refresh button which will refresh the screenshot. It'll be a little hit or miss, but you should be able to reference the screenshot to tap on your blank screen to open the VNC app, hit the start server button, and then see what IP/port it's listening on.
Once you get the VNC server running and connect, you should be able to use the phone fairly easily, although if the screen is dead even during boot (no initial boot screen, no display in h-boot) it would seem like a hardware problem and there's probably not much you can do about it.
Click to expand...
Click to collapse
Yeah i think i'm hosed, i have no screen at all, i can't get the ruu to run, it comes back saying i have the wrong device. i guess im just gonna send it back and hope they don't notice.
captainlovesac said:
Yeah i think i'm hosed, i have no screen at all, i can't get the ruu to run, it comes back saying i have the wrong device. i guess im just gonna send it back and hope they don't notice.
Click to expand...
Click to collapse
Where is it indicating that it's the wrong device if you have no screen?
Please Delete Post
I ran into a similar problem with black screen over the weekend.
However my phone was not rooted.
This is how it happened.
I was using my phone then I saw the screen flicker once or twice, then it went black.
I pulled out the battery and powered up again.
The phone vibrated, and after a while the four bottom buttons light up.
The volume keys work and I could receive incoming calls, but the screen just stays black.
One thing to note is that my pocket was a little wet before I pulled out the phone to use.
Also that I did use my phone for a good 5-10 mins before it went black.
What I am trying to determine is if it is a software issue or hardware.
Are the bottom button lights separate from LCD screen, so that even if they light up it could still mean LCD is bad?
Any help would be appreciated, thanks!
Related
I've seen a lot of these threads on random android forums, never with much resolution, which is frustrating.
My power button has stopped working entirely. I took it into the Sprint shop, they spent an hour with it, came back out and said they could find no reason it shouldn't be working. It's an obnoxious fix, but I downloaded "No Lock" from the marketplace and set the screen to shut off after 15 seconds. Now I press a volume key to turn on my screen...
Now, when it gets annoying is when I went to install Cyanogenmod 7 tonight. The power button obviously doesn't work. Widgetsoid's reboot button is ignored entirely if I do Shut Down, Reboot, Bootloader, or Recovery. It's A-OK with Hot Reboot. So the only way I've gotten into the bootloader to wipe/install CM7 is to pop out the battery, hold VolDown, and put the battery in. Peachy. But once I'm into the bootloader, now not only does power (which is now my "enter" button) now work, but the volume buttons are unresponsive as well. So no scrolling.
I'd love to call up HTC or Spring and see what I can do about a replacement (which might not even happen, I don't have a warranty), but I can't un-root the device to send it in.
Any insight you guys have would be greatly appreciated...
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
END_OF_FLESH said:
Is there an SDK or something that would allow me to remote control the phone using my computer via USB? I'm completely at a loss here.
Click to expand...
Click to collapse
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Samzebian said:
I believe you are referring to adb?
and you can unroot via adb, just search around, I'm sure you'll find something on it.
btw, does Sprint know you rooted your phone? if they didn't find out, then you still have a warranty
Click to expand...
Click to collapse
Yeah, I'm just not as familiar with ADB as I'd like to be.
Not so much looking to unroot, as reload HTC Sense so they don't think to look haha. And yeah, when I brought the phone in today it was very obviously modded. They restarted it and the Cyanogenmod 6 flash screen came up. The guy looked a little confused. He was more than willing to help out, but I'm not so sure it would be the same if I sent it in. They definitely wouldn't replace it.
Alright, so I have ADB up and running with no issue. Got it to give me my device's serial #. At this point, how do I hijack the phone's bootloader and force it to wipe and install the ZIP of CM7 that's on the SD card?
Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.
You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.
Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin
Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.
Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.
Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.
I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.
"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.
Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.
15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.
On Friday night, My phone was in the breast pocket of a blazer that got very damp in an unexpected downpour. The phone continued to work on Friday night as far as I recall (I wasn't using it much, but I'm pretty sure I did use it some). When I woke up on Saturday morning, it appeared to be off and wouldn't turn on. I pulled and replaced the battery and still got nothing. I put it on the charger, but I had to run out, and I ended up being gone all day.
When I came home, the power button still wouldn't turn on the device. I pulled the battery and replaced it, and the Google screen came on, then the CM10 boot animation. When it got to the pin screen, however, the screen wouldn't respond to me entering my pin. Then, after a minute, the screen turned off, and the power button wouldn't turn it back on. I did a battery pull. Again, replacing the battery brought up the google screen, the CM10 boot animation, and the pin screen. But, again, the screen was unresponsive, and the power button did nothing when the screen went off.
I took it apart and left it alone all day Sunday. On Monday morning, I tried again and got the same results. I went and picked up a bag of white rice yesterday and left it in there last night and all of today. Still, I've got the same outcome. Buttons and screen are unresponsive.
So I'm left with a couple of questions:
First, is there anything else that can be done? This seems to me to be water damage. Does anyone have any suggestions for possible solutions?
And second, I keep getting text messages. Is there any way to pull those messages using the Toolkit or adb or anything (I'm pretty inexperienced with adb)?
Any help would be great. I'm stuck in China without a phone right now, which is a pain in the butt. I'd like to revive this, and I don't want to go track down a new phone until I know this one is sunk. Thanks for your help.
install android-sdk
run adb server on the host
connect your device to pc (feed it naked drivers manually found on dev section, if you're on windows and device manager shows unknown device)
type: adb devices
q: do you see your device listed? (should be lots of numbers and letters)
if it doesnt even recognizes that it has been plugged in, then your usb connection went down the drain, nothing else you can do
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
ejchis said:
My computer recognizes the device, and I'm able to do some things using the toolkit, such as a manual reboot, so I think my usb port is intact.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
bk201doesntexist said:
then i would reflash google factory images per this guide and return the device. unless you want to DIY (open the device, etc etc)
Click to expand...
Click to collapse
And you would expect this to resolve the screen and buttons being unresponsive? This is interesting. Is it possible to pull my messages beforehand?
Sent from my Nexus 7 using Tapatalk 2
My Captivate Glide's screen does this whenever I turn it on:
I didn't drop it or get it wet, it just started doing this randomly.
I live in the UK and ordered the phone unlocked over eBay so I can't take it into an AT&T store, sadly.
Do you guys know if there's anything I could do myself or anything someone more experienced in repairing mobile phones could do to fix the screen?
This is bearing in mind that not many people over here have seen one of these phones though.
Any help would be massively appreciated. Thanks guys.
you was using still GB right? just flash ics via odin, with one click or with a tar file
This is UCLH2 without one click
http://androidromupdate.com/2012/09/...ota-stock-rom/
And here is the latest version with bug fixes (like keyboard light)
http://androidromupdate.com/2012/11/...ptivate-glide/
and there is for one click
http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
i think that only one click wipe your internal storage. but is the bes (in my opinion). try it, dont have anything to lose
No, I already updated it to ICS. Should I reinstall it? Will that fix the screen? How will I manage to do it with the screen all messed up?
if you can put in download mode, then you can. Its weird because i only see that problem with GB. Put in download mode and then reinstall
I just tried putting it into download mode but I get the exact same thing.
Thats weird, the problem is weird because it never happen to me in download mode, maybe you can try it without battery, or let the phone without battery a couple of hours, etc.
Dont Know what you cand o, because if you cant enter in download mode, you will be no able to flash ICS
Hrm... that purple splotch in the bottom left of the screen doesn't look so good... Almost appears as if it had been dropped on that corner at some point in the phone's history. I am tempted to say that is a hardware issue, though. Reminds me of when the flex cable for my laptop's display started shorting out many years ago. Might be repairable, but, might be a costly repair depending on what all needs to be replaced. I can't imagine replacing the software on it will do much, though, sorry to say. You could give it a shot, you can verify if your phone made it into download mode without the display by loading up odin and seeing if it detects under that, and then running the one click install (or any other since you'd have odin running anyway) but I wouldn't expect much.
If you're not getting the Samsung/Rogers logo screen, you're done. Either the screen is physically damaged, or the bootloader is corrupt. There's no saving that one, sadly.
yes, try what Artemis-kun say. put in download mode and connect, and see if odin detected. Or maybe just turn on the phone and wait a little, then try to call to your phone, if the phone ring or appears to be on, then is a hardware problem.
But try what Artemis-kun, maybe you have luck
PD: now i see better the image and it seems little different from what it happens to me. if you turn on, inmediatly happen that? or screen banish slowly?
AW: [Q] Screen's gone fuzzy and weird - need help please
There should be a cable, connecting the hardware to the display. Maybe it loosened, you should check out the video of a guy tearing his glide apart, hopefully youll find something to repair there.
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
Hey guys, you'll be glad to hear I finally fixed my Glide by installing a new screen assembly from Repairs Universe.
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
foofiebeast said:
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
Click to expand...
Click to collapse
Hi,
The best way to rule out any software problems would be to flash the latest 6.2.B.1.96 ftf using Flashtool. So, first make sure that the phone has enough charge, then press and hold the volume up+power combination until you get three vibrations. Then press and hold the volume down key and simultaneously connect the USB cable when Flashtool prompts you to. Once the flashing is complete, disconnect your phone and turn it on normally.
Regards,
abcdjdj
Sent from my LT26i using xda app-developers app
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
foofiebeast said:
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
Click to expand...
Click to collapse
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
sudhindrakv said:
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
Click to expand...
Click to collapse
Well there is a slight problem.
The phone does not have an unlocked bootloader yet, so I can't use flashtool. It has been flashed back to stock using the method I mentioned above. I have just finished installing ADB because (bear with me please) there is no way to turn the phone into fastboot mode without turning it off (I cannot currently turn it off because I can't see what is happening on the screen and don't remember how this phone works when you hold down the lock key to turn it off). I can perform a hard reset, but no way to just get it to turn off entirely.
So I thought I could use adb to shut it down, but adb won't work unless I have debugging enabled, which again I can't do unless I could basically just blindly navigate the menu to those buttons.
Although if I wait until the phone is fully dead then I can hopefully get it into fastboot mode, but that only gives me one chance. Plus it has a full charge right now, so that's going to be awhile.
Any suggestions?
I can get it in to fast boot if I'm quick, but I still can't enable debugging beforehand so its semi worthless.
I've been trying to watch videos to see where the button placement is to navigate through the menu to blindly enable debugging, but I can't seem to figure it out. It also doesn't help that I have no idea what version of android is now on the phone. I used the mac sony bridge app to restore the phone, but i'm not sure if that set it back to stock stock, or what version of android it set it to.
I am also now even more confused because I connected the phone to the computer and when I browsed it, all the pictures I took were still there...which should have been wiped when I restored it with sony bridge...
figured out it was 4.1 and watched review videos until i found one that showed the menu layout (although now I realize google images would have been more helpful).
Now going to see if I can get the bootloader unlocked.
I still feel like flashing 6.2.B.1.96 isn't going to do anything, because I assume that is what the sony bridge app flashed to it. Also I don't see where you are talking about that the issue I am having was a known issue, if you could point me in that direction that would be very helpful.
EDIT: Actually I'm not sure I enabled debugging after all, as when I do adb devices, no device is listed as running, just a blank space. Though I'm still not convinced doing the above would do anything, as it is basically what I have already done, just with flash tool as opposed to the official sony route.
Anyone have any ideas? I got a torx 6 and opened the phone, checked the connection between the motherboard and phone and it is fine. Screen is still having same issue.
I would be happy to just buy a replacement part for it, but i have no idea what part is messing up. Is it the display (the touch works fine) or is it the motherboard (it seems weird that it would be this because the phone functions completely normally, I even accidentally answered a call yesterday).
If i was to try and replace the LCD (or whatever it is) would I have to replace the digitizer as well? At which point it would make more sense to just sell the phone for parts I suppose.
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
dkconor said:
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I'll go ahead and try that out, but is there really much of a point do you think? Considering I've technically flashed the phone back to stock using the official software, why would it be any different doing it this way?
I am asking honestly btw, not trying to sound rude. I'm thinking it is more of a hardware failure, i just have no idea what part exactly is failing.
The phone itself works totally 100% fine, the touch works totally 100% fine, the only thing that is not happening is the data getting to the screen and displaying. The screen just flashes white for a second and then fades out (as you can see in the youtube link). Or it flashes a solid block of white at the top in the middle and faded white the rest of the way down and then it slowly all fades out (or disappears immedaitely if i press the lock button. The buttons all work fine (physical and touch) and i can navigate around the phone, albeit totally blindly.
This is really frustrating, and I'm pretty disappointed to see how sony had no interest at all in helping me resolve this situation.
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
UchihaDareNial said:
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
Click to expand...
Click to collapse
....right i know, but why does that matter. Why would reflashing my phone help at all at this point. Did you even read my post?
Listen to us
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
424aca said:
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
Click to expand...
Click to collapse
Hi,
because I could not follow the advice from the first user because the bootloader is locked. The second person gave me the advice, but honestly it seemed like pretty pointless advice. I don't understand how it is "obviously different" if it is literally flashing the same firmware (at least the first advice was that). I don't think it's that strange to ask why it would be any different.
To me it sounds like I had a broken window in my house and I asked someone how to fix it. I bought the replacement glass from store A and it didn't fit. I asked for help and someone pointed me to the exact same item at store B and said that surely it would work. Do you understand why this could be confusing? I feel like about half the time people give help on XDA it is very general and people are just looking for "thanks"...
I'll definitely try this though if you think there's a chance that it might work out differently. I'll try and get it set up tonight, thanks for the encouragement, I understand I probably sound stupid, just trying to figure out what to do.
Also, I assume this flash tool won't work if USB debugging isn't enabled. As I've said in previous posts, I can click things just fine, but because I can't see what I am doing, I don't have way of knowing where to click on the menu.
Does anyone have their phone set up with this version of android still. If you could take screen shots of each click to make to get to the dubugging box (and if there is a confirmation box) i would greatly appreciate it. I only had the phone for a week before this randomly happened, so I hadn't thought to enable debugging yet, as I hadn't even thought about custom firmware yet.
EDIT: Or even just a picture of what the screen that comes up when you long press to shut the phone down. I have no way of turning off this phone right now without just waiting for it to run out of battery.
Holding down the power button for a long time does nothing, holding vol up and power restarts it, but I need a way to turn it off. If i hold the power button for like a second so instead of locking it, the menu comes up, I just can't seem to find the freakin button for power off.
(please remember I can see nothing on the screen, it is just blank).
flashtool does not need debugging when you doing the actual flashing
to turn off the phone
SIMULTANEOUSLY hold down
Power+ Vol up + Vol Down (AT THE SAME TIME)
wait for about maybe less than 25 seconds and you will experience THREE short consecutive vibrations
at this time...the phone is off
then you can begin the flashtool method