(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
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!
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
Coolty said:
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!
Click to expand...
Click to collapse
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
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.
Click to expand...
Click to collapse
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
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
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.
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.
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.
red02 said:
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.
Click to expand...
Click to collapse
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?
Coolty said:
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.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!
steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
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
Coolty said:
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?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425
I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)
Coolty said:
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
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?
steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...
ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..
waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.
Hello Community,
I tried to install custom recovery using this manual "wiki.cyanogenmod.org/w/Install_CM_for_serranoltexx" (<- cannot use the link function, because it's my first post). I followed every step. At point 9 I have to make commands using the cmd. Unfortunately the result is an Error:
Failed to access device. libusb error: -12
I had two insecurities while following the manual:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
To point 5: I deinstalled Kies and the device driver in the Windows operating system. Since I've done this, there are appearing two devices in the zadig.exe when I connect my S4. I installed the zadig driver for both of them.
Im using Windows 7 x64
I hope someone can help me, for this moment I don't know what to do further...
greets
Dr. Bob! said:
At point 4 I had to rename the recovery image but I'm not sure what the recovery image is. What I downloaded was a .tar.md5 file within a .zip. Do I have to rename the .zip or the .tar.md5? The renaming causes a change of the file type and I cannot really understand, why they didn't put the right file in that .zip at the beginnig...this step is a bit confusing
Click to expand...
Click to collapse
I don't know about the libUSB error, and I haven't modded a Galaxy S4 mini, but I have installed CM on Galaxy Player. The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
I flashed the Galaxy Player with Odin 3 v. 3.04, after having installed Kies to have the drivers installed. The Player showed in Odin with something like "ID:0 COM"; I then clicked on the "PDA" button, then pointed to the tar.md5, and clicked flashed, and it worked.
Here are my 2 cents :^)
Is your phone rooted? If rooted already it easy! For the most noob method, install ROM Manager from https://play.google.com/store/apps/details?id=com.koushikdutta.rommanager and ROM manager will install the CWM for you. From there, its pretty simple.
If it not rooted, that the first thing you'll have to do.
fdelente said:
[...] The tar.md5 has to be extracted from the zip; it is in fact a tar.gz file (tar archive compressed with gzip), but you don't have to rename it.
Click to expand...
Click to collapse
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
TNCS said:
If it not rooted, that the first thing you'll have to do.
Click to expand...
Click to collapse
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Dr. Bob! said:
I found out, the .tar.md5 is also a compressed file. If I extract it, I get a file called "recovery.img". At this point it's not very clear what to do. Because there is nothing to rename. And even if you are right, the tutorial would be also wrong.
This is for installing the custom recovery, that's is the root, isn't it? I had the problem that Heimdall doesn't gets access to the device (lubusb error: -12). It's probably a driver problem.
However, I solved the problem by doing another method using odin. The root was succesfull. Afterwards I will flash the custom rom.
Click to expand...
Click to collapse
No, custom recovery is not rooting. Not my favourite method but it easy enough, try this: http://www.kingoapp.com/
It a universal root for JB and it will prompt you to install CWM afterwards.
After installing the CWM I rooted the device. I succesfully installed Canogenmod 10.2.1. The Tutorial says explicit, that it only helps for 10.2.x but I want to install the Nightly version which is running at CM version 11. If I could, I would ask this questions in the threat but I'm not allowed yet to post in the developers section. "forum.xda-developers.com/showthread.php?t=2474054"
Can I use this tutorial for flashing CM version 11?
Hey everyone, I've made this thread to help people like me who face "(assert failed: getprop("ro.product.device" =="GT-S5360" error)" aka Status 7 error" while flashing custom roms/kernels.
Before we begin, here is a little introduction about it :-
Basically, Status 7 error is caused while the updater script of the Custom Rom/Kernel checks to see if the phone model of your phone is compatible with the ROM/Kernel you are installing, called “asserts”.
In a nutshell, "Asserts" is a safety valve which prevents you from installing a Rom/Kernel meant for another device on your phone. Say, a Galaxy S rom on Galaxy Y and vice versa.
A Status 7 error generally arises due to the carelessness of the developer of the Rom/Kernel.
Now, moving onto how to fix it. There are a no. of methods on internet about fixing Status 7 errors. Here, i'm going to list the one's that i think are easy and work most of the times.
Method 1 :-
Here, i'm going to cover the most common method of removing the asserts from updater script. This method works almost 100% of the times.So, lets start right away !
Step 1. Copy the ROM zip file to your
computer and extract it using your favorite unzipping software (WinRar recommended)
Step 2. Once unzipped, browse to the
META-INF/com/google/android
directory. You will find two files called
“update-binary” and “updater-script”.
Step 3. Rename “updater-script” to
“updater-script.txt” and open with your
favorite text file editor.
Step 4. Get rid of the line starting with “assert” to next semi-colon. Usually
this is the first line or one of the first
lines at the top of the text file.
Step 5. Save file.
Step 6. Rename “updater-script.txt”
back to “updater-script”.
Step 7. Rezip all the files you’ve
unzipped.
Step 8. Copy the new, edited zip file to your phone.
Step 9. Try re-installing ROM, now it
should install fine without Status 7 error.
You can do this even on your phone with root explorer
Method 2 :-
Now this method is tricky one ! This method can be helpful for people who are willing to try out custom roms/kernels but have regional varaiants of a phone. For example, Seven variations of the model Galaxy y exist:
S5360 L , S5360 B (Brazil), S5360 T ,
S536 3, S536 7 , S536 8 , and S536 9 .
So, basically this method is based on editing the build.prop of your phone.
However,this method is still untested so try it on your own risk and responsibility !
Open your build.prop.Search the following lines in build.prop having the model name and change them as shown below :-
ro.product.model=GT-S5360
ro.product.name=GT-S5360
ro.product.device=GT-S5360
ro.build.product=GT-S5360
Save the changes.Set the permissions and Reboot and now you may be able to install the rom !
NOTE :- Incase you're using this guide for flashing cm11, you'll have to change your device name to totoro.