Develop Bugs

nubbuns question regarding installing foroy on the defy

Just a quick one.
Ive come from the desire which ive installed just about every rom on and modified the partition table dozens of times so im no stranger to rooting... however this defy has me confused.
I need 2.2 to access lotus traveller for my work emails so im looking to install a custom rom until T-mobile uk finally release the official one but im reading all sorts of things like not being able to downgrade if you flash certain roms which arent "fixed".
Can someone give me a brief overview so i can get my head round what all this is about and can anyone point me in the direction of a good solid 2.2 rom which is as close to the official rom as possible?
cheers
edit : forgive the title, its meant to say FROYO!!

Here you go fella http://forum.xda-developers.com/showthread.php?t=993402
I've just recently flashed this 3.4.3-11 http://depositfiles.com/en/files/tjnmh6d98 onto my Defy & it's running great. There's no T-Mobile branding on this one & I doubt that you would be able to downgrade to an older version either.
You'll need RSD Lite V4.9, Motorola Drivers (I used V4.9 for these).
I followed Higgsy's great guide http://forum.xda-developers.com/showthread.php?t=853674 about flashing a sbf & it worked a treat - in fact this current sbf is the 2nd froyo that I've flashed.
Hope this helps.

thanks for that. Ive actually managed to get a version of 3.4.2 on now which can be downgraded. Im starting to get the hang of this, it certainly a different process than what im used to thanks to motorola!
Im trying to keep it to stock roms now as I found with my desire there was always some bug that "bugged" me with custom roms so with this I think when the official 2.2 comes out for the UK I will flash it and keep the phone unrooted ( I only ever initially got into rooting for apps2sd anyway)
The reason for needing to keep it downgradeable is purely for the warranty with t-mobile otherwise I would just go with the rom you suggested.
Do you know of any version of 3.4.3-11 that is out there that is downgradeable that is still close to stock in terms of apps and features?
edit :its worth noting that higgsys procedure doesnt work with the eclair 2.51, you end up with the black screen issue. ( I imagine most are shipping with this now) although the general guidelines still apply, just different files are needed.

I'm not clued up on anything other than flashing a sbf via RSD Lite but if you have a look at the SBF Service File sticky in the Defy Dev forum the last post or two links to a fixed sbf & a nandroid of 3.4.3-11.
Sent from my MotoDefy.

[Q] Updating from Eclair to Froyo - making sure I can go back!

Hi guys!
First of all, I did a lot of research on the dev forums, and surely I've learned a lot, but somethings are still not clear for me.
My Defy runs a stock branded Eclair, but I'd like to try Froyo ROMs and also the CM7 port. I don't want to lose the ability of coming back to the stock firmware, though. As far as I understand, I have to make a nandroid backup of my phone and then Flash the Froyo ROM without CG31 and CG39, so that I can go back to the original firmware. I've understood that CG31 is something related to phone signature, and CG39 related to system partition. But will the Froyo ROM work without the CG39 flashed? Is there any resultant difference of flashing a full ROM and a "fixed" ROM besides losing the downgrade ability?
I couldn't find any description of what each CG is responsible for, do you guys have any link?
Also, on every ROM thread, someone asks for a nandroid backup of it. Why? Is it easier to flash ou flashing through a nandroid backup preserves the downgrade possibility too?
My phone infos:
System Version:
Blur_Version.6.36.1.MB525.Vivo.en.BR
Firmware Version:
2.1-update1
Version Number:
JORLA_U3_6.36.1
Thanks very much for the attention!
Daniel

The Korean Froyo will let you downgrade back to Eclair.
Its the only sbf (atm) you can flash directly and still go back.
Otherwise you need to use a nandroid and fixed sbf of the Froyo version you want to use.
People want a nandroid because the way around not being able to downgrade is to make up a 'full' rom using the nandroid + a fixed sbf.
So a nandroid gives you CG39 and the fixed sbf makes up the rest of the CG's; thus a 'full' rom.
Rather then flash a full sbf and lose the means to downgrade.
Fixed sbf's exist already: http://forum.xda-developers.com/showthread.php?t=966537
Codegroups: http://forum.xda-developers.com/showthread.php?p=11195544
Btw should also mention Daniel here is smarter than the average bear; he reads before trying . . . . P

