Outline ·
[ Standard ] ·
Linear+
SAMSUNG GALAXY S II Official thread V23, Be a SMART user - Pls read Page 1 first
|
Shizuru
|
Jan 14 2012, 12:44 PM
|
|
QUOTE(Mollai @ Jan 14 2012, 12:40 PM) no one can help me summarize it..and tell me?  Added on January 14, 2012, 12:41 pmok..i got ICS = ice cream sandwich.. and GB i assume = Garlic Bread. TW?..hmm..what food? LOL.. GB is Gingerbread. TW is touchwiz samsung stock launcher. Please don't tell me you donno what launcher is
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 02:16 PM
|
|
QUOTE(fwhoam @ Jan 14 2012, 02:13 PM) guys, it seems that samsung has updated it bootloader in the current firmware to deal with the jig solution. if u are in 2.3.6 the jig cannot be use to reset the triangle and the flash counter. just got the jig and tested with my sgs2. not working .  it wasn't working since 2.3.5 but no problem if you're using custom rom.
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 02:19 PM
|
|
QUOTE(drakzero @ Jan 14 2012, 02:16 PM) Been wondering about this for some time. Aren't we suppose to be able to "eject" our SII? My SII doesn't allow me to do so even when I connect it to my lappie via USB  you can only eject under usb debugging mode
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:11 PM
|
|
QUOTE(plain_white @ Jan 14 2012, 04:09 PM) notice any difference? so the firmware version is 2.3.7? KL3 is 2.3.6
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:24 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 04:21 PM) Tested. Not working. This is my problem. When I turn on phone, phone shows no signal. check Mobile Setting. Sim not detected. Tried another SIM card, sim card not detected. Tried my sim on another phone, working though. The weird thing is this morning, everything was working well. I mean not a problem at all. After 12 noon, I reboot phone and suddenly, no SIM card detected. So, what is the problem here? No changes done or no new app installed. your imei still intact?
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:36 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 04:32 PM) IMEI - unknown Restore efs via CWM right? Never do before but remember I backup EFS last week  wah.. reboot also imei lost. today got 2 cases already yeah, restore like laptopdude and angelz said.
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:44 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 04:38 PM) I backup using EFS backup from NEAK kernel... I use Ktool and it says no such file. But I have in SD card is 2 seperate files with different dates ending with .tar.gz Still can't detect or I did something wrong?  don't have the img file? my ktool can detect both tar and img file. efs in internal storage?
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:46 PM
|
|
QUOTE(bananalow @ Jan 14 2012, 04:44 PM) update to siyah 2.6.7 ~~ i can feel slightly lagness ~~ gonna observe the battery life~~ ><" awaiting your review  still can't decide between siyah and neak
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:56 PM
|
|
QUOTE(bananalow @ Jan 14 2012, 04:52 PM) i just want to see the kernel wakelock of wifi got improve or not ~~ i have no major problem with other wakelock~~  and havent try NEAK kernel b4 ~ dunno how is it ~~ ><" NEAK mostly got good reviews but the camera bug make me reluctant to flash it.
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:58 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 04:55 PM) I have the EFS backup done before and found I have 2 files (one dated yesterday and another last week and both ending with .tar.gz) Are these the right one? I tried ktool and it say no file found. Weird. Not sure how else I should restore.  tar.gz should be the right files but with that you should also have the img file. putting it in internal storage also can detect?
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 04:59 PM
|
|
QUOTE(bananalow @ Jan 14 2012, 04:58 PM) KNOWN BUGS: - Stock Camera app --> lock the screen ---> phone won't wake up, needs hard reboot (will fix into 1.4x)
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 05:02 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 04:58 PM) I have efsbackup.tar.gz, efs_13Jan2012-1733.tar.gz and efsdev-mmcblk0p1.img.gz in my phone but ktool can't detect. What is wrong le?  can anyone help him please.. Donno why ktool can't detect the files
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 05:06 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 05:04 PM) Yalu...the last thing I want to do is to send back to service centre. Just wondering, will restore solve the problem?  restore how? nandroid? nandroid backup does not backup efs
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 05:16 PM
|
|
QUOTE(Fallenangelz @ Jan 14 2012, 05:10 PM) how bout try to use adb shell? adbyeah, uncle benny also post it on first page post #6 Have you tried check EFS backup with ktool? This post has been edited by Shizuru: Jan 14 2012, 05:20 PM
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 05:49 PM
|
|
QUOTE(n8210 @ Jan 14 2012, 05:48 PM) cause its an AP set
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 07:22 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 07:19 PM) Definitely! You guys has been helping me so much. Appreciate that. Now downloading stock ROM as final resort and see if this work. If not, bye bye have to go to SC jorĀ Can we do it at SEP instead? Curious... Nope cause you need to go SC change proc if I'm not mistaken. This post has been edited by Shizuru: Jan 14 2012, 07:22 PM
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 07:30 PM
|
|
QUOTE(nicregi @ Jan 14 2012, 07:28 PM) Change proc? Whats that if you don't mind me asking, Change the processor.
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 08:54 PM
|
|
QUOTE(ashwin1234 @ Jan 14 2012, 08:29 PM) ktool just got an update. Re-did my EFS backup after seeing so many people suffer. Seems like some phones are more prone to the EFS corruption than others. the new update totally screw up my backup  thankfully I got a copy of my previous backup
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 09:01 PM
|
|
QUOTE(antt00 @ Jan 14 2012, 08:59 PM) Really? How you know it was screwed up.  did a check after did a new backup and it says backup file not found for the img file.
|
|
|
|
|
|
Shizuru
|
Jan 14 2012, 09:08 PM
|
|
QUOTE(antt00 @ Jan 14 2012, 09:05 PM) Hmm. Maybe thats the problem also for nicregi, ktools could not detect his backup because backup is done with older version of ktools.  no, the older file can be detected fine with the new update. the new backup that I did after update was the corrupted one
|
|
|
|
|