Anyone got the jtag pinout/location* and dump of the flash ? I managed to progressively get myself from bad root, to some apps crashing, to download mode, to debug mode, to black screen its progress, just not the kind i wanted.
and all because someone wanted to try an ardrone on android..
cheers
* ok nm i figured that part out, bottom left corner two rows of pads, bottom row,
vref,tms,rtck,trst,tdi,tck,tdo,srst,gnd
hopefully the boot files knocking around for heimdal are just raw dumps of the bootloader, they look like it
looks like i spoke too soon, the rev of the board i have doesn't have the same jtag layout.... so if anyone has the verizon tab jtag, pipe up.
since i can't post links yet, flickr.com/photos/[email protected]/5597914369/
these are both 9 pin, the other pcb has two 9's on the other side of the pcb horizontally, one is near the qualcomm, the other closer to the cpu.
Maybe this might help
http://forum.xda-developers.com/showthread.php?t=1010314
Factory mode boot on USB.
ahh cool, i'll probably beyond that as i'm getting the black screen, but i was looking for that information anyway.. and its worth a try.
cheers
Related
I bought this G1 with a cracked screen and I decided to replace the screen, however when I removed a certain part in the phone I managed to rip a ribbon cable. I searched for a replacement part and found out that it will cost about $185 to replace it. Now I am about to buy this other G1 for $50 that had water damage that I will be using for parts. But before I buy it, is there a way I can see whats wrong with it using adb? I'm interested in whether the part that I need is in working condition.
the phones condition is:
-the screen does not show anything but a backlight
-leds work
-rebooting using three buttons work
-lcd is probably screwed up because when i hit the power button i see part of the home background and then it fades away.
-no g1 screen logo while rebooting
-normally vibrates once while rebooting
-android os boots up
-"adb kill-server adb devices" doesn't list me any devices when i hook it up to usb. maybe debugging is turned off.
here is a link to the part i am about to remove
http://www.cellphone-repair-shop.co...icrophone-and-sd-card-slot_50H10000-02M-A.htm
the pcb board has the trackball, usb port, simcard slot, sdcard slot, and various other peripherals.
sensimila said:
I bought this G1 with a cracked screen and I decided to replace the screen, however when I removed a certain part in the phone I managed to rip a ribbon cable. I searched for a replacement part and found out that it will cost about $185 to replace it. Now I am about to buy this other G1 for $50 that had water damage that I will be using for parts. But before I buy it, is there a way I can see whats wrong with it using adb? I'm interested in whether the part that I need is in working condition.
the phones condition is:
-the screen does not show anything but a backlight
-leds work
-rebooting using three buttons work
-lcd is probably screwed up because when i hit the power button i see part of the home background and then it fades away.
-no g1 screen logo while rebooting
-normally vibrates once while rebooting
-android os boots up
-"adb kill-server adb devices" doesn't list me any devices when i hook it up to usb. maybe debugging is turned off.
here is a link to the part i am about to remove
http://www.cellphone-repair-shop.co...icrophone-and-sd-card-slot_50H10000-02M-A.htm
the pcb board has the trackball, usb port, simcard slot, sdcard slot, and various other peripherals.
Click to expand...
Click to collapse
you ARE SO FUNNY!!!
Why? can I laugh too?
I don't see you turning a profit considering u can buy one for $200 on craigslist easy
its funny cuz its like you trying to buy a coumputer without a mother board. this is the main thing in the g1 it would be cheaper to buy the phone brand new
i have two, one of them needs this part and the other one has the part i need. and plus im fixing it for my brother.
G1 #1
-already Bought for $74
-needs pcb board
G1 #2
-$50 as is
-has pcb board
-has water damage
anyhow I managed to get into recovery and did a wipe logged in but once the screen turns off i cant turn it on anymore. would you say it is safe to exchange these parts?
Wrong Forum, goodness
how is it wrong..I'm not asking anybody to take it apart and do it for me. if it was in the wrong place would it be because I'm not developing something for someone to use. is there a section for modding, taking apart the g1 and internals. if i could develop something i would. i guess there's no help in posting useless remarks because that doesn't contribute to nothing. If this so happens to be in the wrong forum well then this is my first mod now isn't it? and since you went of of your way to tell me its the wrong place why don't you be helpful to lead your fellow xda forum member. ok.
accessory forum This seems to strictly be about discussing the SOFTWARE for the Dream. Accessory forum covers mods and replacements (to my knowledge)
$50 for a water damaged G1? WTF? Are you serious?
miketaylor00 said:
$50 for a water damaged G1? WTF? Are you serious?
Click to expand...
Click to collapse
do you mean by that as expensive or cheap???
prince.siraj said:
do you mean by that as expensive or cheap???
Click to expand...
Click to collapse
I'd say expensive, as you have no idea the extent of the water damage. If the phone was on while dropped into the water, the mainboard is likely dead. Buying it would be a waste.
Also, this forum is for software development. Moving this thread. Thanks!
hey thanks for moving my thread. as i reread my post it seems more of a question than a developmental thread.
further testing
i booted up
ran through all of the radios wifi, 2g, 3g, orientation sensor, made a call and they all seem to work fine. the one problem with this phone is that if i turn off the screen it won't turn back on.i think that maybe the pcb board might be salvageable. would that be worth doing?
What cable was it that you ripped? What was it connecting? And is it possible for you to take pictures?
my digi cam isnt working but this will do. its like a 1/8" rip on the side of the ribbon i was thinking about repairing but i cant because the ribbon is soldered to the board. i figure that i should try swapping it out, what could possibly go wrong? im assuming that the lcd has lost the ability to regain power after turning off from the water. and maybe...possibly the main pcb has dried up and not been damaged considering most things work fine. thanks for sticking around.
I'm not liking your chances of getting this working, but fwiw here's the service manual:
http://mikechannon.net/PDF Manuals/HTC Dream SM (A04).pdf
Thanks I already have that manual printed out. Took it all apart like4 or 5 times. its pretty easy to do. I'll be starting operation on it tonight.
PLZ help im freaking out. i accidentally booted into the blue light mode, but when i pulled the battery and rebooted the backlight wouldnt work. i could see everything and even navigate my phone but only under a light. the backlight just wont turn on during boot and changing the setting doesnt help.
i dont get it the thing was working 10 minutes ago and now i cant use it what should i do? i love this phone but i cant afford a new one. is there a way to tell it to turn on during boot in the console?
ok new update the backlight works if i have the keyboard open. i know 100% its software and not the screen. something when wrong with the boot prosses or something.
i think the trackball boot (bluelight boot) must have options but wont display on the screen maybe. like a bios menu. this is very infuriating
Why don't you restore a recent backup?
i have even went as far as downgrading with the .nbh file. and re installing the bootloader (Just the original, didnt want a brick).
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
lbcoder said:
Definitely NOT a software problem.
This is a HARDWARE problem -- hence the fact that it works when the keyboard is open.
When you pulled the battery, you might have twisted/pulled something.
*** I would check the ribbon cable connecting the display to the main body!!!
Bluelight mode (where you end up by booting with the trackball pushed in), is just a serial console allowing interfacing with the radio firmware. Unless you actually had a serial cable connected and punched in some commands (which happen to be security locked, therefore wouldn't work for you anyways), bluelight mode wouldn't be able to do this.
Click to expand...
Click to collapse
if that were the case than wouldnt it flicker if i flex the screen/hinge ? ill try anything at this point cuz im outa warranty and have no money . im going to the store later trying to update to official 1.6 so i can convince them its software related and they may replace it for me.
oh forgot to mention that if i close it and open it the light stays off untill i hit end and unlock with menu again. im not to sure if that helps.
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
projectzro said:
OK OK OK you are right. i just half closed it and the light stayed on untill it compleatly closed (so the screen flipped, i thought that is what triggered it) and then i got it to stay on completely closed and then the problem flipped to it wouldnt come on while open and now back to the way it was. so im going to go buy a T5 screw driver today and clean the contacts of the ribon cable and reinsert it (i have had experience with that just need to know what ribon. a pic would be nice)
Click to expand...
Click to collapse
There is only one ribbon running to the screen. Try THAT one.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
LOL lbcoder - always practical.
lbcoder said:
There is only one ribbon running to the screen. Try THAT one.
Click to expand...
Click to collapse
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
projectzro said:
lol ok didn't know that a lot of the devices I have taken apart have had 2 one for the desplay and one for the backlight. Getting a T5 screw driver in half an hour. Will post results later. Hopefully this works, therr area few more ppl with the same problem.
Click to expand...
Click to collapse
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
ezterry said:
There are two wires going to the screen.. sounds like the "top" one is loose... The jtag photos will give you an idea (it's the two com ports next to the jtag test points)
These are usually taped down very well..
Also you need both a T5 and T6.. the "Security" (has black void sticker) screw is larger than the others.. and a small flat head screwdriver to unclip the cover..
If all else fails: replacement screens seem much cheaper than the phone on ebay.
Click to expand...
Click to collapse
ok got it apart 3 times and no luck its prolly the ribbon cable. im going to test that soon. i have a donor phone comming soon from a friend who dropped it in water, the ribbon cable should be fine to use. if that doesnt work im thinking maybe it is software. either way if i cant get it fixed by next month im spending $410 on a new mytouch 3G brand new from the store and getting insurance XP
Any help would be grateful on this one
I have just changed the heat sink on my 9300 wifi ITX motherboard GF9300-D-E.
It will not boot windows as it gets to the starting screen and stops. Then when i tried linux it will kernal panic and not boot that either.
I thought it was memory and removed one of the sticks. This is when things started to get strange. The bios screen did not fit my monitor as it should, has done previously, also there are strange flickering on this as well.
So i have tried it with both sticks in one stick [both tried]
Now I am a little stuck as to what it can be. I have also reset the bios to a default state to see if that was the problem and it was not.
There is also the issue that on some boots the bios will not fully load up.
If this is not an issue with the motherboard then i am sorry but i am a little stuck for the reason at the moment.
So anyone any ideas on this as I'm a little stuck. Any other info will be added if you think its necessary but i think its all covered.
Please help I miss my desktop, my ageing 5 yr laptop really does not cut it any more
have you tried safe mode? press f8 when windows is starting. if you get a blue screen post what the error message is.
Yeh the one time i got that far i had
Page_access_in_non_paged_area
That was also on a recovery boot of windows.
Next time nothing happened...
Also i get weird graphics glitches on the memory test from ubuntu. if that means anything to anyone
chris10230 said:
Yeh the one time i got that far i had
Page_access_in_non_paged_area
That was also on a recovery boot of windows.
Next time nothing happened...
Also i get weird graphics glitches on the memory test from ubuntu. if that means anything to anyone
Click to expand...
Click to collapse
i need the stop code. it goes like this 0x000000 and so on.
Yeh i would love to post that error message but i cannot get that far until it crashes
I got to the windows system recovery hit enter, then it stopped working
Now it wont even give me a video output! Really starting to think its hardware, but what hardware i do not know. Later im gonna try some RAM from my house mates pc and see if it does any better. If that doesn't work then i think i may be RMAing the motherboard as its the only other thing it can be!
If you have any more ideas joe then i would be welcome to hear them as i would rather not go down the RMA route...
Wish id noted down that bluescreen when it came up now
sounds like your video card. is your video card onboard or add in?
on board but i can disable if i have an external one, i can try this as well house mate has a spare will get back to you when i have tried that one as well.
If it is that then def an rma job. Also i would not be surprised it has been idling at 70/80 degrees C for about 8 months due to the passive cooler i had on it.
Hey,
I had this error, and a range of other ones, stuff like Memory_Error etc (can't remember codes), on my laptop earlier this year.
I tried memtextx86, and burnin, as I suspected it was an issue with ram - I also tried 3 different sets of rams, with different combinations of sticks. Nothing worked.
Unfortunatley, I took it back to the manufacturer and it was the motherboard had gone faulty.
I hope this isn't the case for you, but those 2 programs may be worth trying. Just as a note, neither reported any issues with the ram.
When in windows (vista at the time) I could not be in for more then 20mins without a system hang and crash. Although I did have video out.
Hope this helps
Stu
If the only thing you changed before it started to play up was the heat sink, its probably the cause.
If its turning on and then playing up after a period of time for no apparent reason it could be heat.
Is the heatsink on the right way? I put my amd stock heatsink on backwards when I installed it, didn't notice for 2 months, it wasn't touching the processor at all. Funny when I look back on it.
Did you put thermal paste on it? I once thought it would be a great idea to clean all of that gunk off my cpu, not so good in hindsight.
Hope it helps,
They say you learn from your mistakes, an I've broke more computers than I can count.
stu i shall try at the weekend one more exam and im free for another year!
and mercianary yeh i did clean the paste off, i did apply paste, but going back is a good point as i think there may be slight sizing issues with the heatsink i changed it for. As for temps, not real problem i think as i want from a passive heat sink to one with a fan so it must be cooler, that was the idea anyway.
It was idling at 45-55 if it did anything that needed the whole chip, its a 3ghz core2duo it hit 65 easy and it starts to underclock at 70 so i wanted it to be cooler so i could use all the power all of the time! In hindsight a bad idea.
Also on the grounds of the stock cooler that is broken as it kinda got stuck on the motherboard when i put it on one of the clips went straight through and jammed....
anyway everyone who has replied thanks i will come back when i have done some testing.
This may be a problem beyond the scope of android, but seeing as I'm running it, I thought I'd try here first.
I've noticed that the lower left hand side of my screen has a "dead spot" where touch is simply not registered. To illustrate, I went to screen calibration's test screen and drew a straight line along the edge of the screen. (See Attachment)
I've tried recalibrating the screen (manually and resetting to default calibration) as well as wiping data and reinstalling the system. Reinstalling the system worked once, but then the problem came back and subsequent reinstalls did not fix the issue.
I'm running Incubus26jc super froyo [RLS 12] on the 15-07-10 340X480 Froyo Kernel.
Anyone else seen anything like this? As far as I can tell, the problem is not getting any worse. Currently, it's only a hindrance when trying to use keys in that region, but I can work around it by switching to and from landscape. It's a bit of a hassle, so I'm hoping someone may be able to shed some light on the situation.
I was sure it was hardware until the system reinstall fixed it, but am now baffled as I can no longer replicate the fix.
I have not tried reinstalling the kernel but will at some point in the next day or so. I'd like to avoid switching back to WM to check if the problem persists, but may have to... we'll see. Doing everything I can to make this phone last until the Incredible month of February when I'm up for an upgrade.
dont know the issue resolution... but i have the same with my touch vogue.. and in the same 'area' apparently as well.
hard for me to hit the 'a' key on my keyboard. hehe
I'm glad to see I'm not the only one... anyone else?
Bottom right corner for me... I was able to calibrate around it but it took a few tries.
Sent from my Full Android on Vogue using XDA App
The sensitivity across my screen was inconsistent some time ago. I found that years of my abuse had taken a tole on the exterior of my phone. It eventually got worse and I bought a new housing (with a new digitizer) on ebay for a reasonable price. If it is hardware then it really isn't that hard to fix if you like taking things apart.
If you're sure that win mo accepts input from that part of the screen then nevermind my post. I would play with a painting app though and investigate the hardware further.
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
In any case, my investment in a hew housing was well worth it considering how modern my old phone has become thanks to the developers here.
gooph said:
I may be talking a little out my a$$ with this part but.. is it possible that in calibrating your screen the os may change it's settings on how hard you have to press and such also. that may be how you got it working.
Click to expand...
Click to collapse
In my case, no - when drawing a straight line down or across the screen, the line starts 'moving' away from the stylus (like the picture in the OP).
Gah... now it's shutting itself off randomly and the dead spot has grown. Not good at all.
Yeah, mine was better for a while then 'slid' again. I ended up swapping the digitizer with my other Vogue and things are back to normal.
Sent from my Full Android on Vogue using XDA App
I have another vogue, but am weary of doing anything like that. How hard was it to get done?
All you need to do is switch the front half of the housing rather than the digitizer itself- it's not hard. There's a teardown guide somewhere in the forum, Google Vogue teardown and it should be at the top.
Sent from my Full Android on Vogue using XDA App
The only thing that worries me is that my spare vogue exists because it was dropped in a muddy puddle. I'm hoping the water damage isn't too bad. Guess we'll just have to see.
it is really annoying
I have the exact same problem and I too thought it was a hardware issue till I saw this Thread. I was ignoring it till two days ago when it started really bugging me. Now, I don't even need to press any button and it automatically gets pressed around the curve and I have a google search box there, so it keeps on searching for eee or sss randomly and started draining my battery. Is there a proper fix for this?
I thought I'd chime in too... I could never seem to calibrate the touchscreen properly in either Android or Debian. Changing the screen resolution (i.e. msmfb scaling) seems to have no effect, whether it's 240x320 or 640x480. Any area within 5mm or so of the edges of the LCD will register as the edge, making "A" and several other keys on the virtual keyboard impossible to hit. Passing calibration values to the kernel didn't seem to fix anything, but it's possible I was using them the wrong way...
i have the same kind of problem on my Kaiser... i think its realted to hardware... either the housing or the digitizer...
I am experiencing the same problem on X10 mini pro. the same screen spot exactly, i have to try very hard to get z or x or shift to work. Sometimes when I try locking the screen and unlocking it back, it works.
update
so after a very long time with this problem i decided to change the digitizer and problem is gonne. visualy the broken digitizer had nothing wrong with it. The fix was fairly easy though, there is no glued parts involved into getting a new digitizer on the u20i.
Touch Screen
I just bought a brand new Cubot One and it looks more than perfect! It has just a little problem with the touch screen ( I think its the software, need ROM change). There is a dead line on the right side of the screen that touch doesn't work at all. Any solutions? Anyone faced that before? Can I fix it myself or do I have to send it back for replacement? Is there any video or guide that shows its done?
I uploaded a video on YouTube to show the problem but i cant post it yet.. (new member)
You can write "Cubot One touch screen problem" and it's the 1st one.
Thank You!
Hello Everyone,
I have been unable to find this information anywhere so I thought if anyone knows this would be a good spot for it. So a quick back story, my turbo took a dip in a hot tub for about 5 minutes. I put it in rice as quick as I could (about an hour) long story short it was completely dead unresponsive. I ended up doing a bunch of research and buying an ultrasonic cleaner, taking it apart and cleaning it soaking in 99% isopropyl. I did that several times and each time more functionality returned. At this point everything works perfectly other than wifi and bluetooth (presumably on the same chip). They are both permanently grayed out and cannot be turned on. I would like to know where physically the problem is before attempting anything further.
So can anyone point out the wifi, bluetooth and antenna for each on these pictures? I tried to post in pictures but it seems I cannot because I am a new user. I think you can copy and paste these into browser though or maybe someone else can post one in for reference. The first image is the back of the screen as well as the little cover that goes over the battery. The second is the motherboard.
granttrainingcenter.com/images/phone2.jpg
granttrainingcenter.com/images/phone1.jpg
Oh and while Im at it does anyone think there could be a software issue resulting from water damage like would I need to reflash some drivers or something?
All help is greatly appreciated!
Im going to try contacting motorola and ill update post if I have any luck
You should try flashing the software using rsd and doing a factory reset! Doubt Motorola will be of any help cuz u void the warranty when u take open ur phone and I don't think water damage comes under warranty!
Are you sure there is reason to believe this could be software related? I just finished rooting and getting everything set up, itd be a shame to start over.
Motorola was no help of course said its top secret. Is there no one out there with the electrical engineering or phone repair background to tell where the chip is from those pictures?
Nobody will know from those pictures - all of the IC's are hidden under the metal shields. Your best bet is to check out the FCC filing pictures of the phone, there should be some with the shields removed. If you can read any of the #'s start googling them.
Or find someone else who has taken high-res pictures with the shields removed, chances are they are out there.