Related
IMPORTANT NOTE: Because people do not have respect for the work of other people or to the point of thanking all the links to the alternatives are "down" until further notice. Over 200 downloads and not a thank you?!
Thanks.
After receiving several PM `s trying to get my help in the installation of Froyo ROM` s i decided to create this little "How to" for the avoidance of doubt.
This is a guide based on the Windows XP System.
This guide is ONLY for Xperia X10.
This guide was based on information gathered and based on my own experience and presents, in my opinion, the best way to get what you want. Whenever possible I will present alternatives.
This guide has a starting point of the original ROM SE (no root) if you already have root access please go to step 2.
---------------------------------------
---------------------------------------
What you`ll need before proceeding:
- Download SDK from google (need help for this? go HERE)
- Make sure you`ve just one partition on your sdcard and on FAT32. More info HERE
- Before each and every step make sure you have USB Debugging checked (settings>applications>Development)
---------------------------------------
---------------------------------------
I WILL NOT BE RESPONSIBLE IF ANYTHING GOES WRONG
1. Getting Root Access
1st mode
- Download file rootme.tar.bz2 HERE and follow the instructions or use as an alternative SuperOneClickv1.5.5-ShortFuse;
- Reboot.
2nd mode
You can alternatively use THIS pre-rooted and with xRecovery allready instaled rom. Saying this, if you choose to install this rom can proceed to step 3
Use THIS tool if you have any trouble with Bin4ry one.
Bin4ry realease a new tool you can try it HERE.
2. Installing xRecovery
1st mode
- Download xRecovery HERE and do the installation by following the instructions.
2nd mode
For the case of having problems installing the xRecovery do the following:
- Download THIS version of xRecovery;
- unzip it and copy the content (3 files) to the root of your sdcard;
- Open cmd prompt (start>run and type cmd) - From now on i will call this adb shell. I also recomend that you create a shortcut to this on your desktop, since you will use this many times;
- Now go to tools folder where you install your SDK. In my case (C:\Program Files\Android\android-sdk-windows\tools>);
Now type:
HTML:
adb shell
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
dd if=/sdcard/busybox of=/system/bin/busybox
dd if=/sdcard/chargemon of=/system/bin/chargemon
dd if=/sdcard/xrecovery.tar of=/system/bin/xrecovery.tar
reboot
Check your screen and give permition
- Reboot
- Press several times after "sonyericsson" appear on back button to confirm if xRecovery it`s installed. If it`s corrected installed you wil see your screen as the images bellow.
Although this guide is described for the installation of zhizu rom`s the process is exactly identical to the TripNRaVeRs and jerpelea rom`s
3. Installing Rom`s
This guide is for every rom that supports xRecovery process. I will not answer questions from other method.
- Choose the rom you want.
ZHIZU / TripNRaVers v2.1 / TripNRaVers vMIUI / jerpelea
3.1.
zhizu rom:
- Download-FreeX10 beta1.zip;
- Download gapps_latest_FreeX10.zip;
- Download FreeX10-beta1-hotfix4a.zip (at this point this is the last version, if a newer version exist please download that one. The process is identical);
- Create a folder at the root of the sdcard named ROMS;
- Create a folder inside ROMS called zhizu, TripNRaVers or jerpelea (dependind witch rom you`ll use);
- Copy the downloaded files to that folder;
- Reboot;
- Enter on xRecovery and:
3.1.1.
- Install custom zip;
- Choose custom zip from sdcard;
- ROMS (folder you created earlier);
- zhizu;
- Run the FreeX10-beta1.zip;
- Run the FreeX10-beta1-hotfix4a.zip;
- Reboot;
---------------------------------------
---------------------------------------
NOTES:
After that, probably you won`t have network and screen is crazy... do this:
Open adb shel again and type:
HTML:
adb shell
killall servicemanager
Your phone will reboot.
HAVE REAL ISSUES REGARDING "killall: not found"? type this instead (thks to NeoInc):
HTML:
adb shell
busybox killall servicemanager
If you`ve installed the TripNRaVers rom and if you have issues with wireless run this command on adb shell (thks to rodak ):
HTML:
adb shell
setprop net.dns1 192.168.1.1
If you having problems with su permission type (thks to AzureNightwalker ):
HTML:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
chmod 4755 /system/bin/su
---------------------------------------
---------------------------------------
(back on topic)
- After reboot enter on xRecovery again and go where you put your files again but this time you will run the gapps_latest_FreeX10.zip
- DONNE
If after instaling gapps_latest_FreeX10.zip you still don`t have google apps, please install THIS and then gapps_latest_FreeX10.zip
4.
If you want to install new market, please do this:
- Enter AT LEAST once in the old one;
- Copy THIS to the folder you`ve created earlier and run it from xRecovery.
---------------------------------------
---------------------------------------
CREDITS:
None of this would have been possible without the incredible work of our devs.
All the credit should be directed to them. Not for me. Just tried with this guide to help young (or not) to get phones rooted, install xRecovery and for installation of these incredible ROM `s.
Thanks to (in alphabetical order): (sorry if i forgot someone)
Bin4ry;
CLShortFuse;
jerpelea;
MarylandCookie;
rodak
th4r;
TripNRaVeRs;
XperiaX10iUser;
ZHIZU;
and all XDA users
|tips & tweaks|
some commands that you may require at some point
Copy to/from sdcard
HTML:
adb push /mnt/sdcard/<filename> - to copy the file to SD
adb pull /mnt/sdcard/<filename> - to copy the file from SD
Fix Facebook Sync (at the present TripNRaVeRs Rom may need it)
Please make back up first
Install to your Android using push command
HTML:
adb push ContactsProvider.apk /system/app/ContactsProvider.apk
adb reboot
Download ContactsProvider from HERE (thks XperiaX10iUser )
This will fix the Facebook sync, you might need to remove and add the Facebook account again.
If you loose root access for some reason, please open ADB shell and issue this command:
HTML:
chmod 4755 /system/bin/su
--------------------------------------------
--------------------------------------------
some tips & tweaks to play with
Let`s play with build.prop shall we?
CAUTION WITH THIS!!! ALL CHANGES MUST BE DONNE AT THE END OF THE DOCUMENT!!!
What will you get with this...
Well. In my opinion and only that, i think this way i can preform a much stable version of 2.2 Froyo released by zhizu.
After all apps installed (more or less 35) i get a very stable and fast rom (more or less 1500 on quadrant) and rarely had a FC.
So...like i said...that`s my 2cents.
1st mode - root explorer
You can make changes directly through RE by going on \system and then:
- Press and hold on build.prop file;
- Check all Permitions on the drop down menu;
- Press and hold on build.prop file (again);
- Choose open in text editor;
- After changes were made save and exit;
- Reboot.
2nd mode - Through Text Editor
To edit this one you must do this on a UNIX system base. You can use THIS to do that.
- Copy your build.prop to your sdcard and then to your pc;
- Open build.prop through NOTEPAD++;
- Now check all permitions for build.prop in \system folder
- After you made the changes proceed in reverse way and check all permitions again;
- Reboot.
This is your build.prop of your phone. Here we can do some tweaks in it.
Look carefully some already exist somo you have to add.
ro.sf.lcd_density=XXX (here you can put any value between 180/240) - This will affect the way you see your screen;
wifi.supplicant_scan_interval=XXX - This is how often your phone search for wi-fi spots and obviously will afect your battery life. Choose whatever you want in seconds. For instance, i have 360. Witch means my phone will search for wi-fi every 360 seconds.
dalvik.vm.heapsize=XXX (here you can put any value between 12/40) - This is how Android lead with apps. Lower value faster phone but big apps will crash. Higher value slower phone on small apps but faster on big ones). I have this to 40.
windowsmgr.max_events_per_sec=XXX (here you can put any value between 30/300) - This affect screen responseness of screen. You may try this if you have any problems with lag. I have this to 200.
mot.proximity.delay=XXX (here you can put any value between 0/300) - This will affect the time your screen goes off when receive a call. I have this to 150.
--------------------------------------------
--------------------------------------------
| Rom`s | Themes |
THIS ONLY WORK AFTER RIGHT INSTALATION OF THE ABOVE ROM´s
What is the joke of having rooted phone if we do not install anything to envy to our friends. Right?!
SEMPITERNAL THEME
XperiaX10iUser
wesvista
Whats wrong with my guide?
http://forum.xda-developers.com/showthread.php?t=908791
rodak said:
Whats wrong with my guide?
http://forum.xda-developers.com/showthread.php?t=908791
Click to expand...
Click to collapse
nothings wrong with it. if you read it goes further. root/xrecovery/rom`s and since so many people has sent me pm`s to explain them...
don`t get offensive
rendeiro2005 said:
nothings wrong with it. if you read it goes further. root/xrecovery/rom`s and since so many people has sent me pm`s to explain them...
don`t get offensive
Click to expand...
Click to collapse
From my guide:
"Feel free to help me improve this guide, just post here and I will update this post with all good tips!"
But hey, let´s have a lot of guides spread all around this forum just to get some credit
Hmm. Sorry. Got a question here.
Step 1 and 1a, is it the same? Or i need to do step 1 and then do step 1a?
And partition on my sdcard is already on Fat32, do I need to reformat it again to Fat32?
wanmeow said:
Hmm. Sorry. Got a question here.
Step 1 and 1a, is it the same? Or i need to do step 1 and then do step 1a?
And partition on my sdcard is already on Fat32, do I need to reformat it again to Fat32?
Click to expand...
Click to collapse
Hi,
1st. Like i said "alternatively". 1 is one way and 1a is another way. The diference between the two is the fisrt one you have to root after install and the second one came pre-rooted.
2nd. Since you`ve sdcard on FAT32 don`t have to do it again. Just be sure there`s ONLY ONE partition.
Hope it helps
Oh. sorry. I miss the "alternatively".
Which one is the best? 1 or 1a?
wanmeow said:
Oh. sorry. I miss the "alternatively".
Which one is the best? 1 or 1a?
Click to expand...
Click to collapse
depends on what you want. root or not rooted.
for the installation of above Rom `s you need to have root access.
Oh, ok. Thank you. I go download the files and try it first.
wanmeow said:
Oh, ok. Thank you. I go download the files and try it first.
Click to expand...
Click to collapse
you`re wellcome
tell me how it goes
nice guide.
tnx
Tehouster said:
nice guide.
tnx
Click to expand...
Click to collapse
wellcome
no need to thk me just click thks
Im stuck at SE white logo. If im not pressing back button, it will boot normally. Im thinking like giving up. >.<
wanmeow said:
Im stuck at SE white logo. If im not pressing back button, it will boot normally. Im thinking like giving up. >.<
Click to expand...
Click to collapse
Wicth process you follow?
From stock ir zhizu rom?
If you start from stock witch process you usr to install xrecovery?
As you know i've two possibilities on eatch one if you dont tell all things youve donne i cant help you
sent from my ****up X10 running amazing zhizu rom
Hey guys,
The good news i wanna notice for everybody here is my X10 Mini Pro with lastest firmware 2.1.1.A.0.6 can Root + xRecovery + JIT and use Link2SD okay without any errors !
I will tutorial you to do that. Now lets begin !
Root : Automate Installation
1. Download attached file "SuperOneClick".
2. Enable "USB Debug".
3. Connect phone to "PC" and select "Charge Phone".
4. Open "SuperOneClick" and select "Root".
5. Wait!
6. When it is done, reboot.
xRecovery : Manual Installation
- Phone must be rooted
- Download and install Titanium Backup. Run it and press Problems to install busybox or you can install standalone busybox in market !
- Download attached file and unpack the recovery package in to sdcard
- Use Root Explorer to remount /system rw
- Copy the content of the package (3 files) into /system/bin folder
- Chmod 777 for 3 files copied !
How to use xRecovery :
- Reboot your phone !
- Press BACK button few times right after white SE logo appears.
- Use VOLUME-UP and VOLUME-DOWN to browse, HOME to select, BACK to go back.
JIT : Here is manual installation. Automatic Installer here : http://forum.xda-developers.com/showthread.php?t=951274
I'm strongly recommend to backup with xRecovery before install JIT !
- Download attached file !
- Go to market place and find app "Terminal Emulator" download and install it.
- Extract and copy to sdcard
- Use root explorer to remount /system rw
- Copy dalvikvm,dexopt,logcat in sdcard to /system/bin/
- CHMOD 755 for 3 files copied!
- Copy libdvm.so,libnativehelper.so,libcutils.so,libdl.so,liblog.so,libm.so,libz.so in sdcard to /system/lib/
- CHMOD 644 for 7 files copied!
- Copy build.prop in sdcard to /system/ (You can use your build.prob file. Please see Warning section below)
- Chmod 666 for build.prop !
- Go to /data/dalvik-cache/ and remove all file in it or use command rm -r /data/dalvik-cache/* or we can use xRecovery and choose Advanced Options > Wipe dalvik cached
- Reboot your phone and enjoy !
- To check it work or not run Terminal Emulator and type dalvikvm -k if you see "Configured with: debugger profiler jit show_exception=1. It's mean JIT has been working !
Warning : if your phone cannot reboot again please use xRecovery to restore backup file (if not backup yet you can use SEUS to reflash your device) and JIT again with your build.prop file.
Follow these instructions:
- At the step copy build.prob above please use your build.prob instead my file provided and edit your file :
- Edit /system/build.prob with Root Explorer
+Find :
DEVICE_PROVISIONED=1
Click to expand...
Click to collapse
and replace with
#DEVICE_PROVISIONED=1
Click to expand...
Click to collapse
+Find :
dalvik.vm.heapsize=24m
Click to expand...
Click to collapse
and replace with
dalvik.vm.heapsize=30m
Click to expand...
Click to collapse
+Find :
kernel.log=default
Click to expand...
Click to collapse
and replace with
#kernel.log=default
Click to expand...
Click to collapse
+Find
debug.sf.hw=1
Click to expand...
Click to collapse
if don't have add one
+Add
dalvik.vm.execution-mode=int:jit
Click to expand...
Click to collapse
at the end of file !
- Save file and do continue others step to complete JIT.
Thanks to zdzihu for xRecovery, shivenjuneja for SuperOneClick modified version and all member in XDA for JIT installation method !
Now important action ^_^. Please thanks me if you want cheer !!
Can anyone confirm that the jit part is working?
i just instaled every thing x recovery works but when i installed jit the phone frezes at se logo and will not boot. Waited 15 mins and nothing good thing i did a back up
Sweet,another repair added to my records :/
Miniwolfi said:
i just instaled every thing x recovery works but when i installed jit the phone frezes at se logo and will not boot. Waited 15 mins and nothing good thing i did a back up
Click to expand...
Click to collapse
Do you wipe all dalvik caches ?? and the first boot after install it's take about 5 minutes to rebuild all cache files. After that it's working perfectly. Try to reboot few times and plug off your battery first !
no need to use the modified superoneclick.
the original version 1.6.5 just fine in this firmware
http://forum.xda-developers.com/showthread.php?t=803682
juan77_sonic said:
no need to use the modified superoneclick.
the original version 1.6.5 just fine in this firmware
http://forum.xda-developers.com/showthread.php?t=803682
Click to expand...
Click to collapse
Dude i used this version 1.6.5 but it cannot root for newest firmware for me ! It's notice me that device rooted but it's not you can check device root or not with Root checker in the market , it's also check busybox install !
i tried the method exactly like u write
stuck at SE white logo and it's rebooting again n again (10 minutes)
ntonzrockz said:
i tried the method exactly like u write
stuck at SE white logo and it's rebooting again n again (10 minutes)
Click to expand...
Click to collapse
I have been wrote new warning section for who have problems same you. Please read and do again to fix it. I hope you can because i can
quangnhut123 said:
I have been wrote new warning section for who have problems same you. Please read and do again to fix it. I hope you can because i can
Click to expand...
Click to collapse
okay i'll try it, maybe tomorrow...
it's late night now
thanks anyway
I was updated my TUT for more details !
For those needing JIT in the version 2.1.1.A.0.6.
donetus has updated deano309 xrecovery based installer. All you need to do is copy the files to the SD card and update using xrecovery.
http://forum.xda-developers.com/showthread.php?p=11289748#post11289748
Works well.
safrajs said:
For those needing JIT in the version 2.1.1.A.0.6.
donetus has updated deano309 xrecovery based installer. All you need to do is copy the files to the SD card and update using xrecovery.
http://forum.xda-developers.com/showthread.php?p=11289748#post11289748
Works well.
Click to expand...
Click to collapse
Thanks this i nice TUT but not automate system to install i will write script to do that but now i'm not because i'm have not free time dude
warkxia said:
xRecovery compatible with :
X10 MINI / 2.1.1.A.0.6
Click to expand...
Click to collapse
Please test more as Root and JIT. Thanks for reading my topic !
warkxia said:
xRecovery install but not boot ><
Click to expand...
Click to collapse
Why not boot dude ? Try my AIO installer script : http://forum.xda-developers.com/showthread.php?t=951274 to install xrecovery because xrecovery working 100% on lastest firmware ! i tested so many times
Re: OP
quangnhut123 said:
+Find
Code:
[COLOR="red"]debug.sf.hw=1[/COLOR]
if don't have add one
+Add
Code:
dalvik.vm.execution-mode=int:jit
at the end of file !
- Save file and do continue others step to complete JIT.
Click to expand...
Click to collapse
Hey bro, nice TUT for jit...just wondering, the part in red, what do i replace that with? Or do i just comment it out? Sorry prob a stupid question, im just really sick of having to reflash so just making sure its all good before i flash to my phone.
Cheers,
Jeremy.
jeremyward420 said:
Hey bro, nice TUT for jit...just wondering, the part in red, what do i replace that with? Or do i just comment it out? Sorry prob a stupid question, im just really sick of having to reflash so just making sure its all good before i flash to my phone.
Cheers,
Jeremy.
Click to expand...
Click to collapse
you just need find it if it's exist do nothing . And if not exist please add it after kernel.log=default
PS : As i recommend please backup your phone with xRecovery !
quangnhut123 said:
you just need find it if it's exist do nothing . And if not exist please add it after kernel.log=default
PS : As i recommend please backup your phone with xRecovery !
Click to expand...
Click to collapse
Cheers bro, i thought so but i just wanted to make sure.
And i dont need to back up coz im making my own custom rom and im just enabling jit within it.
Cheers,
Jeremy.
for people who want xrecovery and wants to charge offline (phone off) as well, you just have to follow this post:
http://forum.xda-developers.com/showpost.php?p=11549855&postcount=5
help with xrecovery
hello guys,
just bought myself x10 mini pro and loving it so far. I have successfully rooted and have busy box and su permissions.
next, I followed the following steps for xrecovery but it does not seem to work for me.
Code:
xRecovery : Manual Installation
- Phone must be rooted
- Download and install Titanium Backup. Run it and press Problems to install busybox or you can install standalone busybox in market !
- Download attached file and unpack the recovery package in to sdcard
- Use Root Explorer to remount /system rw
- Copy the content of the package (3 files) into /system/bin folder
- Chmod 777 for 3 files copied !
How to use xRecovery :
- Reboot your phone !
- Press BACK button few times right after white SE logo appears.
- Use VOLUME-UP and VOLUME-DOWN to browse, HOME to select, BACK to go back.
I have copied the 3 files using root explorer and mounting it rw and the permission set to 777. I have also checked the files/permission using adb shell.
I have then turn the phone off, turn it back on and press back < button on the sony ericsson logo but no matter how many times i press or hold the back button it does not take me into recovery menu.
Edit:
my bad, i did not copy over busybox and chargemon because the files were already there from rooting process.
anyone who has this trouble, make sure you copy all the three files to system/bin folder and set the permissions and it should be good.
Why my X10 Mini Pro won't stay off while charging??
It's rooted & JIT enabled, with 2.1.1.A.0.6 firmware............
Yesterday was fine, but this afternoon I rooted my phone and installed xrecovery then JIT.
Everything was okay [looks okay], but the time I charging my phone [2 hours ago] it won't stay off.
Everytime I turn it off, it always turn back on.....Please someone help me!! It's so annoying.
Should I uninstall xrecovery, JIT and unroot it? Or should re-flash my firmware? [hope not]
PS: I always turn off my u20i while charging.
Problem is modified "chargemon" file, installed with xrecovery.
a few features from oem "chargemon" are missing on it.
There is a solution for (big) X10i, but it must be adapted for mini/mini pro.
genyt said:
Problem is modified "chargemon" file, installed with xrecovery.
a few features from oem "chargemon" are missing on it.
There is a solution for (big) X10i, but it must be adapted for mini/mini pro.
Click to expand...
Click to collapse
Can I just fix it by restore the original chargemon file??
Yes, but you will not be able to use xrecovery if you do that.
Sent from my E10a using XDA App
you can get both features: xrecovery, and charge batt staying off.
I think I've found a solution at BIG X10 thread, (look for xrecovery_charge_offline).
I'm neither a developer nor an expert user, and I don't know how to write in English, but I am going to try.
I'm using 2.1.1.A.0.6 firm in U20i and you'll need ROOT in your phone.
First of all, make a backup of chargemon files, both, "SE" one and "xrecovery" one.
then, look at SE chargemon file, its a illegible coded file.
rename it as "charger", (without quotes).
copy it at /system/bin
look at xrecovery chargemon file: you'll see many commands separated by TABS.
insert a command calling charger file as following
#!/system/bin/busybox sh
/system/bin/charger
cat /dev/input/event0 > /dev/keycheck&
sleep 3
kill -9 $!
if [ -s /dev/keycheck ]
then
# remount rootfs rw
mount -o remount,rw rootfs /
# Umount MTDs
umount -l /dev/block/mtdblock1
umount -l /dev/block/mtdblock2
umount -l /dev/block/mtdblock3
# Mount recovery partition
rm -r /sbin
rm -f etc
tar -xf /system/bin/xrecovery.tar
# Umount /system
umount -l /dev/block/mtdblock0
chroot / /init
fi
# Continue booting
exit
Click to expand...
Click to collapse
I've just added "/system/bin/charger" line.
Save file as "chargemon", and copy it to /system/bin
Finally, Test it!!
note: if you edit xrec chargemon file with windows notepad, you'll see commands separated by TABS, not in different lines, so be sure there is a TAB space before AND after "/system/bin/charger" text
Credits:
This fix is adapted (copied really) from xRecovery-charge-offline.zip by zdzihu,
using chargemon from xrec for U20 instead of big X10 one.
More info at:
http://forum.xda-developers.com/showthread.php?t=859571
Try at your own risk!!
Here, you have original and fixed files.
of course, charger file and se original chargemon are the same file.
Thank you genyt.
I've overwritten my original chargemon file.
Can you please provide us a zipd file with all 4 files needed?
And if this works can you please mention it in the xrecovery-Thread http://forum.xda-developers.com/showthread.php?t=878426 ?
Thanks a lot.
Sent from my E10i using XDA App
weissgold said:
Thank you genyt.
I've overwritten my original chargemon file.
Can you please provide us a zipd file with all 4 files needed?
And if this works can you please mention it in the xrecovery-Thread http://forum.xda-developers.com/showthread.php?t=878426 ?
Click to expand...
Click to collapse
done.
Please report if it works... with e10, different firmware versions..
TODO: create an update.zip file installable with xrecovery
in chargemon it should be
cat /dev/input/event1
we had this little bug before.
I changed this and it works fine.
Sorry I'm not familiar with making an update.zip
Maybe the next days I have some time to have a look at it
In the meanwhile here are the corrected files:
http://rapidshare.com/files/4493385...h_genyt_s_fix_for_charge_batt_staying_off.zip
I think this is not an error, but lets see:
if you take a look to BIG x10 files (link in previous post) you can see it has "event2".
but my original file has "event0".
My phone is a mini pro, will mini be "event1"?
What kind of error have you got?
I'm sorry my internet is so sloooooow today.
I have read somewhere here that ist should be 1 to trigger the keystroke.
And in original thread here http://forum.xda-developers.com/showthread.php?t=878426
in the download it is 1 too.
With 0 no reaction while booting.
With 1 everything all right. (Xperia X10 mini)
... have to go to bed now - good night everybody.
verified, x10 mini pro works with "event0".
In conclusion, this method works with x10 mini too, changing event0 to event1.
but using x10 mini version of xrecovery, it comes with event1 "as is".
wow! i followed the guide with changing the SE-chargemon to 'charger' and adding the line in xrec chargemon, and it actually solved my dilema with the xrecovery!
thanks a lot!
now i can charge my U20i offline anytime
Can anyone post the original SE chargemon file for X10 mini 2.1.1.A.0.6?
Thank you!
Sorry I've been busy all day long......
@genyt
TQ for your willingness to help me out.....really appreciate that
So all I have to do now is copy "xrecovery charge fix for u20.zip" file to system/bin??
no, you must extract files in zip file, then, copy 2 unpacked files to system/bin.
Only for U20: X10 mini PRO.
if you have a X10 MINI, you must use weissgold files.
genyt said:
no, you must extract files in zip file, then, copy 2 unpacked files to system/bin.
Only for U20: X10 mini PRO.
if you have a X10 MINI, you must use weissgold files.
Click to expand...
Click to collapse
LOL yeah I know that......! My phone is u20i.
Sorry for my bad english, it's confusing and misleading
Then, we have TWO bad englishes...mine and yours.. LOL
Sent from my U20i using XDA App
from zeroize
Charging off line works for the x10 mini, but when you press the on/off button while charging offlline, It loads the xrecovery menu directly. Is is normal, shouldn't it boot the original menu?
see here http://forum.xda-developers.com/showthread.php?p=11583047#post11583047
Should be the same with PRO.
Maybe it helps to move the call to charger to the end in chargemon.
I tried it, but I didn' got it working.
Here's the fix for
Charging off line works for the x10 mini, but when you press the on/off button while charging offlline, It loads the xrecovery menu directly. Is is normal, shouldn't it boot the original menu?
http://rapidshare.com/files/4496539...t_staying_off-and_weissgolds_fix_for_loading_
On my mini it's working, can you confirm?
Oh sorry --> filename too long --> it's .rar
hello everyone.
I'm quite more comfortable with my SG2, but I have to handle with an X10i, never updated. It has the first basis stock rom : X10i / 1.6 / 1.0.14 / 2.6.29-rel [email protected] #2 / R1FA014
I want to upgrade it to gingerbread 2.3.x. It's quite very easy as the official package is released. But... (there is always a but), the phone isn't anymore recognized by any computer, with any usb cables (even the official one, even on computers with xp or seven (on which the phone was previously seen)). and on the phone the USB logo will not anymore appears when connected to Pc. So I figured out that the connector for USB is broken. Just to say that the phone can be charged by this way...
So it's impossible to use SUES or FlashTools, etc... So I want to do it manually. As I've read, it's possible by doing this way :
a. rooting the phone
b. installing xrecovery on the phone
c. copying an update.zip with the ROM I want
d. flashing this update.zip with xrecovery
But it's impossible !
Let me explain you what I've done :
1. reset phone to factory default
2. x10root
3. root checker = ok
ok... so the phone is now rooted.
4. update busybox to version 1.15.3
5. impossible to update to upper version of busybox
6. impossible to install xrecovery 0.2 neither 0.3 (message saying it's impossible on this phone)
let's trying it manually...
7. extracting xrecovery 0.2, taking files in res folder (busybox, chargemon, xrecovery.tar) and copying it to system/bin
8. reboot >> impossible to get the xrecovery menu by tapping the back button
9. extracting xrecovery 0.3, taking files in res folder (busybox, chargemon, xrecovery.tar) and copying it to system/bin
10. reboot >> impossible to get the xrecovery menu by tapping the back button
11. extracting xRecovery-0.3_GBready.zip, taking files in res folder (charger, chargemon) and copying it to system/bin + xrecovery.tar and sh in system/xbin
12. reboot >> impossible to get the xrecovery menu by tapping the back button
so... now I'm lost !
Anyone can help me in this case ? Thanks in advance...
Some guys have problem using a JB or KitKat because though their Boot-loader is Unlocked, they can not Use the ROM after flashing. Because the Touchscreen will not respond after the new ROM Boots up. So, they are stuck with the ICS Stock that Sony gave. There is a Thread Touch does not work
I was one of these guys.
Well Guess what I got a solution.
So, I am going to write the procedure directly. But first, go and thank these two people...
1. erw1n for this post http://forum.xda-developers.com/showpost.php?p=46276864&postcount=81
2. bangladeshi for this thread. [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
I Got the Idea from them.
Special Note: I'm not responsible if you brick or damage your phone.
The procedure goes as follows. I'm giving the detailed Instructions later.
Download the desired ROM
Extract Touch Screen Firmware and related files from Stock Official Sony FTF or any other source
Open ROM with 7-Zip or any other Zip Software and replace the Firmware Files with Stock ones.
Modify the hw_config.sh file in the ROM if necessary.
Close the ZIP
Flash the ZIP with CWM
Now Goes the Details-
Step One: I Did it with only [ROM] [UB] [Kitkat] [4.4.2] CyanogenMod 11.0 NIGHTLIES. So it's not tested on any other ROM. Theoretically It should work on any ROM. So, Cheers Download your ROM.
Step Two: If you dont want to do all these, then just download the zip file in the attachment and unzip it. for the official Sony firmware files
Else,
You will need FlashTool and Stock Official Sony ICS FTF and Notepad++ or any similar code/text editor and 7-zip for this. You will also need ext2explore (If you know what you are doing then you can also download the CWM flashable one ROM.)
First Open the FTF in 7-zip. Extract the System.sin file and put it in a folder lets say, "ICS_Stock". Now open FlashTool. Go to Sin editor.Browse for the sin file and click on Extract Data. Now after it finish, you will see four extra files in the ICS_Stock folder. with different extensions. one will be ext4. (something like "system_S1-SW-LIVE-3065-PID1-0002-S1-PARTITION.ext4")
Close FlashTool, Open ext2explore (as administrator). Go to file, Open Image, and select the ext4 you just extracted.
browse through the files,
Go to system/etc/firmware, right click on ttsp_fw.hex, save it.
Go to system/bin, right click on cyttsp_fwloader, save it.
Go to system/usr, right click on the folder idc, save it.
Close the ext2explore
Step Three: Now open the downloaded ROM with 7-Zip. Now Pay very careful attention
Go to system/etc/firmware, and delete ttsp_fw.hex if exists.
Go to system/bin, and delete cyttsp_fwloader if exists.
Go to system/usr, and delete folder named idc if exists.
Go to system/etc, and extract file named hw_config.sh after extract and save it in the same folder as other files, delete the file from the zip.
Now again
Go to system/etc/firmware, and drag and drop the ttsp_fw.hex file you just saved. (There will be a warning "Are you sure, you want to copy files into archive.... bla.. bla.. bla..." just say Yes)
Go to system/bin, and drag and drop the cyttsp_fwloader file you just saved.
Go to system/usr, and drag and drop the idc file you just saved.
Now comes the vital Part,
Open the hw_config.sh file with Notepad++ you will find some lines like this one,
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex
# Audio jack configuration
if it is just like my example then, change the lines to
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex -force
# Audio jack configuration
(Just add a -force)
If its not like the example and you don't have a clue what to do, Ask in this thread, If I'm there, I'll reply what to change.
it could be something like below, (taken from the Chienise Guy ROM 6.2.A.1.100 Xiangxin X3
Code:
# Touch FW loader
dev=/sys/bus/spi/devices/spi9.0
fw=ttsp_fw.hex
app_id=`cat $dev/appid`
case `cat /data/ttsp_fw_update` in
"in_progress") flags=-force ;;
*) flags="" ;;
esac
case "$app_id" in
"0x3030") flags=-force ;;
*) echo $app_id > /data/ttsp_appid ;;
esac
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev $dev -fw /system/etc/firmware/$fw $flags
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
Here you may or may not change. but if you really want to change, change it to,
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex -force
# Audio jack configuration
Then save and close the hw_confif.sh file.
Now again go to your ROM opened with 7-zip, and Go to system/etc, and drag and drop the hw_confif.sh file you just saved.
Close the ROM Zip.
Step Four: your Fixed ROM is ready. Take all the Backups you need and don't need . Go to CWM, and also take all the NANDROID backup.
Now keep your fingers crossed and flash the Modified ROM as the instructions say in the Main Thread from where you downloaded the ROM.
If this solution works, Thank the ROM Builder first and then me.
Please Note: Do not distribute the Modified ROM without the permission of the Original Developer.
and Don't Blame Me or the Developer if the solution don't work for you. It worked for me.
If it worked for you, then Please tell us, for which ROM the solution worked. We can make a list of Compatible ROMs for this Modifications.
Up to now, this trick is confirmed to work on Two ROMS.
[ROM] [UB] [Kitkat] [4.4.2] CyanogenMod 11.0 NIGHTLIES
JB Thunder Strike
im really2 thank you.. for your tips..
yeah ,, now my xu rom JB Thunder Strike..!!
touchscreen problem solved..
erw1n said:
im really2 thank you.. for your tips..
yeah ,, now my xu rom JB Thunder Strike..!!
touchscreen problem solved..
Click to expand...
Click to collapse
The KitKat Nightly Is very stable and fast for me. Sometimes the Touch hangs again. I just remove the battery and re-insert it again. And Viola. it Works.
Glad that it worked. Now what I am going to work on is, how to make, Recovery Mode Touch work. I know it's tough, but possible.
CWM Flashable ZIP for recovery touch
I had noticed that, though the ROM Touchscreen works, but in recovery, the touch don't work. So, have made a CWM Flashable ZIP file, if you flash it, hopefully the touch will start to work inside the Recovery. Please note, This is not a permanent solution. You have to flash this file each time you go in recovery.
Once again, I tasted it with only CM11 Nightlies.
If it works, I will try to modify this file to act like a patch for all ROMs. So that, you can flash any ROM and after that you can flash this patch to make touch usable.
@[B]jatinrungta[/B] Can you test it for me?
I tried to extract from system.sin but I only got system.partinfo and system.yaffs2 files. I am trying to fix my mini pro (mango) touch screen and I used the stock ROM SK17i_4.1.B.0.431_(1249-7380).ftf to get the system.sin. Any thoughts?
edit:
Can you also provide an updated CM11 that has a fix on it for sk17i (mango)? I will really appreciate it.
evilfox7 said:
I tried to extract from system.sin but I only got system.partinfo and system.yaffs2 files. I am trying to fix my mini pro (mango) touch screen and I used the stock ROM SK17i_4.1.B.0.431_(1249-7380).ftf to get the system.sin. Any thoughts?
edit:
Can you also provide an updated CM11 that has a fix on it for sk17i (mango)? I will really appreciate it.
Click to expand...
Click to collapse
Sorry for the late answer.
But problem is, I don't have SK17i the set in my hand. So, I am not sure, the fix, I did, will work on your one.
Still, I'm going to download and make a cwm installable zip from the Sony stock ftf. I'm gonna download the FTF tomorrow, i have transfer cap and provide you a CWM file for CM11. Need to search the sk17i (mango) forums. But, you can try with a yaffs2 explorer, it'll work as ext2explorer.
pollob666 said:
Sorry for the late answer.
But problem is, I don't have SK17i the set in my hand. So, I am not sure, the fix, I did, will work on your one.
Still, I'm going to download and make a cwm installable zip from the Sony stock ftf. I'm gonna download the FTF tomorrow, i have transfer cap and provide you a CWM file for CM11. Need to search the sk17i (mango) forums. But, you can try with a yaffs2 explorer, it'll work as ext2explorer.
Click to expand...
Click to collapse
I will look forward for it. Anyway, I will try to use the yaffs2 and hopefully it has the same structure with your original post.
i have this trouble but is was like this when i flash GB back (i was on ICS stock rom)
But i try to revert and back to ICS and dont work
Can anyone help me please!
Xperia sola unresponsive touchscreen
Hi,
I tried the steps that you have suggested, But in the final part(hw_config.sh) with the code, i had something different. I dont know how to alter it. Can you help me out??
The code is below.
# Touch FW loader
dev=/sys/bus/spi/devices/spi9.0
app_id=`cat $dev/appid`
case `cat /data/ttsp_fw_update` in
"in_progress") flags=-force ;;
*) flags=-no-downgrade ;;
esac
case "$app_id" in
"0x3030")
flags=-force
;;
esac
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev $dev -fw /system/etc/firmware/ttsp_fw.hex $flags
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
bhatadarsh said:
Hi,
I tried the steps that you have suggested, But in the final part(hw_config.sh) with the code, i had something different. I dont know how to alter it. Can you help me out??
Click to expand...
Click to collapse
Yes, Just replace the lines with these below,
Code:
# Touch FW loader
#dev=/sys/bus/spi/devices/spi9.0
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /system/etc/firmware/ttsp_fw.hex -force
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
Go to system/usr, right click on the folder idc, save it.
Go to system/usr, right click on the folder idc, save it.
There is no IDC folder .....help me....