Database Users

TOUCH HD keeps turning itself off

Hi Guys, i have a strange Problem since a couple of days.
The touch HD turns itself off after some minutes. I have to take out the battery and put it back in, otherwise it will not turn on...
i have:
- deactivated automatic shut down in power settings
- deactivated today timeout
- tried hardreset
- tried another rom (currently dutties final)
no success :-(
i have absolutlely no clue what could cause this and how i can fix it...
help is highly appreciated.

hello there , actually maby its a virus or there is problem in SPL
Try to install again the SPL modified and tell me
best regards
ms4cah

unlikely it has anything to do with SPL. it was fine for months, i had not flashed or installed anything.
it seams dead now by the way. i cannot turn it on again.
i also tried a new battery. it doesnt even charge, no light at the power button. nothing.

Surrido said:
unlikely it has anything to do with SPL. it was fine for months, i had not flashed or installed anything.
it seams dead now by the way. i cannot turn it on again.
i also tried a new battery. it doesnt even charge, no light at the power button. nothing.
Click to expand...
Click to collapse
Sounds like a warranty claim

I am getting the same problem!! is there anything i can do to fix this? anyone figured out the reason?

I had this sort of problem.
The HD would hang, then switch off, then to get back on I had to remove the battery for a while. Sometimes it worked after a minute, other times I had to leave the battery disconnected for longer.
So I performed a hard reset and it switched itself off during boot (after successfully resetting).
Battery out for a while.
H/R once more. Again crashed during boot but not at the same point as previous.
Tried a different battery with a full charge - same result.
Tried to re-flash a "very popular" custom ROM with USPL. Got to 1% and error. This was because the HD had crashed..
Tried to flash the official HTC ROM and it got to 15% and error. HD crash.
So I have contacted HTC and they are sending a courier to collect it so they can take a look with a view to repairing it.
The last ROM I successfully loaded about 2 weeks prior to the start of my problems was a custom win mo 6.5 rom. As I couldn’t get it to a stable state - I couldn’t flash the official HTC ROM.
I’ve convinced myself it’s a hardware fault rather than any software damage..
Although I fear I’ll be in for some bad news.

mine too
Hi,
I have the same problem.
Mine was doing hard reset and after a day or two the same problem.
Now I cannot turn it on.
I will send it to htc...
Crossing my fingers.

I had the same problem with mine...
While turned on, it automaticly tryed to turn of, as if something was pressing the on/off buttom. Everytime that message for turning it off poped up and I just couldn't control the on/off button anymore.
I tryed everything and nothing worked. It really seemed a hardware and warranty claim issue. However, since I bought it abroad and it does not have warranty here in Brazil, I just decided to sell it (obviously warning the buyer about the issue) and to buy another one (which is working as a charm).
It is a hardware issue, for sure...

So my HD has been away at HTC for nearly a week, and im currently tracking its return journey, due to land back here at some point this morning.
I have had no contact from HTC so its going to be a suprise as to whether anything has been repaired.
My hope was they couldn't turn it on at all - thus replacing the bits n bobs inside, replacing the main board containing my 6.5 ROM.
So for now im hoping "no news will be good news", but I will update this when I have it back.

... I've the same problem...
Hi, I've the same problem. Do you have any solutions?

Nasher79 said:
So my HD has been away at HTC for nearly a week, and im currently tracking its return journey, due to land back here at some point this morning.
I have had no contact from HTC so its going to be a suprise as to whether anything has been repaired.
My hope was they couldn't turn it on at all - thus replacing the bits n bobs inside, replacing the main board containing my 6.5 ROM.
So for now im hoping "no news will be good news", but I will update this when I have it back.
Click to expand...
Click to collapse
Just recieved delivery. The service report states:
1. Diagnosis
2. Replace Main Board
3. Function Test
Result
Confirms it was a H/W fault and my "flashing" did not effect the warranty status. That may have been because they couldnt get far enough to confirm so.

Mega75 said:
Hi, I've the same problem. Do you have any solutions?
Click to expand...
Click to collapse
Other than a Warranty repair, im afraid not. Try your best to get it back to HTC official software, then report it as no power / cant boot.

Nasher79 said:
Just recieved delivery. The service report states:
1. Diagnosis
2. Replace Main Board
3. Function Test
Result
Confirms it was a H/W fault and my "flashing" did not effect the warranty status. That may have been because they couldnt get far enough to confirm so.
Click to expand...
Click to collapse
Good to know, confirmed h/w issue

i simply deactivated automatic shut down in power settings as mentioned in the first post and unistalled a couple of new programs i had recently installed!!
Not quite sure which of the above worked.. but atleast for now it seems to be working fine!! the screen has not turned off by itself and i have not had to remove battery etc to get it to work again!
I'm not quite sure if the problem is properly fixed but it has been a few days since anything occurred!! so fingers crossed!!

mine was doing this last tuesday, each time i went into my pocket for it, it was turned off, then i hard to do the reset pin or remove the battery, it has been ok since, i just thought, maybe it was me, pushing it in my jeans i might be turning it off.
also using duttys popular 6.5 latest rom, i dont think its fair to blame his rom, as mines ok now, maybe i should reflash it again?? im still waiting for a new version to be released.... JESUS!!! just looked it up to r12, im on r9 .
oh no... no it not..... says to go here, and it will be released here and not on dutty throy???
http://htcpedia.com/forum/forumdisplay.php?f=79

iamdarren said:
mine was doing this last tuesday, each time i went into my pocket for it, it was turned off, then i hard to do the reset pin or remove the battery, it has been ok since, i just thought, maybe it was me, pushing it in my jeans i might be turning it off.
also using duttys popular 6.5 latest rom, i dont think its fair to blame his rom, as mines ok now, maybe i should reflash it again?? im still waiting for a new version to be released.... JESUS!!! just looked it up to r12, im on r9 .
oh no... no it not..... says to go here, and it will be released here and not on dutty throy???
http://htcpedia.com/forum/forumdisplay.php?f=79
Click to expand...
Click to collapse
FYI, Throy is releasing roms exclusively to HTCPedia now, so no future roms will be released on either XDA or www.duttythroy.com

wow!!! i never knew!!!! thats crazy as his own site duttythroy wont be used.
im getting it now, but only 11 when it says 12 is out, either way, i will still flash i love the roms, i will be sure to be on all the site, incase theres another change of heart??
anyway guys i will report if i noticed the shutdown thing happening again with the version. 4mins till downloaded.....

I think theres a couple of different issues here. My own problem was due to faulty parts in the hardware itself. Absolutley nothing to do with any ROM, only reason I mentioned them was because of the invalid warranty possibility.
If your problem was ROM related, Im sure in the relevant ROM thread, there would be many people (everyone) with the same issue. Thats not to say that its not some sort of conflicting software you may have installed after the ROM flash.
Some simple troubleshooting steps:
1. Hard reset - If it still has a problem...
2. Flash Official HTC ROM - If still a problem...
Phone HTC.
All the best, hope you manage to get something to work for you. I know how lost I felt without mine!

Nasher79 said:
I think theres a couple of different issues here. My own problem was due to faulty parts in the hardware itself. Absolutley nothing to do with any ROM, only reason I mentioned them was because of the invalid warranty possibility.
If your problem was ROM related, Im sure in the relevant ROM thread, there would be many people (everyone) with the same issue. Thats not to say that its not some sort of conflicting software you may have installed after the ROM flash.
Some simple troubleshooting steps:
1. Hard reset - If it still has a problem...
2. Flash Official HTC ROM - If still a problem...
Phone HTC.
All the best, hope you manage to get something to work for you. I know how lost I felt without mine!
Click to expand...
Click to collapse
Your exactly right. Some people experience similar symptoms which are rom related others have same problem which is hardware related. One can only be fixed by HTC as motherboard problem, other can be rectified by different means without having to send device back for repairs

Hi again,
Today I have received an sms from HTC service informing me that my HD has a circuit problem and they will fix it without any charge.
I have to wait.

Completely lost trying to root UK Vodafone HTC Magic

Hi all,
Firstly apologies for the long post, and thanks for all the info that is up here... however I have managed to get quite lost. I'll try to take you though the whole story as much as I understand it, but I woke up this morning and decided (after 8 months) to finally root my android.
That was 8am, it is now midnight, and I've had sandwiches while working at it, all day. It has been in various stages of bricked, and I think I might have just sent it back that way - should not be playing with it when tired.
Things I have
1 x UK Vodafone HTC Magic, doing return plus power = 32B, HBOOT-1.33.0009 (another story here).
1x 16GB SD-HC card
1x 1gb Card
1x cheap nokia I can use as a reader for the 1gig card, but it can't handle SD-HC
Anyway I started off with the 1 click root idea, which obviously doesn't work these days, so followed the next link, then the next, finding I need to do the 'goldcard' method.
theunlockr.com/2009/08/14/how-to-root-your-mytouch-3g/comment-page-3/
Anyway I'm not sure where all the time has gone (16 hours now), but I have learnt what an SPL was, flashed mine to an ‘imperfect’ one, managed to flash it to deteethed google, then cyanogen on top, but it would never boot, and just hangs saying HTC Magic, then managed to flash it using 'myhero' which gave me a Hero like phone.
However I now seem to have messed it up again as I'm determined to do the cyanogen mod - I really want to be able to tether, and lots of other bits and pieces.
The state at the moment therefore is I have it all working with fastboot, and can easily get the Amon_RA recovery image going, but the cm_recovery one makes it hang and do nothing. If I try and replace the recovery section using fastboot it tells me it has failed (I forget the exact message).
I can therefore upgrade things using the Amon_RA backup, but as I said things don't seem to entirely work, and at the moment my phone is hanging (I think as I'm tired I've overwritten my backup). I'm also not sure if this goldcard method is working – I asked a question in the thread and it seems that it might not be.
I guess I'm just looking for a few pointers, after 16 hours sat here I'm generally pretty frustrated and totally lost - there is a lot of information, but there are so many permutations of hardware, and a lot of the information is now out of date. Trying to take everything in as well as deal with a specific problem may actually be beyond me  Which is something I hate- being the newbie needing help with a potentially simple problem (though I have had a good go at it).
I'm really not sure what stage the phone is at, have I rooted it? After all I can use the myhero rom, but on the other hand I can't do what I want to do, so therefore is there a problem? Exactly which step makes it ‘rooted?’ as every guide is obviously a chain of events to make it in to something else. I'm honestly not sure, but it isn't a fun feeling – I’m stressed and at the momentI have no phone just a brick that I can fastboot to recovery, and a bunch of backups as soon as I get it working again.
I really had no idea it would be this difficult, and am a big angry at Google/HTC for making it so - it is easier to get Hackintosh working than this! I’ve also managed to do hundreds of other similar things without any problem – Xbox Media Center (including soldering), and a few more spring to mind, all to use the hardware I already own! My hardware!
Anyway advice and pointers are appreciated, as although I've learnt a lot today, I'm still blundering about, and it is a matter of time until I cause serious damage in my attempts to make it better, al alternatively just throw in the towel, but then I don’t think I can go back as I have a horrible feeling that the restore I did didn’t work.
Again anything you can offer is appreciated, and if you need more detail, I’ll do what I can!
Anthony

Also just to add I've tried searching, which is partially how I've got myself in to this mess - solve one problem but make another!
Also I do have my APN settings, so when I get it installed, I can get my google account workign with it - I think i've had to do this about 6 times now! So if there is a way to get it in to 'myhero' which I think I can do again, and download an apk, then I should be able to do that.
Ant

There is a lot of information and everyone is recommended to do their research before rooting the phone.
That being said, it sounds like your phone is rooted if you can boot into recovery and load up a sense ROM. It'd been much easier to follow cyanogen's wiki instructions for non T-mobile 32B Magics. I also have a vodafone Magic and I rooted my phone successfully using the method.
Not having used the goldcard method, I don't exactly know where it went wrong. Have you done full wipes before applying a zip file? Stuff like that which might be easily overlooked?

Yeha I've been wiping it all before flashing, so that isn't the problem.
I also did as much reading as I could before starting (and watching the youtube guides before doing anything), but I guess a lot of the problems were unexpected (aren't they always?), for example I only found out half way through that I would need to flash the SPL, and it took me 40 minutes to figure out what SPL was, and what it did, then another 40 to work out how I was going to do it, then 40 to do so.
I have been following guides though - for the cyanogen one I get all the way down to flashing it with the detoothed google build, then cyanogen (obviously wiping before doing these). All the steps appear successful but then it doesn't boot.
The phone is also a rather strange one, a vodafone branded one that says 32B, but I'm sure it has more RAM.
Currently trying 'method 2' from here
android-dls.com/wiki/index.php?title=Magic_Rooting
to see if that works, but I'm not optimistic.

Yup 15 minutes laters same problem - it hangs on HTC magic screen, which is exactly what it does when I go for the Cyanogen one.
I'll goign to try and google for other roms, see if any of them work sucessfully (and might provide a bridghe to what I want to have.
Again however anybody knows good guides, sites or anythign else let me know.
As I said a big problem before is I'm reliant heavily on google, and a lot of the informaion out there is useless, as it is out of date in a big way. Also I don't know anyoen else who has doen this, so recommendations ofmethods/roms are dependent on my reading, not wword of mouth (which is generally better).

Ok I've tried the method 2, defiantely no sucess, went back to the myhero (which performs awfully, so much lag!), and have now tried flaskrec.apk on there.
It does not backup, but then bypassing that step, it gives me the error 'Flash failed'.
Really stuck now, and no idea what to try, any suggestions at all would be helpful. I'm almost at the stage of wishing I'd got an iphone :-(

Bell phones and the lack of 3 button combo

I'm starting a new thread because it doesn't necessarily fall in to unlocking of the phone (as I've been asked).
I'm guessing any new purchases of this phone will have the recovery/download 3 button combo feature completely disabled.
The reason why I say this is that I've been to 5 different stores between yesterday and today (with the most recent one having a stock amount of 9 phones) and here are my findings:
Every single boxed up phone has the feature disabled. (All I did was have them install the battery (no sim or anything) and pass the phone to me).
However, every one of those 5 stores that I went to, I did it flawlessly on their demo phones.
So my guess is, as the demo phones would have been the first batch Bell provided (and some being on display before any actual product released to the public), all subsequent batches of these phones will have this feature disabled.
I went to 2 different best buys that have ample stock of the phones because it is onsale this week, and none of them worked... nor did they work at the future shop I attended or the 2 bell stores (including the one I purchased and returned initially).
But every single demo did.
So if anyone got their hands on the very first batch of phones and it works then you're a lucky one. For the rest of us, I think we are S.O.L.
There's got to be a way to do it... Anyone know a Bell Representative or better yet a person inside samsung that will leak that info to you?
Heck I don't even want to unlock the phone. I'll stay on Bell's network, I just want to be able to load new versions of Android without any risk of bricking my phone.

Thank you! It was annoying reading all those posts abt this in that thread.
And I'm not too sure that the new phones don't have it. There have been a few people on the thread that have said that they got the phone at launch, and it didn't have the feature, but when they went to return it and get a new one (from the new shipment) it was fine...
So really I dont think its very easy to tell if its gonna work or not...

I think I'll wait til september to buy the phone.
I don't care too much about custom roms and the like, the stock one is fine, but Bell has a history (See the i7500L) of not updating their firmwares in a timely fashion. The i7500L is still on 1.5. Terrible if you ask me, considering the "open-source" feel of android.
So there are rumours, I don't know if its true or not, that bell is going to have an official 2.2 update in september. Maybe then I'll buy it and by then all phones will have the 3 button combo on them.
I just went to a local future shop here, and the phone representative contacted their Bell Rep, who was at another store, he couldn't do it on the phones they had there, but promised to call Samsung on Monday to find out if their is an alternate way.
Maybe you have to hit a reset button along with it. I remember doing something similar on my old HTC diamond phone, maybe this is the same thing (sort of).
Too bad, I loved this phone all the 4 days I had it (up until reading about the 3 button combo). I sort of miss it.

I just put a call in to Samsung to find out why some work and some don't, they said because the phone was so new that I had to call a number specifically set up for support on the Galaxy S but they are only open Monday to friday..
So hopefully with all this calling around I'm doing something will be figured out.

I got my Vibrant on launch day, 3 button combo didn't work. Swapped it out for a new one, from a new shipment last Thursday (august 12th) 3 button combo works.

arr0ww,
Can you confirm what i've been reading on wiki then?
It states:
"Note: There are many Bell I9000M floating around with this feature disabled, without the Download Mode enable you wont be able to restore from a failed firmware flash. We highly recommend you to take it back and exchange it for a model that can work properly with the 3 button combination. The first batch from around Aug 5 or Serial # ending with 6000000 have the 3 buttons combo disabled, the new batch after Aug 11 with Serial # ending with 6500000 have the working 3 buttons.
example of full Serial # 89302610202006500000"
Do your last 7 digits end with 65 and not 60?
Also, where did you get yours exactly? I think if its close to me, I'll just pop by that store and get it (assuming your somewhere in the GTA).

I got mine first thing Launch morning. My serial is 59XXXXX. 3 button combo IS working.

it shouldn't be hard to fix the issue. from what i've read, and people have said, the 3-button combo is written into the SPL part (256kb) part of the Nand. all we would theoretically have to do is flash our SPL with some else's 3-button enabled SPL. now two of my friends bought their phones same day as me, and have theirs enabled, and both are rooted, so it's not hard to get our hands on a copy.
i have posted another thread in the software technical section about this and haven't gotten any replies (maybe it's the wrong section). the g1 users flash their spl, but they don't talk about how to make an image of the current spl. so i'm stuck here. i know it can be done, just don't know how yet.
apparently nandroid backup doesn't backup the spl, so that's useless to us. from the SPL backup kit for the g1 users, i read the batch file, and it reads specific hex addresses in the nand and writes them to a file, but i would assume these addresses are different for our nand. so once again, useless.

For all those that have their 3 button disabled... can you confirm if your serial ends with 60XXXXX? Maybe its limited to just that batch of s/n's.
As for wang1chung.. hopefully its a simple fix.. but i'll refuse to buy one again unless I get one that is confirmed working or easily fixable to get it working without a cable.
Thanks

Electroz said:
I got mine first thing Launch morning. My serial is 59XXXXX. 3 button combo IS working.
Click to expand...
Click to collapse
it is possible the bug was only in the batch with numbers ending in 60xxxxxxxx
since the ones on 59xxxxxxxx works, and 65xxxxxxxx works
that seems to be the logical sense

this would be nice
problem is, no one has been able to get a way to extract, and flash back the good SPL to the bad phones
wang1chung said:
it shouldn't be hard to fix the issue. from what i've read, and people have said, the 3-button combo is written into the SPL part (256kb) part of the Nand. all we would theoretically have to do is flash our SPL with some else's 3-button enabled SPL. now two of my friends bought their phones same day as me, and have theirs enabled, and both are rooted, so it's not hard to get our hands on a copy.
i have posted another thread in the software technical section about this and haven't gotten any replies (maybe it's the wrong section). the g1 users flash their spl, but they don't talk about how to make an image of the current spl. so i'm stuck here. i know it can be done, just don't know how yet.
apparently nandroid backup doesn't backup the spl, so that's useless to us. from the SPL backup kit for the g1 users, i read the batch file, and it reads specific hex addresses in the nand and writes them to a file, but i would assume these addresses are different for our nand. so once again, useless.
Click to expand...
Click to collapse

Hey guys, are you still able to start in recovery mode with a cable and ADB. I would like to know cause my G-sensor is dead and I went to Best Buy to exchange it and the phones were all lacking this mode.
I didn't swap ysterday because of this but I have to do something before aug. 20. After that I will have to see with bell what they want to do and it will surely go for a repair. I would prefer to have a new one working right away but the lack of recovery mode is discouraging me.

my s/n is 52xxxxx and 3button is disabled
sp991, recovery mode is still accessible via adb to those with the 3button disabled.
allgamer, i only suggested that as no one else had suggested anything else? i assumed it would be possible since the g1 users can read their spl via the command " pmemdump -a 0x8c000000 0x40000 " and save it to a .nb file to update later. maybe this would be better accomplished in the hands of talented coders/developers.

Mine is 64xxxxx and it is disabled.
adb works.

I exchanged my first i9000m coz the download mode wasn't working.
The second one I got two days ago goes into download/recovery mode without problem!! This one has IMEI ending with 65xxxxxx and manufactured in Aug.
I also tested new one at Bell store today which had IMEI # 65xxxx as well, but it didnt go into download mode. The guy at the store said it was the newest batch as they received it yesterday, and now i'm totally confused....coz I thought all newer batchs are download mode enalbed..

sp991 said:
Hey guys, are you still able to start in recovery mode with a cable and ADB. I would like to know cause my G-sensor is dead and I went to Best Buy to exchange it and the phones were all lacking this mode.
I didn't swap ysterday because of this but I have to do something before aug. 20. After that I will have to see with bell what they want to do and it will surely go for a repair. I would prefer to have a new one working right away but the lack of recovery mode is discouraging me.
Click to expand...
Click to collapse
do you have any other best buy store that you can go to?
try testing with the Download mode, it's easier than testing with the Repair mode
the Download mode kicks in right away, after you put in the battery, and do the 3 button test
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
check the wiki for some visuals
you can do it even with the plastic back and screen protector on top

trueimage said:
Mine is 64xxxxx and it is disabled.
adb works.
Click to expand...
Click to collapse
ADB will always work, but it's useless if it gets bricked
good to know 64xxxxxxxx is not good
so i guess batches between 60xxxxxxxx to 64xxxxxxx are bad?
since the 59xxxxxxxx were good, and 65xxxxxxxxxx are also good

karakake said:
I exchanged my first i9000m coz the download mode wasn't working.
The second one I got two days ago goes into download/recovery mode without problem!! This one has IMEI ending with 65xxxxxx and manufactured in Aug.
I also tested new one at Bell store today which had IMEI # 65xxxx as well, but it didnt go into download mode. The guy at the store said it was the newest batch as they received it yesterday, and now i'm totally confused....coz I thought all newer batchs are download mode enalbed..
Click to expand...
Click to collapse
that's exactly what we are trying to find out, to see if there is any pattern
but if the one you tested with 65xxxxxxxxxxx didn't work, then i guess we can't really identify it via the serials numbers, and only can be tested manually.

Try downloading the new firmware for bell the JH2 that you can download via Kies this might fix the 3 button combo for people have issues. as the recovery screen is a bit different. give your a warning now that you have entered the system menu. the old recovery screen did not have this.
Someone that can't get into recovery should try this update..

no dice, just updated
EDIT: what's worse is i thought it would've at least helped with the gps lag, and now i can't find my location at all. under the gps performance testing option, i can't pickup any satellites whatsoever.
i'm pissed now, as i needed it to go on a roadtrip tomorrow

Take that multi-touch! Fix and lock in what works for YOU regardless of updates

By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes? Suddenly you have dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. Touchscreen works ok when held or plugged in, but is unusable on a table?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q, will work on LTE and custom ROMs also):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in this post.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
Settings->About tablet [tap "Build number" 7 times]
Settings->Developer options [check "USB debugging"]
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
wait until Android is COMPLETELY booted
Note: if you are on Android 4.4 the stock 4.3 kernel will not get past the BouncingBalls
wait 120 seconds for the boot to settle down
press/hold the Power button 10-15 seconds until the tablet reboots
proceed to next step
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
if adb reboot does not work for some reason, use the power button to shutdown/reboot
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
upon first reboot you will have the touchscreen software from the installed ROM/kernel
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.

very interesting! lots of FC after loading the file, cant really "Power off using power button" because of FC-windows, using adb reboot instead.
current ROM: [ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 10-TEST][2013/08/27]
ts-10: no more jumping in google maps while zooming/panning, but still jumping in other apps. after second reboot, starts jumping in maps again. after third reboot, no jumping on rightside of screen.
screenshot using two fingers
ts-20: lots of jumping on right side of the screen, zooming/panning in gmaps is still jumpy. after third reboot, still jumpy in gmaps.
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, same effect. after third reboot, still jumpy on right side of screen.
so what exactly are in those files?

neonlite said:
very interesting! lots of FC after loading the file, cant really "Power off using power button", using adb reboot instead.
tried ts-10. no more jumping in google maps while zooming/panning, but still jumping in other apps, will try others.
so what exactly are in those files?
Click to expand...
Click to collapse
When you say lots of FCs, can you tell me what ROM/version you are running?
You should IGNORE any instability in that first boot. While you can boot into android using the files I'm providing (and in some cases run fine), there could be mismatches in versions depending on what you have currently installed, which is why I say in RED you must reboot at least once before the system will become stable.
Once you do that reboot, you are back on your original software with just the touchscreen controller updated.

neonlite said:
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, seems most stable.
Click to expand...
Click to collapse
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.

sfhub said:
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
Click to expand...
Click to collapse
yes, ignored all FC's. no problem.
ts-10 is running perfectly, no more jumpy stuff. maps/right side of screen, hold and drag working great too.

I really appreciate how much effort you've put into helping others with troubled devices here.
Could we get some clarification on what exactly the 3 packages are? Are these touchscreen settings customized by you or simply the settings from each of the 3 versions of 4.3 we have had available to us?

You sent me here from the other thread and i must thank you, the ts10 one worked fine and now no screen problems, cancelled my replacement. Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?

It is the touchscreen controller software.

pashinator said:
Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
Click to expand...
Click to collapse
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.

sfhub said:
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
Click to expand...
Click to collapse
cool i thought i broke it by bashing it to get the screen to work again

i've been a long time lurker at the xda forums and your multitouch fix made me register and become a member just to say thanks. ts10 fixed my multitouch issues, going to observer for a few more days and update you if there are bugs. thanks a lot!

My tablet was working perfectly on the JSS15J then JSS15Q came along and I found letters "sticking" while typing and the screen was unresponsive to touch while laying flat on a table. I flashed the ts-10-lock image and so far, so good. I have been typing for awhile now with no "sticking" letters, and while laying flat on a table. I have not encountered the unresponsive screen at all flat on its back or otherwise. I will continue running through scenarios that used to give me problems and report back if I encounter anything. Also, running Bulletproof kernel and no impact with kernel functions.
Thank you sfhub!

Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
This is the video of my N7 placed on my MBPs' keyboard.
http://www.youtube.com/watch?v=H05N1P0dpTo
Can this really be only a software problem?
I am not really experiencing other touchscreen issues with my N7 except for some very rare stuck touches. This one I triggered by accident.

bandit_knight said:
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
Click to expand...
Click to collapse
So this guy goes to the doctor's office and says my head hurts everytime I hit the wall. The doctor says, then stop hitting the wall.
Couldn't you just slide it over and don't use the tablet on top of the keyboard?
Have you considered the MacBook Pro might be emitting interference? Stray currents and voltages? It doesn't take much to throw these capacitative touchscreens off.
On this thread, most people have it much worse than you making the tablet very hard to use. We are trying to get these units back into a state that is at least usable.
Your case, while an interesting science project really isn't something someone would feel any sense of urgency to help address.

Excellent.
I'll try these now and put them through there paces.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Great work
Incredible!! tried the ts10 and OMG everything is fixed!! Great work, sfhub!!
you should work in Google, seriously! shouldnt he, everybody?
My device is:
1) 4.3 JSS15Q
2) two finger touching registered as one finger, and muiti-touches ghosted. hold on the Left side of screen and the touch is registered repeatedly
1) TS10

