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
Related
I am completely new to all this but I install some custom roms on my x10 but so far every rom ive installed either doesnt see my sd card or gives me service but no 3g or no service at all. Ive read around and people are saying to flash the rom or something but I have no idea...please help
Hey man,
What have you updated to?
I have the same issue on my phone, ever since i've tried new roms its either been on and off or completely not working.
Theres baseband which i believe is the main basis for the rom, so without the right baseband the rom wont work as it should. Some roms come with the correct baseband. You need to put the .zip rom onto your SD card.
First flash with the right baseband then install Xrecovery. Reboot phone, once it vibrates keep pressing down on the volume control and install custom zip. It should work from there, but so far I haven't had it work for the roms I've tried ;(
ok thanks. How do I flash the rom with the right baseband? I have no idea
I finaly got it to work! I did a reinstall with seus and a factory reset then flashed a generic firmware for x10a with the flash tool to my device. rooted it with z4root installed busybox and xrecovery and then through xrec i installled my custom .zip and I got servie but no 3g so I manually typed in the apn settings from this site....they wont let me post a link .... and everything works perfectly!
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
I tried searching to install custom kernel , i couldnt find one.
1.) should i have to install/flash the custom kernel while i am at V5s and then flash V5c over it ? or how to proceed ?
2.) anyone on ULBL + custom kernel and find any significant or notable performance increase / stability ?
3.)Also can someone tell me how to remove "GET GAMES" , "EXTENSION SEARCH" & "MEDIA SERVER"(If possible) .
4.) Also is there a way to freeze "setup guide"
I am on WB V5s ROM now .
any one ?
/10char
1) You can flash a custom kernel now, you don't need to flash v5.0c first
2) I get pretty good battery life with Freekernel and I suppose overclock would mean faster performance, but I don't personally use high frequencies.
3) Use Titanium Backup
4) I think Titanium Backup Pro would be able to
Thanks a lot first for replying.
1.)select a custom kernel ftf file and flash while in V5s ? and then flash a V5c after ?
do i need to check for signal / radio working after flashing a custom kernel or any other kind of procedure ? I tried searching but there is no proper installation instruction given . thats i posted here.
2.) to ULBL , do i have to be in any specific kernel ? mine is not network locked. also ULBL will prevent me from using SEUS for further updates ? or incase if something goes wrong , SEUS is the final hope to flash to a stock GB and get back to WB or any custom ROM`s now.
3,4.) Will Do with TB . I wanted to know freezing them wont affect the phone working right ? particularly "setup guide"
Again thanks for the reply
Before anything else, is your sim unlocked? If you used anything other than SEtool2 to unlock your sim, I don't think there is a method to unlock your bootloader yet. This link describes the steps and requirements. Follow those steps and you'll only need to downgrade your kernel to unlock bootloader. Then you can upgrade back to GB kernel.
Now if you can unlock bootloader, I assume you're tying to flash DoomKernel 5.0. Flashing custom kernel ftf file requires unlocked bootloader. If you've already unlocked, you can just flash that ftf. You don't need to mess with WB v5.0c at all. The only difference between WB's roms is that 5.0c already has DoomKernel 4.0b. Doom also provides wifi modules that you can flash via Xrecovery for working wifi.
If you have any problems, there's a tool to relock your bootloader.
I don't think freezing setup guide will affect anything, but I am not sure.
Ogbert_theNerd said:
Before anything else, is your sim unlocked? If you used anything other than SEtool2 to unlock your sim, I don't think there is a method to unlock your bootloader yet. This link describes the steps and requirements. Follow those steps and you'll only need to downgrade your kernel to unlock bootloader. Then you can upgrade back to GB kernel.
Now if you can unlock bootloader, I assume you're tying to flash DoomKernel 5.0. Flashing custom kernel ftf file requires unlocked bootloader. If you've already unlocked, you can just flash that ftf. You don't need to mess with WB v5.0c at all. The only difference between WB's roms is that 5.0c already has DoomKernel 4.0b. Doom also provides wifi modules that you can flash via Xrecovery for working wifi.
If you have any problems, there's a tool to relock your bootloader.
I don't think freezing setup guide will affect anything, but I am not sure.
Click to expand...
Click to collapse
really thanks for the reply.
I ran s1 tool and got the following
RUNNING S1_EROM VER "R8A013"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "R4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: CXXXXXX8
SEMC SIMLOCK CERTIFICATE
Elapsed:26 secs.
Click to expand...
Click to collapse
i think mine is not simlocked right ?
i will wait for ULBL for sometime .
can you tell me how to proceed to get custom kernel , either Doom`s or zKernel currently from WB V5 s . always WB used to say to boot and get the signal and then proceed to next step in some cases .
what exactly is the procedure to get a custom kernel on a WB V5 s.
Thanks for helping me out.
If you're not going to mess with unlocked bootloader, it makes things a lot easier. You can just install a custom kernel through Xrecovery or just flash WB v5.0c over your v5.0s.
Ogbert_theNerd said:
If you're not going to mess with unlocked bootloader, it makes things a lot easier. You can just install a custom kernel through Xrecovery or just flash WB v5.0c over your v5.0s.
Click to expand...
Click to collapse
actually last time i flashed V5c over 4.04 and ended up with bootscreenlock up.
thats why i wanted to know the exact procedure. when i flashed the wrong ROM over stock kernel last time , volpad told me to clear dalvik cache and reboot so that it will work , he too said V5c has its own Doom`s kernel , but it didnt work for me. I ended up using SEUS to get into Stock GB and get back to WB V5s now.
Then your phone could just be incompatible with Doomkernel. The same thing happened to me actually. I installed v5.0c over v4.0.4c and ended up in a lock up. I took the battery out, put it back in, started up the phone again, spammed back button to get into Xrecovery and installed Goro's kernel. My phone then booted up normally. Since, you're on v5.0s, just install a kernel that's not Doomkernel through Xrecovery.
Ogbert_theNerd said:
Then your phone could just be incompatible with Doomkernel. The same thing happened to me actually. I installed v5.0c over v4.0.4c and ended up in a lock up. I took the battery out, put it back in, started up the phone again, spammed back button to get into Xrecovery and installed Goro's kernel. My phone then booted up normally. Since, you're on v5.0s, just install a kernel that's not Doomkernel through Xrecovery.
Click to expand...
Click to collapse
well i didnt install V5c over V4c . I did a flash of V5c over V4s .
sorry for askingagain n again , since i am not quite clear.
V5s doesnt support custom kernel right ?
so if i flash a custom kernel then V5s wont be compatible right ? then i have to flash V5c over the flashed custom kernel right ?
also do i need to to boot in to see if signal/radio works and get back to flashing other things , procedure like that ? ?
None of that matters. Think of it this way, v5.0c is just v5.0s that already has Doomkernel installed. If you flash Doomkernel onto a v5.0s, then you effectively have v5.0c; however, since Doomkernel causes your phone to lock up, you'll have to choose another kernel. Here's Goro's kernel, which I have had luck with. Doomkernel FS series should also work, but it doesn't have OC/UV.
So try this:
1) flash WB v5.0s (which you already have, correct?)
2) reboot and check for signal, if you are concerned
3) reboot into Xrecovery and make a back-up, if you want
4) now flash whichever kernel you choose
5) reboot, of course if it everything boots up then you're good to go
Ogbert_theNerd said:
None of that matters. Think of it this way, v5.0c is just v5.0s that already has Doomkernel installed. If you flash Doomkernel onto a v5.0s, then you effectively have v5.0c; however, since Doomkernel causes your phone to lock up, you'll have to choose another kernel. Here's Goro's kernel, which I have had luck with. Doomkernel FS series should also work, but it doesn't have OC/UV.
So try this:
1) flash WB v5.0s (which you already have, correct?)
2) reboot and check for signal, if you are concerned
3) reboot into Xrecovery and make a back-up, if you want
4) now flash whichever kernel you choose
5) reboot, of course if it everything boots up then you're good to go
Click to expand...
Click to collapse
Really thanks a lot ...
I think your reply here will serve as "HOW-TO" for many who seek how to install Custom Kernel and ROM.
yes i am on WB V5s now
one last question . After custom kernel (i will go with Goroh`s Kernel itself) installation , and after rebooting , should i have to flash V5c ?
No, do not flash v5.0c. That would overwrite everything and you'll get locked boot screens again.
Ogbert_theNerd said:
No, do not flash v5.0c. That would overwrite everything and you'll get locked boot screens again.
Click to expand...
Click to collapse
thanks for clearing the doubt. so if WB updates his ROM , which version should i choose next time ? s or c ROM ?
S-version should always be safe, but you would have to reflash a custom kernel afterwards. C-version may or may not be okay. Depends on what custom kernel Wolfbreak decides to go with in the future or if Doom adjusts his kernel. During bootup, Doomkernel briefly peaks at 1.228Ghz, which causes some devices to freeze or lock up. If you're unsure, you should go with S-version.
Ogbert_theNerd said:
S-version should always be safe, but you would have to reflash a custom kernel afterwards. C-version may or may not be okay. Depends on what custom kernel Wolfbreak decides to go with in the future or if Doom adjusts his kernel. During bootup, Doomkernel briefly peaks at 1.228Ghz, which causes some devices to freeze or lock up. If you're unsure, you should go with S-version.
Click to expand...
Click to collapse
thanks a lot. this might be normal , but last time Custom kernel in V5c ran few codes art boot-up and after that the lock-up occured , might be the problem you are saying here , peak of frequency.
thanks a lot for taking time and replying for each question.
will flash a custom kernel and report back with PM to you.
again , really thanks for all the help.
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!
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.