Develop Bugs

[S+ Kernel] - Rooted stock kernel for XWJVZ (2.3.6) - no mods, only root + SU

Hello everyone,
Stock+ Team ($omator & Grooby) are proud to bring you the latest rooted kernels based on samsung stock kernels that you may find in ROM by Samsung.
Why should i use this kernel?
Our kernels are uber-minimal modification of stock kernel used only for rooting (no custom recovery is installed). So the kernel it's like stock just rooted, and there is small chance (or any chance) that it will be detected as modified by service center at the first look
Here's the latest rooted kernel for I9000XWJVZ_I9000OXAJVT_OXA (2.3.6) which just leaked !
ROOTED! I9000XWJVZ - Gingerbread (2.3.6) - CL: 762604 - B.Date: Fri Nov 25 KST 2011 - Download HERE!
Instructions:
1. Flash zImage.tar of choosen kernel using odin (you will find it in package)
2. enable usb debugging in settings->applications
3. while still connected and odin/kies is turned off, run RUNME.BAT (also in package)
4. Install latest Superuser.apk from market!
5. Profit!
Enjoy!
PS: Remember to join our service at http://samsung-updates.com/ or follow us on twitter at twitter.com/SamsungUpdates
"One stock+ Team to rule them all, One stock+ Team to root them, One stock+ Team to beat them all and in the happiness bind them" - Toolkien ;P

Would be nice with CWM

Perka, you know that i got only two hands right? hehehe, either way, the we (stock+) are trying to make roms as clean as possible to original the same with kernel, we don't do tweaks, custom recovery etc. only root and thats it.

direct link:
http://alerson88.dl.rapidbaz.com/kivlC/ROOTED_GTI9000_I9000XWJVZ_stock+.ZIP

<ID:0/036> Added!!
<ID:0/036> Odin v.3 engine (ID:36)..
<ID:0/036> File analysis..
<ID:0/036> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
i am not able to flash? its always the same when i attemt it! some help please

Turn off all KIES processes,
connect phone, run odin, place zImage.tar as PDA and click flash

works fine..
worked fine for me,thank you.

Grooby said:
Turn off all KIES processes,
connect phone, run odin, place zImage.tar as PDA and click flash
Click to expand...
Click to collapse
worked thx.

Doesn't work
Hello!
I flashed zImage, after reboot while USB debugging, and Kies off, I run RUNME and got a lot of: "adb server is out of date ... killing".
Eventually when running Superuser nothing happened, Titanium says that I'm not rooted.
Please help

Before running runme.bat
a) reboot PC
b) kill all KIES and ADB processes
c) run, runme.bat

please new direct link

[SOLVD] Restoring 2.3.4 using a stock rom, problem has become complex (to me, anyway)

I've been wrestling with this for the last 10 hours (thank goodness for days off) and I think I'm on the edge of straightening things out. Or making them worse. Some Gio guidance is desperately needed.
I got my Gio this past January. Solo Mobile (Canada, Bell-owned) s5660M, Gingerbread 2.3.4. It worked perfectly right out of the box. I didn't mod it beyond rooting it.
This past weekend I bumped into this video I stumbled into this Youtube video
/mq8_GwLTrLk
demonstrating how to upgrade the Gio to 2.3.6. I did it without doing a CWM backup and everything ran fine afterwards except the GPS couldn't find a signal and the network would drop after the phone had been locked for a while. I didn't like this and today wanted to undo it.
Without going into a long story, I tried to do a factory reset and the phone has been boot-looping ever since. I installed CWM And the phone is behaving normally other than the boot loop.
I do NOT have a CWM backup. I didn't become aware of CWM until too late. What I have been able to find is an apparent recovery folder from sammobile.com that is specifically marked for the Bell Gio. My problem is that I don't quite know what to do with the contents, pictured below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have also installed Android SDK and am able to use adb through CMD. Adb can see the phone if I boot into CWM's Recovery.
What do I do now? I just want a working phone out of this. I have no complaints about returning to 2.3.4 or taking another, proper shot at 2.3.6 - the video says nothing about factory resets before and after (something I learned here, today in the Big Thread For Noobs,) which might be responsible for my glitches. I don't know.
I'm not in a rush, but it would be nice to have a resolution sooner rather than later. It would be a shame to brick this phone.

You flash the tar.md5 through Odin.
You should be able to find a guide for using Odin by googling it or looking here on XDA
Sent from my HTC Sensation

The zip file you've found on sammobile.com contains an Odin-flashable tar "One Package" style file. Flash that with Odin and you should be good to go.
Before someone leaked sammobile an "official" Samsung image, here's how we managed:
http://forum.xda-developers.com/showthread.php?t=1233719
By the way, there's no point in doing two factory resets in a flash operation.

