Related
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
cbcampos said:
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
Click to expand...
Click to collapse
Wow, I haven't seen or heard of any defect like that in the N7 yet. I would exchange/RMA the device if I were you. It seems like an easily demonstrable problem, there shouldn't be any reason Google/a retailer wouldn't exchange it.
Sent from my Paranoid Nexus 7
RockNrolling said:
Wow, I haven't seen or heard of any defect like that in the N7 yet. I would exchange/RMA the device if I were you. It seems like an easily demonstrable problem, there shouldn't be any reason Google/a retailer wouldn't exchange it.
Sent from my Paranoid Nexus 7
Click to expand...
Click to collapse
Even with the bootloader unlocked? Or do I need to somehow lock it?
update
cbcampos said:
Nexus 7 was working fine and then I pulled it out and notices a gray screen. Restarted it and I get a slight blue shadow to the Google and Padlock boot screen. Then it begins to change crazy colors and ends up fading to a gray screen. Can't boot into recovery from fastboot. Help?
Here are some pictures in order of boot.
Click to expand...
Click to collapse
It actually seems as if it is partially just a screen issue. I heard a notification of an email on the N7. I believe it has actually booted up, but the display is stuck. If I tap where the notification bar would be, I heard audio feedback.
UPDATE: I suspected something was loose in display connection because of the type of problem. I knocked pretty hard on the device, and the display kicked back in. Doesn't solve the problem of being unable to boot into recovery, but it seems like it could be a display problem. Suggestion still to just get a replacement? and relock bootloader?
cbcampos said:
Even with the bootloader unlocked? Or do I need to somehow lock it?
Click to expand...
Click to collapse
My bad, I skimmed your post and didn't realize you could get into fastboot mode. Try turning off the N7, connecting it to a computer , and getting back to fastboot mode. You should be able to use adb to relock the boot loader. In fact, you should be able to boot into recovery from fastboot since the N7 is connected to a computer.
Good job trouble shooting the display connection! I would still personally recommend exchanging/RMA. You never know when the problem might reappear even if you "fix" it.
Sent from my Paranoid Nexus 7
Take the back cover off and check the display ribbon cable,and all other connections are tight. They won't be able to tell that the back was removed, unless you ding it up. Might find a loose connection. May just save you the trouble of going through RMA.
Hi all,
I'm new here, a friend refered me this page to ask for some troubles I'm having with my Nexus 4.
I bought it from ebay about 4 months ago. For all this time, it worked perfectly, no problems at all, running fine.
The thing is that this last week the telephone is doing strange things. While using it, at a few minutes of use, "phantasmal touches" occurs, getting hit the buttons from back, back to desktop and last applications.
Also, after some minutes, or just touching the screen for scroll, the slide malfunction, getting harder to slide, even sometimes this doesn't works, but touching stills operative (sometimes not).
The only way that temporarily works, is locking and unlocking the screen, but problem still appear again and again.
Tried also to restore it (like as it was new). But nothing.
Hope you can help me with this. Thanks.
the-cheshire-cat said:
Hi all,
I'm new here, a friend refered me this page to ask for some troubles I'm having with my Nexus 4.
I bought it from ebay about 4 months ago. For all this time, it worked perfectly, no problems at all, running fine.
The thing is that this last week the telephone is doing strange things. While using it, at a few minutes of use, "phantasmal touches" occurs, getting hit the buttons from back, back to desktop and last applications.
Also, after some minutes, or just touching the screen for scroll, the slide malfunction, getting harder to slide, even sometimes this doesn't works, but touching stills operative (sometimes not).
The only way that temporarily works, is locking and unlocking the screen, but problem still appear again and again.
Tried also to restore it (like as it was new). But nothing.
Hope you can help me with this. Thanks.
Click to expand...
Click to collapse
Have you noticed if it stops or starts doing it if you plug it into a charger (preferably the stock or a decent quality one)
sp99 said:
Have you noticed if it stops or starts doing it if you plug it into a charger (preferably the stock or a decent quality one)
Click to expand...
Click to collapse
The charger is wich it came with the original mobil, and does it also when charging
Is it stock?
sp99 said:
Is it stock?
Click to expand...
Click to collapse
I'm sorry, what you mean with stock.
Have you rooted it or put a custom ROM on it?
sp99 said:
Have you rooted it or put a custom ROM on it?
Click to expand...
Click to collapse
No, it's not.
the-cheshire-cat said:
No, it's not.
Click to expand...
Click to collapse
Is the os up to date? (Settings-> about phone->Software updates->check for updates) Also try wiping the cache partition (I will post instructions of you need them).
sp99 said:
Is the os up to date? (Settings-> about phone->Software updates->check for updates) Also try wiping the cache partition (I will post instructions of you need them).
Click to expand...
Click to collapse
It's updated, and thanks for spending your time with this, I apreciate it, sincerely. Will wait for that instruction!
the-cheshire-cat said:
It's updated, and thanks for spending your time with this, I apreciate it, sincerely. Will wait for that instruction!
Click to expand...
Click to collapse
No problem.
This is from an email from Google regarding my nexus 7, it should be the same:
Hold the*Power Button*until the device powers down completely.Press and hold*Power Button*and*Volume Downsimultaneously.Once at the Android bootloader screen, pressVolume down*until you see the option*Recovery mode.Press*Power*button to restart into*Recovery mode. You should see an image of an Android with a red exclamation point.While holding down the*Power button, pressVolume Up.Use the Volume keys to scroll down to*wipe cache partition*and press*Power*Button*to select it. The device should clear the cache instantly.*Select and press the*Power Button*on*Reboot System Now, then see if the issue is resolved.
sp99 said:
No problem.
This is from an email from Google regarding my nexus 7, it should be the same:
Hold the*Power Button*until the device powers down completely.Press and hold*Power Button*and*Volume Downsimultaneously.Once at the Android bootloader screen, pressVolume down*until you see the option*Recovery mode.Press*Power*button to restart into*Recovery mode. You should see an image of an Android with a red exclamation point.While holding down the*Power button, pressVolume Up.Use the Volume keys to scroll down to*wipe cache partition*and press*Power*Button*to select it. The device should clear the cache instantly.*Select and press the*Power Button*on*Reboot System Now, then see if the issue is resolved.
Click to expand...
Click to collapse
Ok, it's done, I gonna test it for a while and see if it's solved
Nothing, less than a minute to the slider started to fail when moving up and down
the-cheshire-cat said:
Nothing, less than a minute to the slider started to fail when moving up and down
Click to expand...
Click to collapse
Don't quite understand, does that mean it has worked or it still has a problem?
sp99 said:
Don't quite understand, does that mean it has worked or it still has a problem?
Click to expand...
Click to collapse
The problem stills, for example, im in facebook or whatsapp, i slide up and down for reading, and from the nothing it's harder to slide/scroll... it's not that sensitive as before. I mean, with just a slide of the finger at early is scrolls fast, as it must be, but for some reason, after a few slides, with the same finger slide, it just scrolls a bit.
the-cheshire-cat said:
The problem stills, for example, im in facebook or whatsapp, i slide up and down for reading, and from the nothing it's harder to slide/scroll... it's not that sensitive as before. I mean, with just a slide of the finger at early is scrolls fast, as it must be, but for some reason, after a few slides, with the same finger slide, it just scrolls a bit.
Click to expand...
Click to collapse
Have you tried cleaning the screen with (alcohol free) screen wash? Otherwise it sounds like a hardware issue or something wrong with the touch drivers.
Sent from my Nexus 4 using Tapatalk
sp99 said:
Have you tried cleaning the screen with (alcohol free) screen wash? Otherwise it sounds like a hardware issue or something wrong with the touch drivers.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
the-cheshire-cat said:
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
Click to expand...
Click to collapse
It's probably the screen protector causing the problem, take it off and then try using the phone again and see what happens.
Sent from my Nexus 4 using Tapatalk
the-cheshire-cat said:
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
Click to expand...
Click to collapse
Well, for the moment I've done a wipe from all data, the other option from the "recovery menu", and it's been a while using it, and the problem doesn't shows, non of both i mention.
Let's see if this continue like this. Tomorrow I'll let you know.
thanks for all!
after this post, it came again T-T
the-cheshire-cat said:
Well, for the moment I've done a wipe from all data, the other option from the "recovery menu", and it's been a while using it, and the problem doesn't shows, non of both i mention.
Let's see if this continue like this. Tomorrow I'll let you know.
thanks for all!
Click to expand...
Click to collapse
You're welcome Remember to press the thanks/thumbs up button!
Sent from my Nexus 4 using Tapatalk
Nothing, the problem still persist.
I'll see if I must clean the screen (it has a screen-protector althought). If not, I don't know what to do, unless I send it to someone if can repair it or something... :crying:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
razrus said:
I was sitting on my couch yesterday, and my nexus 10 froze up. This is pretty normal as it freezes up alot and i have to hold the power button down for 10 seconds and restart it. But it went to the bootloader screen and now its stuck in there. I have never rooted my device or have never even attempted to, my device has been stock since day 1. Pushing the RECOVERY MODE, RESTART BOOTLOADER, START buttons do nothing but restart the device into bootloader. I have searched up and down these forums for a solution and cannot find anything, everything thats related with this problem is because of a ROOT, once again i did not root or have ever attempted to root my device. please help. here is a youtube video with the problem. BTW my device is not recognized in windows either.
Edit: so i cant post a video cause im new on the sight. Im really stuck on what to do here.
Click to expand...
Click to collapse
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
charesa39 said:
So if you hold both volume buttons + power button, then select "Recovery Mode" with the power button, it just reboots back to that same exact bootloader screen? You don't see the Android laying on it's back with a red exclamation mark over him?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
razrus said:
I was finally able to get it to a screen by holding the down volume + power that says "downloading do not turn off target nexus 10", but that still did nothing. Thats the only thing that it will let me do besides constantly rebooting to the same bootloader screen, no matter which option i choose.
Click to expand...
Click to collapse
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
charesa39 said:
That's the Samsung Download Mode, which is different from the bootloader. Could it be possible that your volume button may be stuck, and that's why it keeps bringing you back to the bootloader? I mean, you should at least be able to boot into Recovery Mode. If not, the only solution I can think of is unlocking the bootloader and flashing the factory image. Maybe your partitions got corrupted somehow?
Click to expand...
Click to collapse
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
razrus said:
I dont think the volume button is stuck, when i select recovery it just restarts and vibrates twice. When i power it off and start it it vibrates once, dont know if that helps. I also remember my battery being below 15% when it froze up. My device has froze up alot since the day i got it, is that normal? maybe it did destroy the partitions.
Click to expand...
Click to collapse
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
charesa39 said:
Hmm. Well, I can tell you I've never had a freeze up on mine. However, I did only buy mine a year ago, back in April of 2014. So I've pretty much only run KitKat on it before Lollipop now. Also not sure if they made any hardware revisions to get more reliability later in the device life cycle. I also pretty much only use it for media consumption like watching videos, so I'm not really doing any taxing processing tasks on it. It's weird that it vibrates twice when you try to boot into recovery. You mention your battery was low when it locked up. Have you left it charging while powered off for a while?
Click to expand...
Click to collapse
Really? Never froze? mine would freeze all the time, especially watching youtube videos, i just thought it was normal haha, maybe something was actually wrong with it this whole time. Ive had it for a little over a year now. The battery did die when i left bootloader on over night, but automatically started itself up into bootloader when it had some charge. i might just contact google at this point to see what they say, like i said i never have rooted it or did anything other then normal usage. maybe they can help me.
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
razrus said:
So I called google and they transfered me to samsung, and samsung transferred me to google. no one seems like they could possibly help me. This is frustrating and i dont think ill buy another nexus tablet, or anything nexus for that matter. i dont even think i can sell this on ebay at this point, and if someone were to be able to get it up and running, all my data might still be on there. ARRRGGGHHH ive never owned something that has "bricked" and not been able to fix it. this one looks hopeless.
Click to expand...
Click to collapse
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
charesa39 said:
That sucks. I can empathize as I (and I'm sure plenty of others) know how it feels to get the runaround. Always frustrating. Well, I am thinking the only shot at possibly getting it working again is to unlock the bootloader and flash a factory image. Chances are always good that with a Nexus (barring any hardware issues), flashing a factory image will get it running again. That's why it's Nexus only for me, as Nexus devices are virtually unbrickable. Not sure if you have any experience with Fastboot and ADB. If not, I'm sure you can find some useful research tools on the interwebs and here on XDA. Once you understand it, here are a couple threads with some simplified installers: http://forum.xda-developers.com/showthread.php?t=2588979 and http://forum.xda-developers.com/showthread.php?t=2317790. Do keep in mind that UNLOCKING THE BOOTLOADER ERASES YOUR DATA, so you will lose everything on your N10. But at this point, it's all about getting it working again so you're not stuck with a $300 paperweight.
Click to expand...
Click to collapse
Is it possible to flash even though it's not recognized by windows?
razrus said:
Is it possible to flash even though it's not recognized by windows?
Click to expand...
Click to collapse
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
charesa39 said:
It's not recognizing it because you need the drivers so it knows it's connected in bootloader mode.
Click to expand...
Click to collapse
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
razrus said:
i have the device up and working now! Thank you so much for you help! I had to unlock my device with the nexus root toolkit after installing that usb fix you suggested, then i had to flash it, but the 5.1 update would get stuck in a bootloop, so i installed 4.4 and it worked. Lost all my data but thats ok. Thanks so much.:highfive:
Edit: Google play was not working, tried updating android software and it got stuck in the bootloop again. will try and tweak it more tomorrow, im gunna look for other custom firmwares as well, dont have to have stock anymore.
Click to expand...
Click to collapse
That's great to hear. I'm glad it came back to life. :good: Although, I wouldn't suggest using a toolkit. In my experience from what I've seen around these forums, they tend to cause more harm than good. It's good if you understand everything that's going on, and they can prove useful for devices that have really complex unlocking and rooting procedures, but Nexus devices are so easy to unlock and flash manually. I always flash each image file manually so if something goes wrong, I know exactly where it went wrong and how to fix it. The Google Play issue you mentioned is a perfect example. Flashing manually also helped me learn the basics of Fastboot and ADB. So if you want to stay on stock 5.1, I would recommend reflashing the factory image manually. I always use this thread to help me out in case I forget something: http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. Although it's for the Nexus 6, it's the same procedure for the Nexus 5, Nexus 10, Nexus 7, etc. That's the real convenient thing about Nexus devices as well, as they are all pretty much flashed the same way. Should all be really simple since you already have the drivers set up from installing the toolkit. Good luck! And have fun with your newly revived N10.
Hey XDA members
I need urgent help to help me restore access to my phone, as you can see in the title my device is stuck on the Galaxy S4 Screen, wont go further (apart from a few lucky times hardly ever and will restart anyway).
I have no idea how this happened, my phone is fully stock, not custom roms or root or anything. i was just using my phone normally and all of a sudden it turned off and it just happened from there on, its been happening all day and it has really p****d me off because i am unable to keep up with work now and my phone pays a vital part in my life.
It's not water damaged as far as i know and i cant even factory reset it because it freezes in the process of going into system recovery mode and restarts, same goes for download mode. i really dont know what to do the PC Doesn't recognize it anymore either and its not got warranty.
The only possible thing i can think that has gone wrong is i was charging my phone in the USA Whilst i was there during the summer. but that was about 6 weeks ago and it just happens so randomly so i doubt it could be that..
Has anyone has a similar problem and can give me any solutions or advice i would greatly appreciate it.
- Kind Regards.
ThePlacid said:
Hey XDA members
I need urgent help to help me restore access to my phone, as you can see in the title my device is stuck on the Galaxy S4 Screen, wont go further (apart from a few lucky times hardly ever and will restart anyway).
I have no idea how this happened, my phone is fully stock, not custom roms or root or anything. i was just using my phone normally and all of a sudden it turned off and it just happened from there on, its been happening all day and it has really p****d me off because i am unable to keep up with work now and my phone pays a vital part in my life.
It's not water damaged as far as i know and i cant even factory reset it because it freezes in the process of going into system recovery mode and restarts, same goes for download mode. i really dont know what to do the PC Doesn't recognize it anymore either and its not got warranty.
The only possible thing i can think that has gone wrong is i was charging my phone in the USA Whilst i was there during the summer. but that was about 6 weeks ago and it just happens so randomly so i doubt it could be that..
Has anyone has a similar problem and can give me any solutions or advice i would greatly appreciate it.
- Kind Regards.
Click to expand...
Click to collapse
Your power button is stuck/faulty. Try to wiggle it loose or replace it.
Lennyz1988 said:
Your power button is stuck/faulty. Try to wiggle it loose or replace it.
Click to expand...
Click to collapse
YEHH I tried that, i also tried taking the phone apart and powering it on without the powerbutton but still its the same it freezes on that screen, i tried a new battery same outcome. what can i do guys?someone must be able to help
Had the same with 4.4.2. Do a factory reset, should work. Although all of your data is gone that way.
I suspect you have a hardware problem. Take it to your nearest repair centre.
mathieu3004 said:
Had the same with 4.4.2. Do a factory reset, should work. Although all of your data is gone that way.
Click to expand...
Click to collapse
Thanks for your help, although i cant access System Recovery because: 1. it either freezes whilst it's loading, 2. the phone turns off before it even tries to load
thundastruck said:
I suspect you have a hardware problem. Take it to your nearest repair centre.
Click to expand...
Click to collapse
Thanks for your help,
I also suspected it was a hardware problem but im trying to figure out what exactly is wrong, i was guessing a short circuit but i cant be entirely sure, do you think it could be something else?
ThePlacid said:
Thanks for your help,
I also suspected it was a hardware problem but im trying to figure out what exactly is wrong, i was guessing a short circuit but i cant be entirely sure, do you think it could be something else?
Click to expand...
Click to collapse
The simple answer is no, I don't.
Considered the info provided I think you're out of options, unfortunately. Sorry mate, repair centre is my humblest opinion.
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
xgerryx said:
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
Click to expand...
Click to collapse
To me that looks like a HW issue!
xgerryx said:
My screen is half green but only in some screens. I just installed a version of viper trying to get it to work on android 11, it didn't and I removed it. After I rebooted, this happened. Also having no sim card detected if that matters.
Edit: Seems like it's happening in apps now too, not on reboot, like for instance the unlock bootloader warning is normal. Fastboot is also fine, no green. I do see it in the recovery screen where you choose your language though.
Edit2: Reflashed Android 11, installed Magisk on both slots and it's still there when it booted back up
Edit3: I wiped all data and flashed the ROM through fastboot and it got worse. Now the bootloader screen is completely green are are the dots around the boot animation. Do I contact support at this point? Seems like it got worse as time went on..
Anyone ever seen this?
Please help
Click to expand...
Click to collapse
Flash it back to normal factory built
Sent from my IN2023 using Tapatalk
Bad turns to worse. Now stuck in crashdump mode, can't get into edl. Pretty screwed right now
xgerryx said:
Bad turns to worse. Now stuck in crashdump mode, can't get into edl. Pretty screwed right now
Click to expand...
Click to collapse
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
FreshlyBaked 420 said:
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
Click to expand...
Click to collapse
I can't get edl mode to stick. Once I release the volume buttons after it's plugged in it just reboots. Won't stay in edl so I can't use the msm tool.
Tried both USB 2 and 3 ports, no difference. Could be a driver thing but nothing I've tried has enabled me to update the qc drivers. Can't get the ones built into the phone obviously.
Nothing is backed up.
So now holding volume up and down and then connecting to PC just brings up fastboot every time. Not even recognizing the driver anymore in device manager.
Update....finally got back into the OS after hours of trying things. Ended up flashing all the img files manually and booting back up. Hugeeeeeee issues. See pictures. The phone is going back.
xgerryx said:
Update....finally got back into the OS after hours of trying things. Ended up flashing all the img files manually and booting back up. Hugeeeeeee issues. See pictures. The phone is going back.
Click to expand...
Click to collapse
That appears to be a loose flex cable to the screen. Shame it can't just be popped back in. Careful when sending it back as they may look at it and suggest it's been dropped (not saying you have) I've worked in the mobile industry in my younger years and we would certainly query this is it came into our shop.
Hopefully they take it in and deal with it, give you a brew device.
Certainly wouldn't be happening pal.
dladz said:
That appears to be a loose flex cable to the screen. Shame it can't just be popped back in. Careful when sending it back as they may look at it and suggest it's been dropped (not saying you have) I've worked in the mobile industry in my younger years and we would certainly query this is it came into our shop.
Hopefully they take it in and deal with it, give you a brew device.
Certainly wouldn't be happening pal.
Click to expand...
Click to collapse
It's funny you say that something could be loose, I have no idea how. I've only had that replacement device for about 2 months and I've never even tossed it in something other than the bed or a chair, normal handling of a device, let alone dropped it. I hope they deal with it though, between the screen and the extreme overheating I wouldn't doubt that something is fried at this point. There's not a scratch on the device.
Waiting for them to send an email about the repair so I can send it back.
xgerryx said:
It's funny you say that something could be loose, I have no idea how. I've only had that replacement device for about 2 months and I've never even tossed it in something other than the bed or a chair, normal handling of a device, let alone dropped it. I hope they deal with it though, between the screen and the extreme overheating I wouldn't doubt that something is fried at this point. There's not a scratch on the device.
Waiting for them to send an email about the repair so I can send it back.
Click to expand...
Click to collapse
Well the overheating could have been a poor contact with the heatsink (more than likely)
The loose connection if it is that won't be your daily as they should clip in, if this is a refurb then that's probably your answer.
It's a weird one but you've just got to roll the dice mate..
All the best of luck with it..
If you can, try to talk to a tech from OnePlus about it.
Get some clarity if possible.
FreshlyBaked 420 said:
Msm tool will bring it back. Hopefully you have backed up persist.img just in case.
Click to expand...
Click to collapse
I have persist.img backed up, but bootloader is locked as I tried to msm.
Anyway to flash it?
areyouanand said:
I have persist.img backed up, but bootloader is locked as I tried to msm.
Anyway to flash it?
Click to expand...
Click to collapse
Check out this thread about the persist.img
https://forum.xda-developers.com/on...de-fix-persist-img-loss-finger-print-t4125909