Related
My Epic's screen turned black yesterday for no apparent reason however the touch screen still works...
if i touch and scroll the lock up it still makes the sounds and i can guess were to touch to turn my alarm off on the black screen and that works, as all the buttons! i just cant see the screen anymore,
i did not install anything new, last thing i remember doing is just taking a picture. now i have a working phone with a black screen how do i fix this?
also, i cant even see the vol down camera power screen
help please
mrose61692 said:
My Epic's screen turned black yesterday for no apparent reason however the touch screen still works...
if i touch and scroll the lock up it still makes the sounds and i can guess were to touch to turn my alarm off on the black screen and that works, as all the buttons! i just cant see the screen anymore,
i did not install anything new, last thing i remember doing is just taking a picture. now i have a working phone with a black screen how do i fix this?
also, i cant even see the vol down camera power screen
help please
Click to expand...
Click to collapse
Can you get into download mode??
With the phone off .. Press 1 (on the keyboard) and power. If so, maybe try to odin back to EC05 stock
http://forum.xda-developers.com/showthread.php?t=1027904
good luck
If on boot after pulling battery it is still black and download mode shows nothing, and you have tried Odin (it works but you see nothing still) I am afraid you need to head to the Sprint store.
kennyglass123 said:
If on boot after pulling battery it is still black and download mode shows nothing, and you have tried Odin (it works but you see nothing still) I am afraid you need to head to the Sprint store.
Click to expand...
Click to collapse
Update: after ltting my phone sit on the charger for about 3 hours it came back on
BUT it went right back to the previous (working but all black screen) problem wen
i made a call which i now remember is what triggered it yesterday
I just tried getting into download mode and it did not work or show up
anyy further suggestions? if not can i ask the sprint store 4 help if i rooted my phone and unlocked it for boost?
PS. (i been making outgoin calls for months now n this never happened even with it rooted & inlocked)
thanx 4 taking the time to answer my questions
mrose61692 said:
Update: after ltting my phone sit on the charger for about 3 hours it came back on
BUT it went right back to the previous (working but all black screen) problem wen
i made a call which i now remember is what triggered it yesterday
I just tried getting into download mode and it did not work or show up
anyy further suggestions? if not can i ask the sprint store 4 help if i rooted my phone and unlocked it for boost?
PS. (i been making outgoin calls for months now n this never happened even with it rooted & inlocked)
thanx 4 taking the time to answer my questions
Click to expand...
Click to collapse
try to odin to ec05 stock ... leave your phone again for a while and see when you get your screen back if you can get to download mode and odin that stock rom ... this will allow you to see if it is something up with a rom you're running.
if it does it then, you'll be at stock so when you go to the sprint store; it won't be an issue.
jdelano said:
try to odin to ec05 stock ... leave your phone again for a while and see when you get your screen back if you can get to download mode and odin that stock rom ... this will allow you to see if it is something up with a rom you're running.
if it does it then, you'll be at stock so when you go to the sprint store; it won't be an issue.
Click to expand...
Click to collapse
I agree Odin back to stock is your best option and if that dosn't work you probaly stuck with a black screen!
Yes, if you got it to come on once by leaving it you should be able to do it again and Odin before making any calls.
I had no choice but to take it to the sprint store
they fixed it !!!
thankx again guys 4 all ur help!
mrose61692 said:
I had no choice but to take it to the sprint store
they fixed it !!!
thankx again guys 4 all ur help!
Click to expand...
Click to collapse
great news, glad you have a working Epic again.
mrose61692 said:
I had no choice but to take it to the sprint store
they fixed it !!!
thankx again guys 4 all ur help!
Click to expand...
Click to collapse
Hey, I know this is an old post but I have an old Epic I'd like to see if I can trade into for credit towards a Galaxy S III but I'm having the exact same problem as described here:
Softkeys light up, screen hepatic feedback "buzz" can be felt, can swipe to unlock and answer a call based on blind-memory of what to swipe but other than that, the screen is completely black. Not black as in lit up but devoid of any other color except black, but gone dark.
If it weren't for the softkeys being lit, I would assume the screen were either broken or disconnected from the motherboard somehow. There are no cracks in the screen. Phone has seen better days for sure but the screen is intact and all functions were working perfectly before it simply...blipped off in front of my eyes.
I've tried doing as you did: charging it for 3+ hours and seeing if that worked at least temporarily. No go.
Assuming our two phones were experiencing exactly the same issue, can you tell me when you had it repaired, if the issue was a hardware or software issue? If hardware, did they have to replace the screen? or was it merely not connected properly somewhere?
If it was a software issue, how did they repair it? I'm assuming I can, in fact, get the phone into download mode, but without a visible screen, I can't boot off of a zip file or see if any of my actions are successful. Can't be sure I cleared the caches properly before I proceed, etc.
Phone was last running toadlife's CleanGB prior to the FC09 update and I'm pretty sure, prior to EL30 (I can't remember but I'm pretty sure it was).
Again, I know this is old but any feedback would be appreciated.
navkat said:
Hey, I know this is an old post but I have an old Epic I'd like to see if I can trade into for credit towards a Galaxy S III but I'm having the exact same problem as described here:
Softkeys light up, screen hepatic feedback "buzz" can be felt, can swipe to unlock and answer a call based on blind-memory of what to swipe but other than that, the screen is completely black. Not black as in lit up but devoid of any other color except black, but gone dark.
If it weren't for the softkeys being lit, I would assume the screen were either broken or disconnected from the motherboard somehow. There are no cracks in the screen. Phone has seen better days for sure but the screen is intact and all functions were working perfectly before it simply...blipped off in front of my eyes.
I've tried doing as you did: charging it for 3+ hours and seeing if that worked at least temporarily. No go.
Assuming our two phones were experiencing exactly the same issue, can you tell me when you had it repaired, if the issue was a hardware or software issue? If hardware, did they have to replace the screen? or was it merely not connected properly somewhere?
If it was a software issue, how did they repair it? I'm assuming I can, in fact, get the phone into download mode, but without a visible screen, I can't boot off of a zip file or see if any of my actions are successful. Can't be sure I cleared the caches properly before I proceed, etc.
Phone was last running toadlife's CleanGB prior to the FC09 update and I'm pretty sure, prior to EL30 (I can't remember but I'm pretty sure it was).
Again, I know this is old but any feedback would be appreciated.
Click to expand...
Click to collapse
Hm, so you're saying download mode or recovery mode open up but with a black screen? But it still reads touches? My guess is it's hardware, a loose connection to the screen.
Yeeeeah, good luck towards funding your S3 purchase.
Sent from my SPH-D700 using XDA
I'm having this issue have my phone was dropped yesterday, so I'm quite sure it's a hardware issue.
I have two questions: can somebody be so kind as to give me the button sequence for how to make a nandroid of my phone? I have CWM 5.0.2.7 without the 'one confirm' option. That would be awesome. Also, is anyone familiar with taking the phone apart and perhaps how to fix this issue?
chillywings said:
I'm having this issue have my phone was dropped yesterday, so I'm quite sure it's a hardware issue.
I have two questions: can somebody be so kind as to give me the button sequence for how to make a nandroid of my phone? I have CWM 5.0.2.7 without the 'one confirm' option. That would be awesome. Also, is anyone familiar with taking the phone apart and perhaps how to fix this issue?
Click to expand...
Click to collapse
A guide to take it apart is here:
http://forum.xda-developers.com/showthread.php?t=1569701
and steps to nandroid
3 finger salute for about 5 seconds
toggle down 4 times hit cam button 2 times
tazfanatic said:
3 finger salute for about 5 seconds
toggle down 4 times hit cam button 2 times
Click to expand...
Click to collapse
Thanks tazfanatic. I tried the backup procedure and it didn't seem to work, and I think I actually have CWM 5.5. Is the procedure any different?
chillywings said:
Thanks tazfanatic. I tried the backup procedure and it didn't seem to work, and I think I actually have CWM 5.5. Is the procedure any different?
Click to expand...
Click to collapse
not sure 5.5? is that the touch version?
tazfanatic said:
not sure 5.5? is that the touch version?
Click to expand...
Click to collapse
CM9 version.
Sent from my PantechP4100 using xda premium
kennyglass123 said:
CM9 version.
Sent from my PantechP4100 using xda premium
Click to expand...
Click to collapse
Oh i have cm9 that is the direction I gave thought cm9 came with 5.0.2.7 my bag.
tazfanatic said:
Oh i have cm9 that is the direction I gave thought cm9 came with 5.0.2.7 my bag.
Click to expand...
Click to collapse
Indeed. I'm running CM9 beta 2, and I'm pretty sure it came with 5.5. However Taz, I believe if you boot into recovery from ROM Manger or the power menu, it still takes you into your previous recovery version (such as 5.0.2.7). Or vice versa. I don't remember. To my knowledge, this is has something to with the switch to MTD, and the devs just have reroute that command.
But regardless, I'm not getting a new backup on my SD card, so I'm pretty sure I'm on 5.5. Kenny, do you know if there's a different button sequence for 5.5?
5.5 is the same. I would remove the battery to make sure it is powered off. Put the battery back in, hold camera, volume down and power in that order (making sure power is last) for 5 seconds. wait 20 seconds to make sure it booted into CWM 5.5. Then volume down 4 times then camera twice. Depending on how many apps you got I would wait 30 minutes before pulling the sd card to check in clockworkmod\backup directory for a new file with current date code.
(Tittle changed from *Phone won't boot with sdcard inserted*)
I woke up this morning and my phone was just dead over night. I thought well the battery just drained but no. First it wouldn't charge, no red led lighting up on the power button. After 15 min. in the wall charger and no sign of charging i hooked it up on my netbook. About five min. went on and then the red led shined and i thought yes and tried booting but just a vibrate once and a black screen.
I was running latest 4.0.A.2.368, rooted, unlocked bl, doomlord's kernel and @thomassafca's samsung theme when this happened.
Tested fastboot mode and flash mode all good there, blue and green light.
Then i re-flashed doomlords kernel and it rebooted to the point of *sony ericsson* on the screeen and went black and then the charging icon and orange led.
Took out the battery and inserted it again and booted up. Again only vibrate once and then black screen.
Then flashed kernel.sin with flashtool, still the vibrate once and black screen.
So i was a bit lost and took out sim and sdcard and flashed 4.0A.2.368 ftf file posted by @thomassafca and it booted fine. Then i turned it off and inserted the sim and booted up. It booted just fine. Then inserted the sdcard and again vibrate once and black screen.
Then formated the sdcard extFat still no boot, tried Fat32 no boot, tried a card from my old nokia wich should be formatted correct since it also run on a linux base (maemo) no boot.
I'm a bit lost on what to do to make my phone boot with sdcard again.
Have been working with no issues at all since i flashed the new firmware/unlocked bl/flashed kernel/rooted.
Any help will or if someone could explain what happened will be great
Regards Dousan...
e: Ok a slight change in this. The phone when turned of won't boot again unless i take out battery and insert again. When booted into the phone i inserted the sdcard and mounted it and now it boots with the sdcard, but still the same issue of having to take out the battery to boot when turned off?
e2: Tried adb reboot and it seems to go in a bootloop. It connects to the pc and disconnects (windows sound plinging connected disconnected) and i can adb devices and a connected device number appears after the first pling and after the second pling there's no device to be found with adb and then it just goes on and on till i disconnect and pull the battery and boot? All this is with a black screen not even *sony ericsson* appears.
e3: Reflashed it with the latest fw and without pulling battery it booted right up and i thought, yes, problem solved. Went through setup and then turned it off and booted the phone and still vibrate once and a black screen. Pulled out battery and botted again and still vibrate and black screen? So pulled it out again and sdcard and it booted up fine. Inserted the sdcard when on and mounted it and it works, but still the boot problem?
After the reflash the vibrate felt different, stronger, and after i pulled the battery it's weaker.
e4:Flashed doomlords kernel again and rooted, still same issue?
e5: Solved problem by flashing doomlords kernel v2 for fw 4.0.A.2.368. After flashing it booted with the kernels new boot txt and then it turned off and the charging icon showed. Then booted into cwm and wiped dalvick cache and battery stats. Then rebooted from cwm and it booted up. To make sure problem was resolved I tried 2 times in a row to reboot with quick boot and it booted without me having to pull the battery Thanks all for your suggestions
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
AndroHero said:
Try going back to .145, see what happens. Flash the .tft file so you get the older baseband. Worth a try
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
Cheers mate for the surgestion, but that was a no go, didn't help
Back on 4.0.A2.368/unlocked/doomlord kernel/rooted... With a reboot problem
Regards Dousan...
Could be related to the doomlord kernel?
Sent from my R800
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Deoxlar said:
Probably fried something from Overclocking too much... Your incident is isolated too..
Sent from my XPlay using XDA App.
Click to expand...
Click to collapse
Not likely as i only OC'ed to 1400 the first feew days i had the kernel and then 1200 and when it happened stock clock.
My incident is isolated and your point is?
@captain67, yes it might be related to the kernel, could be?
Regards Dousan...
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Dousan said:
e: would there be a point in booting into cwm and wipe dalvik cache, wipe data/system and battery stats and then re-flash 4.0.A.2.368?
Click to expand...
Click to collapse
And it turned out that there was a point to it, problem solved
First post edited (e5
Regards Dousan...
Had the same problem
It was solved by magic though
Sent from my Xperia PLAY R800i using XDA App
And then the problem reappeared and this time i couldn't fix it myself and has just gotten my play back from service today (one and a half week they had it). It turned out to be some hardware problem and i've got a new screen, top cover and some other stuf.
Flashed the latest FW and locked the bootloader before handing it in and just told them what happened. Woke up and turned the device on and it froze and then it turned off with the backlight on. Tried rebooting but just a single vibrate and then a black screen.
They fixed my issue but created another. The volume button is now broken and i have to go back tommorow for a second time. Just booted the phone this evening and wanted to hear some music, but couldn't turn up the volume without pressing a pionty thing on the rocker. Down works fine. Bit annoying that a broken volume button can leave the service place, that should've been seen by the service person in the shop before it was ok'ed.
The screen is nice and crisp and the old one had a backlight issue i just lived with... untill now
Regards Dousan...
So a little update on this:
As i said they broke my volume button while repairing it for the stuff i wrote about above (didn't want to turn on).
It took me a week to go back with my play and in the meentime i descovered that it would randomly turn off during the night and wouldn't turn on unless i pulled the battery and charge it untill the charging symbol showed on the screen. It would then boot and first i thought it was the battery that was drained, but when on the lockscreen it showed that there was plenty of juice on. One time it was 35% and another it was 62% and no way it could've charged that much in 1-2 min.
Another thing i descovered was that when turned off it wouldn't turn on again unless i pulled the battery.
Anyway i went to pick it up yesterday and here i saw that they've broken my R-trigger Those idiotic service people even ticked of a box on the service papers that they've checked that all buttons where working (i don't think so, slackers). They did this on both occations
My play had no juice on it so i wasn't able to see if they had fixed my problem about not being able to reboot without pulling the battey and the random switch off's. Further more the service papers that came back with the phone didn't mention it at all? They did fix my volume button or atlest it seems they did as i couldn't turn it on and check if it did actually work.
So once again i'm without my play, but this time they're processing it express
Regards Dousan...
As long as you can use your phone,its all good
Cat_On_Droid said:
As long as you can use your phone,its all good
Click to expand...
Click to collapse
Yeah i know, I'd rather have them fixing it though, than having a fualty device. In the end it might go to SE and let them see if they can fix the issue. Hope not, don't want to be without my play once again Got the iches for gaming and now EA got free games, bummer
Regards Dousan...
Well just need to vent a little.
Starting rant:
So I got my phone back today for the third time. They did fix the R-trigger they recked the last time it was in for service, but they didn't fix my issue with the random rebooting/turning on without pulling the battery.
They claim it worked fine before shipping it, but when i unpacked it and let it charge enough to power on guess what it didn't turn on i had to pull the battery to get it to turn on lol They shipped it without checking if they fixed it. Hell i don't even think they tried at all cuz then they would've cought it straight away. They're full of BS and when googling them and reading their trustpilot it's also full of dissatisfied customors with the same type of problem as me, no fixing or pour fixing or even more breaking of the device or simply lieng it was water damaged
Hey that sound's familiar to me, not fixed and more broken, those C*NTS.
I'm pissed and nothing i can do but a claim with the place i made the purchase.
Rant ended
Regards Dousan...
End of story...
Well the last update on this.
I made a claim with cdon.com where i bought it and sent it of to their service center for repair and once again it was returned non repaired. Still wouldn't turn on without pulling the battery. Then they sent it of to SE and they couldn't fix it either and sent a new device to cdon.com, but i chose to get my money back instead of a new device.
The cons of this device ended up being more than the pros. Relly liked this device though and what it was supposed to've been. I was just not the big gamer i used to be and mostly played RB6 online and found the lag of analog touchpads support in fpse annoying and psxperia converter tool didn't work with the games i liked to play.
Anyway it was a fun ride while it lasted and mostly a friendly helpfull crowd I encountered here in the play sub forum. Must say that it has been the best forum I've been submitted to so far
Thanks to all of you and I might see you around
Regards Dousan...
What are you going to buy in the end?
Logseman said:
What are you going to buy in the end?
Click to expand...
Click to collapse
I ended up with the Lumia 800. The N9 seemed nice and have good specs and a familiar OS, but tried it out a few times in a shop and didn't get that wow feeling. Further more read a few things on TMO (talk.maemo.org) in the N9 sub forum that convienced me not to pick up the N9. Even read some danish users experience with the device and it wasn't good all in all. Though the N9 has it's openess and a lot of modding potential i didn't want to go for a 'half finished OS' as i see it from reviews from users. On TMO hardcore N900 users that shifted to the N9 was dissapointed in the N9 as it's gone more mainstream and comercial in how Nokia build the OS.
As of now the Lmia suites my needs much better and I do like the WP7 feel and looks.
It was hard to choose between the two devices as they both have good things going for them.
Regards Dousan...
I got my S3 last July and rooted it and installed a rom the first day. I've had zero issues with it so far outside of the occasional freeze or reboot. I've pretty much only run Task's AOKP rom. I do not think my problem is rom or kernel related whatsoever, but it seems more like some type of hardware issue.
Anyway, two days ago I was running the 4-26 version of Task's rom with the stock kernel. I did a full wipe and clean install. The phone had been running trouble free with no issues for a couple of days. Suddenly with around 75% battery, it just rebooted when I turned the screen on but kept failing and starting again at the Samsung screen or sometimes made it to the underwear kernel screen. I tried to go into recovery and it started into recovery for about a second and went into reboot again. Tried download mode and it went right in and then rebooted after a second or two. It will not stay in any mode for longer than a second or two. I've tried connecting it to the pc and put it into dl mode and it does the same. I have a usb jig and it puts into download but only for a second or two.
I'm sure I'm missing something, but any help would be appreciated.
double RL said:
I got my S3 last July and rooted it and installed a rom the first day. I've had zero issues with it so far outside of the occasional freeze or reboot. I've pretty much only run Task's AOKP rom. I do not think my problem is rom or kernel related whatsoever, but it seems more like some type of hardware issue.
Anyway, two days ago I was running the 4-26 version of Task's rom with the stock kernel. I did a full wipe and clean install. The phone had been running trouble free with no issues for a couple of days. Suddenly with around 75% battery, it just rebooted when I turned the screen on but kept failing and starting again at the Samsung screen or sometimes made it to the underwear kernel screen. I tried to go into recovery and it started into recovery for about a second and went into reboot again. Tried download mode and it went right in and then rebooted after a second or two. It will not stay in any mode for longer than a second or two. I've tried connecting it to the pc and put it into dl mode and it does the same. I have a usb jig and it puts into download but only for a second or two.
I'm sure I'm missing something, but any help would be appreciated.
Click to expand...
Click to collapse
Check the bad power button or bad battery.
tomy1986.nt said:
Check the bad power button or bad battery.
Click to expand...
Click to collapse
Good suggestion on the power button. Would make sense, but it seems to be fine feels exactly like it should. I took it apart and even left the button off. The part of it that's attached to the motherboard is very crisp and pops right back after pushing it in. Doesn't seem to be the problem. I've tried three different batteries with the same results. Guess I'm going to the service center tomorrow. Damn
Hi everyone,
I'm experiencing pretty silly situation with my phone.
So the story begins here:
I was surfing the web while listening to music in the bus when suddenly my oneplus3 randomly turned off and I couldn't turn it back on. (I was on something around 15% on battery so it's not a low battery problem) I tried to turn it on several times and after holding the power button for like 10secs it turned on, and after pressing the power button again (because I needed to get past unlocked bootloader screen and dm-verity) I saw a boot screen. The capacitive button leds turned on and after 3 secs it turned off again, so I started worrying... After a while I tried to access the recovery, but no luck at all. It powers it self off after bootscreen. So I started to research. Tried to flash the entire OS, partritions with msmdownload tool. After several unsuccessful flashes (firehosewritedata failed sometimes while writing userimg or system.img or boot.img) I did get the download complete green text message, and after successful flash, the white LED turned on, even the phone was not plugged in USB or charger and turned off. The screen is completely black and the white led just flashes constantly without blinking or anything. I could only turn the led off by pressing the power button for another 10 secs. And after turning the phone off, problem still remains. After oneplus logo phone shuts down...
I can access bootloader.
And after flashing everything should be on stock, because now I only got screen only about bootloader, no dm-verity..
And of course - I still cannot access the recovery.
p.s. I tried to do the power cycle (as the tech support told me) but still no luck at all.
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Mukthar. said:
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Click to expand...
Click to collapse
1GB version
djemm1996 said:
1GB version
Click to expand...
Click to collapse
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
Of course. Everything is done right. I also get that green "download complete" message.
p.s I also opened the phone. water indicators are fine and no major defects what can i see by eye... All connectors are good as well.
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
And yes, phone was connected right. :good: installed drivers with test mode on Win10 and got Snapdragon device in COM devices. As well the MsmDownload tool shows up my device in port #20
Any ideas?
djemm1996 said:
Any ideas?
Click to expand...
Click to collapse
Follow method 2 from the Hard Brick guide by Naman Bhalla and try two or three times.
Sometimes it takes more than once for restoration.
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
try to flash again, and if it still maybe something short inside.
if you have disassembly your phone, try disconnecting various flex cable like camera, sim slot etc that connect to the mainboard, that doesn't prevent device from powered on, then try to turning it on.
if it still, check your mainboard, if you don't know how, send it back.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
djemm1996 said:
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
Click to expand...
Click to collapse
They are doing the same thing like you did.
I already had a session since i thought they are going to do something "special"
You can try the remote session but im afraid that wont help you if you already did it multiple times.
What about battery? Charged?
drmuruga said:
What about battery? Charged?
Click to expand...
Click to collapse
Yes battery is charged of course. It's just doint the same thing. Turns on, after a while when bootscreen comes it just turns off and white notification led appears, after that nothing.
I tried to flash it with tool using method 2 for like 15 times with "download complete" messages, but still no luck at all. Tried to erase partritions with fastboot, flashing just only recovery, modded recovery etc. but I still cannot access the recovery nor system. I just don't get it why the phone does not boot into recovery if I flash it or boot it straight away, It just only turns off and that's it. nothing more. Only black screen and white led lighting all the time (after a while the phone turns warm).
I have read all the MsmDownloadTool thread in "Mega Unbrick thread" and saw that few people have experienced the very same situation as me, so I was wondering if there is any fix for this? It's so strange that I was just surfing the Web and it just turned off by it self with like static image for miliseconds and after that just black screen.
There should be any fix. I guess that it's just a partition error...
Ok, not good news. I had a little remote session before a while. They says it's already a hardware problem.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Pfffft you think manufacturers notice when you take apart phones? Hell I took apart my Xperia Z2 because it was having problems and then glued it back together with cyanoacrylate hahahaha (worst thing to do but wtv) and no one noticed though it was seemless and everything looked perfect
Guys, I've got something for you! Not really the same thing as Naman.
p.s. not saying its original hehehehe keep safe
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Actually I was on twrp too! Also I have recently noticed that recovery loading speed was far too long than normal one. I'm talking for something about 5-7 minutes after reboot into twrp. So, who knows what did happen. Just made an RMA request. Will see how it goes.
Anyway, I was on stock 7.1.1 and it's just rooted with custom recovery and that's it! Nothing more! Is that just a factory failure or maybe it's caused by drops i have had? Nothing serious for a 4-5 times for a half year. Of course I have used it even in winter when the snowflakes are coming down from the sky and little rain. Btw, these liquid indicators are white, so all safe. ::laugh:
A
makadama said:
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Click to expand...
Click to collapse
Hey y’all
So my phone fell two weeks ago from about 3 feet after a bad hand off as I was showing a pic to someone.
It already had fallen and only suffered a crack along the outer screen from the first fall, but this second drop cracked the inner screen and rendered the lcd useless.
I was still able to turn it off and on, as well as increase/decrease the volume, but screen was showing blue streaks until I just turned it off.
I reset the phone to no avail and eventually got a new replacement screen and frame from witrigs and was able to get the phone into recovery. I wiped the cache and was able to finally get past the boot screen (which displayed fine) but then immediately goes black as it loads up the main OS.
The screen can sense my finger and the touchscreen vibrates when I touch it as if the unlock number pattern screen would appear on the screen but, the screen remains blacked out.
I can turn the volume up and down, power button works fine. I can access twrp and it shows the full screen on the display, but once the OS tries to load the screen blacks out while otherwise functioning as it should.
I checked all of the connections and they’re all good, no loose ends or incorrectly inserted or disjointed pieces, I just can’t get a visual right when the os loads up.
Any ideas if this is hardware/software based? Doesn’t make sense that the screen shows up fine during the initial boot then goes black during the os boot and everything but the screen functions as normal. Thanks
DD
DD83 said:
Hey y’all
So my phone fell two weeks ago
Any ideas folks? Thanks
DD
Click to expand...
Click to collapse
Which rom/kernel you on? You can try another kernel and check
I think I was in resurrection remix 5.8.2. I mostly care about my files but if I can still use the phone that would be ideal.
Just tried flashing the rom I had on before (rr remix n 5.3.5 20180612 release), then dalvik and cache wipe, with the same result. Thanks to anyone that replies and has some insight! Been going on two weeks since my phone was initially dropped to replacing the screen to this! Grrr
DD83 said:
Just tried flashing the rom I had on before (rr remix n 5.3.5 20180612 release), then dalvik and cache wipe, with the same result. Thanks to anyone that replies and has some insight! Been going on two weeks since my phone was initially dropped to replacing the screen to this! Grrr
Click to expand...
Click to collapse
Sometimes there is a drivers issue on replacement of screen. Try OOS and see if it works. Atleast for some people, OOS solved the issue.
tnsmani said:
Sometimes there is a drivers issue on replacement of screen. Try OOS and see if it works. Atleast for some people, OOS solved the issue.
Click to expand...
Click to collapse
Thanks. Should I try a newer more recent oos or one closer to the oos I had installed? Does it matter?
I would ideally like to get back to where my phone was, but if I can’t I’m content with starting over if it means I’ll have a functioning phone.
DD83 said:
Thanks. Should I try a newer more recent oos or one closer to the oos I had installed? Does it matter?
I would ideally like to get back to where my phone was, but if I can’t I’m content with starting over if it means I’ll have a functioning phone.
Click to expand...
Click to collapse
Recent OOS can be tried. There is no link between what OS you had and the OOS you are flashing.
Hope you succeed!
had similiar problems,replaced my screen was using custom roms too i found out cheap screens dont work properly and the only way around this for me was to install caesuim latest kernel cause my screen use to stay black after the screen went to sleep until i installed that kernel works great now
I have a like problem, my oneplus 3 locks the bottom of the screen, already replaced kernel and nothing works, someone has suggested what it can be, the screen has been replaced.
ireaper4592 said:
had similiar problems,replaced my screen was using custom roms too i found out cheap screens dont work properly and the only way around this for me was to install caesuim latest kernel cause my screen use to stay black after the screen went to sleep until i installed that kernel works great now
Click to expand...
Click to collapse
can I install this kernel on OOS latest build?