Odin is what I used to do the original flash to 2.3.6, as per the now mostly-hated video.
If there's a tar.md5 inside that zip it's hidden from me. Only 4 files have extensions, two with .img and two with .rfs. The image with the filter-dodging link was to show those files.
armss 18.36mb
arm11boot 448kb
boot.img 6.296mb
csc.rfs 13.220mb
mibib 768kb
oemsbl 554kb
qcsbl 360kb
recovery.img 6.7mb
system.rfs 170.832mb
Any idea what program these files are built by/meant for?
Thank you both for replying. Fortunately, the download link for the ROM in Darkshado's linked thread is still working. I'm downloading it now. It's bedtime now. Hopefully, I'll be posting happy news in the morning.
Thanks again.

Yoqui said:
Odin is what I used to do the original flash to 2.3.6, as per the now mostly-hated video.
If there's a tar.md5 inside that zip it's hidden from me. Only 4 files have extensions, two with .img and two with .rfs. The image with the filter-dodging link was to show those files.
armss 18.36mb
arm11boot 448kb
boot.img 6.296mb
csc.rfs 13.220mb
mibib 768kb
oemsbl 554kb
qcsbl 360kb
recovery.img 6.7mb
system.rfs 170.832mb
Any idea what program these files are built by/meant for?
Thank you both for replying. Fortunately, the download link for the ROM in Darkshado's linked thread is still working. I'm downloading it now. It's bedtime now. Hopefully, I'll be posting happy news in the morning.
Thanks again.
Click to expand...
Click to collapse
you already extracted the one-package, so I guess you still have that one, that's where these files are inside.
flash that one, look for a tutorial on how to flash one-packages

Read this page: Step by Step Flashing Procedures with Multiple binary files or Single binary files.

I'm about to start the flashing shortly, I just wanted to post this now for others with a similar problem who might find this thread in the future.
I found a big, basic mistake I was making with the downloaded files. When I unzipped the sammobile package, it created another archive and a .dll. These two items appeared in Details view in Windows Explorer and the file name of the unpacked archive is long enough to be overlapped by the Date Modified column. This overlap is hiding its extension, which is .tar. I've been looking at it, seeing the WinRAR icon of stacked books and assuming it was another .rar. The Type column also says WinRAR archive, reinforcing the false presumption.
That's why I was previously saying that there was no .tar in the Sammobile package.
A simple mistake, but it put everything on hold and delayed fixing this mess for hours. If I hit 10 posts before this is up, I'll post relevent screenshots. :doh:

Yoqui said:
I'm about to start the flashing shortly, I just wanted to post this now for others with a similar problem who might find this thread in the future.
I found a big, basic mistake I was making with the downloaded files. When I unzipped the sammobile package, it created another archive and a .dll. These two items appeared in Details view in Windows Explorer and the file name of the unpacked archive is long enough to be overlapped by the Date Modified column. This overlap is hiding its extension, which is .tar. I've been looking at it, seeing the WinRAR icon of stacked books and assuming it was another .rar. The Type column also says WinRAR archive, reinforcing the false presumption.
That's why I was previously saying that there was no .tar in the Sammobile package.
A simple mistake, but it put everything on hold and delayed fixing this mess for hours. If I hit 10 posts before this is up, I'll post relevent screenshots. :doh:
Click to expand...
Click to collapse
if you look good its .tar.md5 , so that makes a huge difference with .rar

I just finished the flash. Odin went through all 9 steps without reporting errors. Then it initiated a reboot. The phone began bootlooping again. Odin reported PASS!!! and finished. I gave the phone 5 minutes and then pulled the battery to stop the bootloop, waited 30 seconds and then tried starting it again. It's still bootlooping.
Suggestions on what to do next?

U have done a ful whipe and factoryreset?

Wipe as in format the phone's drive? No.
Factory reset - yes, several times from the Recovery menu and it bootloops each time.

Yoqui said:
Wipe as in format the phone's drive? No.
Factory reset - yes, several times from the Recovery menu and it bootloops each time.
Click to expand...
Click to collapse
From recovery wipe cache and Dalvik cache.
After that it can take a while before the foon boots.(about 5.min like a boot-loop)

Cache partition and Dalvik cache have been wiped. Should I try a normal reboot now or do another Odin flash of 2.3.4?

