Related
I have been lurking in the shadows of this forum and it has helped me out alot so far. I finally registered after developing a bug or hardware problem (not sure which) with the original FW (rc33) that is preventing me from rooting my phone. Its with my QWERTY keyboard. It seems the entire top two rows are now activating more than one key stroke when i only press one, ie. press "e" and it comes up "3e". This really sucks when i get to the part of the rooting process to type "telenetd" before launching telenet. I have tried every combination i can think of to fix, but i am at a loss.
So, my question to all who can assist, is there an alternative way to root my phone other than the common way i find on all the forums? Anyway to do this thru the computer or anything? My computer uses windows vista. My phone has a non-rooted rc 29 (i did get that far in the process. i downgraded from rc33, got the recovery img on the root of my sdcard, along with the update.zip file. i also installed telenet from the apps store). I am ready for the next step is there is one for my situation.
I don't care how difficult or how many steps are involved, i just want to root my phone. Am i screwed or do i just wait for the official g1-1.5 and live with that version?
Red
P.S. please don't tell me to turn it in for servicing. I am currently located in the country of Bahrain and that isn't an option for me for about another year. yes i am in the military and kinda stuck. Thank you for any and all support you all have to give.
since you cannot send it in you should try servicing it yourself. i do not have the link to the service manual on hand but i know there is one out there. download that and get a few torx srewdriver heads(i'm sure there are a few laying around the base) take the phone apart and try it that way. or as i have done in the past firmly press your thumb over a few keys in those rows and run it back and forth a few times, occasionally it can help it the buttons are stuck beneath the casing in some way, or stuck together
if you can connect to a wireless network and get tenetd typed correctly you can get into your phone from the comp using the telnet command on the comp
have you tried the "app for that"?
http://code.google.com/p/androidroot/updates/list
I haven't tried it so I don't know what's involved exactly but it is worth a shot.
simply type out the commands as if your phone were working normally...then use the trackball and backspace key and go back and delete the unnecessary keystrokes
Here's how the keypad works, if you're going to open it up and try to troubleshoot it:
The keys are capacitive, so there's no direct electrical connection when you press one down. There's typically one set of contacts that run in rows, and one set in columns. When you press a key, it activates the sensor in that row and column, whereas the other keys on that row and column only see half the signal. That reduces the number of pins necessary to get inputs from all the keys.
So if you're pressing "e" and getting "e3", the column wire is probably working correctly but you're getting the number row and the top text row.
Try taking it apart and seeing if there's some dust or grit between the keypad and the circuit board. If that's not it, usually there's a ribbon cable that connects the keyboard circuit board with the rest of the phone. Both the socket and the cable itself for this type of connection are notoriously finicky.
Let us know how you make out. Also, why will it be a year until you can get it serviced? Are you in the pokey?
great advice!! and timely too!!!!
Hey guys!,
Thanks for the options, it didn't take long for replies and that shows how wonderful this community really is. I will keep you all informed as to my progress. unfortunately i am going to have to wait until the morning to attempt to find a set of torx head screw drivers. right now its 11:52pm and everything is shut down. No, i am not in the pokey, just unable to get back to the states until then and if you thought the mail service was bad in the states, you should really see this place. i am not going to risk my phone through that service.
ohnoezmahfone, thanks for that information. my gut feeling is it has something to do with that ribbon cable. about 60% of the top two rows of keys are doing the same thing. Now, i have never dropped the phone or jarred it in any way, so i don't know why it just started doing this. but then again, it could be dust too. That one thing this place has plenty of!!! Sand and Dirt!!!. as soon as i get my hands on those torx screwdrivers, i will report back.
Now, if someone has an alternate method that might work before i perform open heart surgery to this android unit, by all means speak up! I can build computers but have never dove into something this small, nor do i have all the tools i am used to having. But i will give it a shot. Whats the worst that can happen? I hose it up and spend 400 on a G2 later this year? . Not a total loss, i guess.
i will follow up soon,
thanks again all!!!
Red
in case you dont have the service manual...
http://www.filesavr.com/htcdreamsma04
I used it to open one (got wet ) and it made the job very easy! One step at a time, and it really REALLY helps to have a plastic opening tool (or a plastic knife may work in a pinch).
gospeed.racer said:
in case you dont have the service manual...
Click to expand...
Click to collapse
Hopefully I'll never need it, but it's sure nice to have this sitting on my hard drive. Thanks!
gospeed.racer you are a lifesaver!!!! i recommend that .pdf to everyone. It bailed me out of having to enter the "g1, long distance throwing competition". Anyways, i followed the service manual step for step, took the g1 fully apart and when i got to the keypad module i didn't find any dust. kinda feeling like this was all for not, i proceeded to put the phone back together. once complete i powered it on. then i started to type and Holy Crap!!!!! it is fixed. all the keys are the way they should be and soon i will be on my way to rooting my g1!!!!!!
All of you here are outstanding and i am really proud to now be part of this forum. Thank you again, for pointing me in the right direction. I guess it must have been the ribbon cable not being seated correctly, causing my problem. well, not any more!!!!
Red
p.s. BTW i would like to thank all that posted in this thread. i couldn't have done this without you.
awesome that its fixed now. welcome to the world of root
get one of these http://www.androidaccess.com/sdcard/store.html
you wont need the top two rows of your keyboard to use it
it should reset your keyboard once you go back to rc 29 then it will allow you to just enter two commands that will root your phone. you can read about it here:
http://androidcommunity.com/forums/...allow-you-to-run-apps-from-the-sd-card-15502/
I just received a used nexus s i9020t and I've noticed that whenever my phone gets slightly cooler than say room temperature the hardware back button stops working correctly. When the phone is "cold" if I have BLD turned on and wait till the back light goes out I can press the back button when otherwise it wouldn't work if BLD is turned off. Does this make sense to anybody? I can try and clarify if it doesn't. I'm worried that its a hardware issue and that I'd have to get it fixed somehow. I just bought the phone and I'd rather now put more money towards it.
Sent from my Nexus S using Tapatalk
I'd like to mention that it is responsive when the phone is "warm". Its a really annoying thing and I'd like to get it figured out
Sent from my Nexus S using Tapatalk
I've not experienced your issue, so it might just have something to do with wiping and reflashing your current ROM (especially if you didnt wipe everything from GB to ICS). Though something to note: the "soft" buttons at the bottom use the touchscreen. You can witness this by going on a long web page and scrolling off the screen and down onto the soft keys, and notice that you'll be able to scroll left/right and up/down where the soft keys are.
This just means that if there is an issue with these, it falls back on either a software issue or touchscreen issue. Might help with diagnosing, ICS settings -> dev options has a good option to diagnose touchscreen problems.
I think the capacitive button mechanisms are different in the i9020 and i9023. I've had both and I've noticed that you can scroll around beyond the screen parameters with the i9023 but I cant with the i9020. Maybe somebody can correct me if I'm wrong. I've done some research and it sounds like I may have to pull the phone apart and try to take off some of the paint on the back button. Another suggestion that some people have is to slightly tighten the 6 screws on back of the phone under the back panel. I did that and its sorta helped. I can deal with it now but if it gets worse I may have to take the phone apart which is something I don't exactly wanna do. Btw I did wipe everything multiple times and restored from a backup and I didn't notice an improvement until I tightened the screws
Sent from my Nexus S using Tapatalk
You have a good point there, I assumed they were the same but they may be different, I've never experienced the i9020 to comment.
Good luck with your problem. You might try tightening only the screws near the back button and loosen the others a little, possibly giving it some leverage.
..
Here's the deal:
Did some interesting modifications to my sgs4g lately.
I've been overclocking for gaming with Tegrak (1.3g) lately, works fantastic with Raver's Unnamed RC2 rom. Been doing this for a while, testing many of the fine work from the mods here (Thanks!). I also currently run AdamOutler's Unbrickable Mod on my motherboard which got me out of a hard brick a while back (Thanks Again!).
So, sometimes heat would build too much during gaming forcing the processor to reboot, so i decided to install a heatsink. Problem is, the cpu is wedged under the sim/sdcard board negating a direct heatsink, although it would still probably work ok in general, better than the rear cover plastic.
How about a fan? A fan you say, why Ikoinu, that is the stupidest idea I've ever heard, a fan would never fit on our phones!
Don't be so quick to judge, my good friends. What if one could find a fan of, say, 15x15x4mm? That might work?
Wait a minute Ikoinu, you are in fact a genius of the highest order! Except the electrical draw of such a fan might negate our Juice Defender?
Perhaps a draw of 0,148 W from a 3.3v unit might be not-so-bad? (our batteries run 4.4v or so).
Why yes, for limited running that might in fact improve our OC induced temperatures. Again, we'll reiterate our initial statement, you are in fact a genius!
Well, lets not go that far just yet. I mounted said fan up top between the loudspeaker and the camera, where it fit nicely. Rather than pressurizing, I reverse mounted it as an extraction fan which should keep the dust out. I pulled the smallest pressure switch I could find out of a Ps2 controller (there are 3 on each stick) and wired it in to the negative lead as a manual control button, and ran the +&- leads to the battery.
I had to do quite a bit of modification to the inner case to fit, and cut the rear cover for fan and switch ports. End result? Works fantastically. It should, it's a 10,000 rpm fan! Now if it comes apart it will probably send mini shrapnel flying taking out a small crowd, but I'll cross that bridge when I come to it. (Plausible Deni-ability!)
Which brings me to my current problem: Power switch is not working anymore. I don't think it shorted, as I measured voltage on it and it is functioning just fine (it's a negative switch). Without said power switch, I can still get into CWM Recovery, and go up and down to my hearts content, but I can't select anything in it. Which means I can't flash roms, modify, brick my phone, I'm handicapped!
My solution is CWM touch, which can be installed with this maybe?: http://forum.xda-developers.com/showthread.php?t=1481228
I can't currently flash anything without a power button though. There is no Odin or Heimdall or OneClick options for our phones with CWM touch, as I can use all three still. With CWM touch installed, I have recovery back. That is if I can get it installed. I also have been fighting with flash_image to do it but it just will not work, neither in Better Terminal Emulator on the phone or adb on the computer. Now if it could be installed in a OneClick or one of the others, it should work.
Anyone smarter than me have any ideas?
P.S. I hope you find my embellishments entertaining!
Touch recovery has not been ported to our device.
Currently I dont know of anybody attempting this, but Im not in the know with all the projects going on. However I do know your attempts and further actions of wishing to shoot yourself could have been avoided with some simple searching about cwm for the SGH T959V. The recovery is built into the kernel because and not modifiable unless you compile a custom kernel with CWM Touch ported to it.
Exactly. And it shouldn't be a sec until somebody does. I'm just feeling here.
FB mentioned using softkeys. That is how I navigate CWM. I haven't used the volume or power button since discovering it. The magnifying glass will do what the power button does for you.
Yes, good call. My soft keys have been going out for a while now, I've been using Virtual Button Bar and have deprogrammed them. Reflashing gets them back, and I have tried remapping the power button to the home key (home and back work mostly, settings and search not at all) but that doesn't work.
Know what, I knew that about the search key but didn't think to remap that to home. Let me try it and I'll get back.
No deal. Remapping works fine when phone is on, but in cwm it seems the keys are pre-mapped for the model, they do not change their functions. Older cwm (2.2 Froyo) will use the back softkey as an enter button, but the new ones stick to the power and search only. And neither of those work
I've noticed the aroma file manager creates a calibration config file after the first launch.
Maybe it can be done the same way for CWM recovery itself.
It will have to be an internal file though.
Mmm, your right. It's got to have a configuration file to remap the keys. Question is, where would it be in system. Let me root explorer around a little bit and see what I come up with. If only I could build the team acid aroma cwm touch installer into an odin flashable to replace current red cwm, I think I would be all set. It's a little beyond me right now though. Doesn't hurt to ask I guess.
itzik2sh said:
I've noticed the aroma file manager creates a calibration config file after the first launch.
Maybe it can be done the same way for CWM recovery itself.
It will have to be an internal file though.
Click to expand...
Click to collapse
there is, when flashing on htc g1 I would always have to set it up... But the aroma installer wasn't modified like the one we have to use, it was exactly how amarullz did it.
Sent from my SGH-T959V using XDA
http://forum.xda-developers.com/showthread.php?p=27640961
This should help you Keep Some of your hair lol
Sent from my SGH-T959V using XDA
I'm fixing an infuse for a friend who needed the screen replaced simple enough job so I thought as I repair phones and electronics as kind of a hobby. However the replacement screen isn't responding to any kind of touch at all. It displays the puzzle piece lock screen and everything else even shows there's been some missed calls ect. yet will not respond to any kind of touch. I think it's a calibration issue but I can't get passed the lock screen so there's no way to change the setting. Honestly I'm most worried about all the media on the phone most (pics, videos, contacts, ect )
If there is a way I can retrieve that off the internal storage I'll feel better about taking drastic measures. Other things I've noticed is an unusualy long boot up time hanging at the white Samsung letters but this is the first time I've dealt with an infuse so I'm not to sure on that.
Any advice is appreciated.
Thanks,
s1im
There are different versions of screens or maybe it was revisions. At least for the LCD +digitizer assembly. Rev.6.1 and 6.2 and 6.3 if I remember correctly.
Edit....here is a link for reference, also two of the screens were interchangeable but not all three. Sorry I don't remember which ones.
http://item.mobileweb.ebay.com/viewitem?itemId=180914982430&siteId=0&isClassified=false
Edit....my statement regarding interchangeability may not be true. The screen I bought could be used as a replacement for two of the rev numbers. That could mean that it is backward compatible but the other one isn't forward compatible.
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
s1imch4anc3 said:
The link said this item has been removed, but to be clear your saying not all revisions of screens can be used as replacements that you must find out which rev your original screen is?
Click to expand...
Click to collapse
Correct mine had a sticker on it.
Bummer I have no idea what kind of screen she had I threw it away as a jumbled mess is there any other way to find out what screen it was... either way thanks for the replies
Wish I could answer that, but here is another screenshot. It shows one for 6.0/6.1 and another for 6.2 so my original numbers were off. Did the new one say what it is?
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
s1imch4anc3 said:
Do you know of any way to retrieve the pics and other media off the phone without being able to unlock the screen
Click to expand...
Click to collapse
Just guessing but maybe adb. You could try to edit the title of your thread or start a new one about this question.
Edit..I have an idea but first a few questions , is this phone stock, and would you be comfortable flashing a kernel if it is? This will give you CWM recovery which has mount USB storage as an option in it. All this can be done with the physical buttons, power and volumes.
I found something that may work without having to make software modifications so I'm going to try that first and if not I'll get back to you...
To answer your questions tho the phone is stock and I've rooted /flashed a couple phones with no problems before so I'm OK with giving it a try
Again I'd like to thank you for your continuous help
You should be able to pull everything you need with adb...but the problem is, is adv enabled? And can you pull a whole directory? I doubt you know individual file names for each media file, not to mention that would be a long tedious process as there are likely well over a 100 if not in the 1000s of music/pics/vids
Well..looks like you can pull a whole.directory (sdcard)
this thread may help http://forum.xda-developers.com/showthread.php?t=744454
Btw...you don't have to be rooted to adv pull
Sent from my HTC PH39100 using Tapatalk 2
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
s1imch4anc3 said:
UPDATE: I took the phone back apart finally after some grueling hours of adb research that lead me almost in circles and found that the replacement LCD is a rev 6.2 and that the revs 6.0/6.1 are the universal more common screens in the u.s. infuse. I decided to return the screen and get the other rev in hope it will be that easy...
I'd like to thank the 2 above members that gave me help especially adfergurson for sticking with me and my ?s I will post back when the next screen comes in to confirm it worked for anyone else needing this as future reference
Click to expand...
Click to collapse
ADB was the first thing I thought of, but flashing a kernel with custom recovery in Odin should allow you to get into USB storage. I am not familiar with the stock recovery but you could see what options are there. I believe it would be from device powered off hold volume up+volume down+ power buttons then release power at Samsung screen.
Were you able to resolve the screen issue with the different version? I am having the same problem.
So here is a tricky situation. My infuse was stuck on a bootloop i used a jig and the it continued to reboot. I read somewhere that it is possible that i have a bad power button. I took it apart and un soldered the power button and used the jig to turn it on, went straight into download mode and didnt re boot. I thought my nightmare was over, as I went to solder back on the power button the leads coming off the board broke, not the leads on the power button itself but the actually physical point of contact on the board. I tryed using some flux and cleaning it really well to see if i could get some solder to stick but nothing would work. I talked to one of the engineers here at work he said Im pretty much out of luck, because the leads to that run inside the board between the layers and if it breaks off there is no way to re attach it. I just want it to work even if i have to run 2 tiny wires to some other point on the board and use a tiny tact switch im creative i could get it to work if i had somewhere to solder the button leads to. I understand there might not be anything i can do but does anyone have any ideas?
If you guys need a picture i can provide one, any help is greatly appreciated.
same problem
well my friend i hace the same problem, and i find one point to reconect one terminal o the switch, but still missing one
there is
one point, one left
complete
finally, thanks to @steveRrada