[Q] problem rooting ray 4.1.B.0.587 - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

Hi
I updated my xperia ray to ics with pc companion. = . So i got a downgraded kernel and tried to flash it but i keep getting this error in the flash tool and the rooting program does not work because it says the file system is read only when i try it afterwards.
08/005/2012 23:05:39 - INFO - Flashtool Version 0.9.9.0 built on 2012-11-13 22:53:30 08/005/2012 23:05:39 - INFO - You can drag and drop ftf files here to start flashing them 08/005/2012 23:05:49 - INFO - Device disconnected 08/005/2012 23:05:56 - INFO - Device connected with USB debugging off 08/005/2012 23:05:56 - INFO - For 2011 devices line, be sure you are not in MTP mode 08/005/2012 23:05:57 - INFO - Device connected with USB debugging on 08/005/2012 23:05:58 - INFO - Connected device : ST18 08/005/2012 23:05:59 - INFO - Installed version of busybox : BusyBox v1.18.5 (2011-07-18 07:43:28 PDT) multi-call binary. 08/005/2012 23:05:59 - INFO - Android version : 4.0.4 / kernel version
2.6.32.9-perf / Build number : 4.1.B.0.587 08/006/2012 23:06:35 - INFO - Selected ST18i_4.1.A.0.562_kernel.ftf 08/006/2012 23:06:35 - INFO - Preparing files for flashing 08/006/2012 23:06:35 - INFO - Please connect your device into flashmode. 08/006/2012 23:06:39 - INFO - Device disconnected 08/007/2012 23:07:18 - INFO - Device connected in flash mode 08/007/2012 23:07:18 - INFO - Opening device for R/W 08/007/2012 23:07:19 - INFO - Start Flashing 08/007/2012 23:07:19 - INFO - Processing loader 08/007/2012 23:07:19 - INFO - Checking header 08/007/2012 23:07:19 - INFO - Ending flash session 08/007/2012 23:07:19 - ERROR -08/007/2012 23:07:19 - ERROR - Error flashing.
Aborted 08/007/2012 23:07:19 - INFO - Device connected in flash mode
Can anyone help me please? Thank you

Mod please delete this comment..this comment was made when this was in general for mini,mini pro and active

But your device is already rooted?! The log says busybox is installed, so it should be rooted...
Sent from my SK17i running Android 4.2.1

mihahn said:
But your device is already rooted?! The log says busybox is installed, so it should be rooted...
Sent from my SK17i running Android 4.2.1
Click to expand...
Click to collapse
I ran root checker basic from google play it says I am not rooted. I tried to use connect bot to login and do su root but it says su not found. It also cannot find whoami it says command does not exist.
I doubt I am rooted.

para15000 said:
I ran root checker basic from google play it says I am not rooted. I tried to use connect bot to login and do su root but it says su not found. It also cannot find whoami it says command does not exist.
I doubt I am rooted.
Click to expand...
Click to collapse
Okay I think I would downgrade to gingerbread and update again using the local-prop method

mihahn said:
Okay I think I would downgrade to gingerbread and update again using the local-prop method
Click to expand...
Click to collapse
how do I do that exactly?

para15000 said:
how do I do that exactly?
Click to expand...
Click to collapse
Read the sticked guides, there's how to root .431 and in this tutorial it's explained :good:

I managed to root it by flashing the vulnerable kernel same as in the tutorials.
The problem was that my SD card was read-only(all folders on it).
I just plugged in the phone(via USB to my computer).
Selected all the data on the SD(Ctrl+A) right click properties and changed from read-only to full access.
Then everything started working especially the doomlord exploit.

Related

[Q] Bootloader unlock issues.. Help needed !!

