yashsingh1/xdaforums huggingface dataset:
[Hardware Hacking General] gblues:
Thanks for the link. I managed to figure out the correct "orient" value by trial-and-error, but the screen alignment is screwed up. On a stock kernel, the top-left is 0,0. On a compiled kernel, top-left doesn't even register properly (none of the edges do). I've tried a few experimental things but nothing helped so far. I'll check out that link when I get home and hopefully find something useful.
[Hardware Hacking General] Rebellos:
You might also want to look into mach_aries.c and mach_herring.c files from I9000 and I9020 kernel sources. These shows pretty good how very similiar results can be done in pretty different set of T9 parameters.
[Hardware Hacking General] gblues:
I appreciate your input. I'm experimenting with different T9 values. I found a partial datasheet that shed a little light into some of the parameters.

I've managed to strip out the "piggy" (uncompressed vmlinux) from the stock kernel. Is there anything I can do with that to somehow find out what T9 parameters are used by the actual stock kernel (as opposed to what Samsung released)? I did some searching for kernel disassembly but didn't find anything that looked promising.
[Hardware Hacking General] Rebellos:
Can you upload it somewhere? I'd take a look into it.
[Hardware Hacking General] gblues:
Sure thing. I'll upload it tonight when I get home. Thanks!
[Hardware Hacking General] gblues:
Here it is, gzipped:

http://min.us/mrUKEtr7W
[Hardware Hacking General] Rebellos:
Thanks, one more request - could you also upload .map file generated during your kernel compilation? I don't remember what was the full name of it, AFAIR it's ~70meg textfile in kernel source root or arch/arm/bin dir. Not sure though.

Also, are sources for this kernel available on github somewhere? Downloading tarball but this will take few hours more. :\

Ty in advance.
[Hardware Hacking General] gblues:
It's not on github at the moment. I'm just working from the kernel sources posted on opensource.samsung.com for the SGH-T589. I'll start an account tonight when I get home and upload what I have. I'll get the map file you're after uploaded too.
[Hardware Hacking General] gblues:
I've uploaded the stock codebase (no modifications yet): http://github.com/gblues/samsung-gravity-smart-froyo

I'm working on a commit that adds a few dummy directories so that 'make distclean' works, and the tweaked ATMEL MaxTouch driver. The ATMEL driver is in drivers/input/touchscreen/mXT140.c

EDIT: I've committed the dummy directories and the tweaked mXT140.c driver.
[Hardware Hacking General] gblues:
The only relevant .map file I found is the System.map which isn't 70mb, only 1.2mb, but I think it's the file you're looking for. Here's the link:

http://minus.com/lXdzy2QcuowxT
[Hardware Hacking General] Rebellos:
Entrypoint of piggy is 0xc0008000

0xC048D4D8 - qt602240_ts_init - this is first mxt init call, gonna extract init table later
[Hardware Hacking General] Rebellos:
Aww, that driver is kinda different. There's error message in that piggy

"[TSP][ERROR] line 1347"

while in your github equivalent line is

https://github.com/gblues/samsung-g...34/drivers/input/touchscreen/mXT140_ts.c#L973

Anyway I'm uploading my .IDB, you can open it with IDA 6.1+

https://dl.dropbox.com/u/32145655/piggy.idb (should be downloadable about 11:00AM CET)

Parameters settings is hidden somewhere in "quantum_touch_probe" function - marked it there.

BUT I just found out that there's such line in driver source

set_write_show does dump whole table of parameters to kernel log (dmesg), just not sure how to execute read function on device attribute. I'm linux newb. But I'm sure you can google for it. :P So I'm nearly sure you don't need any reversing to get proper parameter table. :)
[Hardware Hacking General] E:V:A:
"I would like the General Gau's Chicken, please, and wonton soup."

WTF!

Edit: I found that string in the piggy file...among with many other similar and irrelevant strings...
[Hardware Hacking General] gblues:
:confused:

The zImage format contains a decompression stub combined with the gzipped vmlinux kernel, called "piggy". The file I uploaded was the uncompressed vmlinux kernel I pulled out of the phone's zImage contained in its boot.img.
[Hardware Hacking General] Rebellos:
Okay, I've identified "config_all" structure there and added some anonymous variables to fit offsets. I still think you should mail them with request to release updated sources.

config param settings starts there - 0xC02DE5F0

Remember to care for conditional instructions and consider that GCC optimization can be nasty.

header file with modified config_all structure to fit disassembly is attached in zip I'm not 100% sure it's right but should be.

Should be downloadable in about 15mins from posting.

https://dl.dropbox.com/u/32145655/SGH-T589.zip

If you need any more help leave me a message or post here.
[Hardware Hacking General] AdamOutler:
Hey, if you are still interested in finding the UART, I could help. This board seems vaguely familiar..

I'd like to see the same picture you took here... http://dl.xda-developers.com/attach...6caf8195/4ff2d9a1/1/0/7/5/9/2/7/t589-jtag.jpg But do it again with light BLASTING on it. then do the other side.

Another option is to use external UART.. 619kohm resistor in the USB port Pins 4-5 and read RX/TX from pins 2-3.

If you're still interested in locating the UART I can help though.
[Hardware Hacking General] gblues:
Yeah, I'm interested. I didn't actually take that other picture, I borrowed it from the FCC's website. But I have one disassembled that I can take pictures of at home. :) And this is actually great timing, because we just fixed our digital camera so I actually have something to take pictures with other than the camera's crappy phone. I'll upload the pics tonight.

I have the parts I need for the external UART, but I'd still like to locate/use the internal one in case I need it.
[Hardware Hacking General] gblues:
Here are the photos. They're very high resolution and saved at JPEG level 10 to minimize DCT artifacting. If they look kind of funny it's because I used Photoshop to stitch them together and the perspective correction can look a little funky.

http://minus.com/lS0Odm7prEcTF
[Hardware Hacking General] AdamOutler:
Maaaan. I'm not signing up to view pictures. Post them on g+, photo bucket, tiny pic, picasa or anywhere else a sign in is not required.
[Hardware Hacking General] gblues:
Alrighty. I'll use G+ since you should be able to get the full-size pic out of it pretty easily:

https://plus.google.com/photos/103303068617595329719/albums/5761199671932903937
[Hardware Hacking General] gblues:
I did try to contact Samsung. They just replied and tried to tell me the touchscreen driver was correct. I've replied and let them know that their source release is broken out-of-the-box and we'll see where we get. I don't have my hopes up. :p
[Hardware Hacking General] AdamOutler:
The areas in green are where I would look for UART at 115200 8N1. The arrows are where I would try first.
[Hardware Hacking General] Rebellos:
Anyway, using IDB I uploaded, you can really easy compare all values set by piggy's quantum_touch_probe with the one you got in sourcefile. :)

(Tip: Use H/Q keys to switch between dec and hex view of constants)
[Hardware Hacking General] gblues:
Hmm, something isn't working right.. I think the resistor is working because the phone boots when I plug in the jig, but I'm not having any luck reading the COM port at either 19200 or 115200 8N1. I think my soldering is FUBAR. Gonna have to check tomorrow with a voltmeter.

Here's an overview of how I have things wired together:

USB:ID -> 619Kohm resistor -> USB:GND
USB:D+ -> FTDI:RX
USB:D- -> FTDI:TX
[Hardware Hacking General] gblues:
Well, my soldering seems to be OK. I'm at a loss why it isn't working. I'll post as much detail as I can, and hopefully someone can point out what I've done wrong.

Parts used: microUSB breakout, FTDI Friend, 619K resistor, 6-pin breadboard adapter for the FTDI friend, wires.

- I cut the 6-pin adapter into individual pieces, and soldered 3 to the breakout board (D-, D+, Vcc).

- I soldered my 619K resistor between ID and GND on the breakout board.

- I cut my wires to be about 5" long (probably closer to 5.5").

