A noob question maybe
Will be possible to update our beloved custom roms from NobodyAtAll with latest se 2.1.1.C.0.0 with seus? I guess no
Or do we have to wait a new update from developers? And in this case do we need to comeback to se rom and make an update before installing 2.2/2.3 rom?
I have not clear why every custom rom targets a specific baseband, i thought that it installed everything no matter your current version
When did Sony Ericsson release a new update? Also, what differs this from .06?
Watch there : http://forum.xda-developers.com/showthread.php?t=1101332
Can't confirm it yet but some people say that baseband wasn't changed on the newest update, which would mean that you can definitely use any of nAa's ROMs.
yes it has been done, a lot have tried already
but NaA said there is no point in doing so
well if you want to try go ahead. then take time to use NaA's new clockwork recovery too since this update is still 2.1
Related
Hi guys. I think I have some pretty specific questions so I'll just go ahead and ask. Also this thread can hopefully help other AT&T users.
1. I've already used the Flashtool guide to get to Android 2.1 and I've rooted it. What I really want though is just the straight update from Sony Ericsson to 2.1. Now that the phone is no longer locked down with AT&T 1.6 software is there a way to simply install the official SE 2.1 update?
2. If I do have to stick with the update in the Flashtool guide should I do the customize option for JIT? What are the pros and cons?
3. Anything else I need to know? Basically I want the phone working 100% but running 2.1 instead of 1.6, I'm fine with the AT&T apps not being installed.
Thanks for any and all help!
Have you tried connecting your phone to SEUS/PC Companion, and do a factory reset? (not sure it will install 2.1, but if it doesn't, just update it through there)
but.. and this isn't scary at all, just install a good (wolfbreak's for instance) 2.2 ROM. You will notice a significant performance boost, with no downsides actually (can't think of anything not working)
edit:
but then again, i just noticed that at&t users cant use seus...(didnt know that...)
sooo.. just take a leap of faith and go for 2.2
where can I find wolfbreak's 2.2? and will it be as easy to flash as 2.1 was in the guide?
It depends on what you find easy. You do not need flashtool (as long as you have the 54, 55 or 58 Baseband.
To check what baseband you got, go to phone settings --> about the phone --> scroll down, and it should say baseband 2.*.** or something like that the last two asterisks is what matters.
(if you do not have the appropriate baseband, download the one you want from here, and install it with Flashtool)
Now, before you can install this ROM, you first need xRecovery, this program can be found here, along with a howto install guide
After you've successfully installed xRecovery, it is time to download the files from wolfbreak. His ROM can be found here.
Download:
- CM 6.1.3 [v05].zip for Baseband 54/55/58
&
- CM Update v053.zip [Will not wipe anything]
Place those files on your SD Card.. Now you can follow the 'Howto install' guide from wolfbreak
(oh btw, to enter xRecovery you have to do the following:
Press BACK button few times right after white SE label appears.)
kernelklink said:
where can I find wolfbreak's 2.2? and will it be as easy to flash as 2.1 was in the guide?
Click to expand...
Click to collapse
Its in the x10 android development section. Its one of the top links for in that section. I personally use rendeiro2005 ROM 2.2 cuz of personal looks. Hope this helps.
Sent from XDA Premium from my X10a rooted running 2.2.1 CM Rom from Rendeiro2005
so wolfbreak should be 100% working correct? no hardware problems?
what about rendeiro2005?
another thought...since these aren't from SE won't I lose timescape and mediascape? or is there some way to install them after the fact?
kernelklink said:
another thought...since these aren't from SE won't I lose timescape and mediascape? or is there some way to install them after the fact?
Click to expand...
Click to collapse
there is a thought.. mediascape is laggy, and you can get timescape
http://www.mediafire.com/?bxcc12wq10o2z0o
Ok, here's a good question. If I wait until the 2.3 update is released from SE and plug my phone up to SEUS will my phone be brought back to AT&T factory settings or will it actually be updated to 2.3 (now that I'm running a generic ROM)?
What I'm getting at is: Now that I'm running a generic ROM will SEUS try to update to new generic ROMs or will it somehow know the phone is AT&T and keep trying to go with what AT&T is currently using?
No, your phone is debranded after flashing so you can install 2.3.3 with no problems
so that means that if I plugged up to SEUS right now it'd give me the SE 2.1 update correct?
I'm currently running the 2.1 from the flashtool tutorial, but I'd like the official SE 2.1
I'll go ahead and answer my own question. Yes, apparently once you debrand your phone you can simply go to SEUS and update to the latest SE update.
I'm now running 2.1 straight from Sony Ericsson
I'll wait for the 2.3 update and get it through SEUS when it comes out this summer.
please help iv just brought a second hand x10 and its been updated to the latest flash from Sony firmware 2.1 update 1/ baseband 2.0.46/kernel 2.6.29/build 2.0.a.0.504 can i still use custom roms with this version and if so could you guide me to which one i can use.
martin15372 said:
please help iv just brought a second hand x10 and its been updated to the latest flash from Sony firmware 2.1 update 1/ baseband 2.0.46/kernel 2.6.29/build 2.0.a.0.504 can i still use custom roms with this version and if so could you guide me to which one i can use.
Click to expand...
Click to collapse
Not to far to look really...
It was just above your new thread...
All you need to know is here
If youre looking for a good ROM I recommend EWJet, and well that will require to flash new firmware and baseband, make sure you make a full backup of your stuff with xRecovery, before you try
no idea
but i dun like custom rom. since SE going to release official android 2.3.3 or 2.3.4 (not sure)
reason dun like custom rom becox the poor design
many thanks for the reply,s i will try the custom roms until se release their own new version
Hello,
I planned on trying some ROMS for the 2.3 Gingerbread and already downloaded some in the Dev area of the forum. I'm currently running 2.1 in my x10i and downloaded the necessary tools for the update. However, then I connected my x10 to my PC and ran SE PC Companion hoping to get the latest drivers for FlashTool. I got a prompt that a new update that is available (which is not surprising considering I want to try 2.3) but was stomped when I saw the software number (for lack of better term).
Now, I'm hesitant on doing an update since this update might mess up my upgrade from 2.1 to 2.3. Could somebody enlighten me on what this update does?
After doing further browsing I found out that this is the baseband update for the 2.3. I don't understand tho why it doesn't come up in the search when I tried the search function of the forum.
Anyway, would it be safer for me to update through PC Companion or do a direct flash since my 2.1 is already rooted?
You want to update to Gingerbread and install custom ROM or just install custom ROM from Eclair?
I'd like a rom that's closest to the stock first before trying any custom roms since I'm just new to Android and wouldn't want to mess up my phone due to me being a noob at this.
I've already downloaded the TEAM rom & some others but would like to see how my phone works with stock then move on from there.
So you should upgrade to Android 2.3.3 first through PC Companion, try it for few days and learn how Android works. Then you can install custom ROM if you want.
Hello to xda-forum's community!
I've bought new unbranded SE Xperia Mini Pro and it's my first Android device. I'm new to this forum and Android phones, but I'm aware of possibilities custom mods provides. I want to change stock Android to cyanogenmod 7.1.0.2 from official cyangoenmod site. But before I'll try all this I have couple questions for you:
1) Should I update my phone's official firmware before unlocking bootloader and flashing cyanogenmod 7.1.0.2?
2) Is there any option to make a full copy of my official Android before trying to flsh new one? I heard about NANDroid backup available in bootloader, but will it restore Sony Ericsson's Android if anything will go wrong?
3)What is the difference between mods and kernels? I assume I will flash new rom (cyanogenmod 7.1.0.2), but what will be the kernel?
4) How can I prevent bootloop problem during flashing cyanogenmod 7.1.0.2? From what I've read, it's a pretty big problem and nobody presented a full solution, in fact there wasn't any help at all. I searched a bit on other Sony Ericsson Xperia's forums, and this problem is not exclusive for Xperia Mini Pro, but appears in i.e. Xperia Neo, Xperia Mini etc. People claim that removing AntHalService.apk from zip archive (update-cm-7.1.0.2-XperiaMiniPro-SK17i-signed.zip/system/app) made flashing new stable cyanogenmod possible. But I don't know what to tkink about removing one of system apps. I have no idea what is it doing and if it's safe. What do you think?
4) Is everything working in this cyanogenmod 7.1.0.2 release?
5) What's the difference between cyanogenmod 7.1.0.2 from official site and the cyanogenmod 7.2 made by freexperia team? It's completely new cyanogen or maybe they're upgrading version 7.1.0.2? Or maybe they're making their own version of cyanogenmod and that's why it's still in development and some things arent fully working now?
I really hope someone will help me. Have a nice day
1) Yes you should update to the latest firmware .62 because the latest FXP106 requires the latest baseband to work properly.
2) Yes, once you have access to CWM, you can backup your rom.
3) I don't understand what you mean by "mod", you mean like a visual mod, like a .zip file you flash in CWM? A kernel is "a bridge between applications and the actual data processing done at the hardware level". People flash kernel for extra function, like CWM, Root, and Overclocking.
4) I never had any bootloop with custom ROMs, you just need to follow the instructions step by step and everything should work perfect.
4bis) Yes the phone is very functional with Cyanogenmod. Screen, 3G, Camera everything seems to works good, at least for me.
5) Freexperia Team makes both versions to my knowledge. 7.2 is an RC version, it has the latest fixes, changes.
Hope I answered your questions. If I were you, since you are new to Android phones, I would not try to switch to Cyanogenmod for the moment. Get used to your phone before doing anything serious (Cyanogenmod requires an unlocked bootloader, meaning you lose your warranty). Read information, threads, on your phone and Android to learn how things work.
I think I'll take your advice and won't try serious things right now. But I have couple more questions, it will be great if you'll answer
1) I see FXP106 requires the latest firmware, but there are some things not working properly in this version (i.e. radio), propobably because it's a RC. So are there things not working in latest stable cyanogenmod 7.1.0.2 from wiki.cyanogenmod.com/wiki/Sony_Ericsson_Xperia_Mini_Pro:_Full_Update_Guide? I prefer older release where everything is running than new but buggy.
2) Should I update my firmware to the newest one in order to install cyanogenmod from the above link? I still hesitate to do this because there is no way (at least for now) to root latest baseband .64 and rooting seems to be less complicated operation than flashing new rom.
3) In my previous post I asked about the difference between rom and kernel.
4) There's something I don't understand in the guide I linked. At first I'm unlocking the bootloader. Can I make a full backup of my firmware just after this point? Or should I update the kernel (via step with boot.img) and then make a backup?
5) Is it possible to boot firmware after step with updating the kernel? I mean, can I boot the phone after this step?
6) If I follow the above guide, at which point am I rooting the phone?
I'll try my best to answer your questions.
1) Honestly I didn't try Cyanogenmod much time but the latest FXP ROMs worked great for me, no major bugs and pretty stable! I would prefer the latest release if I were you.
2) Anyways if you want Cyanogenmod, you NEED an unlocked bootloader. That will make the ROOT process easy. First you ROOT your device to get access to recovery with a new kernel then you will flash the ROM. And yes you should upgrade to the latest version for Cyanogenmod.
3) ROM = it's the complete system, think of it like installing the OS on your computer. KERNEL = the drivers that allow software and hardware to interact.
4) Once you unlock you bootloader, you will be able to flash a custom kernel that will give you access to recovery (CWM) and there you will be able to perform a backup.
5) Once you flash a new kernel, it depends. If it's a kernel for stock ROM yes you can boot right away. But Cyanogenmod used a different kernel.
6) If you follow the guide, you are rooting your phone at the moment you flash a kernel that gives you root access.
polik1 said:
Hello to xda-forum's community!
I've bought new unbranded SE Xperia Mini Pro and it's my first Android device. I'm new to this forum and Android phones, but I'm aware of possibilities custom mods provides. I want to change stock Android to cyanogenmod 7.1.0.2 from official cyangoenmod site. But before I'll try all this I have couple questions for you:
1) Should I update my phone's official firmware before unlocking bootloader and flashing cyanogenmod 7.1.0.2?
2) Is there any option to make a full copy of my official Android before trying to flsh new one? I heard about NANDroid backup available in bootloader, but will it restore Sony Ericsson's Android if anything will go wrong?
3)What is the difference between mods and kernels? I assume I will flash new rom (cyanogenmod 7.1.0.2), but what will be the kernel?
4) How can I prevent bootloop problem during flashing cyanogenmod 7.1.0.2? From what I've read, it's a pretty big problem and nobody presented a full solution, in fact there wasn't any help at all. I searched a bit on other Sony Ericsson Xperia's forums, and this problem is not exclusive for Xperia Mini Pro, but appears in i.e. Xperia Neo, Xperia Mini etc. People claim that removing AntHalService.apk from zip archive (update-cm-7.1.0.2-XperiaMiniPro-SK17i-signed.zip/system/app) made flashing new stable cyanogenmod possible. But I don't know what to tkink about removing one of system apps. I have no idea what is it doing and if it's safe. What do you think?
4) Is everything working in this cyanogenmod 7.1.0.2 release?
5) What's the difference between cyanogenmod 7.1.0.2 from official site and the cyanogenmod 7.2 made by freexperia team? It's completely new cyanogen or maybe they're upgrading version 7.1.0.2? Or maybe they're making their own version of cyanogenmod and that's why it's still in development and some things arent fully working now?
I really hope someone will help me. Have a nice day
Click to expand...
Click to collapse
Hope you enjoy your Xperia Mini Pro! I'm loving mine
1)Yes, you should update your phone to the lastest firmware. It worked for me when I did it
2)Yes there is, after you unlocked the bootloader and flashed a kernel on, in the ClockWorkRecovery Mod, there is a "backup or restore" option to backup the Xperia Mini Pro stock ROM
3)ROMs is the UI your phone will be using for example HTC Sense is HTC Sense UI and Kernel is the driver for yours phone software and hardware to interact and process
4)I tried to flash CyanogenMod 7.1.0.2 and I got stuck on the bootloading screen, I did many methods and such and I couldn't stop the looping. Plus the Official CyanogenMod team has given a statement or a bug fix to fix it. Though CyanogenMod 7.1.0.1 works but has many bugs to fix out, the biggest one is that Vibration doesn't work.
5)The FreeXperia teams works more on the Mini phones then the Official CyanogenMod team because the CyanogenMod team, usually ports the ROM from another phone and then does all the bugs fixes. While the FreeXperia Team, works fully with the Mini and Mini Pro phones, building a ROM around the phone instead of a port. (Thats what I heard, not fully sure)
If your new to the Android community, do not root or flash a ROM without getting to know how it all works. Plus it will void your warranty. Hope all this helps
do i need to manually update the baseband of my phone? or each kernel/ROM has differrent baseband? help me plz
if a different baseband is required for a certain rom then this will usually be posted on the first page..
just check requirements of the custom rom first.
custom kernels - official ftfs
i just wanted to know if there're any risks of flashing ftfs while using a custom kernel. for example, i installed a custom kernel (Rage something) which only supports stock ROMs. i have a LWW which had .62 baseband. i downgraded it to .42 for rooting and all that. now, will my phone get bricked or something if i flash a different ftf, official or otherwise? (for instance, like the one in this thread: http://forum.xda-developers.com/showthread.php?t=1605150) the thread has .70 baseband, but as far as i know, latest officially released by SE is .62, so is this a custom one? also, how do i root .62? i have already unlocked the bootloader.
also, if it's not too much trouble, can u pls explain the architecture? as far as i can understand, Kernel and ROM are parts of the OS, rite? so what's the baseband (firmware), considering these are all software components?
just checked the link that you have posted. this is the ported official ICS rom.
that rom has its own kernel.
flashing it to your current kernel would brick the phone.
also there will be big differences because you currently have GB (Gingerbread).
baseband is the radio firmware, that is for the phone signal. this will be region dependent.
so, the baseband is the ftf thing, rite? but ppl were saying that .58 (in LWW) had some bugs like repeated rebooting of the phone, and that .62 fixed this bug and also improves battery life.
also, i repeatedly flashed many kernels into my phone. i mean, every time i tried a new ROM, i had to install the kernel provided with it (like FXP 115, or the one provided with the rom, the boot.img), over the already existing kernel, but i had no problems. so when does the risk of bricking come into play? i couldnt really understand what u meant by, "that rom has its own kernel. flashing it to your current kernel would brick the phone."
and yeah, i tried some ICS roms, like these:
http://forum.xda-developers.com/showthread.php?t=1434001
http://forum.xda-developers.com/showthread.php?t=1445821 (FXP 115)
CM 7.2 RC0 coconut
each had its own problems, so i reverted back to stock. but gotta admit, the CM9 android 4.0 UI was really awesome compared to GB
when i was using .58fw, did not encounter the automatic restart.
never noticed that much difference also after upgrading to .62
this is the build or sw version of the rom.
the baseband is independent from this build of the rom.
you are doing it correctly, flashing the required kernel for each rom.
if you would just flash new rom over any kernel would result to bootloops.
bricking is really minimal and there are still ways to fix it,
it is rare that changing roms and kernel causes permanent brick unless there was already a hardware problem to begin with.
im also checked this roms but haven't installed them yet.
will stick with hybrom for now,