Develop Bugs

[Q] screen dead - help

Rooted my Dinc. Installed CM7. All was well for 3 weeks. Used it one day until the battery went dead. Charged and tried to boot. It appears that it goes through the boot sequence (it vibrates) but nothing comes up on the screen. Nada, black.
Any ideas?

Screen might have went bad. You should just try your best to unroot it before you send it in
Sent from my Incredible using XDA Premium App

Have you tried pulling the battery?
Sometimes the phone can get stuck in a state where trying to turn it on results in a series of vibrations but nothing else happening. Pulling the battery resolves this.

Unless flashing a radio, when in doubt pull the battery.

Pulled the battery and re-booted. Nada.
Returned to the Verizon store. Their tech had no luck and ordered a replacement. Verizon ordered a replacement and left me with the phone. They said that when the replacement comes in they will switch it out. I'm hoping that means I've dodged the warranty issue.
Sent from my Xoom using XDA Premium App

elcap373 said:
Rooted my Dinc. Installed CM7. All was well for 3 weeks. Used it one day until the battery went dead. Charged and tried to boot. It appears that it goes through the boot sequence (it vibrates) but nothing comes up on the screen. Nada, black.
Any ideas?
Click to expand...
Click to collapse
That's odd. I had this problem when I went to unroot my phone, being that I had an SLCD and it did not like the 2.1 stock ROM. The screen was blank but it would vibrate and continue to boot.
If this is the case, you could always try to unroot it and see...Here are some instructions on how to do this (its what I had to do)
I went to unroot and flashed a stock 2.1 ROM. Although this sounds correct, there is a problem. The stock 2.1 ROM was made for the release DInc's, and those, my friend, come AMOLED. So by flashing that stock 2.1 ROM, it does not contain the correct hardware drivers to support the display on the newer batch of DInc, the SLCD.
What I did was:
Download the correct ROM that supports the SLCD from here (which can be found on http://dougpiston.com/?page_id=108 )
Rename it to PB31IMG.zip and place that file in the root of your sdcard.
Now since your phone's display doesnt work, like you said it vibrates once, like normal, your phone still functions properly.
Boot your phone into HBOOT and allow it a few minutes (2 minutes to be safe), like normal to find this PB31IMG.zip file. It then will prompt you to press UP to confirm the update or press DOWN to not update. (you will not see this, but if you have flashed a radio then you know this process)
when you press up, it will then start updating to the stock ROM. however, you wont see any of this. just a black screen.
allow that to run, usually for 10 minutes. to be safe wait 15-18 minutes and then press UP. When the update is complete you are asked to reboot. UP for yes DOWN for no. again you will not see this. Then when it reboots....you will be happy and see the HTC Incredible white screen
You can give this a try and see if it works. I know you did not mention unrooting your phone, but if you have nothing on your screen, you can try this

Galaxy nexus keeps rebooting

I have a stock GN, not rooted yet. Today my phone automatically shut off and now it starts back up, google logo shows up and all those colors come on for couple of seconds and then the phone reboots itself.
I can press both volume up+volume down + power button and get into a menu which gives me the options of Start, Restart bootloader, recovery mode, and power off. I choose recovery mode but then it goes on to an android sign with exclamation mark. After that I can't seem to get anywhere. I have tried volume up +power, volume down+power, and volume up+down+power but nothing seems to work. It just keeps on rebooting it self.
Any solutions to this problem??

There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)

....