Yea I booted 10 first and it is great. I can't reproduce any of the bugs I've seen before using YAMMT.
Google Maps Pinch/Zoom is working flawlessly. I couldn't even zoom in before.
The OP says to "fastboot boot boot-ts10-lock.img". Should we eventually "fastboot flash boot-ts10-lock.img" to make it permanent?
My N7 is:
HW rev_e
Bootloader....... FLO-03.14
15Q - CM 10.2 Kanged Build 9
Sitting the N7 on my Logitech Keyboard doesn't make it go crazy either! LOGITECH FTW

sfhub said:
It is the touchscreen controller software.
Click to expand...
Click to collapse
How do you "lock" it in so that it won't get updated? Is it just a file in the filesystem, if so how do you prevent "fastboot erase" from getting rid of it? I've looked at ektf3k.c and know where I need to make a change so that it will replace any non-matching version, but I don't really know where the actual firmware is stored. It doesn't seem to be in the vendor part of the kernel tree or in the actual ektf3k.c or ektf3k.h files. Where is it kept? kept in fw_data.b
I'm new to Android, but I'm not new to Linux or reverse engineering so please be patient with me. Just looking for a technical description of how you did what you did. What exactly is in the .img files?
EDIT: I haven't booted any of them yet, but I'm guessing these are Linux kernel images with a modified version of the elan driver. Sorry for being stupid, I'm just trying to put this all together in my head and I can't cope with anything that seems like magic. Thanks for your time.
EDIT: Ok, I figured out where the firmware is stored. I also successfully built a ROM with my compiled kernel and flashed them to the tablet. No brick, it booted the second try and seems to work. Of course there's no apps on it hardly.
I'm kinda thinking out loud here, please correct anything that I get wrong:
I started off with the assumption that there was a closed source driver, but that seems to have been incorrect on my part. After looking at the code a little more, I see that ektf3k.c appears to be the lowest level driver, outside the embedded firmware. The driver does only update the firmware in the case that the flash is empty (FFFF.....) or the firmware presented is a higher version (just as you said of course). It appears that a simple change will make it flash any version presented that is different than the one currently flashed in. I plan to try this on my tablet and see if there are any unexpected repercussions from doing so.
I wish I had a datasheet for the controller (hint hint anyone).
DISCLAIMER: I know that you have already solved this problem in an arguably better way, I just want to tinker around a little. Thanks again. :good::good::good:

sfhub said:
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be able to get touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
Click to expand...
Click to collapse
So if we do this can we lock the boot loader backup. If for some reason it doesn't work will I be able to take it back for exchange. After unlocking the boot loader. Do people leave the boot loader unlocked . Is the software staying the same meaning will I be ok downloading future updates.

Is there a way to find out what variance is installed right now on the device? I got JSS15Q and my tablet is useable but sometimes there are ghost touches or the touch is stuck or gets interrupted and the likes.

Sensors and MCU not working

Hi guys,
New owner of a S4 (GT-I9505 international) here with a problem. 2 days ago I noticed the screen wasn't rotating anymore. I used to rotate it portrait/landscape in applications like Camera or Internet (browser). The moment when it started to bother me was when looking at pictures with the phone in portrait and the image was landscape. Trying to rotate the phone didn't help. It was frozen. I called a buddy of mine who has some experience with Samsung devices and told me to verify the "Auto-Rotation" settings. It was all OK and enabled. Then he suggested turning the phone off and pulling out the battery and SIM card for 5 minutes and putting it all back. This didn't help either. Finally we got to the point where he told me to enter *#0*# in the Phone dialing application. As you might already know, this code gives you access to the "testing" hidden utility. There I tested all the options available. Everything was fine except for the Sensors and SensorHub Selftest.
In the Sensors section, all the tests failed, starting with the Accelerometer and ending with the Temperature. I uploaded screenshots taken during the tests. Please remember this started 2 days ago. Before this it was working perfectly. I don't recall making and major changes like updating any OS components or installing/running stress utilities related to sensors or device behavior. After doing some research online and reading about other people's similar problems I got to the point where I started to suspect a problem with the MCU (Micro Controller Unit). This component, according to Samsung, controls all the sensors and reads raw data from them without accessing the AP (Application Processor) this way extending the battery life. I believe the problem is here because it seems odd that none of the sensors are working all of a sudden. Can this component put the sensors into a sleep state and shut them down completely? Might this be the case here?
Below are the solutions I tried in order to revive the MCU and finally the sensors. I was all without success:
1) Turned off the phone and pulled the battery and SIM out. Put the back in after about 5 minutes. Result: sensors not working.
2) Reset to factory-settings from the settings option while the phone was in the working state (turned on). Result: sensors not working.
3) Rooted the phone, installed Clockwork Recovery, made a full system and applications backup and then installed custom ROM (two actually: PACMan, Google Play Edition (4.3)). I did this in order to exclude a problem related to drivers in the stock Samsung ROM, even if it was logical that Samsung being the owner and manufacturer of the device might have the "best" drivers and applications for inquiring the device components/sensors. I am aware this ended the warranty for me, but can I know it can easily be undone. Result: sensors not working.
4) Restored the original stock Samsung ROM. Result: sensors not working.
The utilities used for sensor testing were: Sensor Kinetics and Sensor Tester. Both can be found in the Play Store. On my wives phone, which is an old HTC Desire, both utilities picked up the available sensors and created graphs with the results. On my S4, I only got blank charts/graphics/results. In Sensor Kinetics for the Gyro for example, the message was "Waiting for the Gyroscope sensor...", just that, stuck.
If there are any other guys (or ladies!) out there who encountered this awful experience, please reach out and tell me if you found any practical solution, any other then just taking the device back to warranty. I'm open to any suggestions.
Best regards,
Andrei

