yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] NeonZenith:
Thanks to everyone who is helping me out with this. I wanted to write a step by step of my process as well as compile all the different trials I've tested.

*Note*: Please don't follow these instructions, these are just what I'm doing to end up in a bootloop, so unless you want that skip ahead :)

Please forgive me if the terminology is wrong :P

TWRP

1. Using Odin3 v1.85 (also tried Odin3 v3.04) I flash TWRP-Recovery-GTI9210T-v1.1 by putting the tar file into the PDA section in Odin.

2. Boot into TWRP

3. Wipe the System, and Dalvik cache in TWRP. When I try and do a "factory reset" inside TWRP it will get stuck at formating cache.

Also, in my logs as soon as I run TWRP I get "E:Can't open /cache/recovery/log" and "E:Can't open /cache/recovery/last_log"

Clockwork

1. Using Odin3 v1.85 I flash SkyrocketCWMrecovery (I believe it's version 3.0.5 or something) by putting the tar file into the PDA section in Odin.

2. Boot into CW

3. Wipe data/cache multiple times, then proceed the wipe cache by itself multiple times.

When I look into the logs of CW I get these error messages

E: unknown volume for path [/sd-ext]

rm: can't remove /cache/dalvik-cache : no such file or directory

rm: can't remove /sd-ext/dalvik-cache : no such file or directory

4. Wipe Davlik cache multiple times. (I have skipped this step on different tests)

5. Install from SD, cm-10-20120909-UNOFFICIAL-i9210t and gapps-jb-20120726-signed.

6. Wipe data/cache multiple times.

7. Reboot into a bootloop (have waited close to 40mins)

Other Tests

(Most of the testing has been using the CM10 files since I figured going to GB would be easier than trying ICS)

- Tried using cm-9-20120908-UNOFFICIAL-i9210tTEST1 and gapps-ics-20120429-signed. (CM9 still loops)

- Flashed CW done all the wiping of data/cache etc and the flashed TWRP on to do the installation = still stuck in bootloop.

- Used SGH-T989_DARKSIDE.SUPER.WIPE_EXT4 that I got from the soft button fix. to wipe while in CW as well as standard wipes before installing.

- Tried doing the install from the internal hdd and not the SD card.

- Tried flashing stock from sammobile and then doing the install process

What I've successfully done

(by working I mean got past the booting screens, they still had some issues as I imagine neither of these are for this particular phone)

- Manged to get SkyICS working, though at the cost of my soft buttons.

- On trying to fix my soft buttons I installed ICSmegamix and had that working.

Hope this helps consolidate everything so it makes it easier than reading 5 pages and maybe I missed something so simple that you'll be able to let me know from my procedure.
[Android Q&A, Help & Troubleshooting] imblue:
Found another problem with CM10 and a decent workaround... This time it has to do with the Alarm not playing the audio, only the vibration.

To work around this just do the following:

1. Go into Settings

2. Scroll down to Personal, and select Profiles

3. Whichever profile is selected, click the Settings button next to it

4. Scroll down to Volume Overrides and select Alarm, move the scrolled all the way to 7

5. Ensure the tick button is active next to Alarm.

Done! Your alarm should now work.
[Android Q&A, Help & Troubleshooting] Fedelrick:
!!!! Try installing our cwm touch recovery!!!! The links in my guide a been pages back :) let's hope it works.

---------- Post added at 01:55 PM ---------- Previous post was at 01:48 PM ----------

Here
[Android Q&A, Help & Troubleshooting] h4ck3rc1:
I have successfully installed CM10 Jellybean Unofficial for GT-I9210T using CWM 6.0.1.2 Dreamrecovery without any issues.

I was running CWM 6.0.1.2 Dreamrecovery and Embryo 5.0 ICS ROM with Dreamkernel before with no dramas.

Step by step, I did this:

- Copied CM10 and Gapps to SD card.

- Booted into CWM

- Backup current ROM to internal card.

- Wipe Data/Factory reset