Fritolays, thank you for the ultra-fast response!
In fact I've been reading threads here for more than one week... Obviously it's possible to learn a lot from intuition and observing things, but there are moments in which pieces of the puzzle start to miss, because a lot of informations are implicit on the threads or treated like already known by people who are discussing it, what's pretty normal methinks, but makes it a little difficult for the new ones to understand things.
For instance, before reading your reply I was thinking that one should flash the fixed sbf OR the nandroid backup, because I believed they had similar purposes...
So, this also means that when going back from Froyo to original Eclair I'll also need a Eclair sbf besides my nandroid backup, right? Does it have to be a specific one to match my nandroid backup or not?
Also, do you recommend flashing the full Korean Froyo ROM or another ROM with fixed sbf plus nandroid backup?
To receive the official Motorola Froyo upgrade whenever (if ever) ready I'll have to have my stock firmware, right?
Thanks and cheers from Brazil!

To go back to Eclair, yes you will need an Eclair sbf. Though is does not need to be the exact same version (just dont use 2.51, prevents downgrade); as your nandroid will overwrite the system partition with your Eclair version. Just need the sbf to restore the other codegroups.
Personally I just use the Korean Froyo as a starting point. Saves on headaches because you can just flash the sbf. Dont need to install recovery then restore nandroid then flash fixed sbf. Less rebooting P
Ya to get the official moto Froyo, if they ever decide to release it, you will most likely need to be on an Eclair build. But to be honest who cares; with Quarx working on Gingerbread, motorola can shove it. Why have 2.2.2 when he's working on 2.3.3 ? hehe
Hope this help !

fritolays said:
To go back to Eclair, yes you will need an Eclair sbf. Though is does not need to be the exact same version (just dont use 2.51, prevents downgrade);
Click to expand...
Click to collapse
When flashing Eclair back from Froyo should I flash the whole sbf and then restore nandroid backup or should I left CG31 and CG39 out like if I were upgrading with a fixed rom?
fritolays said:
as your nandroid will overwrite the system partition with your Eclair version. Just need the sbf to restore the other codegroups.
Click to expand...
Click to collapse
Do you know what CGs are present in a Nandroid backup?
fritolays said:
Personally I just use the Korean Froyo as a starting point. Saves on headaches because you can just flash the sbf. Dont need to install recovery then restore nandroid then flash fixed sbf. Less rebooting P
Click to expand...
Click to collapse
It saves on headaches but if I don't install recovery, although I'll be able to flash Korean Froyo directly, there will be no way to backup my firmware and so even if I am able to downgrade I won't have my backup to do so. Right?
fritolays said:
Ya to get the official moto Froyo, if they ever decide to release it, you will most likely need to be on an Eclair build. But to be honest who cares; with Quarx working on Gingerbread, motorola can shove it. Why have 2.2.2 when he's working on 2.3.3 ? hehe
Click to expand...
Click to collapse
You are right but don't forget about warranty! Say my camera or touchscreen stop working, they will put the blame on the modded firmware, so I have to be able to go forth and back to keep things official if needed.
fritolays said:
Hope this help !
Click to expand...
Click to collapse
Sure you're helping! Thank you very much!

danimagrin said:
When flashing Eclair back from Froyo should I flash the whole sbf and then restore nandroid backup or should I left CG31 and CG39 out like if I were upgrading with a fixed rom?
Do you know what CGs are present in a Nandroid backup?
It saves on headaches but if I don't install recovery, although I'll be able to flash Korean Froyo directly, there will be no way to backup my firmware and so even if I am able to downgrade I won't have my backup to do so. Right?
You are right but don't forget about warranty! Say my camera or touchscreen stop working, they will put the blame on the modded firmware, so I have to be able to go forth and back to keep things official if needed.
Sure you're helping! Thank you very much!
Click to expand...
Click to collapse
Yup to downgrade flash the full sbf, then your nandroid - fixed sbf's are for going up in versions.
Doesnt really work that way. It backs up your data, cache and system partitions.
Make a backup before you flash the sbf. The backup gets saved to your sdcard card so you can copy it to your computer. That way even if recovery gets deleted from flashing a full sbf you can just re-install recovery, copy your nandroid back to your sdcard, restore it and be on your merry way.
I void warranties. ) At this point its your call. Just to note though officially moto will not fix your phone if it has a leaked version on it. Official ones are ok, and the Korean one is the only official Froyo one out there.

