Related
http://support.setool.net/showthread.php?3-UPDATES-AND-NEWS&p=74240#post74240
read down to Oct 27 news update.
This should kinda serve as a general warning to those who want to unlock their bootloader, though it is not fully confirmed as of yet
Please check production date of your model before any attempt
oh thats so scary. My phone is E16i and has a date of 11W34.
I was able to unlock and relock bootloader for so many times... does it mean that my phone will not get a bad luck on that?
whats resurruction cable method?
Sent from my E15i using xda premium
vientito said:
read down to Oct 27 news update.
This should kinda serve as a general warning to those who want to unlock their bootloader, though it is not fully confirmed as of yet
Please check production date of your model before any attempt
Click to expand...
Click to collapse
To spare everyone the trouble, here's the text of the post in question:
seems most of lately produced msm7227-based phones have chipset with FIXED security hole, which used to altbypass unlock.
(that is not 100% confirmed, we only have few reports, however better be warned)
such phones will DIE after successful unlock procedure.
such dead phones CAN NOT be recovered. ( perhaps, jtag can fix that, perhaps, qualcomm fixed jtag security hole too )
there is NO WAY to determine if phone has fixed chipset or chipset with security hole.
the ONLY safe way is to use unlock by resurrection cables.
if phone can be connected and booted by resurrection cables, phone is safe to unlock.
if phone can not be booted by resurrection cables, phone has fixed chipset and could not be unlocked.
you have been warned.
get and use resurrection cables.
update:
e16 phone with manufacture date 11w38 affected, i think we should care about phones which produced after 11w26
maliceomalice said:
whats resurruction cable method?
Click to expand...
Click to collapse
Seems to be a special designed interface to access the UART recovery mode on a hard bricked device (very low-level stuff, comes right after JTAG'ing). See this YouTube link.
If anyone of you ever followed the awesome Samsung unbrick posts by Adam Outler you should have an idea what UART access means and therefore should have a clue about what the "recovery cable" device is able to do.
The only thing that doesn't add up ... the recovery cable video doesn't show any interface for the W8/E16.
so does it mean newer phones cant unlock bootloader? so my w8 i bought from last week got brick during unlocking bootloader might be a victim of this new security hole? o ya...why must SE do this? to prevent us from bootloading?
....... I got my x8 12 months ago and I successfuly unlocked my bootloader. But what your basically saying is that newer phones can't be unlocked.. like the unlock tool to new phones is a deathtrap? Woooo. Watch out new buyers
sent from my x8 running gingerdx
Simply put, SE has a lot of stakes to protect.
wilbso said:
But what your basically saying is that newer phones can't be unlocked.. like the unlock tool to new phones is a deathtrap?
Click to expand...
Click to collapse
That's the point in case. If the phone is within the specified date of manufacturing you can successfully unlock the bootloader, but after you did the stunt and reboot the device it's basically hard bricked beyond "do it yourself at home" repair possibilities.
The best shot you then have left is to find a repair shop having a RIFF Box (JTAG) or the aforementioned Resurrection Cable (UART Recover) to breathe new life into the device.
However, it's at least good to know that this pithole is there (though I find it fascinating that they kept on fixing up the hardware flaws - or hardware based security holes - in the chipset). EDIT: Might also explain why some people experience weird problems with custom ROMs the majority isn't able to reproduce.
Mine's a 11W28 unlocked my bootloader and it's not bricked.......
B.Jay said:
That's the point in case. If the phone is within the specified date of manufacturing you can successfully unlock the bootloader, but after you did the stunt and reboot the device it's basically hard bricked beyond "do it yourself at home" repair possibilities.
The best shot you then have left is to find a repair shop having a RIFF Box (JTAG) or the aforementioned Resurrection Cable (UART Recover) to breathe new life into the device.
However, it's at least good to know that this pithole is there (though I find it fascinating that they kept on fixing up the hardware flaws - or hardware based security holes - in the chipset). EDIT: Might also explain why some people experience weird problems with custom ROMs the majority isn't able to reproduce.
Click to expand...
Click to collapse
Mine must have been within the specified date cuz like I said before
I unlocked it successfuly, its works perfect. But yeah, thanks for the explanation
sent from my x8 running gingerdx
wilbso said:
....... I got my x8 12 months ago and I successfuly unlocked my bootloader.
Click to expand...
Click to collapse
wilbso said:
Mine must have been within the specified date cuz like I said before I unlocked it successfuly, its works perfect.
Click to expand...
Click to collapse
If you got yours 12 MONTHS ago ... No, yours is NOT in the specified date!
11w26 (and onwards) seem to be problematic
11w38 (and onwards) seem to be sure hard brick
2011, wilbso - NOT 2010 (hint: we're still in 2011 for a few more days)
B.Jay said:
If you got yours 12 MONTHS ago ... No, yours is NOT in the specified date!
11w26 (and onwards) seem to be problematic
11w38 (and onwards) seem to be sure hard brick
2011, wilbso - NOT 2010 (hint: we're still in 2011 for a few more days)
Click to expand...
Click to collapse
Just cuz I got it 12 months ago dosnt mean the model was created then.... on he back of my x8 it says 10w47, that specific anough for ya?
sent from my x8 running gingerdx
Plus my phone is an e15 not an e16 as mentioned in earlier post that's its e16 not e15 phones that willl have the problem
sent from my x8 running gingerdx
amnher said:
oh thats so scary. My phone is E16i and has a date of 11W34.
I was able to unlock and relock bootloader for so many times... does it mean that my phone will not get a bad luck on that?
Click to expand...
Click to collapse
Mine with 11w33,, not bricked..., and always change with many custom kernel....
can explain me with it...?
@wilbso:
U mad, bro?
donny_mey said:
Mine with 11w33,, not bricked..., and always change with many custom kernel....
can explain me with it...?
Click to expand...
Click to collapse
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
B.Jay said:
@wilbso:
U mad, bro?
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
Click to expand...
Click to collapse
i realy sure about that but in 11w38 maybe killed with this act....
but i'm not sure for this,,,, or this a promotion tools from SE tool, and we must buy if we want to unlock that...
it's right...???
donny_mey said:
but i'm not sure for this,,,, or this a promotion tools from SE tool, and we must buy if we want to unlock that...
Click to expand...
Click to collapse
This is not a promotion from SE or any other company. The fact behind this is...
...that if you have a hard bricked W8 you need the "resurrection cable" thingy to _maybe_ restore the firmware on the phone (as there's no intel on how the "resurrection" is possible on the aforementioned models it's yet another guessing based on what has been written all over the place (read: "oberservation"), therefore the "maybe").
...that the safest way to attempt a bootloader unlock on said phones is to do it through the "resurrection cable" as only there you can tell IF it will work or not.
The only "promotion" in all of it is the heads-up on that piece of hardware a do-it-yourself-at-home technician (or privateer wanting to specialize in unbricking dead phones) may need - and that's all.
B.Jay said:
@wilbso:
U mad, bro? Is the 10w47 within the specified date. Because I unlocked bootloader without trouble
Well, as we can only speculate on the Engrish post TheLaser made on the site from where the info comes from ...
W8/E16 phones within the range of 11W26 through 11W37 seem to be problematic. I interpret this as "there's some hardware fix though it can be worked around in software". If this now refers to flashtool or the replacement bootloader binary is up for anyone's guess.
11W38 and onwards seems to be a candidate for a sure kill after unlocking the bootloader. I interpret this as "the new bootloader binary that gets installed doesn't manage to start up because various 'security holes' have been fixed in the hardware therefore rendering the code defunct". That would at least explain why such hard bricks show no sign of life anymore at all (no LED, no screen, no nothing).
If you find a better theory or a better detailed description written in non-Engrish type ahead ...
Click to expand...
Click to collapse
Sorry.... is 10w47 in the specific date? Cuz I managed to unlock bootloader and flash custom kernel. In about to flash another soon just need your oponion
sent from my x8 running gingerdx
wilbso said:
is 10w47 in the specific date? Cuz I managed to unlock bootloader and flash custom kernel. In about to flash another soon just need your oponion
Click to expand...
Click to collapse
10W## through 11W25 should be considered safe
(where 10W## means "from start of production all through 2010")
11W26 through 11W37 could turn out to be problematic
(though I'm not sure what Laser means by that exactly)
11W38 and newer are supposed to hard brick
("no sign of life" .. no LED, no vibrate, no screen, no flash-mode connection)
Note that this seems to apply to the W8 E16 AND X8 E15 as well ... in one of tohno's threads we have a hard bricked X8 (11W43) mentioned.
I'm still trying to make head and tails out of the random info, but I think it's safe to say that one should better have a look at the manufacturing code before trying to unlock the bootload to avoid a bad awakening.
Edit: On a second thought ... while we're still lacking in-depth details I think someone should prod one of the mods to post a sticky tagged as "[WARNING] Read BEFORE attempting bootloader unlock".
I can confirm a hard brick on my Xperia x8 (11w40) when trying to unlock my bootloader.
hi,
I bought a X8 by mail delivery from the internet and got a bricked phone (so it seems)!
Symptom is phone doesn't connect to GSM network, and although i can scan for networks i can't connect to them. Tried several networks, same result. Everything else seems to work fine.
I'm completely newbie to Android phones, and only bought this one to try to avoid to stay behind, but this was a lousy way to start. I've been browsing through the forum, but there's too much info which only makes it more confusing to me.
I tried connecting the phone to S1tool and msm7227setool but i can't find the SEMC flash drivers, and although i browsed through the forum stickies for them i didn't find them.
So, my questions are:
1- Can someone provide a link to the drivers?
2- Is the following link the best way to solve my problem?
http://forum.xda-developers.com/showthread.php?t=1304258&highlight=no+network
3- I also want to debrand the phone, from the 360 apps i assume the phone is from vodafone. Can you recommend a fast ROM with full features support? And a good noob proof flash tutorial..
4- Will any of the above operations remove my SP unlock?
Sorry if most (or all) of this questions are a repetition of past threads, but starting with a phone this way, i honestly feel like a donkey looking at a palace! (Portuguese proverb, not sure you'll understand)
Thanks, Regards!
madz78 said:
hi,
I bought a X8 by mail delivery from the internet and got a bricked phone (so it seems)!
Symptom is phone doesn't connect to GSM network, and although i can scan for networks i can't connect to them. Tried several networks, same result. Everything else seems to work fine.
I'm completely newbie to Android phones, and only bought this one to try to avoid to stay behind, but this was a lousy way to start. I've been browsing through the forum, but there's too much info which only makes it more confusing to me.
I tried connecting the phone to S1tool and msm7227setool but i can't find the SEMC flash drivers, and although i browsed through the forum stickies for them i didn't find them.
So, my questions are:
1- Can someone provide a link to the drivers?
2- Is the following link the best way to solve my problem?
http://forum.xda-developers.com/showthread.php?t=1304258&highlight=no+network
3- I also want to debrand the phone, from the 360 apps i assume the phone is from vodafone. Can you recommend a fast ROM with full features support? And a good noob proof flash tutorial..
4- Will any of the above operations remove my SP unlock?
Sorry if most (or all) of this questions are a repetition of past threads, but starting with a phone this way, i honestly feel like a donkey looking at a palace! (Portuguese proverb, not sure you'll understand)
Thanks, Regards!
Click to expand...
Click to collapse
I have a X8 on Vodafone, and when I repairded my X8 in PCC it removed the vodafone apps and icon from Settings :-D
Sent from my tablet running Honeycomb
IrishStuff09 said:
I have a X8 on Vodafone, and when I repairded my X8 in PCC it removed the vodafone apps and icon from Settings :-D
Sent from my tablet running Honeycomb
Click to expand...
Click to collapse
Just 4 curiosity how to make the vodafone icons appear again??just4fun
Sorry for off-topic thing
As irishstuff said u should try to update your phone with pc companion(google it) and try to update the software.After that if u want to root your phone and install recovery search in xda for x8toolbox , is the most noob-friendly thing u will find
X8invisible13 said:
Just 4 curiosity how to make the vodafone icons appear again??just4fun
Sorry for off-topic thing
As irishstuff said u should try to update your phone with pc companion(google it) and try to update the software.After that if u want to root your phone and install recovery search in xda for x8toolbox , is the most noob-friendly thing u will find
Click to expand...
Click to collapse
Thanx for clarifying that.
But, if i update the phone via PCC, won't i lose the sp unlock? I'm saying this cuz i read that the no network problem is due to sim lock protection.
madz78 said:
Thanx for clarifying that.
But, if i update the phone via PCC, won't i lose the sp unlock? I'm saying this cuz i read that the no network problem is due to sim lock protection.
Click to expand...
Click to collapse
sp unlock? You mean "SIM unlocked"?
No, you won't lose the unlocked SIM by simply flashing back to Stock through PC Companion (in case PCC tells you that there's no update available you need to resort to the Flashtool method).
As for the drivers ... best method would be to install PC Companion. However, if you don't want that crapware on your system I can upload you the drivers (out of PCC) in a ZIP - then you have to point Windows manually to the directory so it can find the appropriate driver (EDIT: shouldn't be much of a trouble if you're familiar with installing drivers by pointing Windows to the directory or the INF file).
The only situation where you might lose your SIM unlock is at unlocking the boot loader to enable installation of custom kernels, but before you head into that you better check the manufacturing date of your phone (sticker below the battery) and then look through this forum to work out if it's a candidate for hard bricking or not.
B.Jay said:
sp unlock? You mean "SIM unlocked"?
No, you won't lose the unlocked SIM by simply flashing back to Stock through PC Companion (in case PCC tells you that there's no update available you need to resort to the Flashtool method).
As for the drivers ... best method would be to install PC Companion. However, if you don't want that crapware on your system I can upload you the drivers (out of PCC) in a ZIP - then you have to point Windows manually to the directory so it can find the appropriate driver (EDIT: shouldn't be much of a trouble if you're familiar with installing drivers by pointing Windows to the directory or the INF file).
The only situation where you might lose your SIM unlock is at unlocking the boot loader to enable installation of custom kernels, but before you head into that you better check the manufacturing date of your phone (sticker below the battery) and then look through this forum to work out if it's a candidate for hard bricking or not.
Click to expand...
Click to collapse
Yup, it says up to date, just clicked repair to see if it works. crapware.. lol, yeah i'd appreciate that zip file, thanks.
I think the issue is exactly that, a bad boot loader unlock, at least all symptoms point to that.. all i see in no network threads seems to be pointing there.
Thanx!
P.S.- SP (service provider) Unlocked.
madz78 said:
yeah i'd appreciate that zip file, thanks.
Click to expand...
Click to collapse
Download here
The Sony Ericsson X8 (and possibly other SE phones) Android drivers (ADB / Smartphone / USB Flash Device) for Windows (incl. x64 Editions) out of the latest and greatest PC Companion crapware.
madz78 said:
I think the issue is exactly that, a bad boot loader unlock, at least all symptoms point to that.. all i see in no network threads seems to be pointing there.
Click to expand...
Click to collapse
Errr... no. A "unsuccessful" boot loader unlock would turn your device into a hard brick (no lights, no vibration, no screen). As you're able to boot up into Android the bootloader and kernel seems to be intact.
IF the previous owner (in case you bought it used) tinkered around with boot loader unlocking ...
Use the s1tool to verify if the boot loader is locked or not. If it's unlocked simply follow the tutorial in the Development section to relock the boot loader or try the trick deedii posted about first (she had the same problem that GSM radio went dead after unlocking the boot loader).
---------- Post added at 12:40 AM ---------- Previous post was at 12:36 AM ----------
*ping* driver ZIP download link inserted
Holy crap!
Thanx for the zip btw..
I hit Repair in PCC and it re-flashed the phone. Now, instead of no network, the phone doesn't recognize ANY SIM card!!
I checked boot loader with S1tool, and the phone is locked (i see R).
I'm starting to think maybe it's a hardware problem and not from ROM.
Any ideas? Thanks.
madz78 said:
Thanx for the zip btw..
Click to expand...
Click to collapse
No problem, you're welcome.
madz78 said:
I hit Repair in PCC and it re-flashed the phone. Now, instead of no network, the phone doesn't recognize ANY SIM card!!
I checked boot loader with S1tool, and the phone is locked (i see R).
I'm starting to think maybe it's a hardware problem and not from ROM.
Any ideas? Thanks.
Click to expand...
Click to collapse
Yes, the "R" means the boot loader is locked.
As for the mSD card ... here's where we enter "trouble reloaded":
- What card? Class? Size? Brand?
- Does the card hold any important data? If not try to reformat the card (FAT32!!!). If Android refuses to format the mSD simply use a card reader and re-format the mSD in Windows.
EDIT: Also, just to make sure everything's vanilla: could you please take a look into Settings -> About phone to confirm you're running the genuine SE baseband/kernel and not some custom kernel?
EDIT 2: Errrrrrrrr.... never mind ... I somehow misread "SIM card" as "SD card". My fault!
X8invisible13 said:
Just 4 curiosity how to make the vodafone icons appear again??just4fun
Sorry for off-topic thing
As irishstuff said u should try to update your phone with pc companion(google it) and try to update the software.After that if u want to root your phone and install recovery search in xda for x8toolbox , is the most noob-friendly thing u will find
Click to expand...
Click to collapse
I actually don't have a clue, but I was glad when thety went
I dont like operators branding the phone with the software
The only apps i had by the operator (vodafone IE) were
Gold Rush, Vodafone Music Store, SIM Settings and SIM Toolkit <- I have GDX and i still have toolkit. XD
I had the 'vodafone 360' option in Settings
Sent from my tablet running Honeycomb
B.B.- M76XX-TSNCJOLYM-53404015
kernel- 2.6.29 [email protected] #1
Thanks again.
madz78 said:
B.B.- M76XX-TSNCJOLYM-53404015
kernel- 2.6.29 [email protected] #1
Click to expand...
Click to collapse
Yes, that's definitely the genuine baseband and kernel.
However, no matter how hard I think it through I don't see a good reason why it won't accept ANY SIM card, as a SIM unlock (or carrier/operator unlock if you want to put it that way) is as good as permanent unless you play around with unlocking the bootloader and either do something wrong or face the problem that it suddenly reverts back to the original SIM lock (in case it got unlocked and didn't ship unlocked by default).
The only problem I know about is ... if you live in a region where you would actually need a E15a baseband but happen to have the E15i baseband (you know, has to do with the frequencies that get used to transmit between your phone and the tower) flashed - or the other way around - you won't be able to connect to the GSM/3G network - but even then the phone won't reject the SIM card but simply fail to find any network.
In that case the problem resolve would be as easy as swapping out the baseband through flashing by Flashtool.
Good morning,
This keeps getting more and more confusing... thank god you've been such a valuable help BJ!
Dunno if it's "don't accept SIM" as much as don't recognize them.. I usually remove PIN codes from all my SIM's but today i've popped a new one to see if anything different happened.. The phone asked me for pin and validated it, but after this it doesn't recognize it anymore, i get a SIM with a red "!" on top of it in the upper right corner of the screen (same icon you get without SIM in phone).
As for all the other cards, it doesn't appear such icon, the phone starts normally and then asks for language and after asks to "insert SIM and restart phone"..
I don't think baseband is the problem, i think it's definitely related to SIM card reading.
NOTE: Before seemed irrelevant but now seems important to say, before, when i scanned for networks and tried to connect to one (same from SIM), phone gave me a message saying something like "your SIM card doesn't allow connecting to this network".
The problem seems to be definitely SIM card reader, the big doubt is if it's HW or SW.
My best guess is SW, because he can read PIN's but then just locks.. Where is the SIM card reader "driver"? baseband, kernel, ROM? should i try to update all those?
Thanks again!
hello again,
i found this in SETool forum which seems to be exactly my problem.
E15i - (x8) it doesn't read sim card and hangs during unlocking
I've had a problem with XPERIA X8 (E15i) for a long time now and I can't fix it.
I was trying to unlock it. I updated Android to v. 2.1. I have credits, I turn on debugg mode, I installed drivers. I push 1,2,5 and press Unlock/Repair.
Unfortunately it didn't finish, the program froze and switched off (on Vista). It took 5 credits. After turning it back on it wouldn't log to the network, even though it saw the network. But it shows that the phone is unlocked. By Setool I installed the version form after the update. After that it stopped detecting the sim card.
In hosting I read that I should repeat the unlock. I reinstalled the drivers, downloaded setool's previous version (v1.1106), but the program hangs every time in the same place and it doesn't go to the end (see screen below). With v1.1107 there's the same problem. I tried on Vista and XP – no difference. I installed setool on my other computer, where there are no boxes, drivers or antiviruses and still I couldn't succeed.
Does anyone have some expirience with the x8?
Thx in advance for help.
---------------
Reply
1.
reflash phone with generic 2.1 firmware, repeat unlock procedure.
2.
to restore phone to original state, write as script most earlier secunits backup from backup\%imei% folder
Click to expand...
Click to collapse
Could this be a bad unlock problem?
Thanx.
IrishStuff09 said:
I actually don't have a clue, but I was glad when thety went
I dont like operators branding the phone with the software
The only apps i had by the operator (vodafone IE) were
Gold Rush, Vodafone Music Store, SIM Settings and SIM Toolkit <- I have GDX and i still have toolkit. XD
I had the 'vodafone 360' option in Settings
Sent from my tablet running Honeycomb
Click to expand...
Click to collapse
Sim toolkit is on every phone,not only on vodafone
Been reading more and more, and this seem to be a very common issue in SETool SIM unlocking. can anyone suggest a solution?
Thanks.
Hello again,
I've been trying to run msm7227 setool2 and semc, but seem to be getting nowhere.. enters debugging mode and nothing else. What am i doing wrong?
Also, i've read in the following thread that sometimes boot is unlocked and S1tool says it's locked, but i can't find SEUS to download anywhere in the forum..
http://forum.xda-developers.com/showthread.php?t=1404148&highlight=sim+card
HEEELLP!!!
Thanks.
Hi, madz ...
To pull it together:
- The "SIM reader" is a software that comes as a part of Android in the form of a system app (inside /system/app). You can't exchange the related parts as they are specific to the Android version, in case your thoughts are running into this direction.
- The problem with "SEtool" is more like this ...
Let us assume the phone was originally SIM locked (bound to only allow SIMs of a specific operator/carrier) and then got SIM unlocked. The original SIM lock will jump back into place once the the boot loader got unlocked.
My observation is that this problem should actually go away once the boot loader got re-locked again. That being said I also read various threads where the SIM lock didn't vanish and the phone had to be unlocked anew.
On another note, it also depends on how the phone got unlocked ... there's a difference if it got SIM unlocked through SEtool or through Omious (<-- I hope it's spelled right)
The one fact that remains: simply querying the boot loader status ("R" vs "r") does not make the SIM lock to fire.
- SEUS ... well ...
I found Update Service (SEUS) 2.11.10.7 in the depths of my hard drive. Going to slap it on MultiUpload for you in a minute - though I can't guarantee that it still works; all I know is that SEUS got discontinued (or something along that line). Wait for the edit of the download!
EDIT: MultiUpload swallowed the file --> Download link
---------- Post added at 01:07 AM ---------- Previous post was at 12:59 AM ----------
Missed this one ...
madz78 said:
I've been trying to run msm7227 setool2 and semc, but seem to be getting nowhere.. enters debugging mode and nothing else. What am i doing wrong?
Click to expand...
Click to collapse
Shouldn't you connect the phone in flash mode instead of USB-Debugging mode?
Flash Mode means:
- Pull the USB cable out of your computer but leave it attached to the phone
- Turn the phone OFF
- Start the software
- Press the Back button and connect the USB cable to the computer
KEEP THE BACK BUTTON PRESSED UNTIL THE PHONE IS RECOGNIZED!
(Note: Windows may want to install the "SEMC Flash Device" driver)
Hi BJ,
The phone is not locked! it accepts pin from all networks, but after this, simply doesn't read the cards anymore. I only talked about this because the thread i found in SETOOL forum explains in detail what's happening to me.
I dunno if what happens to people who have no network or sim locked due to bad boot loader unlock is the same or not. It would be nice to know, but in my thread no one except you steps up.
If unlocked, i believe it's SETool and not Omnius because i only see threads with this issue in SETool support (dozens of complains) and found nothing in Omnius.
I still believe that maybe there's a solution other than unlocking it again, but due to inexperience i fail to see it.
about msm7227: i'm sorry, i meant flash mode, and it detects the phone, sometimes.. but always hangs in 2nd line (can't remember what said, but i'll try it again in a while and post here).
Where exactly is the phone unlocked? ROM, kernel, baseband? Do you think re-flashing it could solve the problem?
Thanks again friend!
Regards.
madz78 said:
The phone is not locked! it accepts pin from all networks, but after this, simply doesn't read the cards anymore. [...]
I dunno if what happens to people who have no network or sim locked due to bad boot loader unlock is the same or not. It would be nice to know, but in my thread no one except you steps up.
Click to expand...
Click to collapse
My X8 came SIM unlocked by default. Since it's old enough, and therefore safe for boot loader unlocking, I gave it a try (even been as daring as to unlock while having GDX v021 flashed).
Connected and checked with s1tool that it's suited for unlocking: Pass
Unlocked the boot loader: Pass
Booted up (SIM does not have PIN1 set)...
Connecting to the GSM Network: Pass
Connecting to the APN for 3G Internet access: Pass
Reboot (to make sure it didn't brick): Pass
Re-locked boot loader: Pass
Checked with s1tool that boot loader is locked: Pass
Device still able to connect to GSM/3G: Pass
I didn't try to flash a custom kernel but just stayed with the stock kernel. During the whole testing scenario - from unlocking to re-locking - I didn't have any problems with GSM/3G network connectivity or troubles reading the SIM.
Like I wrote above the PIN1 check was disabled because sometimes GingerDX shows the "Network unlock" screen after inputting the PIN ... that's more-or-less a bug workaround.
madz78 said:
If unlocked, i believe it's SETool and not Omnius
Click to expand...
Click to collapse
Thank you for correcting the spelling of "Omnius" ... I was typing it from the top of my head and failed to recall how it's spelled.
madz78 said:
Where exactly is the phone unlocked? ROM, kernel, baseband? Do you think re-flashing it could solve the problem?
Click to expand...
Click to collapse
If you refer to "how is the SIM lock lifted" then I think the best persons to answer this question are the guys who cracked the boot loader. I don't know enough about how the low-level init of the phone really works ... the boot loader guys aren't very chatty about telling us how the low-level boot of the X8 works.
Since, in my case, the SIM unlock prevails when flashing a custom ROM on top of the stock kernel (keep in mind I never flashed a custom kernel, so I never altered the "baseband" partition) the unlock can't reside in the ROM partitions.
But ... as the problem only arises when tinkering around with the boot loader but didn't affect my phone during boot loader unlock / re-lock ... and this is now purely guessing ...
The boot loader unlock only replaces the boot loader binary with a altered one. So if the thing that tells the phone that it's SIM unlocked resides in the part of the NAND where the boot loader / kernel / baseband is located it can only be a digital certificate or some sort of a binary that gets loaded through "Stage 1" init (during which the boot loader and kernel gets loaded and all the security checking stuff happens). It can't be in the higher init routines where the initialized kernel is boot strapping the ROM as that would disable the SIM unlock when flashing a custom ROM.
If blagus or the kernel devs have some ideas it would be great to read a few lines from a source knowing about the low-level init routines (to actually understand how the X8 comes to life once the power button is pressed).
On another thought ... the msm7227 CPU also must have some kind of firmware (think of it similar to a BIOS like a PC has) to init itself and the hardware ... maybe the SIM unlock is somewhere in there?
EDIT: On a third thought ... it would seem almost logical that the SIM unlock stuff is stored somewhere in the "security" related part of the NAND (somewhere deep down at the low-level init). If the phone came locked and got unlocked at some point the original SIM lock will most likely spring back into place at boot loader unlocking - so the SIM locked/unlocked thingy has to be somewhere in the low-level boot init; otherwise it wouldn't disable a "soft unlock" once the boot loader got unlocked and replaced past the cracked one which bypasses a whole lot of the security checks so unsigned boot binaries (kernel) can be loaded and executed.
Hello guys, I've been searching on xda-forums and I didn't found anything so here is the noob question.
- What is bootloader and what will I gain by unlocking this?
- I've got "11W22" Black x8 with cypress, so what are the risk of my phone? (I mean, I will install it, loose waranty, but what are disadvantages?)
- What are "all" the advantages of unlocking bootloader?
- What are the characteristic of kernels (alfs, nAa)(pros and cons) and what are battery life consumption?
I see most of you here using custom kernels and all devs are making ROMs for custom kernels.
The most important things for me are: battery life (need 2-3 days with normal use), stability and fullworking ROM (like stock one).
Can you help me?
Antique_Angel said:
Hello guys, I've been searching on xda-forums and I didn't found anything so here is the noob question.
- What is bootloader and what will I gain by unlocking this?
- I've got "11W22" Black x8 with cypress, so what are the risk of my phone? (I mean, I will install it, loose waranty, but what are disadvantages?)
- What are "all" the advantages of unlocking bootloader?
- What are the characteristic of kernels (alfs, nAa)(pros and cons) and what are battery life consumption?
I see most of you here using custom kernels and all devs are making ROMs for custom kernels.
The most important things for me are: battery life (need 2-3 days with normal use), stability and fullworking ROM (like stock one).
Can you help me?
Click to expand...
Click to collapse
- Think of bootloader as the BIOS of your PC.
- You have to unlock bootloader to install custom kernels
- The principal advantage of custom kernel is better performance: you can set swap, overclock, without having to patch modules, has better 3D librarys, etc.
- Since you have a X8, run S1 Tool and verify certificate, to see how to unlock.
- Battery life depends on which rom, how apps you have installed, etc. Dont expect much, cause after all, we have a smartphone (i guess you sleep every night right? so why not left it charging?)
- The main difference between Alfs and nAa is the support of ROMS
nAa = MiniCM based ROMs
Alfs = GDX based ROMs
- Least but not last, you can re-lock your bootloader
Thanks man, really what I needed.
I've got another questions to you:
1 - With unlocked bootloader, can I get back to Stock ROM by using SE application? (In case if anything someday gets ugly and I could need to "reset" everything and start again)
2 - Battery - I know that it depends on ROM and I shall recharge it every day, this is what I'm doing, but with custom kernels the battery improves or gets worse? Or stays the same?
3 - If unlock bootloader is that good, why relocking it?
Antique_Angel said:
Thanks man, really what I needed.
I've got another questions to you:
1 - With unlocked bootloader, can I get back to Stock ROM by using SE application? (In case if anything someday gets ugly and I could need to "reset" everything and start again)
2 - Battery - I know that it depends on ROM and I shall recharge it every day, this is what I'm doing, but with custom kernels the battery improves or gets worse? Or stays the same?
3 - If unlock bootloader is that good, why relocking it?
Click to expand...
Click to collapse
1. Yes you can go back. Just use PC Companion, it restore stock kernel and ROM, and then you relock your bootloader.
2. I think that stays the same or gets better. You should consider that stock is Android 2.1 and the most of ROMs are 2.3. More recurses, a little bit more battery.
3. I dont know, but I guess if you relock your bootloader, you still have the warranty, in case that any hardware fails. (verify this with someone more pro-user)
Sorry for my english errors, still learning.
---------
I'm using nAa + MiniCM and my battery is dropping 5% every 8-9 hrs. But i have a weak signal (consumes more battery), and 3G, Wifi disable.
hunff said:
1. Yes you can go back. Just use PC Companion, it restore stock kernel and ROM, and then you relock your bootloader.
2. I think that stays the same or gets better. You should consider that stock is Android 2.1 and the most of ROMs are 2.3. More recurses, a little bit more battery.
3. I dont know, but I guess if you relock your bootloader, you still have the warranty, in case that any hardware fails. (verify this with someone more pro-user)
Sorry for my english errors, still learning.
---------
I'm using nAa + MiniCM and my battery is dropping 5% every 8-9 hrs. But i have a weak signal (consumes more battery), and 3G, Wifi disable.
Click to expand...
Click to collapse
Thanks mate, I will unlock it right now to install GX Special Edition or Haka's or Froyo Pro (will see which of them are better for me).
---------
E não te preocupes com língua, percebe-se bem melhor do que de alguns que têm a língua materna como inglês.
hunff said:
1. Yes you can go back. Just use PC Companion, it restore stock kernel and ROM, and then you relock your bootloader.
Click to expand...
Click to collapse
I recently unlocked my bootloader succesfully according to this guide.
Then i installed a Kernel (LinuxDX) that bricked my phone and had to restore with Sony Erricson Update Service.
I am using GingerDX now and my log from s1tool is this:
Welcome to S1 identify 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): E15i
SOFTWARE VERSION: 1236-9291_2.1.1.A.0.6
CUSTOM VERSION: 1241-3728_R3B
FILESYSTEM VERSION: WORLD-1-8_2.1.1.A.0.6
SERIAL NO: CB511S8NUJ
SEMC SIMLOCK CERTIFICATE
Elapsed:9 secs.
I know that this RUNNING S1_EROM VER "r8A029" has an "r" that means that my bootloader is unlocked but i want to be sure that i can install another kernel without bricking my phone again.
So, can i install safely another kernel ?
Sorry for my english and my noobness i am new here ...
Yes, you can safely flash another kernel.
If you want to stay with GingerDX you can switch to alfsamsung's Alfs kernel - don't forget to flash the vold update in CWM or you will have problems mounting the SD.
If you want to change to nobodyAtall's nAa kernel you also need to change to the MiniCM7 2.1.9 ROM - GingerDX does NOT work on nAa's kernel. This means you first flash the kernel, reboot, enter CWM right away and flash the ROM (you hopefully copied onto the SD card beforehand).
While i was waiting for a reply i look around some kernels and i must say i got pretty much confused.
I noticed that most kernels have in common the ext2/3/4 , CPU governon and swap (?).
I cant find infos for these and i dont have a clue of what they are for.
And btw smartass is a CPU governon or something else ?
Thnx for the reply as i cant press thank button yet i think.
Edit: Also any info for what X8Gesture is for ?
hunff said:
1. Yes you can go back. Just use PC Companion, it restore stock kernel and ROM, and then you relock your bootloader.
Click to expand...
Click to collapse
You cant use PCC when you have a custom kernel installed, you need to use SEUS which works perfectly and does the same job.
_Sparks said:
You cant use PCC when you have a custom kernel installed, you need to use SEUS which works perfectly and does the same job.
Click to expand...
Click to collapse
For me, PCC works great with custom kernel. I already repair 2x with no problems.
---------- Post added at 08:32 PM ---------- Previous post was at 08:27 PM ----------
Mertang said:
While i was waiting for a reply i look around some kernels and i must say i got pretty much confused.
I noticed that most kernels have in common the ext2/3/4 , CPU governon and swap (?).
I cant find infos for these and i dont have a clue of what they are for.
And btw smartass is a CPU governon or something else ?
Thnx for the reply as i cant press thank button yet i think.
Edit: Also any info for what X8Gesture is for ?
Click to expand...
Click to collapse
- Most of kernels have the same features, but supports a different kind of ROMs.
- SmartASS is a CPU Governor: it increase/decrease clock speed of processor when need it. (Google for more info)
- X8Gesture is a module for fake dual touch in Synaptics touchscreen. In most custom kernel, it already implemented.
- Swap is linux virtual memory (Google for info)
- Ext 2/3/4 linux filesystem. You partition your card, and then you can install apps on it.
Hello Everyone,
Sorry if this is redundant but believe me I searched for hours but still not sure,
I got an X8 (e15i), I wanted to flash ICS, so I did the following:
1- rooted using x8toolbox.final (Success)
2- chose "Recovery" -> "Clock Work Mod Recovery" -> "nobodyAtall CWM 3.2.0.0r4" to install CWM (No errors, didn't try if cwm were really working)
3- Checked Production Date from IMEI code to make sure that it may be unlocked (Success)
4- chose to UnLock BootLoader in x8toolbox.final, it opened s1tool, I followed instructions (got semc simlock certificate)
then it did something and restarted the phone and opened s1tool again, so i powered off the device to hold "back" key and reconnect it, and the device never saw the light again!
it won't turn on by any means, no led no vibration no screen...
I suspected the battery so I charged the battery with an external charger, and no change...
We never have any SE service centers in Syria, so this is not an option, either I fix it or throw it away.
DXMan said:
Hello Everyone,
Sorry if this is redundant but believe me I searched for hours but still not sure,
I got an X8 (e15i), I wanted to flash ICS, so I did the following:
1- rooted using x8toolbox.final (Success)
2- chose "Recovery" -> "Clock Work Mod Recovery" -> "nobodyAtall CWM 3.2.0.0r4" to install CWM (No errors, didn't try if cwm were really working)
3- Checked Production Date from IMEI code to make sure that it may be unlocked (Success)
4- chose to UnLock BootLoader in x8toolbox.final, it opened s1tool, I followed instructions (got semc simlock certificate)
then it did something and restarted the phone and opened s1tool again, so i powered off the device to hold "back" key and reconnect it, and the device never saw the light again!
it won't turn on by any means, no led no vibration no screen...
I suspected the battery so I charged the battery with an external charger, and no change...
We never have any SE service centers in Syria, so this is not an option, either I fix it or throw it away.
Click to expand...
Click to collapse
dude it think...hard brick
try with battery from your friend x8
if not go in place where you buy it and lie something they will send it to SE
and why didn you check product code under battery
852 iciamn
What production date do you have?? Either you did not check it correctly, or something went terribly wrong...
Had twice the same issue (but did not know about the production date warning), both times SE replaced my device.
yeo..dont foregt to check your manufacture date..dont unlock for 11W29+
u can fix by Jtag..but do it with profesional guy
BlackRabbit1703 said:
yeo..dont foregt to check your manufacture date..dont unlock for 11W29+
u can fix by Jtag..but do it with profesional guy
Click to expand...
Click to collapse
Well, thank you all guys, I now realized that mine is 12W07 so hard brick it is.
Can you please tell me where to start with this Jtag thing, I might be not pro, but I practiced with some electronics and microcontrollers, and I also know some guys who do Jtag to XBox.
DXMan said:
Well, thank you all guys, I now realized that mine is 12W07 so hard brick it is.
Can you please tell me where to start with this Jtag thing, I might be not pro, but I practiced with some electronics and microcontrollers, and I also know some guys who do Jtag to XBox.
Click to expand...
Click to collapse
yeah...maybe u can take it to Sony centre..
but if u want to try it, search on youtube..sory I forget the link
for reference http://en.wikipedia.org/wiki/Joint_Test_Action_Group
ahh! maybe u can watch it!
http://www.youtube.com/watch?v=ujH_IpsskLg&feature=g-hist
Hello everybody, I’m new here (so yes I’m noob like it is said in welcome video )
Just before I star describing my problem I must say, that I’ve looked around the forum and also used search button Some threads are similar to my problem, but maybe I can take some alternative advice here
So the problem:
1. Successfully rooted
2. xRecovery installed
3. FroyoBread v023b installed and everything ok
4. Bootloader successfully unlocked (manufactured 11W09)
5. Downloaded GDX and Alfs kernel -> copied to flashtool directory
6. BUT my terrible mistake -> for flashing I’ve missclicked and selected that damn default X10 firmware -> dead phone
7. So I searched the forum and find UART method -> connection of pins was OK -> Omnius detected phone, but when I tried to purchase license from our reseller I’ve been told that they don’t have permission to do that at this time and don’t know how long it will take (some misunderstanding with Omnius or what)
And finally the question, is there another option of resurrecting via UART connection? Another software to do that or anything? And at some reasonable price? Or if you have any ideas how to do that by myself (I can make a lot of things at our Faculty of Electrical Engineering and Informatics) please share your ideas.
Thanks for your comments!
Hello sir, jtag is what you are looking for.
I don't think you are a noob (but its good that you watched the video), so.... what are you waiting for?! Google it
Thanks for your tip. So i've looked around and making of jtag cable (to paralel port) seems to be pretty simple. Some tips on free software which could be used to rewrite to whole firmware of the phone? I don't want to make a cable a then again find that i'm unable to do anything with it. And then i just copy the .ftf file to phone rom? I'm not a programmer
I don't have personal experience with jtag but i have found this.
Take a look at this site.
Sorry i cant help you much with this, you will need to do some deep research. Have fun.
Btw i think you have missed that you need jtag box which is not that cheap.
I know about riff box and i know that it is expensive But i'm not sure if it is possible to connect "homemade" jtag cable right to the paralel port of pc (i have one older pc with paralel port at home) or it is necessary to use some interface like riff box. I'm searching google almost whole last week and i'm starting to hate it
You can also try @aze2learn's method HERE
8cpaiw said:
You can also try @aze2learn's method HERE
Click to expand...
Click to collapse
I tried, like i said in my first post but omnius license can't be bought in our country at this time Some missunderstanding between Omnius and our reseller or what
This is interresting topic: http://forum.xda-developers.com/showthread.php?t=893144#poststop but it is for HTC and I'm not sure if HTC and Sony Erisscon memory organization are the same
I forgot about Omnius