- Wipe Cache

- Wipe Dalvik Cache

- Install CM10 Unofficial GT-I9210T

- Wipe Cache

- Reboot

- Boot into CWM

- Flash Gapps

All worked without a hitch first try.

Only bug I have noticed so far is the capacative buttons backlight does not remain lit.

I can turn it back on by going to Advanced settings and then unchecking and re-checking the option to turn the backlight on with the screen, but as soon as I turn off the screen, the backlight won't come back on unless I repeat the above mentioned procedure.

Will update if I come across any other bugs :)

---------- Post added 11th September 2012 at 12:05 AM ---------- Previous post was 10th September 2012 at 11:41 PM ----------

Just to clarify;

CM10 (Cyanogenmod 10) is JB (Jellybean Android 4.1.x)

CM9 (Cyanogenmod 9) is ICS (Icecream Sandwich Android 4.0.x)

GB (Gingerbread Android 2.3.x) which you mention is actually CM7.x (Cyanogenmod 7)

Sorry if I sound picky or if it was a typo, just wanted to mention to avoid confusion for our less experienced members :)
[Android Q&A, Help & Troubleshooting] NeonZenith:
That would be me! Haha, thanks for the info.

I flashed touch CM, and it freezes when I try to format cache, just like TWRP. Something is definitely wrong with my cache but I have no idea how to fix it.
[Android Q&A, Help & Troubleshooting] Tallustus:
U will find us here ....

Server irc.dream-irc.com

Channel: #TeamSkyFire

u can also use the webchat at http://irc.teamskyfire.co.cc/

best regards
[Android Q&A, Help & Troubleshooting] Fedelrick:
If I can get access to the internet later today I will upload my recovery and you can try it. But it's never been tested so it could possibly turn your phone into a nuke and wipe out half the world.
[Android Q&A, Help & Troubleshooting] Utacka:
Thanks, im in there now, I need the builder of cm10 unofficial guy to provide his local_manifest.xml to me and I will start a PA 2.X JB build.

Skickat från min GT-N7000 via Tapatalk 2
[Android Q&A, Help & Troubleshooting] thewaltz22:
How do you install CWM 6.0.1.2 Dreamrecovery its a zip not tar so odin doesnt see it.
[Android Q&A, Help & Troubleshooting] djkris:
Install CWM 6.0.1.2 Dreamrecovery via Recovery as Install zip from SD Card
[Android Q&A, Help & Troubleshooting] thewaltz22:
Thanks i got it working with TWRP But i will use it on my spare phone now thanks
[Android Q&A, Help & Troubleshooting] imblue:
GPS doesn't seem to want to work for me on CM10... I've seen a few GPS Fix files out there already, any chance we can use one of those?
[Android Q&A, Help & Troubleshooting] wilsd004:
Installed CM10 and Google Apps onto my phone yesterday. Was so sick of Gingerbread!!

Worked a treat only thing I found that my contacts were no longer there but synced with Google again and he presto.

I did it from a stock Telstra phone no dramas at all. Loving the Jellybean OS so much cleaner and nicer!!
[Android Q&A, Help & Troubleshooting] geotherm:
I believe this issue is related to something going funny with your internal memory. Why don't you back-up the memory and re-format it. This post may help you some-what. I suggest removing your sdcard too.

http://xdaforums.com/showpost.php?p=10878511&postcount=8311

Cheers

Geo
[Android Q&A, Help & Troubleshooting] thewaltz22:
To get it working, I had to use odin and flash stock back onto the device, then using odin flashed TWRP and then used TWRP to flask CM10 onto the phone, then worked a treat.. There appears to be an issue with the stock firmware and a version of CWM that is 5.0.2 or lower... as I also got it to work with Dream Recovery.
[Android Q&A, Help & Troubleshooting] geotherm:
Got past the nasty cache bug this is what I did:

From old CWM recovery

Wiped internal memory

Factory reset

wiped cache

superwipe

factory reset