When one sends something for repair here in Brazil they ask for the proof of purchase/invoice (don't know what's the best word for that in English). So, you know... It's a little strange... A phone bought in Brazil running Korean software. They will complain immediately But I won't worry about that.
I've read the CGs thread. Unfortunately there isn't a long explanation about what each CG is responsible for, but only a short description for some of them, and no description for 32, 35, 42, 45, 53, 61, 64 and 65.
However, as far as I understood, some CGs stay the same but some change between different ROM versions. So, if I reflash Eclair after Froyo and restore my Nandroid Backup, despite having the same data, cache and system partitions, some CGs will be different from the firmware I'm running now. Any issues about that, if I choose to stay with Eclair after all?

I've sucessfully made the nandroid backup of my phone.
But just to make sure I understand things, I would like to make one last question. I couldn't find the exact sbf of my firmware on the internet (JORLA_U3_6.36.1).
So, if I need to reflash 2.1, it won't be JORLA_U3_6.36.1.
Will my nandroid backup work together with any other 2.1 sbf than the JORLA_U3_6.36.1? For instance, will it work if I flash JRDNEM_U3_2.21.0, that I can find on the internet?
Thank you...

danimagrin said:
When one sends something for repair here in Brazil they ask for the proof of purchase/invoice (don't know what's the best word for that in English). So, you know... It's a little strange... A phone bought in Brazil running Korean software. They will complain immediately But I won't worry about that.
I've read the CGs thread. Unfortunately there isn't a long explanation about what each CG is responsible for, but only a short description for some of them, and no description for 32, 35, 42, 45, 53, 61, 64 and 65.
However, as far as I understood, some CGs stay the same but some change between different ROM versions. So, if I reflash Eclair after Froyo and restore my Nandroid Backup, despite having the same data, cache and system partitions, some CGs will be different from the firmware I'm running now. Any issues about that, if I choose to stay with Eclair after all?
Click to expand...
Click to collapse
I don't think some CG's stay the same when you flash an sbf, I believe its the CG version that changes. For instance if a particular CG is at version 2 on your phone, some froyo full flashes may update that CG to version 3, and thus you cannot flash back down to a version 2, you can only flash CGs that are the same version or higher.

kashavsehra said:
I don't think some CG's stay the same when you flash an sbf, I believe its the CG version that changes. For instance if a particular CG is at version 2 on your phone, some froyo full flashes may update that CG to version 3, and thus you cannot flash back down to a version 2, you can only flash CGs that are the same version or higher.
Click to expand...
Click to collapse
You're right indeed, but as far as i know some CGs do stay the same between different sbf versions, as you can see, for example, in this comparison taken from CM7 thread:
sunoldman said:
If you depack a full sbf, you will find several CG??.smg files. Here's a comparison between 3.4.3_11 and 3.4.2_177.
Code:
CG31 cdt Codegroup Description Table same
CG32 bploader Baseband Processor Bootloader same
CG33 cdrom CDROM diff
CG34 lbl Linux Bootloader same
CG35 boot Android Boot Image diff
CG39 system Android System diff
CG42 logo boot logo diff
CG45 bpsw Baseband Processor Firmware diff
CG47 recovery Android Recovery Image diff
CG53 kpanic Kernel Panic Console same
CG61 devtree Device Tree same
CG64 mbr eMMC Master Boot Record same
CG65 ebr eMMC Extended Boot Record same
Click to expand...
Click to collapse

Just forgot to mention that this also means, obviously, that CGs having same version can binarly differ...

Very useful information for Android beginners like me, but the most important question still remains - is full sbf of the stock ROM is required in case of downgrade to the stock version? Or can I use nandroid backup of my stock ROM together with different version of Eclair sbf?
The problem is that I cannot find full sbf of my stock ROM, but I want to be able to get back to it if needed.

Agreed, some code groups can stay the same. I wonder what the procedure is to work out what version a CG is?
Actually a database/table of s/w versions along with the CG numbers and version would be a good resourse to help people understand what downgradability options they have by knowing what versions they are flashing to their phones.

