Hi folks,
I have been playing around with my old X10a and spent a few days trying out different ICS roms.
After a bit of a play I decided due to some bugs in the roms I would try out some 2.2.8 roms.
All of the roms I tried would not install with CWM 5 recovery and the version of ICS I was running would not load Amon Ra.
Enter the stupid part of the day.
I flashed the generic firmware that shipped with Flashtool and locked the bootloader.
So now I sit at the startup screen and it will not load the ICS rom, I can't get into recovery, and flashtool won't load a later firmware because the bootloader is locked.
PC companion when set up for repair mode comes up with 'no software available, try again later'
Any suggestions?
Cliff
darkfibre2 said:
Hi folks,
I have been playing around with my old X10a and spent a few days trying out different ICS roms.
After a bit of a play I decided due to some bugs in the roms I would try out some 2.2.8 roms.
All of the roms I tried would not install with CWM 5 recovery and the version of ICS I was running would not load Amon Ra.
Enter the stupid part of the day.
I flashed the generic firmware that shipped with Flashtool and locked the bootloader.
So now I sit at the startup screen and it will not load the ICS rom, I can't get into recovery, and flashtool won't load a later firmware because the bootloader is locked.
PC companion when set up for repair mode comes up with 'no software available, try again later'
Any suggestions?
Cliff
Click to expand...
Click to collapse
first thing.
Most stock based roms here are to be flashed via xrecovery not cwm so it wont boot. Also they require a different kernel than the ICS/cm9 version.
Also ICS/cm9 works only for unlocked bootloader.
You just need to flash a generic firmware to your phone via flashtool. You can find links in my signature. Flashing works for flashtool too. put the phone in flashmode and flash the stock firmware
THeLogiC said:
first thing.
Most stock based roms here are to be flashed via xrecovery not cwm so it wont boot. Also they require a different kernel than the ICS/cm9 version.
Also ICS/cm9 works only for unlocked bootloader.
You just need to flash a generic firmware to your phone via flashtool. You can find links in my signature. Flashing works for flashtool too. put the phone in flashmode and flash the stock firmware
Click to expand...
Click to collapse
Thank you very much for that info.
At first I was going to reply that I had already flashed 3.0.1.G.0.75 and then I noticed the files you linked to were much larger.
Lesson learned, not all firmware files can just be judged by the number.
Thanks again.
Cliff
Related
Hi everyone,
I was able to recover my phone on the weekend after trying my hand for the first time using FlashTool on the weekend. I understand now how putting .ftf files in the firmware folders work (please don't laugh at how non-technical I am with this - I am a Windows system admin by day - I just don't have a lot of under the hood experience with Android). I understand how to flash the .ftf files onto my handset.
I flashed on Saturday, in a means to recover my phone a whole bundled package (I got it from: http://forum.xda-developers.com/showthread.php?t=1192152&highlight=) It's essentially the stock 2.3.3 ROM and it has Baseband 2.1.71 prebundled.
The downside is that I can't install Xrecovery now because my phone isn't rooted now and I don't want to go through the process of using ADB to use gingerbreak.
Is there a 2.3.3+ ROM including BB 2.1.71 and xRecovery ftf bundle out there?
That thread is the pre-rooted 2.3.3 with recovery. Not sure what else you could want.
Try entering recovery when you turn the handset on and pressing the volume down key when you see the white Sony Ericsson text
Okay thanks. I've always entered recovery by going thru by pushing the back button (not volume down). Let me try it. I'll get back to you in a minute.
Ya pressing the volume down didn't get me into recovery. I've also tried installing xrecovery the usual way of downloading busy box, allowing non market apps, using a file mgr to open the xrecovery installer but it fails because the device isn't rooted. I can't su on a terminal emulator either so I don't think this rom i flashed is rooted.
It completely wiped my phone and installed 2.3.3 and 2.1.71 baseband (which is what I want) but now I want it to be rooted so I can play around with more ROMs.
Ok, I remember from when this first came out, you need to flash 2.1 firmware and root it, install xrecovery and then follow the procedure in that thread you posted. That should give you the pre-rooted and pre-installed xrecovery.
It's okay, If I'm going to do that much work I might just use the Android debug bridge (ADB) to install Gingerbreak. No big deal..
2.3.3 stock is a very nice improvement over 2.1 from what I remember. I used FreeX10 2.2 and it was nice as well (but I felt the UI looked a little dated). 2.3.3 stock looks and feels great, but I want even better battery life and better perfomane I know some of the custom ROMs can offer me.
I like the CM7 based 2.3.5 ROM I've seen on this site, and I wanna try 2.3 Free X10 from zdhiu.
Fair enough, I'm using the CM7 FXP rom and its flying. Battery life is pretty much the same as I was getting from SE firmware too.
Awesome!
So just to clarify the usual procedure:
You get your device rooted and xRecovery installed by whatever means. Since my X10 is a clean slate with just 2.3.3 on it with baseband 2.1.71, I will need to use Gingerbreak to root and subsequently install xRecovery.
Then put the .zip for the ROM on the SD card, flash it using xRecovery
Then remove battery, reboot, then using flashtool, flash the baseband and firmware?
I've only been using Android for a few months, and just learned about using custom ROMs in the past 6 weeks or so. I've learned a lot since then lol.
Sounds pretty much right to me if your bootloader is locked.
Okay, great. I really am learning more and more. I'm in IT myself for work, but phone hacking was never really my forte until just recently.
I like the type of flashing that I did in FlashTool with the current ROM I'm running from that previous post.
It was the baseband and firmware and ROM all bundled. I know FlashTool lets you make bundles too.. I find that easier than flashing the ROM in xRecovery and then flashing the firmware and baseband second.
What do you think?
I've found that installing the rom in xrecovery is good as I can make a full backup first and then flash the zip.
I always tend to flash the baseband and/or firmware first, but thats personal choice.
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Dresden21 said:
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Click to expand...
Click to collapse
Let me clarify...
1. ROMs are in zip packages, and are to be flashed using xRecovery.
2. Firmwares are in ftf bundles, which are flashed through flashtool.
3. If you want root and xRecovery on 2.3 follow aZuZu's post on rooting and xRecovery.
4. If you want to unlock the bootloader follow the_laser's thread
Dresden21 said:
Ya I understand all of that. I am fully aware how to install xRecovery (on ROMs previous to 2.3), how to take backups, wipe caches, flash zips.
I used FlashTool to flash a firmware (it was a .ftf file) for the baseband, however when I turned on my phone, it went to the Sony Ericsson white text, then white LED, then boot loop. So I didn't flash that file correctly or I didn't flash the right file.
Is there any prebuilt ftf packages for 2.3.3+ ROMs you know of that include the 2.1.71 baseband? I found that FreeX10's 2.2 ROM was very quick and made my whole Xperia experience more fluid and fast, so I'm interested to try FreeX10 2.3.. I don't know if zdhiu has a prebundled ftf.
Click to expand...
Click to collapse
You need to downgrade baseband so you can root.
Check here buddy....http://forum.xda-developers.com/showthread.php?t=1196808
then you can install xrec and install your rom. Might want to read this: http://forum.xda-developers.com/showthread.php?t=1254087
then this: http://forum.xda-developers.com/showthread.php?t=1278318
all very simple procedures.. good luck!
HELP!!! after searching all the posts i cant find a fix for this, i was running Team Rom on my X10, decided to change to MIUI prime, for some reason my phone then wont boot up after reboot? just stays on SE logo,I tried the SE PC companion, and after running the update process there, it returned error: there is no software available for your phone at this time??
I cant find any reference to this anywhere online??
Has anyone come across or know of a fix??
Thanks in advance
Get Flashtool. Look in the dev section.
just flash back your original firmware http://forum.xda-developers.com/showthread.php?t=936733 using Flashtool and redo the rooting back..back to your MIUI Rom flashing problem..did you read the cobrato method of flashing locked/unlocked bootloader?? if yes..after flashing the MIUI Rom completed using CWM5..immediately flash lockedBL.zip (i presume your X10 is locked)..then reboot
I had a similar problem, I screwed up flashing between roms and the phone wouldn't boot up. I ended up wiping everything, on phone and sd card. I really screwed up! I tried SEUS repair but it wouldn't let me, my bootloader is unlocked so that's why I suspect. In the end I flashed a stock 2.3.3 rom and went from there, all's good now. As for SEUS, even re locking the bootloader didn't help, something to do with DRM, not sure, at least flashtool is a life saver
you could always try the Update service from Sony, saved me a lot of times as that little gem
Flash back to 2.1 generic firmware using flashtool.
You'll need to find the 2.1 firmware on Google(its an xda thread). Then via flash tool flash that firmware. Now everything should work.
I hope you know how to put your phone in mto flashmode
Sent from FeraLabs v;3.0 Rom + patch +theme = best Rom ever for my x10. (Xda Premium)
If I helped you Out Hit Me up
And Press the Thanks BUTTON^_^
I've been having a look at trying a few custom roms on the Neo V and some say to install a different baseband. Some of the links aren't clear what I should be using. Is the baseband for the Neo the same as the Neo V?
I'm guessing that if I flash 4.0.2.A.0.62 then I'll get baseband 64, but I'm looking to see if I can flash just that baseband without the whole stock rom.
Yes you can! i have neo V .42 but having .283 kernel .62 baseband of neo! works perfectl!
I did this tonight and have had quite a few problems. Nothing wrong with the advice, I had other issues. While trying to resolve them I found my own thread, so thought I'd add some more info.
The baseband flash went fine until a point where it rebooted, then said it was connected with debugging off, even though I'd switched it off. It also said to make sure 2011 devices weren't in MTP mode.
At this point, I found another thread that said to flash the rom anyway, so I booted into fastboot mode & flashed a kernel. After that I booted to CWM and tried to flash CM7. I got an error that included getprop and I found the same error in the CM7 for Neo V thread. The solution was a new scripts-update file, but I already had it.
I edited the updater-script to run getprop, so I could see what it was returning and got an error to say getprop wasn't found.
At that point, I decided to flash the complete 4.0.2.A.0.62 rom, which went fine, though Flashtool did tell me I needed to install some included drivers at one point.
From there I followed the instructions on here to root 62 by flashing some of 42, though I did it slightly differently and ticked to exclude the baseband as that was the whole point of this.
After that I was able to install CWM again. I then booted into fastboot again & installed a different kernel. Booted into recovery & flashed CM7 + the Neo V fixes.
All good.
So if you get stuck in boot loops, weird things happen, don't panic. Use the search and you'll get there in the end.
Celtic67 said:
I did this tonight and have had quite a few problems. Nothing wrong with the advice, I had other issues. While trying to resolve them I found my own thread, so thought I'd add some more info.
The baseband flash went fine until a point where it rebooted, then said it was connected with debugging off, even though I'd switched it off. It also said to make sure 2011 devices weren't in MTP mode.
At this point, I found another thread that said to flash the rom anyway, so I booted into fastboot mode & flashed a kernel. After that I booted to CWM and tried to flash CM7. I got an error that included getprop and I found the same error in the CM7 for Neo V thread. The solution was a new scripts-update file, but I already had it.
I edited the updater-script to run getprop, so I could see what it was returning and got an error to say getprop wasn't found.
At that point, I decided to flash the complete 4.0.2.A.0.62 rom, which went fine, though Flashtool did tell me I needed to install some included drivers at one point.
From there I followed the instructions on here to root 62 by flashing some of 42, though I did it slightly differently and ticked to exclude the baseband as that was the whole point of this.
After that I was able to install CWM again. I then booted into fastboot again & installed a different kernel. Booted into recovery & flashed CM7 + the Neo V fixes.
All good.
So if you get stuck in boot loops, weird things happen, don't panic. Use the search and you'll get there in the end.
Click to expand...
Click to collapse
Rightly said my friend!
Well I was wondering the same thing- Can you flash basebands from 62 on 283? This thread has given me some answers.
I have some other questions though. I am a noob running stock neo v .283 firmware with unlocked bootloader(testpoint method) and CWM(the one for stock roms) installed. I want to flash the CM9 by FXP tonight. I have made a backup through CWM so that I can revert back in case something goes wrong.
Now the CM9 installation process involves flashing different kernel+baseband. If at some point I want to restore my previous CWM backup(taken on .283 stock rom), then what should be the procedure I should follow? For example, do I need to flash stock .283 .ftf+kernel again before I restore my backup through CWM?
I had a good search & didn't find a great deal about basebands. It would be useful to have something in the Neo section.
Flashing the stock ftf should include the kernel, I believe. You should be back at the same baseband & kernel and just need to install CWM again and restore your backup. I'd do the usual wipe everything in CWM before restoring, though.
Having said that, You've made me realise that I didn't note which firmware I was on before doing mine. So even though I took a CWM backup, I've no idea which stock to flash. Ah well, I wasn't planning on going back.
I later decided that the .283 firmware is simply too old and not supported by kernel/ROM developers anymore; besides flashing the entire stock .283 every single time just for restoring a backup seems too big a hassle. So I relocked my bootloader, updated to stock .62 firmware through PC companion, unlocked bootloader again, and then flashed a custom .62 kernel with recovery. After that I made my backup through CWM and installed CM9 afterwards. This way, all I will have to do for restoring my original backup is flashing the same custom .62 kernel. no ftf flashing involved.
Hi guys
I recently upgraded to ICS(Stock swiss one) and after using it for a few days without problems I flashed a kernel. I don't think it was meant to be flashed on ICS, so I reflashed the stock kernel again and now my phone doesn't get service and the IMEI is blank in service menu. Does that mean my phone's bricked?
Try to flash the ICS kernel?
randy_c said:
Try to flash the ICS kernel?
Click to expand...
Click to collapse
I flashed the whole ICS firmware and that solved my problem, thanks though
xperia s is generally very hard to kill, as i cannot imagine how can you loose fastboot or flash mode those are handled by software not designed to be altered and noone would ever want to
I was trying to deodex my rom and my phone got stuck up in bootloop. now it won't start. If I connect the USB the LED is red! I couldn't get it to flashmode or fastboot
Edit: It's the battery after charging for sometime I got into fastboot...
oh huh! while playing around I mistakenly flashed cache.sin as boot in fastboot! :-S
Guys,
I need help here too, i'm not sure if i did it correctly. This is all about rooting my XPS.
1. Updated to firmware .75
2. Waited for ICS 4.0.4 and updated.
3. Unlocked bootloader
4. Used flashtool , rooted with pre-rooted img available in XDA
5. flashed recover-img
6. flashed kernel.sin
My device could not boot into system instead it went to CWM Recovery Mode. But now it works fine. I can browse through my device. I'm still not satisfied with the way i've rooted my device.
Is there a way that i can do a clean reset and update ICS 4.0.4 and root my device with proper guide. I don't seem to find an easy guide here as some of the guide does not specify where to go bout getting something.
Thanks
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
jfsat said:
I have the 6833, and I have been rooting by downgrading to .532, rooting, installing recovery, and then flashing which ever ROM I choose. The problem is that if I try to flash anything else after that, the phone no longer boots. I can't even get the SONY screen to come on, nor can I get back into recovery. So when ever I want to try a new ROM, I have to go back to .532, root, and then install the new ROM I want to try.
Surely I am doing something terribly wrong, but I can't figure it out. I'm trying now to install Carbon KK (coming from stock rooted .757) and I once again have a soft brick. Any suggestions would be appreciated. Oh yeah, my bootloader is unlocked.
Click to expand...
Click to collapse
First off once you have unlocked the boot loader you nolonger have to do the downgrade/root/recovery dance if you get stuck. Just flasf the latest FTF then a rootable kernel (jackie099 normally has one out in a day or two of an updated firmware) then you can just flash recoveries/supersu/etc as needed.
Not sure why the installs are failing. If you have flashed a custom ROM (carbon/PAC/CM/...) and it doesn't boot at any point the first step is to flash the boot.img file that is inside the zip of the ROM. Do this in flashtool and put the phone into fastboot mode (vol. up when connecting to the PC).