Develop Bugs

[Q] Did I get a bad Galaxy Nexus?

It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?

Try to do a clean install ... or wipe your cache and Dalvik cache

and your bone stock I would DEFINately bring it back ive installed countless roms and kernels and never pulled battery yet you didnt need to spend your money on a defective phone

irizwan said:
I believe theres a rouge app responsible .. try a clean install then don't install any apps then check
Click to expand...
Click to collapse
He just said he did this.
Anyways, try flashing a kernel and raising the minimum value slightly, saw this fix every SoD on the G2x forums. You'll need CPU Master or something similar.
I'm using CPU Master Pro, in case you were wondering.
Sent from my Galaxy Nexus using Tapatalk 2

Unroot and reroot. Problem should be solved.

Sarumiso said:
It looks like I've got serious sleep of death issues. Here's what's happened so far.
I got the phone on Thursday afternoon. As soon as I started it up, it performed an update to 4.0.4. After entering my account info, a bunch of my old apps were restored and I installed a few more. Thursday night, the phone froze in sleep mode and I couldn't wake it up. Pulled the battery and everything was fine, didn't think too much about it.
Friday I got two similar lock ups, one in the afternoon and one at night. Had to pull the battery both times. I uninstalled any apps that I was no longer using or did not use too much.
Saturday three lock ups! Once while connected to the wall charger. At this point I uninstalled every downloaded app and powered the phone off overnight.
Sunday morning (today) I got a lock up in the morning and finally did a factory reset and did not allow any old apps to be imported. The only thing I have installed now, besides the stock apps, is Google Voice. And my phone just locked up again...
Is there anything else I can do at this point or should I just send this back to Google for a replacement?
Click to expand...
Click to collapse
Install a custom kernel and change your minimum CPU to 700mhz. Fixed my sods. Honestly though I'd go for an exchange.
Sent from my Galaxy Nexus using xda premium

Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA

Toad858 said:
Please update as i am planning on getting a gnex from the play store soon and would like to know what happens
Sent from my SAMSUNG-SGH-I897 using XDA
Click to expand...
Click to collapse
Just get the Gnex, geesh. There's lemons with every product, not just phones.
Sent from my Galaxy Nexus using Tapatalk 2

Might be a bad Sim card

Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.

Sarumiso said:
Thanks for the advice everyone. I ended up contacting Google who transferred me to Samsung for an RMA. During the course of the call, they had me try to reset the phone from recovery mode and I found that my phone can't go into recovery mode. Holding VolUp + Power resulted in a regular system boot. If I go to fastboot and try to enter recovery, I just get a little droid lying down with a red triangle and exclamation point.
At this point I'm thinking that first upgrade to 4.0.4 must have been corrupted somehow. I'm looking at trying to reflash it via Odin since I'm not looking forward to a week or more without a smartphone and the fact that the Samsung rep made me a little nervous by the number of times she said "might", "maybe" and "possibly" when talking about not charging me for a second phone during the RMA process.
Click to expand...
Click to collapse
To go to Bootloader mode requires VolUP+VoldDOWN+Power button

suggest returning defective phone
You phone seems defective.
I realize you don't want to send it back, but getting stuck with a bad phone can drive you crazy.
When I bought my Evo 3D phone a year ago, after the update, it started to reboot at random times. After talking to their support, with no solution, I insisted on a new unit.
Once I got the new phone, I had no problems ever again.
Now I have the Galaxy Nexus, and I used it a lot the first few days to make sure it wasn't defective.
I hope you can find a solution, but if you don't, consider getting a new unit. It's not worth the hassle of keeping a questionable unit.

Have u tried to unroot yet??? It fixes all the problems u could possibly have.
Use Wug's toolkit to fix this issue.

[Q] Possible Brick

I decided to ROOT my phone, which seemed to be sucessful, and then I attempted to install a Custom ROM (where the problem began). This ROM used the AROMA installer and all seemed to be going fine. I rebooted at the end. I wasn't watching my phone at this point because I'm used to reboots following ROM installs taking a while so I just ignored it a bit. When I looked back finally, the screen was off. I figured that it had just gone to sleep but I couldn't wake it up.
What's worse is that I cant get it to turn back on at all! I've tried pulling the batter, hard reset (Power + volume up and power + volume up + home key). Nothing. Is there any advice anyone can give me? What did I do wrong and is there a way to recover the device?

