Related
Hello All,
First time post and as an offering, I will say 'thanks' to anyone that responds in a positive manner to my post (trying to win some friends) :laugh:
Here's my issue, I have an Arc S LT18i.
Unlocked bootloader and rooted.
Whenever I flash anything custom the touch screen fails to respond, i've flashed LupusV7, slim bean 3.1 and 3.2 (with arc fusion 3.6 and 4.5) and Super Jelly Bean. All seemingly start without any issues and the physical buttons work no problem. BUT the screen refuses to work in anyway at all!!
I have made sure I wiped the system, cache and delvak (sp?)
Any help greatly appreciated, I am a NOOB but underneath it all I'm just trying to make the most of this wonderful Arc S...
Anything you want to know, please ask away...
Please help.
Namaste
Ricky:fingers-crossed:
Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™
Same thing!!
msc3169 said:
Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™
Click to expand...
Click to collapse
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky
ricky7D said:
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky
Click to expand...
Click to collapse
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた
compatible ROM and Kernel
popthosegaskets said:
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??
ricky7D said:
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??
Click to expand...
Click to collapse
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた
You sure you installed device-specific patch / chose correct phone in AROMA?
Kernel or ROM issue?
popthosegaskets said:
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello,
As previously mentioned, the reccomended kernel is Lupusv7, When i flash this Kernel into recovery mode, all looks well but as it has a touch screen interface this still doesn't work!
I'm presuming that it cannot be a conflict as it's happen before I instll the new ROM etc... the touch screen doesn't even work within the GUI of the Lupusv7 kernel.
I can get multiple ROMS to load with different kernels but so far, none have booted with the touch screen working!!
I am very much a noob but have read loads of articles on how this should be done, unless i'm missing something very obvious which isn't stated then I dont see anyone else having this issue.
Any clues people? :good:
Thanks, Ricky
AROMA?
Someguyfromhell said:
You sure you installed device-specific patch / chose correct phone in AROMA?
Click to expand...
Click to collapse
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky
here what to do
- Make sure you had installed Official 4.0.4 ftf pack
- When flashing official ftf pack remember to exclude / tick these things:
1. simlock.ta (Exclude TA)
2. Kernel.sin (Exclude kernel)
3. FOTA (Exclude FOTA)
After flash successful, power on your phone and let it start completely
- Now you can start to install any ROM
1.Flash the Recommended Kernel: Vengeance , KTG Anzu , RUSH
2. Place ROM on SD card
3. Power off the phone and boot into CWM
3. Backup and restore > choose Backup
4. Wipe Data/Factory Reset
5. Mounts and storage > Format /system
6. Advanced > Wipe battery stats
7. Install zip from SD card > Choose the rom
8. if rom uses aroma Follow on screen instructions on AROMA, remember to choose "Unlocked bootloader" and also the correct kernel modules and of course the correct phone model
9. After complete installation tick "Reboot" and let the phone restart
10. Give the phone a good full charge, and enjoy ur phone !
11.THE MOST IMPORTANT THING PRESS THANKS if I helped
ricky7D said:
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky
Click to expand...
Click to collapse
Then did you install the device-specific patch?
ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)
AROMOA guide?
Someguyfromhell said:
Then did you install the device-specific patch?
Click to expand...
Click to collapse
on all the ROM guides, I have never seen a part where it says i should install a device specific patch, do you have a link to where these may be?
Or even a ROM with guide where it says this? I'm very happy to follow that to get this working. I have no preference to CM10, Slim Bean, Racing Bean etc... as of yet i've not been able to use any of them.
Thanks for the continued response.
Ricky
THANK YOU
eakav said:
ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)
Click to expand...
Click to collapse
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Does anyone else have an idea on how to update the touch screen firmware?
Really appreciate the feedback, thank you one and all!!
Ricky
ricky7D said:
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Ricky
Click to expand...
Click to collapse
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...
No touch
eakav said:
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...
Click to expand...
Click to collapse
I have same issue have tried many stock based roms and kernels no problem but any CM based rom I have no touchscreen.
You can reboot and about 1 in 5 times it will work
Maybe it only affects certain versions of the phone. I even tried re-locking bootloader and doing official sony update then tried CM again I tried 7.1,9 and 10
same problem.
Here's where I am...
UPDATE:
So, here is where I am. Using advice from previous replies I have managed to install Xperia Ultimate HD and this is working off of the Lupus kernel without any issues. I'm still unable to get ANY Jelly Bean roms working...
Maybe my device will just not work on JB :crying:
Any other tips or tricks are greatly appreciated, would love to get JB working on here my beloved Arc S.
Ricky :good:
Any news here?
I have the same issue over here with a colleagues LT18i
I have same problem, touch screen doesn't work on many different kernels... only work on stock kernel
Any news about this problem?
Hello everyone,
So I've looked around on this topic and it's still an issue, albeit a minor one. I have the T-Mobile HTC One M8 phone........ unlocked/rooted, and S-OFF'd. I am currently using ViperOne M8, which is awesome!
When I boot to HBOOT after installing new firmware the OS line is filled in, but after booting to Recovery and going back to HBOOT, the OS line is now blank. I've been told this is a bug in TWRP, and not a bug or issue anywhere else. I've tried 2 different approaches to fixing it. One entailed flashing a new ZIP (or flashing something), but the instructions stated that I needed to boot to Recovery while in Stock Recovery, which my phone does not do. It's only when I use a TWRP Recovery that I am able to go into any Recovery Menu. The other one had to do with flashing a zipped firmware, but even though that flash worked just fine, it still didn't resolve the OS issue. I have tried looking all around, but either I'm missing something, or it's just not knowing enough about what I'm reading to recognize the right answer.
So please, will someone tell me HOW do I get rid of that pesky TWRP bug that causes the OS line in HBOOT to blank out after only 1 visit to recovery post-firmware update?
I would appreciate ANY info you can give me.
Thank You,
RockStar2005
The Answer!!
IGNORE this post!! Scroll down to my "2nd September 2014, 5:17 PM" post instead for what you're really looking for!
RockStar2005
Ok got it!
Download the modified TWRP from here:
http://forum.xda-developers.com/show...php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
RockStar2005 said:
Ok got it!
Download the modified TWRP from here:
http://forum.xda-developers.com/show...php?p=54054835
You are going to have to flash your current firmware first before installing it for the OS info to show up again in HBOOT. You can use the Flashify app to install it or else just do it the PC/ADB way using command prompt like I did. It totally worked for me, so go ahead and try it!!
If you have questions on how to flash anything, lemme know.
RockStar2005
Click to expand...
Click to collapse
Unfortunately your link to the modified TWRP leads to a 404.
Is there a new thread?
The True Fix
RealZac said:
Unfortunately your link to the modified TWRP leads to a 404.
Is there a new thread?
Click to expand...
Click to collapse
Hey Zac,
Forget about that TWRP. It wasn't good. Please DELETE any backups you made using it and the twrp image file itself as they are all corrupted and won't boot up (I found this out after my initial post here). Read this post I put elsewhere for the real deal Holyfield lol:
So I ended up finding a RELIABLE fixed current version of TWRP on xda you may wanna check out. You can find it here: http://themikmik.com/showthread.php?16278-SPRINT-RECOVERY-TWRP-Recovery-(UNOFFICIAL)-v2-7-0-4 (Go to that link then Control + F this: "Downloads TWRP Recovery 2.7.1.0 (DH) | Mirror (AFH) - build date: July 13, 2014". I downloaded from the Mirror link.)
Don't worry about it saying Sprint...... the dev CONFIRMED it works for all variants/carriers. So after creating a new backup using the standard twrp, I went back to stock recovery, re-flashed my most recent firmware (2.22.401.5), and then switched over to that new version of twrp........ created a new backup and then restored it using that new version. Worked like a charm!! And the "blank OS" issue........... gone! I highly recommend it!!
If you have any other questions Zac, please post here and I will respond.
RockStar2005
Thank you for this detailed answer!
I will test it.
RealZac said:
Thank you for this detailed answer!
I will test it.
Click to expand...
Click to collapse
You're quite welcome! And make sure to check HBOOT (Bootloader) AFTER going to fixed TWRP to verify the OS line is NOT blank.
RockStar2005
RockStar2005 said:
You're quite welcome! And make sure to check HBOOT (Bootloader) AFTER going to fixed TWRP to verify the OS line is NOT blank.
RockStar2005
Click to expand...
Click to collapse
Every time I flashed the firmware I realized that "OS.." displayed the correct version.
I double an triple checked that.
So I did know that this blank OS only showed up after flashing the TWRP standard version.
RealZac said:
Every time I flashed the firmware I realized that "OS.." displayed the correct version.
I double an triple checked that.
So I did know that this blank OS only showed up after flashing the TWRP standard version.
Click to expand...
Click to collapse
Zac,
Ok cool.
Have a good one!
RockStar2005
RockStar2005 said:
I needed to boot to Recovery while in Stock Recovery, which my phone does not do.
Click to expand...
Click to collapse
It does, when you reach the screen with the small phone in the middle(upside down exclamation mark in it) just press volume up(hold) and tap power button. That takes you into stock recovery menu.
Just for future references... :good:
BerndM14 said:
It does, when you reach the screen with the small phone in the middle(upside down exclamation mark in it) just press volume up(hold) and tap power button. That takes you into stock recovery menu.
Just for future references... :good:
Click to expand...
Click to collapse
Hey BerndM14,
I'm 99% sure I tried doing that when I got that screen you just described, and all my phone did was reboot.... and not to recovery either. I dunno. It's not a big deal as I've since resolved the issue by finding a newer "fixed" version of TWRP and/or firmware (whatever the issue was, I think it was with TWRP though).
Maybe next time I do a firmware upgrade and have to go back to stock recovery, I'll try it again.
Thanks!
RockStar2005
RockStar2005 said:
Hey BerndM14,
I'm 99% sure I tried doing that when I got that screen you just described, and all my phone did was reboot.... and not to recovery either. I dunno. It's not a big deal as I've since resolved the issue by finding a newer "fixed" version of TWRP and/or firmware (whatever the issue was, I think it was with TWRP though).
Maybe next time I do a firmware upgrade and have to go back to stock recovery, I'll try it again.
Thanks!
RockStar2005
Click to expand...
Click to collapse
I also had the phone reboot, problem I had was that I held volume up + power, which wasn't right. Just hold volume up and TAP power. Either way though.
For future references like I said :good:
BerndM14 said:
I also had the phone reboot, problem I had was that I held volume up + power, which wasn't right. Just hold volume up and TAP power. Either way though.
For future references like I said :good:
Click to expand...
Click to collapse
BerndM14,
Ok I see.........so TAPPING not holding Power and holding Volume+Up. Got it.
Thanks for the clarification!
RockStar2005
RockStar2005 said:
Zac,
Ok cool.
Have a good one!
RockStar2005
Click to expand...
Click to collapse
Works great & flawlessly! Thank you for the help!
RealZac said:
Works great & flawlessly! Thank you for the help!
Click to expand...
Click to collapse
Zac,
Sweett!! You're very welcome!
RockStar2005
Hi
I have a problem. I searched solution in google and on this forum but i can't find working solution. So I flashed this rom: http://forum.xda-developers.com/xperia-m/development/rom-resurrection-remix2013266094-t3217455
and when I wanted to call to someone pop-up is showing this text "Unfortunately, Phone has stopped". I had same problem with Cyanogenmod 12 and 12.1. This is so annoying that i can't repair it alone. I hope for fast help.
tarzan9521 said:
Hi
I have a problem. I searched solution in google and on this forum but i can't find working solution. So I flashed this rom: http://forum.xda-developers.com/xperia-m/development/rom-resurrection-remix2013266094-t3217455
and when I wanted to call to someone pop-up is showing this text "Unfortunately, Phone has stopped". I had same problem with Cyanogenmod 12 and 12.1. This is so annoying that i can't repair it alone. I hope for fast help.
Click to expand...
Click to collapse
did you clean install before install any custom rom? like cyanogenmod or RR? try to wiped system , data , cache and internal storage. and try to install that with no any gapps package is installed. if problem is fixed may be problem is from your gapps package, but if problem still exist i want to ask something. are you dual sim device or single sim device?
EDIT : and remember. before install cm 12 and up you need base rom android 4.3 or 15.4.A.1.9 to running this custom rom properly or same with dual sim device
I'm Single sim. I did full wipe before installing it. I tried also without gapps. So now i got another problem. Because my USB port in phone doesn't work. So i can't flash stock rom :/ Zipaligned stock rom will work?
tarzan9521 said:
I'm Single sim. I did full wipe before installing it. I tried also without gapps. So now i got another problem. Because my USB port in phone doesn't work. So i can't flash stock rom :/ Zipaligned stock rom will work?
Click to expand...
Click to collapse
i don't know, but flash ftf stock firmware is required for back it stock .
hmmm may be you need to ask another member here, try to contact @Bonoboo or send pm to him. i think he can solved it
Nicklas Van Dam said:
may be you need to ask another member here, try to contact @Bonoboo or send pm to him. i think he can solved it
Click to expand...
Click to collapse
Again, I'm not developer to resolve problems in ROM's.
tarzan9521 said:
and when I wanted to call to someone pop-up is showing this text "Unfortunately, Phone has stopped". I had same problem with Cyanogenmod 12 and 12.1
Click to expand...
Click to collapse
At least try to get logcat to know what's wrong.
Install app Logcat Extreme
Launch and give root
Press 4th button and tap Confirm
Minimize app and produce crash
Return to app
Press button with floppy disc
Select Save current log
Upload file from folder /sdcard/LogcatX
Also you can back to stock without PC: use backup
This really can be solution. Maybe radio stuck in bad state due custom ROM's.
Now I got all what I need to be happy Now I will try back to stock with thread you posted and I will write if everything will be ok. BIG THANKS to you
Everything is now ok Finally all works. I'll stand with stock rom, maby little change it. Thx for help
tarzan9521 said:
Finally all works. I'll stand with stock rom, maby little change it
Click to expand...
Click to collapse
Reverting to stock was suggested as fix for custom ROM's.
So maybe try them too. Curious about result.
Bonoboo said:
Reverting to stock was suggested as fix for custom ROM's.
So maybe try them too. Curious about result.
Click to expand...
Click to collapse
So maybe you recommend any rom? Now i got another problem! The Volume +/- buttons doesn't work :/
I'm pretty sure this has been asked a lot, but I'm trying to install the "TeamSPR Rom" and i'm following the steps exactly. I still get stuck on the bootscreen with the logo with the blue LED glowing. What am I doing wrong, and this happens with TeamSPR and Renegade.
Software Version: G920PVPU3CPF4
Hardware: G920P.02
Model: SM-G920P
Android: 6.0.1
Saafir said:
Wait 20 minutes.
Click to expand...
Click to collapse
My versions are correct for this right? and do I need anything else besides twrp?
steezoe said:
My versions are correct for this right? and do I need anything else besides twrp?
Click to expand...
Click to collapse
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Saafir said:
From the information in your post, you seem to be on the right track. That ROM has taken upwards of 25 minutes to boot for some folks. As long as the blue light is slightly pulsing, it's doing it's thing. As long as you have TWRP installed and working, you should be good to go.
Click to expand...
Click to collapse
So pulsing plus the samsung logo, is a good thing?
koop1955 said:
Make sure that you are rooted (goes without saying) and using the correct version of TWRP: http://forum.xda-developers.com/spr...uide-links-files-update-root-restore-t3366862
Click to expand...
Click to collapse
And I'm using the latest TWRP.
p.s. Thank you guys so much, I'm skepticle when it somes to asking for help on forums, cuz usually people are short tempered and or a-holes. I really appreciate it though.
1 last thing, do i install/flash the OTA part after it optimizes all the apps?
finished everything, it's booted up now, but my screen is spamming "unfortunately, "APPNAME" has stopped" is that normal?
EDIT: Can't get into my text messages either.
Saafir said:
You shouldnt receive any errors. I would reboot to TWRP, do a wipe and reinstall the ROM. Let the device boot and set it up. Once all is good with the initial install, reboot to TWRP and install the update.zip. This should ensure a nice clean start.
Click to expand...
Click to collapse
1. Flashed ROM, waited 20 is mins.
2. Phone loaded up, restarted into TWRP and Flashed the OTA zip.
3. Phone loaded up. This is when I start getting a popup saying "Unfortunately the process android.process.acore has stopped working." and my message app still won't open after i cleared cache and data.
Thanks in advance
Saafir said:
Set the device up before flashing the OTA.
Click to expand...
Click to collapse
Meaning I was supposed to wipe everything on my phone?
Saafir said:
Setup the device as go through the Setup Wizard..
Click to expand...
Click to collapse
I did exactly that. Im currently reflashing the Full ROM taking longer at the samsung screen. But I'll wait. If all else fails I'll probably go back to stock.
I'm now back to stock 6.0.1, going to give this one more go.
Would anyone mind giving me specific step-by-step directions. please?
I feel like im forgetting something crucial.
everthing finally worked out. just having an issue with xposed literally taking hours at the boot screen
Hello, i have a a5y17lte (samsung galaxy a5 2017) phone running custom rom. When i turn up the volume on anything(notifications, media or even alarm) its extremely loud. why does this happen please if anyone knows, help. it is driving me crazy. i have had this issue for far too long.
Install Volume Manager and see if each slider works separately.
ze7zez said:
Install Volume Manager and see if each slider works separately
ze7zez said:
Install Volume Manager and see if each slider works separately.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
THANK YOU A LOT BROOO
i flashed other roms on my sm a520f phone and when i flashed magisk the volume got messed up again. i factory reset it and it is still very loud and messed up. i tried everything from volume manager to trying to find a video on youtube. nothing is working. if anyone knows how to fix this please respond to this tread. i am loosing my mind. I also tried with other roms (without magisk) and that didnt help.
Before installing the custom ROM, format the data partition.
ze7zez said:
Before installing the custom ROM, format the data partition.
Click to expand...
Click to collapse
I do that before i install any rom. I tried it and it didnt work, volume was still insanely loud
If you go back to the stock ROM and the problem remains, it could indicate a hardware failure.
ze7zez said:
If you go back to the stock ROM and the problem remains, it could indicate a hardware failure.
Click to expand...
Click to collapse
ok
use [vol-down + power] to force reboot!