- I soldered one end of the wires to the pieces soldered to the breakout board, and the other end to another of the cut adapter

- I plugged the wire connected to D+ to the RX input on the FTDI friend

- I plugged the wire connected to D- to the TX input on the FTDI friend

- I connected the FTDI friend to my PC. Windows loaded the driver and created a com port (COM16)

- I used a terminal emulator (tried both SecureCRT and PuTTY) to connect to COM16 at both 115200/8/n/1 and 19200/8/n/1

- I powered down the phone and connected the breakout to the phone

Result:

The phone boots as soon as the breakout is plugged in, which at least tells me that the resistor is working. But I don't get any output on the terminal emulator.

Other things I've checked:

- The FTDI friend came pre-configured for 3.3v data lines. I've reconfigured for 5v data lines with no result.

- I've gone into the phone diagnostic menu (*#197328640#) and changed Common > Diag Config and tried with it set to both "USB" and "UART"

- I used my voltmeter to confirm there are no shorts in my soldering.
[Hardware Hacking General] gblues:
One thing I noticed is that when the phone boots with the jig connected, the dmesg output is much more verbose. I was just looking through it, and I think I know what step I missed--I need to actually redirect the kernel output to the MSM port! I think I know which devices to use:

<6>[ 1.729463] msm_serial: driver initialized
<6>[ 1.729770] msm_serial_hs.0: ttyHS0 at MMIO 0xa0200000 (irq = 45) is a MSM HS UART
<6>[ 1.730388] msm_serial_hs.1: ttyHS1 at MMIO 0xa0300000 (irq = 52) is a MSM HS UART
<6>[ 1.731000] msm_serial_hs module loaded

The full dmesg output is attached for the curious.
[Hardware Hacking General] gblues:
Hrm. Still having trouble. I noticed in the first dmesg output, I saw the line:

<5>[ 0.000000] Kernel command line: mem=330M console=NULL hw=4 fbaddr=0xb5000

Later, in the kernel where I attempted to set the console via mkbootimg, I checked dmesg output and noticed this:

<5>[ 0.000000] Kernel command line: mem=330M console=NULL hw=4 fbaddr=0xb5000

It ignored my command line! I expect that the commandline specified in the boot.img can only expand--not override--what's provided by the bootloader. Which means... hacking the bootloader.

I've dumped the bootloader successfully already. What would be the best approach? I'm thinking of looking for the "console=NULL" string and replacing it with spaces, then reflashing. Would that work?
[Hardware Hacking General] E:V:A:
If this device uses the param.blk in /mnt/.lfs/param.blk you can use the sblParam (search for it) tool to change you kernel command line. Otherwise you proably need to flash a hacked kernel.
[Hardware Hacking General] gblues:
No dice on /mnt/.lfs/param.blk.

I know exactly where the kernel command line is--it's in the arm11boot partition. Interestingly, there's also a string for 'console=ttyMSM2,115200' but I've no idea how to get the phone to actually use it.
[Hardware Hacking General] gblues:
Well, I came home the other day to find out my broken phone I planned to use for dev purposes had been fully destroyed, and crucial parts were missing. Today, I found the parts, and was at least able to boot the phone in download mode. Since it was 90% destroyed anyway, I tried flashing my hacked arm11boot.img (replaced "console=NULL" with spaces) and it bricked. :( So at least that method is not going to work.
[Hardware Hacking General] njnken:
Sorry about your phone bro. :thumbdown:
[Hardware Hacking General] gblues:
No worries, my day-to-day phone is fine, it's just my mostly-dead phone (that's already been replaced) that is now all-dead. And it doesn't even have any pockets for me to check for change. :(
[Hardware Hacking General] kachman:
hi gblues and others, I have a jtag box and 2 samsung t589 phones, if u need me to read anything from it, i will help. i am 50% new to jtagging though (android). So i might need directions here and there.

I bought the jtag to try and unlock the 2100mhz 3G one of my T589, and to unbrick my other one.