mindugo said:
Very useful information for Android beginners like me, but the most important question still remains - is full sbf of the stock ROM is required in case of downgrade to the stock version? Or can I use nandroid backup of my stock ROM together with different version of Eclair sbf?
The problem is that I cannot find full sbf of my stock ROM, but I want to be able to get back to it if needed.
Click to expand...
Click to collapse
Have you tried to plug your device to your PC and seeing if the Motorola Software Update tool detects any software versions for it? If so it will download the complete sbf from motorola servers to your Hard Drive.

kashavsehra said:
Agreed, some code groups can stay the same. I wonder what the procedure is to work out what version a CG is?
Actually a database/table of s/w versions along with the CG numbers and version would be a good resourse to help people understand what downgradability options they have by knowing what versions they are flashing to their phones.
Click to expand...
Click to collapse
Used MotoAndroidDepacker (also used to fix SBFs) to extract individual CGs, than the app from http://forum.xda-developers.com/showthread.php?t=945035 to tell each CGs' version. To compare CGs you can use good old linux diff command.
mindugo said:
Very useful information for Android beginners like me, but the most important question still remains - is full sbf of the stock ROM is required in case of downgrade to the stock version? Or can I use nandroid backup of my stock ROM together with different version of Eclair sbf?
The problem is that I cannot find full sbf of my stock ROM, but I want to be able to get back to it if needed.
Click to expand...
Click to collapse
I had the same doubt as yours because I couldn't find the exact sbf of my stock ROM also, but I've tested my stock ROM Nandroid backup (Eclair) and it worked together with every different Eclair SBF I tried, independently whether the "helper" sbf was full or fixed or the CG version it had. Just be aware that even a Eclair ROM may have greater CG version than the one installed on your phone so if you flash one of these you won't be able to come back using a full sbf (if you had it...). However if you lock your phone you can always downgrade using fixed sbf + nandroid backup.
Don't know if I was clear enough, I know this is confuse to explain.
It's easier if you tell your stock rom version and what you want to do exactly.
Feel free to ask if you have any doubts...

Question about update and downgrade
Hello android people!
I'm new to android world, and i have done some things, differente from daniel.........i didn't read sufficiently before, and i already have make some upgrades.
I installed a sbf file - 3.4.2-117 002 blur usa
I wanna know if i can go back to Eclair sbf, just like daniel asked, cause i'm from Brazil and i have the same thing he sayed, about lose the warranty.
Another question, i get the 3.4.3-11 blur usa, the one Quarz from CM7 recomend to install.
If i install that sbf, can i downgrade to the one that i'm already using, or to the Eclair sbf??
Thanks everybody, i starting to like very much this forum, and the android world.
Cheers

Flashing Roms how to start, where to start?

Ive been looking through some of the posts on the Android development board, but im relativly new to the idea of flashing different roms.
At the moment my phone is running the standard Froyo 2.2.2 firmware, from Motorola,
system version 34.164.3.MB525.Retail.en.FR
Is it a simple process to change this?
can i go back to the default Rom/version( listed above)? or would i be stuck with, say, cyanogenmod 2.3.4?
would i still be able to use the Motorola phone portal to send texts via my p.c?

http://forum.xda-developers.com/showthread.php?t=1065798
Follow this tutorial..everything is given in this..
The process is simple..u may face few problems flashing a ROM,just search in this forum for the solution.
Well yes u can go back to your stock ROM if you have the sbf file or an nandroid backup.
Yes phone portal is present in CM7 also..so not a problem.
All the best

Thanks for the link, although im still non the wiser.
You said
Well yes u can go back to your stock ROM if you have the sbf file or an nandroid backup.
Click to expand...
Click to collapse
How can i get hold of that file? my phone updated via motorola sfotware update to this:
Version.34.164.3.MB525.Retail.en.FR
and its running Firmware version 2.2.2
whats this nordic firmware?, and if thats 2.1 would that cause probelms as my phone is curently 2.2.2??

you already have the right firmware. start to flash cm7. should be fine.

