yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] CalinDee:
Hey folks, hoping somebody may be able to provide a little assistance here.

Be forewarned - first foray into Android modding. :confused:

I have just attempted to flash a SGS2 gt9210t from completely stock to CM10 (JB) by performing the following steps, unfortunately it appears to be stuck at the oh so very lovely but boring after 15 minutes CyanaogenMod Boot Logo:

Downloaded TWRP, cm-10-20120917-UNOFFICIAL-i9210t, gapps-jb-20120726-signed, DreamKernel and Odin 1.85 all from http://xdaforums.com/showpost.php?p=31319717&postcount=495.

Using Odin I dropped TWRP onto the phone and then booted into TWRP.

Performed a system backup and copied said backup off to my pc for safe keeping (rebooted to dump across to pc then jumped back into TWRP)

Wiped cache, Dalvik cache and system

Flashed cm10, DreamKernel and gapps

Rebooted

After approximately 15 minutes of displaying nothing but the CM Animation the phone rebooted and then proceeded to apparently get stuck at the CM Animation again.

Any ideas on what may be causing this apparent boot loop and how I might go about getting CM10 working? I can easily go back to stock using the above mentioned backup, and have already done so to test. I then attempted the above again and left the stock kernel in place and saw the same results.
[Android Q&A, Help & Troubleshooting] therethere:
try to flash rom again, and wipe cache and dalvik.

---------- Post added at 02:33 PM ---------- Previous post was at 02:32 PM ----------

try this

wipe cache, dalvik and format data

then

flash cm10 and gapps and try it. first time takes a bit to load see if it's working.

then flash dreamkernel.
[Android Q&A, Help & Troubleshooting] CalinDee:
Format data appears to have done the trick. Cheers!

Will see how it goes.
[Android Q&A, Help & Troubleshooting] sicHiRsch:
Didnt do the trick unfortunately. But my installs always only take about a minute. No long booting after flashing.
[Android Q&A, Help & Troubleshooting] therethere:
try fix permissions on advanced menu on TWRP.

if not work, try flash day 17 rom.
[Android Q&A, Help & Troubleshooting] bjm374:
When I've had this issue in the past I have resorted the flashing the ROM twice before rebooting. I've nearly always found the second flash takes longer.
[Android Q&A, Help & Troubleshooting] sicHiRsch:
Alright I caught the culprit. It was a little tool called 'battery mix. I just remembered it told me something during installation about third party software and made me. Switch third party install protection on. So I switched it off, removed from autostart and fair enough, after a reboot it would let me install whatever from wherever I want :D

Thanks though. Will continue testing
[Android Q&A, Help & Troubleshooting] CalinDee:
Having now dropped CM10 and gapps onto the phone, it appears to running quite well - no glaring issues found as yet.

The only thing Ive noticed so far is that Kies now seems unable to connect to the device, the connecting icon just sits spinning and achieving nothing.

Has anybody else noticed this behaviour?
[Android Q&A, Help & Troubleshooting] bjm374:
I have the same issue with kies so I downloaded a little app called kies air and use that. The alternative is to plug the phone in and use it as a media player, you can access most of the files that way too.
[Android Q&A, Help & Troubleshooting] geotherm:
My battery level is freezing. Even when I plug power in it doesn't charge. What could be the culprit? I have gone back from 17 to 14. Same thing is happening.
[Android Q&A, Help & Troubleshooting] CalinDee:
Hey folks,

I have come across an apparent bug in the cm-10-20120917-UNOFFICIAL-i9210t (standard Kernel) release; or at the least the application of it on my device.

Bluetooth car audio behaves, well, oddly.

The phone pairs with the car as expected and connects quickly, however streaming audio plays through the phone speaker instead of the car speakers. The car controls the playback properly but the output is not passed through to the vehicle.

This applies to telephone calls placed from the car also. The phone controls work as expected and the phonebook transfers as required, again its just the audio that continues to be played through the phone speaker instead of the car speakers as it should.