Both of my phones have faulty touch screens. So i can't test anything once the phone is up and running, but i guess jtag operations wont need touch screen.
[Hardware Hacking General] E:V:A:
It's hard to help you, when you're not being very specific. What crucial parts are missing? And why would you replace the "console=" with empty spaces?? Do you have the slightest idea of what you're doing? (or even want to do?) Since it was alble to run boot sequence it is probably not hard bricked (physically broken) and you should be able to recover...
[Hardware Hacking General] blala:
I have here a similar phone, with the same MSM7227 board.

It's a almost-bricked Samsung Galaxy S5570.

Could someone help me with UART on this phone? With USB Jig i just get AST-POWERON.

Here you can find some photos of the board.

http://dl.dropbox.com/u/7341950/S5770-MSM7227.zip

Thank you very much in advance
[Hardware Hacking General] kachman:
is this any use?
[Hardware Hacking General] gblues:
Sorry, that was more of a status update than a particular request for help. The ribbon cable between the mainboard and the display/touchscreen got cut, making it nearly impossible to keep the battery connected to the mainboard. Since my project phone was on its last legs, I decided to sacrifice it on an experiment that ultimately failed.

From my log file analysis, I believe the reason I am not getting any output from my makeshift cable is because the kernel isn't directing its output to the external UART at all--instead it's going to /dev/null. To test that hypothesis, I attempted to blank out the unwanted kernel boot parameter in order to allow the parameters set in the boot.img to take effect, and it... didn't work. But since my project phone was already damaged beyond use it wasn't a huge loss.

For now, I'm stuck with trying to find an alternate means of enabling UART output without firmware hacks.
[Defy Q&A, Help & Troubleshooting] syedimty:
Hi Guys,

I own a defy +,

Here are some details

Android Version : 2.3.6

Kernel Version : 2.6.32.9-gbdd614e

Problem :

When i try i install any custom roms, i am getting boot loader err. But i was successful in installing CM7 but i am unable unable to install other custom roms.

Actually the roms gets installed but when i try to boot for the first time i always get bootloader error.
[Defy Q&A, Help & Troubleshooting] jalal-jap:
Did u Flash Kernel?

make fixed SBF From Ur Stock SBF.(moto andriod depacker-Delet CG31 And CG39)

and flash Fixed SBF With RsdLite.
[Defy Q&A, Help & Troubleshooting] Vicsa:
Yes, it looks like sbf mismatch. See this guide for defy+. You can also try to flash a nandroid backup like this one
[Defy Q&A, Help & Troubleshooting] syedimty:
Thanks for your help guys, but i understand very little.

I have a nandroid backup, whenever i get bootloader error,i usually flash a Stock SBF then i will restore my phone using the nandroid backup.

Can you guys guide me how to install CM9 on my defy plus.

I flashed CM9 rom and i have also flashed CM9 kernel for gb but i am still getting bootloader error. Where i have went wrong

What is mean by SBF mismatch??
[Defy Q&A, Help & Troubleshooting] jalal-jap:
flash stock SBF.

Root

flash CM9 For DEFY+ .

DONT FLASH ANY KERNEL.
[Defy Q&A, Help & Troubleshooting] Vicsa:
Just follow this instructions carefully. Common mistake is that you forget to wipe cache and data. So, wipe cache and data, and reboot. First boot takes longer (about 10 minutes). Good luck.
[Defy Q&A, Help & Troubleshooting] syedimty:
Thanks guys, i successfully installed CM9.

