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.
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!
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.
Love this forum, and there are some proper good developments going on but sadly I have become lost in the plethora of links in posts and have lost confidence in doing what I want to do, so I was hoping somebody could give me a proper idiot's guide to the below:
2 months ago I finally found it in me to root my phone and to install Wolf's most up-to-date custom ROM on my X10. I obtained it from:
http://forum.xda-developers.com/showpost.php?p=17444017&postcount=10392
As my bootloader is locked, I chose the "Stock" link nearest the top. However I'd now like to use Doomlord's 'medium overclock' kernel (as even on the latest Wolfbreak ROM I still seem to get some major lagging - any ideas?) and I had a few questions.
I can see the medium overclock Kernel is available for download on:
http://forum.xda-developers.com/showthread.php?t=1253853
But is it just a case of me flashing this to my phone or do I need to do anything specific first?
And also, as I used the 'stock' ROM of Wolf's in the first link I gave above, do I need to then remove this from my phone and use the "Unlocked Bootloader Doomlord" instead?
Finally once a new kernel is in place, do my CPU settings for example set the speed automatically or is there a manual process?
Really sorry as I know this is all covered no doubt but like I said I just keep going from one post to another and I have managed to get myself quite lost!
Any help in as little stages as possible would be greatly appreciated.
Alex
as you are on locked bootloader Flash the kernel in xrecovery.It will work fine.
No you shouldnt use the unlocked bootloader version of rom.
you can use free app like No frills CPU app to adjust the cpu frequencies but just be careful not too increase it too much suddenly.
as much as i would like to help you im not confident myself, but i change kernels with the Flashtool, you know you download the kernel zip file, open Flashtool, turn your device off, press the lighthing button on the Flashtool and then choose the proper kernel file, and finnally Press the back button on your device and plug it into the computer, that should install the new kernel.
thats as far as i know... (pretty noob myself)
nope hes on locked bootloader so cant flash through flashtool
Flash the kernel(zip) through xrecovery
Thanks for the very quick responses
mirajp1 - I've only ever installed a custom ROM and some add-on zips (like Xloud etc) in xRecovery, how would I go about installing the kernel through recovery? I've not seen this process in any threads in my search.
Also what benefits will the change of Kernel bring me, as I had it in my mind that when changing the kernel to say, Doomlord's medium overclock, that the CPU frequencies would adjust as appropriate (so under heavy load it'd reach around 1113Mhz)
Maybe I've got the wrong end of the stick and changing the kernel will actually do nothing to improve things??
Thanks,
Alex
alex_ncfc said:
Thanks for the very quick responses
mirajp1 - I've only ever installed a custom ROM and some add-on zips (like Xloud etc) in xRecovery, how would I go about installing the kernel through recovery? I've not seen this process in any threads in my search.
Also what benefits will the change of Kernel bring me, as I had it in my mind that when changing the kernel to say, Doomlord's medium overclock, that the CPU frequencies would adjust as appropriate (so under heavy load it'd reach around 1113Mhz)
Maybe I've got the wrong end of the stick and changing the kernel will actually do nothing to improve things??
Thanks,
Alex
Click to expand...
Click to collapse
custom kernels give better performance and battery life.
On locked bootloader we have install kernel through xrecovery.
Download the kernel(zip file) from this post:
DoomKernel v06
install it through xrecovery.
It's done.
and yes kernel improves a lots of things.
If you are still not satisfied with performance than I would suggest you to use Feralab's rom.I use it and its great
Hope i cleared your doubt
Thanks mirajp1 !
But do I use "Install update.zip" or "install custom zip" in Xrecovery?
Alex
Edit: I just found the answer on another thread. (http://forum.xda-developers.com/showthread.php?t=1175531) Used Custom Zip option and did so, but there was an error message and it said the process was aborted. I rebooted the phone but it looks like the custom kernal has installed anyway. However, the phone is mega slow and when I ran FPS2D my fps was flicking between 30-50 and averaged 33fps. I have also had a number of FCs too so I am now convinced that I must have done something wrong here??
alex_ncfc said:
Thanks mirajp1 !
But do I use "Install update.zip" or "install custom zip" in Xrecovery?
Alex
Edit: I just found the answer on another thread. (http://forum.xda-developers.com/showthread.php?t=1175531) Used Custom Zip option and did so, but there was an error message and it said the process was aborted. I rebooted the phone but it looks like the custom kernal has installed anyway. However, the phone is mega slow and when I ran FPS2D my fps was flicking between 30-50 and averaged 33fps. I have also had a number of FCs too so I am now convinced that I must have done something wrong here??
Click to expand...
Click to collapse
I forgot to tell you to ignore the error
reboot into xrecovery and in advanced options try "fix permissions".
If still it doesnt work then I suggest you to reinstall the the rom again or try other rom you like
Thank you VERY much again
So just to clarify, the error "at line E" or whatever it was, is normal when installing a kernel through Xrec on a locked bootloader? (btw - is the reason I still see the "Sony Ericsson" text logo because it is locked? I don't suppose you could quickly list the benefits of using an unlocked BL?)
Also, whilst I am here (and as you have all been very helpful!) what do I need to do to set my CPU speed? I have seen the SetCPU app but the screenshots in Doomlord's thread look kinda complex at times (with all those I/O options etc) Is there a simple way for me to bump the speed up to 1113Mhz, as I know this state is now available as I have ran CPU Spy.
Thanks again for your help, I will try fix permissions (are there ever any dangers in doing this?) I hope to be able to speed it up, although I may give Feralab's ROM a go, I take it there is a thread for this with screenshots etc in the development forum?
Thank you,
Alex
alex_ncfc said:
Thank you VERY much again
So just to clarify, the error "at line E" or whatever it was, is normal when installing a kernel through Xrec on a locked bootloader? (btw - is the reason I still see the "Sony Ericsson" text logo because it is locked? I don't suppose you could quickly list the benefits of using an unlocked BL?)
Also, whilst I am here (and as you have all been very helpful!) what do I need to do to set my CPU speed? I have seen the SetCPU app but the screenshots in Doomlord's thread look kinda complex at times (with all those I/O options etc) Is there a simple way for me to bump the speed up to 1113Mhz, as I know this state is now available as I have ran CPU Spy.
Thanks again for your help, I will try fix permissions (are there ever any dangers in doing this?) I hope to be able to speed it up, although I may give Feralab's ROM a go, I take it there is a thread for this with screenshots etc in the development forum?
Thank you,
Alex
Click to expand...
Click to collapse
yes that error will come..just Ignore it ..!!
yes as you are on locked bootloader you willl see that white SE text.
there are many advantages of ul bootloader like the kernels are better,you can use cyanogen (cm) roms,etcc
you can use flashtool to unlock it but please read the thread of process properly before doing it.
Use No frills CPU app to easily increase frequency easily.Nothing else to do.
heres the link for Feralab rom : http://forum.xda-developers.com/showthread.php?t=1458001
also if you can wait for few days you should wait before trying it as he will be uploading last version soon.
fixing permissions doesnt harm your phone in any way ..try it
Awesome, thank you so much.
I've bumped it up to 1113Mhz, still slightly concerned at how sluggish the performance is (although it is reporting 50fps, I get the feeling it's running how it used to before I had the FPS uncapped) so I am still worried I have done something wrong! What's the best CPU monitoring app to look at CPU usage?
Thanks for listing the benefits of an unlocked BL. Is there a good thread that describes step-by-step how I would do this?
I may indeed try Feralab's ROM and thanks for the advice of waiting until the next release. The screenshots look very nice. I had hoped Wolfbreak would release a new version of his ROM.
Thanks,
alex_ncfc said:
Awesome, thank you so much.
I've bumped it up to 1113Mhz, still slightly concerned at how sluggish the performance is (although it is reporting 50fps, I get the feeling it's running how it used to before I had the FPS uncapped) so I am still worried I have done something wrong! What's the best CPU monitoring app to look at CPU usage?
Thanks for listing the benefits of an unlocked BL. Is there a good thread that describes step-by-step how I would do this?
I may indeed try Feralab's ROM and thanks for the advice of waiting until the next release. The screenshots look very nice. I had hoped Wolfbreak would release a new version of his ROM.
Thanks,
Click to expand...
Click to collapse
which version of wolfbreaks rom are you using?
the latest version is v7b6.
heres the thread for bootloader unlocking :
http://forum.xda-developers.com/showthread.php?p=19685019#post19685019
READ THE THREAD COMPLETELY BEFORE GOING AHEAD..!!!
and cpu spy is the best free and easy app for monitoring cpu.
Thanks for the response.
I believe I am using Wolfbreak's latest ROM as I only downloaded it just over a month ago, but I can't be sure, in my phones "About" screen there is "Build Number Wolf_Xperia_7.0.0s"
Thanks for the link on unlocked BLs, I may have to give this a go another time! If I was to unlock my bootloader, would I then need to install:
"Unlocked Bootloader Doomlord (You need Doomlords Kernel for unlocked Bootloader)" as shown on http://forum.xda-developers.com/showpost.php?p=17444017&postcount=10392 ??
I'm a little disappointed with the speed, even after the overclock, the reason I think I have done something wrong or something is not quite right is because I have read reports after other people have flashed a custom kernel/custom ROM saying their x10 flies along, but mine still has the stutters it has always had, like for example, taking ages to open the text messages part, or lagging when using widgets such as Flashlight. I'd love to get my phone to be of an excellent performance.
Thanks for all your help, you guys on this forum know it all!!
Alex
PS - just noticed on that link above that it says "Test version 6" - are those links old or something, cos I'm sure that's where I got my Wolfbreak ROM from (I used the "Stock" link at the top under the heading "Locked bootloader ROMs" when I did this a month or so ago)
then you are on the latest version.I guess reinstall would fix your problem
also to unlock your bootloader it is recommended to install the stock SE 2.1 or 2.3.3 rom.
after unlocking then you can use doomlords bootmanager.
The rom is quite fast and there shouldnt be any reason for lags.
try reinstalling the rom
mirajp1 said:
then you are on the latest version.I guess reinstall would fix your problem
also to unlock your bootloader it is recommended to install the stock SE 2.1 or 2.3.3 rom.
after unlocking then you can use doomlords bootmanager.
The rom is quite fast and there shouldnt be any reason for lags.
try reinstalling the rom
Click to expand...
Click to collapse
Thanks for the information
How do I go about re-installing the ROM, do I have to wipe everything (data, cache etc) or install over the top? Is there any way to keep my data (apps, texts etc) or would you recommend a clean installation?
Thanks
if you change rom then wiping data is recommended.
As for re-installing the same rom you can directly flash rom in xrecovery without wiping.but if still you have lags then you should clean install by wiping.
also if you reinstall rom then you should flash the kernel again on locked bootloader.
for backing up apps TItanium backup from market is the best.
as for data you can backup your whole rom in xrecovery and then Advanced restore-data in xrecovery.But restoring data can cause problems sometimes.
Me again!
I've noticed since using the custom kernel on my locked bootloader x10 that startup time has increased quite dramatically when switching the phone on. When I first installed Wolf's ROM using standard stock BL, it was very quick. Now it seems longer than stock BL/stock ROM. Is this because of the custom kernel and is there anything I can do to speed it up?
Thanks
alex_ncfc said:
Me again!
I've noticed since using the custom kernel on my locked bootloader x10 that startup time has increased quite dramatically when switching the phone on. When I first installed Wolf's ROM using standard stock BL, it was very quick. Now it seems longer than stock BL/stock ROM. Is this because of the custom kernel and is there anything I can do to speed it up?
Thanks
Click to expand...
Click to collapse
yes it can increase on locled bootloader .
i dont kno ways to increase that
Hi, only me again.
Although I am using DoomLord's custom Kernel on my X10, I still have the bootloader locked and as we went over previously, I'd like to unlock the bootloader so that I can use DoomLords kernel for unlocked bootloaders. I can then download the UBLDOOM unlocked version of Wolf's ROM.
Is there not an easier way of doing this? Most of the ways I have seen in threads seems very complex and I am not overly confident.
To summarise:
I am rooted (of course) and I am running Wolfbreak's latest ROM and DoomLord's v06-1113 custom Kernel. My bootloader is also locked. I'd like to run DoomLord's unlocked 1113 kernel from http://forum.xda-developers.com/showthread.php?t=1253853 - it mentions flashing it via FlashTool and then flashing the Wi-Fi module via CWMRecovery - is this the same as Xrecovery or not?
I do have Flashtool, but I don't know where to start! I apologise that I keep coming back and going on but there seem to be too many different guides out there!
Thanks for any info
Alex
this is the thread for unlocking bootloader:
http://forum.xda-developers.com/showthread.php?p=19685019#post19685019
after that download the kernel.
it will be .ftf file.
put it in firmwares folder in flashtool folder.
open flashtool.
press flash button and select the kernel.
connect phone in flash mode.
and let the process complete.
and boot up .
the flash recovery in xrecovery.
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
I have a Xperia U blocked bootloader rooted and with CWM installed.
I had an ICS .100 ROM installed and working perfectly but I decided I wanted to test Honami Experience ROM. As I had the terminal rooted I just downloaded the Honami Experience V2 ROM for blocked bootloader device, I copied the file to internal storage, I booted to CWM, I did a data/factory reset, wipe cache, wipe dalvik cache, and finally I installed the Honami_Experience_ST25i_v2_LB.zip from SD card.
After the installation finished I rebooted and as described in installation instructions it took some minutes to boot. After that the phone interface is working very smooth but I have lost many functionality: the sim card is not recognized, wifi is not working, cam not working, when I plug USB it is not recognized saying that the drivers can't be installed (in the windows device manager is shown as ST25i but with a warning under other devices), ... So basically the ROM is pretty smooth but useless this way. I'm not sure if I did something wrong though I think it is correct what I did. It is not important anyway just now.
So, my question is, what can I do to restore the mobile. I have already downloaded st25i_6.1.1.b.1.100 generic - user_sony.zip but the problem is that I don't find the way to put it now on the internal memory as the USB connection is not working. I have tried connecting the mass storage from CWM too but with same problem, windows can't install the drivers and in this case in the device manager shows it as Android instead of ST25i but with same warning.
As USB is not working I can't use flashtool to try to restore either.
I'm going to mention too that no matter if I disable the debug mode on the settings, it looks of on the user interface but when I reboot the phone it comes up with debug mode on always.
Any suggestions appreciated. My last solution would be to use bluetooth that seems it is working on the phone. The problem is just in this very moment I have another bluetooth device to send the data and that's why if possible I would like to know of any other way to solve this issue.
Thanks.
You should download file ftf and flash via flashboot mode
flash mode works
After reading another thread I have realized that flash mode works anyway so I have flashed the stock .100 and seems all is working now again.
So I change the question to, What have I did wrong when I installed Honami Experience ROM? I'm not sure what to do when the big Power Off button and Use Phone button appear on screen. I have waited a lot on that screen but maybe I did something wrong. What exactly I have to look at on that screen to be sure all is fine. When I flash the stock .100 I have no problems.
paulsm said:
After reading another thread I have realized that flash mode works anyway so I have flashed the stock .100 and seems all is working now again.
So I change the question to, What have I did wrong when I installed Honami Experience ROM? I'm not sure what to do when the big Power Off button and Use Phone button appear on screen. I have waited a lot on that screen but maybe I did something wrong. What exactly I have to look at on that screen to be sure all is fine. When I flash the stock .100 I have no problems.
Click to expand...
Click to collapse
I'm not sure, I also installed Honami v2 this morning but my phone is UB and it works normally. Have you followed the instructions in the topic, instructions for Lock Bootloader , your phone is ST25a or ST25i. you can do it again and report to the topic's owner
and power off and use phone button, it depends on you. if you are doing something, you can choose use to continue and turn off later
hungminhon said:
I'm not sure, I also installed Honami v2 this morning but my phone is UB and it works normally. Have you followed the instructions in the topic, instructions for Lock Bootloader , your phone is ST25a or ST25i. you can do it again and report to the topic's owner
and power off and use phone button, it depends on you. if you are doing something, you can choose use to continue and turn off later
Click to expand...
Click to collapse
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
paulsm said:
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
Click to expand...
Click to collapse
i think you should follow the instructions, flash the .10 kernel first. In UB, I also have to install another kernel to install this rom
hungminhon said:
i think you should follow the instructions, flash the .10 kernel first. In UB, I also have to install another kernel to install this rom
Click to expand...
Click to collapse
I tried and no way even with .10 kernel same exactly problems, no cam, no wifi, no sim recognized, ... Not sure if I'm going to try anymore. Really the stock .100 is smooth enough.
one more test
I tested once more. Just reread the instructions very very carefully.
- The instructions say that you have to start with 6.1.1.B.1.100 so I was doing it correctly from the beggining.
- The instructions say to root with superuser while I was rooting with supersu so in this last test, though I supposed it was not the problem, I decided to use superuser.
Again, same problems, no wifi, no cam, no sim recognized, ..., so I only can imply that Honami Experience doesn't work on locked bootloader.
If someone has tested too and read this and it is working for him in locked bootloader I would be glad to hear how he did it.
I can't ask for help nor notify it in the developer thread because of the limits imposed by xda-developers forums.
Thanks
Glad I saw this post...
I have a locked bootloader as well, and have been wanting to try various ROMS.
Was thinking about trying this one on the weekend, but now I'm not sure.
Currently using JB eXperience V2, it works well and everything works, but I'm always looking for something new to try.
I'm not savvy enough to fix problems, so would rather flash ROMS with few "bugs"
Sorry I know I didn't answer your question, but it certainly answers mine of if I should flash this ROM or not.
I certainly give credit to all the devs on here though, don;t get me wrong! They work hard!
need to re-flash the 6.1.1.B.1.100 firmware or not?
I wanna try it but have some questions.
Now I am currently on zperience 1.0. Can I install this rom on over it or sould re-Flash the 6.1.1.B.1.100 firmware.
smtsth said:
I wanna try it but have some questions.
Now I am currently on zperience 1.0. Can I install this rom on over it or sould re-Flash the 6.1.1.B.1.100 firmware.
Click to expand...
Click to collapse
The instructions say you have to start with 6.1.1.B.1.100 firmware
Always Flash the 6.1.1.B.1.100 firmware before flashing this ROM, then follow instructions
Click to expand...
Click to collapse
Same problems on LB
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
incry2 said:
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
Click to expand...
Click to collapse
Thanks for the info. In my opinion if the owner of the rom knows about all those bugs he should include the info on the rom thread.
The rom thread shows a list of bugs and if those bugs are only the bugs of the unlocked bootloader version he should have explained better.
When I decided to try I thought it was a full operative rom with just the few bugs that we can read on the thread. But wifi not working, sim not detected, screen not turning off, lock screen not working properly, cam not working, ..., are bugs that can't be ignored. With those bugs, even with only one of those, because all of them are imprescindible features, the rom is useless.
same problem
paulsm said:
The phone is ST25i locked bootloader. And on the moment I did the test was rooted, it had stock .100 firmware and CWM Touch 5.5.0.4. Taking that into account I just uploaded the Honami v2 zip file (for locked bootloader), I booted into recovery, wiped everything, I installed the zip from SD and rebooted when installation finished.
The only thing I can't be sure if it is wrong to start from .100 firmware (kernel included). Don't know if that is wrong and I must start with .10 kernel.
Now I have it again with .100 firmware, rooted and with CWM Touch 5.5.0.4 so maybe I can just flash .10 kernel and try again the installation of Honami from CWM.
Click to expand...
Click to collapse
incry2 said:
I have LB and i had the same problems with this rom, the wifi didn't work, the screen didn´t turn off. In fact, the same problems. The owner of the roms told me that they are bugs of the rom, i think he will fix it in the v3. As i see it works perfectly on UB, but i'm not going to unlock the bootloader.
Click to expand...
Click to collapse
same problem here. I Just tried 2 times but the problem is same... so waiting for v3