Related
Is there a file I can edit or remove to disable trackball functionality entirely?
The trackball has the bug where it perpetually scrolls to the left. Just curious what I can do to work around the problem.
Many thanks in advance
Sent from my ADR6200 ERIS using XDA App
Ah yes, I remember this problem. Not a fun experience at all.
The only luck I had was sending in my Eris to Verizon and getting another one. I'm pretty sure you can't do that anymore though, and they'll send you a D1 instead, if they even do that anymore.
Cleaning the trackball might work, since it could be just a piece of dirt causing problems. If you're as unlucky as I was though, its a hardware flaw that can't be (easily) fixed.
Yeah, its a common issue. However that would be an interesting fix lol i know there is another version of the recovery you can use that does not require the trackball, use that to unroot if it dies completely so you can return to Verizon.
Sent from my ADR6350 using XDA App
I have the same problem too, but i cant send to verizon because i am in canada for family and two days from now i will be in saudi arabia...so i cant really send it to verizon. I use my phone daily and it roams perfectly. I have 2.3 SENSE on my phone. Back when I had recieve teh bug, it was going on and on and on. After sometime, and also after some flashing new roms, the bug is not as "powerful" as it was before. Now it only does it when i charge it. I remember there was an app in the market that actually stopped the trackball but it only worked for a min. and then the app stops working. I hope this gives you a bit help!
Search under the Stickys here under Eris and it will point you to the link to download & flash the Recovery Rom - where use of trackball is optional, especially if do you boot into doing NAND backup/recovery or flash ROMs, etc.
Cleaning the trackball by pressing down hard & rubbing on a hard surface over a white printer/copier paper sometimes worked wonder (at least for a while - to me.) Stickys for earlier posts (plus look into YouTube for a demo) ....
I got my Eris via eBay and it's been out of warranty and the ultimate solution was to spend $2.50 (including shipping from USPS) to get a Blackberry (8300, etc.) trackball replacement & did a simple transplant or replacement - available in many colors (I got a black one, least expensive, to replace the transparent/clear one on the phone) - and less than 10 minutes of labor to get it changed, as good as brand new. Just need to use a jeweler's screwdriver (it's a torx/hex style micro screws x 4 plus 2 on the circuit board) to open the case with the cover removed, take out 4 screws & then pry carefully around the edge/rim to avoid scratching to pop it open enough, then taking out the 2 crews to get to the trackball. A slight push or nudge, it will pop out - note the direction of the contacts before putting your new one in - reverse the disassembly sequence. Power up once everything is tighten back together & you are good to go - watching that black/blue/red/orange colored trackball dance & light up.
It was a fun project for me & feeling of accomplishments, giving new life to the aging Eris coupled with one's choice of Froyo or GB Rom's.
Actually, I've had the problem for a while now. I've tested many rom's and it really depends on the rom. Funny isn't. I had come up infrequently in GSB. MacRom it didn't it a little but wasn't crazy. What i do to fix it is press down hard and that seems to fix it. I'm running Gin-Sense Tazz and haven't noticed it yet, but i've just flashed the rom.
I've heard of people fixing it by laying the phone down face first and rolling it around with pressure to reseat it. I'm not saying to, it might make the problem worse. But its a thought
Sent from my ADR6200 ERIS using XDA App
Thanks for the suggestions!
Sent from my ADR6200 ERIS using XDA App
I've replaced the trackball on a phone with this problem, still having occasional issues... The trackball replacement didn't fix it entirely. What to do next?
From what I understand of the trackball problem is that it is a grounding issue with the contacts and the charging/usb port. Mine is doing it also so when it breaks I will take it apart and find out for sure:}
I finally broke the annoying sucker and flashed a recovery that uses the call and end buttons instead of the trackball. I'm not having any issues.
sjpritch25 said:
I finally broke the annoying sucker and flashed a recovery that uses the call and end buttons instead of the trackball. I'm not having any issues.
Click to expand...
Click to collapse
Love seeing another satisfied customer .
Cheers!
Yep. I've been frustrated for so long that I was glad to finally fix it
Sent from my ADR6200 using XDA App
sjpritch25 said:
I finally broke the annoying sucker and flashed a recovery that uses the call and end buttons instead of the trackball. I'm not having any issues.
Click to expand...
Click to collapse
did that recovery also disable the trackball within the ROM? Or just in recovery? can you post a link to it? Thanks!
haganme said:
did that recovery also disable the trackball within the ROM? Or just in recovery? can you post a link to it? Thanks!
Click to expand...
Click to collapse
No, the custom recovery is mutually exclusive of the ROM. Sorry, my tweaked version of Amon_RA's custom recovery can't touch the ROM that's installed...
Here's a link to the XDA post where for my tweaked version of the trackball-optional custom recovery for the Eris:
http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
And here is the sister thread over on AndroidForums that has some installation options for you:
http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html
Good luck and cheers!
After, I broke the trackball. All the trackball issues left and i needed a way to use the recovery. The recovery without trackball works great.
I also had a bad trackball, now using my wifes old eris since she upgrade to an inc2.
Please don't try anything mentioned below, if you are not familiar with flashing roms and programming ! You've been warned !
The following steps had been done in 4 sets of Galaxy Tab 10.1 (from different sources), all touchscreens become unresponsive within a minute. The system is still running, volumn keys are working, orientation sensor is operational, even the clock and wifi signal is fine. The only problem is the touchscreen. All 4 devices are not rooted, brand new, fully charged, and now returned to Samsung for inspection.
WARNING !!! The following steps may cause you trouble ! I share these steps only because I think some experts here may be able to solve it ! I'm also looking for some proof, if the same problem occurs to Samsung Tab 10.1 devices in different countries.
The steps to trigger an unresponsive touchscreen :
(1). Download and install any file manager from the Market (skip if you already have).
(2). Browse to "/sys/devices/virtual/sec/sec_touch/".
(3). Select all files (excluding folders).
(4). Copy and paste to any other location that have write permission (such as sdcard). Some of the files are not allowed to be copied, so just skip it.
And then, in a short while, the touchscreen will not respond anymore.
The files mentioned in step 2, are some driver files of Atmel mxt1386 (the touchscreen hardware). It seems that users of Acer Iconia also have touchscreen issue, turned out to be using the same hardware.
I know that there are also many users that do not have any touchscreen problem. This may only because those files are not accidentally accessed yet. I'd rather hope that you have a different version of the hardware driver that does not have such problem.
I'd like to ask for help from experts and developers here. But please don't try it if you are not absolutely confident to at least restore the system. Please don't blame me if your Tab becomes un-usable.
For those who are willing to try (at your own risk), I'm much appreciated. And I'd like to say thank you to all of you. Your effort may be helping a lots of users who have this problem.
Hey idsam,
have you got any ideas how to fix touchscreen broken this way?
Im sorry, I dont get this.
To me its like saying "I removed my battery and now my device won't turn on"
So, if I dont mess around with my system files and touch screen drivers, then my touch screen will be fine?
If you mean something else, please explain
Yeah, you got wrong.
Topic starter made too complicated example. The simple description is: if you try to read files from /sys/devices/virtual/sec/sec_touch/ directory - you'll got broken touchscreen. Looks like this operation damages touchscreen firmware, though this won't happen with properly configured/written (by manufacturer) system.
So who wants to read from those files? Any software for any reason. E.g. a lot of users have bricked their devices by doing a full system scan with Dr.Web for Android antivirus.
Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
idsam said:
Sorry for the complicated example. I just tried to provide as much information as I could.
Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device.
Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all.
Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?
What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
Click to expand...
Click to collapse
When the touchscreen goes unresponsive, do other parts of the device still function? For example, when you hold down the power button, will the shutdown menu appear? When you rotate the device will the orientation change?
I have had an unresponsive touchscreen many many times. I'm not sure it is the same unresponsive touchscreen you talk about here. When mine goes unresponsive I can still use the power button and if I rotate the screen a few times it eventually becomes responsive again.
Yes. The power and volume up/down buttons work, orientation sensor also works as a normal device. I tried to rotate the screen, discharge and recharge the battery, but it aside for hours and tried again, nothing helps.
And it is actually confirmed by Samsung that hardware replacement is needed. They said that they tried to recover the device by flashing rom, but failed.
so I have the same problem. Quite frustrating. Not only that, I've noticed that there is a vertical 1-2 inch area from top to bottom of the screen that doesn't ever respond to touch.
I'm sending it to Samsung
Hi Idsam, I'm from Russia and have a same problem. After full scan by Dr. Web the touchscreen not responding and now I don't know what to do, beacause I've bought my Samsung in USA in Bestbuy, but now I'm at home in Russia, no warranty, no service, nothing. May be somebody can give me advise?
To be honest, it seems that Samsung doesn't have a solution yet. And probably worse, Samsung did not modify the driver at all, which means Atmel is responsible to fix the problem. No matter what, you can wait, but who knows how long it takes.
I think Best Buy has refund policy. You should discuss with them asap, as this kind of policy is normally time limited. You may consider to pay for delivery, in order to minimize your lost. If they refuse to refund for you, then you may need to contact Samsung Russia. I'm sure they know about this issue, and perhaps you may discuss with them. Still, you may need to consider to pay a little more as repair service charge.
BUT, I'm not saying you should pay more for what they've done wrong. It is only a suggestion, in order to speed up the process and at least minimize your lost.
The last option, I think, is to wait until Samsung announce a solution. If the method to fix it doesn't require hardware exchange, perhaps you may get information from Samsung and try to solve it by yourself.
As I know, when the touchscreen issue occurred, the Android system is actually still running WITHOUT problem. It means that you may still control the device by using ADB via USB. So, if Samsung can provide a patch, it may be easily fixed. I'm not sure if it is possible or not, just hope it will be as simple as that.
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
---------- Post added at 07:28 AM ---------- Previous post was at 07:23 AM ----------
oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
No, it doesn't help. Only one method left - use the hammer.
oawalker said:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
Click to expand...
Click to collapse
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
AlexNovoross said:
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?
Click to expand...
Click to collapse
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
idsam said:
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this.
I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
Click to expand...
Click to collapse
I hope Samsung can patch this up when they update to 3.2 if that update comes
Does this mean i Lost my Tap if that patch did't come out..
!!!???
Honestly, only Samsung can answer your question. But my steps can help you to show proof to them that it is a design flaw, and force them to admit that it is their responsibility to provide solution.
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
I have the same problem with my Galaxy Tab P1010. I can get into download and recovery mode i can move the selection using the volume button but i can't press the power to enter my selected option. I have already tried re-installing the latest available firmware for my device using ODIN 1.7. Eventually everything seems to be ok until i reach the point where you select the language. I can't select any option mainly because the touchscreen is unresponsive. All along i thought this problem is only software? Hopefully somebody can find the solution to this.
sp3dev said:
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.
You can read more in http://forum.xda-developers.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
Click to expand...
Click to collapse
It seems that the second link is invalid. Besides, it is necessary to root the device and flash CWM recovery first, right ?
I mean, it may be a bit risky. I read your post before, but not sure if it is the same issue. If it is not, and the device is rooted, the official warranty may be voided too.
I have updated the links but the recovery image is only valid for the Iconia tablet. I mean, one could try using the attached driver sources and add them to the kernel but that will require at least flashing custom kernel. Samsung seems to be releasing a firmware update to fix this issues but people familiar with linux kernel development may try experimenting with the driver from acer.
Please bare with me.
This is the second time this particular problem has happened to my device.
So I was on the tram coming back from my maths exam today.
(Running a ROM with Hardcore's SpeedMod K2-15)
I decide to change the song, all of a sudden, my screen turns black and I can't turn my phone back on. I as soon as it happened I thought uh oh. (the battery was at 74%.
So I tried to reboot my phone, didn't work.
Tried to get into download mode, didn't work.
Tried to get into recovery mode, didn't work.
Went to see if anything happened if I put in my charger AND USB cable. Both instances nothing happened.
When the incident happened last time, I was about to have it shipped to Samsung, was in the car on the way there and I was still pressing the power button in hope that it would work. Low and behold, it turned on, I flashed a different ROM and kernel and was on my merry way until today.
After browsing Q&A for around an hour the only other instances I've found with this problem are my original thread (around a month ago) when the same problem occurred.
http://forum.xda-developers.com/showthread.php?t=1302645
And another one I found today whilst browsing.
http://forum.xda-developers.com/showthread.php?t=1289063
also here
http://forum.xda-developers.com/showthread.php?p=18139062
So up to my knowledge this seems like a problem that isn't only a one off if I'm not the only one reporting it.
Is there anything I can possibly do to fix my phone or something to avoid doing so others don't run into the same unfortunate set of circumstances?
PS. two days ago I deleted a few folders on my USB storage as they were taking up too much storage space. I doubt they had anything to do with the problem though and that's the only difference I can think of that MAY have trigged the event. But I have no reason as to why it happened. I am also using NoMoarPowah and Chainfires3D mod (which I've been using for ages and i'm sure had nothing at all to do with the problem)
hopefully someone knows of a definite solution. :\
Wow the same thing is happening to my phone as well. Thanks for the detailed description. Hopefully we'll find a response soon. Also, I would suggest you investigate the volume of chode in the nearby vicinity of your phone, may be a problem (personal experience)
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
pokergirl said:
You spelt bare wrong
Click to expand...
Click to collapse
I've made similar mistakes in life. You don't want to mix them up at the wrong time. *Shows bear scars*
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
ALSO Don't dinosaur with it, nor allow for sluts to touch it xoxoxoxoxoxoxoxoxox bb <3
pokergirl said:
last edited by pokergirl; today at 01:04 pm. Reason: I did it wrong!
Click to expand...
Click to collapse
you're doing it wrong!
Too late for the sluts, they're all over it! x0x0x0x0x0x
H3h3
H3h3h3h3h3h3h3h3h3 its ****ed darl <3 xxxxxx
Leopardkitty69 stop degrading urself g1rL g3t urs31f @ [email protected] xo
- A girl who knows how to control balls
leopardkitty69 said:
I just dropped mine off a stepladder in kfc, and i'm experiencing the same problem. Avoid doing this. Hopefully someone else has a better solution to your problem but for now, just don't drop it off any stepladders.
x0x0 leopardkitty69
Click to expand...
Click to collapse
I dropped it quite hard and it caused corruption on /efs partition.
lol'd
This thread has suddenly become a lot more interesting.
pokergirl said:
Through implementing my CAS 89 values and inserting chode = 2x length into my TVM solver i introduced the viagra into my phonem therefore, bringing its pwoer to 9001 and causing for it to groan in pleasure. Through utilising square volume = 2 * x * l with x = your vaginas length and y = The radius of your arsehole i solved this problem. (Personal experience, for more information visit (it made me delete the link))
P.s chodemaster - Your personal experience is obviously limited and incredibly detrimental to the phone. When YOU have caught all 151 original chodes you should post in this forum in a SERIOUS and well rounded individual manner
P.P.S NEED MOAR PYLONS
P.P.P.S THIS IS YOUR BIRTHDAY CARD FOR NEXT YEAR
Click to expand...
Click to collapse
Sigh I really need a solution. Not thread spam >.<
This sounds like a serious issue with your phone's hardware. You should return it to Samsung.
with the phones hardware itself?
If they manage to fix it do you think the'll notice it's been rooted?
I've removed the triangle and reset the flash count i've just got a new ROM on it.
(as in will it still be under warranty)
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Freakgs said:
If you manage to reset the counter and get the original stock rom on it (or a new version which was meant for your device and came by kies) you should be perfectly fine, just don't root it again (until you get it back, that is).
Click to expand...
Click to collapse
but it currently won't turn on at all ;|
giga502 said:
but it currently won't turn on at all ;|
Click to expand...
Click to collapse
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Freakgs said:
In that case chances are very high that Samsung will simply replace it, given that they probably won't be able to turn it on, too.
That's what I've heard from many people atleast, who had issues turning their devices on.
Only way to find out: see if you can get warranty.
Other option: be honest that you rooted and hope for the best, yet I don't know how Samsung staff would react to that, probably not too good.
Ps:
I take it that you have a JIG and tried that one already? As you stated, that you did reset the counter.
Click to expand...
Click to collapse
I've given it to a friend but I highly doubt it would work. Anyway for now, I'm going to place it in rice JUST IN CASE there is a tiny bit of moisture on some part of the motherboard which is messing things up. If that dosn't work i'm going to go down to my mobile dealer and hope for the best
thanks for your help!
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
ante0 said:
One question: Did you pull the battery, and put it back in?
I have had this sometimes before, it seems to be caused of overheating... But I'm not 100%. I have checked Logcat but nothing in there of interest.
Click to expand...
Click to collapse
no I havn't done that. I'm taking it back later today
So I don't know ****. Yeah I said it, don't run away though. I'm still reading tons of information on the forum and you guys are awesome and I can't believe I never did this sooner!
I really wish I could have started from a stock phone but that was a great deal to me, and this is how things are.
The situation:
I bought a MINT Atrix 4 for $125. Great. Well the phone already has what the guy called "Jelly bean" installed which is cm10 if I understand correctly (the phone wont be activated till next week).
The problem:
He said "DO NOT try to record a video. The camera works, just not the video recorder. He also says WiFi doesn't work and DO NOT touch that either. Now that's a problem.
Phone specs:
Android version 4.1.1
baseband version N_01.77.37p
kernal 2.3.32.59-mb860-cm9-g89b8854
cm mod version 10-20120729-UNOFFICIAL-olympus
yada yada
If any specific threads can help besides the Nooby and FAQ threads I would appreciate that as well. The more information the more comfortable I will be with the phone.
I wouldn't call a broken phone mint. If wifi doesn't work, its likely that bluetooth doesn't either and if that's the case, you got screwed as the only way to repair it is to send to motorola. Which since you're not the original owner means you have to pay for the repair. I'd return it if he didn't disclose the broken wifi. Good luck
Try flashing a new radio and rom
Sent from my undervolted, underclocked, power saving Motorola Atrix.
pre4speed said:
I wouldn't call a broken phone mint. If wifi doesn't work, its likely that bluetooth doesn't either and if that's the case, you got screwed as the only way to repair it is to send to motorola. Which since you're not the original owner means you have to pay for the repair. I'd return it if he didn't disclose the broken wifi. Good luck
Click to expand...
Click to collapse
It wasn't an eBay purchase so returning it isn't an option. Besides, I never said bluetooth doesn't work. From what I read, when both are not working its hardware and software if only one (most of the time).
Regardless, thank you for your worthless opinion and lack of help.
zhillz said:
It wasn't an eBay purchase so returning it isn't an option. Besides, I never said bluetooth doesn't work. From what I read, when both are not working its hardware and software if only one (most of the time).
Regardless, thank you for your worthless opinion and lack of help.
Click to expand...
Click to collapse
You're right you didn't say bluetooth wasn't working. Its just a known error around the forums. Really no need to snap at me or get defensive. I was not in any way belittling you so I dont appreciate your attitude from a self proclaimed NOOB. That being said, I'm over it and I agree with the other post saying to try another rom. Is it joker or epinter cm10 that its on? (Those right now are the active developers of cm10 for the atrix) If its either of those, read thru their developer posts and see if wifi not working is a known issue.
Your initial post definitely came off as rude. I think I have an idea on what to do but I'm going to do a little more research before I dive in. Thanks for real this time.
So I have tried downloading different cm10 files, a cm9 file, and gapps. When I'm in my recovery and try to install from the sd card, they wont load
(bad)
Installation aborted.
What should I try now guys? Am I damaging the files? I downloaded from jokersax's site (firefox)>open containing folder and drag to F: (I tried E: but I guess that's the phones internal?)
zhillz said:
So I have tried downloading different cm10 files, a cm9 file, and gapps. When I'm in my recovery and try to install from the sd card, they wont load
(bad)
Installation aborted.
What should I try now guys? Am I damaging the files? I downloaded from jokersax's site (firefox)>open containing folder and drag to F: (I tried E: but I guess that's the phones internal?)
Click to expand...
Click to collapse
Put the file in the root of the phone's internal storage.
Sent from my undervolted, underclocked, power saving Motorola Atrix.
Really need to start recovering the phone not throwing roms at it till its fixed. Atrix is an odd ball when you get tied up in partitions and file locations. My suggestion would be to checkout fruitcake and start from there . There are more risky ways of getting out of that rut by try the easy stuff first. Phone needs a clean start and all new files. Cm10 has some issues depending on the logic board revision you have. Before you ask the only way to tell is to physically compare one logic board to another and there are very subtle difference. I only stumbled across this by accident during some full tear downs . I usually judge by symptom then treat them accordingly .
Like I stated above fruitcake is my recommend and I have used it numerous times with trouble phones that need a clean start.
Sent from my MB860 using xda premium
So I sent my Atrix for repair as I couldn't stand the random reboots. It came back unfixed. I sent it again, this time warning Motorola that I wouldn't be ok with it coming back unfixed again and so it got back finally fixed.
However, the phone doesn't recognize the multimedia dock anymore ! Media center through HDMI works fine but not the dock : the phone doesn't charge nor does the audio work through the speaks I plug the dock to.
Do you think this is a software issue or an hardware one, something they messed up while repairing it.
If I have to send it one more time, I'll go nuts...
Thanks !
DannyBiker said:
So I sent my Atrix for repair as I couldn't stand the random reboots. It came back unfixed. I sent it again, this time warning Motorola that I wouldn't be ok with it coming back unfixed again and so it got back finally fixed.
However, the phone doesn't recognize the multimedia dock anymore ! Media center through HDMI works fine but not the dock : the phone doesn't charge nor does the audio work through the speaks I plug the dock to.
Do you think this is a software issue or an hardware one, something they messed up while repairing it.
If I have to send it one more time, I'll go nuts...
Thanks !
Click to expand...
Click to collapse
I'd guess that those things worked when it left, but not when it came back, that it would be a hardware issue if the software was unchanged. Just a thought though, do you have any mods installed or are you running a pure stock ROM?
Maybe they've noticed CM7 is better than their stock and they flashed CM7. :highfive:
lehjr said:
I'd guess that those things worked when it left, but not when it came back, that it would be a hardware issue if the software was unchanged. Just a thought though, do you have any mods installed or are you running a pure stock ROM?
Click to expand...
Click to collapse
Pure stock. And yes, it was working before it left for repair...
DannyBiker said:
Pure stock. And yes, it was working before it left for repair...
Click to expand...
Click to collapse
In that case I would say it's very likely that they broke something else. Their Facebook staff may be able to put you in touch with someone who can help as well as they seem to have access to people that the CSR's don't, or they may just delete your post. Motorola's Facebook did have a large number of complaints regarding issues with repairs a couple months ago, but they suddenly disappeared, most likely due to trying to do damage control (reputation management). There's also their forums, where the discussion of anything other than stock functionality is pretty much taboo. But yes, if it worked before, it should work now.
lehjr said:
In that case I would say it's very likely that they broke something else. Their Facebook staff may be able to put you in touch with someone who can help as well as they seem to have access to people that the CSR's don't, or they may just delete your post. Motorola's Facebook did have a large number of complaints regarding issues with repairs a couple months ago, but they suddenly disappeared, most likely due to trying to do damage control (reputation management). There's also their forums, where the discussion of anything other than stock functionality is pretty much taboo. But yes, if it worked before, it should work now.
Click to expand...
Click to collapse
Was it sent in on warranty or did you pay to have it fixed. Either way I feel for you because I know I sent my 2 atrixes in total of 3 times and even though they were fixed/replaced under warranty I still paid about $45 shipping in the end. Everyone on atrix forums keeps praising motorola build quality but I have failed to see it in mine or my wife's atrixes.
affiatic said:
Was it sent in on warranty or did you pay to have it fixed. Either way I feel for you because I know I sent my 2 atrixes in total of 3 times and even though they were fixed/replaced under warranty I still paid about $45 shipping in the end. Everyone on atrix forums keeps praising motorola build quality but I have failed to see it in mine or my wife's atrixes.
Click to expand...
Click to collapse
I think we're starting to see quite a few cases of storage related failures. I am a bit perplexed as what some consider to be qualifying characteristics of "build quality" myself.
lehjr said:
I think we're starting to see quite a few cases of storage related failures. I am a bit perplexed as what some consider to be qualifying characteristics of "build quality" myself.
Click to expand...
Click to collapse
I myself see having to send them in on hardware issues within the 1st year as poor build quality. A new replacement they sent me froze on GPS then would not boot past moto screen as if it bricked itself. Was replaced with another new one after another 15$ I paid for shipping
I think some think USA company means quality. My new atrixes shipped from Mexico
Yeah, I'll have to pay to send it back again as well...
Do you think it's worth trying to flash a custom rom to see if it "fixes" it ?
Thanks.
DannyBiker said:
Yeah, I'll have to pay to send it back again as well...
Do you think it's worth trying to flash a custom rom to see if it "fixes" it ?
Thanks.
Click to expand...
Click to collapse
No, because it's likely that they would use that in order to blame you for whatever is wrong with the device. If it's a hardware issue, no amount of third party software is going to fix it. I would however try to get in contact higher up in the chain of command regarding the issue. It's one thing to ship a device with a defect, it's another thing to have to ship the same device back and forth continuously to get it fixed. And the sad part is that this is just one of many similar stories regarding repairs. I guess that "New Motorola" just isn't quite so new after all.
lehjr said:
No, because it's likely that they would use that in order to blame you for whatever is wrong with the device. If it's a hardware issue, no amount of third party software is going to fix it. I would however try to get in contact higher up in the chain of command regarding the issue. It's one thing to ship a device with a defect, it's another thing to have to ship the same device back and forth continuously to get it fixed. And the sad part is that this is just one of many similar stories regarding repairs. I guess that "New Motorola" just isn't quite so new after all.
Click to expand...
Click to collapse
I would do a factory reset in recovery. My wife's came back with same issues it was sent in with. They replaced the screen for her. The proximity sensor still wasn't working right someone recommended factory reset from recovery. It fixed it for her. Before that I knew nothing about stock recovery
affiatic said:
I would do a factory reset in recovery. My wife's came back with same issues it was sent in with. They replaced the screen for her. The proximity sensor still wasn't working right someone recommended factory reset from recovery. It fixed it for her. Before that I knew nothing about stock recovery
Click to expand...
Click to collapse
Hmmm, I was assuming that was already done
lehjr said:
Hmmm, I was assuming that was already done
Click to expand...
Click to collapse
Yes but sometimes people don't realize there is more than one way to do a factory reset on stock. Until about a year ago I thought you could only do this through settings. Recovery is the best way I now know
A good tutorial for that ?
'Cause that's what I meant when I asked if flashing a custom ROM would help : can it be something that isn't properly setup at a software level ? I tried flashing the stcok rom again with RSDLite but it didn't delete any data so I'm not sure it really reset anything.
Thanks !
DannyBiker said:
A good tutorial for that ?
'Cause that's what I meant when I asked if flashing a custom ROM would help : can it be something that isn't properly setup at a software level ? I tried flashing the stcok rom again with RSDLite but it didn't delete any data so I'm not sure it really reset anything.
Thanks !
Click to expand...
Click to collapse
You mean a guide to factory reset the device in recovery? I thought that was in the manual, but it isn't, although I did find it here.
So I did a factory reset from Recovery, which worked as all was wiped. However, still no luck with the dock.
The reason I asked if trying to install a custom rom was a good idea is because I'm wondering if flashing another Webtop version or the HDMI-hack could make it work. To be clear : do you think that the fact that the Factory Reset didn't work establishes that it's hardware issue ?
DannyBiker said:
However, the phone doesn't recognize the multimedia dock anymore ! Media center through HDMI works fine but not the dock : the phone doesn't charge nor does the audio work through the speaks I plug the dock to
Click to expand...
Click to collapse
As you're able to attach the HDMI and this works are you sure it's not the dock that's faulty? Had a quick look around and came across this... http://www.atrixforums.com/forum/mo...my-hd-multimedia-dock-useless-without-tv.html also, have you tried to clean ect connectors/ports. Might be worth a try
I should try again but I have two docks and the other one doesn't work either. However, I do feel that the AC connector doesn't feel really stable when inside the dock..it just moves around. I'd have to try with the the other's dock AC cable but it's an UK one and I need an adapter.
The thing is that the dock wasn't touched while the phone was under repair so I don't see how it can break just like that.
As I stated before, connection through HDMI to a TV-set works fine as well as charging with the power cord.
EDIT : saw the link you shared and it feels like the exact same issue indeed !
Well, it's fixed...kinda.
I unlocked it and flashed the "fixed webtop addon" from CSROM. It still wasn't working but with it, I got that the message saying that the device was not in charge anymore when I disconnected from the dock, which it didn't before; it wasn't charging however.
I don't think that was relevant but then I decided to give a look at the dock again and removed the top of it and...tadaaa, it worked ! From what I understand, the dock's connectors were not entering the the phone's inputs enough. I still think it's because they ****ed up during repair but heck, I won't send it back for that...
Good to hear you got it working