hello everyone,
I am having some big trouble with my phone. since the update to lollipop its getting worse.
and now the problems:
1.) I can't reboot to recovery anymore.. it's unbelievable but it doesn't work no more. neither with an app nor manually. (phone off. phone on. press power and volume down simultaneously and let go when Sony logo appears.) tried NTR Utilities which was pre-installed..nope. tried quickboot.. nope.
2.) sometimes when I used my phone a lot I cannot turn off my 3g or my GPS from the status bar. you know you can customize your bar with 3g or hotspot or GPS etc. and my shortcuts in the downer part of the status bar don't work no more. I can press them shortcuts but it won't work. than I have to restart my phone. and it works again..
3.) when my phone is locked and I press the power button to enter my pattern the display gets bright as the sun (seriously!) all the background gets almost white and afterwards it's getting normal brightness again.. still don't know why this is happening..
4.) and sometimes when I want to take a picture the standard camera app says that I don't have a SD card in my phone (I have one ) . so it changes the save directory of the photos. but when I release the SD card and put it back in the phone everything is normal..
anyone has the same issues?
hope one of you guys can help me.
phone:
Lollipop Stock Z1C root
#3 happens to me all the time, stock not rooted 5.0.2, I hope someone replies a solution, I thought I was the only one
none of you ever experienced one of these problems?
Lollipop Stock Z1C root
really.???
no one can help??
Lollipop Stock Z1C root
rakdumafo said:
really.???
no one can help??
Lollipop Stock Z1C root
Click to expand...
Click to collapse
I don't know much, but it may help to know if you're using locked or unlocked boot loader, which kernel, which ROM, which recovery, did you flash any other mods, (xposed etc.)... These things help people help you. I don't know technical stuff, but I know that some ROMs have recovery built in, and some don't, so you have to flash yourself. Some ROMs work with some recoveries and not others. If you're rooted and unlocked BL, it may be as simple as installing Rashr, and flashing a new rec. image. In general, I've found that CM type ROMs do better with TWRP, whereas stock-based work well with CWM. If your BL is locked, it seems like Nut's dual recovery might be best. Use the PC installer for best results if you can't get any recovery at all.
The other problems you described also sound to me like ROM or kernel issues, and not necessarily lollipop related. Did you do a full wipe before updating, (system,data, and cache)? Did you flash a kernel first, etc., etc...
Like I said, I'm no expert, but I've been helped enough that I'm glad to help if I can. You just might need to add some more info.
The issue with a very bright display is true for my phone as well. I guess that it's rom or kernel related...
Heres what I suggest you do since It worked on mine:
1) Unlock your bootloader here.
2) Re-flash Lollipop FW using Flashtool
3) Boot the phone
4) Reboot Into fastboot mode and in Flashtool flash a custom kernel that has a dual recovery and is for lollipop.
5) Once the phone boots, vol - to enter recovery and flash the latest Supersu zip file to get your fw rooted
6) Download SELinuxMode Changer and set it to permissive
7) This should pretty much fix all problems
Related
Hi guys,
I just unlocked my bootloader with fastboot.
There was not any problem in unlocking. But after unlock when i turned on my phone.
I've noticed that my home button is not working. It is physical normal and not damaged.
If i press home button when my phone screen is off, it can turn on screen. But after turning it on. It's not doing anything. Like is not even working or exist.
My phone was .42 FW Stock ROM and rooted. ( I've changed few things in bootanimation and status bar etc with root explorer but i think i didn't change anything important and it was working perfect)
PS: I've just noticed that my Camera is not working at all. If a press camera icon in Launcher. Phone's screen is turn black and nothing happens. Also camera button not working too. ( OMG- Maybe i shouldn't do that Bootloader unlocking thing
Guys please help.
Thank you so much for reading.
Best Regards.
Try instal some custom rom (MIUI, CYANOGENMOD)
What if i want to use Stock ROM ?
Thank you for answering.
Tried reflashing the firmware with FlashTool?
Sent from my iPad 2 using Tapatalk
I can't flash any ROM using flashtool. It says unplug your phone, enable usb debugging and unknown sources. I checked again and again they are already enabled
do you have drivers instaled properly?
Yes. I can use fastboot commands. Programs can see my ARC in fastbootmode or flashmode. But flashtool can't flash it as i said :/
Now i have CM7 kernel with CM7 installed. My home button works normally. I want Flash to SE Stock ROM. How can i do it without using Flashtool ? (fastboot, recovery mode etc.)
I used wotan server to flash Sony Ericsson Stock ROM (.42). Rooted again with easy root.
Thank you for answering.
Thread can be deleted.
Best regards.
why dont you stay on cyanogen if your bootloader is unlocked
I liked Cyanogen Mod. But when i flashed lastest version (7.0.2). It stuck at BootAnim.
Then i flashed v7.0.1 it worked normally. But in that process i decided that CM7 is not complete for ARC yet and i have to wait a bit more for fully function and stable
Probably i will flash it soon but not now
you still have MIUI rom, it is good to
it happened to me when i unlocked my bl and flashed doomlord's kernal
to correct it i relocked my bl & updated via seus and unlocked bl again
and the problem was gone
everything was working normally again.....
Dear Techies
I love to play around and use new gadgets ans fotware. Android is my first choice but unfortunately this something very new for me. I was looking for Jelly Bean and got it as Pacman. Which i came to know is combo of three ROMS features.
I decided to go for first time for custom ROM with my SOny Xperia Pro MK16i. It was having its official ROM as ICS (b 587 i suppose).
I could read 3 steps mainly one was Unlocking the boot and then Root and then flash ROM. I did first 2 (right i suppose) but when i came to the last one for flashing the custom ROM i suppose i did something wrong.
with flashtool i flashed IMG file in fastboot mode. I was done without any error i did restart to the system. Pacman logo came with SONY under it but then nothing i did 3-4 times but i was left with very dim light screen with nothing on it.
But i suppose this was a better position than now. here i think i did the main mistake i again flashed with recoveryNeo IMG (it was in fastboot folder which i downloaed earlier).:crying:
SInce then its blank no light for first 2-3 attempts for restarting it vibrate but now even it doesnt vibrate.
I dont what to do next lots of question did i bricked my phone. Is that recoverable ? can i still get it back to official ROM if yes then how or can i still put custom ROM if yes then HOW ?
Please help
thanks in advance
Please guys Help me
Hunk2012 said:
Dear Techies
I love to play around and use new gadgets ans fotware. Android is my first choice but unfortunately this something very new for me. I was looking for Jelly Bean and got it as Pacman. Which i came to know is combo of three ROMS features.
I decided to go for first time for custom ROM with my SOny Xperia Pro MK16i. It was having its official ROM as ICS (b 587 i suppose).
I could read 3 steps mainly one was Unlocking the boot and then Root and then flash ROM. I did first 2 (right i suppose) but when i came to the last one for flashing the custom ROM i suppose i did something wrong.
with flashtool i flashed IMG file in fastboot mode. I was done without any error i did restart to the system. Pacman logo came with SONY under it but then nothing i did 3-4 times but i was left with very dim light screen with nothing on it.
But i suppose this was a better position than now. here i think i did the main mistake i again flashed with recoveryNeo IMG (it was in fastboot folder which i downloaed earlier).:crying:
SInce then its blank no light for first 2-3 attempts for restarting it vibrate but now even it doesnt vibrate.
I dont what to do next lots of question did i bricked my phone. Is that recoverable ? can i still get it back to official ROM if yes then how or can i still put custom ROM if yes then HOW ?
Please help
thanks in advance
Click to expand...
Click to collapse
Xperia Pro flashed
Hunk2012 said:
Please guys Help me
Click to expand...
Click to collapse
After flashing the kernel, you need to boot through recovery mode with the PACman build (.zip) available on your SD storage. To log in to recovery mode, as soon as you get the PACman SONY splash screen (when LED turns blue) press the volume down button located at the side of your device. Once into recovery:
1. back up your data
2. wipe all user data and cache
3. Install update from a zip file and pick the relevant ROM
Just in case you're completely locked out and want your old ICS 587 build, just switch off your cellphone, connect it to your PC with Sony PCC installed. In all probability, PCC identifies it as a Sony device but not the model. Follow the steps on the screen and choose xperia pro when the option to install stock OS appears.
I bricked my xperia pro twice before successfully upgrading to PACman 17 so its a pretty normal scenario.
Do let us know how goes it!
Hi everyone,
Before criticizing me for posting this thread please note that I've spent a lot of time googling and trying to find a solution.
Before I begin I want to mention that I'm pretty new to android system. I learned few basics today but must admit I'm a noob. I've had my Xperia Arc S for a while now, but decided to root it (got annoyed with all restrictions + bloadware). But to the point.
After few hours I successfully unlocked bootloader and rooted my device. It's been 7 hours now and I'm really stuck. Finally I decided to get help from you guys - I'm just fed up with it.
Here's my problem:
At the first place I had Android 2.3.4 [4.0.2.a.0.62]. Found out that this version is hard to unlock and root, so I downgraded it to 4.0.2.a.0.42 (which apparently was easier to achieve what I wanted).
Then I followed the guide how to unlock bootloader - succeeded.
Later I used OneClickRoot to root my device - also succeeded.
Now the problem begins - I've read this guide http://forum.xda-developers.com/showthread.php?t=1592104
Tried to install CWM using Rom Manager - failed as I got the message that my LT18i is not supported. Instead I installed X-Parts and using it I installed CWM. Seems it all went fine but I can't access Recovery Mode - and seriously I tried everything: volume up, volume down, hold, pressing few times, tried even with back and menu button. I also tried "Reboot to recovery" option in X-Parts - still no result.
I downloaded SE Extreme Tweak and installed CWM using this program but still nothing.
As far as I know to install new ROM I need an access to Recovery Menu. I want to install Stock ROM 2.3.4 [4.0.2.a.0.62] (the one I had before) and remove unnecessary bloatware.
Any suggestions guys? How to fix that Recovery Mode problem?
My device details:
Sony Ericsson Xperia Arc S
LT18i
Android version: 2.3.4
Buld number: 4.0.2.A.0.42
Thanks for any help!
nadaall said:
Hi everyone,
Before criticizing me for posting this thread please note that I've spent a lot of time googling and trying to find a solution.
Before I begin I want to mention that I'm pretty new to android system. I learned few basics today but must admit I'm a noob. I've had my Xperia Arc S for a while now, but decided to root it (got annoyed with all restrictions + bloadware). But to the point.
After few hours I successfully unlocked bootloader and rooted my device. It's been 7 hours now and I'm really stuck. Finally I decided to get help from you guys - I'm just fed up with it.
Here's my problem:
At the first place I had Android 2.3.4 [4.0.2.a.0.62]. Found out that this version is hard to unlock and root, so I downgraded it to 4.0.2.a.0.42 (which apparently was easier to achieve what I wanted).
Then I followed the guide how to unlock bootloader - succeeded.
Later I used OneClickRoot to root my device - also succeeded.
Now the problem begins - I've read this guide http://forum.xda-developers.com/showthread.php?t=1592104
Tried to install CWM using Rom Manager - failed as I got the message that my LT18i is not supported. Instead I installed X-Parts and using it I installed CWM. Seems it all went fine but I can't access Recovery Mode - and seriously I tried everything: volume up, volume down, hold, pressing few times, tried even with back and menu button. I also tried "Reboot to recovery" option in X-Parts - still no result.
I downloaded SE Extreme Tweak and installed CWM using this program but still nothing.
As far as I know to install new ROM I need an access to Recovery Menu. I want to install Stock ROM 2.3.4 [4.0.2.a.0.62] (the one I had before) and remove unnecessary bloatware.
Any suggestions guys? How to fix that Recovery Mode problem?
My device details:
Sony Ericsson Xperia Arc S
LT18i
Android version: 2.3.4
Buld number: 4.0.2.A.0.42
Thanks for any help!
Click to expand...
Click to collapse
Have you tried flashing a custom kernel? As far as I know, they come with recovery pre-installed. I'd suggest you give the following a go. Should definitely work for you.
http://forum.xda-developers.com/showthread.php?t=1421992
MarcSinger said:
Have you tried flashing a custom kernel? As far as I know, they come with recovery pre-installed. I'd suggest you give the following a go. Should definitely work for you.
http://forum.xda-developers.com/showthread.php?t=1421992
Click to expand...
Click to collapse
Thanks for reply. Well the thing is - maybe it's a bit silly reason - that I love the favourites widget in 2.3.4. As far as I know this widget is not available in any other versions - even custom ROM's....
edit: Sorry just noticed that it's actually "fixed" version of stock Kernel. Thanks, will try to give it a go then
Are these similar to what you're looking for?
https://play.google.com/store/apps/....gowidget.contactwidget&feature=search_result
https://play.google.com/store/apps/details?id=com.contapps.android&feature=search_result
I'm sure Google Play has a lot of what you want.
The first one is. I used it before - need to use Go Launcher with it though, which I didn't really like :/
The one I'm talking about is called "favorites and call log widget" (sorry apparently as a new user I can't post outside links to show you what I'm exactly after)
@ MarcSinger
thanks again for trying to help, I've read the post, however it still requires to boot the phone in recovery mode, which I'm not able to do
Any other suggestions guys?
Guys I sorted it out!!
I unrooted the phone (don't know if this helped), rooted again, then found this app "5.0.2.7-nAa-r2 Auto-Installer", installed it on my device and installed CWM from there. Now I can access Recovery Mode. Finally I can carry on with flashing ROM. Will try to install what MarcSinger posted.
nadaall said:
Guys I sorted it out!!
I unrooted the phone (don't know if this helped), rooted again, then found this app "5.0.2.7-nAa-r2 Auto-Installer", installed it on my device and installed CWM from there. Now I can access Recovery Mode. Finally I can carry on with flashing ROM. Will try to install what MarcSinger posted.
Click to expand...
Click to collapse
If your bootloader is unlocked then simply flash a kernel with CWM, no need to install it via the apps.
Sent from Myushi
i am also havin the same problem after rooting the phone and after installing CWM through X-parts i am not able to open my phone in recovery mode please help .... i am not able to open my Xperia Arc LT15i in recovery mode
SarcasticGenius said:
i am also havin the same problem after rooting the phone and after installing CWM through X-parts i am not able to open my phone in recovery mode please help .... i am not able to open my Xperia Arc LT15i in recovery mode
Click to expand...
Click to collapse
Same here with my xperia neo MT15i/2.3.4/Lock Bootloader
nadaall said:
Guys I sorted it out!!
I unrooted the phone (don't know if this helped), rooted again, then found this app "5.0.2.7-nAa-r2 Auto-Installer", installed it on my device and installed CWM from there. Now I can access Recovery Mode. Finally I can carry on with flashing ROM. Will try to install what MarcSinger posted.
Click to expand...
Click to collapse
Thanks a lot, I had the same problem and it helped! Now I have a working CWM too :good:
mchaals said:
Thanks a lot, I had the same problem and it helped! Now I have a working CWM too :good:
Click to expand...
Click to collapse
Glad I could help, good luck!
u solved it yourslef, lol.
this app is cwm-auto-installer. i always use it after rooted to install cwm though i flashed the custom kernel had cwm pre-installed.
2 cwm is just better for me, i dont know why but i use lupusv14 kernel, in kernel's cwm, it doesnt do the action "advance restore" like restore system only, so i return to manual cwm to do this
Sent from my LT15i using Tapatalk 4
njckjen said:
u solved it yourslef, lol.
this app is cwm-auto-installer. i always use it after rooted to install cwm though i flashed the custom kernel had cwm pre-installed.
2 cwm is just better for me, i dont know why but i use lupusv14 kernel, in kernel's cwm, it doesnt do the action "advance restore" like restore system only, so i return to manual cwm to do this
Sent from my LT15i using Tapatalk 4
Click to expand...
Click to collapse
hi there is something i cant understand..im legendary noob on installing kitkat so here i got a problem after i select a kernal in flashtool i mean dat boot.img n well disconnected my phone i couldent enter to recovery mode with my arc s and that screeen keep coming repeatity now can you help me what exactly to do? like you are teaching to baby thanks in advance
same problem....
i read this post now after 2 year of original post.because now im having same problem,i rooted my phone but now i canot enter clock wok mod recovery,i tried x-parts,rom manager,recovery x....it says after tryin to install cwm that instalation complete but i canot enter recovery mode neither by presing down vol at sony logo nor by clicking reboot in recovery mode in x part or any other software...i have unlocked bootloader.
my phone specs are
sony ericsson arc s LT18i
android 4.0.4
build #4.1.B.0.587
thanking in anticiaption.....
alyakram said:
i read this post now after 2 year of original post.because now im having same problem,i rooted my phone but now i canot enter clock wok mod recovery,i tried x-parts,rom manager,recovery x....it says after tryin to install cwm that instalation complete but i canot enter recovery mode neither by presing down vol at sony logo nor by clicking reboot in recovery mode in x part or any other software...i have unlocked bootloader.
my phone specs are
sony ericsson arc s LT18i
android 4.0.4
build #4.1.B.0.587
thanking in anticiaption.....
Click to expand...
Click to collapse
sr, i just seen this notif. maybe cwm was not installed actually, though these apps (xpart, rommanager, recovery...) said is was completed. i think these apps cannot install by ifself (if i remember exactly, cuz a long time ago n i dont use arc anymore). so u must use cwm-auto-installer app, install this app, open it then tap 3rd line to install cwm inside this app. i always do that after root (though i use kernel have cwm preinstalled).
after that, when u power on ur phone, ull see green led light which means u have cwm already n able to access cwm by pressing volume (-) when that led light appear, through that moment u cant access anymore n must reboot to try again. or easier u can use [ndr utils] app, have all reboot option.
alyakram said:
i read this post now after 2 year of original post.because now im having same problem,i rooted my phone but now i canot enter clock wok mod recovery,i tried x-parts,rom manager,recovery x....it says after tryin to install cwm that instalation complete but i canot enter recovery mode neither by presing down vol at sony logo nor by clicking reboot in recovery mode in x part or any other software...i have unlocked bootloader.
my phone specs are
sony ericsson arc s LT18i
android 4.0.4
build #4.1.B.0.587
thanking in anticiaption.....
Click to expand...
Click to collapse
If you have an unlocked bootloader just flash a kernel with CWM on it, why go through all the trouble to use CWM auto installer if it doesn't work for you?
You could also try connecting your phone with your computer, make sure you have adb drivers installed and adb turned on in developers settings on your phone , then just type in this command within a terminal: adb reboot recovery .
Please Note that this solution does not mean you haven't got recovery installed on your phone, so this one might fail.!
Have you guys tried holding power + camera? I once had a recovery installed which used the camera button to enter recovery
Also do not press the power button for to long or your phone might just restart and doesn't have the time to boot in recovery, so start up holding volume down or up and press power, realease the power after like 7 seconds , (can't remember how long it really was so experiment.... )
I tried flashing a kernel believed to be ExcaliBur on my HTC One M8, but as soon as i rebooted the screen was black yet still on.
I know it's not bricked completely because i can still hear sounds, feel vibrations and see the LED's work properly. Basically I have a "blind" phone. I have began to look into a way to capture my screen one frame at a time with my computer.
Please help me!
Running Android 4.4.4 Cyanogenmod Snapshot 11
T-Mobile
TWRP 2.8.0.3
Tried getting back to bootloader and flashing back the boot.img you had before flashing new kernel?
If the device still has "some" interaction then you should be able to connect it to PC and use the adb reboot bootloader command to boot it into bootloader.
BerndM14 said:
Tried getting back to bootloader and flashing back the boot.img you had before flashing new kernel?
If the device still has "some" interaction then you should be able to connect it to PC and use the adb reboot bootloader command to boot it into bootloader.
Click to expand...
Click to collapse
I actually DID just get into my bootloader. I had to mess around by pressing the buttons until i finally got it to boot into bootloader. Now I flashed a stock kernel for now, I always keep it in my SD Card.
I found you can use a program called Wondershare MobileGo for Android that can read whatever is on your phone if you happen to be "blind" like me.
P.S. I really need a kernel for CMod that has fast charge. Currently ExcaliBur is off the list.
I haven't heard of Wondershare MobileGo, seems interesting.
I can't help with custom Kernels, I always stick with stock, haven't flashed a custom kernel since way back with my S3. Sorry, can't help there.
Thanks anyways! Notice I got my phone working again! I flashed the stock, and then reflashed CMod and nothing was wiped. Interestingly...
Sent from my One M8 using XDA Free mobile app
That's quite lucky, any other time I've heard of this happening the phone's died completely.
Hi guys,
(Samsung S4 Mini GT-i9190)
I could really use some help.
I have been searching all over and perhaps I'm not understanding what is being said so if it sounds familiar and there is a solution then i'm thankful.
So about a week ago, the phone came back from repairs and had the motherboard replaced after the phone was washed by accident. Nonetheless, there hasn't been any hardware defects besides signal loss now and then.
When the phone came back, it had 4.2.2 and it automatically picked up the update to 4.4.2 which I did. The phone worked fine until 2 days ago, where it just stuck at the Samsung galaxy gt-i9190 screen and just freezes there.
I can boot into a custom recovery (Philz) (not stock recovery for some reason) and download mode. I then attempted to install CM 11.0 as I got frustrated. It worked, booted past animated logo and install the apps until i came to the language section where the touchscreen which didn't work (unresponsive). I then reverted back to the stock ROM found at sammobile (i9190xxxCOD2XFA - South Africa), loaded the custom recovery and still no booting past the first screen. The custom recovery touchscreen (Philz) is also non responsive (besides using the volume keys, home button and power for navigation).
I flashed a couple of times, nothing works.
Is there a root cause to these issues? The unresponsive screen, not booting properly?
Some info: KNOX is voided 0x1
Please help!! Thank you in advance
It's not „root“ that cause your problem. You should have to choose right recovery for your model. Flash back to original ROM and look for one of fully supported custom ROM here on the XDA and fallow all steps how to flash it properly. Succes ! Cheers !
Alright, I'll try that. What I did in the meantime was flash, Slimkat 4.4.4 UNOFFICIAL rom for I9190 (http://forum.xda-developers.com/showthread.php?t=2708677).
The rom booted into the andoird system but the touchscreen is still unresponsive.
@Boombastical .. If you can help me by giving me a guide in order to do what you say, then please do help. Even in recovery especially TWRP the touchscreen is unresponsive except for ClockWorkMod and Philz. So i don't know if it is hardware related or I'm doing something wrong.
Its driving me crazy :crying:
Update
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
GeezyTab88 said:
So what I did last night:
I loaded the SlimKat rom and based on the stock bootloader and after doing a couple of battery pulls the screen starting functioning properly. However it was just luck or could've been something more technical.
I need help in understanding why that happened.
Then I decided I dont trust my method and reloaded the stock 4.4.2 firmware from sammobile. What then happened, is that it booted past the "Galaxy GT-I9190" screen into the samsung logo and then installed the applications. Come to the choose language screen, the touchscreen became once again unresponsive.
Bear in mind, that when I did a reboot with the stock rom, it didn't want to boot past the screen and just hung there.
So what could my problem be?
Is it the rom that I used? Using Unified Android Tool, I saw my region code is GB which I haven't seen anywhere in the stock roms.
Could the system somehow become corrupted? Emmc, partitions? Could the screen calibration be out of sync?
Must the bootloader always be the stock one? Are there custom bootloaders that one can use?
Please help, thanks
Click to expand...
Click to collapse
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Confirmed for that is
GeezyTab88 said:
Possible solution:
So I thought it could be screen calibration so this is what I did to make my phone work.
I loaded the CARBON Rom as I somehow lost root privileges with SlimKat. It loaded into the OS as per normal but the touch screen didn't work. So after numerous battery pulls, i read this post http://forum.xda-developers.com/showthread.php?t=2353972&page=1 .
So then I connected the phone to the pc (having had the samsung drivers installed as well as adb) and booted into cmd promt as admin.
This is what I did in cmd prompt:
cd adb
adb shell (make sure there is a "#" as that ensures you that your phone is rooted)
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal (did this several times)
@xcxa23
It then still didn't work (the touch screen) then somewhere on one of the pages in the above post, someone mentioned holding home button. I switched the phone off, I then held the home button (until it booted into the OS) and then powered the phone on. The phone booted into the OS and presto the screen worked again. I did a reboot and the screen is still fine.
Again I'm not sure if its that exact method but what I am sure of, is that I did a clean rom install (an option in Philz touch recovery), wiped the cache, formatted the options (boot, system, cache, preload, data) in mounts and storage and then proceeded to install the rom from the sd card.
I haven't tried with the stock rom as yet so if this helps you, goodluck and if you can help improve on this method or help me understand why this is happening, it would also be appreciated.
Thanks
Click to expand...
Click to collapse
Hey guys, just a quick update.
I reloaded Cyanogenmod mod CM13. I can confirm that my screen didn't freeze up and booted perfectly. I also then decided to take a chance adn reload the stock rom 4.4.2 and it also worked perfectly and booted directly into the OS.
I'm guessing the screen calibration was out.
So if this happens to you, I would suggest loading a custom rom and doing the screen calibration reset through adb and then test again with another custom rom. Once you comfortable, you can reload a stock rom.
I used Philz Touch for recovery
Thanks to everyone who put posts up .. Time to rest
Not working again!!
Hey,
So in my previous post I said I got it to work. Well I did, up until a few minutes ago when the phone just decided to freeze up again. I restarted the phone and would you know, back to square one!
I've noticed issues that I'm wondering if they could be the problem:
1) The audio didn't work at all. By audio, I mean the mic. When I did voice recording, it just gave static, whatsapp calls, the other person can't hear you as well as regular phone calls.
2) I just rooted the phone in order to change the audio_policy.cnf and delete lines relating to the above audio problem but then the screen, return, and menu button didn't function. The screen could still rotate until I pressed the power button to lock then unlock and then it didn't unlock :crying:
So once again, some help guys please. Is it rom related, hardware (motherboard, chip) or software that just isn't working right? Could it be KNOX?
Thanks