I have ran SEUS and restored my X10 to Stock 2.3.3
Then I rooted the phone using the newest version of flashtool
Then ran the plugin/bootloader unlock option in flashtool
Then when I reconnect the phone in flash mode, The phone does not enter flash mode and flashtool displays that the phone has been removed and the phone starts up to the Sony Ericsson screen.
Kindly help me and advice on how I can achieve bootloader unlock.
U are doing right thing pal it just the usb connection is a bit poor on our phone. Remove battery for 10-20 seconds, reimsert battery, wait bout a munute, then connect on flash mode. May take couple attempts but the way u doing it is correct
Sent from my X10i using XDA
Thank you for the comment. I'll keep trying, finger crossed
I can't seem to get mine past 2.1...... tried to flash after root and all and after I learned the weird recovery process. Flashed one that was safe for locked and unlocked BL but it loops. Even flashed some initD file that the OP of that rom said to flash right after and it is still nil.......
Sent from my SGH-I777 using XDA Premium App
No luck
Must have tried at least a hundred times.. Still no luck with mine.. Anymore suggestions ? Anyone ?
Try just plugging it in and not holding back button. Does that work?
Sent from my X10i using XDA
Are u trying to flash a 2.3.3 rom on 2.1? If u have u will have issues. If u did above grab flashtool and flash
global generic 2.3.3 firmware. Then flash the rom.
Sent from my X10i using XDA
Gave up on fit. I'm sure that its something small but, I'm doing this pro-bono for a friend of mine and its killing me. I've flashed other phones before and nothing this weird. Ill stick to the phones that are one big ass button flash and fix lime my sgs2 and the HTC inspire I used to have. Thanks again for all the help and in site that you all have provided.
Sent from my SGH-I777 using XDA Premium App
Hi.. Well, I still havn't been able to unlock the bootloader.. i don't know how many attempts I've made.. .. Anyways.. Im posting the log from flashtool.. Is this of any use to help me solve my problem ?
04/006/2012 20:06:39 - INFO - <- This level is successfully initialized
04/006/2012 20:06:40 - INFO - Flashtool Version 0.6.8.0 built on 2012-02-26 19:26:25
04/006/2012 20:06:40 - INFO - You can drag and drop ftf files here to start flashing them
04/006/2012 20:06:47 - INFO - Device disconnected
04/007/2012 20:07:16 - INFO - Device connected with USB debugging off
04/007/2012 20:07:16 - INFO - For 2011 devices line, be sure you are not in MTP mode
04/007/2012 20:07:17 - INFO - Device connected with USB debugging on
04/007/2012 20:07:18 - INFO - Connected device : X10
04/007/2012 20:07:19 - INFO - Installed version of busybox : BusyBox v1.19.3-Stericson (2011-11-01 20:22:18 CDT) multi-call binary.
04/007/2012 20:07:19 - INFO - Android version : 2.3.4 / kernel version : 2.6.29-00054-g5f01537
04/007/2012 20:07:21 - INFO - Root Access Allowed
04/007/2012 20:07:24 - INFO - Please connect your device into flashmode.
04/007/2012 20:07:27 - INFO - Device disconnected
04/007/2012 20:07:50 - INFO - Device connected in flash mode
04/007/2012 20:07:50 - INFO - Opening device for R/W
04/007/2012 20:07:50 - WARN - Cancelled
04/007/2012 20:07:51 - INFO - Device connected in flash mode
04/008/2012 20:08:53 - INFO - Device disconnected
04/008/2012 20:08:56 - INFO - Device connected with USB debugging off
04/008/2012 20:08:56 - INFO - For 2011 devices line, be sure you are not in MTP mode
Click to expand...
Click to collapse
Guys...please help me on this.
I have the same problem as Vsak here. This is my flashtools log.
06/044/2012 07:44:13 - INFO - <- This level is successfully initialized
06/044/2012 07:44:13 - INFO - Flashtool Version 0.7.1.0 built on 2012-05-01 22:07:23
06/044/2012 07:44:13 - INFO - You can drag and drop ftf files here to start flashing them
06/044/2012 07:44:18 - INFO - Device connected with USB debugging on
06/044/2012 07:44:18 - INFO - Connected device : X10
06/044/2012 07:44:18 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
06/044/2012 07:44:18 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
06/044/2012 07:44:18 - INFO - Root Access Allowed
06/044/2012 07:44:28 - INFO - Please connect your device into flashmode.
06/044/2012 07:44:33 - INFO - Device disconnected
06/045/2012 07:45:02 - INFO - Device connected in flash mode
06/045/2012 07:45:02 - INFO - Opening device for R/W
06/045/2012 07:45:02 - INFO - Reading device information
06/045/2012 07:45:02 - INFO - Phone ready for flashmode operations.
06/045/2012 07:45:02 - INFO - Flashing loader
06/045/2012 07:45:03 - INFO - Ending flash session
06/045/2012 07:45:03 - WARN - Cancelled
06/045/2012 07:45:03 - INFO - Device connected in flash mode
06/045/2012 07:45:04 - INFO - Device disconnected
06/045/2012 07:45:05 - INFO - Device connected in flash mode
06/045/2012 07:45:15 - INFO - Device disconnected
Click to expand...
Click to collapse
I've done exactly as the steps here : http://forum.xda-developers.com/showthread.php?p=19685019#post19685019
Please anyone?
bayanster said:
Guys...please help me on this.
I have the same problem as Vsak here. This is my flashtools log.
I've done exactly as the steps here : http://forum.xda-developers.com/showthread.php?p=19685019#post19685019
Please anyone?
Click to expand...
Click to collapse
When i flash a kernel, i click to flash, i choose the kernel and wait the screen shows to conect in flash mode, if i try before choose the kernel it fail too, so try it.
Thanks for the reply.
There was no problem when flashing kernel but when I want to unlock the bootloader, it gave me the log below (I'm using latest flashtool 0.7.1.0) :
06/045/2012 07:45:02 - INFO - Flashing loader
06/045/2012 07:45:03 - INFO - Ending flash session
06/045/2012 07:45:03 - WARN - Cancelled
When I switch off the phone, and connect it back with flash mode (pushing the back button).
I tried several method to unlock bootloader but failed. I've even flashed flashed to stock 2.1, flashed the downgrade kernel and tried to unlock via X10 Bootloader Unlock Tool 0.1.1 (old method, i know). I've check my phone and it is good for unlocking (via s1tool).
Can anyone suggest any method I can try?
bayanster said:
Thanks for the reply.
There was no problem when flashing kernel but when I want to unlock the bootloader, it gave me the log below (I'm using latest flashtool 0.7.1.0) :
06/045/2012 07:45:02 - INFO - Flashing loader
06/045/2012 07:45:03 - INFO - Ending flash session
06/045/2012 07:45:03 - WARN - Cancelled
When I switch off the phone, and connect it back with flash mode (pushing the back button).
I tried several method to unlock bootloader but failed. I've even flashed flashed to stock 2.1, flashed the downgrade kernel and tried to unlock via X10 Bootloader Unlock Tool 0.1.1 (old method, i know). I've check my phone and it is good for unlocking (via s1tool).
Can anyone suggest any method I can try?
Click to expand...
Click to collapse
Which version of flashtool are you using? get the most recent one.
I had a similar problem unlocking th bl for a friend too and it got stuck at that part bcz i was using an older version of flashtool
I'm using flashtool 0.7.1.0, the latest one, i think.
I've flashed, root and install recovery with no error.
Except unlocking the bootloader..
Guys,
I've finally unlocked my bootloader using "The proper method".
The mistake (i think) was, I was on generic 2.3.3 when I use this method.
I flashed back to generic 2.1 and ran the unlock tool. When finished I check back with S1tool, my device show "r" and not "R" Yeaa...
Note that, I failed to unlock my bootloader when I was on 2.1 and 2.3.3 using latest Flashtool.
Thanks guys.

Cannot Unlock BL [DONE IT]

Solved!!
Im on Achotjan_Stock_Remplacement_Rom | X10i_2.3.3_6.0.B.0.743_V2.0
http://forum.xda-developers.com/showthread.php?t=1690148
Here is the log from flashtool:
11/051/2012 23:51:06 - INFO - <- This level is successfully initialized
11/051/2012 23:51:06 - INFO - Flashtool Version 0.8.6.0 built on 2012-06-13 08:08:54
11/051/2012 23:51:06 - INFO - You can drag and drop ftf files here to start flashing them
11/051/2012 23:51:11 - INFO - Device disconnected
11/051/2012 23:51:14 - INFO - Device connected with USB debugging off
11/051/2012 23:51:14 - INFO - For 2011 devices line, be sure you are not in MTP mode
11/051/2012 23:51:15 - INFO - Device connected with USB debugging on
11/051/2012 23:51:15 - INFO - Connected device : X10
11/051/2012 23:51:15 - INFO - Installed version of busybox : BusyBox v1.19.3-Stericson (2011-11-01 20:22:18 CDT) multi-call binary.
11/051/2012 23:51:15 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
11/051/2012 23:51:16 - INFO - Root Access Allowed
11/051/2012 23:51:19 - INFO - Please connect your device into flashmode.
11/051/2012 23:51:24 - INFO - Device disconnected
11/051/2012 23:51:40 - INFO - Device connected in flash mode
11/051/2012 23:51:40 - INFO - Opening device for R/W
11/051/2012 23:51:40 - INFO - Reading device information
11/051/2012 23:51:40 - INFO - Phone ready for flashmode operations.
11/051/2012 23:51:40 - INFO - Flashing loader
11/051/2012 23:51:46 - INFO - Loader : S1_Loader_Root_f851 - Version : R4A024 / Bootloader status : UNROOTABLE
11/051/2012 23:51:46 - INFO - Start Reading property
11/051/2012 23:51:46 - INFO - Reading TA finished.
11/051/2012 23:51:46 - INFO - Ending flash session
11/051/2012 23:51:46 - INFO - Found semcSL
11/051/2012 23:51:46 - INFO - You can now unplug and turn on device, then plug it again
11/051/2012 23:51:46 - INFO - Waiting for device
11/051/2012 23:51:46 - INFO - Device connected in flash mode
11/051/2012 23:51:48 - INFO - Device disconnected
11/051/2012 23:51:49 - INFO - Device connected in flash mode
11/052/2012 23:52:03 - INFO - Device disconnected
11/052/2012 23:52:19 - INFO - Device connected with USB debugging off
11/052/2012 23:52:19 - INFO - For 2011 devices line, be sure you are not in MTP mode
11/052/2012 23:52:21 - INFO - Device disconnected
11/052/2012 23:52:23 - INFO - Device connected with USB debugging on
11/052/2012 23:52:34 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\qsd8250\qsd8250bootwrite_semcSL to /data/local/tmp
11/052/2012 23:52:34 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\qsd8250\mapper_2.6.29-00054-g5f01537.ko to /data/local/tmp
11/052/2012 23:52:34 - INFO - Pushing C:\Flashtool\custom\features\UnlockBL\files\qsd8250\fixPart to /data/local/tmp
11/052/2012 23:52:34 - INFO - Running runfixPart as root thru sysrun
11/052/2012 23:52:34 - ERROR - Cannot apply fixPart. Aborting
11/052/2012 23:52:35 - INFO - Running runClean as root thru sysrun
someone can help me?
Thanx, Itamar
How did you unlock your bootloader?
Im not at a pc so cant check your link or give you one (edge network is fun)
Google this "xperia x10 unlocking bootloader"
First result xda how to
Make sure you test what files you need
Read it very carefully!
I doubt whatever rom you use makes a difference
Im sorry that i could not provide anymore help the guide just says it all i suppose!
Good luck!
EDIT; incase you do not want to unlock boot loader then use roms for locked bootloader!!
If not sorry you just didnt provide that much info
Sent from my X10i using xda premium
fterger the
@Itamar2
You can see bootloader unlocking threads here (bootloader bypass) and here (bootloader unlocking).
hope it helps... cheers :fingers-crossed:
Need Stock kernel...
Need stock kernel... you may need this
http://www.sonymobile.com/gb/tools/update-service/
Root via FlashTool 0.8.6
Unlock bootloader plugin will be available under plugin in FlashTool 0.8.6
Thanks.
Iv read all of the "how to unlock BL" guides on XDA, and i did it thrwo flashtool, i also added the log and it is defrent then the one on the guide.
Any solutions?
Sorry for my bad english XD
Sent from my X10a using xda app-developers app
Identify your simlock certificate status. download S1tool here.
- open S1tool and click "DO JOB" on the right.
- turn off your phone, and connect USB cable while pressing BACK button (right button) of your phone.
- check your phone's simlock certificate. if identified as "NOT RECOGNIZED", you can follow the_laser's bootloader bypass method.
How to...
- download qsd8250.7z (courtesy of the_laser).
- flash your phone with standard/generic 2.1 firmware. (PLEASE DO MAKE A BACK-UP BEFORE FLASHING)
- extract qsd8250.7z and run "qsd8250_semc.cmd" from that folder.
- turn on the phone, enable USB debugging and connect the USB cable. just follow the command. you'll see message below
Code:
process requires standard 2.x android firmware.
Press any key to continue . . .
Getting ROOT rights.
1464 KB/s (585731 bytes in 0.390s)
error: protocol fault (no status)
Waiting ...
Removing NAND MPU restrictions via SEMC backdoor. Permanent. Require ROOT rights.
192 KB/s (3087 bytes in 0.015s)
success
Waiting ...
Getting ROOT rights.
Waiting ...
Writing patched semcboot. Two step process
First, we need get access to semcboot area
504 KB/s (8064 bytes in 0.015s)
Second, we need to write semcboot ;)
1531 KB/s (588236 bytes in 0.375s)
successfully wrote 0001ff80
Press any key to continue . . .
if you had the same message... you had bypassed the bootloader. it's now unlocked.
- to make sure it's already been unlocked, runt S1tool again.
- the phone should be running S1_EROM ver "r8A022" (with uncapitalized letter 'r')
NOTE: This procedure is an excerpt from the_laser's thread above. I hope I had made it easier for you. This method worked on mine.
CREDITS:
- the_laser
- 9Lukas5
- Androxyde
The s1tool says i can unlock my BL....
Thts why i tride flashtool...
Sent from my X10i using xda app-developers app
try this cmd programe......... http://forum.xda-developers.com/showthread.php?t=1759264
lol i have to admiit, even though i made the video, i forgot the names of the softwares. i think it is obvious from the vid. just google it after watching
Itamar2 said:
The s1tool says i can unlock my BL....
Thts why i tride flashtool...
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
try to flash standard/generic 2.1 firmware and unlock BL thru flashtool then.
optionally, you can do the bypass method via "qsd8250_semc.cmd" if flashtool failed.
Where can I get generic 2.1?
Sent from my X10i using xda app-developers app
Itamar2 said:
Where can I get generic 2.1?
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
found this on Androxyde's thread provided above.
X10i Generic 2.1update1 build 2.1.A.0.435
Thanks, and do i flash it with xrecovery? And after the unlock (with 2.1) how do i flash fxp CM7.2?
Sent from my X10i using xda app-developers app
helpful tips all about flashtool functions -> http://forum.xda-developers.com/showpost.php?p=19684846&postcount=2
flashing guide CM7.2 -> http://forum.xda-developers.com/showpost.php?p=17998666&postcount=12446
NOTE: after unlocking BL, you should upgrade to 2.3 firmware to be able to flash CM7.2
BordenG said:
helpful tips all about flashtool functions -> http://forum.xda-developers.com/showpost.php?p=19684846&postcount=2
flashing guide CM7.2 -> http://forum.xda-developers.com/showpost.php?p=17998666&postcount=12446
NOTE: after unlocking BL, you should upgrade to 2.3 firmware to be able to flash CM7.2
Click to expand...
Click to collapse
How to flash the 2.1 firmware ? ( the links have no info abote that... )
How to upgrade and keep the unlock ?
Sent from my X10i using xda app-developers app
Itamar2 said:
How to flash the 2.1 firmware ? ( the links have no info abote that... )
How to upgrade and keep the unlock ?
Sent from my X10i using xda app-developers app
Click to expand...
Click to collapse
you'll use flashtool for flashing .ftf firmwares.
use recovery for flashing .zip file. ie roms, add-ons etc.
CM7.2 should be flashed with CWM recovery, which you could also install via flashtool.
just refer in the thread provided above. you'll get used to it..
unlocked BL should never get locked unless you do so.
ganbatte!!!
Ok, but how do I flash with flashtool - is it like flashing kernel?
And to update I do so with SE PC-companion?
Sent from my X10i using xda app-developers app
yes. same process as what you did in your first post.
and make sure you already had generic 2.1 and 2.3 downloaded and copied into C:\Flashtool\firmwares folder. you should see identical files below when you open flashtool, clicked on thunder icon (utmost left button) and chosen flashmode.
then connect your phone in flashmode when prompted (phone turned off, pressing back button while connecting USB cable).
RECAP:
- flash generic 2.1
- root, if not rooted (you can hover your mouse on every icon to identify each)
- unlock bootloader (clicking Plugins-> bootloader ->run)
- install recovery (cross icon), you can install both 0.3 and CWM5. if you want to.
- flash generic 2.3
- flash FXP kernel
on this part, I assumed you already had your CM7.2 rom (.zip) on your SD card.
- boot into CWM recovery (via flashtool or pressing volume down button when blue lights on during kernel boot)
- in CWM recovery mode, make a factory reset. format system in mounts and storage.
- mount data, cache, system, sd-ext (you should see "unmount data" and so on...)
- install .zip on sd-card, and choose the rom in .zip file.... wait for installation.
- reboot, if everything goes right...congrats! you already had a custom rom installed... :good:

[Q] lww stuck after "SONY" Logo

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??

Solved [Q] U20 (10W42) root ok, CWM ok, kernel nok, ...

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!

[Q] X10 MP Unrootable? :(

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.

Categories

Resources