How much battery left you had before flashing?
Sent from my SGH-T999

lazarat said:
How much battery left you had before flashing?
Sent from my SGH-T999
Click to expand...
Click to collapse
I'm not 100% sure actually. was low when I started the root process but I did have the device plugged in the whole time though. Do you think that's the problem? I actually swapped my battery with my GF's battery (which was nearly fully charged) so I don't think its a "dead battery" issue. Any ideas on how I can get it back on? Doesn't even show the charging icon.

Plug it into Odin and see if anything comes up.
Sent from my SGH-T999 using xda premium

Yes your battery died in the process of flashing which sucks bwcause i do not know what are the consequences of it but seems bad since you cannot even get into download mode. Never flash with battery below 50%. Good thing is though that if the phone does not turn on at all then jist go to tmobilw store say left it overnight to charge when woke up was all black screen. Idk whats wrong with it. Get a replacement.
Sent from my SGH-T999

Pull the battery out for like 2-3 mins then let it charge for like 15 and try to get in download mode... If it does pop odin open and flash stock image. You can find it under the stickies in dev section.
Sent from my SGH-T999

I wasn't able to resolve the issue but I was able to take it back to the TMO store and just swap it for another one. The guy didn't ask too many questions. Crisis averted but it's made me hesitant to flash on this again so soon. I've rooted and flashed dozens of Android devices for myself and others over the years but this is the first time something like this has happened to me. Being careless I suppose. When I get my nerves back up, I'll be back.
Thanks for all the help you guys offered. I appreciate it.

Is this what a hard brick tastes like? (Not a MM thread)

Well, I'm at wit's end. I'm usually pretty decent at borking and consequently unborking a phone. But I think I'm stumped this time; and am hoping that the community here can help me out. Though, to be fair, I suspect that rolling back to my old phone and eventually buying a new one is my only recourse.
So I imported an H815 Open EU from Handtec UK. No real issues on that front. I eventually unlocked the bootloader, flashed TWRP, and used the KDZ method to (clean) flash my way up to Europe OPEN H81510D initially, and then around two months ago, to Europe OPEN H81510E. I've been running that software without issue since that clean flash. And all this time I've been rooted through the TWRP method.
While this is (was?) my first LG phone, it isn't my first Android experience. So I've been using TiBu to back up my apps nightly, was running Kickoff's lovely hybrid theme, and had a few Xposed modules activated to tweak my experience a bit from stock behavior. I was curious about Marshmallow, but autoprime's warning that it could be non-final test software and the fact that Xposed doesn't work on it kept me from indulging that curiosity.
Everything has been going swimmingly until today. No major issues that I couldn't solve on my own. Certainly nothing that booting into recovery and clearing caches didn't fix. I was out and about engaging in a chat via Hangouts with a friend when my phone suddenly crashed and black-screened. I wasn't plugged into the wall or my PC, and I hadn't performed any kind of major update since the 10E flash a month or two ago. I had not installed any new Xposed modules or any rogue Google Play store apps. I was just using my phone normally and it crashed.
I popped out the battery and played around with it, trying to get it to boot up. I couldn't access recovery or even get beyond the LG logo. It would just hang there and after a few seconds, black-screen. Only popping the battery out and reinserting it would allow me to try again. I eventually left it alone until I got home, at which point I figured I'd try for download mode and reinstall the 10E KDZ via a CSE flash. It's always been a last resort, but a reliable one. I successfully performed the CSE flash of the 10E KDZ.
I thought it did the trick, as I got past the static LG logo for the first time and saw the LG boot animation, but it hung towards the end of the animation and black-screened again. Tried a few more reboots. Recovery mode still not accessible. Download mode was only accessible every third or fourth attempt. Finally got back into download mode and figured I'd try to roll back to 10D (I still had the KDZ I had previously used saved, just in case). Everything seemed to start going fine. Download mode's circle arrow animation on the phone was doing its thing, and then I hear the USB connection drop out. The arrow animation hangs, and the phone black screens. LG Tool 2014 spits out an error I can't read (the software is all question marks for me at this stage). Before it black-screened, it appeared that download mode hadn't progressed beyond 0%.
Now the phone is completely unresponsive. Popping out the battery and reinserting shows no signs of life. No USB sounds from my PC. No static LG logo. No recovery mode or download mode. Not even the lonely flash of an LED.
I've never had a phone hard brick, but I imagine this is what it tastes like.
So I'm probably out of luck, right?
I apologize for the long story. Thanks in advance for sticking around.