I tried a normal reboot. It went into bootloop. I let it run for 10 minutes but it did not enter the OS.
I pulled the battery, waited a minute, went back into CWM, wiped both caches again and then did a factory reset. It complained about not being able wipe the SD card but otherwise seemed fine. Rebooted and it bootlooped. Again, gave it ten minutes and then pulled the battery.
Cleared the caches again, factory reset again, then flashed the Bell 2.3.4 with Odin.
Here is the contents of the Odin message window:
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> big partition size!!
<1> mibib download..
<1> 1/8 Finished.
<1> qcsbl download..
<1> 2/8 Finished.
<1> oemsbl download..
<1> 3/8 Finished.
<1> amss download..
<1> 4/8 Finished.
<1> arm11boot download..
<1> 5/8 Finished.
<1> boot.img download..
<1> 6/8 Finished.
<1> recovery.img download..
<1> 7/8 Finished.
<1> system.rfs download..
<1> 8/8 Finished.
<1> reset pda..
<0> Started Timer
<1> Close serial port and wait until rebooting.
<1> PASS!!!
<0> Destroy instant..
<0> Killed timer
After 5:08 it declared PASS. But the phone was stuck in bootloop. As before, I gave it ten minutes and pulled the battery.
Time to try an adb recovery reboot...

Before using adb (all this reflashing feels like banging my head against a wall) I did some more searching and found this, also on xda-developers:
http://forum.xda-developers.com/showthread.php?t=1619401
Peteragent5 said:
Ohhhhh that's right! When you come from the new roms these days, it formats your device to EXT4. So if you try to go back to RFS (Stock), the phone bootloops.
Click to expand...
Click to collapse
Could this be what's happening to my Gio?

Yes..
There was a method to add empty rfs partitions with odin but I never used it...
Sent from my GT-S5660 using xda premium

http://madteam.co/news/2011/10/flash-samsung-stock-rom-over-cm-guide/
Can someone comment/confirm if their file is usable with a Gio. It appears to be what I'm looking for but I don't want cause more harm because of a compatibility issue. Would someone please download and look at the file and confirm that it only does the partition modification that they promise?

Do you use firmware special for the s5660M or for the GT-s5660?

If you mean, "Does Bell use special firmware?" I don't know.
And I think I've found the last piece of the puzzle.
http://forum.xda-developers.com/showpost.php?p=25328527&postcount=5
Darkshado said:
If you want to reformat your /data and /cache partitions to RFS, here are empty RFS images you can dd into place.
Click to expand...
Click to collapse
I've downloaded his file. What does dd mean and how do I do it?
[update]
I've found most of the information I think I need. I'll lay it out here, both for confirmation and to have a clear step-by-step for the next person who comes along with this kind of problem.
The dd command is like a pipe that allows data to be moved to and from areas of the phone's memory that you aren't normally able to access. You first have to run adb.exe within a CMD window, confirm it can see the phone and then start a shell. Then you type in the dd command(s).
Run adb.exe.
Type "adb devices" [no quotes] to confirm it can see the phone.
Type "adb shell" [no quotes] to launch a shell. A "$" will appear to indicate that a shell is running.
It feels good to be finally nearing the end of this. Do I put Darkshado's two rfs files into same folder as the adb.exe (to make them easier to find?) And what command(s) do I use to write them to the phone?

I knew I had explained this elsewhere on XDA...
Darkshado said:
To reflash an RFS partition into place, you could use the dd command (carefully). Here's an empty RFS formated /data partition.
Extract to your SD card and use the following command:
dd if=/sdcard/data.rfs of=/dev/block/stl13 bs=4096
Click to expand...
Click to collapse
Also read this thread if you haven't yet.
The /cache partition is stl14.
Good luck,
Darkshado

Problems with root and Clockwork recovery

Hello,
I've just bought my new Samsung Galaxy Gio, and on it I had Android 2.3 version.
I performed a Root on my phone, and after that, I updated the Android version with Kies and now I have Android version 2.3.6, Baseband version S5660XXKT6, , Kernel version 2.6.35.7-perf-CL1047966 [email protected]#1 Build number GINGERBREAD.XXKTK
I've downloaded Clorkwork mode recovery and I to installed it, but after that I did a recheck to see if my phone is still rooted and with the help of Root Checker Basic app it says that the device does not have proper root access.
I've tried to root it againg but in recovery, and it's showing these messages : E:Can't mount /cache/recovery/command' and 'E:Can't open /cache/recovery/last_log',
I don't know what to do know, all that I want is to have a proper root on my phone and CMM recovery nicely installed.
Did I do wrong my rooting my phone before updating it to 2.3.6?
How can I make it ok?

