[Q] Touchscreen problem after install Webtop hack - Atrix 4G Q&A, Help & Troubleshooting

Anybody have this problems???? I recently decided to try install the webtop hack over hdmi (by _unknown) using the cmw zip file provided by Ronaldo. after successfully hacked and used it on my TV, i now have a problem with the touchscreen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The area circled in the image, is not registering any touch. i cannot choose Motorola Widget, i cannot press the back button in Dialer, i cannot choose Sign In when you first set-up the Google Account. It seems like that line on the screen is dead or something.
i tried format data/cache/system/ in recovery mode and fastboot mode, i flashed several ROMs (Alien, Aura, piCRUST even sbf the original 4.5.91 from Motorola) to see if it's ROM-related but problem not solved. i even replaced the screen protector and its still the same.
anyone have seen this before and suggest a solution????

- Update: i also try Touchscreen Booster suggested in another thread, but still no help.
- Also, the navalynt ROM does have a new kernel, which i did flashed, but the problem is still there. i flashed back to Alien with the default kernel, the touchscreen is still messed up.
anyone suggest something???

Reboot into CWM and do a "permissions fix".
As your last resort, clean install stock 2.3.4 with full wipe.
If that doesn't help, then unfortunately your digitizer is dying.

Did you skipped the MotoBlur account setup?
If so, then try to set it up and see if that helped.
Cheers!
Rayan
Sent from my Atrix using Tapatalk

Rayan said:
Did you skipped the MotoBlur account setup?
Click to expand...
Click to collapse
i did Motoblur setup, that's why i was stuck at the Google sign-in account, had to rotate screen to select Sign In
xploited said:
Reboot into CWM and do a "permissions fix".
As your last resort, clean install stock 2.3.4 with full wipe.
If that doesn't help, then unfortunately your digitizer is dying.
Click to expand...
Click to collapse
I tried permission fix last night and the problem is still there. i also did a clean install of stock sbf 2.3.4 and fully wipe everything i can think of ( i thought it was the webtop hack that cause the problem, so i tried to delete all ) but its still there. i think this might be a hardware problem at this point. this sucks
also, my phone's root is now crazy im on Alien 4. it denied access of Quickboot but granted access to Root Explorer, which is weird.

ok, so i have tried everything i have searched on this forum: permission fix, pdsfix flash, change the value of touchpad.cfg, reflash stock sbf twice, and im still having this problem (see picture below). anyone know what is the symptoms of this ????
(i flashed ROMs occasionally, from stock to Alien, to Aura, to Homebase, i also tried webtop hack over hdmi).

anyone can help define my screen problems like in the picture???? i press one spot and the screen registers 2 touch. i now have 2 dead area on my screen.

Holy hell this is EXACTLY what my phone is doing.Except mine is randomly touching the top left corner of the screen. So when I type it enters the letter q no matter what letter I hit. Today it got so bad that everytime I hit the backspace button it would type q 5 times.
It seems asthough the multitouch hack seems to scew up the digitizer.
When I "hit" the phone (against my hand, and the phone is in a Otterbox) sometimes it would fix it. Or if a press hard on certain corners of the glass.
I reflashed the phone today to Home Base, and it hasnt done it since. I even ran Quadrant and Smart bench for a hour, while running at 1.3Ghz, and it didnt do it. So its not the phone heating up. But I am not certain its fixed. Its very random.
My only answer is the digitizer. Which is gonna suck. Not going to be as easy to fix as a iphone..

Related

Encryption Unsuccessful? Please Help