Maybe a stupid question but still deserves to be asked, what does pluging the phone in a wall socket gives you?
Sent from my HUAWEI MT7-L09 using Tapatalk

that is strange to happen randomly. The same thing happened to one of my old devices, a 1st gen moto atrix after I dropped it. I can get it to boot up but eventually it acts like the battery is pulled and just reboots. I'm convinced some wires or chip has been damaged inside even though it was only a 2 foot drop on thick carpet... not a whole lot you can do off warranty. Good luck.

Yeah, I figured the phone was toast. Of course the only time I hard brick a phone, it'd be the one time I import one from another country. Alas.
I think I'll return to my Galaxy S4 for now and pick up a Moto X Pure in a week or two, if no other ideas or opportunities present themselves.
As for having the phone plugged in, I just mentioned it in passing in order to rule out a power surge or short or whatever. Just to be completely clear about what I was doing with my phone.

There are already a few other threads on this man. Try to read first and post. Probably it's a motherboard problem. See the date of manufacturing of your device.

I read completely through the first 5 or 6 threads I saw on bricks and was overwhelmed by Marshmallow woes. Mobo, huh? That's a damn shame. Thank you.

Marshmallow broke my phone so I...

Installed CyanogenMOD and it still resets, locks up and has other performance related issues.
I did an OTA update to Marshmallow originally. This corrupted my SD card and then caused about 10 resets a day, ranging from when I was using it lightly to heavily or even when it was sleeping/screen off. If I woke it up it would reset or I could feel it reset when it was in my pocket.
First thing I did was a factory reset. I tried other tricks such as swapping out the battery, SD card (or none at all), clearing cache, etc.... Nothing worked. So I tried installing CyanogenMOD, and I failed. But I got the phone back to BPA1. I updated back to marshmallow via my computer and the Verizon software updater.
About a day later the resets and lockups came back. I kept it light of apps but did slowly begin to reinstall some of my usuals (from the play store).
I had some more time so I tried installing Cyan again and was successful. It took a long time to load and optimize but it worked. I used gapps mini and the only step I did not follow in the guide was I did not install xposed.
It's been running for about 12 hours and has hanged, locked up and rebooted on me multiple times. Chrome even locks up (it will stop resounding, I'll get the message asking if I want to wait or close at the same time it starts responding again.)
When it reboots, it still takes forever and even optimizes apps (that I assume have already been optimized). I've seen two boot screens for it, one the little alien guy and the other with gears turning. It did the gears the second time I booted and then I haven't seen them again.
I'm not sure what my next step should be. Maybe I'll try reflashing Cyanogen. I have a feeling it's a hardware issue at this point, but I'm open to ideas. Are there any good diagnostic tools that could help my situation?
The phone is out of warranty and I'm sure that now that I've installed Cyanogen, the warranty was voided anyway. It's a shame because this phone was perfect up until the marshmallow update. I probably had 5 lockup/boots in the year or two I've had it.

Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.

HORIZONx720 said:
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
Click to expand...
Click to collapse
Admittedly, I did not even know about lineage until my phone was wiped with no OS. I did a quick Google search for it but could not find a Verizon note 4 mod. Now that I am not pressured to find a fix, I'll research it a bit more. Thank you.