klickig said:
you already have the right firmware. start to flash cm7. should be fine.
Click to expand...
Click to collapse
How can i get hold of a revocery file, if i decide to go back to the standard motorola 2.2.2?

http://forum.xda-developers.com/showthread.php?t=1126907
Here is the link to the official 2.2.2 UK sbf(as u r from UK)
you can use this to get back to 2.2.2 anytime you want
http://www.multiup.org/fichiers/dow...06b1_Motorola_Defy_Nu___Android_2.2_FroYo.rar
or go to above link to download you present official ROM..
Both should work fine..
All the best

How to make a full backup before installing roms?

Hello,
I would like to create a full stock backup, I do not care for applications or settings, the only thing I want is full non-rooter, current Gingerbread with ability to install possible upcoming OTA updates.
The reason for this is simple, I want to try out different ICS roms just for fun and then go back to original, HTC Sense 2.1 powered rom.
The question is: How do I do that? I know I can handle rooting the device and installing various things but how do I get back?
Thanks!
PS A link with instructions on how to do that would be nice, I tried searching the forums and Google but nothing legit came out.

If you have already rooted your phone and installed a recovery such as ClockworkMod or 4EXT, reboot into recovery and go to the "Backup" menu and make a full backup.
In the event of problems, you can do a full wipe or factory reset, and then go to the same backup/restore menu to restore your backup from the SD card.

But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?

stranded.eu said:
But if the phone is Gingerbread (it is) I have to downgrade first, correct? To Froyo 2.2. So Basically that leaves me with a copy of 2.2 while my phone came with Gingerbread in the first place.
It basically shows that I've changed (downgraded) the software, doesn't it?
Click to expand...
Click to collapse
If you have ALREADY rooted it, then there is no need to be downgrading back to an exploitable firmware when you've already exploited the phone. If all you're doing is installing a custom rom on an already rooted/unlocked phone then you need only flash the roms via recovery.
You would only have to downgrade the firmware if you for some reason decided to flash the original stock firmware, hboot, etc onto the phone.
But that's least as far as the backups go.
In terms of how to get the phone back to non-root/locked state there's a sticky/wiki for that, though I would find it to be a pain in the butt to have the phone rooted and unlocked and then have to go thru the process of locking it back up only to possibly risk bricking it. The more times you mess with the firmware/radio/hboot the more likely you are to brick it.

Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
That's too bad there is no other way to root Desire Z.

stranded.eu said:
Just to make it all clear my phone is kinda new, was never rooted, that's why I'm asking. I still can't believe that HTC doesn't have an app like Xperia has, SEUS to be exact, you can fix any phone with one click. By saying fix I mean install the latest, official rom.
Click to expand...
Click to collapse
If never rooted there's not much of a way to make a full backup first (since most backup tools like Titanium Backup requires root).
That's too bad there is no other way to root Desire Z.
Click to expand...
Click to collapse
Well there is the HTCDev unlocker from HTC themselves, but you actually have better luck following something like cyanogenmod's wiki entry.
Something like this works quite well : http://wiki.cyanogenmod.com/wiki/HTC_Vision
You just need to make sure to triple-check all the numbers and messages, someone accidentally skipping 2 or 3 steps multiple times is just asking for problems.
But once rooted (like for my G2 I followed the cyanogenmod steps, and then went another step by upgrading my radio to the latest, I just went with a different rom after being rooted) it's usually best to keep it that way even if you decide to just flash the stock rom (i.e.: still rooted and unlocked, but simply using the original software they provide you, which can be rooted simply by having the su binary and superuser app).
The voiding of warranty usually applies to software, i.e.: you bricked the phone as a result of flashing the wrong hboot. Where as if the screen or eMMC dies, it's a hardware failure and shouldn't be voided simply because the phone was rooted (unless of course they determined you fried your CPU by running the phone at 1.9Ghz constantly).

You could just download a full version of the G2 gingerbread rom from shipped-roms.com and flash that if you ever want/need to go back to stock gingerbread.
-Nipqer

[Q] Arc S android update suggestions (for backup and space issues?) - noob :$