Anybody else seeing similar behaviour?
[Android Q&A, Help & Troubleshooting] braso:
A similar thing happened to me. The battery didn't charge overnight and the phone would no longer connect to the PC. Kept coming up with 'USB device not recognized' error. The phone was also charging very slowly. I gave the Micro USB connection a good clean with a toothbrush and compressed air. That still didn't fix it, so I tried my Galaxy Note on the PC (the 9210T is my wifes). For some reason, the computer had to install drivers for the N7000. After that I plugged the 9210T back in and it worked fine after installing the drivers. I can't explain what has happened as I used Odin to flash CWM on the 9210T when I rooted it, so it was definitely working before. In any case, the battery issue fixed itself using the above method.
[Android Q&A, Help & Troubleshooting] geotherm:
Battery issue was fixed by wiping caches and fixing permissions.
[Android Q&A, Help & Troubleshooting] dglewis80:
I have also found this.
[Android Q&A, Help & Troubleshooting] blitzace:
In version 17, if i don't touch my phone for about 10-20 min, when i go back to it, it reboots, and doesn't go pass the samsung logo. I have to remove battery and reboot it to enter the system.

In version 21 (wich a user gave me acess from the IRC) when i'm at a program, for example text messages, and press the "back" softkey, it doesn't close the program, it just goes to homescreen, and it keeps the program running on background.

Hopefully you guys can fix this. :)

:good:
[Android Q&A, Help & Troubleshooting] geotherm:
The car BT issues I fixed with my audio_profile.conf file in versions 12&14. In version 17 I couldn't get the BT to work by modifying the conf file. I don't know what 17 broke...
[Android Q&A, Help & Troubleshooting] Norman3000:
I have read but..

Hi guys, I recently purchased a Samsung S2 phone, unfortunately I did not know earlier that this one had limited to none developer support.:crying:

I have succesfully Rooted my phone but my capacitive buttons are not working, I did NANDROID backup and flashed boot.img but still no effect

I have been reading this thread and I am now at Page 20 :)

So my questions are:

Is GT-I9210 and SHV-E110S the same phone? ( I may have been looking at the wrong forum this whole time)

I have read successful CUstom Roms, like Alien, Slickmod, SKYICs, Juggernaut and ICS MEgamix, is there any Rom that removes the 80 SMS Limit?

Or can you immediately remove it after rooting? If so how?

Also how come the buttons *#*#2663#*#* does not work for me? Thank you for your time everyone :)
[Android Q&A, Help & Troubleshooting] therethere:
i think SHV-E110S is the samsung galaxy s2 LTE HD, so with different specs than i9210.

if you have i9210, try flash this cm10.
[Android Q&A, Help & Troubleshooting] bwp85:
Link to the latest build (21/09/12) here and more instructions.
[Android Q&A, Help & Troubleshooting] bwp85:
Found an issue while using the back button (right soft key). It has the same mapping as the home key.

Problem: You want to go back (previous page) in a web browser and it would take you to home screen.

Fix: Installed DreamKernel-GTI9210T-v1.5CM10_RC1-20120912053352-CWM.zip Gives you your stock buttons. Working fine since.

Have not yet had a chance to test bluetooth. Will do and let you know.
[Android Q&A, Help & Troubleshooting] CalinDee:
Another, very small, issue found.

CM10

Dreamkernel (DreamKernel-GTI9210T-v1.5CM10_RC1)

The indicator light (missed calls etc) doesn't function, it is enabled and have tried both default and custom lighting settings.

BTW, BT audio still fails to redirect to car audio using the above Kernel.
[Android Q&A, Help & Troubleshooting] therethere:
it seems that's the same problem
[Android Q&A, Help & Troubleshooting] geotherm:
It is not the kernel as I am having no issues with BT on the 14/9 release and the dream kernel and my modified audio profile config file. It is just when you update to 17/9 version it BT and the car audio fails to re-route the voice.
[Android Q&A, Help & Troubleshooting] bjm374:
So you can stream audio and receive calls with the 17/9 kernel?
[Android Q&A, Help & Troubleshooting] Nekrosys:
Can you upgrade from the Talustus builds to this?
[Android Q&A, Help & Troubleshooting] therethere:
seems samung just confirmed the JB update to our device.

http://www.theverge.com/2012/9/24/3381542/samsung-galaxy-s-iii-android-jelly-bean-update-device-list
[Android Q&A, Help & Troubleshooting] geotherm:
No, I found I could not get BT working on the 17/9 rom with sound in calls in the car, but it worked fine with audio streaming. I went back to the 14/9 rom and found that to work very well and be quite stable. I did update the audio_profile.conf and I am using the dream kernel.
[Android Q&A, Help & Troubleshooting] Nekrosys:
Knowing Samsung and our handsets, this will be made available (if ever) several months after the release of the next Android OS.
[Android Q&A, Help & Troubleshooting] therethere:
well they say S3 is being updated and the others gets updated in the near future, so i believe that the free version (unbranded) of our device will get the update soon.
[Android Q&A, Help & Troubleshooting] Drachy:
not working.