arina_arina said:
Hello,
I've just bought my new Samsung Galaxy Gio, and on it I had Android 2.3 version.
I performed a Root on my phone, and after that, I updated the Android version with Kies and now I have Android version 2.3.6, Baseband version S5660XXKT6, , Kernel version 2.6.35.7-perf-CL1047966 [email protected]#1 Build number GINGERBREAD.XXKTK
I've downloaded Clorkwork mode recovery and I to installed it, but after that I did a recheck to see if my phone is still rooted and with the help of Root Checker Basic app it says that the device does not have proper root access.
I've tried to root it againg but in recovery, and it's showing these messages : E:Can't mount /cache/recovery/command' and 'E:Can't open /cache/recovery/last_log',
I don't know what to do know, all that I want is to have a proper root on my phone and CMM recovery nicely installed.
Did I do wrong my rooting my phone before updating it to 2.3.6?
How can I make it ok?
Click to expand...
Click to collapse
i think you are wrong with the step that you performed..
after you upgrade your firmware,root access was lost,so you have to root it again before install the CWM cz root file can only flashed via stock recovery..
to fix it just install stock recovery again (search for that in development forum),root the device and install the CWM again..
CMIIW
Sent from my GT-S5660 using Tapatalk 2

Step is :
1. Upgrade to latest
2. Install Root From stock recovery
3. Install CWM
4. Upgrade to custom...

Many thanks for the answers, but how do I install stock recovery? I didn't find details or I don't get them. Please explain,

arina_arina said:
Many thanks for the answers, but how do I install stock recovery? I didn't find details or I don't get them. Please explain,
Click to expand...
Click to collapse
Have a look here: http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2
You can download the stock recovery and flash it via Odin.

No need for the stock recovery.
However, the stock Samsung ROM uses RFS and most CWM builds out there are meant for ext4 partitions.
Get a proper CWM, along with ChainsDD's super user zip and you'll be good to go.

Darkshado said:
No need for the stock recovery.
However, the stock Samsung ROM uses RFS and most CWM builds out there are meant for ext4 partitions.
Get a proper CWM, along with ChainsDD's super user zip and you'll be good to go.
Click to expand...
Click to collapse
So, I don't need to stock recovery?
Where can I fiind a good root zip for my phone???? After that, what CWM should I use? Please answer because my phone is working really slow and I can't root it for good! :crying:

arina_arina said:
So, I don't need to stock recovery?
Where can I fiind a good root zip for my phone???? After that, what CWM should I use? Please answer because my phone is working really slow and I can't root it for good! :crying:
Click to expand...
Click to collapse
And your PM while I'm at it.
Hello,
I've already posted a new thread and I didn't get the right answer...
I just want to root my phone again and I can't find the propper zip for android 2.3.6, and also I don't know what RFS means,
I know how to install a stock ROM, but before that I need to have my phone rooted and CWM installed .
Sorry for the many questions,
Good day!
Click to expand...
Click to collapse
Keep the conversation in the thread. We're lacking a bit of information...
How did you root the first time, prior to the official Kies update?
Remember, in most situations, official updates will remove root, simply because they completely overwrite the /system partition where your su binary and Superuser.apk reside. You need to put those back, either with CWM or by using an exploit of some kind, SuperOneClick being a very handy tool in this scenario. (It uses the different included exploits to gain a temporary root shell, remount the /system partition in read-write, pushes the binary and the apk, then sets the proper ownership and permissions to them. In contrast, CWM is already rooted without any exploits, but can only be installed from a live and rooted device, or Download Mode, or for some other devices with fastboot and an unlocked bootloader.)
RFS: Robust FAT File System. A Samsung proprietary file system format used in many mid-range, older devices such as the Gio. Deprecated in newer models, which favor ext4. Similar to good old FAT32, but adds *nix style file permissions support amongst other features. For this reason RFS images may be read but not safely modified on most *nix systems and with some Windows based programs. Modified ROMs enable ext4 support on the Gio as well. Switching back and forth between ext4 and RFS is possible, but that is beyond the scope of this post.
This file system also adds a little gotcha to CWM not found in ext4-based devices. Some CWM builds are meant for use with RFS, others with ext4. I'd avoid those claiming support for both if only because they're not very clear in which format they're working for a given operation.
I'm going with the idea that you want an essentially unmodified, Samsung stock ROM with CWM and root, and that you've only flashed over recovery since updating, or that you've reflashed the whole phone to stock with Odin:
Get the real deal ChainsDD "official" superuser zip file for ARM devices from androidsu.com and put it on your MicroSD card.
Find an RFS-compatible CWM image (iirc Phiexz and Hyriand both have built such recoveries) and flash it with Odin.
Reboot in recovery, and mount the /system partition manually prior to installing the superuser zip. I'm pretty sure the mount command in the updater-script will not work since it assumes an ext4 file system.
While you're at it double check that the files are there with adb shell and have the proper permissions. If the superuser zip installation has failed for some reason you could always manually push the two files, and chown/chmod them like the script does.
Reboot the phone, check for root.
You should be done!
Remember, root isn't a magical make-phone-go-fast panacea. The Gio isn't very fast to begin with, and there's only so much you can do...

Darkshado said:
And your PM while I'm at it.
Keep the conversation in the thread. We're lacking a bit of information...
How did you root the first time, prior to the official Kies update?
Remember, in most situations, official updates will remove root, simply because they completely overwrite the /system partition where your su binary and Superuser.apk reside. You need to put those back, either with CWM or by using an exploit of some kind, SuperOneClick being a very handy tool in this scenario. (It uses the different included exploits to gain a temporary root shell, remount the /system partition in read-write, pushes the binary and the apk, then sets the proper ownership and permissions to them. In contrast, CWM is already rooted without any exploits, but can only be installed from a live and rooted device, or Download Mode, or for some other devices with fastboot and an unlocked bootloader.)
RFS: Robust FAT File System. A Samsung proprietary file system format used in many mid-range, older devices such as the Gio. Deprecated in newer models, which favor ext4. Similar to good old FAT32, but adds *nix style file permissions support amongst other features. For this reason RFS images may be read but not safely modified on most *nix systems and with some Windows based programs. Modified ROMs enable ext4 support on the Gio as well. Switching back and forth between ext4 and RFS is possible, but that is beyond the scope of this post.
This file system also adds a little gotcha to CWM not found in ext4-based devices. Some CWM builds are meant for use with RFS, others with ext4. I'd avoid those claiming support for both if only because they're not very clear in which format they're working for a given operation.
I'm going with the idea that you want an essentially unmodified, Samsung stock ROM with CWM and root, and that you've only flashed over recovery since updating, or that you've reflashed the whole phone to stock with Odin:
Get the real deal ChainsDD "official" superuser zip file for ARM devices from androidsu.com and put it on your MicroSD card.
Find an RFS-compatible CWM image (iirc Phiexz and Hyriand both have built such recoveries) and flash it with Odin.
Reboot in recovery, and mount the /system partition manually prior to installing the superuser zip. I'm pretty sure the mount command in the updater-script will not work since it assumes an ext4 file system.
While you're at it double check that the files are there with adb shell and have the proper permissions. If the superuser zip installation has failed for some reason you could always manually push the two files, and chown/chmod them like the script does.
Reboot the phone, check for root.
You should be done!
Remember, root isn't a magical make-phone-go-fast panacea. The Gio isn't very fast to begin with, and there's only so much you can do...
Click to expand...
Click to collapse
Thanks for the answers:
After I bought the phone, I've rooted it with an update.zip which I found on google. It worked and my phone was rooted. After that, I updated through KIES to 2.3.6 and then I noticed that my phone wasn;t rooted anymore. I should've read firs the instructions I found on xda forum, but I was too eager on updating and playing with this phone.
From your explanations I understand that I should do the following:
- install superoneclick
- find a good superuser app
- install cwm.
Am I right? I originally thought that I should install a root zip file again and then cwm....

Nope, reread the second to last paragraph, it's: CWM, then su.zip. No need for SuperOneClick this way.
Or, just use SuperOneClick and leave the stock recovery as is.
Sent from my Nexus S using xda app-developers app

Darkshado said:
Nope, reread the second to last paragraph, it's: CWM, then su.zip. No need for SuperOneClick this way.
Or, just use SuperOneClick and leave the stock recovery as is.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
I searched for a propper CWM and I couldn't find it...where can I find CWM for android 2.3.6?

The Android version you're using is unrelated to the CWM version. So the same 5 or 6.something will work with GB, ICS and JB.

Well, I've downloaded Odin and the S5660M_CWM-5.0.2.7_ext4+rfs_feb_23_12.tar.md5 file which I found on this thread : http://forum.xda-developers.com/showpost.php?p=20896513&postcount=2
I switched to downloading mode, connected the phone with the pc and started the cwm installation through Odin, but after 50 minutes nothing happens and it's stuck on this :
Download Start...
<0> Create File...
<1> StartThread Detected : 1
<2> StartThread Detected : 0
<3> StartThread Detected : 0
<4> StartThread Detected : 0
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
<1> setup connection...
<1> odin mode.. check plcatform verification.
<1> VerifyPlatform:V0, P0,R0
<1> START!!!
<1> set download environment.
<1> big partition size!!
<1> recovery.img download..
What did I do wrong?
Did I downloaded the wrong CWM file for my android 2.3.6 version?
Did I downloaded the wrong ops file?
If so, where are the corret CWM and ops files?
Please answer!!!

[Q] How do I restore Samsung official firmware?

Hello,
I have a rooted Galaxy Gio (GT-S5660) with CWM and CM10.1 (from
Maclaw). I now need to restore it to factory firmware,
but am running into a brick wall no matter what I try.
I have downloaded S5660XXKTK_S5660COVKS1_COV.zip and tried with
Odin but that fails (don't remember the error message). And
anyway, it seems really unnecessary to boot into Windows to do
this, one should be able to do it all from Linux.
Is there any way to restore factory firmware using adb/fastboot?
adb connect to the phone etc., but fastboot doesn't work, it just
gets stuck in the "< waiting for device >" state.
(Yes, of course I run the adb/fastboot commands as root.)
I haven't found any tutorials/howtos on how to do this in Linux,
can anyone write one or point me in the right direction?
Or, if Odin is the only way, what files do I need to download to
make it all work? Obviously S5660XXKTK_S5660COVKS1_COV.zip isn't
enough.
I have tried the instructions found at android.gs, androidaddition.com
and mobotechie.com (seems I'm not allowed to post links...) but
nothing works.
Thanks,

Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Sent from my GT-S5660 using Tapatalk 2

Gyovany96 said:
Have u tried with .ops file in odin ?
U extract S5660XXKTK_S5660COVKS1_COV.zip , right ?
Click to expand...
Click to collapse
No I did not extract the S5660XXKTK_S5660COVKS1_COV.zip , I've assumed it's supposed to be used as-is, just like custom ROMs.
But there is no .ops file in the archive:
Code:
$ unzip -t S5660XXKTK_S5660COVKS1_COV.zip
Archive: S5660XXKTK_S5660COVKS1_COV.zip
testing: S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 OK
testing: SS_DL.dll OK
No errors detected in compressed data of S5660XXKTK_S5660COVKS1_COV.zip.
And no .ops file in the .tar.md5 file within the archive either:
Code:
$ unzip -xp S5660XXKTK_S5660COVKS1_COV.zip S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar.md5 | tar tvf -
-rw-rw-rw- a.oldak/0 18784256 2012-03-04 09:18 amss
-rw-rw-rw- a.oldak/0 459132 2012-03-21 09:40 arm11boot
-rw-rw-rw- a.oldak/0 6451200 2012-03-21 09:40 boot.img
-rw-rw-rw- a.oldak/0 19116032 2011-10-14 15:08 csc.rfs
-rw-rw-rw- a.oldak/0 786432 2012-03-21 10:11 mibib
-rw-rw-rw- a.oldak/0 566888 2012-03-21 10:11 oemsbl
-rw-rw-rw- a.oldak/0 368640 2012-03-21 10:11 qcsbl
-rw-rw-rw- a.oldak/0 6864896 2012-03-21 09:40 recovery.img
-rw-rw-rw- a.oldak/0 212430848 2012-03-21 09:40 system.rfs
Now what?

http://www.4shared.com/rar/ttIilfrh/Odinv442GIO_v10ops.html
Put .tar.md5 file in one package and flash. Don't forget .ops file
Sent from my GT-S5660 using Tapatalk 2

Gyovany96 said:
URL removed since I'm a new user and as such not permitted to post links...
Put .tar.md5 file in one package and flash. Don't forget .ops file
Click to expand...
Click to collapse
So, I'm supposed to extract the .tar.md5 file from the .zip file, separately download a .ops file from some completely other site (riddled with ads and popups and requiring registration, btw), and create a new .zip file containing the .tar.md5 file and the .ops file? Is that correct, or do I need to bundle more files into the new .zip file?
And in Odin (version 3.07), should I add the file as a PIT, Bootloader, PDA, PHONE, or CSC?

1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration http://hotfile.com/dl/140235732/ec749d2/?lang=ro
Sent from my GT-S5660 using Tapatalk 2

Gyovany96 said:
1. Put phone in download mode
2. Use odin 4.42 (is in archive I gave u)
3. Click on ops and navigate to .ops file ( also it's in archive )
4. Check one package file , then click on "one package file" and select .TAR.MD5 file
5. Fash !!
P.S. I am on mobile and I'm not sure about buttons NAME...I hope u can do it
EDIT : Here another link without registration (removed as I'm not allowed to post links...)
Click to expand...
Click to collapse
Well, that almost worked. I put the phone in download mode, connect it to a USB port, start Odin, the phone is detected as COM8, I add the .ops file, check "One Package" box, and add the .tar.md5 file. Odin has up until this point replied with this in the Message box:
Code:
<1> Added!!!
<1> Detected!!!
Check MD5 Filename : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Open File Name : S5660XXKTK_S5660XXKT6_S5660COVKS1_HOME.tar
Check MD5 ...
Tail MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Image MD5 : 7BCD76F2AA8BB985AC91E3DE94CFA784
Check MD5 ... ok
The I click the Start button in Odin. The Message box is cleared, and this appears:
Code:
<5> StartThread Detected : 0
<6> StartThread Detected : 0
<7> StartThread Detected : 0
<8> StartThread Detected : 0
And after a few more seconds, this line is added:
Code:
<1> --- cannot open the usb serial port. code: 32
It doesn't matter whether I start Odin as Administrator or a regular user, the phone is detected but the "error 32" appears when trying to flash. The phone is the only thing connected to any USB port.
Any ideas?

1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Sent from my GT-S5660 using Tapatalk 2

Gyovany96 said:
1.Usb debugging was checked ?
2.You have samsung drivers installed ?
Click to expand...
Click to collapse
1. USB debugging was not checked. Is it supposed to be?
2. Kies was installed, I guess perhaps drivers come along with that? I just deinstalled Kies, and now Odin doesn't detect the phone any more. Should I install just some drivers and not Kies? If yes, which drivers, where do I find them?

Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Sent from my GT-S5660 using Tapatalk 2

Gyovany96 said:
Kies will install drivers automatically.
Hmm....I had this problem with an I9000 and solved it with a ROM than contains 3-files package.
Search a ROM with 3 files
EDIT: If your phone can still boot check Usb debugging and then try flash again
Click to expand...
Click to collapse
The phone can still boot, and USB debugging is activated.
To solve the error code 32 problem, people on forums suggest killing Kies using the Task Manager, and trying out different USB ports and making sure I use the USb cable that came with the phone. Well, I have tried reinstalling Kies, rebooting, deinstalling Kies but keeping the USB drivers, different USB cables and different USB ports, but no luck... nothing works. The phone is not detected by Odin any more.
It is detected by adb under Linux, though, so USB is still working.
When searching for a 3 file ROM I found the pages
www modaco com /topic/361399-latest-odin-309-odin-185-odin-183-all-versions-samsung-rom-flashing-tools/
and
www modaco com /topic/361286-18072013-latest-samsung-usb-drivers-for-mobile-phones-15270-win-87xp-adb-fastboot/
so I downloaded the latest Samsung USB driver, and made sure I was using an Odin version compatible with my phone.
And still, now after reinstalling Kies, Odin does not even detect the phone any more. Windows chimes when the phone is plugged in, but it does not appear in Odin, regardless of whether I start Odin before or after plugging in the phone, and regardless of whether I run Odin as administrator or not.
Seriously, is there no way to do all this using adb and fastboot under Linux? I get more and more homicidal when I have to spend time using Windows.

I sent you PM
EDIT : http://hotfile.com/dl/106492222/cc53f0f/S5660_XXKB9_OXXKB8.rar.html download this
http://droidangel.blogspot.ro/2011/05/procedure-how-to-flash-updateupgrade.html this is tutorial

Gyovany96 said:
I sent you PM
EDIT : (URL removed as I don't have permission to post them... moronic forum rules...) download this
(URL removed as I don't have permission to post them... moronic forum rules...) this is tutorial
Click to expand...
Click to collapse
Well, I finally managed to flas in Samsung stock firmware.
The instructions on the page
nguyenkieuhung1984 blogspot se /2012/01/how-to-upgrade-samsung-galaxy-gio-s5660_13.html
comes closest to describing what I did, except I used S5660XXKTK_S5660COVKS1_COV.zip and GIO_v1.0.ops .
I don't really know what I did to resolve the USB connections problems, but hey, when using Windows it's all trial-and-error, right?
First, install, deinstall and reinstall Kies a couple of times, and inbetween installs try the Odin procedure described in the nguyenkieuhung1984 blog mentioned above. And download the very latest Samsung USB drivers (I used 1.5.27.0) and install that. Repeat these steps until you feel like vomiting all over your keyboard. Oh, and install Odin 4.42 too while you are at it. And keep SS_DL.dll and GIO_v1.0.ops in the same folder as the Odin executable file. I don't know if it matters, but getting Windows to work is 80% magic, 15% luck and 5% skills, so why not?
Then reboot to Linux, read mails, surf, code, whatever is needed to regain sanity.
Reboot into Windows, install Kies again, including the bundled USB driver. After Kies has installed, verify that the Samsung USB driver version is still 1.5.27.0 and not whatever version came with Kies (I think Kies came with 1.5.23.0 ?). Anyways, 1.5.27.0 is what's on my system now, along with Kies 2.5.3.13043_14.
Start Kies and close it. Do NOT go into Task Manager to kill off any Kies processes; at least I didn't. Other tutorials tell you to, at least if you run into the error code 32 problem. Well, I didn't have that problem on my 30th attempt (on attempts 10-29 I did, though...).
Follow the steps on the nguyenkieuhung1984 blog mentioned earlier in this post, replacing filenames if needed (like I did, I mentioned that at the start of this post...).
The phone might now enter a reboot loop (mine did). Press and hold the Power and Home buttons to reboot the phone into the bootloader(?), and there you wipe settings and caches (two different wipes if I remember correctly).
The phone should now boot to stock firmware. Enjoy Android 2.3.6 or whatever Samsung ROM you selected.

It's recomended to "wipe data/factory reset" in recovery mode after you flash a stock ROM. But, enjoy ROM finally
Sent from my GT-S5660 using Tapatalk 2

[GUIDE] External wifi support on SGH-I747

First of all, I would like to thanks XDA crew and registred user for keeping this site alive and healthy !!!! :angel: Without them i could never be good enough to realize this thing.... Back 3 years ago it was a dream to do pentesting on android device !! Now it's reality (again) :angel:
This is my first post on XDA so ....
NEEDED HARDWARE
A samsung S3 (d2att) SGH-I747
Alpha Network AWUS036H usb WIFI adapter (Tested) or any device that have a RTL8187 chipset (Not tested)
Amazon like for the alpha:: http://www.amazon.com/Alfa-AWUS036H...&qid=1382239471&sr=8-1&keywords=alpha+rtl8187
A Y usb OTG Cable : ( The WIFI adapter need 5V to operate)
Amazon link for the Y Cable : http://www.amazon.com/Micro-Cable-P...F8&qid=1382239653&sr=8-1&keywords=y+otg+cable[/I]
A 3500 mAh or more battery for 5V Output. (Take one made for charging cell)
BASE ROM INSTALL
(Make a backup !!!!)
I base my work on the stock rom and kernel from samsung. (Sorry for those who want a CM base)
So go to : http://forum.xda-developers.com/showthread.php?t=2388065 (Thks to loserskater for the rom !!!) and download the rom and copy it to sdcard. Boot to custom recovery. Go to Wipe menu, Factory Reset, Wipe Cache, Wipe Dalvik Cache.
Go back to main menu and chose : install zip from Sdcard, choose the zip that you put on your Sdcard and flash. Once finish reboot System.
CUSTOM KERNEL
You would need Odin mobile to flash custom kernel : http://forum.xda-developers.com/showthread.php?t=1347899
Download my custom kernel at : https://www.dropbox.com/s/4setym4cacc7ncu/boot.img?dl=0
Open Odin Mobile and hit kernel. Select the boot.img that you download and flash it !!!
Let Odin mobile flash and reboot phone. Now if everythings goes well, you are ready to chroot Kali linux and start using aircrack-ng and others tools !!! You need to reinstall busybox so go ahead !!!!
CHROOT KALI LINUX
Fat32 filesystem have a limit of 4 gig of file size and the chroot file of Kali linux need to be 5 gig and more...
First of all take out your Sdcard from your phone (Go to settings, storage and umount sdcard before take out). Insert it to SDHC adapter and put it in a Windows box. Copy the content of your Sdcard to a direcotry of your choice. Format the Sdcard to NTFS. And recopy back the content of the directory to the formated Sdcard.
Don't insert it back WAIT !!!
Return to your phone. Hit Google play store and Download Paragorn NTFS&HFS+ (its free). Install and open the app.
While your in Paragorn reinsert your SDcard and it should mount it. (Now you have support for 4 gig and more file)
Return to Play Store and download Linux Deploy and open it.
When you are in it, hit the arrow on down right corner :
Distribution : Kali Linux
Distrubution suite : Kali
Architecture : armhf
Installation type : File
Installation path : /pathtosdcard/kali.img
image size : 10000 (10 gig)
File system : Auto
User name : your choice
Desktop environnement : i choose Gnome
Select components : check everythings !!!
Allow SSH and GUI
Hit install
Wait a long time and take me more then one try before a clean install so be patient !!!
WORKING IN THE CHROOT ENVIRONMENT
Another go to Google play store and Download JuiceSSH
( Your SSH ip is write in Linux Deploy on the top left)
Open JuiceSSH and fill the new connection information
REMEMBER : You change your username so it should :
ssh <username>@<ip>
Default password is : changeme
Once your in Kali : plug everythings ( OTG Cable , battery and Alpha adapter to phone)
enter iwconfig command and you should see wlan1
ifconfig wlan1 up
airmon-ng start wlan1
*Bang monitor mode enable on wlan1
Victory !!!!!
Cheers my firend !!!!

Wow. Good work. I will definitely have to try this. Thanks!

Please update a rom for kitkat. Thank you