So i was using my vibrant running DocMasters ics v5 when suddenly my phone rebooted only to be greeted with this "Encryption Unsuccessful" screen that i've never before seen in my life. Not knowing what to do i clicked on "Reset phone". 1 minute later this "Encryption Unsuccessful" screen appeared again so i went into CWM...factory reset..clear cache...and flashed DocMasters ics v5...again the screen appeared. Finally I decided to start from scratch and entered "Download Mode" and flashed back to stock 2.1...Now my phone goes into a bootloop...and i am unable to enter CWM...dont have access to my internal memory/nor sd card. I've tried everthing I think...but know luck at all. So my point is guys. I officially have the first Soft Bricked Vibrant. Those who said this phone was unbrickable...well i managed to do it...of course unintentionally.
RIP Vibrant: 11/20/2010 to 3/25/2012
Oh here is a screen shot i found of the "Encryption Unsuccessful" screen. I can still enter Download Mode so i guess there maybe hope after all. But i dont know where to start. Any help or advice would be greatly appreciated.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is EXACTLY what happened to my phone too! I made a thread about it... no one was able to find a solution... .
I'm pretty sure its completely bricked, I've tried EVERYTHING. Luckily, I can upgrade in about a week...
Try flashing Eugene's froyo that does not brick.
@lolrus101...Yeah i have tried everthing from flashing back to stock 2.1 to executing adb commands to try and unbrick this phone. I think at this point it is impossible to fix unless Samsung gets a hold of it...wich is not an option since it is out of warranty. Anyways there no need to worry anymore since i just bought a Galaxy Nexus (GSM).
@djquick...Is Eugenes Froyo flashable through odin or heimdall? I cant access CWM only download mode. If not well i give up. I'll just wait till my GNEX arrives.
Thanks for replying guys.
Eugenes that does not brick is odin flashable, just search it.
Cool it is odin flashable. I guess i'll give it one more try. Lets see if this thing really is unbrickable.
I just flashed Euguene's Froyo rom and there are some good signs and bad ones. Well the good news is there is no more boot loop at the first boot screen (Vibrant Samsung logo)...The bad news is there is what appears to be another boot loop at a different boot screen (Galaxy S Animation). After the animation the screen turns completely off and the led buttons stay lit. I let it sit for about 10 mins and nothing happened. I followed every step in Eugene's guide inlcuding the adb command "adb reboot".
I'll reflash it and wait a little longer lets see if it works.
If you got past that stupid message, just reflash to a regular stock rom 2.1.
Here's a link to help: http://forum.xda-developers.com/showthread.php?t=848737
Follow the directions to a T. Usually works like a charm everytime
I give up
After flashing Euguene's rom nothing happened. Then I flashed T959UVJFD.tar
stock 2.1 and i get the same results. Well i guess this is it then. This phone is officially "soft-bricked". I think i've tried almost everything now. I can wait till my new Galaxy Nexus arrives. This phone i will not root i don't want to brick it like my vibrant.
Even though i wasn't able to fix my phone i truly appreciate the help guys.
Thank you.
I actually just picked up a T-Mobile Nexus S GT-I9020T also and I rooted it as soon as I took it out of the box
Ha that's one thing i probably won't do this time. The only reason i decided to root my phone in the first place was to get an AOSP android build and to get rid of all that Samsung and Tmobile bloatware. Of course rooting my phone won't be necessary this time since my new Galaxy Nexus GT-i9250 will come preinstalled with the latest google build in ICS. Along with that it will not have any bloatware from any carriers since it is unlocked
OP, I kow you already got your GNex but when you got this error, OP, what ROM were you running? Also what kernel?
Since you are not the only one this happened to, I would like to know the above and see if it correlates to the others that this happened to in the Vibrant section. I'll post the same in their threads too.
See here for possible work-around

[Q] i9100p Bricked while recovering previous save of rom

