GT-i9000 / broken screen/ stuck at on-screen keyboard settings - Galaxy S I9000 Q&A, Help & Troubleshooting

Hi,
My device(gti9000) screen broke. I managed to install Stock JVT 2.3.5 Gingerbread using ODIN.
Screen is beoken so to view screen on PC I have also installed VB application AndroidControl.exe which is working Fine.
Problem is that now I am stuck at on-screen keyboard settings as I have a broken phone screen. So can see the screen on PC. Have tried various methods using ADB like ADB shell input keyevents but still cannot bypass the on-screen keyboard settings.
Can someone guide how can I continue or skipt this setting through ADB. Have also used ADB shell PS and Kill commands to kill processes but got no success.
Any help would be appreciated.
Thanks

Are there any ADB commands that can send touch event to Android Phone.
I have managed to write text in the text box but cannot click or send click events using ADB.
Regards

Attaching Screenshot from my PC.

Hi
Are there any custom ROMs that I can install through ODIN or Recovery Mode where I do not need to enter any on scree settings through touch keypad and the phone boots directly bypassing all such settings.
Then I can use ANdroidControl application to control phone.
Am stuck as I cannot by any means skip this on-screen keyboard settings that I got after installing stock JVT using Odin.
Thanks

Ok, so this is what I have searched
The tool that I am using to view broken screen on pc is AndroidControl.exe and that uses commands that do not support shell commands on version 2.3.5. New shell commands for input tap were introduced after 2.3.5.
There are only 2 ways for me to move forward
1. If anyone can suggest a ROM above 2.3.5 with ODIN support can solve my purpose.
2. I can go into recovery mode. If there is a ROM that I can sideload by adb and is above 2.3.5 can also solve my purpose.
Please suggest.
Thanks

Hi,
I have been able to install ICS on my device.
I have also figured out a way to use Input Keyevent in ADB Shell and have managed to bypass initial screen setups. I can see my device on PC only as it has a broken screen.
I have also rooted my device.
All this would have been a cakewalk if my screen was working but accomplishing all this with a broken screen and AndroidControl is a different ball game.
GTi9000 is a very old device but I wanted to take it as a challenge. It definately made me dig through a lots of posts related to ADB, ROMs, JAVA, Shell Commands, Keyevents, Sendevents and lots more.
But I am still facing following issues
1. I cannot boot into recovery. Moment I boot into recovery using ADB it takes me to normal boot.
2. I want to install any ROM version above 4.1.1 but doing so the device bricks and then I have to downgrade to 2.3.5 and redo everything. I have tried numerous custom ROMs but all with fail.
Would be great if anyone can suggest way forward.
Thanks

Same problem with me

Related

[Q] flash captivate to stock Ubuntu live cd

I accidently flashed SRE 1.3.1c over the captivate hybrid ROM and after gettin the error message every boot i deleted all user data it now only boots to a black screen and i cant get in to clock work recovery because i left the update.zip in the root of my internal sd card so it keeps flashing SRE when i hit reinstall packages is there anyway i can save my captivate
so know i am stuck because the only OS i can currently run is a ubuntu live cd
anyone know a way?
if the phone is still booting at all (passing AT&T screen) you should be able to use adb. you can force and adb reboot recovery or download and use adb push to move the clockwork update.zip back and restore your nandroid. or download to restore to a stock JF6
if you aren't booting at all though, then the only way to restore is to go back to a stock build using Odin. I know you say you only have an Ubuntu Live CD, but that just won't cut it. To use Odin, unfortunately, you need Windows (though it will work inside virtualbox).
its booting past the at&t screen but im having some trouble with adb
rsmith675 said:
its booting past the at&t screen but im having some trouble with adb
Click to expand...
Click to collapse
sounds like Odin will be your easiest method to fix this. boot into download mode using the 3 button method and find a windows based computer
im using regular installed ubuntu now (no more cd) ive got odin running in wine but its not being recognized in either download or recovery
Last time I was on the Linux scene, Wine had some major problems with USB. Windows is your best bet. (You can find a copy somewhere of xp for pretty cheap these days)
One thing I would suggest, based on my past experience with jailbreaking iPhone:
When trying to connect to any device in recovery/download/whatever-non-normal mode, try to connect to OS directly. Do not use tools like vmware. These sometimes have difficulty in recognizing devices in virtual machines/modes.
My iPhone wasn't recognized even in XP virtual machine on top of Windows 7. Maybe the same thing applies here too.
Edit:
Keep following the thread below. One more user is trying to achieve what u r trying to do.
Code:
http://forum.xda-developers.com/showthread.php?t=922690

[Q] Flashing via Odin but using Terminal Emulator to access Download Mode ?!

I am using Terminal Emulator while key combination on my phone does not doing the job at all to access either Download Mode or Recovery / Update Zip etc. Apparently some devices has been blocked with this manual option.
I need flash my SGS, while after last update to Froyo 2.2.1 my WiFi is faulty and rebooting doesn't work properly a swell - needs 3 attempts to reboot it.
Did anyone try to flash SGS via Odin but using Terminal Emulator to access Download Mode successfully ?!
Need your support please, before trying and ending with a "brick".
Much appreciate for advice.
Cheers in advance!!!
soulflyer84
Couldn't you just do adb reboot download with the SDK? I'd check in the dev section, I'm pretty sure there are ways to update the sbl to enable the 3 button recovery/download modes. I'd get those working before messing around with flashing ROMs (through either official KIES or Odin for cooked roms)!!

[Q] Download Mode from MIUI