wiped cache

Installed new touch by Odin

Installed CM10

reboot and allow CM10 to run

reboot into touch recovery

install gapps.

All working sucessfully!
[Android Q&A, Help & Troubleshooting] tealine:
TWRP + CM10 worked like a dream. Installing from stock without any problems during the process.

The only hitch was me having problems finding my internal storage. Turned out it was labeled /emmc instead of /sdcard for some obscure reason.

Haven't been able to test against 4G yet, but works fine on 3G. Battery consumption low, only lost 3% during night (WiFi and Data off).

Only annoyance found so far is that the screen flickers when typing password chars. The fix for the alarm volume was clever.
[Android Q&A, Help & Troubleshooting] Nekrosys:
The screen flickering issue can be temporarily resolved by disabling HW overlays in the developer options.

I have noticed today my phone randomly rebooting or requiring a battery pull (when it reboots, HW overlays are re-enabled) so that might be related. Pick your poison I guess.

EDIT: Wiped my cache/Dalvik Cache and it seems fine. Awesome.
[Android Q&A, Help & Troubleshooting] imblue:
Found another displeasing bug. The device will occasionally reboot during a call, or just after a call. I don't believe this is specific to our device and runs across all users of CM10.

On the upside I found that my GPS works and locks on when I enable use mobile networks (and also send anonymous data to Google). Otherwise whilst driving my GPS locked on almost immediately and was accurate to 3 metres... Great!

The bug hunt continues!
[Android Q&A, Help & Troubleshooting] NeonZenith:
Well after a lot of work, I've finally gotten CM10 on my phone. Thanks heaps for everyone who helped along the way. Turns out that I had to do a complete wipe of my phone to stock, and from there wipe everything off it. Installed TWRP and it was a simple process. Now I shall be on the look out for bugs and hopefully give back to you guys that helped me out!

Cheers!
[Android Q&A, Help & Troubleshooting] h4ck3rc1:
As djkris said, I renamed it to update.zip and used the update facility in CWM itself and rebooted recovery to use the new version :)

---------- Post added at 09:24 PM ---------- Previous post was at 09:19 PM ----------

I have also experienced the phone resetting during a call twice, first time I thought it may be a fluke but twice in one day and now that you have mentioned it, there is definately something going on.

---------- Post added at 09:55 PM ---------- Previous post was at 09:24 PM ----------

Just to update the bugs in one spot to date:

- Phone does soft reset during or immediately after calls (not every time - no known workaround or fix yet )

- GPS lock is buggy (Workaround thanks to imblue - Enable mobile networks and send anonymous data to Google)