Hi
I will try and list everything i can i suspect i will not be able to fix this but thought someone might have some insight as to how it happened.
Whats Wrong:
No signs of life, no boot screen, no recovery mode and no download mode. I have held down the reverent buttons for over a min and i get no response from the phone. Have checked its not just a flat battery, its been charging for 2 hours and same response whether plugged into charger or not.
What I was doing:
The Phone was the stock Rom that I had rooted (I use the orange signal boost app at home, and didn't want to lose it.) I decided to change the menu icons for my apps to a matching set and was using APK editor to do that. Knowing that messing with the signal boost app could mess it up I created a backup of the Rom using CWM before starting and then tried changing the icon and re-installing signal boost. It failed and the app would not run when I tried to re-install the original. So I booted into recovery mode and told CWM to recover from the backup i had created. I left the phone and when i came back it was blank and has been ever since.
Phone details
Orange Uk branded i9100p
running android 4.0.4 stock (rooted)
As I said I doubt this is an easy fix but if anyone can give me a hand i would be eternally grateful. Failing that is someone can shed some light on what went wrong so i can avoid it in the future that would be great to.
Thanks
Tom0468 said:
Hi
I will try and list everything i can i suspect i will not be able to fix this but thought someone might have some insight as to how it happened.
Whats Wrong:
No signs of life, no boot screen, no recovery mode and no download mode. I have held down the reverent buttons for over a min and i get no response from the phone. Have checked its not just a flat battery, its been charging for 2 hours and same response whether plugged into charger or not.
What I was doing:
The Phone was the stock Rom that I had rooted (I use the orange signal boost app at home, and didn't want to lose it.) I decided to change the menu icons for my apps to a matching set and was using APK editor to do that. Knowing that messing with the signal boost app could mess it up I created a backup of the Rom using CWM before starting and then tried changing the icon and re-installing signal boost. It failed and the app would not run when I tried to re-install the original. So I booted into recovery mode and told CWM to recover from the backup i had created. I left the phone and when i came back it was blank and has been ever since.
Phone details
Orange Uk branded i9100p
running android 4.0.4 stock (rooted)
As I said I doubt this is an easy fix but if anyone can give me a hand i would be eternally grateful. Failing that is someone can shed some light on what went wrong so i can avoid it in the future that would be great to.
Thanks
Click to expand...
Click to collapse
is your phone in warranty ?
also does it show any display wen u plug it on charging
also wen u put it for chargin leave it from 30 to 60 mins and check if the area near the camera is getting hot , if its gettin hot then u have hard bricked ur phone
if ur phone is in warranty u can head to service center for replacement jus don tell them what u ver actually tryin to do
or if its not in warranty then u can try getting ur phone to ur nearest jtaq center
Brickbug??
"To err is human, to forgive is divine"
Sent from my SGS II
try a USB jig.. does it work??
Listen to neo there.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from the little guy

[Q] Help, Samsung Galaxy Player 4.2 Bricked.

Okay so i have let this sit for a while now becuase i just said forget about it i will get a new one later in time. well i changed my mind. A while back i tried to root my Samsung Galaxy Player 4.2 (Model: YP-Gl1CB/XAA) And (I believe this is what happened) I didn't pay attention to what i was doing and i believe i replaced the boot-loader with a WIFI backup? I know chances are i cannot fix this and its garbage now but i would like to give it one more shot. hopefully if i didn't explain something up here the pictures will help.
Note: I used these following threads to attempt the root - http://forum.xda-developers.com/showthread.php?t=1884071 (zebluk) - http://forum.xda-developers.com/showthread.php?t=1885374&nocache=1 (alice90)
Screen-Shots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I also cannot connect it to my laptop, nor can i access download mode anymore. that is the only screen i have been able to access.
I know i didn't go into much detail. but if someone can help it would be much appreciated. also if anyone needs more detail i will be glad to add more.
EDIT: I have been able to get to the download mode main screen (press up to go into download mode or down to cancel and reboot.) but pressing up locks it up again.
FluzzyWuzzy said:
Okay so i have let this sit for a while now becuase i just said forget about it i will get a new one later in time. well i changed my mind. A while back i tried to root my Samsung Galaxy Player 4.2 (Model: YP-Gl1CB/XAA) And (I believe this is what happened) I didn't pay attention to what i was doing and i believe i replaced the boot-loader with a WIFI backup? I know chances are i cannot fix this and its garbage now but i would like to give it one more shot. hopefully if i didn't explain something up here the pictures will help.
Note: I used these following threads to attempt the root - http://forum.xda-developers.com/showthread.php?t=1884071 (zebluk) - http://forum.xda-developers.com/showthread.php?t=1885374&nocache=1 (alice90)
Screen-Shots:
I also cannot connect it to my laptop, nor can i access download mode anymore. that is the only screen i have been able to access.
I know i didn't go into much detail. but if someone can help it would be much appreciated. also if anyone needs more detail i will be glad to add more.
EDIT: I have been able to get to the download mode main screen (press up to go into download mode or down to cancel and reboot.) but pressing up locks it up again.
Click to expand...
Click to collapse
Dude you if actually did that you replaced your bootloader files the core of download/odin mode so you cannot flash any rom or kernel to fix that but i have had a similar problem on my 4.2 use this guide http://forum.xda-developers.com/showthread.php?t=2308221 from an experienced gp dev to fix mine (read through the comments) (i never replaced my bootloader files so i cannot guarantee this fix just had the error screen )but if you actually replaced your bootloader files you may have a hard bricked player try a usb jig it may not do much but you never know
niklus101 said:
Dude you if actually did that you replaced your bootloader files the core of download/odin mode so you cannot flash any rom or kernel to fix that but i have had a similar problem on my 4.2 use this guide http://forum.xda-developers.com/showthread.php?t=2308221 from an experienced gp dev to fix mine (read through the comments) (i never replaced my bootloader files so i cannot guarantee this fix just had the error screen )but if you actually replaced your bootloader files you may have a hard bricked player try a usb jig it may not do much but you never know
Click to expand...
Click to collapse
Actually i fixed it o-o sorry i did not update the post or anything. i couldn't find it but yeah. its fixed the only "lol" part about it, is that it has a Samsung galaxy s2 load screen thing? i think but works 100% now
FluzzyWuzzy said:
Actually i fixed it o-o sorry i did not update the post or anything. i couldn't find it but yeah. its fixed the only "lol" part about it, is that it has a Samsung galaxy s2 load screen thing? i think but works 100% now
Click to expand...
Click to collapse
Oh......Okay good for you :good:

Bootloop?

Hi,
I have a big problem.
My brother tried to root my Xtrons Px6 rk3399 gs. with Su user. He updated superuser. Now the radio is in the boot loop and it won't start. He then tried a new firmware to bottles which does not work either, the radio only shows the logo. I get into recovery. I just do not know how to go on:-(
it's the Xtrons PQ80UNV
Sorry for my english.
Greez
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TF? Why would you want to root that?
Did you try factory resetting?
He said it would be better. then you have more options. Because of some sound patch, I don't know much about it. Factory reset? I pressed Restet button but no change. It doesn't just start the boot logo from Vw.
I don't even get to the Adroid. Only in recovery.
Did a wipe, but it still doesn't start.
You chose wipe cache partition. I meant "Wipe data/factory reset"
Try choosing it.
If your brother is the one who did this as you say, if it's me I'd force him to fix it or at least pay for it.
I tried that too. I also tried the original firmware here, but always the same.
Yandex
Finds everything
yadi.sk
Yes, that's right, he's currently doing assembly work. I'm really desperate :-(
What I noticed is that with every firmware I install it is always the same recovery version.
voxdie said:
What I noticed is that with every firmware I install it is always the same recovery version.
Click to expand...
Click to collapse
Can I ask how did you root it?
Unfortunately, I don't know. I only know that an rk3399 mcu was previously a gs version
voxdie said:
Unfortunately, I don't know. I only know that an rk3399 mcu was previously a gs version
Click to expand...
Click to collapse
I don't believe you can root a device and suddenly you forget about it...
Do you have unlocked bootloader? You may need to flash the stock ROM if you can find it.
It works again, I have now flashed the img instead of the ota. Now it works again. Great. Thank you so much for your help
voxdie said:
It works again, I have now flashed the img instead of the ota. Now it works again. Great. Thank you so much for your help
Click to expand...
Click to collapse
I don't think I did anything but happy to see everything work out fine.
Make sure your brother doesn't do something like that again.
NO, he can't get to this radio anymore .. thanks again
the UNIT you have, looks almost the same as ICE/HU/PBX89UNV ( except mine has android 9 ) XTRONS ? 64GB -4GB ?
correction- there are multiple versions of this exact same unit. (even one with a qualcomn)
yours has the HDMI out pigtail ?
firmware link -
word instruction -
codes to ENABLE DEVELOPER OPTIONS
To start debugging, enter adbon in the factory settings input password box
if you want to change the factory settings, boot image, etc,, enter 126 in the factory settings input password box.
may i ask fellow members , to root this ,
unlock boot-loader,
flash updated BOOT.img (magisk patched)
-- because this is android 9, do i need a BLANK VBMETA flash?
funny fact--- this unit, will BOOTLOOP if you put a 512GB micro SD card in the slot, it boot loop cycles..
(anything above 128GB causes issues )
the micro SD slot for MAP/GPS , --- can we use this for anything else ?
and does anyone know of there are any custom roms and or TWRP already built for this > (this should share similar/same across a few brands ?)

Question Redmi 10 128GB

Hello,
i got my mom new phone. After initial configuration + update to latest stock miui, this problem started to show at random. You can hear that touch is working when screen i garbled. I think this is software issue but any suggestions will help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
hitmanbg said:
Hello,
i got my mom new phone. After initial configuration + update to latest stock miui, this problem started to show at random. You can hear that touch is working when screen i garbled. I think this is software issue but any suggestions will help.
Click to expand...
Click to collapse
Try restart if it is not working then press power button and volume up button for until Redmi logo appears then reset it through mi recovery
@durga5151 I did factory reset yesterday but the phone still doing this.
Ok, thanks i will try this
If you have warranty ask for replacement.
Is the recovery screen working properly? If not, it's a hardware error.
Hello,
yes fastboot and recovery boot screens work and operate perfectly fine.
Also sometimes it fixes itself after lock/unlock again.
In that case, you need to completely clean your phone and reinstall the system. MiFlash20181115 + the corresponding latest Miui ROM (fastboot = *.tgz). "Clear all" mode.
Yep, gonna do that, i'm waiting my bootloader to unlock and i'm thinking flashing the phone with Pixel Exp. to see if the problem will occur, if not i will reflash with stock rom.
Ty for you help
Did the reflash "Clear all" all was working until i configured face recognition, then problem reoccurred. I think there is
HW problem, maybe with front facing camera.
Bought this phone a week ago and this same thing occurs once in a day and to fix it i just turn the screen off and on and it goes away, judging from this scenario do you guys think if it's a hardware issue? Or it might be a software bug?... Thanks in advance!
Hassanmad said:
Bought this phone a week ago and this same thing occurs once in a day and to fix it i just turn the screen off and on and it goes away, judging from this scenario do you guys think if it's a hardware issue? Or it might be a software bug?... Thanks in advance!
Click to expand...
Click to collapse
first try with reset your phone, if not solved, then flash rom with miflash tool with "clean all" option, if still the problem occuring then, u should go to the service center.
aamnahid said:
first try with reset your phone, if not solved, then flash rom with miflash tool with "clean all" option, if still the problem occuring then, u should go to the service center.
Click to expand...
Click to collapse
I'll try that, thanks!
Two weeks later still no such problem, after i disabled face recognition. Working with fingerprint, no problems.
Ohh, I'm not using the face recognition lock and still getting this once a day, all I'm worried about is if it'll get worse in the future or not.
hitmanbg said:
Two weeks later still no such problem, after i disabled face recognition. Working with fingerprint, no problems.
Click to expand...
Click to collapse
No idea but i did "Clear all" reflash
hitmanbg said:
No idea but i did "Clear all" reflash
Click to expand...
Click to collapse
So if you did clear all reflash and it's not giving this issue anymore that could mean it's probably a software bug
Ps. When it was happening I tried squeezing on the screen with fingers to make it go away as if the screen would properly connect with the connecters but it just stays static and what helps it go away is just putting it in lockscreen and out with the power button.
hitmanbg said:
No idea but i did "Clear all" reflash
Click to expand...
Click to collapse
So it happened again just now making it twice today and i decided i wanna reflash the phone,
Did you flash the stock rom file again or did something else? Just let me know what rom should i flash,

Categories

Resources