I tried EmotionOS and NSeven, but both share the same error.
Emotion FCs random processes sporadically and then when my cell/data switches to Searching, it crashes multiple processes until the UI (trebuchet is default for Emotion?) and/or settings FCs and I have to restart. I am also stuck on 3G on that platform. I'm guessing network connectivity / switching is the root of the problems.
Nseven installed and right at the Welcome Screen where I pick my language, Google Play Services started crashing. I only had the option to click OK and then every 5 seconds after that, it kept crashing. I set up the phone, restarted and Google Play Services started crashing again. I am in the process of restoring back to Emotion, as it is the most stable platform so far.
I tried a new SIM card, hoping this was the problem but to no avail.
Does anyone have any other suggestions? I'm guessing its hardware at this point, but since it happened on an OTA Update and I can reproduce the same errors every time, I'm hoping there's still an option left for a fix.
Holy crap. As I was typing this and restoring Emotion, it fully installed and booted. I have 4G! I don't know if that will fix the FC issues, but I have regained a little hope!

I'm still getting FCs and restarts. The more I use it the more it happens, but at least with EmotionOS, It's more limited. Only about 3 or 4 a day compared to 10-20.
I'll try one more flash and I guess tough it out until my contract is up in April.

I can't help you with EmotionOS (haven't tried it yet), but if you want to stop the Google Play Services crashing in NSeven you can make your way to Settings - Applications, then select Google Play Services - Permissions and give it all permissions. It's a bit of a chore to get there when the warning pops up every five seconds, but it will stop once you do that.

So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.

Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.

trickyvinny said:
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
Click to expand...
Click to collapse
I know a lot of people are blaming software, but I'm fairly certain that the problems in many cases are caused by failing hardware. I went through many of the same trials and tribulations with my Note 4 (except I never rooted the phone). I finally contacted Samsung Customer Support and sent the phone in for repair. They replaced a lot of the hardware including the motherboard and returned the phone in "like new" condition. I've been using it for a few weeks now and the performance is flawless.
I was planning to get either the V20 or the G6 if I wasn't able to get the phone fixed. How do you like the V20?

I'd agree that it's most likely hardware and having to put everything in the freezer for it to when confirms it for me although I have no real expertise to say so. But I'd argue that the update created the hardware issue, it was night and day with the update. It was working 100% and then directly after the update to marshmallow, it started having catastrophic issues. Oh well, it's nice not having to pull the battery every hour or so.
V20 is pretty nice. Having used EmotionOS for a few months the switch to the Nougat was pretty smooth. The xda forums for it are a little more limited but I didn't start messing with my phone until it broke and I'm hesitant to try with a new phone given my limited knowhow.
To be honest it's not a big difference in day to day usage from the note 4. Which I like!
+ I never used the finger print scanner but really like it on the v20. I didn't bother with a screen lock before but now I'm protected and have a just as quick access.
-the grip is too slick, I feel like I will drop it. The note had that rougher back which I liked better. A case or a replacement cover should fix that though.
+ I like this top menu screen, I have quick access to a few select apps or can turn the flashlight on or whatever. I'd like it more customizable, I find I switch screens too much when trying to just pull my top menu down. If I could put everything on one tab and combine their special buttons (ie the flashlight button) with apps, it would be perfect.
-the back button and menu button are switched. I can probably customize that but I don't yet know how and by the time I figure it out, I will have relearned that habit. It actually is probably a better placement for how I hold the phone but I'm a big fan of choices.
+ upgraded camera, sound, storage. I don't notice the screen size difference, but it is a lighter phone.
-bloatware
All in all its a good shift from the note 4. I'm happy to be off of Samsung and still have the same basic user experience.

trickyvinny said:
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Click to expand...
Click to collapse
I have had the exact same problem with my note 4. It wouldn't last 30 seconds at a lock screen from a cold battery before it would start boot looping, and the longer you left it in, the worse it got. Google told me I needed a new battery from several other forums and places I read. So I ordered one and replaced with a genuine Samsung one direct from them, and it didn't change anything.
I figured out it was heat related and I had it sit on an ice pack and it would run and work fine as long as the ice pack held out, about 2 hours. I've down graded, flashed, rooted the boot loader, installed a recovery console, flashed to different versions, all have the same problem. So I've kind of reserved myself to the fact it must be a hardware problem. Perhaps it was caused by the update, but nothing software change wise seems to be able to fix it. Did wake-loc fix as well. I've spent the last week with mine trying everything in the world and every evening having it on the ice pack hooked up trying whatever I could think of or read up on doing, and basically as soon as it warms up, it starts doing it again.
Heres a pic; http://imgur.com/a/5L64V