- Alarm no sound (Workaround thanks to imblue -

1. Go into Settings

2. Scroll down to Personal, and select Profiles

3. Whichever profile is selected, click the Settings button next to it

4. Scroll down to Volume Overrides and select Alarm, move the scrolled all the way to 7

5. Ensure the tick button is active next to Alarm.​

- Screen flickering (Workaround thanks to Nekrosys - Disable HW Overlays )

- One not mentioned anywhere else I can see that I have experienced; The capacitive buttons seem to lose their lighting and vibrate feedback after the screen times out and only seems to come back on when an app "uses" them. (While the they do not light up or vibrate, they

DO

still function - No workaround known yet but they do come back on if you go into Settings > Advanced > Sensors and uncheck then re-check the Enable keys backlight option).

If I missed anything or there is now a fix for one I don't have listed, or if there are any bugs I haven't listed let me know and I'll edit it.

I apologise if I mixed up any of the credits for the fixes, let me know if I have.

EDIT: - Not being able to read SD card (tealine reported not being able to find

internal

storage, I however did not have this issue, instead I was unable to view any of the data on the SD card. I tried using ES File Explorer and set home directory to / instead of /sdcard and i looked in /external_sd/ as well as /mnt/external_sd (which I know should be the same thing) and /sdcard all with no luck.

As a fix, I ended up copying my entire SD card to my PC and then formatted the card, then when I put it back in to my phone and copied files back on to it, I was able to read it fine going to /external_sd/.

Hope this helps if anyone has the same problem.

EDIT: lunchbox201 found the issue of not being able to change from 4G to 3G, after checking, I am also getting this problem.

The list grows :)
[Android Q&A, Help & Troubleshooting] Nekrosys:
Oh. I found my SD card in /storage/sdcard1.
[Android Q&A, Help & Troubleshooting] geotherm:
If you want Bluetooth to play music (sound) use this thread.

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

Worked for me.
[Android Q&A, Help & Troubleshooting] madshabz:
Ok so i haven't checked that yet but i will check it tomorrow when i am in 4G coverage and let you know.
[Android Q&A, Help & Troubleshooting] noxter:
The loaded Touch key FW change after running Sky ICS

Stock touch key FW

Phones Touch key FW version : 0x7

Parts Touch key FW version: 0x7

Sky ICS touch key FW

Phones Touch key FW version : 0x9

Parts Touch key FW version: 0xf

Can anyone confirm if their SG-I9210 or SG-I9210T has the very same stock FW 0x7 before and after rooting the device?
[Android Q&A, Help & Troubleshooting] TimTams:
Just to consolidate what has been said already... is there an ICS custom ROM working for this phone? If so can someone please post me a link to the correct version? I assume I will just need to restore a backup of the boot.img to get the buttons working?

Also which version of CWM is required, I have v5.0.2.6, will this suffice or should I update it?

Thanks :)
[Android Q&A, Help & Troubleshooting] TimTams:
Ok, so I have CWM on and made a backup.... then rebooted... and now my touch buttons don't work. Before I even started thinking about messing with a ROM.

Any ideas?

Cheers
[Android Q&A, Help & Troubleshooting] bwp85:
Did you install super user? Most problems I've seen is after getting su permissions.

Also, what version CWM did you install?

Sent from my Samsung Galaxy S II GT-I9210T
[Android Q&A, Help & Troubleshooting] bwp85:
I have tried a few ICS roms and have managed to get them to boot. However, the radio is incompatible with the ICS binaries and the Soft key problem is still there. I tried fixing soft key by restoring boot.img from a GB backup but then it wouldn't boot.

I'd like to learn how to modify radios and boot.img files (unless someone already knows how) before trying ICS again.

Another thing. You need Touch Clockwork Mod Recovery to flash ICS ROMS. I'm using 5.8.1.3

Sent from my Samsung Galaxy S II GT-I9210T
[Android Q&A, Help & Troubleshooting] bwp85:
Yes I have the same version come up. It's stored within the boot.img file.

EDIT: I misread what you said. Mine comes up as 0x9 current.

Sent from my Samsung Galaxy S II GT-I9210T
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi Guys,

I have come to a conclusion this soft key issue is caused by CWM.

I rooted my phone around a month ago, everything worked fine, CWM installed, SuperUser installed, all working perfectly.

Last night i went into CWM and had intentions of creating a backup, I accidently ran through the menu pressing the Volume Up key to many times and noticed the message:

Back menu button disabled

After doing the same thing, cycling through the menu x3 times to get the message:

Back menu button enabled

I rebooted my phone, did not do anything else, the soft keys were gone.

Ran the *#*#2663#*#* command the noticed the following:

Phone's Touch key FW version: 0x7

Part's Touch key FW version : 0x0

I tried the "Touch key FW update" button with no luck.

Also tested the following roms's:

Juggernaught v5.0

Digital Warefare v2.6

Foxstar 1.4.0

Original Telstra Firmware

The issue still persists, although i did notice with each rom the Phone's Touch key FW verion was different but still did not match the Part's Touch key FW version.

I have no doubt if i did not go into CWM and accidently disabled the Back menu button my soft keys would still be working perfectly.

I have found a temporary work around which is an application called "Button Savior" which is free and available from the Play Store, which gives you access to the "Back" and "Menu" soft keys through a slide in application, very handy for us people who are effected by this bug.