It doesnt seem to matter what i try, it just sits on the boot screen... i just don't why it works on other peoples phones. this is for the australian telstra galaxy s2 4g lte gt i9210t isnt it?

Also ive lost the use of my capacitive buttons, how do i get them back?
[Android Q&A, Help & Troubleshooting] therethere:
desbribe your flashing method.

the first flashing takes a bit to load on boot logo so...
[Android Q&A, Help & Troubleshooting] Drachy:
The first time i flashed i was on embryo ICS rom with its dream kernel installed for the the touch button funcionality, this worked perfect.

I have the cm10 rom and gapps on the external sd card.

boot cwm

wipe data

wipe cache

wipe dalvick cache

install rom

install gapps reboot.

It sat for about 20 minute on boot screen, i tried rebooting.

sat for a further 20ish minutes.

i have a backup of my original phone with only root, so i restored that, tried the same flash process again, put it on charge and watch a movie.

after the movie was still sitting on the same boot screen.

reinstalled my previous embryo rom (with and without the dream kernel), touch buttons light up and dont work.

tried to flash cm10 again, same thing.

using odin flashed stock firmware from telstra, same touch button thing.

tried to flash cm10 again, further bootloop

went back to telstra stock again, touch button issue

currently back on embryo, still with touch button issue.

Not sure what to try now...
[Android Q&A, Help & Troubleshooting] therethere:
what is the touch button issue?

Wich version of cm10 are you flashing?

try to flash recovery with the TWRP on this post:

http://xdaforums.com/showpost.php?p=31319717&postcount=495
[Android Q&A, Help & Troubleshooting] Drachy:
im flashing the newest version of cm10 20120917 unofficial i9210t.

ah and i tried the TWRP recovery but it froze while wiping cache.

