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!
Related
Hi
I wanted to load Wolf ROM onto my stock 2.3.3 Gingerbrand onto my Xperia X10i.
I downloaded latest flashtool from doomlord I enabled install from unknown sources earlier because I was installing some applications, but I haven't enabled debugging.
I opened flashtool, chose Kernel Downgrade and pressed OK.
I unplugged USB cable, turned off phone, pressed back button and plugged USB in.
From now on I can only see "Sony Ericsson" label on lightly lit screen, but the phone will not power on. It will not als power off by button (only when batterry is taken off)
I downloaded SE Companion 2.0, went to support zone, repair phone, but the phone couldn't be found.
Is this device bricked?
Flashtool says:
22/023/2011 23:23:08 - INFO - Searching Xperia....
22/023/2011 23:23:09 - ERROR - Please plug you device in flash mode
===============================
OK i got it back. I downloaded 2.3.3 stock firmware from topic 920746 - Generic version 2.3.3 build 3.0.1.G.0.75 (MD5: 36F52BAA3556CDD7E56383614C01E5D6), launched the flashtool and chosen this firmware.
I has some problems because I couldn't turn off phone (one of steps) so I plugged off battery, pluged in again holding BACK and it worked - my X10i is flashed to;
Android version: 2.3.3
Baseband: 2.1.71
Kernel v: 2.6.29.00054-g5fo1537
Compilation: 3.0.1.G.0.75
can you please show me how to properly load WOLF ROM onto this stock firmware? I tried with flashtool (Downgrade Kernel) and it stuck...
thanks
======================
Which version if wolfs ROM are you trying to install?
Sent from my X10i using xda premium
Try reflshing your phone back to 2.3.3 and then install the ROM again.
Drdan03 said:
Try reflshing your phone back to 2.3.3 and then install the ROM again.
Click to expand...
Click to collapse
He needs more help than that, he is completely getting the wrong endof the stick to install wolfs rom, thats why I asked which rom he wanted (Wolf has 4 different versions) then I can give him a step by step guide...
Hi
I successfully reflashed my Xperia X10i with ROM: Generic version 2.3.3 build 3.0.1.G.0.75 (MD5: 36F52BAA3556CDD7E56383614C01E5D6) found oh this website.
I had little problem though, because power button on phone was not working. On of the steps in flashtool is after plugging off the USB is to turn off the phone. Anyway I just removed battery.
I launched flashtool again, put the original firmware to firmwares directory, pressed flash button, chose generic firmware and flashing process started. It looked line on attached images in tutorials shown here.
And finally I could power on the phone (took little longer tha usual) I entered PIN for my SIM, did some basic configuration and I have fresh Gingerbread 2.3.3 on my Xperia X10i.
Anyway I want to give a try to WOLF ROM (which one you recommend for me?) or any other which is fast, because lately switching between menus, opening phone book was very laggish.
What ROM can you recommend for me, and can you give me clear explanation step-by-step, how to flash generic 2.3.3 to other ROM? Just put WOLF's rom into firmwares directory and flash with flashtool the same method I used to recover generic 2.3.3? I don't get these pre-roots and xrecovery - do I need this?
One more question - before I did reflash to generic 2.3.3 I saved phone settings and data with standard SE app, that after reflashing phone I was able to recover these setting - how is that possible? Is the recover file on SD card?
Regards
pc131 said:
Hi
I successfully reflashed my Xperia X10i with ROM: Generic version 2.3.3 build 3.0.1.G.0.75 (MD5: 36F52BAA3556CDD7E56383614C01E5D6) found oh this website.
I had little problem though, because power button on phone was not working. On of the steps in flashtool is after plugging off the USB is to turn off the phone. Anyway I just removed battery.
I launched flashtool again, put the original firmware to firmwares directory, pressed flash button, chose generic firmware and flashing process started. It looked line on attached images in tutorials shown here.
And finally I could power on the phone (took little longer tha usual) I entered PIN for my SIM, did some basic configuration and I have fresh Gingerbread 2.3.3 on my Xperia X10i.
Anyway I want to give a try to WOLF ROM (which one you recommend for me?) or any other which is fast, because lately switching between menus, opening phone book was very laggish.
What ROM can you recommend for me, and can you give me clear explanation step-by-step, how to flash generic 2.3.3 to other ROM? Just put WOLF's rom into firmwares directory and flash with flashtool the same method I used to recover generic 2.3.3? I don't get these pre-roots and xrecovery - do I need this?
One more question - before I did reflash to generic 2.3.3 I saved phone settings and data with standard SE app, that after reflashing phone I was able to recover these setting - how is that possible? Is the recover file on SD card?
Regards
Click to expand...
Click to collapse
I still need to know which version of wolfs rom you want to flash....please send me the link that you downloaded the rom from and I will be able to help you.
If you are unsure which one to flash, let me know if you have unlocked your bootloader or not (If you dont know what that means then you havent done it)
After that, use pccompanion to flash back to stock 2.3.3 and let me know (Preferably via PM) and I will help you out
Hi
I downloaded file Wolf_GB_2.3_TW.zip - I can't find from where I downloaded this, I think it might be somewhere from topic 1192988 (Wolf TW | Gingerbread 2.3.3 | Theme, Tweaks & Extra's).
I think I haven't unlocked bootloader yet (why should I?)
I am not sure about what versions you ask. Do these versions vary across different source android version or for unlocked bootloader? Or do these versions vary in deatails and specification?
I flashed back to generic 2.3.3 using flashtool (if you want flashtool version and 2.3.3 ROM file name, I can provide later) - the phone fresh like the day I bought it.
I would appreciate if you give me explanation what steps I need to flash generci 2.3.3 to Wolf ROM.
Thanks
pc131 said:
Hi
I downloaded file Wolf_GB_2.3_TW.zip - I can't find from where I downloaded this, I think it might be somewhere from topic 1192988 (Wolf TW | Gingerbread 2.3.3 | Theme, Tweaks & Extra's).
I think I haven't unlocked bootloader yet (why should I?)
I am not sure about what versions you ask. Do these versions vary across different source android version or for unlocked bootloader? Or do these versions vary in deatails and specification?
I flashed back to generic 2.3.3 using flashtool (if you want flashtool version and 2.3.3 ROM file name, I can provide later) - the phone fresh like the day I bought it.
I would appreciate if you give me explanation what steps I need to flash generci 2.3.3 to Wolf ROM.
Thanks
Click to expand...
Click to collapse
I will send you a reply to your pm when I get to my PC
Sent from my X10i using xda premium
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.
[Q] Rooted x10a stuck at "se" screen; SEUS, Flashtool not helping. What's next?
Working on my wife's AT&T x10a. When she got it several months ago it came with 1.6, and I updated to 2.1 through PC Companion. She recently decided she wanted root, so yesterday morning I rooted with SuperOneClick 1.5.5, after trying a couple of newer versions with no success. Root Checker from Play Store confirmed root. She said she really wanted 2.2 or 2.3, so this morning I started looking at installing a new rom.
1. Installed Flashtool according to this thread.
http://forum.xda-developers.com/showthread.php?t=928343
It recognized my phone, and appeared to have the needed drivers. I installed CWM via Flashtool, again it appears successfully.
2. Using Flashtool, and the instructions and files in this thread
http://forum.xda-developers.com/showthread.php?t=1192152
I attempted to install 2.3.3 via the Recovery method mentioned. It appeared to be going fine, I followed the instructions completely, but after step 13, when it's time to restart device, it loads the "sony ericsson" logo on the black screen, and hangs there. I left it for 15 minutes or so to see if anything happened, but nothing.
3. I then attempted to go back to stock 2.1 with SEUS, but it wants me to pull down the tray and hook up USB and tick Debugging. Well if the phone is stuck at boot there's no way for me to do that.
4. Attempted to flash x10a generic 2.1 from this thread
http://forum.xda-developers.com/showthread.php?t=920746
but ended up stuck at the se logo screen as in step 2 above.
At this point, I'm lost. I've been reading so many threads I'm having trouble keeping track of what I read and where I read it. I'm going to start from square 1, and re-read what I've gone through so far on the chance that I might have missed something. But in the meantime, any help or suggestions would be greatly appreciated. My wife is enormously patient about this, but it's her phone, and she really liked the little x10. I'd love to get it running for her again, stock 2.1, 2.2, 2.3, CM7, whatever it takes.
Thanks for any help you might be able to provide.
Have you tried an older version of f lash tool. Like 6.8. People have trouble with newer version. Use old flashtool and flash 2.3.3 stock ftf file
From my XPERIA X10S v8.2 @ 1.19ghz. IF SOMEONE HELPS CLICK 'THANKS'
I have always use flashtool to root (no super one click and other things) and there was never any problems so use only flashtool!
When u have an instruction to do something why do not use it?
My ideas:
1. Can u go to xrec now? U could try to restore some backup then.
2. Try to flash 2.3 stock with flashtool or repair phone in official pc companion software
3. Try to flash 2.1 stock with flashtool
4. Try older Flashtool versions
I had a similar problem, I just flashed a stock 2.3.3 firmware via flashtool and booted up fine
Sent from my X10S using xda premium
An update: last night (or rather, early this morning) in desperation I flashed a generic 2.1 x10i rom I had inadvertently downloaded yesterday, using Flashtool. Lo and behold the little phone came to life. Wife can make and receive calls, and Contacts came back. I have no idea why it worked this time, but at least the phone is functional.
So now I'm back to square 1. That's progress I guess. She still wants 2.3, so tomorrow I'll be starting the process over. Think I'll take a different tack this time.
Thank you all for your suggestions. I hadn't considered using an earlier version of Flashtool, though that makes sense; I had to try 3 different versions of SuperOneClick before I got one that worked. I used S1C at first because it seemed so simple, but looking at Flashtool I suspect things might have gone easier if I had used it from the beginning.
A couple more questions:
1. Will having the x10i rom cause any problems? I'm thinking not, but I'm a little leery after yesterday's difficulty.
2. I've heard reports that stock 2.3.3 is kinda laggy. I take you all are pleased?
3. Where's a good place to find stock 2.3.3 ftf?
Thanks for all your advice.
Longstreet said:
An update: last night (or rather, early this morning) in desperation I flashed a generic 2.1 x10i rom I had inadvertently downloaded yesterday, using Flashtool. Lo and behold the little phone came to life. Wife can make and receive calls, and Contacts came back. I have no idea why it worked this time, but at least the phone is functional.
So now I'm back to square 1. That's progress I guess. She still wants 2.3, so tomorrow I'll be starting the process over. Think I'll take a different tack this time.
Thank you all for your suggestions. I hadn't considered using an earlier version of Flashtool, though that makes sense; I had to try 3 different versions of SuperOneClick before I got one that worked. I used S1C at first because it seemed so simple, but looking at Flashtool I suspect things might have gone easier if I had used it from the beginning.
A couple more questions:
1. Will having the x10i rom cause any problems? I'm thinking not, but I'm a little leery after yesterday's difficulty.
2. I've heard reports that stock 2.3.3 is kinda laggy. I take you all are pleased?
3. Where's a good place to find stock 2.3.3 ftf?
Thanks for all your advice.
Click to expand...
Click to collapse
I dont know were you can get a 2.3.3 ftf file i havent found a working one:/ if i were you i would the 2.3.3 and install ferlabs rom for LB its amazing simple fast and awesome. and yes stock 2.3.3 is somewhat laggy but not really just root and install a custom rom! hope this helps you i remebr in i think 7.1 flashtool there is a rebrand option in the pull down menu to rebrand your x10 so like the porivders firmware i think? so try that if you need to
If your ROM won't boot but you have access to recovery, step one is to wipe cache and Dalvik cache and reboot. If that doesn't do the trick, reflash, rinse, and repeat.
I went a little ROM crazy this past weekend. I landed on CM7 for now, but of all the ones I tried X10S was probably the best "stock-like" experience. It's a port of the Xperia S firmware for the X10, and I was really impressed with the speed and responsiveness.
This guy does a little video demo, and you'll find a link to a helpful install guide in the vid description:
Fair warning, I flashed this ROM twice over the weekend, and both times it took multiple boots, pulling the battery and sometimes doing cache/Dalvik wipes in recovery, before I got past the "xperia" boot screen. It's really pretty common after flashing a new ROM.
it take a while but all Stock Gingerbread tft files are still here
http://forum.xda-developers.com/showthread.php?t=936733
try SEUS(Sony Ericsson Update Service) to install fresh v2.3.3 GingerBread directly from sony site, download this SEUS file -> http://www-support-downloads.sonymobile.com/Software%20Downloads/Update_Service_Setup-2.11.12.5.exe
I've looked and not found an identical problem.
I've an x10 mini pro (U20i) which workls fine with the SE firmware, but as soon as I install a new kernel (tried the gingerbread and ICS nAa) I get the system freezing after the kernel boot logo.
I can get into recovery if I hit the back key during startup, but other than that all I can do is remove the battery.
I've tried booting with just the new kernel and with new kernel +minicm7
Ive been using the flashtool (tried on both ubuntu and windows xp) and that shows that the bootloader is unlocked OK, and will allow me to go install the new firmware.
Even though the phone freezes, I can still get in with flashtool to upgrade the kernel again - but that doesnt help.
I'm using PC companion to take the phone back to build 2.1.1.A.0.6 firmware 2.1-update1 with baseband ending 4015 after my attempts fail.
I've tried now with and without a sim (phone is sim locked o2 uk) with 16gb sd and 2gb sd but I'm getting the same result every time.
I must be doing something stupid, but I can't see what. I've exactly followed instructions here and elsewhere to no avail.
So suggestions?
Is there any way that I can monitor what is going on through the boot process?
Is there another kernel that I should try?
I'm going to grab my wifes X8 and try that tomorrow, but for now I'm off to bed.
thanks in advance for any help.
I'm kind of thinking you're trying to use the kernels with the stock rom, and that will never work.
You say you tried the new kernel with minicm7, but which kernel did you flash when you tried that? and did you wipe the data/factory reset, the cache and dalvik-cache after you installed the rom?
All these things can have an impact on what you're trying to achieve
If you use the nAa ICS Kernel, you need the MiniCM9 ROM.
If you use the MiniCM7 ROM, you need the nAa-Gingerbread kernel.
Hope i've helped, and if the answer isn't here, you may need to be a bit more specific in what combinations you've tried and maybe where you got the kernels and roms from.
Sleep well
Hi,
Maybe thats it? I updated the kernel to gingerbread first then used the built in boot manager toinstall miniCM7 from the sd card.
Kernels taken from here, downloaded several times - in case of corruption.
Should I have installed CM7 first? I assumed the kernel needed updating before installing the updated interface.
So I'll need to install CWM onto stock first, then use that to install CM7 then once happy that that is OK upgrade the kernel?
I'll try it that way this evening.
No, installing the kernel and then installing minicm7 is ok, no need to do that the other way around
But did you make sure you got both from them both from the proper forum?
GB kernel from Here
MiniCM7 from Here
Strange by me it also freeze as i flash the kernel first. I install always with CMW on stock kernel and flash the nAa kernel than.
Interestingly:
requirements for that kernel are : miniCM7
requirements for CM7: latest kernel
However - redownloaded from those link and it worked.
Which is good, but also bad because I didn;t do anything differently to get it to work.
Since I did download a couple of times before, all I can think of is that I've inadvertently downloaded from elsewhere.
Hmmm
maybe is the bad memory management but when it happend to me i hard rebooted the phone then pressed the back button to go to recovery and before kernel boots to recovery i realesed it.If this problem keep existing then flash kernel,when it sows the logo pull out the battery quickly and then boot again
Okay i saw that some wanted to go back to the stock VZW 2.3.4. Even though its broken I have had the best result with it. So here I am posting this. I take no credit for this and ask you show the ones who are some thanks. :good:
Thanks to FXP and netizenmt :highfive:
1. Flash the 2.3.3 ftf then root and add cwm.
2. Unpack the 2.3.4 nan and put in the cwm backup folder. Reboot to cwm and restore then reboot.
3. Place the 2.3.4 ftf in your firmware folder in flashtool. Now open flash tool and select flash mode. Find the ftf and then uncheck all wipes and exclude everything except kernal. Reboot and re-install cwm.
You should now have a fresh rooted VZW 2.3.4. Works on locked and unlocked bootloader.
VZW-2.3.4-NAN
VZW-2.3.4-ftf
zackspeed said:
Okay i saw that some wanted to go back to the stock VZW 2.3.4. Even though its broken I have had the best result with it. So here I am posting this. I take no credit for this and ask you show the ones who are some thanks. :good:
Thanks to FXP and netizenmt :highfive:
1. Flash the 2.3.3 ftf then root and add cwm.
2. Unpack the 2.3.4 nan and put in the cwm backup folder. Reboot to cwm and restore then reboot.
3. Place the 2.3.4 ftf in your firmware folder in flashtool. Now open flash tool and select flash mode. Find the ftf and then uncheck all wipes and exclude everything except kernal. Reboot and re-install cwm.
You should now have a fresh rooted VZW 2.3.4. Works on locked and unlocked bootloader.
VZW-2.3.4-NAN
VZW-2.3.4-ftf
Click to expand...
Click to collapse
It may be broken but it is still nice to have it available!
It sure is. I could get most of my PS1 games working on this and I don't have to chase bugs. Kinda sucks games have such a issue on ICS and up though. The x getting left behind didn't help either but oh well. Think I am just going to sale this one after I set it back up and get me one of the JXD units that looks like a PSP.
Found a wired bug on the 234 ftf, not sure why I tested this last night on my play, I have a Casio commando so many play is just a game phone now so I flashed back to stock 234 with the original Kernal from the ftf and the back camera takes the picture like its supposed to do BUT if you use custom Kernal the back camera will not take the picture it flashes, but then freezes after. I've tried to different custom Kernal both the same out come back camera freezes but the front camera will work. So if your unlocked boot loader with custom Kernal the camera will not work back camera only works on the stock drive Sony Kernal
Dark Lords Development Team
I don't see why people don't go back to their 2.3.3 version. Much better than Verizon's fail 2.3.4