In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.

trickyvinny said:
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
Click to expand...
Click to collapse
Just out of curiosity, what phone did you wind up going to?

The LG v20 and so far so good!

Phone is bricked, can't load into recovery and can't turn on without being plugged in

This phone is quite old but I've only recently had the courage to open it up to try to fix it.
I've tried to flash the stock firmware when I could access recovery mode but it says that it couldn't install it from the SD Card.
I've tried plugging it in to my computer but the phone doesn't boot.
The phone wasn't rooted or messed with in anyway. The battery life on it just slowly went down and down until it is in the state now where it can't get past the boot logo. It doesn't even get to the boot animation either.
I'm just seeing if I can try to restore the phone to its former glory at all, whether it be a parts replacement or a software fix.

Trainer_Red said:
This phone is quite old but I've only recently had the courage to open it up to try to fix it.
I've tried to flash the stock firmware when I could access recovery mode but it says that it couldn't install it from the SD Card.
I've tried plugging it in to my computer but the phone doesn't boot.
The phone wasn't rooted or messed with in anyway. The battery life on it just slowly went down and down until it is in the state now where it can't get past the boot logo. It doesn't even get to the boot animation either.
I'm just seeing if I can try to restore the phone to its former glory at all, whether it be a parts replacement or a software fix.
Click to expand...
Click to collapse
It's a great phone!
Just got mine working.... It was so nicely built.
Of course, it's waaaay beyond really practical but it works well. Even the camera is still good as long as you replace the rear cover-plus-lens
You need to replace the battery...cheap from eBay
Replacing it however, is very difficult to do well so find a shop

kolembo said:
It's a great phone!
Just got mine working.... It was so nicely built.
Of course, it's waaaay beyond really practical but it works well. Even the camera is still good as long as you replace the rear cover-plus-lens
You need to replace the battery...cheap from eBay
Replacing it however, is very difficult to do well so find a shop
Click to expand...
Click to collapse
I actually managed to remove the battery to see if the battery was the problem in anyway. It still acts the same way when the battery is removed. I would spend the money to buy a new battery but I just want to make sure that it is the most likely problem.

Re-download your recovery firmware... Sometimes it's as simple as a corrupt file - is happened to me! Also, Leave it plugged in over night with the battery on.... It won't rescue the battery if it's dead but it's happened when with my last battery it was dead and the overnight got it to at least boot up and switch on before it powered off again.
It's worth getting it running. The only phone slimmer now is the Moto...and that has a huge camera bump!
The screen is great, the colors are lovely and if it's stock firmware, EMUI is at its quirky best.
It's a great feeling in the hands and I'm enjoying using it again.

kolembo said:
Re-download your recovery firmware... Sometimes it's as simple as a corrupt file - is happened to me! Also, Leave it plugged in over night with the battery on.... It won't rescue the battery if it's dead but it's happened when with my last battery it was dead and the overnight got it to at least boot up and switch on before it powered off again.
It's worth getting it running. The only phone slimmer now is the Moto...and that has a huge camera bump!
The screen is great, the colors are lovely and if it's stock firmware, EMUI is at its quirky best.
It's a great feeling in the hands and I'm enjoying using it again.
Click to expand...
Click to collapse
A big problem is that my phone won't install the firmware from SD Card for some reason. I've also tried to charging but that no use.

Have you tried copying the firmware to phone internal memory?

kolembo said:
Have you tried copying the firmware to phone internal memory?
Click to expand...
Click to collapse
It won't boot into recovery when plugged into my computer.
Edit: I managed to boot into system and use the local update function to install the firmware. It works once again! This phone has been dead for a couple years now and I'm glad to see it back now. I ripped the ribbon cable for the battery so I'm gonna buy a new one. Thanks for the help!