Hi,
I'm having problems with space and the general speed of my Xperia Arc S so the time has come to finally upgrade from Sony's version of Android 2.3 in hope that it will improve things.
I've kind of avoided this so far as I don't really know the best way to back-up things.
I want to back up to my computer - not to the internet.
I am guessing that for the applications that I would like to back up I would need to back up both their APK files and whatever their setting files are. I guess there are also some system settings to back up (but then these are less important).
A problem I have always had is space on the phone - it has very little storage space and although I try and move everything to the SD card, a lot of it doesn't seem to be able to be moved.
Things like simply the Google Play services take up loads of space! I don't even really have that much on there - mainly just whatsapp.
The phone is stock although I have checked in the service menu and it says that I can unlock the bootloader. Part of the reason I didn't upgrade to Sony's version of Android 4 was because I heard that it locks the bootloader and I didn't know if this was bad.
What is the bootloader unlock for? Is it for loading custom roms? As i thought you could do this even if it was locked? Or is it for rooting?
So yer, I guess I am looking for recommendations for a CFW to suit my needs. Priorities are that it works and i'm guessing the latest android version possible would be best as this will help with performance etc. Or is that a misnomer as newer android releases are generally geared for phones with higher specs? I've heard that some CFWs have problems with wifi etc so i'd like to avoid those as I certainly need that.
Overall there seem to be so many even on this forum that I don't really know which would be a best fit for my needs or this phone.
I also have an original San Francisco (zte blade) to update but will save that 'till I've done this one.
Hopefully I can get an understanding as to how all this CFW / Rooting / whatever business works and the best / latest way to do things, as as with everything, it all rapidly changes and you can find yourself looking out lots of outdated and now incorrect or superseeded information.
All a bit overwhelming really, which is why i've put it off so long!
Thanks for your time and help!

1. Q : For backup on ICS 4.0.4, right?
A : Unlock bootloader first -> root -> flash cwm - now u can backup everything from ur phone.
2. Q : Little storage, right?
A : After backup, reboot system.
Partition ur sdcard -> install link2sd. (google it for how to)
Link what do u want to link (google it for how to)
3. Q : Unlockbootloader, right?
A : It's for using custom kernel (google it for how to)
There's too many tutorial from all your question.
Read it again and again :good:

Abigail said:
1. Q : For backup on ICS 4.0.4, right?
A : Unlock bootloader first -> root -> flash cwm - now u can backup everything from ur phone.
2. Q : Little storage, right?
A : After backup, reboot system.
Partition ur sdcard -> install link2sd. (google it for how to)
Link what do u want to link (google it for how to)
3. Q : Unlockbootloader, right?
A : It's for using custom kernel (google it for how to)
There's too many tutorial from all your question.
Read it again and again :good:
Click to expand...
Click to collapse
I have android 2.3 - is this a problem?
I thought that the Sony ICS 4.0 update made it so you could not unlock your bootloader?
Hmm if you unlock your bootloader, it will also root the phone, correct?
But it seems that using the Sony tool will wipe my phone developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
So i saw there is the S1tool but then people said that it does not work with the Arc S.
Is this still the case? What is the reason? is it impossible?
So, you say that in order to back up my applications and things, i need to unlock my bootloader. The official way seems to wipe my phone though - so then i can't back up :S
Hmm, see, i am confused about the order i should do things. Also i've heard that if you use the Sony tool then you cannot use OTA updates which seems like it could be problematic? Mind you i guess CFW cannot use OTA either - so how do you update? You must check for updates on your PC and reflash your phone regularly? Or are there ways for Stock android CFW to support OTA updates?
So, does the Sony ICS update stop you unlocking the bootloader?
I guess there are 2 options. Update using that and then install helium OR root and then use titanium backup.
Not sure which to try.
Thanks!

1. Unlock bootloader is only affected by the phone manufacture date, check the battery compartment and see if the date is before 12W11. Any date after this means the phone can't be unlocked.
2. Software does not affect the unlocking of bootloader, like I mentioned earlier check the battery compartment.
3. Unlocking your bootloader does not mean you have rooted your phone. It just means you can flash custom kernels onto your phone.
4. It's not that S1tool doesn't work, if I told you the entire process of doing it you wouldn't want to do it either.
5. Sony last stopped the update at 4.0.4, no need to concern yourself with future updates.
6. If you use CFW, refer to the thread for instructions on how to install updates.
7. Like I mentioned, ICS update does not affect bootloader unlock, only the manufacture date does. Furthermore, if you update from stock to a CFW, you will not be able to restore your data from the old software. You will have no choice but to start with a clean slate.

