Related
Guys, thanks to all of you - especially frysee, who was a big help via Gtalk - the biggest part of my problem is solved:
My Transformer is still bricked and display won't turn on, but I was able to go back to stock ROM and wipe all personal data. So I won't get any trouble with warranty
If anyone is interested, me or frysee could write a How To for returning to stock ROM and retrieve warranty when screen is dead.
Thanks again!
qwer23
_____________________________________
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23
I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.
demonotter said:
I was initially having this problem with my Transformer (it would usually happen when it had gone on standby and it couldn't get it to turn back on again) until I ran the ASUS updates on it - have you been able to update your Transformer on the occasions it did turn on for you?
If you've rooted it and stopped the OTA updates going onto it, you might just have to undo that and get an official ASUS firmware build on there to help fix the problem.
Click to expand...
Click to collapse
Hi!
First of all, thx for your answer.
Well as I said, the first time the problem occured, the device was out of the box and untouched before. So I don't think it has to do with something I did.
For me it normally also happened when device was in sleep mode, except the first time out of the box
I installed a custom ROM + Clockworkmod Recovery after that, hoping it'll fix the deep sleep problem. And it really didn't happen again - until now
I didn't turn off OTA updates as I first saw that thread when the device was already dead Perhaps it tried to OTA update itself but I guess I would have to confirm this manually right? And I didn't do that...
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!
Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?
frysee said:
Nice, another german Transformer
"playing the plug and play sound" means you propably have adb access? Tried getting a logcat?
Click to expand...
Click to collapse
yes, being unable to wait for the german release, i imported from uk
adb gives me "device not found". even though i'm not a total noob, i don't know what i have to change to make it work. any advice? sadly i'm working while my tf is charging @home so can't really try something. i only hope you guys have some ideas
Sent from my rooted X10i using awesome custom roms
qwer23 said:
Reflashing another ROM or the stock ROM was my first idea, too. But hell, I can't even go to recovery! No matter what I do, press, plug or unplugg, the screen stays black!
Click to expand...
Click to collapse
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...
demonotter said:
Ahh. I didn't realise the screen was completely dead, I thought you had it working some of the time as had happened to me.
If you're seeing it in Explorer, maybe it is just a hardware failure and you'll have to get Asus to look at it...
Click to expand...
Click to collapse
no i guess that it is indeed the same thing that happened to you, sometimes it worked, sometimes not. only this time it doesn't come back from the not working part I guess you see yours in explorer too if it troubles to get out of deep sleep. i guess it's just the screen that sometimes doesn't turn on for all with that problem. but for me it doesn't even turn on for booting
Sent from my rooted X10i using awesome custom roms
It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?
demonotter said:
It's possible. I don't think I tested connecting it to the Explorer while the screen was off, I assumed it just wasn't on.
Can you test it with the HDMI out and see if that shows you what would be on screen?
Click to expand...
Click to collapse
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?
qwer23 said:
Yeah, good idea! Will try this asap when I'm back home. Do I have to press something on the TF to enable HDMI output or is it enough to plug it in?
Click to expand...
Click to collapse
You just plug it in.
qwer23 said:
Hi Guys!
I have a problem that is pretty common over at MoDaCo, but I haven't read anything about it here.
My Transformer sometimes doesn't turn on or wake up from sleep mode when turned on already. You can push the power button endlessly and nothing happens. Then suddenly it'll turn on as if nothing had happened.
I had this problem the first time right out of the box, so there's no bad software installed by me, don't know what ASUS did though. Perhaps it's one of the pre-installed apps.
As I said, normally it eventually comes to life again, but now I couldn't turn it on for a whole day! After I had no success, I left it on the charger over night, but still nothing this morning.
I feel I tried everything, pushed Vol Down + Power to go into recovery, pushed Vol Up + Vol Down and plugged USB to go into (useless) flash mode just to see the device to something, but no.
The only things that happen, if I push power:
- if I plug USB, the Windows plug and play sound plays and if I force shutdown the Transformer again (long-press power), the unplug sound plays. The device even appears in the Explorer and I can access SD card, but it only shows empty folders, no files in them.
- When I force-shutdown the device, I hear an internal "click" sound, similar to the one when you switch from front to rear camera, and you hear the speakers turn off. So it seems to initialize everything and stuff...
But all the time the Transformer screen stays dead
Any advice? Really need your help here guys! At MoDaCo there's no answer so far...
Regards,
qwer23
Click to expand...
Click to collapse
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.
checkbox111 said:
When it seems dead, try holding the power button for about 5 seconds (or whatever time you hold it for when turning it off)
Leave for about 2 minutes then hold power button again (like you do when turning device on) and it should boot.
Click to expand...
Click to collapse
Tried that a lot of times already. No help.
Phone still won't turn on, but I just realized I cannot only access my SD Card, I can also access internal storage.
Is this of any help?
qwer23 said:
Tried that a lot of times already. No help.
Click to expand...
Click to collapse
Then your ****ed!
checkbox111 said:
Then your ****ed!
Click to expand...
Click to collapse
I guess so
I'm getting a mini-hdmi cable today to determine if the screen is broken, because i have the feeling that ***** is booting but not showing anything...But I'll have to send it to ASUS nonetheless. Has anyone ever sent a device in for warranty reasons with custom software (CWM, Custom ROM) on it? What kind of trouble will I have to face?
I'd say try it with the HDMI cable, see if you get anything up on it and if the touchscreen/everything else still works, see if you can get the latest official ROM on there, see if that fixes the problem.
If nothing else, you can then send it back with an official firmware on it.
Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps
Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.
sbirsen said:
Try holding the power button for 5-10 sec, then press power + volume down (might be volume up - try both) together for another 5-6 sec. You'll get to a reset screen where it asks you to confirm if you want to wipe everything. press volume down (I think!! - read the screen carefully) instead to boot normally.
hope this helps
Click to expand...
Click to collapse
Not possible since I installed CMW.
stuntdouble said:
Its 10+ seconds for a full power off by the way, nothing shorter than that. If you changed any system files either by flashing or by pushing via ADB then you will have invalidated your warranty. Unless you can restore it to the way it was before you fiddled with it, you'll have an expensive paperweight.
Click to expand...
Click to collapse
Big bummer And sadly there are no "ASUS Stores" around where I could use a stupid employee who has no clue and is convinced it's hardware related.
Well I don't have my HDMI cable by now and will try this first, but if that doesn't work:
Can someone give me a step-by-step how I can access the restore function of CWM without seeing anything on my device? I did a backup in CWM before installing the custom ROM. Perhaps tell me sth. like this: "press power+vol. down on start, then after approx. x seconds press vol up, wait a bit to make sure CWM started, press vol down twice, to go to recovery, ..."
And can someone do the same for the stock recovery to reset the device? Perhaps there's a chance that a failed OTA update deleted CWM an there's the stock recovery.
I know the chance to save it like this are small, but otherwise a lot of money is lost
Regards,
qwer23
On the flip side however, you could probably make some money by being the first to dismantle your device, and sell the photos of the internals to some website like iFixit. Then you could also sell it off as parts on eBay. Obviously it might take more effort than you are willing to give it, but at least it's another option.
If you do decide to open it up I would love to hear what mA rating the battery has on its label. Not being able to find out the actual proper rating from any site has been driving me nuts. I believe it's 6800mA but im not 100% sure.
I tried to flash a custom ROM on my Nexus but since then the phone will not start up.
If I try to boot normally, the screen flashes for a second, I get a quick buzz of haptic feedback, then the "Home" and "Search" buttons light up, then the "Back" button, and then the "Settings" button lights up and stays lit. Sounds weird but this is true.
If I try to boot into the bootloader, the "Search" and "Home" buttons light up and stay on, but nothing appears on the screen.
Annoyingly, fastboot picks up the serial number of the phone, but it can do nothing else. oem unlock is unresponsive, the three dots come up and the cursor flashes, though it at least gets past the "waiting for device" stage. If I try issue oem lock, it reports that the phone is already locked so Johnny 5 is somewhat alive.
adb doesn't recognise the phone at all, I tried on mac, WinXP, W7, and linux for good measure.
Superboot also reports that the phone is locked so no luck there.
I hope I'm not covering old ground here, any help would be greatly appreciated.
What custom ROM did you flash? What is your phone model?
Of course ADB wouldn't recognize your phone. ADB requires the phone to be on.
The only thing that would detect would be "fastboot devices" in bootloader mode.
Are you able to get into recovery mode?
And your phone is not bricked. Stop using that term. There hasn't been a report of a brick for the Nexus S unless the user has flashed a ROM that isn't for their phone via Odin or whatever.
I don't know... if he doesn'tget that Google and lock or unlock screen he might be a first one.
Did you try the volume up and then hold power to boot? It should go into fastboot menu. If that doesn't than you are first to brick it. Must have been faulty from the beginning though.
Sent from my Nexus S 4G using XDA App
Take out the battery and hold the power button for 20 seconds
Uncle Jimmy says hello
zephiK said:
What custom ROM did you flash? What is your phone model?
Of course ADB wouldn't recognize your phone. ADB requires the phone to be on.
The only thing that would detect would be "fastboot devices" in bootloader mode.
Are you able to get into recovery mode?
And your phone is not bricked. Stop using that term. There hasn't been a report of a brick for the Nexus S unless the user has flashed a ROM that isn't for their phone via Odin or whatever.
Click to expand...
Click to collapse
I believe I can use that term if the phone does not boot into recovery, which, to answer your question, and to re-iterate what I already said, it doesn't.
I don't have the other details you asked but I will post again later with them.
snandlal said:
Take out the battery and hold the power button for 20 seconds
Uncle Jimmy says hello
Click to expand...
Click to collapse
Can't just now, but I will give it a go later, thanks.
obsanity said:
I don't know... if he doesn'tget that Google and lock or unlock screen he might be a first one.
Did you try the volume up and then hold power to boot? It should go into fastboot menu. If that doesn't than you are first to brick it. Must have been faulty from the beginning though.
Sent from my Nexus S 4G using XDA App
Click to expand...
Click to collapse
Absolutely, I am getting the feeling it's a faulty handset too. No, it doesn't boot into fastboot, or normally either, the screen is completely blank.
No-one has seen this behaviour where the buttons along the bottom of the screen light up when you try to boot the phone? I concede that this is a very rare thing to happen to a Nexus S, but it seems strange that nobody has seen or heard of it before?
I'm sorry I didn't fully understand. It doesn't boot into fastboot but it picks up the serial number? Have you tried flashing a recovery through fastboot?
culberto said:
Absolutely, I am getting the feeling it's a faulty handset too. No, it doesn't boot into fastboot, or normally either, the screen is completely blank.
No-one has seen this behaviour where the buttons along the bottom of the screen light up when you try to boot the phone? I concede that this is a very rare thing to happen to a Nexus S, but it seems strange that nobody has seen or heard of it before?
Click to expand...
Click to collapse
In your OP post you said,
Annoyingly, fastboot picks up the serial number of the phone, but it can do nothing else. oem unlock is unresponsive, the three dots come up and the cursor flashes, though it at least gets past the "waiting for device" stage. If I try issue oem lock, it reports that the phone is already locked so Johnny 5 is somewhat alive.
Click to expand...
Click to collapse
But yet you can't get into the bootloader mode? I'm confused.
If you want us to help you, you have to be as precise and clear as you can.
zephiK said:
In your OP post you said,
But yet you can't get into the bootloader mode? I'm confused.
If you want us to help you, you have to be as precise and clear as you can.
Click to expand...
Click to collapse
I think he means that if you do "fastboot devices" it comes up with a number. That means there is some hope.
Did you try flashing with Samsung's exe? You have to know which model you got.
zephiK said:
In your OP post you said,
But yet you can't get into the bootloader mode? I'm confused.
If you want us to help you, you have to be as precise and clear as you can.
Click to expand...
Click to collapse
Fastboot reports the serial number okay, but when I turn the phone on holding the volume button up, nothing happens.
Actually, I had a moment of inspiration when using the fastboot oem unlock command- I realised that when the cursor was flashing it was waiting for me to confirm that I wanted to unlock on the phone itself. So, I pushed up on the volume rocker and confirmed by pushing the power button, and fastboot reported that I had successfully unlocked the phone. "Great!" I thought, but whatever I try to flash onto the phone I get the same behaviour, the lights at the bottom of the screen flash but nothing happens on the screen.
So it seems I have a faulty screen, or I did something to screw with the electronics. There are a couple of sugestions here to try but I don't hold out much luck.
Thanks for you help anyway
brmayhem said:
I'm sorry I didn't fully understand. It doesn't boot into fastboot but it picks up the serial number? Have you tried flashing a recovery through fastboot?
Click to expand...
Click to collapse
No problem, from other posters it seems I'm not too good at explaining myself. I think the phone is actually booting into recovery but the screen is dead so it looks like nothing is happening.
Yeah, I finally managed to unlock the handset (see my previous post), and I can flash the recovery no problem (or at leasts it reports no problem), but nothing comes up on the screen. As I said in my last post I think the screen must be borked.
Thanks for posting anyway, it's much appreciated.
obsanity said:
I think he means that if you do "fastboot devices" it comes up with a number. That means there is some hope.
Did you try flashing with Samsung's exe? You have to know which model you got.
Click to expand...
Click to collapse
Samsung's exe? Sorry, I did a quick google on this but I'm not sure exactly what you mean? As I've said in my last 2 replies, I think the screen is the problem but it's worth a try.
Thanks for all the suggestions so far, and sorry to pipe on about this, but has nayone seen this behaviour where the screen flashes for a millisecond when the phone is turned on but then stays dead, and instead the function keys at the bottom light up and turn off in a particular sequence? As I've said in my last couple of posts I think my phone is toast but maybe there is a clue somewhere in that description?
Samsung has an exe for windows to restore your system where it was original. Find the one for your phone and flash it. The file is different depending on who you carrier is and what model number do all the research them run the exe
Edit exe is called swupdater on sprint
Sent from my Nexus S 4G using Tapatalk
http://forum.xda-developers.com/showthread.php?t=1072698
Uncle Jimmy says hello
Hello there.
A few days ago, my Nexus 7 refused to turn on as normal. When I clicked all buttons down to load up the fastboot menu, I can see the status of my device as LOCK STATE - LOCKED.
So, I researched how to unlock my Nexus 7 bootloader and using software, I managed to allow my Nexus 7 to get to the unlock bootloader menu. However, when I pressed the volume button to highlight Yes, when I press the power button, nothing happens.
I am open to all ideas and can try an array of different measures to do this. I have some experience with rooting before.
Thank you in advance.
ValkyrieOneNiner said:
Hello there.
A few days ago, my Nexus 7 refused to turn on as normal. When I clicked all buttons down to load up the fastboot menu, I can see the status of my device as LOCK STATE - LOCKED.
So, I researched how to unlock my Nexus 7 bootloader and using software, I managed to allow my Nexus 7 to get to the unlock bootloader menu. However, when I pressed the volume button to highlight Yes, when I press the power button, nothing happens.
I am open to all ideas and can try an array of different measures to do this. I have some experience with rooting before.
Thank you in advance.
Click to expand...
Click to collapse
Hi, ValkyrieOneNiner...
This seems to be commonly reported problem.
Take a look here for a possible solution.
You either have a faulty Nexus 7 (eMMC nand chip gone bad)... or just a faulty USB connection whilst unlocking the bootloader.
Rgrds,
Ged.
Ah, thank you! I actually put my tablet on charge there and it booted up as normal, but with a message to say Safe Mode. It then cut off due to a lack of charge, but I'm going to leave it on charge for a few hours to see if anything else can be done as this looks promising!
"Your device is corrupt. It can't be trusted and may not work properly." (Red)
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
https://support.google.com/nexus/an...6399943843044-1589582643&p=verified_boot&rd=1
Has anyone else experienced this?
I also got that message when I first got device. Set up my Google account and then let it sit and charge. Looked 30 mins later that message appeared. It was also followed up by another screen talking about unsecure boot or something and powered it self off. It said can not boot when I tried to restart phone and I tried again and no response from the phone at all.waited 5 mins and it booted fine and never seen the messages again .
that screen appears when the bootloader is unlocked. did you guys unlock your bootloader? or, did you purchase from T-Mo/someone else?
Bl still locked and bought online from tmobile never even loaded any apps yet
anoymonos said:
Bl still locked and bought online from tmobile never even loaded any apps yet
Click to expand...
Click to collapse
if you reboot to bootloader mode, does your screen look like the picture below:
Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.
maruichan said:
Posted a thread with the same error so you're not the only one. Phone booted fine once it went through it's rolodex of error screens and shut off. Had to manually power it back on.
Click to expand...
Click to collapse
if your phone screen in bootloader mode does not look like the one in my post, you purchased the phone direct from T-Mobile/Other Retailer and you didn't unlock the bootloader, i'd ask for a replacement. if your phone screen in bootloader mode looks like the one in my post, the bootloader has been unlocked somehow/by someone...
cortez.i said:
if you reboot to bootloader mode, does your screen look like the picture below:
Click to expand...
Click to collapse
Power + Vol Dwn gives me this screen...
maruichan said:
Power + Vol Dwn gives me this screen...
Click to expand...
Click to collapse
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.
cortez.i said:
that's not bootloader/fastboot mode.... that's the Factory Reset/Recovery mode. i enter bootloader/fastboot mode using ADB commands (from windows command prompt) while the phone is connected to my laptop. steps to enter fastboot mode:
1. power off device - make sure your phone is not connected to laptop via USB cable
2. hold the Volume Down Key for a few seconds
3. while holiding Volume Down Key connect the Micro USB cable to your device.
4. release Volume Down key as soon as phone goes into Fastboot Mode (screen similar to my post above)
What does your screen say in fastboot mode? to get out of fastboot mode, unplug the USB cable from laptop, hold volume down + power key until blank screen, release all buttons and phone will proceed with boot process.
Click to expand...
Click to collapse
K, will try it in a bit
maruichan said:
K, will try it in a bit
Click to expand...
Click to collapse
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.
cortez.i said:
by the way, do you have a Korean or US version of the G6? i have the T-Mo version.
Click to expand...
Click to collapse
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.
maruichan said:
T-mobile US. It is a pre-order
Here is the screen. It is not unlocked.
Click to expand...
Click to collapse
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.
See still locked
cortez.i said:
i'd request a replacement since your phone is unlocked (based on picture) and you're getting the "...corrupt.." message. maybe go to a corp store show them the problem and request to keep the phone until a replacement is received. good luck.
Click to expand...
Click to collapse
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.
maruichan said:
It doesn't seem to effect the function of the phone. So perhaps it is just a bug. Doing a little bit of light research, some other people have had issues with this popping up even with stock on Nexus.
I have until the 17th to exchange/return.
Click to expand...
Click to collapse
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.
BTW, did anyone get a second screen saying contact customer support (some kind of language like that)? It is very similar to the red error screen, but it read like the device was basically bricked. It disappeared after a while and the phone turned off while I was trying to get a picture.
Got both screens
cortez.i said:
true, but i'd at least make T-Mo aware of the issue. personally, i'd ask for a replacement.
Click to expand...
Click to collapse
I did, that is how I got the return date. They notated my account massively and it looks like it'll be a root canal to a exchange.
I'm not sure that it's anything more than a bug... it hasn't stopped the phone from working and possibly may be an oversensitive security measure on Android's part. So far it seems only related to Nexus(?) that I could find... I am only posting here so others can inform themselves. Maybe others with similar errors who have owned a Nexus could enlighten us.
Either case, doing a factory reset in a little bit. I also received the latest update and applied it. So maybe that'll help too...
franki_667 said:
I was on a phone call when my phone crashed and then displayed the following message:
"Your device is corrupt. It can't be trusted and may not work properly."
There was a URL which directed me to the following site for further information:
Has anyone else experienced this?
Click to expand...
Click to collapse
Yes I have had this happen 2 different times and 4 days apart on my AT&T LG G6, U.S. Variant. NO I don't unlock my devices ever. And I only install well known apps from the Play store. One possible pattern I noticed was that both times it happened relatively soon after turning OFF the always on display. Then when I rebooted the AOD was turned back on by itself. No other settings appear to be changed and my Nova launcher is running normal.
Did you happen to turn off your AOD as well?
My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe
Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.
there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..
Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx
Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs
Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.