Most likely a defective device ... can't you claim warranty and sent it back?

Sounds like hardware failure. This would be an issue for Samsung to solve.
Sent from my GT-I9505

AvelonTs said:
Most likely a defective device ... can't you claim warranty and sent it back?
Click to expand...
Click to collapse
Unfortunately I bought it second-hand and it does not have any warranty. I guess it's one of those moments I wish I had patience and gathered more cash to buy a new one from the store. Anyway, it's my bad luck. I had it working perfectly for weeks after buying it. I will use it like this for the time being..

i´ve got the exact same problem since yesterday...
i think i´ll take it to the shop for warranty

I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...

darklord said:
I've got the exact same issue. All sensors are having the same issue. None are working,
I found out because my camera app was not switching between landscape and portait any more. All pictures are saved as landscape...
Called Samsung Netherlands and they told me to wipe my phone (still latest original stock ROM) and try again.
Making a backup now using Kies... and will hard reset it afterward and check the sensors.again.
Probably not going to work... So I have to send it in...
Click to expand...
Click to collapse
Hi there. I had same problem with sensors and MCU test failed, so i took phone to service. They said its hardware failure and replaced main board. Im picking phone tommorow and we will see...

Hi guys,
I took mine to a local phone service, not the official one, but they are an affiliate. They could not figure out exactly what the problem was so they replaced the logic/main board just for testing. It was all working fine. They called and informed me of the findings. Given the fact I don't have warranty for it, they suggested to send it to our main service in Bucharest where they have a more sophisticated testing equipment. It is possible to get a more precise answer regarding the defective component and maybe a less pricey solution to the problem. At this time, the only viable option is to get a new logic board in place, which is about to set me back 250 USD. I will get an answer from Samsung in Bucharest by tomorrow or the day after tomorrow.
I will get back to you with my final solution... hopefully something not so expensive
@darklord, @eweu: please post back you findings. Maybe in the future when some other unfortunate owner finds his way in here, will have a better understanding of whats on the plate for him.
Thanks,