There should be a [NOOB] tag for forum posts...
I'm a long time windows mobile user, rather than jump into windows phone I'm making the switch to Android.
I bought my captivate on eBay, it shipped unlocked with a clean gingerbread rom. Not sure which. After reading through a number of threads and articles I was able to:
Setup ADB - Win7 x64
ADB to download mode, Odin 1-click back to stock
Flash CWM, again via ADB to recovery, and then flash the latest MIUI
3br does not seem to be working for me. At first I was able to get to recovery with Vol up + Home + plug into USB. I can no longer get to recovery or download mode at all. MIUI, has the reboot to Download/Recovery mode options, but neither work and just boot back to the OS. When plugged into my computer, the device drivers are not recognized. So it no longer works with ADB. I haven't been able to get the drivers re-installed. When I attempt to ADB, it says "Error: No device connected" (or along that wording). I tried installing the USB drivers straight from Samsung and the galaxy S x64 drivers posted online. Not having any luck.
I can't seem to find my answer searching the threads and web...maybe I'm not using the right terms (I avoided making a new post as long as I could). Everything else works fine otherwise, the phone isn't bricked...but where's the recovery? Any ideas?
I'm assuming if I can get into download mode, then I can Odin-1-click to stock and everything is peachy again? I'm not quite understanding the 3BR fix guides...I thought since I could get to recovery with other methods when I got the phone, that I was fine, but maybe that's my problem.
The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.
studacris said:
The combo is all 3 buttons for recovery and both volumes and plug in a usb fire download. Sometimes odin one click will disable the combo.
As for adb not working miui is an aosp (android open source project) build not based on samsung firmware so you need the google drivers installed for it to work.
Click to expand...
Click to collapse
It must have gotten disabled somehow then...
By Google drivers, you mean the USB package you can select from the Android SDK Manager? I didn't mention this but I think I tried those as well. But I'll remove everything I've installed, restart and try re-installing fresh to double-check.
Thanks for the suggestion, that worked with the drivers from the sdk. So if I end up flashing a touchwiz based rom, will I have to go back to the samsung drivers?
That's correct

[Q] Trying again: Rom with USB debugging set by default?

Hello,
I've got a stock Galaxy S ROM (factory reset - silly, don't ask) with a Speedmod Kernel and a broken screen. Do you know of a ROM (uploadable using ODIN) which turns USB debugging on by default?
Thanks in advance.
Dont know of a ROM that can do that but voodoo has a debug mode option. Its not the same as usb debug but maybe it will help. If you get into recovery i or someone else can give you directions (how many and which keypresses can get you to it) to activate it.
If your trying to access the device via ADB im fairly sure you can access it in recovery.
Why do you need debug mode? If its to replace the screen by Samsung I have read they don't care or look at the software, just replace it and see if it works..
Can't find much information about it, but it might just be a logging option rather than a control.
I haven't been able to access the device in recovery mode via ADB yet. Possibly missing recovery mode through improper key-press timing due to the broken screen, but not sure.
USB debugging enables control of the phone via the computer using ADB and utilities such as "Android Screencast".

[Q] Need help making Z with broken screen usable

I have a Z here with broken screen/digitizer. ADB is not enabled, I want to enable through any means and then config it via vnc or similar with the long term goal of turning it into a headless mediaplayer(xbmc).
I am able to control it using the painstaking method of plugging in a usb kbd or mouse, doing some blind movements and then swapping that out for an mhl/hdmi cable so I can see where I am at.
With that I have been able to disable the lock screen, start terminal emulator, get into developer options and some other things.
The phone had previously been rooted and had adb enabled but my SO had updated it to stock OTA 10.4.B.0.569 (4.3)before The Drop without my knowing so I lost both of those.
So, the problem...I cannot enable adb. I can get into the developer menu but the options are greyed out. I cannot select anything. I don't know why. I suspected it was because there was a usb device plugged in (either mouse/kbd or screen) but I have checked a Z tablet running 4.2 and a Z1, which is running 4.4.2 and you can enable usb debugging with a device plugged in on both those. I tried toggling dev options off/on, but no difference. Annoying.
Because I have lost root I cannot enable it via terminal either.
I unlocked the bootloader and installed a custom recovery (Advance Stock Kernel with Recovery v11 (FW:*10.4.B.0.569}*) from this this thread, linked from [HOW TO] Root 10.4.B.0.569 [ONLY UNLOCKED BOOTLOADER]
In doing this the phone was reset to defaults, but it made no difference to the Dev Options being disabled. I can get into it, but most options are still greyed out, so still no adb
So now I am stuck. With no screen, I have no idea what steps to take to flash the SuperSU zip file from recovery. This is where I need some help
I have no problem wiping the phone, installing custom roms etc. but I need to get root and adb working somehow.
Is there any reason why USB debugging, amongst others, in Developer Options might be disabled?
Possibly a permissions problem? Fixable without root?
Could someone running the same recovery possibly detail the steps needed using the hardware buttons (up, up, power, down, power, etc) to flash supersu so I can get root?
Assume blank external sdcard with only that zip on it
Could someone recommend a custom rom that is safe to install on that software version that has root and maybe adb enabled?
Would it be possible to flash that from fastboot?
afaik, only stock/signed roms can be installed that way?
If I got adb working, could I sideload a rom/zip from that recovery or another non-touch recovery(swipe to proceed is definately out)?
Does anyone have any suggestions, ideas or alternative methods to attempt, in order to get control over the device?
thanks in advance to anyone that can help!

Categories

Resources