But , can one suggest me ROM for my defy plus, which gives good performance and also stable. ??
[HTC Sensation] D_avi_D:
I got my HTC Sensation, it was already upgraded to the official ICS, everything works except bluetooth. When I try to start bluetooth it just says "Turning bluetooth on" and stays like that for about 10 seconds and nothing happens. Is there any fix for this?
[HTC Sensation] Macklessdaddy:
reboot the phone,I think this is a ICS glitch because it happens on every rom I have tried.
[HTC Sensation] D_avi_D:
I did as you said, but still nothing. i.imgur. com/8bBhf.png
[HTC Sensation] Rumball:
Have you been flashing any radios?
[HTC Sensation] D_avi_D:
I have no idea, I just bought the phone and it had ICS in it... when I turn the phone on it says swisscom... The phone is not even rooted.
[HTC Sensation] KAwAtA:
Swisscom?
[HTC Sensation] D_avi_D:
shop.swisscom. ch/Onlineshop/Pages/ProductDetail/ProductDetail.aspx?cat=OS_Mobilkommunikation&subcat=OS_Mobiles_Internet&lang=EN&id=000000000010039811
[HTC Sensation] Rumball:
I would return it. Could be a hardware issue if the phone isn't rooted /running a custom ROM
[HTC Sensation] D_avi_D:
Alright, thanks for the help!
[Samsung Galaxy Fit GT 5670] Arjun kar:
can someone give me the link for xloud for our phone ??:rolleyes:
[Samsung Galaxy Fit GT 5670] sj1021:
Bravia Engine + xLoud

http://xdaforums.com/showthread.php?t=1653244

one more link

http://xdaforums.com/showthread.php?t=1441470

:)
[Samsung Galaxy Fit GT 5670] Arjun kar:
thnks a lot :)
[AT&T Samsung Galaxy Note I717] easybucketz:
Hey i wanted to know if someone could get the Asus Transformer Prime App called SuperNote to work on the Note.
[AT&T Samsung Galaxy Note I717] hashbrown:
http://xdaforums.com/showthread.php?t=1556565

Next time search,

You'll have to be on ICS to use though.
[AT&T Samsung Galaxy Note I717] assaace:
Is this note has eraser function?

I can't find it.
[AT&T Samsung Galaxy Note I717] ndfan4u:
I installed and it f/c on me. I am running latest ICS leak.
[AT&T Samsung Galaxy Note I717] dincdoes.me:
You need correct lib files for this phone had the same problem on Acer iconia a500 once you get the lib files though works great
[AT&T Samsung Galaxy Note I717] omar322:
Excellent
[HTC EVO 3D] frexe:
I recently downgraded to 1.4 hboot with revolutionary s off. I then updated with Freezas AIO. And running meanrom ics 1.0 now.

The problem is that my 3g speed is at slug speeds. Ping is up at 900ish download and upload is below 100.

Before I was on hboot 1.5 2.17.651.5_Radio_1.06.00.1216 and had decent speeds.

Just wondering if someone can shed some light to this problem. Or maybe I have to go back to 1.5hboot and live without a true root.

My Phone is flashed to boost.
[HTC EVO 3D] darkredflame:
Upgrade to h-boot 1.5, and you'll have 1.5 S-Off. Your phone will still be locked though, so run the HTC Dev Unlock Bootloader tool, and then it will also be unlocked and running fine.
[HTC EVO 3D] Tilde88:
i wouldnt follow these directions. your Hboot WILL NOT affect 3g/4g/WiMax/WiFi/GPS/GPRS/EDGE*(N/A)/1x.

These things WILL affect 3g/4g/WiMax/WiFi/GPS/GPRS/EDGE*(N/A)/1x:

Radio/PRL/PRI/build.prop edits/QPST configuration(some of it accessible by doing ##DATA#), your NVdata (Non-Volatile).

Also, the guy who postedthe 'solution'... Has 1 post. And joined a few months back. Stick with 1.4 Hboot. I have never gone to 1.5, and I never will upgrade the Hboot EVER. Maybe a downgrade for engineering commands... BUT DONT UPGRADE!
[HTC EVO 3D] chROMed:
Lol, I would pass on that.
[HTC EVO 3D] laie1472:
@op follow this.

#Root-Hack_Mod*Always\
[HTC EVO 3D] frexe:
lol i wish you guys posted eariler =D

I am currently hboot 1.5 s off. but yep that did nothing at all.

Its all a journey though. Now to go back to 1.4 I would probably need to oem lock, flash run 2715 ruu? then Brick revert back to 1.4 and revolutionary again right? Fun stuff.

My prl is the latest one 60687

PRI is the latest.

Radio is latest.

Build prop.. now this one i have no clue. can someone shed some light? I do recall messing with the build prop on the nook tablet to make it a look like a different device so I could run certain games. But yeah what can I do to my build prop to fix this issue?

I have tested on my other phone with speedtest.net and the same prl. And im getting about 80ping 1000kbps down 800 up. Versus the slug speed I have now on the evo 900+ping below 80 down below 80 up. Tested and compared in the same exact location.

I will try to write my NV data over again, maybe thats what went wrong. I did have to reflash the phone after reverting back to hboot 1.4 Maybe I left that part out.

BTW Thanks for helping.
[HTC EVO 3D] frexe:
Okay problem solved. Turns out it was the nv items 466. 466_1 and possibly 1192

Thanks for the help =)

I feel like a pro now, after downgrading to 1.4 s off twice and a bunch other stuff.
[HTC EVO 3D] Tilde88:
no prob. what did you use to pull the NV? I found a NV-Items_Reader_Writer (free) from cdma-ware. (note people, that is JUST a name, they are not illegal warez). Or did you use PSAS or cdma workshop, or QxDM? ive been a bit lazy to go into my NV and screen through all the lists... but ill use this info you gave to fiddle around :D thanks you too

edit: meh downloading all... got nothing to do today... lets boost some 3g.. "it has moar gbz"
[Android Q&A, Help & Troubleshooting] r3ptilicus:
I'm involved with a company that's giving a batch of ASUS Transformers to a local elementary school for a connected classroom test. Most of the content they will be accessing is accessed through the browser but there a couple of apps that the teachers would like pre-installed and some pre-setup tasks I would like to perform like associating with the school's wireless access and enabling the PIN lock on the marketplace.

I have seen a few apps that let you batch install APKs off a MicroSD card, looking for recommendations on which might be the best for this. Also curious if there is anyone to batch apply the settings without burning through the menus one device at a time.

Thanks in advance for any advice!
[HTC Sensation] trufan1:
I have S-OFF but it seems like every Clockwork Recovery that I download doesn't work. If I do it through the PC on Fastboot, it says "Can't load IMG." and if I try to load it through through the Bootloader on the Phone, it says "Wrong image". :( Plus there are so many recovery images floating around, I have no idea which is the right one.
[HTC Sensation] Kevc44485:
Try following instructions. Works every time for me.
[HTC Sensation] trufan1:
Thanks but I would have liked some real help. Anyone else please?
[HTC Sensation] kgs1992:
You could try EXT instead. Part I to install the recovery. Part I & Part II to install EXT & 3.32 firmware.
[Samsung Galaxy Nexus] lil-tom7:
Can someone help me with the best battery stuff such as kernels and or batter scripts.But the catch i kinda want to stay with the stock rom.

So if anyone can help please do because I have no clue which to get and or will work.
[Samsung Galaxy Nexus] nodstuff:
All kernels work with stock rom as long as it is 4.0.3/4.0.4

Try them out yourself and see.
[Samsung Galaxy Nexus] lil-tom7:
Well I'm just out for opinions and which ones are best the try the best and so on.
[Samsung Galaxy Nexus] nodstuff:
I use Franco kernel, give it a go and see what you think.
[Samsung Galaxy Nexus] Ankh87:
I've got a 3800 battery and it works pretty well. Phone doesn't look as good but battery life is much better
[Samsung Galaxy Nexus] lil-tom7:
Well I don't want to get a 3800 battery I want to stay with the stock battery. And so a Franco kernel is one choice anyone use that and get good battery or if not what do you use to get great battery.
[Samsung Galaxy Nexus] lil-tom7:
Anyone able to help out too?
[Samsung Galaxy Nexus] nodstuff:
Its not even a problem, that's why no one is replying.

These threads always appear.

Try them out for yourself its not difficult, that's what everyone else has to do.