Hey,
so.. I want to install a custom rom on my X10 mini pro. I have experience on doing this, because I already rooted many smartphones. But this one is just trolling me.
I used this tutorial (sorry, but it's german). Everything went well till Step 4.7.
I plug in the USB cable, let the flashtool get informations about the device, go to Plugins > Bootloader Unlock and run it.
Then I unplug the cable, start the device in flashmode and theeeen flashtool wants to start unlocking, but the device just shuts down for a moment (green light goes off) and then it reboots into flashmode again.
Here is the output from flashtool
Code:
13/021/2013 17:21:01 - INFO - <- This level is successfully initialized
13/021/2013 17:21:01 - INFO - Flashtool Version 0.9.12.1 built on 2013-06-04 22:50:00
13/021/2013 17:21:06 - INFO - Device disconnected
13/021/2013 17:21:08 - INFO - Device connected with USB debugging on
13/021/2013 17:21:09 - INFO - Connected device : SonyEricson X10 Mini Pro
13/021/2013 17:21:09 - INFO - Installed version of busybox : BusyBox v1.20.2-linusyang (2012-10-15 16:24:24 CST) multi-call binary.
13/021/2013 17:21:09 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
13/021/2013 17:21:10 - INFO - Checking root access
13/021/2013 17:21:14 - INFO - Root Access Allowed
13/021/2013 17:21:58 - INFO - Device connected in flash mode
13/021/2013 17:21:59 - INFO - Opening device for R/W
13/021/2013 17:21:59 - INFO - Reading device information
13/021/2013 17:21:59 - INFO - Phone ready for flashmode operations.
13/021/2013 17:21:59 - INFO - Current device : U20i - CB511NMQAZ - 1237-8223_R13B - 1235-3411_2.1.1.A.0.6 - WORLD-1-8_2.1.1.A.0.6
13/021/2013 17:21:59 - INFO - Processing loader.sin
13/021/2013 17:21:59 - INFO - Checking header
13/021/2013 17:21:59 - INFO - Flashing data
13/022/2013 17:22:01 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / Bootloader status : UNROOTABLE
13/022/2013 17:22:01 - INFO - Start Reading unit 00000851
13/022/2013 17:22:01 - INFO - Reading TA finished.
13/022/2013 17:22:01 - INFO - Ending flash session
13/022/2013 17:22:01 - INFO - Waiting for device to reboot
13/022/2013 17:22:01 - INFO - Waiting for device
13/022/2013 17:22:02 - INFO - Device connected in flash mode
13/022/2013 17:22:03 - INFO - Device disconnected
Code:
13/022/2013 17:22:01 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / [COLOR="Red"]Bootloader status : UNROOTABLE[/COLOR]
Status : unrootable? So does that mean I don't have any chance to root my device? Is there a way to bypass this?
I'd appreciate every kind of help!
regards,
furi
Well, seems like I got it. I've installed a custom kernel (nAa 2.6) but now the device won't boot anymore
It stucks at the nAa-Bootscreen. What can I do now?
furiify said:
Well, seems like I got it. I've installed a custom kernel (nAa 2.6) but now the device won't boot anymore
It stucks at the nAa-Bootscreen. What can I do now?
Click to expand...
Click to collapse
Install a ROM.
SmG67 said:
Install a ROM.
Click to expand...
Click to collapse
Can you tell me how? My pc doesn't detect the device if it's in the bootscreen. Do I have to go into the flashmode?
If yes, there's one little problem. I can't turn it off And if I pull out the battery and put it back in, then the device automatically starts into that bootscreen. ._______.
aaaaand.. I dont have any recovery installed O__o
furiify said:
Can you tell me how? My pc doesn't detect the device if it's in the bootscreen. Do I have to go into the flashmode?
If yes, there's one little problem. I can't turn it off And if I pull out the battery and put it back in, then the device automatically starts into that bootscreen. ._______.
aaaaand.. I dont have any recovery installed O__o
Click to expand...
Click to collapse
Recovery is in the kernel, use that
Reboot is Home- and Powerbuttons together
If you use the JB-kernel It should boot into Recovery, if that doesn't happen flash the kernel again, that might do the trick. Otherwise you have to press the back-button repeatedly when the phone starts up.
SmG67 said:
Recovery is in the kernel, use that
Reboot is Home- and Powerbuttons together
If you use the JB-kernel It should boot into Recovery, if that doesn't happen flash the kernel again, that might do the trick. Otherwise you have to press the back-button repeatedly when the phone starts up.
Click to expand...
Click to collapse
Thanks alot. It helped. Now I am able to boot into recovery.
BUT! I can't install any rom!? I've tried LiteCM and PureSlim.
All I get is this message :
By the way - I installed this kernel now (U20_nAa-jb-03_2.6.29.6-nAa-jb-03)
I also tried to use the newest kernel (U20_2.6.32.61-nAa-06), but I get the same result
And yes, I did a full wipe and formatted /system /cache and /data.
Now I am a bit helpless It's a JB Kernel and also JB Roms, so why won't they install? :'(
Edit : After trying and trying and trying I got the xperiabean installed.. Thanks again SmG <3
furiify said:
Thanks alot. It helped. Now I am able to boot into recovery.
BUT! I can't install any rom!? I've tried LiteCM and PureSlim.
All I get is this message :
By the way - I installed this kernel now (U20_nAa-jb-03_2.6.29.6-nAa-jb-03)
I also tried to use the newest kernel (U20_2.6.32.61-nAa-06), but I get the same result
And yes, I did a full wipe and formatted /system /cache and /data.
Now I am a bit helpless It's a JB Kernel and also JB Roms, so why won't they install? :'(
Edit : After trying and trying and trying I got the xperiabean installed.. Thanks again SmG <3
Click to expand...
Click to collapse
I think lightCM and PureSlim both look for kernel version 2.6.32.60. The Old JB kernel is 2.6.29.6 and the latest one (the 06) is 2.6.32.61. So you could edit the updater-script to reflect the correct version.
Related
So you did the inevitable... you got a phone that's bricked.. fear not.. this happens to all of us.. consider it a "right of passage" when it comes to dealing with custom ROM's
Here at xda, help is never too far away (I was there once too)
I've tried to get you back to functioning latest Local 2.1 with recovery (xrecovery)
0) You'll lose all data with this method....
come to terms with that... not stuff on the sd card but data of your phone, sms'es, contacts, applications etc
1) Turn off your phone
Pull the battery and reinsert it if you have to...
2) Install Flashtool
go here and downlad flashtool
Install on your windows pc
Thank Androxyde and Bin4ry for this kickass tool
3) Download and flash stock 2.1
Go to this thread and download a 2.1 rom in your language of choice (Dont worry that it's not your local ROM)
4) Flash this rom using Flashtool
In the first link there is a how-to. follow it and flash the downloaded ROM from step 3
Once you have 2.1 on your phone,
5) Enable USB Debugging and Root
Use flashtool and root your phone using the simple button "Root" (I know!! what an awesome tool right!!?? )
Once rooted, disconnect the phone.
6) Get yourself a root file manager
Download a file manager capable of root access such as root explorer or solid explorer.
7) Access and edit the build.prop file
Open the file manager. U should get a superuser prompt to allow root access. Touch "Allow". Go to /system and mount the system as RW. there's a file there called build.prop. open it in a text editor. Find all instances of a number that looks like this 1238-9045 (this is my build number, yours will not be the same). Edit this number(all 3 instances) to look like your build number (Found on original box or behind the battery). Save the file and exit
8) Update via SEUS OR PC companion
Now connect your phone back. PC companion or SEUS will tell you there is a new update available. follow the instructions and you'll be running the latest 2.1 for your region and variant of the mini pro
9) [optional] Root and recovery
The new firmware installed by SEUS/PC companion is not rooted. If you need it, root again (same way as in step 5). once rooted, click "Ask root perms" on flashtool. Once root access is confirmed, install xrecovery from the menu.
Hope that helped!
Enjoy
Edit: if you get an error while opening flashtool saying "JVM could not be started because heap size bla bla bla..." Please try on another pc and maybe reinstall windows on urs
Bricked u20i
My phone keeps disconnecting nce the green light goes on. Please help
I have bricked xperia mini x10, and it's failing to boot. Debugging is turned off, so flashboot can't recognize it.
16/010/2012 19:10:31 - INFO - Device connected with USB debugging off
16/010/2012 19:10:31 - INFO - For 2011 devices line, be sure you are not in MTP mode
Click to expand...
Click to collapse
Can someone help?
Immortalis said:
I have bricked xperia mini x10, and it's failing to boot. Debugging is turned off, so flashboot can't recognize it.
Can someone help?
Click to expand...
Click to collapse
Repair it with SEUS or PC Companion.
Step A: leave your phone disconnected from your PC
Step B: Run SEUS/PC Companion, and select update
Step C: It doesn't recognise your phone because it's disconnected and give you a repair option
Step D: Select it, choose your model, it will download the firmware
Step Ea: You get a popup, Press the back-button on your phone while it's off and plug in the USB-Cable
Step Eb: If you can't turn off your phone, plug in the USB-cable and press home- and power-buttons at the same time, it will do a hard reboot and enter flashmode.
Step F: Wait till it's done...
everything past item 3 is pretty hard since we can't acces anything on phone(that's bricking a phone right) to enable usb debugging.
Good tutorial though for those who installed a custom rom and they want to revert to original plus root acces.
Any ideea how to force seus or flash to force flash?
slvjpn said:
everything past item 3 is pretty hard since we can't acces anything on phone(that's bricking a phone right) to enable usb debugging.
Good tutorial though for those who installed a custom rom and they want to revert to original plus root acces.
Any ideea how to force seus or flash to force flash?
Click to expand...
Click to collapse
You don't need usb-debugging in order to flash your phone.
SmG67 said:
You don't need usb-debugging in order to flash your phone.
Click to expand...
Click to collapse
tell this to my sister's x10 pro mini ). I know your right but the phone is @&&&@%))+6)-)-))-=+( up so it doesn't know human comands
Help needed !!
Hi to all,i`m new on this forum and new to Sony Ericsson!
Few days ago i did a repair option with the PcCompanion,becouse i removed to much apk`s.
After about 2 minutes,PcCompanion displayed error (code 100) and stopped flashing!
Searched the internet and found solution!
Flashtool!
But no way it keeps telleing me an error!
17/028/2012 17:28:11 - INFO - <- This level is successfully initialized
17/028/2012 17:28:11 - INFO - Flashtool Version 0.7.0.0 built on 2012-04-14 11:34:01
17/028/2012 17:28:11 - INFO - You can drag and drop ftf files here to start flashing them
17/028/2012 17:28:20 - INFO - Device disconnected
17/028/2012 17:28:38 - INFO - Selected Xperia X10 Mini Pro (U20)_2.1 (2.1.1.A.0.6) Reloaded_Greek (by Leajian).ftf
17/028/2012 17:28:38 - INFO - Preparing files for flashing
17/028/2012 17:28:53 - INFO - Please connect your device into flashmode.
17/029/2012 17:29:01 - INFO - Device connected in flash mode
17/029/2012 17:29:02 - INFO - Opening device for R/W
17/029/2012 17:29:03 - INFO - Reading device information
17/029/2012 17:29:03 - INFO - Phone ready for flashmode operations.
17/029/2012 17:29:03 - INFO - Start Flashing
17/029/2012 17:29:03 - INFO - Flashing loader
17/029/2012 17:29:04 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
17/029/2012 17:29:04 - INFO - Flashing fota1.sin
17/029/2012 17:29:04 - INFO - Ending flash session
17/029/2012 17:29:04 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
17/029/2012 17:29:04 - ERROR - Error flashing. Aborted
17/029/2012 17:29:05 - INFO - Device connected in flash mode
17/029/2012 17:29:07 - INFO - Device disconnected
17/029/2012 17:29:09 - INFO - Device connected in flash mode
please any help will be usefull!
How to bring back alive my X10 Mini Pro?
Now the only thing happends,green blink for 1 second and a bit vibration!
Also tryed with SEUS,no suc6!
(Damn I've been gone a while)
Not too sure of the greek firmware file bro.. can you put the link of the forum where you got it from? are you sure it is a stock firmware?
gixxerfan said:
Hi to all,i`m new on this forum and new to Sony Ericsson!
Few days ago i did a repair option with the PcCompanion,becouse i removed to much apk`s.
After about 2 minutes,PcCompanion displayed error (code 100) and stopped flashing!
Searched the internet and found solution!
Flashtool!
But no way it keeps telleing me an error!
17/028/2012 17:28:11 - INFO - <- This level is successfully initialized
17/028/2012 17:28:11 - INFO - Flashtool Version 0.7.0.0 built on 2012-04-14 11:34:01
17/028/2012 17:28:11 - INFO - You can drag and drop ftf files here to start flashing them
17/028/2012 17:28:20 - INFO - Device disconnected
17/028/2012 17:28:38 - INFO - Selected Xperia X10 Mini Pro (U20)_2.1 (2.1.1.A.0.6) Reloaded_Greek (by Leajian).ftf
17/028/2012 17:28:38 - INFO - Preparing files for flashing
17/028/2012 17:28:53 - INFO - Please connect your device into flashmode.
17/029/2012 17:29:01 - INFO - Device connected in flash mode
17/029/2012 17:29:02 - INFO - Opening device for R/W
17/029/2012 17:29:03 - INFO - Reading device information
17/029/2012 17:29:03 - INFO - Phone ready for flashmode operations.
17/029/2012 17:29:03 - INFO - Start Flashing
17/029/2012 17:29:03 - INFO - Flashing loader
17/029/2012 17:29:04 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
17/029/2012 17:29:04 - INFO - Flashing fota1.sin
17/029/2012 17:29:04 - INFO - Ending flash session
17/029/2012 17:29:04 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
17/029/2012 17:29:04 - ERROR - Error flashing. Aborted
17/029/2012 17:29:05 - INFO - Device connected in flash mode
17/029/2012 17:29:07 - INFO - Device disconnected
17/029/2012 17:29:09 - INFO - Device connected in flash mode
please any help will be usefull!
How to bring back alive my X10 Mini Pro?
Now the only thing happends,green blink for 1 second and a bit vibration!
Also tryed with SEUS,no suc6!
Click to expand...
Click to collapse
cant flash using SEUS...its saying i have latest version but in reality the phone is already bricked by me and not having the original stock firmware... now it just keeps restart with sony erricson logo and turns off again and bootloop...cant root, cant flash... heard that there is some special modified usb that will make the bootloader enter download mode so that we can flash fresh firmware inside it?
jasonmiracle said:
cant flash using SEUS...its saying i have latest version but in reality the phone is already bricked by me and not having the original stock firmware... now it just keeps restart with sony erricson logo and turns off again and bootloop...cant root, cant flash... heard that there is some special modified usb that will make the bootloader enter download mode so that we can flash fresh firmware inside it?
Click to expand...
Click to collapse
You can always flash... post your model and if your bootloader is locked or unlocked ( since you're on SE kernel logo, i assume it's locked), and i can provide you with stock firmware (E10i or U20i) to flash with flashtool.
SmG67 said:
You can always flash... post your model and if your bootloader is locked or unlocked ( since you're on SE kernel logo, i assume it's locked), and i can provide you with stock firmware (E10i or U20i) to flash with flashtool.
Click to expand...
Click to collapse
hi, i am u20i model...i accidentally locked the bootloader while having nna kernel i think, because flashing customised rom and kernel, my phone will enter bootloop, thats why i pressed Restore inside s1tool.exe, which got my bootloader locked....
and now that my bootloader is locked, and i cant root my phone without turning it on( the phone bricked cant turn on anymore) i cant unlock my bootloader to flash new kernels into it... please do provide stock firmware and rom for me... i can only flash stock kernel, but not the rom... after i flashed the stock u20i kernel, i dont know how to flash the original rom into my phone, since now my phone, didnt have the CWM or XRecover anymore, which can browse my SD card, and install the rom from .zip files....
flashing stock kernel no problem but did not know how to flash the stock rom
01/041/2012 15:41:58 - INFO - Device connected in flash mode
01/041/2012 15:41:59 - INFO - Opening device for R/W
01/041/2012 15:41:59 - INFO - Reading device information
01/042/2012 15:42:00 - INFO - Phone ready for flashmode operations.
01/042/2012 15:42:00 - INFO - Start Flashing
01/042/2012 15:42:00 - INFO - Processing loader
01/042/2012 15:42:00 - INFO - Checking header
01/042/2012 15:42:00 - INFO - Flashing data
01/042/2012 15:42:02 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Bootloader status : UNROOTABLE
01/042/2012 15:42:02 - INFO - Processing kernel.sin
01/042/2012 15:42:02 - INFO - Checking header
01/042/2012 15:42:02 - INFO - Flashing data
01/042/2012 15:42:05 - INFO - Ending flash session
01/042/2012 15:42:05 - INFO - Flashing finished.
01/042/2012 15:42:05 - INFO - Please unplug and start your phone
01/042/2012 15:42:05 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
01/042/2012 15:42:06 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
unable to flash customised kernel probably because of the locked bootloader
01/052/2012 15:52:27 - INFO - Device connected in flash mode
01/052/2012 15:52:27 - INFO - Opening device for R/W
01/052/2012 15:52:28 - INFO - Reading device information
01/052/2012 15:52:28 - INFO - Phone ready for flashmode operations.
01/052/2012 15:52:28 - INFO - Start Flashing
01/052/2012 15:52:28 - INFO - Processing loader
01/052/2012 15:52:28 - INFO - Checking header
01/052/2012 15:52:28 - INFO - Ending flash session
01/052/2012 15:52:28 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
s1tool shows locked bootloader
i1109.photobucket.com/albums/h426/jasonforeverlove/11-2.jpg
problem- cant turn on the phone in order to choose usb debugging mode to root the phone
problem- SEUS cant detect update to my phone...
spent 3 weeks in vail...wish i can get it working ...reli hope to succeed in using customised ROM
jasonmiracle said:
hi, i am u20i model...i accidentally locked the bootloader while having nna kernel i think, because flashing customised rom and kernel, my phone will enter bootloop, thats why i pressed Restore inside s1tool.exe, which got my bootloader locked....
...
spent 3 weeks in vail...wish i can get it working ...reli hope to succeed in using customised ROM
Click to expand...
Click to collapse
Download this, It's the complete SE 2.1 Firmware (Kernel and ROM), flashable with flashtool.
(It's about 213.5MB, although the site may display it's less in your download dialog, but it will keep downloading till it's all there)
SmG67 said:
ubuntuone.com/515oWr7b8j4PeeZfm8xZ1pIt's the complete SE 2.1 Firmware (Kernel and ROM), flashable with flashtool.
(It's about 213.5MB, although the site may display it's less in your download dialog, but it will keep downloading till it's all there)
Click to expand...
Click to collapse
im trying this out... :victory:
tks for the thread, dude
My X10 mini pro won't turn on.
I've try the methods that mentioned in this thread but it all failed.
my phone still won't turn on. if i charged it, it's just boot for 2 seconds and then dead. repeatedly.
any suggestion?
*sorry for bad english
itwasgood said:
My X10 mini pro won't turn on.
I've try the methods that mentioned in this thread but it all failed.
my phone still won't turn on. if i charged it, it's just boot for 2 seconds and then dead. repeatedly.
any suggestion?
*sorry for bad english
Click to expand...
Click to collapse
Repair with Sony Update Service or PC Companion?
SmG67 said:
Repair with Sony Update Service or PC Companion?
Click to expand...
Click to collapse
already tried it. but still it won't turned on.
flashtool does not recognize my phone
flashtool does not recognize my x10 mini pro, screen still remains black, seus and pc companion does not recognize it either. what do i do?:crying:
itwasgood said:
already tried it. but still it won't turned on.
Click to expand...
Click to collapse
Your tried to unlock your booloader and now dont turn on?
If your phones was manufacturated after 11w29, you got a hard brick.
I used a custom rom "Real ICS 5.1" for past two months, suddenly this evening mobile restarted, and stuck with home screen, after i remove and insert the battery, now mobile stucks after sony logo, i restarted many times, but no luck.
just panic now.
connect with flashtool and get the log below.
04/034/2012 20:34:54 - INFO - <- This level is successfully initialized
04/034/2012 20:34:55 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/034/2012 20:34:55 - INFO - You can drag and drop ftf files here to start flashing them
04/035/2012 20:35:01 - INFO - Device disconnected
04/035/2012 20:35:54 - INFO - Device connected in flash mode
04/037/2012 20:37:27 - INFO - <- This level is successfully initialized
04/037/2012 20:37:37 - INFO - Device disconnected
04/038/2012 20:38:02 - INFO - Device connected in flash mode
04/038/2012 20:38:42 - INFO - Device disconnected
04/039/2012 20:39:19 - INFO - Device connected with USB debugging off
04/039/2012 20:39:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:53 - INFO - Device disconnected
04/041/2012 20:41:58 - INFO - Device connected with USB debugging off
04/041/2012 20:41:58 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:58 - INFO - Device connected with USB debugging on
04/041/2012 20:41:59 - INFO - Connected device : WT19
04/041/2012 20:41:59 - INFO - Installed version of busybox : BusyBox v1.19.4-wraithdu (2012-02-16 23:47:29 CST) multi-call binary.
04/041/2012 20:41:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf
04/041/2012 20:41:59 - INFO - Remounting system read-write
04/042/2012 20:42:01 - INFO - Installing toolbox to device...
04/042/2012 20:42:01 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
04/042/2012 20:42:04 - ERROR - failed to copy 'C:\Flashtool\custom\root\ftkit.tar' to '/data/local/tmp/ftkit.tar': No space left on device
04/042/2012 20:42:04 - INFO - Root Access Allowed
04/042/2012 20:42:38 - INFO - Log written to C:\Flashtool\flashtool_2012-10-04_08-34-54.log
I didn't know what do next, any suggestions please.
Regards
Jaleel.
jaleelchennai said:
I used a custom rom "Real ICS 5.1" for past two months, suddenly this evening mobile restarted, and stuck with home screen, after i remove and insert the battery, now mobile stucks after sony logo, i restarted many times, but no luck.
just panic now.
connect with flashtool and get the log below.
04/034/2012 20:34:54 - INFO - <- This level is successfully initialized
04/034/2012 20:34:55 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/034/2012 20:34:55 - INFO - You can drag and drop ftf files here to start flashing them
04/035/2012 20:35:01 - INFO - Device disconnected
04/035/2012 20:35:54 - INFO - Device connected in flash mode
04/037/2012 20:37:27 - INFO - <- This level is successfully initialized
04/037/2012 20:37:37 - INFO - Device disconnected
04/038/2012 20:38:02 - INFO - Device connected in flash mode
04/038/2012 20:38:42 - INFO - Device disconnected
04/039/2012 20:39:19 - INFO - Device connected with USB debugging off
04/039/2012 20:39:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:53 - INFO - Device disconnected
04/041/2012 20:41:58 - INFO - Device connected with USB debugging off
04/041/2012 20:41:58 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/041/2012 20:41:58 - INFO - Device connected with USB debugging on
04/041/2012 20:41:59 - INFO - Connected device : WT19
04/041/2012 20:41:59 - INFO - Installed version of busybox : BusyBox v1.19.4-wraithdu (2012-02-16 23:47:29 CST) multi-call binary.
04/041/2012 20:41:59 - INFO - Android version : 4.0.4 / kernel version : 2.6.32.9-perf
04/041/2012 20:41:59 - INFO - Remounting system read-write
04/042/2012 20:42:01 - INFO - Installing toolbox to device...
04/042/2012 20:42:01 - INFO - Pushing C:\Flashtool\custom\root\ftkit.tar to /data/local/tmp
04/042/2012 20:42:04 - ERROR - failed to copy 'C:\Flashtool\custom\root\ftkit.tar' to '/data/local/tmp/ftkit.tar': No space left on device
04/042/2012 20:42:04 - INFO - Root Access Allowed
04/042/2012 20:42:38 - INFO - Log written to C:\Flashtool\flashtool_2012-10-04_08-34-54.log
I didn't know what do next, any suggestions please.
Regards
Jaleel.
Click to expand...
Click to collapse
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
can i try other custom rom?
mihahn said:
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
Click to expand...
Click to collapse
can i try other custom rom? like real ics 6?
jaleelchennai said:
can i try other custom rom? like real ics 6?
Click to expand...
Click to collapse
If your bootloader is unlocked, sure. Otherwise, can you enter cwm?
yes i can enter in cwm, i will try another rom, thanks..
jaleelchennai said:
yes i can enter in cwm, i will try another rom, thanks..
Click to expand...
Click to collapse
Is your bootloader locked or unlocked? Because if it's unlocked and you chose the right kernel and rom, maybe you forgot to do a factory reset or wipe cache?
it is unlocked 7 months ago, i tried some gb roms and this ics rom, but now only i had this type of problem, that why i little worried about.
May b just reflash the right kernel (kernel panic works fine with r6) then factory reset,wipe,dalvik cache and format system and flash the rom. I hope that should solve your problem. Otherwise you can always try stock kernel & rom suggested by mihahn
Try Pestanoid v3
Can you try this my ROM Pestanoid v3 ...http://forum.xda-developers.com/showthread.php?t=1905976
Just try another rom+kernel and remeber: You will have to do a factory reset and wipe cache/dalvik cache, but only format system if it's required in rom thread! Otherwise don't format it
Sent from my SK17i running Jelly Bean via CM10
Also turn usb debugging on when using flashtools!!
Thanks for all, now it is solved with another rom and Mesa kernel. But now i am think to re-flash new rom http://forum.xda-developers.com/showthread.php?t=1908269,
will download in this evening.
Stuck after SONY logo
I tried everything bt nothing is helpin me out to solve ths issue.
I flashed my cell again n again to stock ROM. bt, still my XMP is not able to boot or charge. I've repaired my cell through SUS, bt still same problem. what to do ?? I am on stock kernel n Stock ROM (ICS 4.1.B.0.587). My Bootloead is Locked.
Pls Reply ASAP.
First of all dont panic. you have NOT BRICKED ur phone.
Just flash any other kernel and any other ROM. your device should work fine...
Once I had the same problem.
The solution is flash your mobile with another kernel and wipe everything.
Use a custom rom.if nothing happen reunlock ur bootloder with testpoint method.
Sent from my WT19i using Tapatalk 2
mihahn said:
You must reflash stock rom in flashmode. Just select the stock gingerbread 4.0.2.A.0.42 firmware and flash it. Do you know how to do that?
Click to expand...
Click to collapse
hey i jst got the same problem i installed Xperia T Ics Rom 7.1.8 and then i was using it suddenly my device restarted and is stucked on sony logo:crying:
plzz help me on that!!!
CHETANN.5 said:
hey i jst got the same problem i installed Xperia T Ics Rom 7.1.8 and then i was using it suddenly my device restarted and is stucked on sony logo:crying:
plzz help me on that!!!
Click to expand...
Click to collapse
Have you tried reflashing the stock rom? If not search on xda, there should be a tutorial
Sent from my SK17i running stock ics (.587)
mihahn said:
Have you tried reflashing the stock rom? If not search on xda, there should be a tutorial
Sent from my SK17i running stock ics (.587)
Click to expand...
Click to collapse
No coz i dont know how to flash it ..n also i had a locked bootloader
CHETANN.5 said:
No coz i dont know how to flash it ..n also i had a locked bootloader
Click to expand...
Click to collapse
You can even flash on locked bootloader
So you download the stock firmware .ftf (for ics 4.1.B.0.587) for your device. (e.g. mini=st15=smultron, minipro=sk17=mango, active=st17=satsuma, livewithwalkman=wt19=coconut). Then you install flashtool and install all drivers for all devices/modes from flashtool installation folder - drivers
Now you place the downloaded .ftf in flashtool - firmwares and delete all other files in there. Afterwards you launch flashtool
Now click on the flash - flashmode - select the .ftf - click okay - now turn off phone, take out battery, wait 10 seconds, reinsert battery, hold volume down and while holding volume down simply connect phone via usb to your pc, the green led will light up and the flashing process starts. Now wait until it has finished, disconnect phone and boot it. Done :good:
Sent from my SK17i running stock ics (.587)
Thanxxxxx it worked
N also can i now install other roms on it as did before??
Deleted! - see post 3
Help soon plzz
Anyone here to help??
I'hv repaired my phn n rooted it!
BUT I CAN'T UNLOCK BOOTLOADER. I MEAN THE FLASHTOOL DOESN'T SHOWS ANY PLUGIN?? :/
WHY?
N ALSO CWN RECOVERY IS ALSO NOT INSTALLING N Naa KERNELS TOO.. WILL THE BE INSTALLES AFTER UNLOCKING BOOTLOADER??
mkhawx said:
Anyone here to help??
I'hv repaired my phn n rooted it!
BUT I CAN'T UNLOCK BOOTLOADER. I MEAN THE FLASHTOOL DOESN'T SHOWS ANY PLUGIN?? :/
WHY?
N ALSO CWN RECOVERY IS ALSO NOT INSTALLING N Naa KERNELS TOO.. WILL THE BE INSTALLES AFTER UNLOCKING BOOTLOADER??
Click to expand...
Click to collapse
You need to turn on usb-debugging on your phone (settings, applications, advanced, usb-debugging).
If you're having trouble with flashtool, you could post the output of what happens when you plug in your phone or try a particular option that fails.
SmG67 said:
You need to turn on usb-debugging on your phone (settings, applications, advanced, usb-debugging).
If you're having trouble with flashtool, you could post the output of what happens when you plug in your phone or try a particular option that fails.
Click to expand...
Click to collapse
USB-Debugging mode is always on + unknown sources too!
I have atached the screenshot plz see..
Flashtool doesn't shows any plugin..!!
n for instaling nAa kernel is it necessary to have bootloader unlocked?????
N when i flash nAa kernel.. it shows this....:
26/005/2012 21:05:47 - INFO - Selected U20_nAa-14_2.6.29.6-nAa-14.ftf
26/005/2012 21:05:47 - INFO - Preparing files for flashing
26/005/2012 21:05:47 - INFO - Please connect your device into flashmode.
26/005/2012 21:05:47 - INFO - Opening device for R/W
26/005/2012 21:05:48 - INFO - Reading device information
26/005/2012 21:05:50 - INFO - Unable to read from phone after having opened it.
26/005/2012 21:05:50 - INFO - trying to continue anyway
26/005/2012 21:05:50 - INFO - Start Flashing
26/005/2012 21:05:50 - INFO - Processing loader
26/005/2012 21:05:50 - INFO - Checking header
26/005/2012 21:05:54 - INFO - Ending flash session
26/005/2012 21:05:54 - ERROR - Error in processHeader : 995 : The I/O operation has been aborted because of either a thread exit or an application request.
26/005/2012 21:05:54 - ERROR - Error flashing. Aborted
26/005/2012 21:05:54 - INFO - Device disconnected
26/006/2012 21:06:03 - INFO - Device connected with USB debugging on
26/006/2012 21:06:04 - INFO - Connected device : U20
26/006/2012 21:06:04 - INFO - Installed version of busybox : N/A
26/006/2012 21:06:04 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
mkhawx said:
USB-Debugging mode is always on + unknown sources too!
I have atached the screenshot plz see..
...
n for instaling nAa kernel is it necessary to have bootloader unlocked?????
N when i flash nAa kernel.. it shows this....:
...
26/006/2012 21:06:04 - INFO - Installed version of busybox : N/A
26/006/2012 21:06:04 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.A.0.6
Click to expand...
Click to collapse
Yes, you need to have your bootloader unlocked, and the first problem i notice is that you haven't installed busybox to your phone. Let flashtool 'root' your phone by pushing the 'padlock' button and follow the instructions.
SmG67 said:
Yes, you need to have your bootloader unlocked, and the first problem i notice is that you haven't installed busybox to your phone. Let flashtool 'root' your phone by pushing the 'padlock' button and follow the instructions.
Click to expand...
Click to collapse
Thnx for ur replies.. I successfully flashed it! unlocked bootloader + cwm + nAa kernel + cm7......
thnx btn pressed! :good:
Well gj
Gretings, my rooted phone keeps restarting for ever. Likely after I installed busybox and made some changes with Root Toolbox Pro.
Can't even turn off. Is there a chance how to turn it off and repair the phone to bootable state?
Which phone? If you cannot pull battery, press and hold power + vol up button for about 10 seconds, ( wait for 3 vibration), this will turn phone off, then use flashtool to flash stock ftf.
Sent from my ST27i
bflmpsvz said:
Gretings, my rooted phone keeps restarting for ever. Likely after I installed busybox and made some changes with Root Toolbox Pro.
Can't even turn off. Is there a chance how to turn it off and repair the phone to bootable state?
Click to expand...
Click to collapse
Its in bootloop.......
try this LINK
satan89 said:
Which phone? If you cannot pull battery, press and hold power + vol up button for about 10 seconds, ( wait for 3 vibration), this will turn phone off, then use flashtool to flash stock ftf.
Sent from my ST27i
Click to expand...
Click to collapse
Thank you, holding power+up finally turned off the phone.
Now what are chances to repair the phone booting without losing applications and settings, if any...
The exact firmware version is 6.1.1.B.1.54 on LT22i.
Is this the proper firmware to use for this?
@[email protected] said:
Its in bootloop.......
try this LINK
Click to expand...
Click to collapse
TY. It shows the Sony Logo, then Xperia logo for few seconds and restarts.
Now I'd appreciate the workflow to restore my phone with least harm to installed system.
Is flashing stock ftf resetting to factory defaults?
bflmpsvz said:
Thank you, holding power+up finally turned off the phone.
Now what are chances to repair the phone booting without losing applications and settings, if any...
The exact firmware version is 6.1.1.B.1.54 on LT22i.
Is this the proper firmware to use for this?
Click to expand...
Click to collapse
flash that ftf present in the link
uncheck wipe data in flashtool
ur apps will stay bt settings wont
Sent from my Xperia U using Tapatalk 2
Is that possible before flash copy all my phone's memory with flashtool to my HDD so that I could selectively restore data for safe apps?
The recovery went fine.
Flashed Sony Xperia P LT22i_ 6.1.1.B.1.54_Sony.ftf no reset data succesfully, phone is bootable now with all settings but unrooted
I open flashtool, flashmode, use Xperia P LT22_6.1.B.0.599_Kernel.ftf, reboot phone and the screen is dark, can't do anything with it.
Returned back to Xperia P LT22_6.1.1.B.1.54_Kernel.ftf and tried with flashtool>Unlock>Superuser or SuperSU but still no root.
Code:
26/008/2013 21:08:46 - INFO - Device connected with USB debugging on
26/008/2013 21:08:50 - INFO - Connected device : LT22
26/008/2013 21:08:50 - INFO - Installed version of busybox : N/A
26/008/2013 21:08:50 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
26/009/2013 21:09:17 - INFO - Pushing D:\comm\Sony\FlashTool\.\devices\LT22\busybox\1.20.2\busybox to /data/local/tmp/busybox
26/009/2013 21:09:19 - INFO - Pushing D:\comm\Sony\FlashTool\custom\root\subin\Superuser\su to /data/local/tmp/su
26/009/2013 21:09:19 - INFO - Pushing D:\comm\Sony\FlashTool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
26/009/2013 21:09:22 - INFO - Pushing D:\comm\Sony\FlashTool\custom\root\AdbRestore\RootMe.tar to /data/local/tmp/RootMe.tar
26/009/2013 21:09:26 - INFO - Now open your device and restore "RootMe" backup. Waiting ...
26/009/2013 21:09:26 - INFO - You have 60 seconds to follow the restore advice
26/009/2013 21:09:26 - INFO - Running adbrestoreexploit
26/009/2013 21:09:28 - INFO - Restore worked fine. Rebooting device. Please wait ...
26/009/2013 21:09:38 - INFO - Waiting for device
26/009/2013 21:09:39 - INFO - Device disconnected
26/010/2013 21:10:10 - INFO - Device connected with USB debugging on
26/010/2013 21:10:21 - INFO - Root hack did not work.
26/010/2013 21:10:21 - INFO - Cleaning hack files
26/010/2013 21:10:22 - INFO - Rebooting device. Please wait.
26/010/2013 21:10:29 - INFO - Device disconnected
26/010/2013 21:10:59 - INFO - Device connected with USB debugging on
26/011/2013 21:11:04 - INFO - Connected device : LT22
26/011/2013 21:11:04 - INFO - Installed version of busybox : N/A
26/011/2013 21:11:04 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
26/012/2013 21:12:17 - INFO - Pushing D:\comm\Sony\FlashTool\.\devices\LT22\busybox\1.20.2\busybox to /data/local/tmp/busybox
26/012/2013 21:12:18 - INFO - Pushing D:\comm\Sony\FlashTool\custom\root\subin\Supersu\su to /data/local/tmp/su
26/012/2013 21:12:19 - INFO - Pushing D:\comm\Sony\FlashTool\custom\root\subin\Supersu\Superuser.apk to /data/local/tmp/Superuser.apk
26/012/2013 21:12:21 - INFO - Pushing D:\comm\Sony\FlashTool\custom\root\AdbRestore\RootMe.tar to /data/local/tmp/RootMe.tar
26/012/2013 21:12:24 - INFO - Now open your device and restore "RootMe" backup. Waiting ...
26/012/2013 21:12:24 - INFO - You have 60 seconds to follow the restore advice
26/012/2013 21:12:25 - INFO - Running adbrestoreexploit
26/012/2013 21:12:27 - INFO - Restore worked fine. Rebooting device. Please wait ...
26/012/2013 21:12:35 - INFO - Waiting for device
26/012/2013 21:12:36 - INFO - Device disconnected
26/013/2013 21:13:06 - INFO - Device connected with USB debugging on
26/013/2013 21:13:19 - INFO - Root hack did not work.
26/013/2013 21:13:19 - INFO - Cleaning hack files
26/013/2013 21:13:20 - INFO - Rebooting device. Please wait.
26/013/2013 21:13:27 - INFO - Device disconnected
26/013/2013 21:13:56 - INFO - Device connected with USB debugging on
26/014/2013 21:14:01 - INFO - Connected device : LT22
26/014/2013 21:14:01 - INFO - Installed version of busybox : N/A
26/014/2013 21:14:01 - INFO - Android version : 4.0.4 / kernel version : 3.0.8+ / Build number : 6.1.1.B.1.54
26/015/2013 21:15:21 - INFO - Canceled
Root
bflmpsvz said:
The recovery went fine.
Flashed Sony Xperia P LT22i_ 6.1.1.B.1.54_Sony.ftf no reset data succesfully, phone is bootable now with all settings but unrooted
Click to expand...
Click to collapse
Root all Xperia This way.
mathbalaji said:
Root all Xperia This way.
Click to expand...
Click to collapse
Thanks. I already did a factory reset and rooted successfully. For the next time I go into such trubl, can I get a recommendation about a powerfull app that backups all my apps and SETTINGS (except firmware) from phone internal filesystem to PC's HDD (not SD card because I'm out of space), either via network or via USB connection. I've heard about Titanium Backup which probably is able to backup all I need but I'm afraid it's not able store my backups to PC.
Bootloop on Xperia u
I use an Xperia u( rooted,locked bl) with cwm touch recovery.I installed the AOKP ICS rom for locked bl on my device. Ever since then, whenever I flash a file via cwm, even if I wipe cache and dalvik cache,phone goes into bootloop and I have to unplug and replug battery to get it to work.Please help
Hi!
I have a Xperia X10 Mini Pro (U20) with Stock Firmware (after recovery with "UpdateService" from SE).
I have installed CWM successfully with "CWMInstaller - Windows - v5".
When I try to install "MiniCM7-2.2.1-mimmi" (or 2.2.2) it says that I need a nAA-Kernel but successfully installs CM7.
When I do a reboot CWM says that "recovery is bad and has to be renewed". After that all I get is the white "Sony Ericsson" lettering (again with the option to start CWM when pressing the back button several times).
So I tried to follow this "Bootloader and kernel guide" and unlock my bootloader first using Flashtool. But when the phone restarts it "hangs" on the white "Sony Ericsson" lettering. When I try again, Flashtool tells me that it is not possible to unlock this bootloader.
My phone is produced 10W42 - could it really be that the ancient stock firmware is the only one which works?
All I want is a more modern and fast (lightweight) android version to use my old phone furthermore.
Thanks in advance for your advice and help!
greetz
davie
davie2000 said:
Hi!
I have a Xperia X10 Mini Pro (U20) with Stock Firmware (after recovery with "UpdateService" from SE).
I have installed CWM successfully with "CWMInstaller - Windows - v5".
When I try to install "MiniCM7-2.2.1-mimmi" (or 2.2.2) it says that I need a nAA-Kernel but successfully installs CM7.
When I do a reboot CWM says that "recovery is bad and has to be renewed". After that all I get is the white "Sony Ericsson" lettering (again with the option to start CWM when pressing the back button several times).
So I tried to follow this "Bootloader and kernel guide" and unlock my bootloader first using Flashtool. But when the phone restarts it "hangs" on the white "Sony Ericsson" lettering. When I try again, Flashtool tells me that it is not possible to unlock this bootloader.
My phone is produced 10W42 - could it really be that the ancient stock firmware is the only one which works?
All I want is a more modern and fast (lightweight) android version to use my old phone furthermore.
Thanks in advance for your advice and help!
greetz
davie
Click to expand...
Click to collapse
When you install CWM it is installed in the system part of the ROM. When you installed MiniCM7 it got wiped out, because MiniCM7 is for the nAa-kernel, and in that kernel CWM is built in. Which means it doesn't need to be in the MiniCM7 ROM. That's why you lost it.
And ofcourse it 'hangs' on the white SE lettering, because the ROM you installed does not work with the Sony Ericsson kernel.
You say you unlocked the bootloader, so why don't you flash the nAa-kernel?
Prepare flashtool to flash it, then attach the usb-cable and press home- and back-buttons together to force a restart. If the bootloader unlock was successful the flash will get through and after that, you'll have CWM back and you will continue to boot into the ROM too.
And be very careful not to flash the x10blrelock.ftf by accident, it will definitely break your phone. Best is to remove that from the flashtool/firmwares folder before you proceed.
SmG67 said:
...
You say you unlocked the bootloader, so why don't you flash the nAa-kernel?
Prepare flashtool to flash it, then attach the usb-cable and press home- and back-buttons together to force a restart. If the bootloader unlock was successful the flash will get through and after that, you'll have CWM back and you will continue to boot into the ROM too.
And be very careful not to flash the x10blrelock.ftf by accident, it will definitely break your phone. Best is to remove that from the flashtool/firmwares folder before you proceed.
Click to expand...
Click to collapse
Thanks for your answer, SmG67.
The problem is, that I have _tried_ to unlock the bootloader, but it did not finish. The "s1tool" still shows a capital R in the version ("RUNNING S1_EROM VER 'R8A029'") which means "not unlocked".
I also tried to install the kernel "U20_2.6.32.61-nAa-06.ftf" but this does not work as the bootloader is locked.
So can you give me a tip, how I could move on?
davie2000 said:
Thanks for your answer, SmG67.
The problem is, that I have _tried_ to unlock the bootloader, but it did not finish. The "s1tool" still shows a capital R in the version ("RUNNING S1_EROM VER 'R8A029'") which means "not unlocked".
I also tried to install the kernel "U20_2.6.32.61-nAa-06.ftf" but this does not work as the bootloader is locked.
So can you give me a tip, how I could move on?
Click to expand...
Click to collapse
You should not have proceeded to install the ROM in the first place if you didnt unlock it. Open SONY Update Service in PC, click repair and follow what they say. When you connect your phone to PC for repair, follow what SmG67 told you
Sent from my E10i using xda premium
pongnamu said:
You should not have proceeded to install the ROM in the first place if you didnt unlock it. Open SONY Update Service in PC, click repair and follow what they say. When you connect your phone to PC for repair, follow what SmG67 told you
Click to expand...
Click to collapse
Thanks for your reply, pongnamu!
I am unsettled now, so I want to make sure to do the right things:
I have "repaired" the phone using UpdateService and made the first setup - phone is now running and USB debugging is switched on.
Then I started flashtool and clicked on the flash-button (U20_2.6.32.61-nAa-06.ftf); followed the instructions but it quits working after phone restart with the following output:
Code:
13/006/2013 12:06:28 - INFO - <- This level is successfully initialized
13/006/2013 12:06:28 - INFO - Flashtool Version 0.9.12.1 built on 2013-06-04 22:50:00
13/006/2013 12:06:32 - INFO - Device disconnected
13/007/2013 12:07:27 - INFO - Selected U20 / nAa-06 / 2.6.32.61-nAa-06
13/007/2013 12:07:27 - INFO - Preparing files for flashing
13/007/2013 12:07:27 - INFO - Please connect your device into flashmode.
13/008/2013 12:08:09 - INFO - Device connected in flash mode
13/008/2013 12:08:09 - INFO - Opening device for R/W
13/008/2013 12:08:09 - INFO - Reading device information
13/008/2013 12:08:09 - INFO - Phone ready for flashmode operations.
13/008/2013 12:08:09 - INFO - Current device : U20i - CB511P8HKN - 1238-7168_R5B - 1235-3411_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
13/008/2013 12:08:09 - INFO - Start Flashing
13/008/2013 12:08:09 - INFO - Processing loader.sin
13/008/2013 12:08:09 - INFO - Checking header
13/008/2013 12:08:09 - INFO - Ending flash session
[COLOR="Red"]13/008/2013 12:08:09 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"[/COLOR]
13/008/2013 12:08:09 - INFO - Device connected in flash mode
[COLOR="Red"]13/008/2013 12:08:10 - ERROR - Error flashing. Aborted[/COLOR]
13/008/2013 12:08:11 - INFO - Device disconnected
13/008/2013 12:08:12 - INFO - Device connected in flash mode
13/008/2013 12:08:27 - INFO - Device disconnected
13/008/2013 12:08:35 - INFO - Device connected with USB debugging off
13/008/2013 12:08:35 - INFO - For 2011 devices line, be sure you are not in MTP mode
The phone is connected and shows an orange LED and the loading screen; nothing else happens.
Regarding to S1info the bootloader is still locked:
Code:
RUNNING S1_EROM VER "[COLOR="Red"]R[/COLOR]8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): U20i
SOFTWARE VERSION: 1235-3411_2.1.1.C.0.0
CUSTOM VERSION: 1238-7168_R5B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.C.0.0
SERIAL NO: xxxxxxxxxx
[COLOR="YellowGreen"]SEMC SIMLOCK CERTIFICATE[/COLOR]
Elapsed:12 secs.
Can you help me out again?
davie2000 said:
...
Can you help me out again?
Click to expand...
Click to collapse
Root the phone again with flashtool and then unlock the bootloader using flashtool. After that, you should be able to flash the kernel.
SmG67 said:
Root the phone again with flashtool and then unlock the bootloader using flashtool. After that, you should be able to flash the kernel.
Click to expand...
Click to collapse
Thanks to your reply, I was able to root the device with flashtool. Afterwards I successfully started Superuser and switched off the phone again.
While unlocking the bootloader (button BLU) with flashtool afterwards it gave me the following output:
Code:
13/037/2013 16:37:33 - INFO - <- This level is successfully initialized
13/037/2013 16:37:33 - INFO - Flashtool Version 0.9.12.1 built on 2013-06-04 22:50:00
13/037/2013 16:37:38 - INFO - Device disconnected
13/038/2013 16:38:54 - INFO - Device connected with USB debugging off
13/038/2013 16:38:54 - INFO - For 2011 devices line, be sure you are not in MTP mode
13/038/2013 16:38:54 - INFO - Device connected with USB debugging on
13/038/2013 16:38:55 - INFO - Connected device : SonyEricson X10 Mini Pro
13/038/2013 16:38:55 - INFO - Installed version of busybox : N/A
13/038/2013 16:38:55 - INFO - Android version : 2.1-update1 / kernel version : 2.6.29 / Build number : 2.1.1.C.0.0
13/039/2013 16:39:02 - INFO - Decrypting E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\PsNeuter\psneuter.tar.uue.enc to E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\PsNeuter\psneuter.tar.uue
13/039/2013 16:39:10 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\PsNeuter\psneuter.tar.uue to /data/local/tmp
13/039/2013 16:39:10 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\.\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
13/039/2013 16:39:10 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\subin\Superuser\su to /data/local/tmp/su
13/039/2013 16:39:11 - INFO - Pushing E:\Program Files (x86)\[HARDWARE]\[HANDY]\Flashtool\custom\root\subin\Superuser\Superuser.apk to /data/local/tmp/Superuser.apk
13/039/2013 16:39:11 - INFO - Running part1 of Root Exploit, please wait
13/039/2013 16:39:12 - INFO - Running rootit
13/039/2013 16:39:13 - INFO - Waiting for device. After 60secs, stop waiting will be forced
13/039/2013 16:39:13 - INFO - Device disconnected
13/039/2013 16:39:14 - INFO - Device connected with USB debugging on
13/039/2013 16:39:15 - INFO - Running part2 of Root Exploit
13/039/2013 16:39:15 - INFO - Running rootit2
13/039/2013 16:39:17 - INFO - Finished!.
13/039/2013 16:39:17 - INFO - Root should be available after reboot!
13/039/2013 16:39:17 - INFO - Device disconnected
13/040/2013 16:40:53 - INFO - Please connect your device into flashmode.
13/041/2013 16:41:58 - INFO - Device connected in flash mode
13/041/2013 16:41:58 - INFO - Opening device for R/W
13/041/2013 16:41:58 - INFO - Reading device information
13/041/2013 16:41:58 - INFO - Phone ready for flashmode operations.
13/041/2013 16:41:58 - INFO - Current device : U20i - CB511P8HKN - 1238-7168_R5B - 1235-3411_2.1.1.C.0.0 - WORLD-1-8_2.1.1.C.0.0
13/041/2013 16:41:58 - INFO - Processing loader.sin
13/041/2013 16:41:58 - INFO - Checking header
13/041/2013 16:41:58 - INFO - Flashing data
13/042/2013 16:42:00 - INFO - Loader : S1_Loader_Root_8e35 - Version : R4A045 / Boot version : R8A029 / Bootloader status : UNROOTABLE
13/042/2013 16:42:00 - INFO - Start Reading unit 00000851
13/042/2013 16:42:00 - INFO - Reading TA finished.
13/042/2013 16:42:00 - INFO - Ending flash session
13/042/2013 16:42:00 - INFO - Waiting for device to reboot
13/042/2013 16:42:00 - INFO - Waiting for device
13/042/2013 16:42:00 - INFO - Device connected in flash mode
13/042/2013 16:42:01 - INFO - Device disconnected
13/042/2013 16:42:03 - INFO - Device connected in flash mode
13/042/2013 16:42:22 - INFO - Device disconnected
13/042/2013 16:42:31 - INFO - Device connected with USB debugging off
13/042/2013 16:42:31 - INFO - For 2011 devices line, be sure you are not in MTP mode
There are no errors this time, but again nothing more happens: phone is loading and showing orange LED.
I am surprised of the log line saying that "Bootloader status is UNROOTABLE"?
btw: S1info still gives me a uppercase "R" for "not unlocked".
Can I proceed flashing the U20_2.6.32.61-nAa-06.ftf?
davie2000 said:
There are no errors this time, but again nothing more happens: phone is loading and showing orange LED.
I am surprised of the log line saying that "Bootloader status is UNROOTABLE"?
btw: S1info still gives me a uppercase "R" for "not unlocked".
Can I proceed flashing the U20_2.6.32.61-nAa-06.ftf?
Click to expand...
Click to collapse
That will fail since your bootloader is still locked. Not sure why flashtool failed to unlock it, but maybe you can try the manual method, as linked to in the opening post of the kernel.
SmG67 said:
That will fail since your bootloader is still locked. Not sure why flashtool failed to unlock it, but maybe you can try the manual method, as linked to in the opening post of the kernel.
Click to expand...
Click to collapse
You mean to unlock bootloader with "msm7227_semc.cmd" as stated in the "Bootloader and kernel guide" (from above)?
Because this always leads to:
Code:
process requires standard 2.x android firmware.
Drücken Sie eine beliebige Taste . . .
Getting ROOT rights.
* daemon not running. starting it now *
* daemon started successfully *
and the phones LED flashing red sometimes
Thats not the first device I am using custom firmware with, but this phone resists all my attempts.
Finally I managed to run CM7 on my phone following this german instruction.
My mistake was that during the flash process the phone has to be switched on normally and not to be connected in flashmode (pressing back button while plugging USB in).
Thanks for your suggestions and hints!