Develop Bugs

[Q] Bricked? Screen Fails to turn on after it's turned off the first time.

Hi,
I'm experiencing a strange problem with my Desire. It's S-ON and rooted with modaco's root kit.
I was running CM6 nightlies fine for 2 weeks. All of a sudden the screen failed to turn on. The only way to make it work again is to take out the battery and boot. Once booted, the first time the screen goes to sleep again, it's impossible to turn it back on. It also happens when I turn the screen off manually with the Power button.
I'm not a newb. I'm familier with adb, flashing various roms and radios. I've been actively reading these forums since I signed up here.
I've also performed all the wipes in modaco's rooting pack recovery various times (wipe factory, wipe cache, wipe dalvic-cache, wipe battery stats etc.)
No matter what I try, how many times I wipe and which ROM I flash the screen sleep problem still persists.
Radio version: 32.47.00.32U_5.10.05.23.zip (I also reflashed this once)
I would appreciate any help. Please let me know if you need more information about the problem, or device.
thanks

Have you tried wiping the SD card partitions and setting them up again?
Or if you have a spare, using that so you dont destroy your data??
If you are using A2SD then a corrupted partition might be causing this?? Worth a try as you've pretty much done all else bar shove it in a microwave on FULL for a min*
*dont try this!!! lol
Hope you get it sorted.....

MadMic said:
Have you tried wiping the SD card partitions and setting them up again?
Or if you have a spare, using that so you dont destroy your data??
If you are using A2SD then a corrupted partition might be causing this?? Worth a try as you've pretty much done all else bar shove it in a microwave on FULL for a min*
*dont try this!!! lol
Hope you get it sorted.....
Click to expand...
Click to collapse
I'm not using ext3/partitions on the sdcard. Either way, the problem also persists when the sdcard is not in the phone.

When the screen goes off what happens if you ring the phone? Try setting the volume off silent and wait for the screen to blank and call it - see what happens..
I'd then try flashing an RUU and using a blank unpartitioned SD card so the phone is as it came from the factory... if that fails then I'd guess you might have a hardware fault as that's pretty much all that it can be