I am on Sonys 2.3, build 4.0.2.A.0.62 and i read that i cannot root this version.
I can't use backup software as i can't root to use titanium and helium doesn't support 2.3.
Sony back also apparently doesn't support my phone.
Basically, my apps are outdated due to me not having enough space to update them.
I think that updating to Sony's ICS update might enable me to use these programs and root so that i can backup, then unlock the bootloader and use cfw. (i checked and my s# is older than 12W11 so that's fine).
However, i am worried that if i try to update to Sony's ICS update that i will either lose my applications or the data that is stored with them (whatsapp history, game saves, app config etc etc) - particularly as they are not up to date.
Is this the case? Is there anything i can do?
Thanks

oneNight1 said:
I am on Sonys 2.3, build 4.0.2.A.0.62 and i read that i cannot root this version.
Click to expand...
Click to collapse
Take a look at the tool namend one click root (this thread: http://forum.xda-developers.com/showthread.php?t=2219781), your build should be root-able, just read carefully and decide if you wanna try...
I used this tool on stock sony ics 4.0.4 build and it worked nicely, haven't tried it on stock sony gb 2.3 build though.
Good luck! :good:

BadGround said:
Take a look at the tool namend one click root (this thread: http://forum.xda-developers.com/showthread.php?t=2219781), your build should be root-able, just read carefully and decide if you wanna try...
I used this tool on stock sony ics 4.0.4 build and it worked nicely, haven't tried it on stock sony gb 2.3 build though.
Good luck! :good:
Click to expand...
Click to collapse
Thanks for the tip! It worked!
If you do it twice it relocks your phone. Took some google translate to find out what the chinese was saying hehe.
I'm now on stock 4.0.3 (4.1.A.0.562).
Doesn't seem a great deal better than 2.3, i guess i need to find out what a good lightweight CFW is really. Firefox for android constantly crashes so i tried naked browser and that does too. Wish there was a good selective script blocker for mobile browsers - that would help a lot. Noscript for firefox would be a possibility but the problem is it crashes a lot even with javascript disabled.
So yer not sure where the problems are coming from, maybe due to the low RAM in this phone. That's why i was thinking a lightweight CFW might help matters but not sure if it's best to go with a 5.1 one that breaks 720p recording and has issues with things like turning off GPS.
Or it might be better to go with the latest type that doesn't break anything. I'm guessing that is a 4.0.4 CFW? Or maybe 4.4? I know stock only goes up to 4.0.4 but i think i read something about being able to get CFW based on stock so HDMI, FM radio, 720p recording etc etc won't be broken?
Thanks anyway!

oneNight1 said:
Or it might be better to go with the latest type that doesn't break anything. I'm guessing that is a 4.0.4 CFW? Or maybe 4.4? I know stock only goes up to 4.0.4 but i think i read something about being able to get CFW based on stock so HDMI, FM radio, 720p recording etc etc won't be broken?
Click to expand...
Click to collapse
Well, I haven't tried 5.1 so far, only following the 5.1-threads to see how it's going on.
HDMI is only working up to 4.0.4 roms, FM radio is working in 4.1 roms too, and you'll get 720p recording also in 4.4.4 roms. If you want all things working your phone is able to you will have to use roms based on stock GB or ICS. Therefore I'm using a stock based ICS rom most of the time (T-Rom).

By T-Rom for Arc S, i assume that you mean this? http://forum.xda-developers.com/showthread.php?t=1746508
Or if not then this port of it? http://forum.xda-developers.com/showthread.php?t=2239187
Sounds like something worth trying to see if it helps!
Thanks!

oneNight1 said:
By T-Rom for Arc S, i assume that you mean this? http://forum.xda-developers.com/showthread.php?t=1746508
Or if not then this port of it? http://forum.xda-developers.com/showthread.php?t=2239187
Sounds like something worth trying to see if it helps!
Thanks!
Click to expand...
Click to collapse
For Arc S the first link is the matching one. I think it's the most recently updated ICS rom for our device :good: