hi,
when i try to see root access with flashtools i see that :
26/051/2011 12:51:23 - INFO - Device connected with USB debugging on
26/051/2011 12:51:26 - INFO - Connected device : E10
26/051/2011 12:51:26 - INFO - Installed version of busybox : BusyBox v1.19.3-Stericson (2011-11-01 20:22:18 CDT) multi-call binary.
26/051/2011 12:51:26 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
26/051/2011 12:51:32 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
26/051/2011 12:51:33 - ERROR - Please Accept root permissions on the phone
26/052/2011 12:52:15 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
26/052/2011 12:52:17 - ERROR - Please Accept root permissions on the phone
26/052/2011 12:52:29 - WARN - Please check your Phone and 'ALLOW' Superuseraccess!
26/052/2011 12:52:31 - ERROR - Please Accept root permissions on the phone
what is the problem ? what can i do ?
It s dot it after i try to flash my x10 mini and have errors. After, i reboot my phone all is ok but not with flashtools
I need to be root to flash stock kernel with flashtools? i need what to to do it ?
thanks
Which android version do you have
Download this if you have android version 2.1 when you connect your phone touch the charge phone and then press root
Press the thanks button if helped you
hi thanks it s help but i don't understand why flashtools do that...
Related
I have done everything(phone rooted,recovery installed and unlocked boot loader)There is option to install kernel through flashtool and i have installed Doomkernel V6 successfully as the log says.But how do i know it.
Easiest way to check it... go to Settings > about phone ... there it should show which kernel you have.
HAve Fun
DIP
No sign of doom kernel in settings.Still showing the stock kernel.
if you have terminal emulator or..
or adb shell.
type ----> cat /proc/version
it will tell you for sure which kernel is running
Through flashtool log
Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
Best way to do it is using S1tool, just run the prog,click identify, connect in flash mode and read the output, if "S1 ERROM VER" starts with a small letter "r8A033" it is unlocked, if starts with a capital letter "R8A033" it is not
One last thing, if you SIM.unlocked your phone using Omnius, then the bootloader it's unlocked, but the flashing process is different, I can tell you because that is my case (and it will appear as not "R8A033")
Can you try reflashing and make sure the Flashtool didn't report any errors?
Here's the log
22/023/2012 15:23:05 - INFO - Installing kernel to device...
22/023/2012 15:23:05 - INFO - Remounting system read-write
22/023/2012 15:23:23 - INFO - Installing chargemon feature / kernel bootkit to device...
22/023/2012 15:23:23 - INFO - Remounting system read-write
22/023/2012 15:23:24 - INFO - Pushing C:\Flashtool\.\devices\X10\bootkit\bootkit.tar to /data/local/tmp
22/023/2012 15:23:24 - INFO - Running installbootkit as root thru sysrun
22/023/2012 15:23:24 - INFO - bootkit successfully installed
22/023/2012 15:23:24 - INFO - Pushing C:\Flashtool\.\devices\X10\kernel\2.6.29-modFXP-DooMKernel-v06-1113\kernel.tar to /data/local/tmp
22/023/2012 15:23:28 - INFO - Running installkernel as root thru sysrun
22/023/2012 15:23:30 - INFO - kernel successfully installed
22/023/2012 15:23:45 - INFO - Device disconnected
22/023/2012 15:23:50 - INFO - Device connected with USB debugging on
22/023/2012 15:23:50 - INFO - Connected device : X10
22/023/2012 15:23:50 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
22/023/2012 15:23:50 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
Did you install the kernel via flashmode or some kind of other method? I don't recall the process to be that long when flashing a kernel.
I just recently got a new X10a so I flashed the new 2.3.3 global generic firmware so that I could root it via flashtool. However, everytime I try and root my phone I get this:
20/021/2012 20:21:29 - INFO - Device connected with USB debugging on
20/021/2012 20:21:29 - INFO - Connected device : X10
20/021/2012 20:21:29 - INFO - Installed version of busybox : N/A
20/021/2012 20:21:29 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537 / Build number : 3.0.1.G.0.75
20/021/2012 20:21:43 - INFO - Decrypting C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue.enc to C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\custom\root\ZergRush\zergrush.tar.uue to /data/local/tmp
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\.\devices\X10\busybox\1.20.0\busybox to /data/local/tmp/busybox
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
20/021/2012 20:21:44 - INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
20/021/2012 20:21:45 - INFO - Running part1 of Root Exploit, please wait
20/021/2012 20:21:45 - INFO - Waiting for device. After 60secs, stop waiting will be forced
20/022/2012 20:22:47 - INFO - Forced stop waiting.
20/022/2012 20:22:47 - ERROR - The part1 exploit did not work
20/022/2012 20:22:47 - INFO - Cleaning files
It should also be noted that I've tried to use the GB ready flashtool 0.2.9.1 to try and root my phone and when I use it the program says that it completed the root successfully. But when I open root checker it tells me I have no root access. Is there anything that can help this? Would manually rooting my phone help anything?
I am actually getting the same issue when attempting to root a x10a. Here's my post in the other thread
http://forum.xda-developers.com/showpost.php?p=34430771&postcount=1849
check out the response from the creator of the Flashtool
http://forum.xda-developers.com/showpost.php?p=34483707&postcount=1854
I've already applied the update and it works fine for me now
waldo98 said:
check out the response from the creator of the Flashtool
http://forum.xda-developers.com/showpost.php?p=34483707&postcount=1854
I've already applied the update and it works fine for me now
Click to expand...
Click to collapse
Thanks a lot man!
Hello,
I have xperia X10 mini (Not pro): E10.
I've used "Flashtool" to root the phone and then to install "xRecovery" (with the cross button).
I manage to use Flashtool V0.7.1.0 because I didn't succeed rooting with the new version 0.9.9.0.
Flashtool recognised my phone OK (E10) and installed recovery with no errors (Log attached).
Now my phone is rooted and has recovery that I can get into while booting.
My question is- The recovey screen headline says "FreeXperia X8 Recovery v001"
. Is it OK even though my model is X10 mini? or I wiil have troubles when flashing ROMs or Kernels?
22/030/2012 14:30:12 - INFO - <- This level is successfully initialized
22/030/2012 14:30:12 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:23
22/030/2012 14:30:12 - INFO - You can drag and drop ftf files here to start flashing them
22/030/2012 14:30:18 - INFO - Device connected with USB debugging on
22/030/2012 14:30:18 - INFO - Connected device : E10
22/030/2012 14:30:18 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
22/030/2012 14:30:18 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29
22/030/2012 14:30:19 - INFO - Remounting system read-write
22/030/2012 14:30:19 - INFO - Installing toolbox to device...
22/030/2012 14:30:19 - INFO - Pushing D:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
22/030/2012 14:30:20 - INFO - Running installftkit as root thru sysrun
22/030/2012 14:30:20 - INFO - Root Access Allowed
22/030/2012 14:30:58 - INFO - Installing Recovery to device...
22/030/2012 14:30:58 - INFO - Remounting system read-write
22/031/2012 14:31:03 - INFO - Installing chargemon feature / kernel bootkit to device...
22/031/2012 14:31:03 - INFO - Remounting system read-write
22/031/2012 14:31:03 - INFO - Pushing D:\Flashtool\.\devices\E10\bootkit\bootkit.tar to /data/local/tmp
22/031/2012 14:31:03 - INFO - Running installbootkit as root thru sysrun
22/031/2012 14:31:04 - INFO - bootkit successfully installed
22/031/2012 14:31:04 - INFO - Pushing D:\Flashtool\.\devices\E10\recovery\xRec\recovery.tar to /data/local/tmp/recovery.tar
22/031/2012 14:31:05 - INFO - Running installrecovery as root thru sysrun
22/031/2012 14:31:05 - INFO - Recovery successfully installed
Did some trys..
I rerooted the phone with SEUS, and repeated the proccess with v0.8.6.0 of FT: Succeed rooting and recovery install.
But the recovery headline is the same- X8.
Is it OK?
well It say the same on my phone and it works perfect and in t he worst case u can flash a new recovery like cwm or new virson of xrecovery :b
Sent from my E10i using xda app-developers app
aharonzu said:
well It say the same on my phone and it works perfect and in t he worst case u can flash a new recovery like cwm or new virson of xrecovery :b
Sent from my E10i using xda app-developers app
Click to expand...
Click to collapse
Nice to hear that, thx!
i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
this comes when flashing
20/044/2013 00:44:14 - INFO - <- This level is successfully initialized
20/044/2013 00:44:15 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
20/044/2013 00:44:15 - INFO - You can drag and drop ftf files here to start flashing them
20/044/2013 00:44:26 - INFO - Device connected with USB debugging on
20/044/2013 00:44:26 - INFO - Connected device : ST17
20/044/2013 00:44:27 - INFO - Installed version of busybox : BusyBox v1.20.2-cm9 bionic (2012-07-14 01:52 +0200) multi-call binary.
20/044/2013 00:44:27 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-FXP / Build number : IMM76L
20/044/2013 00:44:28 - INFO - Root Access Allowed
20/045/2013 00:45:19 - INFO - Selected WT19i_4.0.2.A.0.58_(1254-1868).ftf
20/045/2013 00:45:19 - INFO - Preparing files for flashing
20/045/2013 00:45:30 - INFO - Please connect your device into flashmode.
20/045/2013 00:45:35 - INFO - Device disconnected
20/046/2013 00:46:14 - INFO - Opening device for R/W
20/046/2013 00:46:15 - INFO - Device connected in flash mode
20/046/2013 00:46:15 - INFO - Start Flashing
20/046/2013 00:46:15 - INFO - Processing loader
20/046/2013 00:46:15 - INFO - Checking header
20/046/2013 00:46:15 - INFO - Ending flash session
20/046/2013 00:46:15 - ERROR -
20/046/2013 00:46:15 - ERROR - Error flashing. Aborted
20/046/2013 00:46:15 - INFO - Device connected in flash mode
Try checking "no final verification" before flashing. Should work
Siddharth121 said:
i have cm 4.1 on my wt19i(live with walkman).. bootloader unlocked. flastool is detecting my device as st17. and when try to flash the stock rom, error comes!
plz help
19/025/2013 23:25:51 - INFO - <- This level is successfully initialized
19/025/2013 23:25:51 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
19/025/2013 23:25:51 - INFO - You can drag and drop ftf files here to start flashing them
19/026/2013 23:26:01 - INFO - Device disconnected
19/026/2013 23:26:20 - INFO - Device connected with USB debugging off
19/026/2013 23:26:20 - INFO - For 2011 devices line, be sure you are not in MTP mode
19/026/2013 23:26:22 - INFO - Device connected with USB debugging on
19/026/2013 23:26:22 - INFO - Connected device : ST17
19/026/2013 23:26:22 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/026/2013 23:26:22 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/026/2013 23:26:24 - INFO - Installing toolbox to device...
19/026/2013 23:26:24 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
19/026/2013 23:26:24 - INFO - Running installftkit as root thru sysrun
19/026/2013 23:26:25 - INFO - Root Access Allowed
19/027/2013 23:27:25 - INFO - Device disconnected
19/027/2013 23:27:29 - INFO - Device connected with USB debugging on
19/027/2013 23:27:29 - INFO - Connected device : ST17
19/027/2013 23:27:29 - INFO - Installed version of busybox : BusyBox v1.20.2-jb bionic (2012-11-25 17:47 +0100) multi-call binary.
19/027/2013 23:27:29 - INFO - Android version : 4.1.2 / kernel version : 2.6.32.9-FXP / Build number : JZO54K
19/027/2013 23:27:30 - INFO - Root Access Allowed
Click to expand...
Click to collapse
you have to tick your usb debugging... and then you must in MSC mode it can be on setting .
and dont connect your phone . you must flashing .ftf then after it wait until they say connect your HH with ~~~~.... after that in 10 seconds connect your usb and phone to pics/ laptop during press volume download
Sent from my WT19i using xda premium
hi,
I have pretty much the same symptoms, my ray is seen as ST17i by flashtool.
Is this a flashtool bug or is it really recognized as ST17i?
Thank you!
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Siddharth121 said:
You must b running a custom rom. Is it so? Then it will not be recognised properly. But anything you want to flash, flash it. No problems
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
nroberto13 said:
Yes, I'm running custom rom, but my phone is bricked, if I use stock fw, it hangs at sony ( sony ericsson ) logo.
The phone boots with cm9/10 rom and kernel, but touch is not working .
Click to expand...
Click to collapse
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Mysteryagr said:
It seems like you flashed wrong Rom on your device.
Search in the General section, there is a way to fix touch issue.
Good luck
Sent from my ST15i using xda app-developers app
Click to expand...
Click to collapse
yes, I saw the topic, but none of the fices worked for me .
I haven't found anybody on the forum who was successful on a ray with any of the fixes .
any advise?
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Siddharth121 said:
When you go stock, flash the kernel again. ie flash the fw, then flash kernel.
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
tried that, also flashed system once again, then system and kernel, but phone doesn't boot.
what does cm9/10 different to stock so it boots?
is this issue coming from kernel or from rom?
where are the touch driver placed? in initrd or in rom?
thank you!
Please Help. Please.
I am having WT19i. I have installed Super Jelly Bean 8.0 and having nAa 2.6 kernel. I flashed this kernel through flashtool. That time my device was shown correctly (I guess that means all the drivers are installed correctly). And I havent changed anything on my PC (Windows 7) or in flashtool (0.9.13.0) after that. Now I want to install some KK Rom in my phone. So when I connected my LWW, it shows connected device as Xperia Active (ST17i) instead of WT19i. For that KK Rom, I need to flash .587 stock.ftf file. But I fear if I try to flash, it will brick my phone. I wont get a new mobile in near future. So I dont want to brick it. Anyone please help me through this. How can I get the job done without getting bricked. It will be a great if anyone could tell me.
If I continue with flashing ftf with the current situation (WT19i recognized as ST17i), will it brick my WT19i?? If yes, how to overcome this situation?? Help needed from members. Please, its urgent. I am a newbie actually. This is my first post in xda. Thanks in advance.
m trying to root my Xperia U but when I do that using Flashtool, it gives me an error. The log is below.
03/03/2014 08:30:02 - INFO - <- This level is successfully initialized
03/03/2014 08:30:03 - INFO - Flashtool Version 0.9.14.0 built on 12-02-2014 22:45:00
03/03/2014 08:30:03 - INFO - Device connected with USB debugging on
03/03/2014 08:30:04 - INFO - Connected device : ST25
03/03/2014 08:30:05- INFO - Installed version of busybox : N/A
03/03/2014 08:30:07- INFO - Android version :4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.10
03/03/2014 08:30:10- INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
03/03/2014 08:30:15- INFO - Pushing C:\Flashtool\custom\root\subin\Superuser\chattr : Not found
first i unlock boot loader of xperia u by using official method on sony website
then i try root xperia u by using flash tool and it give me above error
so plz help me to root my xperia u
and whan i select supersu mode then the process started normally
That's how the log ends?
U could 1st try this One
Good luck
[LB][JB] same problem
I just want to root my xperia P to remove some sony and google apps that I don't like,
but I've tried with a win8.1 and win7 pc and I have the same problem. Any solution?
Thanks in advance.
Superuser root package is broken, known bug