Hi guys,
I have problem with my X10i phone. In a row, I:
1. Installed stock rom from SEUS
2. Rooted device via flashtool
3. Unlocked bootloader via flashtool
4. Installed kernel (FeraKernel) via flashtool
5. Installed custom rom from CWM (Achotjan ROM)
6. AND then I've got an Wi-Fi issue, so I installed other kernel -> nAa 14. After that device won't boot AND I cannot:
- Flash it (in flashmode too)
- Boot
- Root/Shell Root (via SuperOneClick)
- Install stock soft via SEUS or PC Companion (repair in Companion won't do)
- Hard Reset by pressing keys (left, right and power)
- Unlock via ... Emma (Emma, right? From Sony) - It calls that I have blocked device
I can do nothing besides start in flashmode, which gives me nothing, cause I have problems flashing other kernel. Flashtool waits for device or gives me an RED COLOR Error: "SIN header verification error".
Can I do anything with this device or simply put it in a trash?
Where on earth did you get naa kernel for x10?
Sent from my Xperia X10 using xda app-developers app
AW: X10i won't boot - I tried everything (YES! Everything!)
can't you get into flashmode? maybe battery is empty... naa kernel is bullshiit forget it... search for thread "diXperia 7" avenger for 2.3.3 baseband+kernel or look in x10 development section for 1.6 .ftf file and try to flash those via flashtool. you dont need to power your device on to flash. it is thr only way (i know) to debrick a phone.
Greets
Sent from my X10i using xda app-developers app
epulrevo said:
Where on earth did you get naa kernel for x10?
Sent from my Xperia X10 using xda app-developers app
Click to expand...
Click to collapse
Do not ask me - I've read something wrong and ... and you see what it does...
can't you get into flashmode? maybe battery is empty... naa kernel is bullshiit forget it... search for thread "diXperia 7" avenger for 2.3.3 baseband+kernel or look in x10 development section for 1.6 .ftf file and try to flash those via flashtool. you dont need to power your device on to flash. it is thr only way (i know) to debrick a phone.
Greets
Click to expand...
Click to collapse
I tried this: http://forum.xda-developers.com/showthread.php?t=2145994 - without flashing mode it won't start
PS. I CAN GET INTO FLASHMODE. But it gives me nothing, cause I have errors or my PC can't recognize phone after flashing by nAa kernel...
EDIT: I tried with generic rom - still error: "SIN verification header error"
Proxxx23 said:
Do not ask me - I've read something wrong and ... and you see what it does...
I tried this: http://forum.xda-developers.com/showthread.php?t=2145994 - without flashing mode it won't start
PS. I CAN GET INTO FLASHMODE. But it gives me nothing, cause I have errors or my PC can't recognize phone after flashing by nAa kernel...
EDIT: I tried with generic rom - still error: "SIN verification header error"
Click to expand...
Click to collapse
Flash back ferakernel.
Sent from my Xperia X10i using xda app-developers app
AW: X10i won't boot - I tried everything (YES! Everything!)
epulrevo said:
Flash back ferakernel.
Sent from my Xperia X10i using xda app-developers app
Click to expand...
Click to collapse
if you get into flashmode there must be something that you can flash
and report back if it works
Greets
Sent from my X10i using xda app-developers app
No - I can flash NOTHING. My phone is not recognized by SEUS, so I think there's an error related to that header from an error in flashtool
AW: X10i won't boot - I tried everything (YES! Everything!)
in kernel. it is just: you het your kernel, put ut in firmwares folder, go to flashtool, choose it and plug your device while pressing back button.
if it doesnt work then you are reallx fcked.
Greets
Sent from my X10i using xda app-developers app
Proxxx23 said:
No - I can flash NOTHING. My phone is not recognized by SEUS, so I think there's an error related to that header from an error in flashtool
Click to expand...
Click to collapse
Search for any rom img .ftf . Its was the whole rom+kernel to be flash using flashtool. I've done this.
Sent from my Xperia X10i using xda app-developers app
in kernel. it is just: you het your kernel, put ut in firmwares folder, go to flashtool, choose it and plug your device while pressing back button.
if it doesnt work then you are reallx fcked.
Greets
Click to expand...
Click to collapse
I WROTE - I can flash nothing using flashtool. Grrr...
Search for any rom img .ftf . Its was the whole rom+kernel to be flash using flashtool. I've done this.
Click to expand...
Click to collapse
Where? ROM+Kernel in one ftf file?
Proxxx23 said:
I WROTE - I can flash nothing using flashtool. Grrr...
Where? ROM+Kernel in one ftf file?
Click to expand...
Click to collapse
Yup, rom + kernel in ftf file. Search it yourself. I've done it with x8 and I found the rom+kernel ftf.
Sent from my Xperia X10 using xda app-developers app
try this http://forum.xda-developers.com/showthread.php?t=1400384
Just don't forget to check "no final verification".
No mater what I do, I see:
24/054/2013 20:54:15 - INFO - Device loader has not been identified. Using the one from the bundle
24/054/2013 20:54:15 - INFO - Checking header
24/054/2013 20:54:15 - INFO - Ending flash session
24/054/2013 20:54:15 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Proxxx23 said:
No mater what I do, I see:
24/054/2013 20:54:15 - INFO - Device loader has not been identified. Using the one from the bundle
24/054/2013 20:54:15 - INFO - Checking header
24/054/2013 20:54:15 - INFO - Ending flash session
24/054/2013 20:54:15 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
Click to expand...
Click to collapse
I got exact the same error trying to flash .ftf from flashtool.
19/017/2012 03:17:46 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
For me this was because I did not have an unlocked bootloader.
I spent at least a whole day trying to resolve the problem as months earlier I had an unlocked bootloader and everything worked.
For me I resolved the problem by unlocking the bootloader...'again'.
Have you run S1 Tool and verified that you have an unlocked bootloader at this time?
LOADER VERSION: "R4A024" means a locked bootloader. If it a lower-case "r" then you're fine and you have an unlocked bootloader.
If you get SEMC SIMLOCK CERTIFICATE at the end of the S1 Tool information output then at least there is still something readable in the boot image of your phone.
It is odd though, when I had a locked bootloader on my XPERIA X10i I was still able to install a SEUS firmware upgrade.
Information about unlocking a bootloader can be found here. Tutorial: Rooting, Bootloader Unlocking and Updating
Dr Goodvibes said:
I got exact the same error trying to flash .ftf from flashtool.
19/017/2012 03:17:46 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
For me this was because I did not have an unlocked bootloader.
I spent at least a whole day trying to resolve the problem as months earlier I had an unlocked bootloader and everything worked.
For me I resolved the problem by unlocking the bootloader...'again'.
Have you run S1 Tool and verified that you have an unlocked bootloader at this time?
LOADER VERSION: "R4A024" means a locked bootloader. If it a lower-case "r" then you're fine and you have an unlocked bootloader.
If you get SEMC SIMLOCK CERTIFICATE at the end of the S1 Tool information output then at least there is still something readable in the boot image of your phone.
It is odd though, when I had a locked bootloader on my XPERIA X10i I was still able to install a SEUS firmware upgrade.
Information about unlocking a bootloader can be found here. Tutorial: Rooting, Bootloader Unlocking and Updating
Click to expand...
Click to collapse
I have unlocked bootloader earlier, but maybe I have it locked again. How can I unlock bootloader without device connected (by turning it on)? I can only start it in flash mode, which doesn't allow me to unlock bootloader in flashtool. Also I cannot update firmware using SEUS
AW: X10i won't boot - I tried everything (YES! Everything!)
I just had the same or at least a similar problem (sunday it happened) and solved it by flashing the 1.6 rom and the 2.3.3 only kernel +baseband, first found in dev section, second in dixperia 7 thread and then updated via seus. It didn't work at first try but now i have the working stock rom and cannot root anymore. If you try this please tell us if you can root afterwards.
And try to boot 1.6 first - it is nice and i wanna know if it works for you. You can look in my profile to find the thread i created with details.
Greets
Sent from my X10i using xda app-developers app
Proxxx23 said:
I have unlocked bootloader earlier, but maybe I have it locked again. How can I unlock bootloader without device connected (by turning it on)? I can only start it in flash mode, which doesn't allow me to unlock bootloader in flashtool. Also I cannot update firmware using SEUS
Click to expand...
Click to collapse
And you've tried S1 Tool to see what it returns?
If you can't view the information results or the results indicate your XPERIA X10i is in a state that does not support an unlocked bootloader (due to corruption) then at least you have a documented state at which your phone can or can't operate.
If the XPERIA X10i can't load ANY firmware, then you'll have to start analyzing the low level boot code to find out what is corrupted and how bad it is. S1 Tool is an easy info display to a least be able to say, "OK I can get a return information display from S1 Tool" and I have posted the output so people can better understand the situation.
If you can not install firmware via Sony Ericsson Update Service(SEUS), PC Companion or Flashtool 'flashmode' using a generic GB 2.3.3 ftf.
Then you're limiting your options. You still have flashtool 'fastboot mode' BUT indications are that you HAVE to have an unlocked bootloader for it to work.
Have you tried flashing a 'STOCK' GB 2.3.3 ROM via flashtool flashmode? [Completed]X10 Stock Firmware Collection
Have you placed the xxx.ftf file to be flashed in /flashtool/firmwares/ folder?
Does your XPERIA X10i have drivers installed on the PC so that the USB connection is established and recognized?
If the USB connection is not recognized, have you run the driver install from /flashtool/drivers ?
Dr Goodvibes said:
And you've tried S1 Tool to see what it returns?
If you can't view the information results or the results indicate your XPERIA X10i is in a state that does not support an unlocked bootloader (due to corruption) then at least you have a documented state at which your phone can or can't operate.
If the XPERIA X10i can't load ANY firmware, then you'll have to start analyzing the low level boot code to find out what is corrupted and how bad it is. S1 Tool is an easy info display to a least be able to say, "OK I can get a return information display from S1 Tool" and I have posted the output so people can better understand the situation.
If you can not install firmware via Sony Ericsson Update Service(SEUS), PC Companion or Flashtool 'flashmode' using a generic GB 2.3.3 ftf.
Then you're limiting your options. You still have flashtool 'fastboot mode' BUT indications are that you HAVE to have an unlocked bootloader for it to work.
Have you tried flashing a 'STOCK' GB 2.3.3 ROM via flashtool flashmode? [Completed]X10 Stock Firmware Collection
Have you placed the xxx.ftf file to be flashed in /flashtool/firmwares/ folder?
Does your XPERIA X10i have drivers installed on the PC so that the USB connection is established and recognized?
If the USB connection is not recognized, have you run the driver install from /flashtool/drivers ?
Click to expand...
Click to collapse
Ok, so:
1. I tried to flash stocking ROM - I Have an error with SIN header.
2. Yes, I placed file in given directory
3. Yes, I have drivers on my PC (Gordon's Gate too) - PC has been recognizing a phone before. Now I have only "device connected in flash mode" information.
4. SEMC Debrand doesn't work.
S1 Tool:
RUNNING S1_EROM VER "r8A033"
SOFTWARE AID: FFFF
LOADER AID: DEAD
FATAL ERROR [ SECURITY_CLASS, SIN_header_verification_failed ]
error while uploading HDR block
LOADER NOT STARTED
Elapsed:8 secs.
Just for reference my rooted and unlocked bootloader XPERIA X10i returns.
Welcome to S1 tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A033"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "r4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: 9999999999
SEMC SIMLOCK CERTIFICATE
Elapsed:28 secs.
The error status your S1 Tool returns sounds ominous.
SOFTWARE AID: FFFF
LOADER AID: DEAD
The fact that the phone and the PC are communicating is good. Now you just have to wait for some smart person that knows the boot code your phone is missing. I've got nothing.
Dr Goodvibes said:
Just for reference my rooted and unlocked bootloader XPERIA X10i returns.
Welcome to S1 tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A033"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "002C/00B3"
LOADER VERSION: "r4A024"
MODEL (from GDFS): X10i
SOFTWARE VERSION: 1227-4612_3.0.1.G.0.75
CUSTOM VERSION: 1241-1846_R1C
FILESYSTEM VERSION: WORLD-1-4-8_3.0.1.G.0.75
SERIAL NO: 9999999999
SEMC SIMLOCK CERTIFICATE
Elapsed:28 secs.
The error status your S1 Tool returns sounds ominous.
SOFTWARE AID: FFFF
LOADER AID: DEAD
The fact that the phone and the PC are communicating is good. Now you just have to wait for some smart person that knows the boot code your phone is missing. I've got nothing.
Click to expand...
Click to collapse
So You don't know how to restore this code?
Related
I have a X10minipro (U20a) with the M76XX-TSNCJOLYM-53404015 baseband, latest (2.1.1.A.0.6) firmware - just updated/repaired using PC Companion.
I just tried to flash Cm7.1.0 RC1 FXP028's kernel in this phone (first step of the install guide, http://forum.xda-developers.com/showthread.php?t=1212949), but it won't boot. It doesn't even display any logo at all (no FXP logo, nor Sony Ericsson logo). After pressing the power button, I can feel the usual little vibration it makes when powering up. After that, the phone gives no other life sign - the screen just keeps black forever.
I'm not sure, but when the usb cable is connected, it appears that the phone enters into some sort of loop in and out of flash mode. The green LED blinks shortly and I can see the usb device being detected as the flash mode device (eg. on lsusb) for a short period of time. And I haven't pressed the back button at all.
Of course, flashing back the stock kernel unbricks the phone.
The bootloader was unlocked using msm7227_semc. Just to be sure it was unlocked correctly, I flashed D4Kernel v1.2 (http://forum.xda-developers.com/showthread.php?t=1254202), and it worked like a charm. So the bootloader appears to be working well.
Does anybody have an idea of what is going on? Maybe I was expected to flash another version of the baseband?
If you got FXP kernel to work in your phone, please tell me if you can see any difference between your phone and mine (versions, etc.)
I found it strange that U20_CUSTOM.ftf, when opened using flashtool, shows "E10" in the column "Device". But perhaps this is just a typo.
Additional info (s1tool output):
Code:
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "r4A060"
MODEL (from GDFS): U20a
SOFTWARE VERSION: 1235-3408_2.0.A.0.504
CUSTOM VERSION: 1238-8213_R6B
FILESYSTEM VERSION: WORLD-1-2-5_2.1.1.A.0.6
SERIAL NO: BY9008UWWE
SEMC SIMLOCK CERTIFICATE
Thank you
Have you discovered the problem yet ? I have a similiar problem and how can you reflash the stock kernel if it doesn't even turn on or connect with computer ?
thotypous said:
I have a X10minipro (U20a) with the M76XX-TSNCJOLYM-53404015 baseband, latest (2.1.1.A.0.6) firmware - just updated/repaired using PC Companion.
I just tried to flash Cm7.1.0 RC1 FXP028's kernel in this phone (first step of the install guide, http://forum.xda-developers.com/showthread.php?t=1212949), but it won't boot. It doesn't even display any logo at all (no FXP logo, nor Sony Ericsson logo). After pressing the power button, I can feel the usual little vibration it makes when powering up. After that, the phone gives no other life sign - the screen just keeps black forever.
I'm not sure, but when the usb cable is connected, it appears that the phone enters into some sort of loop in and out of flash mode. The green LED blinks shortly and I can see the usb device being detected as the flash mode device (eg. on lsusb) for a short period of time. And I haven't pressed the back button at all.
Of course, flashing back the stock kernel unbricks the phone.
The bootloader was unlocked using msm7227_semc. Just to be sure it was unlocked correctly, I flashed D4Kernel v1.2 (http://forum.xda-developers.com/showthread.php?t=1254202), and it worked like a charm. So the bootloader appears to be working well.
Does anybody have an idea of what is going on? Maybe I was expected to flash another version of the baseband?
If you got FXP kernel to work in your phone, please tell me if you can see any difference between your phone and mine (versions, etc.)
I found it strange that U20_CUSTOM.ftf, when opened using flashtool, shows "E10" in the column "Device". But perhaps this is just a typo.
Additional info (s1tool output):
Code:
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "r4A060"
MODEL (from GDFS): U20a
SOFTWARE VERSION: 1235-3408_2.0.A.0.504
CUSTOM VERSION: 1238-8213_R6B
FILESYSTEM VERSION: WORLD-1-2-5_2.1.1.A.0.6
SERIAL NO: BY9008UWWE
SEMC SIMLOCK CERTIFICATE
Thank you
Click to expand...
Click to collapse
The kernel that comes with CM 7.1 is broken, you need to use a older version of FXP, there's one in the mini pro dev and flash the just the kernel but I can't find the kernel any were for the mini pro, the mirrors come up as X8. I've been told that it still has bugs.
Sent from my U20i using xda premium
henzx said:
Have you discovered the problem yet ? I have a similiar problem and how can you reflash the stock kernel if it doesn't even turn on or connect with computer ?
Click to expand...
Click to collapse
As danlivesey said, the custom kernel from FXP is broken. When I posted this, nobody had complained yet (people complained only when they released FXP030), so I thought I was doing something wrong.
To reflash the stock kernel, download "X10 mini pro (U20) stock kernel" from this thread: http://forum.xda-developers.com/showthread.php?t=1254225
Then use flashtool to flash the ftf file. You should be able to put your phone in flash mode. If your are not able, probably it is stuck frozen trying to boot, then just remove the battery and insert it again and follow the procedure again (keeping the back button pressed and inserting the USB cable).
Hi, i've tried two ways to unlock bootloader, by Flashtool and Xrecovery.
With flashtool I didn't get the message "Successfully applied unlock" but the phone rebooted anyway.
I triede pressing several times, the back button when the sonnyericson letters appear, tried always pressing and nothing.
Can anyone help me.
I can supply the flashtool log if necessary.
Thx
Anyone??? Do I have to do it all over again? What's the best way to re-do it?
heinz_pt said:
Anyone??? Do I have to do it all over again? What's the best way to re-do it?
Click to expand...
Click to collapse
Mate what is the exact problem?? You not getting into xrecovery or your bootloader in unlocked even after using flashtool??
Sent from my U20i using xda premium
The exact problem is I can't acess the bootlooder, when the phone is restarting.
I tried by both metod's: flashtool and xrecovery.
heinz_pt said:
The exact problem is I can't acess the bootlooder, when the phone is restarting.
I tried by both metod's: flashtool and xrecovery.
Click to expand...
Click to collapse
you mean you cannot access the x-recovery right..?? try the tool in my signature n install the CWM recovery from it.. After installing CWM recovery with the tool reboot your phone.. press the back button when sony ericsson logo comes and your done.. you can now flash Custom ROM's with CWM recovery..
Also, double check which baseband you have. It should end in x015 (x being the rest of the number). If not then you'll need to flash to the correct version. My minipro wouldnt enter xrecovery/cwm until it had been flashed to it, like you the backbutton did nothing and I couldnt find a solution for a few days.
My phone came shipped with android 1.6 and previous baseband. If you look around the forum for basebands you should be able to find it. Flash with flashtool.
Sent from my U20i using Tapatalk
Having the problem it iscoolbutton.ocx, tried the fix and still the sameproblem. My baseband ends in 15. When I run the Flashtool it gives this message:
"05/042/2012 20:42:03 - INFO - Start Flashing
05/042/2012 20:42:03 - INFO - Flashing loader
05/042/2012 20:42:05 - INFO - Loader version : r4A060 / Bootloader status : ROOTED
05/042/2012 20:42:05 - INFO - Flashing kernel.sin
05/042/2012 20:42:07 - INFO - Flashing finished.
05/042/2012 20:42:07 - INFO - Please wait. Phone will reboot
05/042/2012 20:42:07 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
05/042/2012 20:42:07 - INFO - Device connected in flash mode
05/042/2012 20:42:09 - INFO - Device disconnected"
And then phone restarts. Any ideas?
I've done it. Installed the E10_nAa-10_2.6.29.6-nAa-10 kernell and worked. Now the problem is does detect my SD Card.
Nothing that a Format to my SD card didn't solve.
heinz_pt said:
Nothing that a Format to my SD card didn't solve.
Click to expand...
Click to collapse
The point is the nAa kernel n Mini cm7 2.8 by nobodyatall together work perfect.. This usb moutn feature is included with thr ROM.. So flash the ROM it'l be fine..
Sent from my U20i using xda premium
quick question if I may, I tried every single way to bootloader unlock my x10 mini and when I try I get a message in cmd about a daemon that doesn't start, then it says that it started succesfully and it does nothing else after that, those were my last intends to bootloader unlock, before I got messages about daemon as well,but multiple times and in the end said that it couldn't start daemon, I can't bootloader unlock my x10 mini please help!!!
Try installing the JDK and the android SDK. I unlocked my bl using the original way and those were required. Things normally work best on our phones with them
Sent from my X10 Mini Pro using XDA App
x10man said:
Try installing the JDK and the android SDK. I unlocked my bl using the original way and those were required. Things normally work best on our phones with them
Sent from my X10 Mini Pro using XDA App
Click to expand...
Click to collapse
I have the android SDK and JDK what should I do and how? could you please help?please...
SOLUTION FOR THOSE WHO COULDN'T(like myself)
[email protected] said:
quick question if I may, I tried every single way to bootloader unlock my x10 mini and when I try I get a message in cmd about a daemon that doesn't start, then it says that it started succesfully and it does nothing else after that, those were my last intends to bootloader unlock, before I got messages about daemon as well,but multiple times and in the end said that it couldn't start daemon, I can't bootloader unlock my x10 mini please help!!!
Click to expand...
Click to collapse
I found the solution for my problem, I hope it helps somebody else.
steps:
1. download Flashtool-0.5.0.0beta (ask me if you want a link)
2. download s1tools (version doesn't matter)
3. install flashtool, and restart your computer (don't install gordon's gate yet0
4. plug in your turned on x10 mini(it needs to be in usb debug mode as well)
5. wait for flashtool to recognize it
6. on the menu click on plugins,unlock boot loader(or something similar),run
7.you will get some response like this:
Root Access Allowed
INFO - Searching Xperia....
ERROR - Please plug you device in flash mode
you will get it multiple times, even a popup window indicating how to put your phone in flash mode.
8. unplug your phone and turn it off
9. now go to the directory where you installed falsh tool,drivers folder, and install gg(gg setupxxxx.exe)
10. now connect your device in flash mode(turned off, connect to pc while you hold the back button)
11. your phone will restart a couple times, just wait.
12. in my case the process ended when it rebooted in recovery mode(i had cwm recovery put in already),I manually rebooted, and voila !!!
BOOTLOADER UNLOCKED !!!!
13. run s1 tool and double check, you know, the cap letter and stuff, it shouldn't be cap anymore
x10man said:
Try installing the JDK and the android SDK. I unlocked my bl using the original way and those were required. Things normally work best on our phones with them
Sent from my X10 Mini Pro using XDA App
Click to expand...
Click to collapse
What is the "original way"?
http://forum.xda-developers.com/showthread.php?t=1254225 that is the first way of unlocking before it was implemented into flashtool. I used it when I unlocked mine
Sent from my X10 Mini Pro using XDA App
I'm a complete noob, all i ever did was flashing a ROM, so please don't shoot me...
So i started by reflashing 2.3.3 stock firmware. I downloaded flashtool and installed it on my pc (0.7.1.0). I rooted the phone and installed xRecovery. So now i wanted to unlock my bootloader to flash FeraLab 17.
I installed the s1 tool to check if my phone is good to be unlocked, and it says it's fine. And now i go back to flashtool to start the unlocking: plugins> bootloader unlock> run.
So all is fine till i get to this point. When i unplug my phone and power it off and then press the back button and plug it back in it says the following:
06/052/2012 16:52:00 - INFO - Device connected with USB debugging on
06/052/2012 16:52:00 - INFO - Connected device : X10
06/052/2012 16:52:00 - INFO - Installed version of busybox : BusyBox v1.19.0 (2011-08-14 23:46:58 CDT) multi-call binary.
06/052/2012 16:52:00 - INFO - Android version : 2.3.3 / kernel version : 2.6.29-00054-g5f01537
06/052/2012 16:52:11 - INFO - Root Access Allowed
06/054/2012 16:54:47 - INFO - Please connect your device into flashmode.
06/054/2012 16:54:57 - INFO - Device disconnected
06/055/2012 16:55:25 - INFO - Device connected in flash mode
06/055/2012 16:55:25 - INFO - Opening device for R/W
06/055/2012 16:55:25 - INFO - Reading device information
06/055/2012 16:55:25 - INFO - Phone ready for flashmode operations.
06/055/2012 16:55:25 - INFO - Flashing loader
06/055/2012 16:55:25 - INFO - Ending flash session
06/055/2012 16:55:25 - WARN - Cancelled
06/055/2012 16:55:25 - INFO - Device connected in flash mode
06/055/2012 16:55:27 - INFO - Device disconnected
06/055/2012 16:55:28 - INFO - Device connected in flash mode
Click to expand...
Click to collapse
and the following thing is that my phone shows a charching battery icon. It still works but i don't seem to be able to unlock the bootloader..
Does anyone have a clue what the problem is here?
KingRafox said:
I'm a complete noob, all i ever did was flashing a ROM, so please don't shoot me...
So i started by reflashing 2.3.3 stock firmware. I downloaded flashtool and installed it on my pc (0.7.1.0). I rooted the phone and installed xRecovery. So now i wanted to unlock my bootloader to flash FeraLab 17.
I installed the s1 tool to check if my phone is good to be unlocked, and it says it's fine. And now i go back to flashtool to start the unlocking: plugins> bootloader unlock> run.
So all is fine till i get to this point. When i unplug my phone and power it off and then press the back button and plug it back in it says the following:
and the following thing is that my phone shows a charching battery icon. It still works but i don't seem to be able to unlock the bootloader..
Does anyone have a clue what the problem is here?
Click to expand...
Click to collapse
Better use this method. Works great if u are not drunk.
http://forum.xda-developers.com/showthread.php?t=1254087
Sent from my LT26i using xda premium
Thanks, but this one doesnt work because the links for de azuzu upgrade and downgrade files are down ... i don't know how i can do this now...
king-iyokan said:
Better use this method. Works great if u are not drunk.
http://forum.xda-developers.com/showthread.php?t=1254087
Sent from my LT26i using xda premium
Click to expand...
Click to collapse
I have the same problem KingRafox. And i've tried several method including the link posted above.
Please make sure you have enabled usb-debugging in your current rom before starting with this!!
flash the azuzu kernel downgrade ftf with flashtool
disconnect usb cable, press power button until phone vibrates shortly and immidiatly connect the usb cable again (it is supposed to be stuck at SE logo)
start the batch file for unlocking bootloader, cause it says press any button before it starts, it won't start unlocking until you press any button
now wait until flashtool recognizes your x10 (if flashtool doesn't do anything, check third post please! thx)
close flashtool and then press any button in the cmd window that the unlocking process starts (please close flashtool, instead the bl unlock cmd and flashtool are constantly killing and restarting adb!!) <--- failed!!
after unlocking is finish you have to flash azuzu kernel upgrade
now power on phone to check if the phone is starting after the unlock (if you are using a custom kernel yet with the bypass method and get stuck in a bootloop enter xrecovery and clear dalvik-cache, then your phone should boot up again fine)
power off phone and flash dooms ck v05-fs with flashtool
now flash the wifi modules for dooms ck with recovery. (atm the update.zips are for xrec, but for sure please always check dooms kernel-thread if there is anything changed)
power on phone again and if everything is right, read the line under that one
WOOOHOOO!!! Here you are with unlocked bootloader, custom kernel directly loaded AND without reflashing any rom, means you have kept your current installation
If you aren't seeing the se logo at turning on phone, but directly the custom kernel logo, you were succesfully. If you want to enter xrecovery you have to spam the back button now if the xperia logo appears instead of the se logo.
Click to expand...
Click to collapse
I've followed these instruction but it failed when running the unlock file (qsd8250_semc.cmd). It says that it failed to get root access or something. (I'll post the log later on).
I also flashed to stock 2.1, downgrade the kernel and tried using x10 Bootloader Unlock Tool (with the big "Unlock Bootloader" button). But failed.
If anyone have any other methods or any suggestion, i'm all open.
Thanks for replying.
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.
Guys,
I encountered the same situation when I using the least version of Flashtool (0.7.1.0), it always display - WARN - Cancelled
So I roll back to use Flashtool (v0.6.8.0) then plugins> bootloader unlock> run, it works
i'm using FlashTool_0.2.9.1-GBready_root_xRec, flash without any error. Try find it. .
Guys
Make sure your SEMC SIM LOCK status supported by doom kernel (forgot about status lock or unlock cause I tried only 1 times and get lucky)
from my expirence.. some many devices will be locked for the networks and it will give you EMERGENCY CALL and you OUT OF LUCK!
Sent from my Xperia X10 using xda premium
What the hell, I'm still having the same "disconnect" problem as in the original post.
Let me ask you all if I'm missing something here:
1) I have a new, Vodafone-locked X10 mini Pro.
2) I downloaded Flashtool latest
3) I used it to root the phone (ok, it worked)
4) I use the Plugin menu, then Unlock Bootloader, then you know the rest.
Am i missing something here?
Should I change kernel or install a recovery first?
If only every device was as easy as the SGS's...
Thanks guys
try this
Phk said:
What the hell, I'm still having the same "disconnect" problem as in the original post.
Let me ask you all if I'm missing something here:
1) I have a new, Vodafone-locked X10 mini Pro.
2) I downloaded Flashtool latest
3) I used it to root the phone (ok, it worked)
4) I use the Plugin menu, then Unlock Bootloader, then you know the rest.
Am i missing something here?
Should I change kernel or install a recovery first?
If only every device was as easy as the SGS's...
Thanks guys
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1759264
Devin-J said:
http://forum.xda-developers.com/showthread.php?t=1759264
Click to expand...
Click to collapse
Thanks DJ.
I've managed to Unlock the bootloader still yesterday, i don't know why or how, but it worked.
The difference from my previous post is that I started the process with the phone already in flash mode, then reboot, then flash mode again, and then the Flashtool did everything (even saying Bootloader: UNROOTABLE)
My difficulty after that was to flash CWM. It's funny but that next step is not explained anywhere.
Are these the correct procedures?
Stock Phone > Flashtool:Root > Flashtool:Unlock Bootloader > CWM (???) > Flash Image > Flashtool:Kernel
It's strange why:
1) There is no CWM to flash from Flashtool
2) The kernel cannot be flashed from CWM
CWM recovery is built in to kernels like doomlords v6 multi recovery or FXP kernel. You will have to flash a CWM based kernel to get CWM recovery
Sent from my X10i using xda premium
There should be an install recovery button in ft which allows u to install cwm or xrecovery
Sent from my GT-I9300 using xda app-developers app
Or flashing KCernel v3, got CWM recovery and Xrecovery in one.
Whitefang
Anyone help plz..
I have x10 mini pro..
I'm trying to unlock its bootloader but flashtool doesn't show any plugin..(he plugin menu is empty
What to do??
thnx in advnce
google for ominuserver. pay the 15$..
mkhawx said:
Anyone help plz..
I have x10 mini pro..
I'm trying to unlock its bootloader but flashtool doesn't show any plugin..(he plugin menu is empty
What to do??
thnx in advnce
Click to expand...
Click to collapse
If the same as x10 it blanked out as u not meet unlock requirements. U would have to check with someone else who has mini pro as not sure if it different
Sent from my GT-I9300 using xda app-developers app
Same Pb with Xperia X10
mkhawx said:
Anyone help plz..
I have x10 mini pro..
I'm trying to unlock its bootloader but flashtool doesn't show any plugin..(he plugin menu is empty
What to do??
thnx in advnce
Click to expand...
Click to collapse
Hi all,
I am having the same issue on my Xperia X10i.
When I connect my phone and run Flashtool 0.9.9, the plugin menu is empty. Any idea ?
I am trying to unlock my BL without success so far...
http://forum.xda-developers.com/showthread.php?p=17494049
teddymild said:
http://forum.xda-developers.com/showthread.php?p=17494049
Click to expand...
Click to collapse
Thanks for you help.
I have tried to enter flash mode and press RESTORE as it says. I receive a "NOTHING TO RESTORE" message...
Do you know why Flashtool does not show anyting in Plugin menu ?
hello guys
here is my issue....
I wanted to install gb or ics or jb on my x10mini (e10i)
my baseband is : M76XX-TSNCjoLYM-53404015
firmware : 2.1-update1
android v : 2.1.1.A.0.6.
i successfully rooted my phone and unlocked the bootloader using flashtools 0.9.8.0.
but my problem is when ever i try to flash custom kernel i get this error
Code:
ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Failed to init erase";
i tried all custom kernel including nAa-13, nAa-14, nAa-ics,nAa-jb. everything fails and i get my phone semi bricked with phone reboots and all i get is white screen and LED glows White.
then i use SEUS to flash back to stock rom. i did this for almost 20times so far everytime it fails....
any help?
Confirm again with stool that if ur bl unlocked or locked.
Vınce said:
Confirm again with stool that if ur bl unlocked or locked.
Click to expand...
Click to collapse
yes it is unlocked. i used flashtool 0.9.8
alienwrz said:
yes it is unlocked. i used flashtool 0.9.8
Click to expand...
Click to collapse
You do use flashmode, and not fastboot i hope?
SmG67 said:
You do use flashmode, and not fastboot i hope?
Click to expand...
Click to collapse
ofcourse flashmode mate
unlock bootloader
I didn't know you can unlock the bootloader with flashtool. I used another tool (attachment)
Just connect your phone with debugging mode turned on and open "msm7227_semc" from the zip and follow the instructions.
This worked perfectly for me. After finished, just reboot the phone, then its unlocked. Then you can install a custom kernel with flashtool.
pls tell me if it has worked
TheDiddyhamster said:
I didn't know you can unlock the bootloader with flashtool. I used another tool (attachment)
Just connect your phone with debugging mode turned on and open "msm7227_semc" from the zip and follow the instructions.
This worked perfectly for me. After finished, just reboot the phone, then its unlocked. Then you can install a custom kernel with flashtool.
pls tell me if it has worked
Click to expand...
Click to collapse
There are actually three different methods to unlock the bootloader, which one to use depends on the status of your phone. Flashtool does actually do a decent job in deciding which method (including the one you mention here) to use. It's in the plugins menu.
I would like to ask alienwrz to post a slightly more extensive part of the flashtool output, and maybe the output of the identify-button in S1Tool.
SmG67 said:
There are actually three different methods to unlock the bootloader, which one to use depends on the status of your phone. Flashtool does actually do a decent job in deciding which method (including the one you mention here) to use. It's in the plugins menu.
I would like to ask alienwrz to post a slightly more extensive part of the flashtool output, and maybe the output of the identify-button in S1Tool.
Click to expand...
Click to collapse
ok i will look for verification of BL status via s1tool. i will post the screens asap. i will try the method given by above person aswell
alienwrz said:
ok i will look for verification of BL status via s1tool. i will post the screens asap. i will try the method given by above person aswell
Click to expand...
Click to collapse
Code:
Welcome to S1 tool.
That is small and crippled subset of SETOOL2 service tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "r4A060"
MODEL (from GDFS): E10i
SOFTWARE VERSION: 1235-3408_2.1.1.A.0.6
CUSTOM VERSION: 1237-8595_R4B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511S1RTD
SEMC SIMLOCK CERTIFICATE
Elapsed:57 secs.
so it is unlocked. even then i cant flash it via flashtool in flashmode. any help?
alienwrz said:
Code:
Welcome to S1 tool.
That is small and crippled subset of SETOOL2 service tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Mini,E15 Xperia X8,U20 Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
ST18 Xperia RAY,ST15 Xperia Mini,SK17 Xperia Mini Pro
PRESS AND HOLD "Volume Down" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "r8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "r4A060"
MODEL (from GDFS): E10i
SOFTWARE VERSION: 1235-3408_2.1.1.A.0.6
CUSTOM VERSION: 1237-8595_R4B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511S1RTD
SEMC SIMLOCK CERTIFICATE
Elapsed:57 secs.
so it is unlocked. even then i cant flash it via flashtool in flashmode. any help?
Click to expand...
Click to collapse
Where did you get the kernels from (the actual links may be useful) and what sizes are they?
(You did unlock the bootloader, so it's not directly a problem with flashing per se, because unlocking involves flashing a new loader to the phone, maybe your anti-virus could be interfering with flashing the actual kernels)
SmG67 said:
Where did you get the kernels from (the actual links may be useful) and what sizes are they?
(You did unlock the bootloader, so it's not directly a problem with flashing per se, because unlocking involves flashing a new loader to the phone, maybe your anti-virus could be interfering with flashing the actual kernels)
Click to expand...
Click to collapse
Code:
https://code.google.com/p/minicm/downloads/list
e10_13,14 etc. my phone is robyn.
and yeah i will try with av off my av is essential from MS
SmG67 said:
Where did you get the kernels from (the actual links may be useful) and what sizes are they?
(You did unlock the bootloader, so it's not directly a problem with flashing per se, because unlocking involves flashing a new loader to the phone, maybe your anti-virus could be interfering with flashing the actual kernels)
Click to expand...
Click to collapse
i did with av off.... it still gives same error
EDIT: i started flashing kernel from release 1 (i.e) E10_nAa-01_2.6.29.6-nAa-01.ftf till E10_nAa-11_2.6.29.6-nAa-11.ftf but i couldn't flash from 12-14 and ics, jb.... any help?
I was using CM7 on my X10i, and i wanted to update to CM10, too bad i flashed the phone with wrong kernel and brick it. However, the phone is recovered now, i rooted it, installed xRecovery, but when i try to unlock the bootloader in order to flash the kernel i got this:
Welcome to S1 tool.
TO CONNECT NEXT PHONES
X10 Xperia,E10 Xperia Mini,E15 Xperia X8,U20 Xperia Mini Pro
LT15 Xperia ARC,MT15 Xperia NEO,R800 Xperia PLAY
PRESS AND HOLD "BACK" BUTTON...
PLEASE ATTACH TURNED OFF PHONE NOW
RUNNING S1_EROM VER "R8A029"
SOFTWARE AID: 0001
LOADER AID: 0001
FLASH ID: "0020/00BC"
LOADER VERSION: "R4A045"
MODEL (from GDFS): E10i
SOFTWARE VERSION: 1235-3408_2.1.1.A.0.16
CUSTOM VERSION: 1237-1709_R14B
FILESYSTEM VERSION: CHINA-1-8_2.1.1.A.0.16
SERIAL NO: BX902BT4AW
NOT RECOGNIZED SIMLOCK CERTIFICATE
MAYBE YOU SHOULD UNLOCK PHONE BY SETOOL2 ?
Elapsed:41 secs.
Im scared to run msm7227_semc.cmd because of this NOT RECOGNIZED SIMLOCK CERTIFICATE. Before the brick there was SEMC_SIMLOCK CERTIFICATE.
However i try to flash the kernel via Flashtool but i got this:
21/057/2013 16:57:26 - INFO - Flashtool Version 0.9.10.1 built on 2013-01-09 19:49:47
21/057/2013 16:57:26 - INFO - You can drag and drop ftf files here to start flashing them
21/057/2013 16:57:31 - INFO - Device disconnected
21/057/2013 16:57:45 - INFO - Selected E10_2.6.32.60-nAa-05.ftf
21/057/2013 16:57:45 - INFO - Preparing files for flashing
21/057/2013 16:57:45 - INFO - Please connect your device into flashmode.
21/059/2013 16:59:51 - INFO - Device connected in flash mode
21/059/2013 16:59:51 - INFO - Opening device for R/W
21/059/2013 16:59:51 - INFO - Reading device information
21/059/2013 16:59:51 - INFO - Phone ready for flashmode operations.
21/059/2013 16:59:51 - INFO - Current device : E10i - BX902BT4AW - 1237-1709_R14B - 1235-3408_2.1.1.A.0.16 - CHINA-1-8_2.1.1.A.0.16
21/059/2013 16:59:51 - INFO - Start Flashing
21/059/2013 16:59:51 - INFO - Processing loader
21/059/2013 16:59:51 - INFO - Checking header
21/059/2013 16:59:51 - INFO - Ending flash session
21/059/2013 16:59:51 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
21/059/2013 16:59:51 - ERROR - Error flashing. Aborted
21/059/2013 16:59:52 - INFO - Device connected in flash mode
21/059/2013 16:59:53 - INFO - Device disconnected
Should i risk with msm7227_semc.cmd? Manifaction date is 10W26 according the phone sticker and im 100% sure that i unlocked it once before the bricking, but i dont know after this jteg repair, give me some advice please.
kumboom said:
I was using CM7 on my X10i, and i wanted to update to CM10, too bad i flashed the phone with wrong kernel and brick it. However, the phone is recovered now, i rooted it, installed xRecovery, but when i try to unlock the bootloader in order to flash the kernel i got this:
...
Should i risk with msm7227_semc.cmd? Manifaction date is 10W26 according the phone sticker and im 100% sure that i unlocked it once before the bricking, but i dont know after this jteg repair, give me some advice please.
Click to expand...
Click to collapse
Trying to unlock the bootloader of your device won't break it as bad as flashing the wrong kernel did. The only thing that can happen is that you lose the ability to connect to your providers network.
If you unlock the bootloader, boot up the phone and see if you still have signal. If that's ok you can go and flash the kernel.
If you don't have a signal, use S1tool's restore button to relock the bootloader again, usually your signal will come back that way.
And don't forget to delete the x10blrelock.ftf from your flashtool folder if you haven't already.
Ive tried msm7227_semc.cmd and the phone is bricked again
kumboom said:
Ive tried msm7227_semc.cmd and the phone is bricked again
Click to expand...
Click to collapse
What happened?
SmG67 said:
What happened?
Click to expand...
Click to collapse
S1 Tool said "NOT RECOGNIZED SIMLOCK CERTIFICATE", but i started msm7227_semc.cmd anyway - it says "access denied" few times and the phone was restarted. I had signal and everything so i decided the unlocking was successful. I turned off the phone in order to flash the kernel, but when i started the Flashtool and it says "Hold back and plug the cabel" nothing happened (no green light, no screen, no nothing) than i tried to turn on or recharge the phone and nothing again. Bricked like before.
I guess the guy from the service was not using jtag repair machine, but replace the main chip, so thats why the phone act like it was manifactured after 11W21. However i didnt want to use the stock kernel so i had to try
Im separeted between U and Sola now
kumboom said:
S1 Tool said "NOT RECOGNIZED SIMLOCK CERTIFICATE", but i started msm7227_semc.cmd anyway - it says "access denied" few times and the phone was restarted. I had signal and everything so i decided the unlocking was successful. I turned off the phone in order to flash the kernel, but when i started the Flashtool and it says "Hold back and plug the cabel" nothing happened (no green light, no screen, no nothing) than i tried to turn on or recharge the phone and nothing again. Bricked like before.
I guess the guy from the service was not using jtag repair machine, but replace the main chip, so thats why the phone act like it was manifactured after 11W21. However i didnt want to use the stock kernel so i had to try
Im separeted between U and Sola now
Click to expand...
Click to collapse
I guess you forgot to root the phone before starting the unlock-process, that's why you got access denied errors.
I'm not sure what you flashed though, but if you did anything else than the x10blrelock.ftf it should have failed.
SmG67 said:
I guess you forgot to root the phone before starting the unlock-process, that's why you got access denied errors.
I'm not sure what you flashed though, but if you did anything else than the x10blrelock.ftf it should have failed.
Click to expand...
Click to collapse
No, Im pretty sure that the phone was rooted. I did it with SuperOne click - i check after and i had Superuser app in the menu. After that i installed Root explorer, granted superuser permissions and copy files of xRecovery at /system/bin. If the phone wasnt rooted i wasnt able to do that.
But, if u are using e10i ... U should need 11w04 like mine or a little bit higher, or it will hard brick it.