Hard reset did not work as expected. Going to drop it off at a local official repair center....

S4 Sensors failing
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week

KSal7506 said:
I have the same problem with my S4 GT-I9505 device not auto-rotate, air gestures with gyroscope and accelerometer tests failing. S4 been back for 3 weeks to Samsung for repair came back and failed again after 1 week
Click to expand...
Click to collapse
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!

canaris1780 said:
After installing some other ROM's and playing with different CSC's I have no sound and even no wireless and only Edge speeds on some ROM's. Restoring from backups, wireless came back and HSDPA+ also, but no luck with sound what so ever. Now, I have a tablet more or less. Thanks Samsung, this is great!
Click to expand...
Click to collapse
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.

i'm tired
canaris1780 said:
Flashed I9505XXUDMH8_I9505OXXDMHA_BTU, sound and wlan working again. Previous problem with MCU/sensors still there.
Click to expand...
Click to collapse
really i'm tired to solve this issue.
when i install new stock software the sensors work fine just a few minutes only yhen return to fail again.
i think its software issue and i'll solve it :good::good::good:

Sensors work again
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again

abdali_m2 said:
:laugh: :victory:
Its work right now by itself
:crying:
after uploading the pictures its fail again
Click to expand...
Click to collapse
I have the same thing here
all sensors are broken because of SensorHub BIN FW Version: AT0199999
then i try to update firmware with *#2663# it failed.