FredFS456 said:
There are two possibilities:
1) Software problem. Since you were stock, this is unlikely.
2) Hardware problem. This is more likely, in my opinion.
If you want to eliminate 1) as a possibility, you can try this:
1. Download the GNex Toolkit here
2. Install it & get the drivers working on your computer (if you haven't already)
3. Unlock the bootloader by selecting Option 3 (it'll wipe your phone)
4. Flash factory stock rom by selecting option 8
5. Try it. If it works, congratulations. (if you want to re-lock your bootloader, use option 11)
If this doesn't work, relock your bootloader and send it in for warrantee. (most likely a hardware problem)
Click to expand...
Click to collapse
So, I did the above method and after flashing the factory stock rom it won't start up anymore. It doesn't respond to anything at all. It seems I've bricked it
Is there any way to unrbick it now? I'm assuming I can't send it in for warranty either now if it's semi bricked. Unless it's been completely bricked which means there is still a chance of getting a replacement phone.

I have the same prob on rooted SGN
This morning I switched off the airplane mode to be available, system crashed and restarted. And then still the same again - booting / android logo / restart again.. /./. I am using Android Revolution HD 2.1.5, for last month with no problems.
I tried to boot into recovery, then wipe the cache and reflash rom and radio from sd, it is still the same. I can see all the files on my int. sd with no probs.
Please help.

I'm thinking it might be a hardware issue, but I'll wait for another member's opinion before confirming.

Solved!!!
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.

630263 said:
That's what I thought - HW prob, but it seems that luck is on my side, I hope. It helped to get back on stock but with total deletion including int partition
Anyway thanks for support.
Click to expand...
Click to collapse
Was your phone rooted or bootloader unlocked before the problem occurred?
Anyways I've sent in my phone for warranty, hopefully samsung will fix it.

So my phone company called me today and apparently Samsung told them that it's corrosion(?) problem. When I asked exactly what does that mean they said it's moisture damage or physical damage that probably caused it. But I'm confused how could my phone possibly get moisture damage inside an otter box. I know how delegate these devices are and I know how to take care of them.
Anyhow it'll be $90 to fix it. I had no other option so I asked them to go ahead with the repairs. So frustrated with Samsung to be honest. I never dropped my phone once, never had any water damage, phone was always inside the defender case. And I still have to pay them for fixing my phone even though it's not my fault.

That's quite worrying, I just started having boot loop problems today. I've had the phone since Feb 29th and not had a problem with it yet, but today it started boot looping. I went into recovery and did a factory reset, was alright for a couple of hours then it crashed, started bootlooping again. Running stock 4.0.2 unrooted, I'm wondering if flashing 4.0.4 might help.

I'm in the same boat.... unrooting stock 4.0.1 firmware - canadian version from Negri.
April 23rd my phone crashed and started boot looping. Google logo - reboot - Google logo - reboot
Factory reset worked. I installed less apps than I had before figuring perhaps an app was corrupting something.
Yesterday - it happened again. Phone crashed. Boot loop. Factory Reset worked. Installed even fewer apps.
We'll see what happens this time around. I am hoping it is just a software thing. Hoping 4.0.4 gets pushed soon too.....

I've been having the same issue, plus sometimes my home screen it would lock up and wouldn't let me do anything, so I did a battery pull and it would boot loop for a half hour.
After the 3rd time I just took it to my Verizon wireless store, and showed them the situation and they couldn't figure it out, so their sending me a replacement, which I'm not looking forward too, don't want a semi-used phone....
Via Galaxy Nexus [LTE]

Rebooting Issue Solved.
I was also a troubled Samsung Galaxy Nexus user and my phone kept restarting more than half a dozen times everyday. Most of the times when I switched between two or more applications, or when it was simply idle on my desk.
However, I found a solution (at least in my case). All I did was root my phone, install cwm recovery, and flash a custom rom after wiping cache and factory resetting the phone, It's been about 5 to 6 hours now since I flashed the custom rom and I haven't had a single reboot or hang since.
Others who face this problem, please give it a shot, who knows? You might save your Galaxy Nexus instead of sending it back to get a replacement or spend some money on it for repairs which aren't even required in the first place.

I also had this problem unrooted. I had to give it to Samsung for the warranty
Swyped on my Galaxy Nexus running AOKP with Trinity Kernel, overclocked to 1.4GHz

I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.

2stardiver said:
I got my nexus yesterday, almost immediately after first start it start to install JB from OTA.
I did buy 2000mAh samsung original battery and started straight with it. not even testing with 1750mAh bat.
after installing JB and needed softwares, it started to randomly reboot.
it rebooted even it was just in my pocket.
sometimes when I did do something, display freezed and after about 5sec it rebooted.
Now I did changed to original 1750mAh, and it havent boot at all couple hours, even I did play angrybirds space.
I wont dare to root it before I am very sure problem is with 2000mah battery.
Click to expand...
Click to collapse
I could be wrong, but have you tried to clean the pin on the battery? Seems like battery and the phone isn't contracting too well
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

Little update, phone did continue rebooting with original 1750mAh battery also.
I did also reset with recovery mode, and after that it did also reboot one time.
like it uses all memory/cpu and when nothing to do reboot (like windows )
I also did flash stock rom with toolkit but no help.
I will test rooting phone and flash another rom, or is it useless ?

after using couple days, not yet rooted.
Phone works and wont reboot even in heavy stress. but sometimes it just reboots by own not a single program in task list.
might reboot right after previous reboot or take hours to reboot.
stupid phone

I have been done some research.
I did one more time reflash google stock with rootkit, and forgot lock phone, it was almost 3 hours by own in wifi, no reboots at all.
when I noticed that I forgot to lock it I rooted whole phone and installed paranoid android 2.13 with CWM.
Now Ive been using 2 hours without any reboot, installing software, setting things up and using apps.
I dont understand at all:silly:
edit: noup, yesterday evening one almost reboot, paranoid android did reset itself but didnt even reset uptime. so I didnt count that normal reboot.
but after wake up this morning, it did reboot once when I put in my pocket, another just lying on table, once activating bluetooth in my car.
going to send it back to seller.

I have a similar issue, although not quite the same. Last night my phone started boot looping - it managed to boot up to the lock screen, and I can use it for about a minute before it dies and then reboots. This continues again and again (I have to pull the battery to quit it).
I have stock JB on my GSM GN, but rooted with an unlocked bootloader / CWM. I restored my old CWM backup, and had the same issue. I also wiped the cache and the dalvik just to see if that helped, but I had the same issue. I then tried to do a factory reset in CWM, but after I did that the boot loop just got to the nexus logo and died, entering a new (slightly shorter) boot loop. I went back into recovery and reflashed my CWM backup, and that at least got me back to booting into android.
I can't understand what's going on - could it be a hardware issue if it will happily stay alive in recovery, but dies after 1-2mins of android?
Thanks for your help. If it is hardware then I hope I can reflash the stock recovery / bootloader and unroot through recovery... the phone doesn't stay on long enough to do it when it's booted into full android!

Phone Keep Restarting Problem

Hey everyone I have a problem that I sort of fixed but not really? About 2 days ago my phone kept restarting and vibrating. I researched the problem and it said that it might be a stuck button problem. After a few hours I came to the conclusion that a stuck power button was the problem. I went to a cell phone repair shop and had it repaired. IT worked fine on the way home but then I got home and set it on the counter only to come back to it restarting and vibrating all over again. How is that possible after replacing the power button I though. So I did my best and I was able to flash the stock 4.1.2 rom back onto my phone and unroot it and everything. Now my phone has been working fine ever since. Could it be that I cant flash roms anymore? Does anyone know what the real problem to my phone is? If so please respond here. Thank you very much for you're time.

Jyjieng11 said:
Hey everyone I have a problem that I sort of fixed but not really? About 2 days ago my phone kept restarting and vibrating. I researched the problem and it said that it might be a stuck button problem. After a few hours I came to the conclusion that a stuck power button was the problem. I went to a cell phone repair shop and had it repaired. IT worked fine on the way home but then I got home and set it on the counter only to come back to it restarting and vibrating all over again. How is that possible after replacing the power button I though. So I did my best and I was able to flash the stock 4.1.2 rom back onto my phone and unroot it and everything. Now my phone has been working fine ever since. Could it be that I cant flash roms anymore? Does anyone know what the real problem to my phone is? If so please respond here. Thank you very much for you're time.
Click to expand...
Click to collapse
If your phone is functioning normally.....there's no reason why you can't flash any rom made for our phone.
Sent from my cell phone telephone....

The problem is that everytime I flash a custom rom my home button goes crazy and makes the rom un-usable. I have flashed both JMT and Slimrom on my phone and bot ended in the same result.

Jyjieng11 said:
The problem is that everytime I flash a custom rom my home button goes crazy and makes the rom un-usable. I have flashed both JMT and Slimrom on my phone and bot ended in the same result.
Click to expand...
Click to collapse
It sounds more like boot loops which can happen often if you look thru the forums. Your buttons either work or they don't. What rom you are on plays no part in hardware issues like that.
Just be sure when trying a rom, you follow the instructions to the letter. Otherwise boot loops can easily happen.
Sent from my cell phone telephone....

kj2112 said:
It sounds more like boot loops which can happen often if you look thru the forums. Your buttons either work or they don't. What rom you are on plays no part in hardware issues like that.
Just be sure when trying a rom, you follow the instructions to the letter. Otherwise boot loops can easily happen.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
It couldnt have been a bootloop because it was working just fine for a while after flashing and then later on I set it on the table to come back to it flashing where it kept unlocking and locking and unlocking. I was unable to do anything with the phone at the time and after a while it kept restarting and vibrating. You dont think its hardware issues?

[Q] Stuck in first screen bootloader

So, I flashed yesterdays CM10.2 and had no problems, up until today. I was in class, using twitter, set the phone down, and looked back at it 5 minutes later to find it shut off. I restarted it, figured no big deal, it turned off again. I thought there was a problem with that nightly so I flashed back an older, more stable one(still 10.2). It booted up, and shut off again. Now, though, the phone boots up, shows Samsung, then shows the GS3 and CM logo, then just goes into a loop from there. I went to recovery and tried to wipe, which, oddly, the phone restarted again. Luckily I was able to get in and wipe data before a new reboot, but even that didn't fix it. I rebooted into recovery again, and it said something like "root access available" and asked me if I would like to use root, which I didn't get the chance to fully read because it restarted again. When I am able to successfully boot into recovery though, I get a warning saying "no file_contexts", this could be it?
I've already tried to flash back stock Touchwiz with Odin, but it keeps failing to do so. Any help with this?
EDIT: After successfully booting up a CM10.1 backup, I've begun to believe the power button is broke, because the power menu will randomly popup, followed by a shut down.

It's called SDS sudden death syndrome it's very common on the S3. It's a failure of the power button. It's a defect. If your phone is newer than a year old put it back to stock and take it to sprint.
Remember search is your best friend, Have a great day!

LG G3 D855 blackscreen right after booting logo

Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.

Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.

Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card

EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets

I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.