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
Related
Ok, I went to take a picture and it freaked the **** out. Now I rooted my phone when I got it, I have done nothing else other then Xposed modules and since it start acting up I've literally done nothing else. I only get the screen that says custom and then blah nothing else. I swapped battery (got another battery from samsung directly) and I have no idea wtf to do. Don't recommened ****ing flashing **** or whatever because I have everything stock. This should not happened. I wiped dalvik cache and cache and it was within recovery but my phone can't boot, I removed SD card, sim card and sometimes it'll boot be on for a couple minutes and bam same issue.... WHAT THE FLYING **** CAN I DO? I need this phone ASAP.... I'm this close to just tossing it over the edge and getting a new one.... it's a flying piece of **** and **** samsung!
You might have to start from scratch and determine if it's a hardware issue. Do you know what firmware you're on? Also back everything up because if you start from scratch, we'll that's the what you'll have.
Thanks, I managed to get it on again, made some calls uninstall some apps, but then it ****ing freaked out again. I have the firmware that was on when it was released. I got the first batch of 32gb's S4's haven't changed the firmware since... to prevent this type of ****. UGH! So after a phone call my phone just bleeped again and ****ed up. So I don't understand anything anymore.
rubsnick said:
Thanks, I managed to get it on again, made some calls uninstall some apps, but then it ****ing freaked out again. I have the firmware that was on when it was released. I got the first batch of 32gb's S4's haven't changed the firmware since... to prevent this type of ****. UGH! So after a phone call my phone just bleeped again and ****ed up. So I don't understand anything anymore.
Click to expand...
Click to collapse
So you used odin to flash mdl firmware?
I've done nothing in regards to flashing. I have not connected my phone to my computer. I've done nothing at all. other then keep trying to turn it on over and over again.
rubsnick said:
I've done nothing in regards to flashing. I have not connected my phone to my computer. I've done nothing at all.
Click to expand...
Click to collapse
Well you might have to to see if it's a hardware issue. I would suggest flashing the firmware you're currently on through Odin
How am I supposed to do that if the phone just won't be recognized by anything? it's ****ing dead now. It shows me the Samsung Custom lock and logo and then nothing. I press the power button and nothing, I have to remove the batter and put it back in to see that screen.
Ok now it randomly is charging and now I can turn it on again, no problem, after I forcefully press the power button and some other random things... could I have an issue wiht my power button staying pressed? why would it do that? how can I fix this? I'm willing to open it up. I'm currently doing a backup in titanium backup and so far it seems ok. Recieved a phone call, phone is charging and everything is ok. how do I boot it into safe mode?
http://m.samsung.com/us/support/faq/FAQ00052827/62062/SGH-I337ZWAATT
Thanks, I believe the cause was a stuck power button.
I've had this Motorola Droid RAZR for like two years now and a friend of mine took it and worked on it, adding something called "Cyanogen Mod" and he 'rooted' it I believe? Ever since, phone has worked great. However, today I tapped the home button and the whole screen had a weird visual glitch where the wallpaper was entirely intact but the icons and such were only half appearing, like someone scratched them out with fingernails or something. It would go away and come back so I got frustrated and rebooted my phone. It starts up normally and goes to this screen where you can do different stuff with Cyanogen mod (like changing the rom? or changing boot options) and usually I just continue past that because for 1) I know nothing about it and 2) It always was fine. But when it did the typical boot up, it just skipped back to the first screen you get when you turn the phone on and repeats. It never goes to the second part of the Cyanogen Mod where the words appear and the little thing spins, it simply skips back to the screen you get when you power up and repeats. It keeps doing this and I looked online how to fix it, tried about twelve different things (like restoring different aspects and using different roms or making new roms) and it just didn't work. Eventually it got bugged out where the screen was just black, couldn't get it to do anything but reboot and go back to black. I let it sit until the battery ran dry I believe and now I'm at a brick wall.
Is there a way I can totally just revamp and start fresh? Like remove all of it and reinstall Cyanogen mod/the OS and all that jazz? I don't mind losing everything if I can just keep the phone, I don't pay for a cellphone and I don't want one I just use the droid for texting apps/games/reddit/etc. If anyone could help me save this thing I'd appreciate it.
Hi there,
Please stand by until mods will move this thread to the related forum for Droid RAZR.
For reply or ask other questions you must register an account.
Stand by
Hello? Can Somebody help me out, I've waited a couple days now and no one has said a thing?
You have safestrap installed, correct? If so, what version?
Dr. Mario said:
You have safestrap installed, correct? If so, what version?
Click to expand...
Click to collapse
How would I know if I had it installed? I remember when I booted up the phone something came on with a picture of a little robot that said "Safestrap Enabled" and then when I had this problem it was saying "Safestrap Disabled". I can't get the phone to turn on right now though, is there a way I can check what version I have another way?
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Dr. Mario said:
Ah. I see. First. try entering Safestrap menu upon rebooting, instead of allowing it to boot normally, and look at ROM slot and see if custom OS' ROM slot is active. If it's there and is not active try reactivate it. If it won't budge, get microSD card and find XT910 (RAZR - spyder) CM 11. If you don't know what to pick, I will look in a bit.
Click to expand...
Click to collapse
Just tried booting it up, nothing is working I think the phone is dead. I plug it into the charger and only the notification light on the top left goes on a blueish white and stays on as long as it is plugged into the charger. Nothing will turn on at all and the phone doesn't seem to respond to anything. Is my phone just dead..?
Soft bricked. Try pushing both volume down and up button while plugged into either computer or charger, and hold down power button until it boots. I hope you won't need to buy Motorola factory cable at this point.
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
ATTACK said:
Let your device charge for a few hours until it boots up. Then boot it into APfastboot and flash the stock firmware with RSDLite.
Click to expand...
Click to collapse
In English please?
Edit: Just plugged it in like you said and instantly the boot screen came on rather than simply that silly light so I think my phone is improving but I still would like to entirely revamp it or redo it or whatever you wanna call it so that everything is fresh and new and my phone is okay.
Good. I think it could be because the battery died somehow. Good thing the protection mechanism on the bootloader didn't have the wild idea of disabling the phone.
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.
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
No fastboot or custom recovery ?
Then no theirs nothing really to do
Maybe a battery replacement would boot it up
Sent from my ONEPLUS A6010 using Tapatalk
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
easyxpress said:
No fastboot or custom recovery. I'm wondering if the *storage* can be pulled out like a hard drive?
Click to expand...
Click to collapse
Nope it's just a chip on a circuit board
Sent from my ONEPLUS A6010 using Tapatalk
easyxpress said:
I am unable to boot up the device. I tried all (power + Vol Up) key combos, not working. Is there anyway to pull data out from the device?
Click to expand...
Click to collapse
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
twistyplain said:
Not enough information. What did you do prior to your phone failing to boot? Was there a software mod you installed? What were the symptoms the phone showed the last time it was on? Any problems before it failed to boot like an old battery, misbehaving ROM, poor charging?
Basically, you need to identify (help us identify) the cause of your phone not booting. We cannot find the solution to a problem we don't know the cause of. The problem must first be defined and then we work from there.
All the best.
Click to expand...
Click to collapse
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
easyxpress said:
Prior to the phone failing to boot, the phone kept crashing. I saw the screen turning into *mess* and then the phone shut off by itself. Initially, I was able to boot up the phone after the crash, however the screen would get mess up and shut off again after a few minutes. Eventually, It got harder and harder to turn on the phone until it finally failed to boot (die). At this point, the phone seems dead. When I plug in the charger, there is no response of any kind, just black screen.
At one time, when the phone was on its last legs, I was able to boot into the Recovery mode, the phone seems to stay in that mode without the crash. Unfortunately, I didn't stay long enough in the Recovery mode to confirm this.
The phone was running on Lineage of Android 8. I have been using the phone for two years, the battery is surely weakened but can still last an hour or two for continual Youtube watching. I didn't do any software update after the Lineage Android 8's last nightly build.
Hope you can help and give some pointers. Thanks.
-- Joseph
Click to expand...
Click to collapse
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
twistyplain said:
This appears to be hardware failure. The SoC is most probably dead. You should have recovered your data when it was still able to boot. Right now I think it's too late.
Click to expand...
Click to collapse
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
what happened to TWRP ? thats stock recovery
will it enter fastboot mode ? if you can get into TWRP their is a chance of off loading your userdata to a PC
easyxpress said:
I just plugged in the phone. Miraculously, after few minutes, it did come up with the boot screen (with some messy lines), see the attached picture. However, It didn't go beyond the boot screen and recycle again for 2 or 3 times and then no more. I was able to duplicate this recycling situation several times after plugging it to the charger. Also, I was able to push it into the Recovery mode, but it only stay at the boot screen (with lines) and shut off again after few seconds.
What do the messy lines on the boot screen suggest? Is it the battery totally dead? Or, is the charging system faulty that somehow it doesn't have any enough juice to push thru beyond the boot screen and hence shut off?
-- Joseph
Click to expand...
Click to collapse
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Sent from my LeMobile Le X526 using XDA Labs
twistyplain said:
Yup...This phone is dead. I have seen a similar le pro 3 posted here on XDA with the same streaks along the display. It's definitely a hard brick. No way to get around it that I know of. I'd like to rope @tsongming in on this. He has seen a few dead pro 3's so this is within his expertise.
Click to expand...
Click to collapse
Sorry bad news.
As twistyplain said, your phone is absolutely fried, and there is no solution.
It's definitely no brick, that is a hardware issue... Most likely shorted solder connections. The same thing happened to two of our X727s, we have one left that still works.
I highly recommend buying a seemingly unbrickable Xiaomi phone. Their budget models are awesome and of course their flagships are awesome. Everyone in my family has Migrated to Xiaomi . I currently have Android 10 working flawlessly.
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
easyxpress said:
Thanks for the info. I made a mistake of not backing up the photos from the phone. I'm still hoping for a slim chance and searching that some of the repair shops (in China?) are somehow able to boot up the phone and retrieve the photos for me. Meanwhile, I'll check into Xiaomi.
-- Joseph
Click to expand...
Click to collapse
If you are in China and located in a large city or tech industrial area you should have plenty of shops that repair at the component level.
Your phone could very likely be repaired by a shop that has a hot air rework soldering station with an electron microscope.
We used to have these types of places in the US but they have all gone out business, replaced by board swappers, who charge a lot. I would suspect that you could get it repaired in China for 100 yuan or less.
I worked in Beijing for 3 months, about 18 years ago and these types of places were everywhere.
Hi! I was wondering if what happened to me it's normal and so I thought about asking here.
My phone was on my desk, I had looked at something a couple of minutes before. I grab it again and... Crashdump Mode. I pressed the usual combination of keys (I think it was Vol+ and Power), the device turned off and then rebooted in Lineage OS. No problem, no data lost, nothing.
While searching for this I met all kind of horror stories and so I wonder... is what happened a sign of more trouble along the road (faulty hardware that is going to only get worse, for instance) or it can happen without it pointing to any larger issue?
EDIT: also... I am rooted. Could anyone point me to an absolute idiot's (that would be me) guide to do a full backup of the phone? Before it happens again and I end up being SOL.
No ideas?
gorman42 said:
No ideas?
Click to expand...
Click to collapse
I am new to this as well, as long as your device boots up it is not hardware error. You can back it up and try to fully reinstall using MSM tool and check if it happens on official OOS...