I have tried the restore boot.img as advised but this has not resolved the issue.

Would it be possible for someone to post their boot.img whom restoring this has resolved the issue?

I have a feeling this issue is due to the fact we are installing CWM for the SkyRocket version, and our phone settings may be differernt.

In the meantime, i advise everyone who has not tried yet, please DO NOT root until this issue is resolved.

Thanks

Scott
[Android Q&A, Help & Troubleshooting] TimTams:
Just to update - I flashed my phone with the original Telstra firmware and it has gotten rid of CWM, but the problem with the touch buttons still exists.
[Android Q&A, Help & Troubleshooting] bwp85:
Did you remove battery?

What is the soft key version saying? Should be "0x7"

What version CWM were you running? (I'm running Touch 5.8.1.3)

If you're at an end, I suggest taking it back for warranty. Just make sure in download mode it says;

"CUSTOM BINARY DOWNLOAD: NO"

"CURRENT BINARY: SAMSUNG OFFICIAL"

Note: CWM should not effect these switches.

I currently have Jeggernaut-V5.0 installed with buttons and 4g working.

Requirements:

Jeggernaut-V5.0

Working boot.img (can provide) to copy into a recovery. approx 10mb

Original radio

ROM Manager (after flashing CWM Standard and root) to get Touch 5.8.1.3.

If you'd like instructions let me know.
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi bwp85,

The Part's Touch key FW version is 0x0, this is my problem.

If you could please provide your working boot.img for me to test that would be greatly appreciated ;)

I have also updated CWM to CWM Touch 5.8.1.3 successfully.

Could you please provide step by step instructions so we can follow and test this.

Thanks in advance

Scott
[Android Q&A, Help & Troubleshooting] bwp85:
For those that would like to try Jeggernaut-V5.0:

Step 1: Get the resources.

Jeggernaut-V5.0

My Working boot.img 5.49 MB

Clockwork Mod Recovery Touch 5.8.1.3 via this link or flashed through ROM Manager (recommended).

Step 2: Flash CWM and get running, I'm guessing if you have come this far you know how.

Step 3: Create a backup of your stock ROM broken or unbroken to external SD.

Step 4: While in CWM connect PC then go to "mounts and storage" > "mount usb storage". Wait for PC to connect. On PC navigate to "\clockworkmod\backup\##########" ##### being the backup you just made.

Copy the "boot.img" unzipped into this folder replacing the one that is there. and if you have not already done so, copy Juggernaut into a folder you will remember.

Safely remove from PC and unmount.

Step 5: Follow the steps laid out to install Juggernaut

Step 6: Providing you have got Juggernaut to boot and setup, you should be at a stage where your soft keys don't work.

Boot into CWM. "Backup and restore > advanced restore > ####### > Restore boot"

Restart and voila you should now have your soft keys back.

Hope this is clear enough, this is my first guide.

Please hit thanks if it got you going again.

This method should also work with stock rom, just skip step 5
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi bwp85,

Thanks for your fast response.