I have the same problem with my S4 GT-I9505.
Suddenly the device do not auto-rotate, and no air gestures with gyroscope and accelerometer are working.
The SensorHubTest end with FAIL.
Mid december I got one OTA firmware update and I didn't notice any problems first.
A few days after newyear I notice that my auto-brightness adjustment did not work properly.
Can't remember if auto-rotate didn't work when I notice the auto-brightness problem.
But finally I am here because I searched for sensors problems.
I did the SensorsHub Test with *#0*# and it ends with FAIL.
It seems that there is a problem with the 4.3x firmware.
With 4.2x all was fine.
Can anybody confirm my thoughts - that the firmware is broken and not the MCU itself?
What can we try? Downgrade? I read that one was lucky with "factory reset" but it didn't helped to revive the MCU of my device.
Thanks for reading
and answering
___
DK

Hi, i am a owner of a sch-i545 phone, and i have the same problem with the phone: no response of any sensor and a fail on test (or upgrade firmware) of the sensorhub.
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Yesterday i give the phone to a technician (a close friend of another best friend), he will test the phone on this weekend to determine what is the problem to try to fix it.
When He fix this phone, i will post any news!
Regards.

remy1004 said:
At this time i was tried a lot of solutions: i was flashed stock firmware, custom firmware, and of course a factory reset (by the way, the first time with this problem was when i did it a single factory reset), its still broken the communication with the sensors.
I get back to life the phone when i upgrade the phone from 4.2 to 4.3 (sadly) and get lost when i update the binaries in super su (previously rooted with vroot).
Regards.
Click to expand...
Click to collapse
Thanks for your answer. I have hope that the next firmware will fix it.
What is strange that none of any reseller/privers know this problem. It seems that also Samsung has no knowledge about this special error.
Well if the next firmware didn't fix the problem, I can replace my model with a working one, that is what the guy at the phone shop offers to me.
___
DK

