Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Samsung Galaxy Gio GT-S5660M Discussion - Rooted Stock ROM, Partition Mapping

OP Darkshado

25th August 2011, 02:51 AM   |  #1  
Darkshado's Avatar
OP Senior Member
Montréal
Thanks Meter: 474
 
997 posts
Join Date:Joined: Apr 2011
Donate to Me
More
(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)

Hello,

I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.

I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.

Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.

ROM development and deployment is going to be safer going forward.

I copied the blocks with the dd command as follows:

dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096

WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.

From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.

Here are the results:

Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.

/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition

/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read

/dev/block/stl6 Empty: contains only \xFF

/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read

/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.

GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)

Tutorial on flashing with Odin, with link for the appropriate version for our phone.

I've released my custom 5660M ROM, ArpegGioMod.

Goodbye,

Darkshado
Last edited by Darkshado; 15th February 2012 at 04:41 AM. Reason: Multiple changes.
The Following 7 Users Say Thank You to Darkshado For This Useful Post: [ View ]
25th August 2011, 05:21 PM   |  #2  
Junior Member
Thanks Meter: 2
 
27 posts
Join Date:Joined: Jan 2010
Wow,

Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.

I will be flashing this ROM back to my s5660m.

THANK YOU!

STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!

Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Last edited by Coolty; 25th August 2011 at 06:21 PM.
25th August 2011, 06:19 PM   |  #3  
Darkshado's Avatar
OP Senior Member
Montréal
Thanks Meter: 474
 
997 posts
Join Date:Joined: Apr 2011
Donate to Me
More
Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?

Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.

Good luck,

Darkshado
25th August 2011, 07:08 PM   |  #4  
Darkshado's Avatar
OP Senior Member
Montréal
Thanks Meter: 474
 
997 posts
Join Date:Joined: Apr 2011
Donate to Me
More
Quote:
Originally Posted by Coolty

STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!

Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!

Great! You just made my day!

About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.

Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.

I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.

Another, simpler solution would be to modify the OPS file to skip the CSC partition.

One question: did you re-tar each file individually for ODIN to take them?

CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.

Goodbye,

Darkshado
25th August 2011, 07:21 PM   |  #5  
Junior Member
Thanks Meter: 2
 
27 posts
Join Date:Joined: Jan 2010
Quote:

Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.

I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now

Quote:

One question: did you re-tar each file individually for ODIN to take them?

No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.

Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.
25th August 2011, 08:17 PM   |  #6  
Junior Member
Thanks Meter: 2
 
27 posts
Join Date:Joined: Jan 2010
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
25th August 2011, 09:12 PM   |  #7  
Junior Member
Thanks Meter: 0
 
2 posts
Join Date:Joined: Aug 2011
Step by Step guide for Noobs?
Hello,

My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?

Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?

Thanks a lot.
25th August 2011, 09:23 PM   |  #8  
Junior Member
Thanks Meter: 2
 
27 posts
Join Date:Joined: Jan 2010
Quote:
Originally Posted by red02

Hello,

My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?

Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?

Thanks a lot.

Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
25th August 2011, 09:40 PM   |  #9  
Junior Member
Thanks Meter: 1
 
13 posts
Join Date:Joined: Aug 2011
Quote:
Originally Posted by Coolty

I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.

if you could post it, that would be much appreciated!!
25th August 2011, 10:05 PM   |  #10  
Junior Member
Thanks Meter: 2
 
27 posts
Join Date:Joined: Jan 2010
Quote:
Originally Posted by steez003

if you could post it, that would be much appreciated!!

I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.

EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Last edited by Coolty; 25th August 2011 at 10:53 PM.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes