I flashed Energy Rom to my Touch Pro first. After this I flashed another rom and everything was fine. Then I flashed back to Energy Rom and now my touch screen didn´t respond to touch.... So I just wonder if someone could help and tell how I get it working again??? Screen shows everything and qwerty is working fine.
Have you tried an hard reset ?
Moved as not ROM *Development*
Try hard reset, if not working flash stock ROM to test if hardware.
ok
So I Hard reset first. If it doesn´t work I put back stock rom. and do I hard reset stock rom after installation? well I try and reply after I have tried.. thanks.
didn´t work... any other ideas???
the stock rom is same. touch screen doesn´t work though the picture comes.
I faced same problem after endless flashing different ROM, stock Rom no improvment.
Went to HTC service center & they said moatherboard is gone have to replace it.
Hi, I have a big problem with my Galaxy S SCL i9003.
From last week everything was working good, but something happened.
The camera stop working. Hours and hours searching and I find the solution but I need root.
Ok, I make root and surprise, the phone doesn't want to exit from CWM Recovery.
I tried installing ROMs, and the f*cking recovery won't let me do it. I tried with a ROM from a Spanish forum, it was installed all correctly and then another time, the damned recovery.
I tried to install a lot of ROMs, a lot of things from XDA-Developers, now even won't let me to install any ROM.
I do with Odin several times reflashing with original FW and it works by the way... But I need to be root to make my camera work, because I need to replace some system files :crying: :crying: :crying:
Please, what can I do ?!? If I root with Odin everytime my phone won't exit from recovery and the damn recovery even let me install a rom, so I need another time to flash to original FW and well... I can use the phone but I can't use the camera :crying: :crying:
¿What can I do? I tried with 3 different recoveries, all of them are quite old (the newest is from 2012) and I want to know if exists an newer version for my phone. I need to root it, but if I try everytime with Odin and do all good, everytime my phone bricks in Recovery. Whatever I do it's the same... it doesn't exit from recovery mode until I flash to stock FW.
Big thanks in advice. :good:
If you flash stock rom and the camera still dont work i think is hardware problem related. Fresh installation of Stock rom should fix All software related problems.
acuicultor said:
If you flash stock rom and the camera still dont work i think is hardware problem related. Fresh installation of Stock rom should fix All software related problems.
Click to expand...
Click to collapse
Hi friend thx for the reply, the thing is that im on stock rom and all goes good, but the problem is I want to root it to solve the camera problem.
I searched on the web and several i9003 and i9001 have this issue when they're updating or when they've been updated... I can solve it changing some files on system but I can't have root access :crying:
I think your problem is related to recovery.
You can flash Bam Kernel via Odin. I'm
using it. Download the latest fix version and
flash it in pda. It has CWM & it will root the
device.
http://forum.xda-developers.com/showthread.php?t=1355675
So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
di3zelherbert said:
So I'm new to rooting and flashing custom roms on android devices. This also shows that I'm new because I forgot to make a backup of my stock system before moving forward, hence this problem.
So I currently have CM 10.2 flashed on my phone and so far I can't get the wifi to work. My bluetooth works perfectly fine (I've read that if one fails usually the other should too), so I don't know what to do.
At this point I'm sure i'm stuck because I've flashed a few different roms already to see if i can fix it (10.0, 10.1, 10.2, and hacker's aosp 4.4) but the wifi isn't working in either so I stuck to the rom that had the fewest bugs.
What's weird was that it was working when I had 4.4 flashed, but when i found it too buggy and flashed CM 10.2, now it doesn't work.
Anyone else have this problem? I guess I can live with it for a while until maybe I purchase a new phone.
Thanks
Click to expand...
Click to collapse
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
koftheworld said:
Did you flash 10.2 directly over 4.4 without wiping system data and both caches?
Sent from my XT926 using Tapatalk
Click to expand...
Click to collapse
The first time, no. I thought I may have installed 4.4 incorrectly so after installing 10.2 i tried flashing 4.4 again, but I did wipe the caches, system, data and dalvik caches the second time going back after reading in this forum how to flash over a custom rom. But then seeing that the bugs were still there, i wiped again and went back to 10.2 and I've been there for a day now.
Missed Wifi
I'm facing the same trouble , same conditions.
Solved
zirig said:
I'm facing the same trouble , same conditions.
Click to expand...
Click to collapse
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
zirig said:
This will solve !! http://forum.xda-developers.com/showthread.php?p=47415109&posted=1#post47415109
thanks for xXLuHXx
Click to expand...
Click to collapse
That worked! Thank you!
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!
Hey!
First of all, this post will be too hard to write because of my English.
I had decided to improve the performance of my Fame a long time ago (I have to clarify that I'm a noob at flashing roms and doing related stuff). So I flashed Galaxy Fame - Stock deodexed and it worked perfect.
After a while my cell phone became slow again so I installed Cyanogenmod 12.1. I didn't like that rom due to the bugs and performance.
So I wiped the data/cache/dalvik and re-flashed the previous deodexed rom again.
What's the problem? It boots and stays in the "s6810L" screen for a few seconds, then reboots and stays in that screen again for a few seconds and THEN it shows the CWM recovery menu.
I haven't tried another rom yet, but I want to know why it didn't work this time... I really like the deodexed rom because it's so smooth and fast.
What am I doing wrong?
I'm sorry for my english again, thanks in advance, and regards!
Edit #1: I'm using this CWM
Hi !
When flashing roms a factory reset is recommended especially when flashing between 2 totally different based roms , cyanogen / stock
My advice is to use odin and revert to stock , don`t flash via recovery
Also , I can move this thread to the designated location if you continue to have problems and the solution I suggested doesn`t work , there may be more users with the same device.
Use the same thread you have linked above to get the firmware
Good luck and let me know !