Thanks to J & Z for creating such a wonderful rom (Free X10 Froyo 2.2.1) and the wonderful utility xRecovery for us to play with. xRecovery is a must have if you want to play with different roms. The thing is that Free X10 & xRecovery can't coexist.
On close study, I found that the difference is only the chargemon. Both share the same busybox file. So I write these 2 little scripts to make the switching easier.
I would assume that you have already installed both Free X10 & xRecovery before. Your SD Card should have the folders: FreeX10 and xrecovery.
Preparation:
1. Copy chargemon for Free X10 to FreeX10 folder in the SD Card (it should already be there)
2. Copy chargemon for xRecovery to xrecovery folder in the SD Card
3. Copy freex10.sh and xrec.sh to root folder of the SD Card
To Switch to Free X10:
Start adb shell or use terminal emulator from your phone, then type:
su
sh freex10.sh
the phone will reboot and you can boot into Free X10 by pressing the back key when the Sony Ericsson logo appears
To Switch to xRecovery (boot into 2.1 rom first):
Start adb shell or use terminal emulator phone, then type:
su
sh xrec.sh
the phone will reboot and you can boot into xRecovery by pressing the back key when the Sony Ericsson logo appears
Notes:
1. I am not a coder, so I use cut & paste to write my scripts. There maybe easier way to do this
2. You may take out these 2 lines:
busybox cp -f /sdcard/FreeX10/e2fsck /system/bin/e2fsck
busybox cp -f /sdcard/FreeX10/ramdisk.tar /system/bin/ramdisk.tar
In freex10.sh if you already have the 2 files e2fsck & ramdisk.tar copied to /system/bin folder
Bricked g tab
I am locked into a loop hell with a fc of android.process.acore has stopped. I cannot get past this error or FC. any ides???
djohncline said:
I am locked into a loop hell with a fc of android.process.acore has stopped. I cannot get past this error or FC. any ides???
Click to expand...
Click to collapse
No idea. You may want to check out this thread for solution:
http://forum.xda-developers.com/showthread.php?t=851443
Related
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
Code:
adb shell
mkdir 21system
mount -o rw /dev/block/mtdblock2 /21system
If you're lucky it will mount your 2.1 system partition as /21system
Most likely it will say "Device or resource busy"... But worth trying anyway.
Cheers
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
thermoska said:
Hello all
I need help
Unfortunately I have managed to damage my 2.1 rom. (i have replaced 2.1 framework-res.apk)
Now I cannot boot into it , problem is that I do not have a backup, so I cannot just easily "reburn" the firmware.
I have 2.2 ROM implemented. but I do not -know how to reach 2.1 system files from it. There is some chroot done in boot process imho .
Can anybody help me how to reach the files
I have a backup of framework-res.apk
Click to expand...
Click to collapse
I did the same thing at least twice. I was able to save it without restoring by replacing my framework-res.apk before it rebooted or froze.
Basically, try to adb into it while it is still at the Sony logo or if you get the blackscreen after the logo.
One weird thing I did notice was that I was able to replace the framework-res.apk file apparently without using 'su'. After I killed it when I was doing adb at/after the logo I tried to 'su' but it gave some error and remained at the '$' prompt. I then did the 'dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk' command and it completed. Rebooted and it worked again.
Think my whole thing was tested second time with a script.
Try making a frameworkfix.cmd file and putting this in it.
@echo off
@echo.
@echo Installing Framework
@echo.
@adb shell su
@adb push framework-res.apk /sdcard/framework-res.apk
@adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
The keep trying to run it while at the Sony logo. Give it a few runs before you give up, I swear it worked for me.
thermoska said:
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
Heck just try the following from folder with your original framework.
adb push framework-res.apk /sdcard/framework-res.apk
adb shell dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
or
adb push framework-res.apk /sdcard/framework-res.apk
adb shell
su
dd if=/sdcard/framework-res.apk of=/system/framework/framework-res.apk
thanks guys , but I do not need commands,
I know them already , I had permissions problem.
Instructions mentioned above did not worked for me
I've got permission denied
anyway thanks
thermoska said:
Thanks
I had to think about remount
Going to try now ..
EDIT:
You are absolutelly right : Device or resource busy .
What should I try now ?
I found out that I can reach 2.1 system in adb , but my root do not work. so I cannot do anything to the system partition . Any ideas how to achieve root in this state ? On phone display there is still only firts sony ericsson logo ..
Click to expand...
Click to collapse
You can access the 2.1 /system partition through 2.2 with adb.
Use this to unmount 2.2 /system
Code:
su
busybox umount /dev/block/loop1
You can check if all worked well this way:
Code:
busybox ls -1d /system/* | grep xbin
If it gives you anything, it's 2.1 -- if not, try
Code:
busybox umount -l /dev/block/loop1
Now, you should have the old 2.1 /system structure available. Ignore all errors appearing *on the phone* it'll be screwed up, unusable. Until a restart.
Now through adb you can overwrite your 2.1 framework apk with dd
(assuming you already have it on the sdcard, else, well, push it there (adb push framework.apk /mnt/sdcard/ )
Code:
dd if=/mnt/sdcard/framework.apk of=/system/framework/framework.apk
for remount system, just do
Code:
busybox mount -o remount,rw /system
after you have the 2.1 system available.
I installed 2.2 to my nand (almost fully working) at one point this way =3
Or...
You can flash again just using system.bin and everything you had would be there.
;-)
You also will need loader.sin
I did this a couple of times and work for me; I only need to root again
Good luck!
PS: In the firmware folder, you need to leave ONLY this 2 files: System.sin and loader.sin. Backup and delete all other files like amss.sin, cache.sin, etc.
well thank you
This a good idea ..
Unfortunatelly I already reflashed the phone
Hope it will help to somebody in the future
ttxdragon said:
I installed 2.2 to my nand (almost fully working) at one point this way =3
Click to expand...
Click to collapse
Thought that would work, was going to do it with .003, but I guess the recovery tool will do that for us - now we see what Z has been working on - excellent news
Just curios. Any speed improvements when extracting the img files to nand and mount/run it from there ?
Even running from sdcard img files is a perfect backup solution by just copy the img files away from time to time. But of course r/w cycles of the card are increased --> less lifetime.
But otherwise running from images is nice, as you're able to mount them. (diskinternals linux reader but R-only)
Anyone knows a win32 prog to mount the img files r/w ?
Here is what I believe is a simple way of rooting and installing CWM for Windows.
I have bricked my phone many times now and used SEUS to get it back to 2.1.1.A.0.6 and had to go through the process of rooting and installing CWM again. Here is what I have found.
Download SuperOneClick to a folder, e.g. C:\SuperOneClick
Create a sub-folder under this folder, e.g. C:\SuperOneClick\CWM
Download your preferred version of CWM or xRecovery (should be the 3 files "busybox", "chargemon", "recovery.tar")
Copy these 3 files into the sub-folder you created, e.g. C:\SuperOneClick\CWM
Copy the code snippet below and save as INSTALL.BAT in the sub-folder
Reflash your phone with SEUS to get back to plain 2.1.1.A.0.6
Reboot and set USB debugging mode
Run SuperOneClick and click Root - do not reboot
Once Root has finished click Shell Root - do not reboot
Open a command window and enter CD C:\SuperOneClick\CWM
Run INSTALL.BAT - this will reboot the phone at the end
Press BACK key on the phone at the Sony Ericcson text - you should get into CWM
The benefit of the above is that if you keep the files in the folder above you can repeat from step 6 very easily.
Code:
@echo off
echo.
echo.1) Run SuperOneClick
echo. a) Click Root - do not reboot
echo. b) Click Shell Root - do not reboot
echo.2) Press any key in this window to install CWM - phone will reboot
echo.
pause
..\adb devices
..\adb remount
..\adb push busybox /system/bin
..\adb push chargemon /system/bin
..\adb push recovery.tar /system/bin
..\adb shell chmod 755 /system/bin/busybox
..\adb shell chmod 755 /system/bin/chargemon
..\adb shell chmod 755 /system/bin/recovery.tar
..\adb reboot
This technique does not require installing BusyBox from the Market, setting permissions via Root Explorer or anything like that. It just uses SuperOneClick and a small script using the ADB program in the SuperOneClick folder.
I got SuperOneClick from here http://forum.xda-developers.com/attachment.php?attachmentid=515017&d=1297434892 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I got 2 files for CWM "chargemon" and "recovery.tar" from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=627115&d=1308237137 (from thread http://forum.xda-developers.com/showthread.php?t=1106146)
I got busybox from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=515016&d=1297434832 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I hope some people find this useful and that I haven't offended the guys where I got the files from (I did list your threads as well as link to your files so others can see all the useful posts in your threads).
Darren
DarrenNewsgroup said:
Here is what I believe is a simple way of rooting and installing CWM for Windows.
I have bricked my phone many times now and used SEUS to get it back to 2.1.1.A.0.6 and had to go through the process of rooting and installing CWM again. Here is what I have found.
Download SuperOneClick to a folder, e.g. C:\SuperOneClick
Create a sub-folder under this folder, e.g. C:\SuperOneClick\CWM
Download your preferred version of CWM or xRecovery (should be the 3 files "busybox", "chargemon", "recovery.tar")
Copy these 3 files into the sub-folder you created, e.g. C:\SuperOneClick\CWM
Copy the code snippet below and save as INSTALL.BAT in the sub-folder
Reflash your phone with SEUS to get back to plain 2.1.1.A.0.6
Reboot and set USB debugging mode
Run SuperOneClick and click Root - do not reboot
Once Root has finished click Shell Root - do not reboot
Open a command window and enter CD C:\SuperOneClick\CWM
Run INSTALL.BAT - this will reboot the phone at the end
Press BACK key on the phone at the Sony Ericcson text - you should get into CWM
The benefit of the above is that if you keep the files in the folder above you can repeat from step 6 very easily.
Code:
@echo off
echo.
echo.1) Run SuperOneClick
echo. a) Click Root - do not reboot
echo. b) Click Shell Root - do not reboot
echo.2) Press any key in this window to install CWM - phone will reboot
echo.
pause
..\adb devices
..\adb remount
..\adb push busybox /system/bin
..\adb push chargemon /system/bin
..\adb push recovery.tar /system/bin
..\adb shell chmod 755 /system/bin/busybox
..\adb shell chmod 755 /system/bin/chargemon
..\adb shell chmod 755 /system/bin/recovery.tar
..\adb reboot
This technique does not require installing BusyBox from the Market, setting permissions via Root Explorer or anything like that. It just uses SuperOneClick and a small script using the ADB program in the SuperOneClick folder.
I got SuperOneClick from here http://forum.xda-developers.com/attachment.php?attachmentid=515017&d=1297434892 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I got 2 files for CWM "chargemon" and "recovery.tar" from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=627115&d=1308237137 (from thread http://forum.xda-developers.com/showthread.php?t=1106146)
I got busybox from the ZIP file here http://forum.xda-developers.com/attachment.php?attachmentid=515016&d=1297434832 (from thread http://forum.xda-developers.com/showthread.php?t=950324)
I hope some people find this useful and that I haven't offended the guys where I got the files from (I did list your threads as well as link to your files so others can see all the useful posts in your threads).
Darren
Click to expand...
Click to collapse
Very useful, thank you. I usually spend a couple of minutes re-installing CWMR via a root explorer and it annoys me. This saves 10-20 minutes per restore
It doesn't work..
I bricked my phone 3 timies..
easyyu said:
It doesn't work..
I bricked my phone 3 timies..
Click to expand...
Click to collapse
are you using the same busybox/chargemon and recovery tar that you usually manually install?
svyr said:
are you using the same busybox/chargemon and recovery tar that you usually manually install?
Click to expand...
Click to collapse
I'm used files from first post!
@easyyu
I am sorry that your phone got bricked. Unfortunately you will need to reflash your phone via SEUS. After that check your phone settings are the same as mine below. The 3 files work with my phone settings.
My X10 Mini Pro has the following Settings->About Phone
Model number U20i
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404015
Kernel version 2.6.29 [email protected] #1
Build number 2.1.1.A.0.6
@svyr
Can you confirm that the above settings are the same as in your phone. This would confirm that the 3 files work for my phone settings.
Darren
DarrenNewsgroup said:
@easyyu
I am sorry that your phone got bricked. Unfortunately you will need to reflash your phone via SEUS. After that check your phone settings are the same as mine below. The 3 files work with my phone settings.
My X10 Mini Pro has the following Settings->About Phone
Model number U20i
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404015
Kernel version 2.6.29 [email protected] #1
Build number 2.1.1.A.0.6
@svyr
Can you confirm that the above settings are the same as in your phone. This would confirm that the 3 files work for my phone settings.
Darren
Click to expand...
Click to collapse
yes, the above settings from about are the same on my phone.
Hmmm, just reflashed again, ran it and forgot to include busybox/rebooted.
Now it says it can't copy the files/files are read-only and system
Any ideas?
Aside from following the 'do not reboot' (edit: ran superoneclick again and it's all good (re-run the script))
Can't vouch for the busybox/etc set above, but the on I always used still works when installed this way instead of manually.
DarrenNewsgroup said:
@easyyu
I am sorry that your phone got bricked. Unfortunately you will need to reflash your phone via SEUS. After that check your phone settings are the same as mine below. The 3 files work with my phone settings.
My X10 Mini Pro has the following Settings->About Phone
Model number U20i
Firmware version 2.1-update1
Baseband version M76XX-TSNCJOLYM-53404015
Kernel version 2.6.29 [email protected] #1
Build number 2.1.1.A.0.6
@svyr
Can you confirm that the above settings are the same as in your phone. This would confirm that the 3 files work for my phone settings.
Darren
Click to expand...
Click to collapse
Yes this is the right parameters that you mentioned!
I know how to unbrick my phone..thats not problem!
svyr said:
yes, the above settings from about are the same on my phone.
Hmmm, just reflashed again, ran it and forgot to include busybox/rebooted.
Now it says it can't copy the files/files are read-only and system
Any ideas?
Aside from following the 'do not reboot' (edit: ran superoneclick again and it's all good (re-run the script))
Can't vouch for the busybox/etc set above, but the on I always used still works when installed this way instead of manually.
Click to expand...
Click to collapse
ps here's the one I use. Can't remember where the chargemon is from, but busybox is from xrec mini and CWM is 3.2.0 rc3
I made this, a lot of test give a lot of success, but it's only for mini pro.
CWM recovery by this script easily: http://www.multiupload.com/NDZB8HSIOV
Heres more easy way to install cwm or xrecovery or jit or apps2sd
this is basically quangnhut123's AAIS script, I modified it to add cwm support,
heres the link to download http://www.4shared.com/file/KQf9bym2/AAIS.html
heres the steps to follow
1) Download n extract the aais.zip to /sdcard
2)Open terminal emulator(available on market)
3) enter following commands
su
cd /sdcard/aais
Sh install.sh
Click to expand...
Click to collapse
4) choose ur option and enter the no.
plz note it requires pre rooted device! Only for mini pro! 2.1.1.A.0.6!
Why not try D4rK's recovery installer? It is a one-click installer which lets you choose from xrecovery or CWM...Google search D4 recovery installer
For recovery I made this: http://www.multiupload.com/QE60V6RORD
It works like a charm, thanks to the script xrecovery of mikevhl
Maybe someone could make a script like that for mini ?
D4rK's recovery installer ? I can't find it, even with the google's help...
JBSroid said:
Why not try D4rK's recovery installer? It is a one-click installer which lets you choose from xrecovery or CWM...Google search D4 recovery installer
Click to expand...
Click to collapse
when i tried it, it didn't work on sdk 7 or was it 8...
What do you mean by sdk 7 or sdk 8? Someone mentioned sdk numbers before. Is this something to do with downloading the complete android stuff onto my windows pc just to get the adb command? This is why I thought using the adb in SuperOneClick was so useful.
Darren
DarrenNewsgroup said:
What do you mean by sdk 7 or sdk 8? Someone mentioned sdk numbers before. Is this something to do with downloading the complete android stuff onto my windows pc just to get the adb command? This is why I thought using the adb in SuperOneClick was so useful.
Darren
Click to expand...
Click to collapse
no, I thought it was about downloading the SDK, but it's actually about the runtimes on the phone... I think (the only way to change them is pretty much by getting a rom with newer ones )
How to use ADB shell. Please back up your sd card before trying this
For all those not sure on how to install ADB shell and then the gingerbread ready xrecovery 0.3, Here is a simple tutorial on how to do it.
First download the xrecovery gingerbread ready zip from http://forum.xda-developers.com/showthread.php?t=859571 Then
1. Download http://forum.xda-developers.com/showpost.php?p=13430042&postcount=25 and put all the files into a folder in C drive, preferentially name the folder adb and extract the zip file into it.
(thanks doomlord for the link)
2. Connect phone to usb and computer and enable unknown sources and enable usb debugging.
3. Reboot into your current xrecovery
4. Go to start on the bottem left of your windows, then Run...
5. Type cmd and then press okay( run cmd )
6. Type cd \adb and press enter
7. Type adb.exe and press enter
8. Type adb shell and press enter
9. Type rm -r /sdcard and press enter
10. Type mkdir sdcard and press enter
11. Type chmod 777 sdcard and press enter
12. Now go to your phone and install custom zip x recovery gingerbread ready
13. Reboot and go back into your new xrecovery
This is for all those that have problems mounting recovery images all credits go to zdzihu and doomlord just providing a simpler way to install it
(btw this is a compilation of instructions from zdzihu's post and doomlord's post and i take absoulutely no credit for it)
good luck with that. All it does is erase, or make your old directory totally unavailable.
uh? it doesent erase anything all my files are still in my sd card just help to fix the cant mount image problem when ur flashing custom zip if your using like prerooted version of 2.3.3 doomlords etc.
my sdcard is coming up blank now in xrecovery....., and I can't connect with the usb either
### Plezzz BACK YOUR SD CARD OR ANY MOUNT/DRIVE UP BEFORE rm -rf /* ANYTHING. ###
All this is going to do is remove everything stored on your sdcard inclueing your security certs if u have passwords or screen locks. Also the only thing that xrec stores on your sd and backups zip an the logo.this will not remove any configs or xrec from the phone.
rm -r /sdcard/xrecovery <--- This Will Remove The Xrec data storeed on the phone but still this will not work .
and this is in the xrecovery install 1.0 see http://forum.xda-developers.com/showthread.php?t=859571
This is a dublepost
Great, thanx for tutorial?!
Weird im not a developer so i dun know why this is happening but my sd card is working perfectly and nothing has been erased. on ericwills rom for the past few hours and it is flying
For all those who dun want to mess around with adb shell, i suggest you to take a look at doomlords thread http://forum.xda-developers.com/showthread.php?t=1196808 if your recovery has some problems mounting images
fyi depending on your computer, it may end up corrupting your sdcard as well.
what computer os are u using? do a full reformat of your sd card?
okey so i read slade87´s thread on how to get mutitouch on peria mini the link below
http://forum.xda-developers.com/showthread.php?t=1064558
and the truth is i dont understand how to do it so if anyone that knows how to do it then pleas tell me as most detailed as possible
thank you and forgive my ignorence
I would like to help you. Which point you don´t understand?
You must have a ROM which included the kernel "M76XX-TSNCJOLYM-53404015"
For example "X10 Mini Froyo [ROM] MiniCM6-1.0.0-RC2, Froyo Cyanogen 6.1.3" (you can find it in google).
How to get root: (i know it´s not so easy but this is the easiest i found)
1. Download: exploid_x10mini.zip - download and extract the archive...
You will need ADB from Android SDK and USB drivers for X10 mini (part of Sony Ericsson PC Companion).
Enable USB debugging on the phone in Settings>Applications>Development and connect the phone to PC via USB. Reboot your system.
Add the Power Control widget to your active widgets on the phone, so you can quickly turn off and on the wi-fi function.
From the command line (on windows it's cmd.exe):
cd c:\exploid_x10mini (or another folder where you've extracted the files from exploid_x10mini.zip)
adb push Superuser.apk /sdcard/Superuser.apk
adb push su /sdcard/su
adb push exploid /sqlite_stmt_journals/exploid
adb push busybox /sqlite_stmt_journals/busybox
adb shell
cd sqlite_stmt_journals
chmod 755 exploid
chmod 755 busybox
Immediately after the next command, you will need to disable and enable the wi-fi using the power widget on the phone:
./exploid
then run:
rootshell
enter password rootnow
prompt will change to # - now we have root
./busybox cp /sdcard/Superuser.apk /system/app/
./busybox cp /sdcard/su /system/bin/
./busybox cp busybox /system/bin/
chmod 4755 /system/bin/su
rm /system/bin/rootshell
exit - out of rootshell
exit - out of adb shell
Now you can follow the instructions.
To open a shell you need "Android Terminal Emulator". You can find it in Android Market.
Please keep in mind that i just searched for this instruction to help you. I´m not responsible if you brick your phone. Good luck!
nice i didnt knew the possible...
Thanks puRR_cAt for your help however I already rooted my phone and I thought that I didn't need a rom to get multi touch if there's a way to do it without a rom tell me
Sent from my E10i using XDA App
Multitouch is for Mini PRO only!! Not Mini!!
---
- ---
- Sent from my iPod touch using Tapatalk
for x10 mini u get "fake" dual touch....u can get the needed information here
http://forum.xda-developers.com/showthread.php?t=1064558
actually, in very "simple", lucid language, do this step by step:
i am NOT responsible if i brick ur device, use this post guidance at your own risk. or better yet, follow the instructions in the actual post
1. check ur baseband to be "M76XX-TSNCJOLYM-53404015"
2. check the firmware
3. download the "cy8ctma300_ser.zip" attached, to ur computer and extract the "cy8ctma300_ser.ko" file from there, copy it to your memory card. (better u go for the "updated version" link in the post).
4.get root explorer from the market
5.copy the downloaded file which you copied to the memory card to /system/lib/modules" (tap mount r/w before doing this)
6. now go to /etc (tap mount r/w) and scroll down to "hw_config.sh"
7. long press and choose "open in text editor" and add the 2 lines mentioned.
8. press "save and exit"
9. go to /system and scroll to "build.prop" -> tap and hold -> open in text editor and add the two lines in the post.
10. save and exit root explorer
11. reboot and ur good to go
if i helped you, press the "THANKS" button
achyut said:
for x10 mini u get "fake" dual touch....u can get the needed information here
http://forum.xda-developers.com/showthread.php?t=1064558
actually, in very "simple", lucid language, do this step by step:
i am NOT responsible if i brick ur device, use this post guidance at your own risk. or better yet, follow the instructions in the actual post
1. check ur baseband to be "M76XX-TSNCJOLYM-53404015"
2. check the firmware
3. download the "cy8ctma300_ser.zip" attached, to ur computer and extract the "cy8ctma300_ser.ko" file from there, copy it to your memory card. (better u go for the "updated version" link in the post).
4.get root explorer from the market
5.copy the downloaded file which you copied to the memory card to /system/lib/modules" (tap mount r/w before doing this)
6. now go to /etc (tap mount r/w) and scroll down to "hw_config.sh"
7. long press and choose "open in text editor" and add the 2 lines mentioned.
8. press "save and exit"
9. go to /system and scroll to "build.prop" -> tap and hold -> open in text editor and add the two lines in the post.
10. save and exit root explorer
11. reboot and ur good to go
if i helped you, press the "THANKS" button
Click to expand...
Click to collapse
is dat fake dualtouch work for u??? does it work on games??
danigladson said:
is dat fake dualtouch work for u??? does it work on games??
Click to expand...
Click to collapse
It works perfectly
Hi ,... im trying to root my xperia x10 mini pro like in this post:
I have bricked my phone many times now and used SEUS to get it back to 2.1.1.A.0.6 and had to go through the process of rooting and installing CWM again. Here is what I have found.
1.Download SuperOneClick to a folder, e.g. C:\SuperOneClick
2.Create a sub-folder under this folder, e.g. C:\SuperOneClick\CWM
3.Download your preferred version of CWM or xRecovery (should be the 3 files "busybox", "chargemon", "recovery.tar")
4.Copy these 3 files into the sub-folder you created, e.g. C:\SuperOneClick\CWM
5.Copy the code snippet below and save as INSTALL.BAT in the sub-folder
6.Reflash your phone with SEUS to get back to plain 2.1.1.A.0.6
7.Reboot and set USB debugging mode
8.Run SuperOneClick and click Root - do not reboot
9.Once Root has finished click Shell Root - do not reboot
10.Open a command window and enter CD C:\SuperOneClick\CWM
11.Run INSTALL.BAT - this will reboot the phone at the end
12.Press BACK key on the phone at the Sony Ericcson text - you should get into CWM
i made a root w/superoneclick, and apear an option in my phone "superuser" etc... and when i try to do the shell root... appears something like this:
device as a temporary ADB root!Reboot your device to remove it
and when i run install.bat its the same...
...ADB isnt recognized bla bla bla....
can you give me some help?!?
try2me said:
Hi ,... im trying to root my xperia x10 mini pro like in this post:
I have bricked my phone many times now and used SEUS to get it back to 2.1.1.A.0.6 and had to go through the process of rooting and installing CWM again. Here is what I have found.
1.Download SuperOneClick to a folder, e.g. C:\SuperOneClick
2.Create a sub-folder under this folder, e.g. C:\SuperOneClick\CWM
3.Download your preferred version of CWM or xRecovery (should be the 3 files "busybox", "chargemon", "recovery.tar")
4.Copy these 3 files into the sub-folder you created, e.g. C:\SuperOneClick\CWM
5.Copy the code snippet below and save as INSTALL.BAT in the sub-folder
6.Reflash your phone with SEUS to get back to plain 2.1.1.A.0.6
7.Reboot and set USB debugging mode
8.Run SuperOneClick and click Root - do not reboot
9.Once Root has finished click Shell Root - do not reboot
10.Open a command window and enter CD C:\SuperOneClick\CWM
11.Run INSTALL.BAT - this will reboot the phone at the end
12.Press BACK key on the phone at the Sony Ericcson text - you should get into CWM
i made a root w/superoneclick, and apear an option in my phone "superuser" etc... and when i try to do the shell root... appears something like this:
device as a temporary ADB root!Reboot your device to remove it
and when i run install.bat its the same...
...ADB isnt recognized bla bla bla....
can you give me some help?!?
Click to expand...
Click to collapse
Seems like the install.bat script can't locate adb command. Copy the content of cmw folder to whereever you installed the adb platform tools. You did download these I assume?
Or
Copy adb tool to the cwm folder.
Sent from my GT-I9100 using XDA Premium App
actually not all devices are supported with adb shell...