Hey,
I´m a new user, but a long time lurker.
I have a weird 'bug', or maybe it´s something i´m not doing right (and i did use the search button):
My x10a does not run properly with rendero´s CM, nor with any other 2.2 rom - It keeps restarting itself after one or two minutes.
But with bluesparks v5 and any other 2.1, it works normaly.
The baseband is: 2.1.54;
kernel 2.6.29 SEMCUser at SEMCHost#1
version number is: 2.1.A.0.435
I tried updating with SEUS, but it didnt work.
I used flashtool to flash the dual touch firm, the .435 firm, restored to factory default, but it still reboots after applying the update through xrecovery. I also followed ALL instructions
Any toughts on this?
Thanks in advance and sorry for my bad english.
i thought you were supposed to use the flashtool instead.
aR_ChRiS said:
i thought you were supposed to use the flashtool instead.
Click to expand...
Click to collapse
Quoting rendero from his own topic:
YOU SHOULD INSTALL THIS THROUGH xRecovery.
IF YOU`RE NOOB AND DON`T KNOW WHERE TO START PLEASE GO HERE.
THIS IS FOR LATEST BASEBAND ONLY(54)!!! CHECK MY SIG AND GO TO [FLASHTOOL GUIDE] HOW TO for n00bies TO UPGRADE
Instructions:
- Make a backup (if you want to);
- Factory Reset (Full Wipe);
- Wipe cache partition;
- Wipe Dalvik Cache (Advanced options > Wipe Dalvik Cache);
- Wipe battery stats (Advanced options > Wipe battery stats);
- Install [MOD][rendeiro2005]Cyanogen6.1.1.zip;
- Reboot;
- Let him reboot one more time and you`re donne;
- Go to Settings > CyanogenMod Settings > User interface > Tweaks extras > Select a theme > Cyanogen
- Install Google_APPS.zip;
- Reboot;
- Let him proccess cache files for about 10 minutes then reboot.
- Donne.
Well, seems to me that he´s talking about xrecovery, but i´ll see if i can do it via flashtool.
Thanks!
It worked. My x10 was locked until yesterday.. when i received the subsidy code from Claro, i decided to try again, and it worked like a charm. Thanks!
Since flashing this the screen is so sensitive I can't even scroll without it selecting something and using key pad is a nightmare. Is there a way to reduce the screen sensitivity?
Sent from my HTC HD2 using XDA App
Related
Hello,
i want wo update my X10 but i have some problems.
I have succesfully rooted my phone and installed xRecovery too.
Then i install "X10i_2.1.A.435_GLOBAL-GGL GENERIC 1232-9897 - Global Generic" to my X10 without any problems.
I boot my x10 some times but i have no network access (2/3/4G) and i cant use WLAN...
Then i look at the system info and see "baseband version: unknown"...
What is the problem with my update???
I still tried to flash the update again but nothing has changed.
Sorry for my bad english guys... ^^
mfg
Flo
Plenty of solutions to your problem on the forum if you use search but...
Your problem is you installed the new software over your old without wiping data (Factory Rest) in the Xrecovery options before you flashed it.
If you backed up your original first...
Go to Xrecovery (Restart phone and press back button a few times while "Sony Erricson" is showing)
Move to wipe User data (Factory Reset)
THEN reinstall your back up.
THEN you can go back to Xrecovery menu
Wipe User Data (Factory Reset)
Then Install the new global generic software.
This should fix your data and signal errors and also give you a working baseband number.
Thanks for your help but it doesn´t works...
I have the same problems than before...
Baseband version ist still unknown...
Any other solution for my problem???
If the rest of your phone is still functional after re-installing the latest firmware with xrecovery then you might want to try installing one of the custom ROMs for this .435, like the high performance ROM kx10 R2B001. This ROM is definately better than the stock firmware just look it up in the development forum.
Hey im sorry about my above post... when i said with xrecovery i ment make sure you have xrecovery working; not installing the firmware with xrecovery as all firmware uses the flash tool.
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the two files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?) Now DON'T reboot before you made the next step, cause you have to start from zero if you reboot before making the next step
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
9Lukas5 said:
Cause of I read it from many users, that they get WLODs anymore on the newest Cm7 release from J and I haven't problems, I'll share a list with steps to install it, with that it worked for me perfectly.
If you have a working Recovery you can start directly with step 6
1. Flash with Flashtool a stock firmware
2. Boot up into stock
3. Activate usb debugging
4. Root it (connect phone with activated debugging mode and press in flashtoll root)
5. Install FreeXperiaRecovery (connect phone again, click "ask root permissions" and then click on xrecovery button)
6. Download the Cm7 rom form here, and the files from here: http://forum.xda-developers.com/showthread.php?t=1073859
7. Copying all files needed for flashing the rom on your sdcard: Cm7 rom and the Screen off fix
8. Reboot and check if you can enter Recovery
9. If not, start at the point where you install it via Flashtool
10. If yes, take out the battery and wait ~15-30 sec.
11. Now put your battery in again and flash the .ftf bundle from the thread i linked above
12. If it flashed succesfully reboot and enter Recovery. Make ALL available wipes (full wipe, wipe cache, wipe system, wipe battery stats, wipe dalvik cache. I think that are all, right?)
13. Flash the Cm7 rom
14. Flash the screen off fix
15. Reboot and wait until you get into the rom.
Note:
I know that J provides a own Baseband package, but i use this .ftf bundle, where I mixed the 435 Firmware parts with the amss.sin of the bb.52 bundle available in the bbcollection thread and I haven't any problems with this and on that way, you haven't to flash always the normal and the modded bb if you switch between roms.
Click to expand...
Click to collapse
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
where can i download FreeXperiaRecovery?? I will tray this!
avez197 said:
Hi there. I am curious to try this. How is your battery life. Also, which version are you running, the previous "b" or "c". Reason i ask is because on your signature, it says "7.0.3-X10-J020b"
Thanks
Click to expand...
Click to collapse
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
9Lukas5 said:
I have runned this way J020b, I would try the c, but I can't! It's bad, but my phone is at the se service point for repairing it. But if I get it back, I'll install directly the latest Cm7 version again.
Click to expand...
Click to collapse
Thanks. Will give feedback after trying
barsom said:
where can i download FreeXperiaRecovery?? I will tray this!
Click to expand...
Click to collapse
If you download Flashtool 0.2.9.1 there is FreeXperiaRecovery included. Look into the list, there wrote to click on the xrecovery button for installing FreeXperiaRecovery. The files are included in flashtool.
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
nadiros said:
@ 9Lukas5
Hey, just for clarification - I thought it was never a good idea to use the option
"format system" in the "partion tools" sub menu of xrecovery?
Doing this will erase everything - including xrecovery itself [self destruct] and therefore the user would not have any option except complete reflash if anything were to go wrong with the subsequent install.... ?
Correct me if I am wrong.
Edit: if this is what you meant by "wipe system" in OP !
Click to expand...
Click to collapse
Yes i ment this.............maybe you're right, cause it will be formatted by installing the rom, too.........hm..will correct op.
Edit: I made it that way always, and had never problems, so i haven't thought about it.
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Hello 9lukas5,
I thought I might mention that I've finally managed to fix my wlod but by installing setcpu on the earlier version of J's rom I was using, and setting it up to on boot run the processor at the usual 998 speed. Then I flashed the update.zip (from j's latest release, just formats the system) which didn't remove setcpu so the cpu was running at 998, this stopped all the random reboots and wlods.
I tried for a couple of weeks to use an update, trying so many different ways of stopping my phone being unusable as soon as I flashed the updates due to wlods.
Just though I'd mention it in this thread as it was on topic. Not everyones fix I'm sure, but helped me.
Cheers for all your support and help with installing the roms.
Sent from my X10 using XDA App
BULL3TPR00F said:
no its COMPLETELY fine to format system AS LONG AS, you flash the rom RIGHT AFTER (DO NOT REBOOT THE PHONE BEFORE FLASHING ROM AS RECOVERY WILL HAVE BEEN ERASED).
When you format system, and install the rom, the rom has recovery built into it as well and it installs the recovery to your system partition when you flash the rom.
So as long as you dont reboot after format system and install the rom first, your fine.
Click to expand...
Click to collapse
K - Right on, ty. Just so it's out there and people know ;-)
I believe the majority of WLODs are to due with the CPU constantly running at full speed.
I was getting a lot of WLODs with FreeXperia Kernel-10 on my ROM until I manually set the CPU governor to on demand.
Just go into Cyanogen Settings and change the CPU governor to on demand (it probably already is set to on demand, so change it to something else and then change it back to on demand).
After that my CPU was running at more than the max frequency and I haven't had many WLOD's (think I've had one since, a major improvement).
Erm not to be funny but their are no WLOD due to the changes J has made in his new version, regardless of how I flash it, no WLOD anymore... It has nothing to do with the way you flash the rom that caused this...
Hi guys,
I have follow ALL step from the step 1.
The phone boot, ask for the PIN code, then the page to change the language and then WLOD...
Do you think it come from the CPU frequency ?
I can't found the BTS kernel for this ROM.
Thank you for your help.
hmm....I shared it cause I hadn't any problems of WLODs yet on Cm7 since J019
Hello all,
the main trouble I had causing wlod, was definitely the clock speed. When I flashed the rom (about twenty times, different ways) I would not get enough time to configure any cpu settings, or any other settings, before my phone crashed and it would just start to bootloop with wlod.
I had to install setcpu on an older version of j's rom which didn't have overclock. Checked the box to apply settings on boot. So that when I flashed j's latest rom which is just the update of the system, all my apps were there (didn't bother wiping cache, data, etc) setcpu was still running on boot to keep the cpu set to 998.
Haven't had a single problem since, apart from low battery phone crash.
I tried so many different ways to flash before trying this, hope this helps someone.
Sent from my X10 using XDA App
Any body make a stock kernel image to flash to check sleep state vrs miniloader issue?????????
Worked a treat!! Thank you!
Model Number: x10i
Firmware Version: Eclair BitSnacker.com v2.5
Baseband Version: 2.1.54
Kernel Version: 2.6.29
[email protected] #1
Build Number: 2.1.A.0.435
I'm currently using this this ROM and would like to switch to this ROM. using xRecovery 0.3, but I do not know the first step. Do I have to go back to the generic x10 ROM or can I just factory reset in xRecovery and use another ROM?
Also, how do I update to the recently released xRecovery 1.0? is there an easy "Push bewton to update" thing?
Please tell me if I need to give any more information. Thank you.
no you don't have to go to generic X10 rom, just follow the steps in the rom's own thread:
Fresh Install: (aka coming from another rom or going from A to B or C)
Prerequisite - If you would like to retain your current apps, I suggest backing them up and restoring them using this method
1. In xrecovery, perform a full back up
2. In xrecovery, factory wipe, wipe cache, wipe dalvik cache, wipe battery stats
3. In xrecovery, install custom zip and choose wpx10.zip
4. When finished, reboot
5. DO NOT RESTORE DATA IN XRECOVERY!!
enjoy
it's a fresh install so backup your contacts, sms & apps before flashing
about updating your xrecovery to version 1.0.0 I suggest you wait a bit because it's in its early stages & still not working on all custom roms, you must wait for the cookers to release compatible versions
riginal said:
no you don't have to go to generic X10 rom, just follow the steps in the rom's own thread:
Fresh Install: (aka coming from another rom or going from A to B or C)
Prerequisite - If you would like to retain your current apps, I suggest backing them up and restoring them using this method
1. In xrecovery, perform a full back up
2. In xrecovery, factory wipe, wipe cache, wipe dalvik cache, wipe battery stats
3. In xrecovery, install custom zip and choose wpx10.zip
4. When finished, reboot
5. DO NOT RESTORE DATA IN XRECOVERY!!
enjoy
it's a fresh install so backup your contacts, sms & apps before flashing
about updating your xrecovery to version 1.0.0 I suggest you wait a bit because it's in its early stages & still not working on all custom roms, you must wait for the cookers to release compatible versions
Click to expand...
Click to collapse
And if I were to return to the current ROM i'm using, do I have to install xRecovery again? The thread didn't say it comes with xRecovery, so I'm a bit worried.
Stanley Richards said:
And if I were to return to the current ROM i'm using, do I have to install xRecovery again? The thread didn't say it comes with xRecovery, so I'm a bit worried.
Click to expand...
Click to collapse
All of custom roms come with xrecovery so I think this one shouldn't be an exception, but just to double check in your pc go to the zip file of the rom & take a look at system/bin do you see xrecovery.tar & xrecovery.apk or something like that?
Hey, don't know what happened but since few days my dialer is very slow. It takes approx. 15 seconds to start calling since I press call button in the contact. I cannot reinstall system, because it is time-consuming, I am waiting for ICS but in meantime I need to fix this issue
In other dialers it is alike - example exDialer.
I've got Gingerbread 2.3.6, stock.
Cheers.
menu / settings / applications / manage app / all / Dialer -> clear data
You say you're stock, but rooted? If rooted, try installing another dialer or modded one. Also, if you have CWM Recovery, clear cahe and dalvik.
Edit: You could also re-flash the stock ROM without wipe
Actually, reinstalling has newer been faster.
First, disable USB debugging and connect to pc/kies and make backup of msg, logs, notes...
Second, install titanium backup and back yours data+apps, it is one click process...
After that you are safe to factory reset your phone/install new rom..
Then you restore backup from kies (phone will reboot), install titanium backup and make one click restore for all applications+data...
Done!
Sent from my GT-I9100 using XDA App
I cleared but didn't help.
Yes I am rooted, installed next dialer and it is same - long waiting, I noticed during waiting lag CPU is working at 1200 Mhz - dunno why...
I have CWM Recovery but frankly I touched this only when I was rooting and installing 2.3.6 over 2.3.3. I do not know what dalvik is
Reflashing stock you mean system on system? It would be third system-on-system - I guess it would be too much
Burgscheinkerkdeiktraast said:
I cleared but didn't help.
Yes I am rooted, installed next dialer and it is same - long waiting, I noticed during waiting lag CPU is working at 1200 Mhz - dunno why...
I have CWM Recovery but frankly I touched this only when I was rooting and installing 2.3.6 over 2.3.3. I do not know what dalvik is
Reflashing stock you mean system on system? It would be third system-on-system - I guess it would be too much
Click to expand...
Click to collapse
Backup your data and factory reset.
Just re-flash your ROM. If stock use ROM download and instructions here:
[ROM+Guide]Official i9100 Firmwares KG, KH, KI, KJ, KK1/2/5, KL1/2/3, LA2 Download
If your running custom ROM, boot into CWM recovery and factory reset, wipe cache, go to advanced and wipe dalvik, and immediately flash custom rom.zip file from sdcard.
I upgraded 2.3.6 XXILA from 14.01.2012. Problem is gone
Thanks for help!
BTW, Google should check this issue out, it shouldn't have happened.
Edit ----deleted
Hi,
I'm new to the forum, apologize if I made any mistake by posting this here and notify me.
Issue: I have installed sony style V1.1 after 1 day it gets reboots, I tried wiping cache, reinstalling using CWM . Initially I have installed using Xrecovery and i had mutiple issues, like stuck up at boot animation logo, but after rebooting it worked fine. Experts out there please help me out.
-------------------------------
X10 mini pro
Kernel version: 2.6.29 [email protected]#1
MOD ver: MiniCM7 Pro-SE-StyleV1.1
REcovery Verision: CWM v3.2.0.0-r5 x10mini
Build number: 4.0.1.A.0.283
minipro.port said:
Hi,
I'm new to the forum, apologize if I made any mistake by posting this here and notify me.
Issue: I have installed sony style V1.1 after 1 day it gets reboots, I tried wiping cache, reinstalling using CWM . Initially I have installed using Xrecovery and i had mutiple issues, like stuck up at boot animation logo, but after rebooting it worked fine. Experts out there please help me out.
-------------------------------
X10 mini pro
Kernel version: 2.6.29 [email protected]#1
MOD ver: MiniCM7 Pro-SE-StyleV1.1
REcovery Verision: CWM v3.2.0.0-r5 x10mini
Build number: 4.0.1.A.0.283
Click to expand...
Click to collapse
Hi, did you try factory reboot? It usually helps. My usual workflow looks like this:
1. backup via Titanium backup or similar tool
2. backup in recovery
3. reboot into recovery
4. factory reset, wipe cache, wipe everything
5. flash firmware again
6. reboot
7. wait for first boot
8. reboot again
Thanks for the reply. I have tried all the above - including factory reset,wipe everything.
After first boot I do not get GSM working, but after first reboot it works fine.
After 1 day phone automatically switch off, then I have to switch on, but repeats again after sometime.
Now I have come back to Original ROM. It would be great help if you can tell me the exact procedure for rooting and installing CWM for mini pro. I'm looking for Gingerbread with "4 corner menu" sony style, can you recommend better ROM- on official kernel coz I'm new to this.
---------------------------------
Thanks kopancek, Looks like issue is resolved now- no reboot till 20 hours now.
steps:
1) flashed stock using SEUS
2) Rooted installed CWM
3) boot into CWM
4) backup using CWM
5) factory reset ..all wipe
6) install Sonystyle v1.1 from update.zip
7)factory reset ..full wipe
8) first boot ..no GSM
9) reboot again