I followed your below instructions, currently have the Juggernaught the rom installed, all is running well except the softkeys :( as using your boot.img has not resolved the issue.

Back to the drawing board unfortunately.

Thanks for trying...

Scott
[Android Q&A, Help & Troubleshooting] bwp85:
Don't mean to sound like a broken record, but did you shut it down, replace the battery and boot up?
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi Bwp,

I did not shut the phone down at any stage and remove the battery, I would like to re flash and try this, when exactly should I be shutting down and removing the battery?

Also how long do you recommend leaving it powered off for?

Thanks

Scott
[Android Q&A, Help & Troubleshooting] ecips:
Touch Buttons

Hi Guys,

I am running the stock Telstra firmware, however I have deodexed, zipaligned and rooted it.

Looking at the dmesg output of the kernel on my phone I see the following:

This is the kernel initialising the touch keys:

<4>[ 0.285491] [TKEY] tkey_device_init: 8901_lvs2 On

<4>[ 0.286010] [TKEY] tkey_device_init: TKEY_L12 3.3 V Set

<4>[ 1.243804] [TKEY] touchkey_init START

<4>[ 1.244995] [TKEY] touchkey_init F/W version: 0x7, Module version:0x3, HW_REV: 0xa

<4>[ 1.245086] [TKEY] melfas i2c_touchkey_probe

<6>[ 1.245239] input: sec_touchkey as /devices/virtual/input/input9

<4>[ 1.245697] [TKEY] enter touchkey_auto_calibration

<4>[ 1.296112] [TKEY] touchkey_init END

and this is the touch screen controller

<6>[ 0.875946] input: sec_touchscreen as /devices/virtual/input/input2

<4>[ 0.876220] mxt224_power_on: enter

<4>[ 0.876251] mxt224_power_on : I9210 Rev02 8901_l4

<3>[ 0.876647] [TSP POWER ON L1 3.3 enable

<3>[ 0.877105] [TSP POWER ON L4 1.8 enable

<4>[ 0.877288] mxt224_power_on: exit

<4>[ 0.934509] mxt224_power_on is finished

<3>[ 0.975830] [TSP] family = 0x81, variant = 0x1, version = 0x10, build = 170

<3>[ 1.000335] [TSP] TSP chip is MXT224-E

<3>[ 1.001068] [TSP]user_info_value is 0

<3>[ 1.094604] [TSP] ta_status is 0

<3>[ 1.094726] [TSP] mxt224_ta_probe

<3>[ 1.105224] [TSP]TA_probe MXT224E T48 Byte2 is 96

<3>[ 1.107940] [TSP]calibration success!!!

<3>[ 1.108367] [TSP] mxt224_probe e

<3>[ 1.109649] [TSP] Calibration!!!!!!

<3>[ 1.111236] [TSP] Calibration End!!!!!!

<3>[ 1.114837] [TSP] Calibration!!!!!!

<3>[ 1.126617] [TSP] Calibration End!!!!!!

<3>[ 7.136077] [TSP] mxt224_ta_probe

<3>[ 7.147552] [TSP]TA_probe MXT224E T48 Byte2 is 114

<3>[ 7.277740] [TSP] Calibration!!!!!!

<3>[ 7.279327] [TSP] median filter ON!!!

<3>[ 7.281005] [TSP] Calibration End!!!!!!

This line:

<6>[ 1.245239] input: sec_touchkey as /devices/virtual/input/input9

Shows that the touchkeys are registered at:

/sys/devices/virtual/input/input9

Looking in there:

/sys/devices/virtual/input/input9 # cat uevent

PRODUCT=19/0/0/0

NAME="sec_touchkey"

PHYS="melfas-touchkey/input0"

EV==3

KEY==2000000 0 40000800 40 0 0 0

MODALIAS=input:b0019v0000p0000e0000-e0,1,k8B,9E,D9,ramlsfw

Can someone who has broken buttons have a look at the output of their device and see if anything is wildly different?

Might also be good to see the output from other working devices too.

Cheers!

Gary
[Android Q&A, Help & Troubleshooting] bwp85:
After first reboot, let the OS settle then shut it down, remove the battery (only has to be for a second) the reboot.

This is all i have had to do to get my phone working properly.

Regards,

Brian
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi Brian,

So just to confirm I should be shutting down straight after I install the juggernaut ROM after it reboots?

It is suggested to let the phone idle for 10 minutes following a reboot on the juggernaut forum topic, so I did this but did not shut down, as it never said to.

I'm just curious exactly how you did what you did in what order as your is working and mine isn't.

Also in your above topic you mentioned to transfer the boot.img while on CWM, I tried this but didn't work, so I transferred this with the file manager, then restored the boot via CWM, would this make any difference?

Thanks

Scott
[Android Q&A, Help & Troubleshooting] bwp85:
I'll try again on my phone and provide step by step.