MadMic said:
When the screen goes off what happens if you ring the phone? Try setting the volume off silent and wait for the screen to blank and call it - see what happens..
I'd then try flashing an RUU and using a blank unpartitioned SD card so the phone is as it came from the factory... if that fails then I'd guess you might have a hardware fault as that's pretty much all that it can be
Click to expand...
Click to collapse
thanks for your reply.
When the screen is off, and I call the phone, I can answer it by sliding the blank screen and perform a phone conversation. The screen never turns on though, not even when the call is over.
I will look for a 2.1 RUU rom on the forums here and flash it. See what that does. Do you have any suggestions on which RUU? (I thought 2.1 so it's rootable again). .. Also is the flashing process the same as flashing a custom ROM?

I'm not sure if flashing an RUU is going to work - you can try, but I think this is more of a hardware issue worth a try as if you've got to send it back then you'll need to unroot...
Only thing to be aware of is if you send it back to HTC you'll more than likely get an SLCD screen rather than the AMOLED you may have at the moment - the jury is out of which is better....

[Q] Nexus keeps freezing and restarting, why?

I've had this GN for about 2 weeks now. I unlocked the bootloader and put 4.04 on the phone (using the directions from xda). For the past two weeks the phone was running great, 4.04 is much smother than 4.02. However, today the phone started going crazy.
It keeps restarting over and over again. I flashed the phone and put 4.02 back on it using the Google img hoping it would fix the issue. The phone will now be stable for a few minutes, but then freezes and either restarts or I have to pull the battery.
I have no idea what is going on? Is this a software or hardware issue?
I would love some help/suggestions,
Thanks
It has been stable for about an hour and a half now, but all day it had the issue above.

did u use custom kernel? or oc/uv?

I am somewhat new to this so bare with me.
It believe it was custom... under phone info it says - kernel version 3.0.8-gaaa2611.
Here is a link to what I did:
http://www.gottabemobile.com/2011/12/16/how-to-unlock-the-galaxy-nexus-bootloader-verizon/
http://www.xda-developers.com/tag/android-4-0-4/
In case I did not already say, I am on Verizon.

kaseyk said:
I am somewhat new to this so bare with me.
It believe it was custom... under phone info it says - kernel version 3.0.8-gaaa2611.
Here is a link to what I did:
http://www.gottabemobile.com/2011/12/16/how-to-unlock-the-galaxy-nexus-bootloader-verizon/
http://www.xda-developers.com/tag/android-4-0-4/
In case I did not already say, I am on Verizon.
Click to expand...
Click to collapse
boot into recovery by pulling the batery and then hold the power and volume up and down at the same time until you are in fastboot mode. from there volume down should give you the recovery option to reflash tshe stock rom or whatever rom you want. tey without any custom kernel and see what happens

I flashed the stock google image and it was good for about a week or two. All of a sudden it started doing it again. Is anyone else having issues like this? Could it be some kind of app causing this? I've only downloaded market apps.
How can I fix this?
I just reflashed the stock google image and it freezes and resets before I can even enter my account information. After a couple of reboots I was finally about to register it, but can't unlock the lock screen before it freezes are restarts again. It is almost like it is lagging a ton and then freezes and resets. Could it be hardware? Should I relock the bootloader and swap it out for another (I have the Best Buy Insurance policy)?

kaseyk said:
I flashed the stock google image and it was good for about a week or two. All of a sudden it started doing it again. Is anyone else having issues like this? Could it be some kind of app causing this? I've only downloaded market apps.
How can I fix this?
I just reflashed the stock google image and it freezes and resets before I can even enter my account information. After a couple of reboots I was finally about to register it, but can't unlock the lock screen before it freezes are restarts again. It is almost like it is lagging a ton and then freezes and resets. Could it be hardware? Should I relock the bootloader and swap it out for another (I have the Best Buy Insurance policy)?
Click to expand...
Click to collapse
'fastboot erase recovery'
'fastboot erase boot'
'fastboot erase userdata'
'fastboot erase system'
Then reflash stock rom.
Don't use a toolkit. Reflash stuff like google tells you to. Educate yourself if you need to.
After you get back up and running, don't install apps. Well just a few maybe. No widgets. Monitor the phone for a week or two. If it still goes nuts, i'd say turn it in for warranty, after relocking the bootloader.

[Q] One X Malfunctioning after HBOOT 1.39 Update. FCing everything on all ROMs.

I have a One X S720e, CID_J15
I recently upgraded the hboot to 1.39, and since the update the phone has been going crazy. First installed a IceColdJelly 2.5.1 ROM. And after installing Gapps everything was okay at first but 5min into usage everything started FCing. starting from com.google.process to the launcher to every single application. And this just keeps happening. I ran a super wipe script installed other ROMS including the CM 10.1 and same issue kept happening.
After a day of this, the phone randomly started turning off and got stuck in APX mode. I managed to get out by holding power button and vol up + vol down for 40+ sec. The phone runs for a bit, boots into ROM, works for some time as long as no app is run. If i open ANY app at all, again the FC starts and eventually the phone reboots into the APX mode again.
Frustrated, i ran another Super Wipe Script, again tried to install the HBOOT 1.39 update, and then installed the STOCK ROM for a nandroid backup i had. But the same thing keeps happening. All apps force closing. So basically i cant use the phone.
PLEASE HELP ME. Anyone have any ideas whats wrong ? or could it be a hardware issue ? should i relock the bootloader and send it to a HTC service center ??

You did flash the boot.img for every specific ROM right?
I think if you send it to HTC they will charge you for the full repair service, which WILL cost you a lot of money.
Got no further solution for you buddy, good luck. Hope you can fix it before sending it to HTC

yup. Done evreything by the book. flashed all the boot.img files. The ROMs boot perfectly, just that after a while while im installing apps and or doing ANYTHING everything starts crashing.
My phone is still in warranty though. I read that if the phone goes into APX mode its usually a hardware problem. My question is why did the problem arise only after i updated the HBOOT. everything was just fine till then. I hope this issue is covered in warranty :'(

i have exactly the same problem!!
What you say, sometimes it will work for 5 minutes. But when you open an application it will force close and all the applications will start FCing.
Did you already solve the problem?

APX is a hardware defect ..... not much to do about that.

I have exactly the same problem! It all started with ICJ: gapps and almost all other apps started FCing after some time. After dozens of hard reboots I got stuck in APX mode. At least that's what I think. My PC recognized the device as "unknown devices", the screen was black, adb and fastboot didn't work. I managed to get out by pressing the power button + volume up/down for many seconds... I flashed numerous Roms in the past days and I always get the same FCs (especcially Gapps) - doesn't matter if it is a sense or an AOSP based ROM. So is this a hardware probelm? Is there any way I can solve it? If I send my HOX to HTC I'll most probably need to pay right?

Mr Hofs said:
APX is a hardware defect ..... not much to do about that.
Click to expand...
Click to collapse
Said it already ....

Mr Hofs said:
Said it already ....
Click to expand...
Click to collapse
sh*t Already thought so
so basically we're f*cked...

Yep

Hyper Gamer rom, screen won't wake.

I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.

JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
If you want good rom for gaming and everything else, then try gaming hybrid 2.1.2
Amazing rom with 190 mb free RAM on startup
And there is no bugs.

JimmyDeemo said:
I'm having this strange issue with the Rom in the following thread; http://forum.xda-developers.com/showthread.php?t=2578972.
Sometimes when I press the power button the screen doesn't wake. This doesn't happen all the time and I've been trying to work out a pattern without success. If I pull the battery and try to boot the phone, it will vibrate to show that it reached the kernel logo but again the screen isn't on so you don't see it.
The only way I've found to fix it is by removing the batter for a while, clearing some sort of temp memory. Then the phone boots as normal and i can use correct.
No other issues and I wondered if anyone had any ideas on what this could be. I would post in the development thread but I don't have the permissions. Any help much appreciated.
Click to expand...
Click to collapse
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?

Jure220 said:
What kernel are you using?
When the screen goes black can you see the phone in if you run adb devices?
Click to expand...
Click to collapse
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.

JimmyDeemo said:
Hi Jure220, thanks for the reply. I'm using the 480p version of the one you recommended in the ROM thread here; http://forum.xda-developers.com/showthread.php?t=1804003.
I'm not able to try adb devices right now, but will do later. It's like the phone is still running but just the screen won't turn on. Sometimes I can get it to come alive with by opening the slider. When booting with the problem, I get one vibrate to show that the power has been pressed, then another for the kernal logo (used to indicate going into the recovery menu). It's very strange, I will get back to you on the adb devices but is there any other details I could get you?
Cheers for the help.
Click to expand...
Click to collapse
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released

Jure220 said:
If its posible run adb logcat when the screen still works and keep it connected until the black screen apears and post the log in a txt file. But it isnt necessary. But if you reflash the rom it shuld work fine. And if it dosent try the new update I just released
Click to expand...
Click to collapse
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.

JimmyDeemo said:
Yes I did notice that you had posted v1.3, will give that a try. I was a bit confused as to why the ROM would affect the screen on boot, but this is me assuming that it is something to do with the ROM at all.
Out of interest, did I need to use any specific settings when formatting /system ready for the ROM? I did a full wipe and fresh Kernal install at the time so had to format it.
Click to expand...
Click to collapse
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...

Jure220 said:
When you flash the rom /system will be formated automaticly, and I also doubt it is a rom issue I think something went wrong while flashing...
Click to expand...
Click to collapse
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>

JimmyDeemo said:
Hi Jure2020, so I just flashed the ROM again with v1.3, booted fine after flashing. Powered off and then black screen again. I think that it must be a Kernel issue, do you have any other recommendations for Kernels compatible with your ROM?
I tried adb devices btw, all I got was the follwing;
C:\Development\Android SDK\platform-tools>adb devices
List of devices attached
CB5A1E0AJ2 device
C:\Development\Android SDK\platform-tools>
Click to expand...
Click to collapse
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?

Jure220 said:
Try to reflash the kernel or use lupus ics/gb one and if it still dosent work reflash the firmware, btw when it first happend did you drop the phone or something?
Click to expand...
Click to collapse
Yeah I will try re-flashing a new kernel this evening. Will try this one; http://forum.xda-developers.com/showthread.php?t=2167766.
No honestly, just one time I noticed it didn't wake the screen. Then it got a bit more regular, now it's pretty much every time the phone is left idle for a while, the screen just won't come on. The phone is active, I can 'unlock' it by swiping; I get the haptic feedback and hear the unlock noise. The phone is running, just the screen is off. I even thought it could be a CPU clocking issue, so used SetCPU to force the minimum speed up for resumption and no luck their either.
I have been thinking that it could be a hardware issue, my phone is kinda old now, but the thing is once the phone is on, it's on. I've gamed on it for a good hour or two with no problems, then pressed power to sleep and immediately haven't been able to turn it back on again. It's just very strange, thanks for the help though.

Hi JimmyDeemo,
I think your problem is flex cable related. I've also experience this before. After I replaced the damaged flex cable, my phone just work fine....:victory:

HELP - (Hard) Brick Z1C

Hi guys, I've a big problem, and it's very strange:
today I've updated lucky patcher, after installed it, the phone showed screen of the turning off. I started again the phone, but at the start screen, showed again the turn off screen. I tried to wipe and restore backup, samre problem. I tried to flash a stock firmware but after the sony logo i've a black screen with phone on. I really don't know what to do, I need your help. thanks a lot :crying::crying::crying:

ULT][MO said:
Hi guys, I've a big problem, and it's very strange:
today I've updated lucky patcher, after installed it, the phone showed screen of the turning off. I started again the phone, but at the start screen, showed again the turn off screen. I tried to wipe and restore backup, samre problem. I tried to flash a stock firmware but after the sony logo i've a black screen with phone on. I really don't know what to do, I need your help. thanks a lot :crying::crying::crying:
Click to expand...
Click to collapse
If you have revovery, you can just delete Lucky Patcher apk from /system or /data, (wherever it is). It's not a hard brick...

levone1 said:
If you have revovery, you can just delete Lucky Patcher apk from /system or /data, (wherever it is). It's not a hard brick...
Click to expand...
Click to collapse
Very bad news: I tried to flash a stock L, after flashed I started it, but it shutted down at waves bootanimation. I putted it on charge and showed this message "your device turned off due to overheating ,charging will continue once the device cools down".
An expert technician said to me that's a processor's cooling problem and, in his opinion, it is impossible to fix it. except sendind it directly to sony. But it should be very very expensive...

ULT][MO said:
Very bad news: I tried to flash a stock L, after flashed I started it, but it shutted down at waves bootanimation. I putted it on charge and showed this message "your device turned off due to overheating ,charging will continue once the device cools down".
An expert technician said to me that's a processor's cooling problem and, in his opinion, it is impossible to fix it. except sendind it directly to sony. But it should be very very expensive...
Click to expand...
Click to collapse
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...

levone1 said:
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
Click to expand...
Click to collapse
Thanks levone for your answer, and sorry if it's passed a lot of time.
Unfortunately i tried everything coud be possible. tomorrow I'll try with an expert friend to open it and see the problem. A technician said to me that probably it's a cooling problem. Processor can't be cooled and phone shut off, or probably is (again) a battery problem. Soon i'll write if i've found a solution, also to try to help someone who could have a similar problem (i hope not).

How can the "processor" not be cooled? There is no cooling hardware that could stop working.. It could still be another hardware defect, yeah.. Have you wiped it or did you just flash system/baseband/kernel/etc ?

levone1 said:
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
Click to expand...
Click to collapse
I've used Z1C in sauna (where is 100°C degrees) and the phone becomes so hot it is untouchable to hold and even struggling to play video playback (under clocking). Then i know it is too hot and take it out.
It takes ~1 min and it is cooled enough where is it fast and smooth again. Never has it said too hot, shutting off or something similar. Then again i'm using KitKat which doesn't maybe have that function?
I'd say issue related to battery or software as i had same problem after installing Lucky Patcher. Got bootloop after restarting.
I also used restoring and it succeeded but somehow Lucky Pather was still present but bootloop problem was cured.