It says only ipl 2.25.0001 and spl 2.25.0001
I try a hard reset, but when it asks me to confirm by pressing SEND, I press SEND and nothing happens.. press any key and nothing happens, just sits there saying press SEND to confirm...
I tried flashing Cingular/AT&T's rom on to it, it was successful on the screen, but after rebooting, just went back into the 3 color screen...
Does anyone have any suggestions?
Additional info
I just wanted to add, I have searched threads here on xda-dev and other sites, and have found similar issues - normally the other issues have been resolved in one way or another involving a hard reset, which my phone will not complete. When it asks me to press send, the phone freezes at that point and does not accept any key entries (except reset). I would really appreciate any input. I also have a theory-that I may attempt this evening-If you hold the camera button down and reset, it brings up the boot loader screen (if my information is correct)... could my problem be caused by a faulty camera button? Maybe internally the button is remaining closed, which could prevent it from doing anything on a reset outside of the boot screen? Any engineers around that may know this? I am going to attempt (hopefully with low heat) to remove the button this evening... possibly even repair or replace it if the phone works with the button removed...(these thoughts are based on my phone being dropped in the sand at the beach...maybe a grain of sand worked it's way into the camera's button housing and is holding the contact closed)
problem's almost fixed
well thanks for no advice... i desoldered and removed the camera button (button 3). powered it on and the phone works. I reprogrammed the camera to button 5. (i also loaded a new WM6 rom and some other stuff) The last time I opened up the phone, I broke the itsy bitsy super micro tiny lock on the keyboard ribbon cable socket... so now my slide out keyboard doesn't work. I installed a full screen keyboard and set it to the messaging button (button 1) - the messaging button still brings up messaging with just a touch, but a long hold brings up a full screen touch keyboard that works fantastically!!! I am going to dismantle the very tiny micro switch and repair it, then resolder it back on the mainboard to make my camera work like it should again...and find a way to get the keyboard ribbon cable to lock into the socket...then my phone will be as good as new!
umm... thanks???
well congratulations on getting it working again.
tiny switch
I have taken the tiny little switch apart without breaking anything... one tiny grain of sand stuck under the button pressing on the switch plate... now i have to find a way to put the little switch back together... then attempt to solder it back onto the board without over heating nearby components. I have been playing around with Byka's cube... took a bit of tweaking to get it to work well.... not sure if I want to keep it or not... I have been trying to find htc cube, but no luck outside of a rom... which I may consider...but I just spent the past week reinstalling all of the software I use... Would like to just design my own windows for my phone if I had the time... Been working on an ion motor for an electric car...
I would like to thank everyone here at xda-dev. for all the information. Could not have learned so much, so quickly, if it weren't for this site.
oh... and I am using an 8125 (G4) with Faria Crossbow
Have the same problem...
Hi!
I have the same problem (but I don't have much tech know how).
It all started when phone got wet (inc. in battery compartment).
My phone would not soft reset beyond the Bootloader, unless I leave the battery out for a few hours. Then once it loads up, after a short amount of usage 2 things happen: 1) every time I would turn it on (or get a call) it starts in Camera (you didn't report it but you must have had the same experience). 2) the buttons don't work properly.
It finally dawned on me the camera button might be stuck, I set the button to "none", and no more more automatic camera. I still need to free the button altogether as still causing button freezeup and also allow soft resets.
I don't know much about soldering.
Any ideas?
Thanks
Phone works and everything but the touch screen is not responsive.
Does anyone know how to call up the "Start" menu just using the keyboard?
or
How to press "Send" using just the keyboard for SMS msg?
Thanks in advance!
I'm not sure that it is possible. this has happened twice to me* (see below) and those were the only 2 things that I could not do. you can go to the program tab to the far right and start any programs you may still be able to use...
*I've had this happen to 2 of my touch pros...What I was told by a rep was there is a small plastic tab on the back of your screen. If you look on your phone where the volume buttons are...opposite side. That small plastic tab should be removed because this rubs against some connector inside the phone that causes the touch screen to die. soooo long story short you'll need to take it in and get it replaced
Sort of the same issue:
I've got a stock ROM, PhoneAlarm (latest beta) and a few other applications installed on this device, only recently has it caused me as much of a hassle as it has. I get a phone call and no matter if I press the softkey "Answer" button or the answer button on the bottom left below the jogdial, NOTHING picks up a call. Sometimes if I stab at it wildly enough it answers and immediately places a call within a call which means I can't get back to the original one i answered. It's frustrating and really annoying.
@sanjsrik - I'm having the same issue.
Using a Sprint issued TouchPro. Along with the 'Answer' issues, I'm also having problems with the screen jogging around. When I go into applications or the phone keypad, the screen is skewed, however if I touch the screen (in the correct spot), the correct command happens. For example, if my keypad screen is skewed (which only happens sporadically), it shows the '7' where the '9' should be and if I touch the screen there, the '9' correctly apprears. I plan to take the phone to Sprint either tomorrow or next and hopefully will have a clearer verdict.
Stock ROM
Apps:
Adv Config Tool
Google Maps
Facebook
Skype
TinyTwitter
"How do I make a permanent change to my Streak's touchscreen's 'Interrupt Method' setting?"
US Beta device: Can't get into proper fastboot mode -second fastboot screen, and screen calibration is messed up unless I use the EMlist utility to temporarily change the "Interrup Method".
I wrote the following in another thread, where I was also emphasizing a touchscreen calibration problem that plagues me during normal use of the OS.
Question #1: Does anyone know a workaround for this "un-clickable" Fastboot screen area that must be clicked on to get into fastboot mode and flash a new ROM?
Question #2: Does Anyone know what settings will allow me to keep the screen configuration set to "SensePeriodical"?
##########
*Issue #1*
##########
The main point for posting this as a new topic is summed up by the sentence: "The area of the screen with an unbounded word "FastBoot" has not been clickable at all."
After booting while holding down the UP/DOWN volume buttons, I get the following.
I see only:
1. (Top Left) "Touch Calibration"
2. (Top Right) "FastBoot"
3. (Bottom Left) "Press:"
4. (Bottom Right) --Phone keypad with numeric buttons and the two labels "CLS" and "Enter" on their own buttons.
The area of the screen with an unbounded word "FastBoot" has not been clickable at all.
The first time I tried to boot into fastboot this way, these things appeared and then I attempted to use the numeric keypad --and each attempt failed, printing the wrong character. When I pressed "1", then for example, the number "6" would appear.
I then pressed the top volume button and the screen went dark. After ~3 seconds, the screen was repopulated identically, *except* for the word "FAIL" beneath the "Touch Calibration" on the top left.
I then retried without rebooting. This time, all my keypresses were accurate. I pressed the top volume button again, and the screen went dark again. The same display reappeared, along with the word "FAIL" in red beneath "Touch Calibration".
I then rebooted into fastboot again --but this time, all of my key-presses were accurate the first time. I filled up the 10 characters of space after the "Press" item on the bottom left by pressing the number pad buttons in sequence. I then pressed the top volume button, but then got the red "FAIL" when the screen came back on.
This phone was rooted (at least) once, then updated to 2.1, then (I believe) flashed with a 1.6 image. After the first aforementioned update, wiped with a factory reset.
##########
*Issue #2
##########
Touch screen mis-calibration problems were reported/observed after the first manual ROM flash. That has still been a problem for me since acquiring the Streak, and the only workaround I have yet found is a temporary adjustment using one of the engineering tools beneath the Eng. menu item "EMlist". This workaround is only functional until the screen goes to sleep, and then I get the same behavior from the touchscreen that forces me to trickily press items quickly or in a swiping motion, which is maddeningly inefficient.
Here is that little "procedure", as I typed it up:
################################
1. Enable Engineering apps by dialing *#*#307#*#* into the Phone Keypad.
2. In Application drawer, Go to "EMlist"
3. In "EMlist", go to "Touch Panel".
4. In "TouchPanel", go to "Configuration"
5. In "Configuration", under "Interrupt Mode", I changed the selected radio button from "CoordinateCompare" to "SensePeriodical" --and the keyboard began to behave as I'd hope, with no trace of the difficulties before. However, upon opening that applet up to this point, I observed that the value had reset itself to "CoordinateCompare". There is apparently an "OK" button below there that needs to be pressed in order to save the Configuration change. However, upon reboot, the same old problems reappeared, and the setting had reverted to "CoordinateCompare". There must be a way to hard code this setting, but I'm not sure just where.
################################
Does Anyone know what settings will allow me to keep the screen configuration set to "SensePeriodical"?
The speculation from the last owner is that this may be hardware failure in the digitizer, which would kind of stink because I can't get Dell to fix or trade out this device from the Texas beta program.
I'm really hoping that this is a software issue, especially seeing how changing from the "CoordinateCompare" Touchpanel Configuration setting solves the main problem 100%, if only temporarily.
I'd love to get more input or feedback about this problem, and I also hope that this post of mine helps someone else make shareable progress.
Sounds like a hardware issue to me. Can it be sent back for repair?
Sent from my Dell Streak using XDA App
It cannot be sent back for repair since it is a Beta hardware model.
If it be a hardware problem, then it's really kind of odd that the change in sensory detection or interpretation makes a 100% improvement. The "Interrupt Methd" should not be able to correct a hardware problem that would otherwise be really pervasive, don't you think?
I reallyy appreciate the feedback!
I think that the most important question for me and my little orphan is: "How do I make a permanent change to my Streak's 'interrupt Method'?" If it can be done satisfactorily with the utility in question, then where is the configuration file (in /etc, I'd imagine) where I can manipulate it?
Everything in the running GUI environment for the touchscreen is made better by this adjustment, but I don't know how to make it a persistent configuration change rather than a temporary one (and it is temporary when I change it with 'Emlist', reverting when the screen goes to sleep),
On top of that, I'm getting USB errors --oh, nevermind.
I have observed in my gnu-linux syslog that I'm getting:
###########################################
Sep 21 21:00:50 $HOST kernel: usb 2-2: new high speed USB device using ehci_hcd and address 4
Sep 21 21:00:55 $HOST kernel: usb 2-2: device descriptor read/64, error -71
###########################################
...from the Streak when on the first FastBoot screen.
EDIT: Nevermind --My USB connection has been fine for ADB operations, so this is of no consequence.
I had this problem, such that the device was essentially unusable. Dell replaced my phone. I've seen on various forums that a number of people have this- hopefully Dell gets a fix for it.
Sounds like you took a spin on the Beta roulette wheel and lost. Sucks to be you, but youre not the only one, if it makes you feel better.
Sent from my Dell Streak using XDA App
johnh123 said:
I had this problem, such that the device was essentially unusable. Dell replaced my phone. I've seen on various forums that a number of people have this- hopefully Dell gets a fix for it.
Click to expand...
Click to collapse
Do you mean that you had a USB problem or the Calibrate Screen problem?
My USB connection has been fine for ADB operations.
I have just noted that my first FastBoot screen lacks the border of dashes that can be seen at 01:58 of this HOWTO video: http://www.youtube.com/watch?v=vDXH17USk-g . I have never gotten a glimpse of the screen that appears at 01:31 of the video.
The FastBoot item on the first fastboot screen is not clickable, no matter how hard I press or how widely I go for a click/press.
This makes me think that the FastBoot "problem" may not be intrinsically related to the touchscreen's problem.
Any ideas? I am starving for ideas, especially since I just tried to use 'flash_image boot.img' from a Modaco recipe, which has left me unable to access the OS.
Also, there is no ADB access from the Dell recovery console. Is that true of all these Streaks? All I've ever gotten while in that recovery mode is "Device not found".
I had the calibration issue.
philverb, try a screen calibration, that might help.
johnh123 said:
I had the calibration issue.
philverb, try a screen calibration, that might help.
Click to expand...
Click to collapse
I tried to take note in the OP that screen calibration actions in the Recovery Console and in the first screen of FastBoot do not work, failing with a big, red-lettered "FAIL".
Did you have something else in mind?
Maybe. I don't get the fastboot screen when I power up with both volume buttons pressed. I get a different screen, which has a couple options including screen calibration, but not fastboot. After calibrating there, you may have some luck.
Sent from my Dell Streak using XDA App
johnh123 said:
Maybe. I don't get the fastboot screen when I power up with both volume buttons pressed. I get a different screen, which has a couple options including screen calibration, but not fastboot. After calibrating there, you may have some luck.
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
There are two things here: the Recovery Console and the Fastboot Console/Screens.
Recovery Screen: hold down both volume buttons while powering up. You then get a menu of Four items:
1. Factory Reset
2. Software upgrade via Update.zip on SD Card
3. Screen calibration
4. Power off
--The Screen calibration has its own contextual instruction screen that indicates to "Press volume down key to calibration screen, Press camera key to exit." [grammatical errors not mine]
**This screen calibration for me fails with "FAIL" in red letters, no matter how many times I try.**
FastBoot Screen: hold down Camera button while powering up. This is where, as I have said a couple of times, the word "FastBoot" appears in the top right, but it is not surrounded by dashes as it is in the video I mentioned ( http://www.youtube.com/watch?v=vDXH17USk-g) at 01:58 of the video. It is the missing dashes that appear to define that "FastBoot" area as a button. In my version of the bootloader/fastboot thing, that area appears just to be a "dummy" area and intended not to be a clickable button.
--There is also a non-clickable area labeled "Touch calibration" in the top left screen, and I can activate it by using the left-hand volume button.
**When activated, this function makes the screen go dark, then returns to the original screen (also described in great detail in the original post), but then has the word "FAIL" in letters highlighted in red.
I really do appreciate your interest, and I hope that it doesn't seem tedious that I repeat myself in order to try to clarify, since you seemed to have gotten the wrong idea from the laborious detail I threw into the original post.
I think that what you have just mentioned is included in what I've been saying I have seen, no?
Thanks!
Did you tried opening the streak and reseating the touch panel cable? When I opened my streak just to check it out I saw a finger print in the camera connector, that made me think that MAYBE some wires weren't fitting 100%. Just a tought.
Good thinking....
BrokenPixel said:
Did you tried opening the streak and reseating the touch panel cable? When I opened my streak just to check it out I saw a finger print in the camera connector, that made me think that MAYBE some wires weren't fitting 100%. Just a tought.
Click to expand...
Click to collapse
That's a strong thought, and I thank you for it. My phone is (semi) bricked at the moment I am wondering now about the question of whether or not the screen problem may itself be preventing the FastBoot GUI from creating the border and therefore a clickable button.
I never get the the button border that is visible at 01:58 of the video at http://www.youtube.com/watch?v=vDXH17USk-g .
What do you think?
I have a galaxy s2 running ICS (but the issue occurred) and I have a very odd issue with the keyboard that I am hoping someone could help me with. I have searched around but did not find anything already posted.
A short while ago, my screen broke and I had it replaced, good as new. Well almost. When ever I use the messaging app, or another type of app like that (Whats App for example), when you are composing a new message, and the textbox is shrunk down to one line at the bottom of the screen, there appears to be no input detected on that part of the screen, the send button (on the right hand side) works, and the other controls all work fine, just not the textbox.
So I figured that when the screen broke, it messed up that part of the screen, but other apps that have controls in that region (such as the camera app that has the photo button, or the lock screen with the emergency call button) all work 100%.
Its just textboxes at the bottom of the screen that do not seem to accept touch events. VERY odd.
Has anyone seen this before or know of a few tests/checks I can do. I am a new-ish user to Android.
xkram said:
I have a galaxy s2 running ICS (but the issue occurred) and I have a very odd issue with the keyboard that I am hoping someone could help me with. I have searched around but did not find anything already posted.
A short while ago, my screen broke and I had it replaced, good as new. Well almost. When ever I use the messaging app, or another type of app like that (Whats App for example), when you are composing a new message, and the textbox is shrunk down to one line at the bottom of the screen, there appears to be no input detected on that part of the screen, the send button (on the right hand side) works, and the other controls all work fine, just not the textbox.
So I figured that when the screen broke, it messed up that part of the screen, but other apps that have controls in that region (such as the camera app that has the photo button, or the lock screen with the emergency call button) all work 100%.
Its just textboxes at the bottom of the screen that do not seem to accept touch events. VERY odd.
Has anyone seen this before or know of a few tests/checks I can do. I am a new-ish user to Android.
Click to expand...
Click to collapse
This really sounds anoying but i know several issues quiet close to yours.
For instance sometimes on my sgs+ one side of the screen....in many cases the top side does not recognize any touching by me...
after loocking and afterwards aunlocking the phone everythings allright again...
i would suggest you to try to install a thirdparty keyboard from the play store.
if this doenstn work.....well maybee try another rom but i would send it to samsung to get a new phone...cus errors caused by wrong placed hardware are always comming back
fare well my friend
My tablet is HKC P077A with 8GB ROM, 512 RAM and a 7'' Touch screen (Android 4.0.3). I am having 2 problems
When I switch on the tab, first "HKC" logo comes to screen and then disappears to show "android". This is standard. But after that the thing wont move forward. Just keeps on showing "andriod" with a flashing like thing implying the loading process. But after long wait there is no start screen and nothing changes. It just hangs there....
But if somehow got it to get into normal working(I donno how, but It sometimes boots ok and gets into normal working mode, with home screen and apps and everything). So once I get it right the other problem I am having is that the touch is giving VERY bad response. I have to click at spots multiple times to select that thing. Also the response is very slow. Its like the tablet is hanged. But when I tried connecting a mouse (through OTG) and everything works fine again. Is my touchscreen gone bad..??
I am already done with, reset (from "settings> backup and reset") [I cant find how to do factory reset on this model from "off" state(read below)]
I have tried to get into reset screen by pushing "Power Button+Vol up" button. Then I know the tab gets turned on (I can hear a small white noise from the loudspeaker) but nothing comes to screen. So the "Robot with heart open" is never shown. I also tried using "power button + Volume down", this takes me to a screen written in chinese. Now, I don't know Chinese but from the look and feel, its a troubleshooting window, where I can check weather components of my tablet are working (eg. I click one menu(with difficulty), then the front cam turns on, another menu makes loud sounds from speaker and another flashes many colors in screen etc). I found that most are ok except something called "T" (On the screen, its the last item to the right, is it "touchscreen"??)
So, what can I do to get my tab to work smooth again..? Is the touchpad having trouble..? Need I do any specific troubleshooting..?? Any Ideas on which key combinations to get on to the "factory reset" menu from off state..??
Also can u please specify the key combinations to the tablet factory-reset menu from "off" state.