The touch button issue is that they light up (i think they stay lit up while im interacting with the phone, but that do not respond. when i touch them nothing happens at all.
[Android Q&A, Help & Troubleshooting] therethere:
try to flash another version of cm10.

TWRP should work....it's fine on my device.
[Android Q&A, Help & Troubleshooting] Drachy:
Im having a number of problems :/

I had been using cwm 5026 which i used for my embryo rom.

I tried putting cwm6013 touch on my sd then flashing through cwm, however when i reboot into recovery it will appear but then immediately reboot the device.

TWRP wipes system and Dalvek fine, but wont finish wiping cache, just sits there saying "Formatting /cache..."

clearly i must be doing something wrong.

EDIT: should there be an MD5 file in the cm10 or gapps files? i tried checking the option to force it TWRP to check but it found none.
[Android Q&A, Help & Troubleshooting] *d1000:
Firstly thank you very much for Tallastus, Nutterpc and all others who have spent time and energy developing for this handset with great potential. I've pretty much signed up just to say that.

For the cyan boot loop and not being able to wipe cache with twrp this has been covered. Flash the original Telstra rom, then twrp (or cwm) and then it will work. Links and instructions are in the thread please spend the time going through because it just makes the thread longer and the next person will then also not want to spend the time going through it so posts the same question and the cycle continues. Not having a go just stating the obvious.

My question is regarding the headphones. I've also purchased a replacement battery with a standalone charger (so it doesn't have to be inserted into phone) from eBay for dirt cheap and it's been great. Can't find any headphones for the i9210t...can we use skyrocket? I tried a few standard headphones and they didn't work properly. This also reminds is there an app or solution to getting the radio working on the phone yet? I lost the clear end piece on the headphones so I now have en excuse to get a new set...I must admit I was disappointed to find the originals were white...
[Android Q&A, Help & Troubleshooting] Drachy:
Ive been able to fix the freezing on cache, and i can get my touchkeys back with a touch key fixer, but nothing will get this rom past the cyanogenmod boot screen. just sits spinning :(

EDIT: managed to evantually get it working, through the process of installing the button fixer, then the telstra firmware, then doing a stock factory/cache reset, then flashing TWRP in odin, then using twrp to install cm10 gapps AND dreamkernel. tries every combination of everything else and ths is all that go it working..

FINALLY, lol.
[Android Q&A, Help & Troubleshooting] Dallby:
Hey folks,

Just flashed the 21/9/12 update of CM10 JB and lost my softkeys :(

Is there a fix for this?

It's the first time I've lost my softkeys, when I flashed the 17/9/12 update i didn't lose softkeys, same with flashing ICS roms.
[Android Q&A, Help & Troubleshooting] therethere:
1- revert to your stock rom.

2 - wipe/factory reset in samsung stock recovery

now your phone is completely clean

3- flash TWRP on this thread with Odin

4- then factory reset and wipe cache on TWRP

5-flash CM10 and gapps
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi Guys,

This has been discussed many times throughout this thread, please use the search feature or view older pages.

Regards,

Scott
[Android Q&A, Help & Troubleshooting] Drachy:
Hey i've noticed a few bugs that i'm not sure if they've been mentioned so just putting them out there.

My Wifi seems to refuse to turn on

The phone continues to randomly reboot

The voice assistance doesnt talk back, it functions but doesn't speak.

Has anyone else noticed these issues?
[Android Q&A, Help & Troubleshooting] thewaltz22:
Hey

The first two issues stated have been mentioned before and I believe there is a fix for the wifi issue a few pages back from memory. As for the reboots, they seem to happen to some and not others... clear your cache and dalvik and this seems to resolve it from rebooting randomly for some but some people have stated the reboots continue to happen but less frequient. The voice assistance issue I havent heard of before as I myself do not use it.
[Android Q&A, Help & Troubleshooting] Drachy:
Where is this 21/9/12 update? latest i can find is the 17th.
[Android Q&A, Help & Troubleshooting] thewaltz22:
Hello,

I believe this is not an Update done by the guys here on this forum, this appears to be a CM10 version from another forum.

Cheers
[Android Q&A, Help & Troubleshooting] Drachy:
as far as installation problems go, what if you

restored the original telstra software,

made sure buttons, wifi and things all work as they should,

have done a full factory reset

flashed twrp

installed the cm10 and gapps zips

wiped cache and dalvik

reboot

...and it still doesnt go past the boot screen??

have tried with dream kernel as well, have used button fixes, other recoveries, other versions of cm10, no luck.

managed to get it to install once but i think i flashed to many things so it kept rebooting and the wifi wasnt working.
[Android Q&A, Help & Troubleshooting] brenno88:
Please read the OCAU forum CAREFULLY AND SLOWLY!

You need to clear your dalvik cache after flashing TWRP, the same thing happened to me, even after I did that, so I went back to TWRP and cleared all the dalvik/caches twice and I got past it.

If it doesn't work, read it again and do a search, to avoid clutter as has been said before in the thread.

http://forums.overclockers.com.au/showpost.php?p=14758446&postcount=2 (known issues and solutions)

While I am at it, you will need to install dream kernal 1.5 to fix the back button issue.

Play around with it before you post your questions, as this is meant to be for the devs to discuss issues ect not for you to ask questions that have already been answered.
[Android Q&A, Help & Troubleshooting] therethere:
for all problems that some of you are having try this:

1- revert to your stock rom.

2 - wipe/factory reset. wipe cache/dalvik in samsung stock recovery

3- load rom to see if all is fine.

now your phone is completely clean

3- flash TWRP on this thread with Odin

4- then factory reset and wipe cache/dalkvik on TWRP

5- load rom to see if all is fine

5- on TWRP flash CM10 and gapps

6 - wipe cache, dalvik

7- load rom and all should be fine.
[Android Q&A, Help & Troubleshooting] thewaltz22:
Nutter and Tal,

Are you guys working on any more updates to CM10 at the moment....

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

Thanks for your reply, testing now, will post results soon

Scott
[Android Q&A, Help & Troubleshooting] ecips:
More digging

I have been digging around some more.....

I found that the touchkey firmware menu is accessed by typing:

*#*#86824#*#*

This "android.provider.Telephony.SECRET_CODE" is embedded in the FactoryTest.apk.

I wonder if it also contains the payload that gets flashed and if it is different on the 727 ROM from the 9210T ROM.

More digging to do......

Dug more.....

Found:

/sys/devices/virtual/misc/melfas_touchkey/

Which contains:

-rw-rw-r-- radio system 4096 2012-04-25 07:26 touch_version

-rw-rw-r-- root root 4096 2012-04-25 09:45 touch_recommend

-rw-rw-r-- radio system 4096 2012-04-25 07:26 touch_update

-rw-rw-r-- radio system 4096 2012-04-25 07:26 brightness

-rw-rw-r-- radio system 4096 2012-04-25 07:26 enable_disable

Amongst other things.

enable_disable looks interesting.

Also found -

/system/usr/keylayout/melfas-touchkey.kl

Which contains:

key 158 BACK WAKE

key 139 MENU WAKE

This file is probably different on a 727 ROM

This line:

//------------------- Auto Firmware Update Routine Start -------------------//

in

drivers/input/touchscreen/melfas_touchkey.c

Looks interesting too!

Dig, dig dig....
[Android Q&A, Help & Troubleshooting] bwp85:
I'm going to break my boot and try the menu.

Can confirm that entering *#*#86824#*#* in dial pad then updating works!!! Thanks ecips.
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi Brian,

Thanks for your guide, i got up to Step 5 - (b) in which when restoring boot i get the message:

"Checking MD5 sums..."

"MD5 mismatch!"

Any idea's?

Thanks

Scott
[Android Q&A, Help & Troubleshooting] ecips:
You need to calculate the md5 of the boot.img and update the nandroid.md5 file

root@bruce:/home/gary/Downloads# md5sum boot.img

7f3d310122a0ccf9829c52a001862be2 boot.img

There is no editor in recovery so you will need to pull the file to your PC and edit it then push it back again.
[Android Q&A, Help & Troubleshooting] bwp85:
Not sure. You could try re downloading the file. However, another fix has been provided. See my previous post.

Regards,

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

Managed to update the MD5 successfully, thanks for the tip.

Tested again managed to restore your boot.img successfully, but the softkeys still not working unfortunately.

*#*#86824#*#* also has not worked :(

Part's Touch key FW version : 0x0

Cant seem to get the FW version to go back to 0x7

Testing full process again now.

Scott
[Android Q&A, Help & Troubleshooting] bwp85:
After restoring boot.img, did you try rebooting a couple of times? I didn't need to but you never know.

Does anyone know how to modify mdm.bin files?
[Android Q&A, Help & Troubleshooting] ecips:
VLB3_I9210TTELLB1_I9210TDVLB1_HOME.tar.md5_FILES# file mdm.bin

mdm.bin: x86 boot sector; partition 1: ID=0x6, active, starthead 0, startsector 0, 409600 sectors, code offset 0x3c, OEM-ID "MTOO4013", sectors/cluster 8, root entries 512, sectors/FAT 200, heads 5, sectors 409600 (volumes > 32 MB) , serial number 0x29b2acbf, unlabeled, FAT (16 bit)

It's a filesystem

mount -o loop mdm.bin /mnt
[Android Q&A, Help & Troubleshooting] bwp85:
I'm using Cygwin, doesn't like the command string provided.

I was going to compare stock mdm to an ICS one.

Cheers,

Brian
[Android Q&A, Help & Troubleshooting] ecips:
I actually tore apart the modem files of one of the 727 ICS ROM's and found the word "Telstra" in it.

:-)
[Android Q&A, Help & Troubleshooting] sc0ttf:
Tested full process again guys, no luck.

Rebooted 3-5 times, still no soft keys :(

Might put the Telstra firmware back on and try restore the boot.img again.

Scott
[Android Q&A, Help & Troubleshooting] ecips:
For your enjoyment: -

http://www.spice.net.au/GT-I9210T/

:-)

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------

Scott,

Read my earlier posts.

Provide me with some of the information I have asked for.

I cant get a result unless people give me info.
[Android Q&A, Help & Troubleshooting] sc0ttf:
Hi Gary,

Im not sure how to get the information you have provided above from my device :(

Scott
[Android Q&A, Help & Troubleshooting] bwp85:
install a terminal emulator link

open then type "dmesg"

Copy and past all txt into a txt editor or strait into XDA Thread.
[Android Q&A, Help & Troubleshooting] ecips:
Even better - enable USB debugging on the device, plug it in to your PC with a USB cable and use adb.

Windows ADB can be downloaded at above URL.

If you would like some more interactive help, I am on IRC - #IndieROMS on irc.freenode.net

If you dont have an IRC client go to:

http://www.spice.net.au:9090

Nickname - you can choose!!

Channel - #IndieROMS