Same Problem Here
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves. I have thought about this and looked around and to me it seems like there are only 3 possibilities for the problem:
1) The SensorHub BIN FW Version is out of date and needs to be updated manually (not through *#2663 as it doesn't work)
2) There is a connection issue e.g. the cable from the sensorhub to the motherboard is loose or broken
3) The sensorhub is broken (not the sensors)
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan

shadowsoulxp said:
Hi guys, I'm new to this forum so be nice :angel:
I am having the same problem in that none of the sensors are working which indicates that it is a connection issue or the actual hub not working or the firmware and not the individual sensors themselves.
[...]
I will try to find the firmware files and see if I can do a manual update. If that fails I will open up the phone and see if the cable is connected/broken. If I still cannot solve the issue, I will have to take it to the shop and hope I can fix it off warranty (I bought it second hand)
Dan
Click to expand...
Click to collapse
Thanks Dan for your reply.
I assume that your S4 shows the same behaviour as my one and the phone is still working fine.
The sensorhubtest failed and your light sensor for automatic adjusting and the sensor for turning the display are not working.
What is really strange that I went to a vodafone shop in Hamburg and ask them if there is any other one having problems with the S4.
You know the answer? They where wondering and telling me that this is wierd and they heard the first time of such an issue from me.
I showed them the device and showed them how I test the sensors. *#0*# funny they didn't know this combo
I hope that you succeed and share your knowledge,
with best regards.
___
DK