Related
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....
friends,
I need help ...
After a trial that went wrong to access the root in my part of the Defy touchscreen stopped working. I sent for motorola technical assistance and returned as not having any problems, and to solve the problem just reset the phone. They said it was a corrupted file on the phone.
It turns out that now another part of the touchscreen is not working. I already did a flash wipereset and wanted to know if you have any other way I can make a master reset on the Defy.
I've tried installing the original SBF with RSD Lite. And I have tried to wipe reset. Any other possibility?!
Thanks for the help ...
Seemed you already tried reset, wipe and flashing. But the problem persist.
It could be now down to the screen touch panel faulty or the touch control faulty in the motherboard.
You are suggesting it may be a hardware problem?
Yea since you already tried flashing different rom.
I might be wrong but based on your posting above it could be the hardware problem.
An old man suggestion: Might work for you too. Flash it to a stock rom and make sure everything worked(of course except the touch issue). Then shut down and take out the battery. Leave it for 24 hours and try again putting back battery and boot it. Sometimes some small voltages trapped in the board that may resulting phone acting crazy. This normally due to a bad motherboard. Having leave it complete shut down for 24hours will simply drained those trap voltages in the board and the device is good to go. Now this will not permanently fixed your problem though.
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
Edit: --> I was able to install TWRP using Mobile Odin. Now I'm going to change the bootloader and see if that fixes the problem.
biga72112 said:
Hello.
This my first thread. I have done some reading, but I can't find a similar problem, so I really hope that this is posted in the correct location...
I have an odd problem with my phone. I did a flash a few months ago, and I also (attempted to) update the modem and bootloader. After the reboot, I had to begin pulling the battery to get the phone to power back on after the power was off or after a restart. I've replaced the battery, charger, and installed SEVERAL new roms, but the problem persists. I don't know if I need to do something else, or if the phone is damaged...
But if it IS a programming problem, and not physical damage, then here's the real problem...
I have installed the latest version of CWM. I am running CM 11 with Kitkat 4.4.2. I would like to just flash the stock rom and see if that fixes it, but I have read that once you are running a 4.3 or beyond bootloader, you WILL brick your phone if you try to downgrade. So that stops that.
Another issue is that if I try to install a different/newer bootloader in CWM, it fails every time. I also cannot flash another version of CWM or TWRP. About halfway through the process, Odin says it has failed, no matter what version of Odin, CWM, or TWRP I am using.
So the short version of this is, based on what I've listed, how do I fix this rebooting issue?
I know that this is a long post, but I'm trying not to leave anything out. If anyone has any ideas, please feel free to let me know.
Thank you in advance
Click to expand...
Click to collapse
If the phone powers on itself immediately the battery is replaced, i.e. without you having to press the power button, chances are 99% you have a stuck power button problem. It's not uncommon with this device and can be routinely fixed at any repair shop or by DIY if you have the right tools and technical resources.
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Larry2999 said:
If the phone is working OK (other than the booting issue), I'd stay off flashing bootloaders to avoid bricking
Click to expand...
Click to collapse
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
biga72112 said:
Thank you very much for the reply!
No its not a power button issue. I DO have to hold the power button to power on. Here's what happens when the restart fails...
I have to:
1) pull the battery
2) sometimes, I have to hold the power button WITHOUT the battery in for a few seconds (I've had laptops that have this issue before. I think it's a static buildup of some sort.)
3) reinsert the battery
4) hold the power button, and
5) if I'm lucky, the phone will boot up.
This is only about 50% successful. Sometimes I have to do this 3-4 times.
Now, I don't know if this is a hardware issue, or a firmware/software issue. If it IS a hardware problem, then I may just replace the phone. If it's a firmware/software problem, then hopefully it can be fixed. If it's a problem with the bootloader, and a fix isn't possible, then I'll just keep on truckin' till I get a new phone.
Click to expand...
Click to collapse
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Larry2999 said:
It's almost certainly an hardware issue. Very unlikely a firmware problem would cause this and even more likely the bootloader would. With a bootloader issue, your phone likely wouldn't even boot at all. Power button problems present in several ways and a loose power button could cause the kind of issues you've described. I'd take it to a local tech shop for a quick look before giving up on it.
Click to expand...
Click to collapse
I may just wait and get me a new phone in a few months. I'm expecting a bonus from work, and I'll likely just get the new S5. Thanks for the information
Hi everyone, i just bough a I747 unlocked, im from Venezuela.
It come with last stock rom (tough its 4.4.4) and i rooted, instaled Philz Touch Recovery and flashed Cyanogen Nighties 13, from the official cyanogen site all fine here (btw i have to update the modem so the sim can be recognized). Yesterday i download the last nightie and installed via recovery, and start to reset just turning on, i mean, the phone get to the desk, and turn on totally, then just turn off (this happen when i tried to open a app or just open the menu, now make it just after 4 seconds of tottally turn on). I make a full wipe again and install the previous version of Cyanogen, and the problem still, wipe all data and cache, same with Dalvik Cache.
Something curios happen yesterday, the phone make the sound that makes on low battery, i plug to charger and it turn off, and show the battery with 42%, it work perfectly with charger plug in, but when i disconect it turn of and i have to turn on, REALLY SORRY FOR THE BAD ENGLISH, I TRIED MY BEST TO EXPLAIN THE PROBLEM, IF U DONT UNDERSTAND SOMETHING, ASK ME AND I WILL TRY AGAIN TO EXPLAIN BETTER.
I uploaded the modem withouth making it version by version, i just upload to I747UCUEMJB withouth the others, i dont know if this make the error happen, becuz i have a few days working with it before the error happen.
Im now dowloading OctM to test.
Sreeens from InfoSamsung
imgur. com /a/ FjGpI /all
Detele spaces
Okay, i just install last octo-m, the phone have to still plug to turn on, but then i can disconnect and works normally. I could appreciate if someone gets me a Stock Rom for the SGH-I747 so i can comeback to TouchWiz, and help me with to bootloader/modem updated guide, i think the problem is on there.
Nope, the phone still gettin off, doest'n last even 3s on desktop.
If the phone was running stock 4.4.4 and you installed the mjb modem which is from 4.3, this may have caused the problem. Maybe flashing a newer modem may solve the problem.
Just bought a new battery and the problem it's gonne, thansk to reply, the problem was a bad battery. (the phone isn't new, i buy from 2nd hand)
when my phone disconnected to charging port my phome started rebooting in sometime & after port connect its work normal.....help me
1. First make sure u have clean flashed the ROM.
2. If problem persist try any another ROM.
3. If anything didn't work ,Try flashing stock ROM using qfil or mi tool. Then again flash twrp.
4. If still the problem persist contact the service centre .. there maybe some hardware fault.
??
same fault here ... i think its a battery related issue ...
It's like if the phone need too power it reboot( maybe the battery no longer reach a higher voltage) ...
try to decrease brightness while you are waiting for new battery
is the battery, I spend with my phone a few months ago I changed the battery and I stop doing it.