first of all, allow me to say the main, obvious cause of the bricking of my poor x10:
i'm an idiot. A huge one.
With that being said, here's what's going on and how i end up suiciding my phone.
Was messing up, for my first time ever, with custom kernels.
I had free10 beta 4 with hotfix and latest xrecovery, and i decided to pop in a custom kernel; went to try out the freekernel 14xxxxxx "http://forum.xda-developers.com/showthread.php?p=13022717#post13022717", so i did all the passages.
At the end, everything was fine, but wifi didn't work.
So i downloaded and installed the wifi module and flashed with xrecovery, wifi the worked, but for some strnage reasons neither emails not (new) marked were working; they both gave no connection problem.
That's where i started losing my patience, i did full wype, went back to old market, but still no connection.
So went back here and found another newer kernel, 15xxxxx; xrecovery flashed that, and found out that wifi went back to gave error. Then i noticed that the kernel didn't boot, so what i did, like the huge idiot i am???
Went back to xrecovery, did full wype, reinstalled in this order: freex10 beta 4, beta4 hotfix, beta4 gapps, beta4cyanogen mod, kernel 15xxxx (again...), AND last thing, what i think bricked my phone: i installed this again "[OPTIONAL] if u want to make CUSTOM kernel as DEFAULT booting option then flash this file: chargemon_FXRec_default_CUSTOM.zip using recovery ONLY after u have installed the BootKit [Step 2]".
rebooted and BAM, it starts doing 2000 force close including system and android.launcher and if i turn off the phone and turn it back on pressing back to try to acces the xrecovery, it doesn't work.
Sorry for the long post but i wanted to make sure you all know what i did in details.
What the heck can i do right now??? Is there a way to get back to stock kernel? Is there a way to access again the xrecovery???
Re Flash with SEUS or FlashTool an your X10 will like a New one..
oh gosh i got carried away and forgot that ahahah.
Yeah i already did and god saves my soul my poor x10 is back at stock 2.1 but at last is working
pelly_jelly said:
oh gosh i got carried away and forgot that ahahah.
Yeah i already did and god saves my soul my poor x10 is back at stock 2.1 but at last is working
Click to expand...
Click to collapse
That's why we have xRecovery!
Always make a backup before messing with your phone!
Xperia X10i via Tapatalk
it's also OK for not having backups, as there are folks out there providing global ROMs...
so, are you going to flash custom ROMs again? ;-)
Related
Hello to all,
Firstly first post to this site and also new to the world of rooting/flashing so bare with me on this one..
Ok as title states I would like to know on how to successfully flash my x10 and receive the benefits that xda have given to alot of us!
Phone specs:
Xperia x10a.
Ver 2.1update1.
Rooted via super one click.
So far I have only been able to root the phone.. I have TB and have performed a back up recently. I do also have the Rom Manager app whilst watching a tutorial via youtube flashing using the Rom Manager I was not able to use the Flash ClockworkMod Recovery as the x10 was not in the listing to proceed. I have also got xrecovery ver 0.3 and tried another method using this but I was not able to install xrecovery properly.. I downloaded it all well and good but went to install and the 3 windows never became ticks just crosses.. Uninstalled and reinstalled but to no avail it did not work..
So my questions are:
Have I done something wrong on my end for this not to work? (knowing my luck yes).
And all I'm after if someone could take the time out and lay out a clear somewhat easy path in order for myself to be able to flash and install custom Roms? cm7 is what I would like to use unless if a good recommendation is given.
Thank you in advance to all and I do apologize for the long post I just wanted to make sure I covered everything.. Still new to this
Kind Regards.
Agera.
Xrecovery installer can be a bit troublesome. Sometimes it doesn't even work for me.
In my opinion, the best way to install xrecovery, root, & jit enable your x10 is through flashtool. You will need a PC but the process works better than the installer. Try that method and find out if that works.
Hey thanks for your reply, my noobness is showing greatly at this point regarding xrecovery... it'll help if I actually click install busy box and destination folder (duh) made me look....yeah Ok well now I have a phone that has been rooted and now have xrecovery in operation, I guess now comes to install a custom rom.
Now to sum it all up basically I have to copy paste desired rom and google rom pack load it onto the sd card (not in any file inside sd but just on sd) perform final backup get into xrecovery factory wipe first? I believe then custom rom reboot then get back into xrecovery then install google apps reboot and done?
I hope I got that down I'm trying to remember processes without having to go back to a tutorial, if I left anything out permission to give me a clip over the ear
Cheers.
When you pick a ROM, make sure the phone's baseband matches the ROMS baseband the developer wants. Also, follow how the way the dev wants the ROM installed, like phone wiped and cache wiped and stuff. And sometime there are multiple files that needed to be flashed in a specific order in xrecovery. So make sure you follow all the devs directions. Hope this helps.
Sent from my X10i using XDA Premium App
and you can find different ROMs that don't require you to flash googleapps as well, that just makes it confusing. I started with FreeX10, as it was simple and easy to install. once you have a hang of it, I recommend using Trip's GB MIUI. and you said you backed up phone before you installed xrecovery? I recommend you backup using xrecovery first
Sent from my X10 TripNMiUI using XDA Premium App
fixed phone was able to get back into xrecovery and do a restore...
Ok, something I want to ask regarding what I did today when I went to update to a newer o/s eveything went fine until after the phone rebooted and came back to the home screen the 2.2.1 froyo rom I used seemed to be refreshing itself every 2 seconds which made it next to impossible to navigate around the phone... The arc version 2.3.1 opened up and about 30 seconds it froze restarted and shut down again did that for a while... So both didnt work for me only other thing I opened up was the google pack so I could get the market and gmail, I also tried it without installing google apps... same thing happened.
So my question is have I forgotten to put an extra file in? or was it my blind luck that I used to unstable roms?
I've really tried here.. if anyone can please post a link that is certain to work with exactly what i need to do and what files I need that would be really great. Whether its 2.2 or 2.3 it doesnt matter to me so long as it works at this stage I'm having no luck getting something solid here...
Cheers.
hello i just did a clean fresh install on official se 2.1, rooted, busybox installed, flashed xrecovery about ten times now so i can flash the new zKernel. i can only get xrecovery to actually work prob 1 in 10 power ups and iv flashed the 20072011.zip file 3 times now yet it doesnt actually work. when i open about in settings its still the stock kernel, is there a way of flashing the new kernel using the flash tool or just plain without xrecovery????
cheers if anyone can help
What baseband are you using with the zkernal and tell me how to you make xrecovery appear on the boot up? There is only one way to do it.
Sent from my Atrix 4G with XDA Premium App
had the same problem... just made a work around which worked for me.. as i see, flashing zkernel does not delete anything... but this uuntz kernel delets the stock kernel any applies the custom kernel... so what i do is first flash the uuntz kernel which deletes the stock kernel and applies itself.. and straight after it without reebooting i flash the zkernel... and it works... i dont know how the hell it works this way but it works...
im having problems with xrecovery as well so flashing the two kernels is proving to be difficult. iv had xrecovery for about 6mths and booted into it fine everytime but now im on official se rom as i mentioned less than 1 in 10 boot ups will boot into x recovery
its giving me the ****s i hacked/flashed different roms from day 1 of owning this phone but now im on se rom nothing works iv even let se pc suit update it three times and started from scratch. ill keep trying xrecovery cheers for your help
[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
Mine could be a stupid question, especially since I''ve already downgraded successfully from ICS to GB, but anyway I'd like to have some feedback from anyone who's a bit more experienced than me
I tried stock ICS for Mini and I didn't quite like it (LED issue, too much heating, some app incompatibilities and so on) so I decided to downgrade to my beloved and trusted stock GB. BUT my bootloader is locked, and I had no internet access nor DoomLord's root kit with me either. This meant that, after downgrading to GB, I couldn't have rooted it, so no CWM, no Recovery, no backup restoring, oh well, I didn't feel like going around with a brand new phone for a whole afternoon (I'm an idiot, am I? ).
So here's what I did: I had CWM Recovery installed on stock ICS. I used Flashtool to flash only stock 2.3.4 kernel. Then I booted and when prompted by the brighter screen (no blue LED, damn ICS!) entered CWM Recovery (which, let me repeat that, I had previously installed on ICS) and restored a stock GB backup. I rebooted, and I'm on stock GB now. Great.
Now I'd like to know... even if everything's going just fine, and even if I can't think of a reason why I could get in trouble, I still think that maybe I just don't know something, or I forgot some important information, and this way of restoring a stock GB ROM could just be totally wrong. And here you come, experienced users: did I do something stupid?
Thanks for your attention... I just talk a lot, I know...
EDIT
Also: if I feel like going back to stock ICS, I suppose I can flash stock ICS kernel and then restore a stock ICS backup... right?
Feanor88 said:
Mine could be a stupid question, especially since I''ve already downgraded successfully from ICS to GB, but anyway I'd like to have some feedback from anyone who's a bit more experienced than me
I tried ICS for Mini and I didn't quite like it (LED issue, too much heating, some app incompatibilities and so on) so I decided to downgrade to my beloved and trusted GB. BUT I had no internet access, and I didn't have DoomLord's root kit with me either. This meant that, after downgrading to GB, I couldn't have rooted it, so no CWM, no Recovery, no backup restoring, oh well, I didn't feel like going around with a brand new phone for a whole afternoon (I'm an idiot, am I? ).
So here's what I did: I used Flashtool to flash only 2.3.4 kernel. Then I booted and when prompted by the brighter screen (no blue LED, damn ICS!) entered CWM Recovery (which I had previously installed on ICS) and restored a GB backup. I rebooted, and I'm on GB now. Great.
Now I'd like to know... even if everything's going just fine, and even if I can't think of a reason why I could get in trouble, I still think that maybe I just don't know something, or I forgot some important information, and this way of restoring a GB ROM could just be totally wrong. And here you come, experienced users: did I do something stupid?
Thanks for your attention... I just talk a lot, I know...
EDIT
Also: if I feel like going back to ICS, I suppose I can flash ICS kernel and then restore an ICS backup... right?
Click to expand...
Click to collapse
With an unlocked bootloader getting back / switching between gb an ics is easy.
Use in both ways a prerooted kernel with cwm. Install the kernel via flashtool. After that restore your nandroid and you are done.
That shouldn't take much more than about five minutes. Switching is so an easy way.
Gesendet von meinem WT19i mit Tapatalk 2
I did it with a locked bootloader. It doesn't matter, since CWM is not installed in the kernel (it's in /system, I think, but I'm not sure of it).
If you install CWM Recovery and then flash any stock kernel you can access the recovery even if it's not included in the kernel. That's what I tried, and it worked.
What I was asking is: is there any chance that this method can leave old/unwanted data on the phone? Based on what you said, it should be ok
I did the same but via wotanserver, because I have a belgian azerty mini pro and couldn't find the right firmware on xda.
Didn't have any issues, but you should remove all application data on your sd card to avoid problems.
I did like the complete ICS look, but it was too choppy, and too many bugs to live with.
jvdv360 said:
I did the same but via wotanserver, because I have a belgian azerty mini pro and couldn't find the right firmware on xda.
Didn't have any issues, but you should remove all application data on your sd card to avoid problems.
I did like the complete ICS look, but it was too choppy, and too many bugs to live with.
Click to expand...
Click to collapse
Thanks for your feedback
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