I've find an affordable solution so I've decided to modify the original thread in order to give immediately to all who reads the correct procedure.
Later on this message you can still see the original start of the thread, for future references.
________________________________
How to downgrade from Froyo 2.2.2 v3.4.2-177 to Eclair 2.1 v2.51.1.
Requirement:
- Defy Android 2.2.2 v3.4.2-177 (probably other versions also) flashed from the phone itself or from direct sbf original file and RSD Lite.
- Rooted. You can use SuperOneClick on both android version.
- Defy Recovery 1218 0326 signed.apk. you can find it here.
- A nandroid backup of the old Eclair system (made by yourself otherwise you can quite easly find one on the internet and on XDA)
- the original full sbf file of Eclair system (many are here) in order to create a fixed sbf or directly the fixed sbf.
- Moto Android Firmware Depacker V.1.2 a3.exe (a Windows executable that need Dot Net FX 2.0 and it's able to pack and unpack OEM sbf files).
- RSD Lite and obviously the USB Windows Moto drivers.
Before proceding you need to create or to obtain such called fixed sbf made from the same version you're going to downgrade, so from Eclair 2.51.1.
You can find such fixed sbf online but for safety I prefer to made it by myself. It's so easy.
1. open the original full sbf with Moto Android Firmware Depacker V.1.2 a3 and split to folder;
2. remove CG31.smg and CG39.smg
3. open the extracted folder (the same you've just removed the files) and compile files.
The resulting file is the fixed sbf file you'll need soon ;-)
The procedure:
1. Install drivers and RSD Lite on pc and test the driver. USB debug must be always OFF (exepted for the superonclick rooting procedure)
2. Root the Froyo, reboot, install Defy Recovery and push to the sdcard the nandroid backup of your Eclair. The backup dir should be placed here: /sdcard/goapkrev/backup/
3. open Defy Recovery app and tap recovery boot.
4. wipe data/factory (so your're gonna loose everything on Froyo. Make a backup before, if you want)
5. restore the nandroid backup of the Eclair system.
6. pay attenction to reboot and immediatly push power + vol up in order to go to the bootloader mode. Otherwise the boot will loop and you need to pull the battery off.
7. with RSD Lite flash the fixed sbf. Wait untill the automatic reboot ends, and RSD Lite tells you PASS.
You've done
The M logo is now white, the standard recovery is restored, the haptic feedback works and everything is Eclair
If you appreciate, a thanks is more than enought
________________________________
Original start of the thread:
I've decided to open a new thread because I still don't find a final, safe, topic on how to downgrade from the latest Froyo to Eclair.
There are many topic on it but seems there are a little confusion.
The XDA official topic on the Developers page called "SBF - Service Flash -files "READ THIS FIRST if you try to flash new stock sbf" says litterally:
If you have flashed direct Android 2.2 via sbf -->
No direct downgrade for all 3.4 Froyo beta ROMs to Android 2.1 or official Android 2.2
No direct downgrade for 2.51.1 and 2.59 Eclair
I do not know what a "beta" Froyo is, but I know that I was able to switch from Defy Android 2.2 Froyo OEM JRDNEM U3 3.4.2 164-003 BLUR France to MIUI and viceversa using RSD lite for Froyo and zip install for MIUI.
Or MIUI is not a "beta" as intended before, but the JRDNEM U3 3.4.2 164 was the OEM france edition.
In any case here my question, and my situation:
Question: what is the real safe way to downgrade from 3.4.2-177 en.it to 2.51.1 en.it ??
My actual situation: I have Froyo 3.4.2-177 en.it, and it was direct sbf flashed; but I have a copy of my previous Eclair 2.51.1 by. Nandroid.
Is that procedure correct and really safe?
________________________________
1. Boot from Froyo in advanced recovery, factory reset and dalvik erase and ...
2. restore a nandroid backup of my previous Eclair and ... reboot.
3. the reboot should loop because the partitions are different signed or the nandroid backup is not able to overwrite the froyo bootloader, right?? so ...
4. pull battery and push again while press volume + to go bootloader (this should work 100%?? any possibility of complete dead defy?? It's really possible to ALWAYS and in any conditions access bootloader in order to connect RDS lite?).
5. Flash with RSD Lite a fixed sbf, where that should means: open the OEM 2.51.1 sbf with MotoAndroidDepacker-1.2alpha3, erase CG31 and CG39, repack and that's a ready to work fixed sbf?? reboot
________________________________
After that my old Eclair should work even on a Froyo bootloader?
I need to downgrade only because I have all my configuration on the old system, and I would have the occasion to copy some configuration settings before going definitively to Froyo.
Is that downgrade safe or dangerous?
After the downgrade is it possible to direct flash back the original Froyo 3.4.2-177 sbf with RSD Lite like before?
Thank you in advance for all your kind reply.
That will work
SeaFargo said:
It's really possible to ALWAYS and in any conditions access bootloader in order to connect RDS lite?
Click to expand...
Click to collapse
Yes.
Until your phone will enter into bootloader mode ( volume up button before turning on ), you'll be able to flash via RDS lite.
Thank you, mpiekp
Thanks to carlo93, also.
But Carlo, my phone should always be able to load in bootloader mode? In other words, can I, with the mentioned procedure, corrupt the boot sector in such a way to NOT be able to boot in bootloader mode anymore?
or ... is there a way (so I can pay very very attenction to avoid it) to corrupt the bootloader mode?
I know that till I reach bootloader mode I always be able to flash with RSD Lite. But can I, working with roms (nandroids and sbf), be able to crash the bootloader mode so I can't reach it anymore or not?
SeaFargo said:
But can I, working with roms (nandroids and sbf), be able to crash the bootloader mode so I can't reach it anymore or not?
Click to expand...
Click to collapse
Maybe if something goes wrong while flashing a sbf via RSD Lite ( i.e. black out during a flashing, i hope this will never occur... )...
Otherwise there's no reason of being afraid .
Question for update
currently i m running cm7 rom for gingerbread. if i revoke back to original one . (i messed up big time cause i didnt get a chance to make a nanodroid backup of my own eclair ).. so i guess i have to follow ur tutorial to revert back to my eclair 2.1 update one firmware version = 2.59
what i wanna know is if i would b able to get the official froyo via msu if i revert back to my original eclair 2.1 firmware 2.59 using full sbf method.. is it at all possible ?
Nandroid restore + fixed sbf
joydeep1985 said:
currently i m running cm7 rom for gingerbread. if i revoke back to original one . (i messed up big time cause i didnt get a chance to make a nanodroid backup of my own eclair ).. so i guess i have to follow ur tutorial to revert back to my eclair 2.1 update one firmware version = 2.59
what i wanna know is if i would b able to get the official froyo via msu if i revert back to my original eclair 2.1 firmware 2.59 using full sbf method.. is it at all possible ?
Click to expand...
Click to collapse
Dear joydeep1985, first of all I've never flashed CM7 so I don't know how to go back from it to original Froyo, but I have no reason to doubt it is different from going back from MIUI, that I've tested. So a complete wipe, than a full Froyo sbf flash should work.
After that, to downgrade to Eclair, I have read in many forum, in XDA also, thant the direct Eclair sbf flash with RSD Lite procedure doesn't works!
The original sbf are made to upgrade from previous system or to repair the same version system, but are not enough to downgrade from a more recent system.
A nandroid backup only can do so, in conjuncion with a fixed sbf as I mention in this guide.
I do not know the exact reason why, maybe nandroid is able to restore overwriteing much more than the original Eclair full sbf.
In any case I can confirm thant, from a flashed full OEM Froyo, it is possible to succesful downgrade using nandroid + fixed sbf.
If you do not have a nandroid backup file that's not a big problem. There are many in internet, and in this forum also.
SeaFargo said:
Dear joydeep1985, first of all I've never flashed CM7 so I don't know how to go back from it to original Froyo, but I have no reason to doubt it is different from going back from MIUI, that I've tested. So a complete wipe, than a full Froyo sbf flash should work.
After that, to downgrade to Eclair, I have read in many forum, in XDA also, thant the direct Eclair sbf flash with RSD Lite procedure doesn't works!
The original sbf are made to upgrade from previous system or to repair the same version system, but are not enough to downgrade from a more recent system.
A nandroid backup only can do so, in conjuncion with a fixed sbf as I mention in this guide.
I do not know the exact reason why, maybe nandroid is able to restore overwriteing much more than the original Eclair full sbf.
In any case I can confirm thant, from a flashed full OEM Froyo, it is possible to succesful downgrade using nandroid + fixed sbf.
If you do not have a nandroid backup file that's not a big problem. There are many in internet, and in this forum also.
Click to expand...
Click to collapse
that was really a nice reply.... one more thing i would like to know .... in clockworkmod i dint get to see the nanodroid option.. also when i extracted the zip it gave me some img files .... like boot.img,android_secure.img etc in the nanodroid backup... when i put all the files under /sdcard/clockworkmod/backup and then choose the option restore . it doesnt seem to work at all. also due to no options such as present in clockworkmod > 3 i am not able to understand why its not working . how to make it work with clockworkmod >3 ???
In Froyo I've used Defy Recovery 1218 0326 signed.apk (the link is on the guide).
It works perfectly.
And the dir in wich you have to push the nandroid backup files is:
/sdcard/goapkrev/backup/
So at the end it will result something like:
/sdcard/goapkrev/backup/Eclair-2011-06-07
Beaware that the all path must be named without spaces.
one more question i have ... after my downgrade will i be able to update from motorola msu ? for official froyo update ? if i have to get that what i need to do ? can u please explain what are the requirements if i have to get the software update from motorola msu ? so that after my downgrade to eclair (i dont have my original nanodroid backup) i can update from motorola official MSU ?
joydeep1985 said:
one more question i have ... after my downgrade will i be able to update from motorola msu ? for official froyo update ? if i have to get that what i need to do ? can u please explain what are the requirements if i have to get the software update from motorola msu ? so that after my downgrade to eclair (i dont have my original nanodroid backup) i can update from motorola official MSU ?
Click to expand...
Click to collapse
I still do not know, because my Eclair was personally deblurred, and without Blur the "update firmware" doesn't works.
But I can confirm that, from this procedure downgraded Eclair, it will be perfectly possible to upgrade to Froyo by flashing its full sbf file with RSD Lite.
In any case I suggest to keep a copy in your PC for future references of:
- the OEM full sbf files of all the versions of Android you've using (from here and from a lot of places over the internet);
- the Nandroid backup of the installed, factory reset, versions of Android you've using (so before downgrade and afrer the factory reset make a nice backup of your actual Froyo);
- the zipped copy of the pulled system dir of the versions of Android you've using (by the command example like this: adb pull system "D:\Temp\Defy\pull system Froyo Defy")
SeaFargo said:
I still do not know, because my Eclair was personally deblurred, and without Blur the "update firmware" doesn't works.
Click to expand...
Click to collapse
oops that might be a problem cause my personal one came with blurred ...and the service flashes found in the link you provided are all without blur ( as you have stated ) so arent there any method left then ? so that i can revert back to original motoblur 2.1 update 1 eclair ? cause the service flashes doesnt contain motoblue where as my defy had motoblur in it
joydeep1985 said:
oops that might be a problem cause my personal one came with blurred ...and the service flashes found in the link you provided are all without blur ( as you have stated ) so arent there any method left then ? so that i can revert back to original motoblur 2.1 update 1 eclair ? cause the service flashes doesnt contain motoblue where as my defy had motoblur in it
Click to expand...
Click to collapse
Can't you find a Eclair blurred nandroid backup?
The full sfb file of the link of my guide DOES contain blur.
You just need a nandroid backup or the OEM Eclair Blur (so still not deblurred).
But if you find a deblurred modded Eclair nandroid backup it's OK the same! Is even better!!
Than, to future upgrade to Froyo, you can flash one of the many OEM full sbf, almost all blurred. ;-)
okay cool ... so like for now you mean i have to flash with nanodroid + fixed sbf = my current system (its deblurred and wont work)
so from that to make it work i have to find a full sbf (provided on your like flash it and bingo it has all )
and then i can upgrade from msu ... thats d procedure right ??? sorry for being complete noob
joydeep1985 said:
okay cool ... so like for now you mean i have to flash with nanodroid + fixed sbf = my current system (its deblurred and wont work)
so from that to make it work i have to find a full sbf (provided on your like flash it and bingo it has all )
and then i can upgrade from msu ... thats d procedure right ??? sorry for being complete noob
Click to expand...
Click to collapse
I have a litte difficulties undertanding your english ...
In any case, the fixed sfb is just a sort of bootloader, and it never contains app, system app, blur, and anything like that. It's just a bootloader that works for the scope.
The fixed sfb must be made from the same version of the nandroid backup. So for a nandroid backup Eclair, you have to use fixed sbf from Eclair.
Do not mix versions!
lol... sorry my bad ... was excited tht time .. so dint get to check out my punctuations ... .. sorry for being so bad in my reply and my english ........ got it for the time being .. the official froyo is yet to release in india . so i guess i have time till then ... until that i m jus making it sure that i get my eclair back in working condition before the official froyo update is out in msu ..... would try out this on weekend ... though pretty new in making sbf and nanodroid stuffs ....
many thanks for the help
Hey
I'm still on my 2.1. Got my nandroid backup, and now, how do I "create" a SBF file of my Eclair? Cuz it's a little bit hard to find it online. Hope there is a tool in wich I can do that.
"- the zipped copy of the pulled system dir of the versions of Android you've using (by the command example like this: adb pull system "D:\Temp\Defy\pull system Froyo Defy")"
May that be the answer?
Thank you so much.
Fixed sbf
victorvasconcelos said:
how do I "create" a SBF file of my Eclair?
Click to expand...
Click to collapse
I've clearly explained in the guide!!
This are the lines :
Before proceding you need to create or to obtain such called fixed sbf made from the same version you're going to downgrade, so from Eclair 2.51.1.
You can find such fixed sbf online but for safety I prefer to made it by myself. It's so easy.
1. open the original full sbf with Moto Android Firmware Depacker V.1.2 a3 and split to folder;
2. remove CG31.smg and CG39.smg
3. open the extracted folder (the same you've just removed the files) and compile files.
The resulting file is the fixed sbf file you'll need soon ;-)
But can I create a full SBF of my own Eclair? Because I can't find a full SBF of my carrier online
Sorry if I'm getting it wrong, hehe
Thaks for helping!
I don't know ...
About If you can create an sbf from just a nandroid backup ... I do not know, but I do not think so.
Otherwise whould be possible to restore anything without the need of any sbf, and I I've never find a guide telling so ...
In any case, give an accurate reserch over the internet for your country sbf. If it exists in your phone, should exists in "the cloud" somewhere ...
Related
I've not created a package for Odin before, but I thought it'd have a go at packaging up XXJP3 pre-rooted (as it's a bit of a pain to root).
So here it is - XXJP3 for Odin, pre-rooted with the latest Superuser Permissions, an insecure bootloader (so you can push files directly from adb / adb shell direct to root), clockworkmod recovery (replacing the stock recovery which can't flash test signed / unsigned images) and no other changes, and 512 PIT file included. Please provide feedback... I flashed to my device and it seemed to work but, well, you know... this is a new way of doing things.
Odin 3 v1.0 is also included in the zip.
BACKUP EVERYTHING ON YOUR DEVICE / SD CARD FIRST!
Enjoy!
JP3 repack r2 - DOWNLOAD (ROMraid Load Balancing) - MD5: 1fde7ab0cfa4be58896b3d0811c0f104
P
Thank you Paul.
r2 already, that was quick
hopefully get this d/l and flashed before the day is out ... (didn't get to do r1 yet !!)
Thank you Paul
anyone who flashed it. root explorer works ok?
i have jp3 rooted with this jp2 kernel, adb, flash jp3 kernel way and root explorer and some other i tested not working. fc's
flash just completed without issue, will have to play around some more to discover what is and isn't working for me.
let's see how long i can stick with TouchWiz before switching over to LauncherPro Plus :-D
i m in india and my firmware is i9000ddjf3.....
can i flash dis frimware to my phone and if yes dan i can i turn back to da original firmware thanx...
dhruvzz said:
i m in india and my firmware is i9000ddjf3.....
can i flash dis frimware to my phone and if yes dan i can i turn back to da original firmware thanx...
Click to expand...
Click to collapse
yes but only if you have your original firmware to flash back to. Check out samsung firmwares, to see if they have it.
BTW, thanks paul, I hope I dont flash it and jp4 comes out!
does this work on TMO-vibrant? There's not much in the vibrant section of this site...
Hi, Can anyone tell it CoPilot and Gameloft games work ok or say no sd card space left. Many thanks
fua said:
anyone who flashed it. root explorer works ok?
i have jp3 rooted with this jp2 kernel, adb, flash jp3 kernel way and root explorer and some other i tested not working. fc's
Click to expand...
Click to collapse
Root Explorer working for me, no FC
Sent from my GT-I9000 using XDA App
Do I have to flash with JP3 first before flashing this or can this be done from any previous firmwares?
Thanks
can be done from any firmware. very handy.
Sent from my GT-I9000 using Tapatalk
is the sdcard name still change in this version?
if so, all games can't be played or need to be reinstalled
I'm gonna revert the sdcard name for a future version.
P
Works great! One question:
Hi Paul,
works great, thanks a lot. Why the old busybox version?
paulobrien said:
I'm gonna revert the sdcard name for a future version.
P
Click to expand...
Click to collapse
If this would fix the sd card issues would be a great step forward in froyo
=(
hmm in the Clockwork i cant wipe :S
Did someone note a wrong black levels in cam recording? I don't know if by playing video on a different output, like a TV, it would give back the same faded blacks. Is it a recording or reproducing only problem?
hi, does this include the flash player 10.1
On my N900 to flash a new copy of the OS all you had to do was connect to pc and run maemo flasher. And some stuff of how to flash different android versions is a bit confusing(The defy is my first android device).
I deduced that Roms are custom android versions right?
What do nandroid, bootloaders, sbf files?, rsdlite and custom recovery do?
What else should I know?
Thanks,
confusedfella said:
On my N900 to flash a new copy of the OS all you had to do was connect to pc and run maemo flasher. And some stuff of how to flash different android versions is a bit confusing(The defy is my first android device).
I deduced that Roms are custom android versions right?
What do nandroid, bootloaders, sbf files?, rsdlite and custom recovery do?
What else should I know?
Thanks,
Click to expand...
Click to collapse
There are loads of explanations in the forum for that. Just look at the Defy Android Developement Section.
Basically it is not that difficult to flash a new ROM but be aware that u might lose the ability to downgrade back to 2.1 and thus u might lose waranty.
The Bootloader is locked in our Defys therefore we cant modify that. SBF-Files are official signed ROMS from Motorola which contains the whole system. These sbf files can be flashed with the RSD-Lite Tool under Windows. There are 2.2 SBF Roms from Motorola from China, Finnland, Uk ... but i think if u flash one of them then u cant go back to the original 2.1
Custom Recovery is a kind of Application which can be executed between the bootloader and the start of the main system. It looks like a second bootloader where u can make a complete Backup of your System with all the Data and Apps. These Backups are called Nandroids...
Hope that helps a little.
Greetz
If you are not installing a custom rom and have no plan going back to the stock android 2.1, you can flash defy the same way you flashed N900. Just choose a leaked official 2.2 rom (sbf) and flash it using rsdlite.
Thanks for the help. Would you guys recommend a rom that's zippy(right now it stutters a lot and worsens the experience) and isn't exactly barebone?
Hi all,
My first rom is paysrom 5.1. So to get this rom i flashed 3.4.3-11 uk sbf. I know, i can't downgrade for 2.51.1.
For installing rom in different post, we need to flash another sbf. That's the first instruction before flashing rom. That's mean to downgrade the 3.4.3-11 uk sbf.
I saw after many search that we can't downgrade sbf without brick the phone.
Now how can try differents roms?
Need help, please.
I ask some different people on some different post and have many different answer.
1/ flash sbf boot only after wipe everything and flash the rom
2/ install 2ndinit and flash the rom you like after wipe everything, without changing your sbf
3/ restore nand backup rom you like and flash sbf after
...
Wich is to safe ?
The problem : i live in madagascar and they don't have motorola support here if i brick the phone. Need to send the phone in europe.
Sent from my MB525 using XDA App
Just flash Froyo ROM over it or ? I am pretty sure that was a specific file from TMartin or even Virus but don't know where is it.
erik077 said:
Just flash Froyo ROM over it or ? I am pretty sure that was a specific file from TMartin or even Virus but don't know where is it.
Click to expand...
Click to collapse
Just wipe and flash like you'd normally flash. There are no special steps required to revert back to froyo from gingerbread.
The special files you're asking about were simply zips that did the wiping for you. Just do the normal wipes and you'll be fine.
Thanks....
gingerale
Recently added ginger ale 3.0 on my DROID x.not happy at all does anybody know how I get back to original factory. Or where I can get the file.also since the update usb has stopped working.
I just bought my Gio in the Netherlands. I've rooted it and installed cwm 5.0.2.7 rfs+ext4. I made a backup with cwm so I have a backup of the stock ROM.
3 hours after I bought it I converted my rfs partition to ext4 to install CM7.2 this went well and installed cwm 5.0.2.7 ext4 only (so i can make backups of ext-sd (EXT4)).
My question is if I wanted to go back to the stock ROM how would I go about this ? I am thinking I should do it like this.
I believe I can't restore the backup I made with cwm initially of my stock ROM since I converted the phone partition to ext4. I would need to flash the stock ROM (download it online) with ODIN.
Root it and install cwm 5.0.2.7 rfs+ext4 and restore the backup I made of my stock ROM with cwm. Or is this step pointless and is the backup I made exactly the same as the stock ROM you download online (meaning there are no specific dutch modifications) ?
Tbh i'm quite happy how my phone is working now, I just want to try this so i'm confident I can go back to way it was.
Regards,
oOze
Latest Kies file
Product Code: GT-S5660DSAXEN
Latest firmware: S5660XXKPS/S5660XENKP1/S5660XXKPA/S5660XXKPS
Modified: 9/14/2011 10:12:10 AM
Download
Flash it with Odin
When i tryed to restore stock rom from CWM backup it failed . So here is the latest file for your phone download it and keep it somewhere safe in case u want to go back to stock
o0ze said:
I just bought my Gio in the Netherlands. I've rooted it and installed cwm 5.0.2.7 rfs+ext4. I made a backup with cwm so I have a backup of the stock ROM.
3 hours after I bought it I converted my rfs partition to ext4 to install CM7.2 this went well and installed cwm 5.0.2.7 ext4 only (so i can make backups of ext-sd).
My question is if I wanted to go back to the stock ROM how would I go about this ? I am thinking I should do it like this.
I believe I can't restore the backup I made with cwm initially of my stock ROM since I converted the phone partition to ext4. I would need to flash the stock ROM (download it online) with ODIN.
Root it and install cwm 5.0.2.7 rfs+ext4 and restore the backup I made of my stock ROM with cwm. Or is this step pointless and is the backup I made exactly the same as the stock ROM you download online (meaning there are no specific dutch modifications) ?
Tbh i'm quite happy how my phone is working now, I just want to try this so i'm confident I can go back to way it was.
Regards,
oOze
Click to expand...
Click to collapse
You're right. Restoring a stock rom to a phone that hase ext4 filesystem partitions wont work. The Android OS wont start up. I did test it. Ik teste het
Installing a stock rom with Odin will make the internal system rfs again i did read.
I think installing cwm 5.0.2.7 rfs+ext4 even will make the file system rfs again? Not tested it. Would save 5 min. odin.
Happy testing
Ty for the quick replies.
I downloaded the ROM one that was suggested in the replies.
I had S5660XXKPE_S5660XXKPA_S5660XENKP1.rar I guess thats an older version.
And if you restore a stock rom via Odin, can you restore the CWM backup afterwards in order to regain your original settings and stuff ?
Or doesn't it work that way ?
Otherwise you could always do a full backup using Titanium of course...
WalkerOfTheDay said:
And if you restore a stock rom via Odin, can you restore the CWM backup afterwards in order to regain your original settings and stuff ?
Or doesn't it work that way ?
Click to expand...
Click to collapse
I don't know I guess I will find out but if its the Dutch/Netherlands ROM you posted in the link I won't have to I guess.
I guess i'll have to use Titanium backup anyway since the backup I made with cwm is old already (or lose some data I don't have much I really want to keep now).
o0ze said:
I don't know I guess I will find out but if its the Dutch/Netherlands ROM you posted in the link I won't have to I guess.
I guess i'll have to use Titanium backup anyway since the backup I made with cwm is old already (or lose some data I don't have much I really want to keep now).
Click to expand...
Click to collapse
I didn't post that link ( SilviuMik did )
My 2.3.5 version is S5660XXKS2, which I got from the Android Advice tutorial, guess I don't have the newest either
Right my bad well anyway he said in a other thread its the newest dutch ROM
Code:
GT-S5660 S5660XXKS2 ## 2.3.5 2011 September S5660OXXKS2
Btw: My firmware seems newer, it's from September 2011. It's not official Kies though. It's on SamMobile Firmware Page.
WalkerOfTheDay said:
Code:
GT-S5660 S5660XXKS2 ## 2.3.5 2011 September S5660OXXKS2
Btw: My firmware seems newer, it's from September 2011. It's not official Kies though. It's on SamMobile Firmware Page.
Click to expand...
Click to collapse
I have no ideea which one is newer. U can stay on that no problem Mine is "good" in case of warranty issues and u must bring phone back to where u buyed it , because u can`t bring the phone with another firmware on it other then the one u have in your country Netherlands
Yeah, your right about the warranty, but I sim-unlocked my prepaid phone myself, so I guess I'm out of warranty anyway
Or is there an option to relock too ?
WalkerOfTheDay said:
Yeah, your right about the warranty, but I sim-unlocked my prepaid phone myself, so I guess I'm out of warranty anyway
Or is there an option to relock too ?
Click to expand...
Click to collapse
I have no ideea if u can lock it back . Maybe if u did a backup of /dev/stl5 ( EFS ) folder before u started to modify it for the unlock process and restore it, then it would be locked again, but i am not sure about this never did it
An appropriate CSC file followed by a factory reset should relock.