[Q] I think i bought a bricked X8 - help! - XPERIA X8 Q&A, Help & Troubleshooting

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.

Related

[Q] No SIM inserted

Well, I have a OB with the "No SIM inserted" problem... (with SIM from the network lock or any other)
Any idea how to fix this?
Just tried pretty much any trick I could find online (just missing the heatgun thing - in due time...)
I appreciate more ideias.
thx!
If it doesn't recognise any SIM card it's hardware problem I think...
Btw i had the same problem....it got fixed in some store and the problem was something called main pcb
Sent from my LG-P970 using XDA App
I know it is most probably HW... but, doesn't hurt to ask for opinions/ideas.
Right now I only have a cool media player
I think I might try the heat gun trick and see how it goes.
[EDIT]: Could it be black listed by the operator? (I got it as is, used)
Hi, I've got this same prob but with another phone, non-android it was a samsung gt-s5560 [marvel or tocco] it was mine and I sell it, after a few days the girl keep telling me that she couldn't use the phone cause of a PIN, does your OB ask for a PIN? if so, just ask the old owner, when I remember the PIN call the girl and now she's happy using the device
I had the same problem with my ob. I take it to service and they replaced the phone with a new one. It's an hw problem with pcb.
Sent from my LG-P970 using XDA App
I guess taking it to service won't do 'cause I don't have any receipts of the purchase (it was used and I know about the issue).
Yesterday I tried to check the connections to the SIM reader module but no avail.
Maybe today I'll try to toast it with the heat gun.
If your phone asks for PIN when SIM is inserted then it's probably stolen and was blacklisted in international base of stolen phones used by operators worldwide.
If it isn't asking for PIN then it's 100% hardware fault. Better take it to some electronic repair service, because with the heatgun you can make it even worse...
I had that problem before. I think it's software-related (or maybe just a fluke). My OB is running on Nova 4.5.
I always use "network sim #1", but when I switched to my other network sim, which we'll call "network sim #2", it was ok for a couple of minutes then after that "NO SIM INSERTED" appeared.
After that, I rebooted and noticed that my phone was unusually slow... I still have the "NO SIM INSERTED" on the display.
I rebooted again and my phone still was slow and "Force Close" prompts appear one after another.
So I just re-flashed Nova 4.5... I didn't take the SIM out. And voila! 1 month and no "NO SIM INSERTED" messages again.
radkor said:
If your phone asks for PIN when SIM is inserted then it's probably stolen and was blacklisted in international base of stolen phones used by operators worldwide.
If it isn't asking for PIN then it's 100% hardware fault. Better take it to some electronic repair service, because with the heatgun you can make it even worse...
Click to expand...
Click to collapse
Not stolen. Not blacklisted. Just won't assume any SIM. From my searches this seems a pretty common issue that can strike at any time... (You are warned...)
I know the heatgun can easily kill it but I'm willing to take the risk. In other phones replacing the SIM reader module would fix it but the P970 is somewhat welded/glued to the shielding in the MoBo and I couldn't find a replacement part also.
Anyway, I bought this with the hope I could fix it, otherwise it'll be a cool media player and a nice development platform addition to my other android.
ajcantonio said:
I had that problem before. I think it's software-related (or maybe just a fluke). My OB is running on Nova 4.5.
I always use "network sim #1", but when I switched to my other network sim, which we'll call "network sim #2", it was ok for a couple of minutes then after that "NO SIM INSERTED" appeared.
After that, I rebooted and noticed that my phone was unusually slow... I still have the "NO SIM INSERTED" on the display.
I rebooted again and my phone still was slow and "Force Close" prompts appear one after another.
So I just re-flashed Nova 4.5... I didn't take the SIM out. And voila! 1 month and no "NO SIM INSERTED" messages again.
Click to expand...
Click to collapse
As of now, don't think its SW related anymore... I've flashed Nova (v8) and CM7 (n#11) a couple of times already.
Still, there are some radio files (AMSS?) that eventually could help. I'm trying to find those but the LG's seems harder to find.
Thank you all.
I've just read your post . I have exactly the same problem. I have also bought my OB with a hope that I could fix it . Did you found a solution for your problem ?
Thanks in advance.
aalmo1 said:
I've just read your post . I have exactly the same problem. I have also bought my OB with a hope that I could fix it . Did you found a solution for your problem ?
Thanks in advance.
Click to expand...
Click to collapse
maybe your phone has lock on mobile network?
same problem here :/
its all after my phone has been rooted!
it was via blackjack
Maybe some of you are wrong ! Maybe it`s software related.
If you root it with blackjack this dont`t kill or get your hardware malfunctioned because it only trick your firmware to get privileges. Hardware is not the answer.
Maybe you all must try the unbrick thread from Optimus Black Android Development with the option of Erase CP and flash .bin and .fls files on your OB.
It happened to me too when i was flashed CM nighly`s. The cure was to to flash nova rom and nova kernel v10c and look now my phone work very well whithout any SIM problems.
scamex said:
Maybe some of you are wrong ! Maybe it`s software related.
If you root it with blackjack this dont`t kill or get your hardware malfunctioned because it only trick your firmware to get privileges. Hardware is not the answer.
Maybe you all must try the unbrick thread from Optimus Black Android Development with the option of Erase CP and flash .bin and .fls files on your OB.
It happened to me too when i was flashed CM nighly`s. The cure was to to flash nova rom and nova kernel v10c and look now my phone work very well whithout any SIM problems.
Click to expand...
Click to collapse
I have tried to unbrick my phone this way but I cant activate "Erase entire CP".
Windows anabler "on" doesn't help too. I will try to install nova kernel v10c as you recommend without Erasing cp. Maybe it will help.
---------- Post added at 12:31 AM ---------- Previous post was at 12:25 AM ----------
dflt said:
maybe your phone has lock on mobile network?
Click to expand...
Click to collapse
I dont think there is Simlock on this phone. When I want to enter unlockcode it shows me "your phone is not personalized". So it seems there is no Simlock.
aalmo1 said:
I have tried to unbrick my phone this way but I cant activate "Erase entire CP".
Windows anabler "on" doesn't help too. I will try to install nova kernel v10c as you recommend without Erasing cp. Maybe it will help.
---------- Post added at 12:31 AM ---------- Previous post was at 12:25 AM ----------
I dont think there is Simlock on this phone. When I want to enter unlockcode it shows me "your phone is not personalized". So it seems there is no Simlock.
Click to expand...
Click to collapse
Exactly ! I think if you want that Erase Entire CP you must go in hidden menu of OB and tick CP USB instead of ...
scamex, thanks to your advices I have solved my problem. As you said I got to the hidden menu , then AP CP USB Switching and CP USB . After these steps I could check "Erase entire CP" in Smartflashtool . I have flashed my phone with v10c rom using .bin and .fls files and now I have the signal and my SIM is recognized again. Thanks so much again .
So now check your IMEI via *#06# and this one under your battery
aalmo1 said:
scamex, thanks to your advices I have solved my problem. As you said I got to the hidden menu , then AP CP USB Switching and CP USB . After these steps I could check "Erase entire CP" in Smartflashtool . I have flashed my phone with v10c rom using .bin and .fls files and now I have the signal and my SIM is recognized again. Thanks so much again .
Click to expand...
Click to collapse
About imei, check here :http://forum.xda-developers.com/showthread.php?t=1447311
I panicked when i saw my "new" Imei but thanks to Redpik I have chenged it easily back . It works , thanks.

Unlocking Focus S

Hey guys,
So I need to unlock my Focus S and went to fastgsm.com, and there are two methods, one by USB and one via IMEI. Can anyone tell me what the difference is? I'm in the USA btw. Thanks!
tonynojutsu said:
Hey guys,
So I need to unlock my Focus S and went to fastgsm.com, and there are two methods, one by USB and one via IMEI. Can anyone tell me what the difference is? I'm in the USA btw. Thanks!
Click to expand...
Click to collapse
USB can be quicker and cheaper but more trouble sum to get working if it is possible at all (not all models work)
IMEI can take a while to come through and generally costs more, but is a lot easier to get working.
My phones yet to arrive so I cant say for sure what does and doesn't work, but after spending an hour or so researching unlocking via cable. it doesn't appear to be possible, in that the i937 isn't on any of the supported cable unlock lists..
I unlocked via USB and it worked fine. It's not working in Windows 8 though!
Also, in the event that the USB unlock doesn't work, the network unlock tool is actually displayed within the app, that you can then enter in the phone manually.
64GUNSHIP said:
I unlocked via USB and it worked fine. It's not working in Windows 8 though!
Also, in the event that the USB unlock doesn't work, the network unlock tool is actually displayed within the app, that you can then enter in the phone manually.
Click to expand...
Click to collapse
could you drop some details of where you did it?
still cant find any cable unlock sites that say they support the i937
FastGSM.com worked fine for me.
Sent from my SGH-i937 using XDA Windows Phone 7 App
Just tried to unlock my Focus S (updated via Zune to the latest 8773 version with Samsung drivers) using the USB method from FastGSM and the program failed to unlock my phone. Also tried using the program to unlock after restoring to a 7720 backup but usb unlock still failed - thinking it is the bootloader as its version number didn't revert to an earlier number even after restoration. Currently waiting for support from FastGSM to respond...
armodons said:
Just tried to unlock my Focus S (updated via Zune to the latest 8773 version with Samsung drivers) using the USB method from FastGSM and the program failed to unlock my phone. Also tried using the program to unlock after restoring to a 7720 backup but usb unlock still failed - thinking it is the bootloader as its version number didn't revert to an earlier number even after restoration. Currently waiting for support from FastGSM to respond...
Click to expand...
Click to collapse
Are you using Windows 8 by chance? It didn't work on W8 for me. The program actually displays the unlock code during the process. It's like "network code" or something in the dialog. You can simply enter that into your phone.
64GUNSHIP said:
Are you using Windows 8 by chance? It didn't work on W8 for me. The program actually displays the unlock code during the process. It's like "network code" or something in the dialog. You can simply enter that into your phone.
Click to expand...
Click to collapse
I am using Windows 7 Pro 64-bit. Hm...nothing like that comes up in the dialogue box of the FastGSM program. Here is the log (replace the IMEI and serial with X's):
7/4/2012 1:54:44 PM
1. Please ensure that battery of your phone is fully charged
2. Turn on your phone without simcard.
3. On keypad of your phone type ##634# and click "Call" button to show Diagnosis screen.
4. Type *#7284# onto Diagnosis screen, select "Modem, USB Diag." and confirm selection.
5. After the phone restarts please connect USB cable to your computer and to the phone
6. Wait until all drivers are installed.
7. Click "Next" button.
OPENING COM5 : [OK]
PDA VERSION : I937UCKJ1
CSC VERSION : I937ATTKJ1
PHONE VERSION : I937UCLE2
HARDWARE VERSION : REV1.0
BUILD VERSION : M7630A-AAEQMWZM-1.6.002407
PHONE IMEI : XXXXXX-XX-XXXXXX-X
PHONE SERIAL NUMBER : XXXXXXXXXX
PHONE MODEL : SGH-I937
PHONE PLATFORM : WP7_YUKON
BYPASSING MSL PROTECTION : [FAIL]
Log was created using FastGSM Client 1.0.0.65
Unfortunately no network code seems to be displayed
just to give an update, the fastgsm client is unable to unlock phones that have applied the new LE2 firmware update from samsung. they refunded my cost (rather than unlock it with IMEI for me :crying
if they won't.. try SAMSUNGimeiUnlock.com
i got mine there for my focus s
Can you guys tell me how much are they charging for unlocking Samsung focus s on http://www.samsungimeiunlock.com ?
and we are talking about network unlock right? could somone confirm if the below phone can be unlocked?
http://www.ebay.com/itm/AT-T-SAMSUN...0941959080?pt=Cell_Phones&hash=item4ab9a1a7a8
lsguntu said:
Can you guys tell me how much are they charging for unlocking Samsung focus s on http://www.samsungimeiunlock.com ?
and we are talking about network unlock right? could somone confirm if the below phone can be unlocked?
http://www.ebay.com/itm/AT-T-SAMSUN...0941959080?pt=Cell_Phones&hash=item4ab9a1a7a8
Click to expand...
Click to collapse
yeah it can be SIM unlocked via IMEI and if you don't update it (apparently) via USB cable as well.
One more question . Any other specific advantage on buying a unlocked device apart from price?
lsguntu said:
One more question . Any other specific advantage on buying a unlocked device apart from price?
Click to expand...
Click to collapse
Even being unlocked the chances are with the Focus S it will still be branded so the only difference buying unlocked against locked, is that its usually more expensive to buy an unlocked device, however unless you fail do to your research you will find that the price is usually about the same anyway, sometimes marginally more expensive, I suppose you could call it the "hassle tax"
My Experience with UNLOCKing Samsung Focus S i937
...this is is the worst to unlock. I went through 3 ebay sellers (range .99 to $25). No one could find a unlock code (but refunded my money...after complaining). I went to local 3rd party mobile phone shop...they couldn't find a unlock code.
I then went to FastGSM and selected USB unlock...since IMEI way hasn't worked. I paid, downloaded client...client connected..but didn't do anything.. I left it there for 30 mins. Contacted FastGSM, they referred me to online tutorial..which i followed to the "T". Still didn't work. So I deiced to hard reset my phone...still didn't work...i decided to update it to the latest version through Zune( DON'T DO THIS! without making a Backup first!! http://forum.xda-developers.com/showthread.php?t=13795711).. Then I found this thread...member "64GUNSHIP" stated that usb client doesn't work with Windows 8 ( which is what I was using). So I used another computer with Windows 7. The usb client works!!! I got unlock code...but somehow the "SIM Unlock Screen" didn't show up any more with or without a SIM card. [Unaware to me, the client somehow unlocked my phone without me entering the code]
So the entire time I was trying to figure out did the Zune update kill the Sim unlock menu, I tried the #7465625*638*CODE#. I even restored to a previous ROM Backup. The issue is that I was using an OLD OLD OLD Sim card from a different carrier that the phone didn't recognize. Once I put in a working Tmobile SIM ...everything worked great!

Unlockable botloader after soft brick?????

Hi to everybody.
After soft bricking my sim-unlocked X8 due to install attempt of the lates tGingerbread v23 rom with alfadons and overclock-module, I had to use SEUS to flash an OEM rom and baseband.
Now I tried to re-root and unlock the bootloader several times but unfortunately the last string in cmd window is: not recognized simlock... or something similar.
After doing a lot of forum search there are plenty of hints telling that there's nothing to do. no possibility to install custom rom.
I tried it anyway and still soft brick (SE logo appears and nothing else..)..
So I decided to re-flash the OEM Rom and use the phone this way BUT......it works fine only WITHOUT a sim card inserted. If the sim card is inserter no icons appear, no button working. The only thing you see is the background immage...
Can anybody help me??????
sputnik81 said:
Hi to everybody.
After soft bricking my sim-unlocked X8 due to install attempt of the lates tGingerbread v23 rom with alfadons and overclock-module, I had to use SEUS to flash an OEM rom and baseband.
Now I tried to re-root and unlock the bootloader several times but unfortunately the last string in cmd window is: not recognized simlock... or something similar.
After doing a lot of forum search there are plenty of hints telling that there's nothing to do. no possibility to install custom rom.
I tried it anyway and still soft brick (SE logo appears and nothing else..)..
So I decided to re-flash the OEM Rom and use the phone this way BUT......it works fine only WITHOUT a sim card inserted. If the sim card is inserter no icons appear, no button working. The only thing you see is the background immage...
Can anybody help me??????
Click to expand...
Click to collapse
Visit this link and read every step carefully..
It might help u...
http://forum.xda-developers.com/showthread.php?p=10879507#post10879507
sputnik81 said:
Hi to everybody.
After soft bricking my sim-unlocked X8 due to install attempt of the lates tGingerbread v23 rom with alfadons and overclock-module, I had to use SEUS to flash an OEM rom and baseband.
Now I tried to re-root and unlock the bootloader several times but unfortunately the last string in cmd window is: not recognized simlock... or something similar.
After doing a lot of forum search there are plenty of hints telling that there's nothing to do. no possibility to install custom rom.
I tried it anyway and still soft brick (SE logo appears and nothing else..)..
So I decided to re-flash the OEM Rom and use the phone this way BUT......it works fine only WITHOUT a sim card inserted. If the sim card is inserter no icons appear, no button working. The only thing you see is the background immage...
Can anybody help me??????
Click to expand...
Click to collapse
did u flash/downgrade to stock rom before unlock bootloader?
if not u should unlock bootloader with stock rom but not custom rom
According to that threat you linked me....I permanently bricked the phone as my phone was sim-unlocked with a tool different from semc or setc2 tool and I tried to unlock to bootloader....
No I'm really pi...ed off....
If I'm right I have to buy a new phone....
sputnik81 said:
According to that threat you linked me....I permanently bricked the phone as my phone was sim-unlocked with a tool different from semc or setc2 tool and I tried to unlock to bootloader....
No I'm really pi...ed off....
If I'm right I have to buy a new phone....
Click to expand...
Click to collapse
No, you dont have to buy a new phone.
Just go to the store and say that this happened when im updated my phone with pccompanion.
My buddy did that twice and they did believe him, and hes phone got repaired for free.
Skickat från min ST18i via Tapatalk 2
Unfotunately that's not possible as yhe phoen is an "3 italia" sim-locked phone bougth in italy obviously and I moved to germany now..... The bill is still at home in Italy....
3 Italy would immediately notice the phone has been sim-unlocked...and I would have to pay the whole listing proce of the period when I bought the phone and would have to pay a high penality too...
That woudl be more than 400 euro in sum.....not worth....
Thanks to everybody who tried to help me
sputnik81 said:
Unfotunately that's not possible as yhe phoen is an "3 italia" sim-locked phone bougth in italy obviously and I moved to germany now..... The bill is still at home in Italy....
3 Italy would immediately notice the phone has been sim-unlocked...and I would have to pay the whole listing proce of the period when I bought the phone and would have to pay a high penality too...
That woudl be more than 400 euro in sum.....not worth....
Thanks to everybody who tried to help me
Click to expand...
Click to collapse
Have you tried re-locking your phone? ONLY IN STOCK ROM, PLS!
How can I sim-lock it again?
sputnik81 said:
Unfotunately that's not possible as yhe phoen is an "3 italia" sim-locked phone bougth in italy obviously and I moved to germany now..... The bill is still at home in Italy....
3 Italy would immediately notice the phone has been sim-unlocked...and I would have to pay the whole listing proce of the period when I bought the phone and would have to pay a high penality too...
That woudl be more than 400 euro in sum.....not worth....
Thanks to everybody who tried to help me
Click to expand...
Click to collapse
Don't take it to the 3 store. Take it so the Sony Ericsson store and tell them what DevStaffAndroid said. You will need to have warranty though.
Sent from my X8 using xda premium
sputnik81 said:
How can I sim-lock it again?
Click to expand...
Click to collapse
1) Download the original stock rom. run flash tool to flash the stock rom.
2) Run S1 tool, press " RESTORE" button!
At the stage, no harm trying!

[Q] Xperia T soft brick - HELP GREATLY APPRECIATED

Hi there
I am encountering an issue with my Sony Xperia T (FW: 9.1.A.1.141) which I am certain can be resolved with the correct tools and knowhow, but having spent the last week following what feels like every related link on the internet, I am no further forward - sleeping badly as a result - and very much in need of some help.
I'd prefer to avoid a torrent of potential fixes that I may already have tried at length so please forgive me if I go into too much detail. I just want to be very clear exactly where I am and what I have done so far to try and fix the issue. My PC is running Windows 7 64-bit (no issues).
This is my first proper smartphone so after a few months getting to grips with the underlying nature of the Android OS, I decided it was now time to root the phone and try out different ROMs etc. After reading what I could about the process, I finally used DooMLoRD's Easy Rooting Toolkit 17 (For Sony Xperia Devices) and was amazed by how easy it was to unroot my device. After installing Titanium Backup and fully backing up my files, I then installed ClockWorkMod Recovery 6.0.4.6 (For Sony Xperia Devices), and was able to boot into the recovery environment without issue (I also made an additional backup of the system at this point). So far, so good.
I then copied two ROMS to my SD card - Android 4.4.2 (KitKat) For Sony Xperia T (AOKP Build) & CyanogenMod 11.20140127 (Nightly) For Sony Xperia T - and tried to flash the CyanogenMod ROM from within the ClockWorkMod Recovery Environment, however I received a Status 7 Error, preventing me from flashing the ROM, then tried the same with Android 4.4.2 (KitKat) ROM, but again I received a Status 7 Error. As I attempted to leave the recovery environment to research the Status 7 Error, the program flashed a popup saying the phone was not rooted and would I like to root it. At this point, I assumed I had lost root as a result of the Status 7 Error, but didn't want to make any more changes, so chose no to the root option and restarted my Xperia T.
At this point the Sony logo went into a loop and despite restarting the phone using power and volume up many times, I was unable to boot back into the ClockWorkMod Recovery Environment nor connect the phone to my PC, although I could see the drivers appear for a few seconds in Windows before disappearing. It took me a good couple of days to realise that I had to fully charge my phone, so when I began the operation again with a fully charged phone I was able to update the driver in Device Manager from Sony Ericsson Seehcri Control Device (yellow exclamation mark) to Sony ADB Device (although the Sony Ericsson Seehcri Control Device with exclamation mark later returned so I am unable to assess how successful this actually was).
From here, I tried to update the phone using the already installed and up to date PC Companion, but the phone will not connect in flash mode, so it is not possible to connect the phone. I also tried the latest Sony Update Service (2.13.4.16), then Sony Emma Flash Tool (For Sony Xperia Devices), but none of these recognise the phone because I cannot get the phone into flash mode. Using the Android Flash Tool 0.9.13.0 (For Sony Xperia Devices), I am able to connect to the phone in fastboot mode, but when I try to install a stock kernel or any other variant, the Flash Tool states that I can't make any changes because the phone is not rooted.
Thinking I could root my phone again with DooMLoRD's Easy Rooting Toolkit 17, this time it no longer works, I assume because my phone cannot enter flash mode, even though it is recognised in Android Flash Tool 0.9.13.0 in fastboot mode (blue light).
Now, it is conceivable since my phone is no longer rooted that I may well be able to have my phone fixed under warranty and returned to me, however I would thereafter be scared to try and install a custom ROM, and would never really feel comfortable with the phone again, so I would much prefer to learn how to fix the problem myself. I am convinced the phone is salvageable because I have no issue recharging the phone, the screen is lighting up to display the Sony logo without issue and I am able to connect to my PC so that Sony ADB Device is recognised in Device Manager and via the Android Flash Tool 0.9.13.0, but can make no other changes.
My suspicion is that it has something to do with the ADB drivers, (which I linked to my Android Developer Tools Bundle 20131030 64-bit via the Windows Environment Variables), since no devices are recognised when I connect the phone and run the ADB Devices command in the Windows Command Prompt even when Windows is otherwise able to identify the device in Device Manager.
If anyone would be willing to talk me through this, I would be most grateful and would follow up all advice up so this information might be useful to others in the future as I can't see this being an isolated case. Likewise, if I am simply wasting my time and need to get the phone replaced or repaired, at least it would be good to know that I have exhausted all other options.
FYI Prior to the soft brick, I had USB debugging enabled and was in Mass Storage Mode (since this was more stable than Media Transfer Mode).
Hi. I don't see any mention of bootloader status. Did you go through the process of unlocking your bootloader? Or have you checked to see if your phone is "bootloader unlock allowed: yes"? The reason I ask is because the 2 roms you want to try seem to be AOSP-based / Cyanogen, which run on custom kernels. If your bootloader is locked, you are not allowed to flash custom kernels. That might explain the failure code you say in CWM - or it might not (since my bootloader cannot be unlocked, I don't have much experience with those kinds of ROMs).
Moving on to the recovery you flashed - Which recovery did you install? I have been reading that Clockworkmod recovery (v9) is quite buggy. You can get v8 in this thread: http://forum.xda-developers.com/showthread.php?t=2609997
The peeps in this forum are pretty good problem solvers (and creators ;D) - we'll get you going again hopefully!
is your bootloader unlocked dude?i mean if you have a locked bootlader you are not supposed to install custom roms. and if your boot loader is unlocked sony update engine and pc companion wont solve the issue. you have to try with flashtool .firstly you gotta install the flashtool drivers fot xt .and then run flashtool x64. hold the vol down button and connect it using usb. i had this problem many times. and that above procedure may solve your issue
Hi there
First of all thank you so much for replying. These forums are quite daunting at times and it is good to know someone with some clout is listening. Apologies again for going into yet more detail, but it should help me reach a resolution sooner rather than later.
As re the bootloader, I was under the impression that DooMLoRD's Easy Rooting Toolkit 17 would root my stock Xperia T while leaving the bootloader untouched - that is to say locked (as far as I am aware) - should I wish to revert the rooting process at a later date. Now, I obviously lost root somewhere along the line, but has the bootloader also been changed to unlocked? I don't know, but I wouldn't imagine so, so I can only assume it is still locked.
I have recharged my phone ready to make some fresh attempts at this, but to confirm the current state of my Windows 7 connection, I can only connect to the PC in fastboot (with the blue light turned on after connecting to the machine while pressing volume down). There is definitely an issue with some aspect of the drivers since the Sony ADB Device is recognised as working in Device Manager as soon as I connect the phone, however the bothersome Sony Ericsson Seehcri Control Device is also present with a yellow exclamation mark indicating a problem.
Now, whether this is actually affecting my use of the Android Flash Tool 0.9.13.0 and the other flash tools, I can't actually say. When I open the Android Flash Tool with the phone connected, the two options available to me are flashmode or fast boot mode. When I try to use the flashmode with the (as far as I am aware) Xperia T stock firmware LT30P_9.1.A.1.141_PL.ftf, I simply cannot connect in flashmode when prompted. I am asked to remove the phone then reattach it, but no green light ever shows indicating flashmode, only the blue light indicating fast boot mode. When I try to use fast boot mode on the other hand, firstly I am not sure which of the various methods to use - I have of course tried them all, and also I should say both the 32-bit and 64-bit versions of the Flash Tool - but when I do, I am always told that the device needs to be rooted first.
Now, this may have something to do with the kernels/firmware/ROMs that I am using (there's no question all the variations confuse me a little) as I assumed it simply wasn't possible to flash via fastboot yet further reading suggests that it should be possible to flash a stock kernel without root access. The kernels/firmware I have tried are: stock-7.0.A.3.223-twrp-2.3.3.0.elf; 15102012.img; Sony Xperia T Kernel (Stock) With CWM602; Sony Xperia T Kernel (Stock) With TWRP2500. So perhaps I am not using the correct firmware or kernel (I would like to try the LT30P_9.1.A.1.141_PL.ftf, but cannot see an option to do so via fast boot mode). If this is the case and I am able to identify the correct kernel, then perhaps this "device must be rooted first" notification would no longer happen and the state of the ADB drivers would be largely irrelevant.
On the other hand if the flash tool in fast boot mode is always going to ask me to root first, wouldn't it make more sense to focus my attention on being able to connect to DooMLoRD's Easy Rooting Toolkit 17 in order to root the device so I can then use the Flash Tool in fast boot mode without any further issues. But that being the case, perhaps I should focus on working out what is happening with the problem Sony Ericsson Seehcri Control Device in Device Manager. Perhaps when that is resolved I will be able to connect to any of the available flash tools.
As far as ROMs and Recovery Environments are concerned, I truly appreciate your advice - and believe me when I resolve this problem I will be sure to run through my rooting plans BEFORE executing them on these very forums - but for now I need to focus on flashing the phone back to stock or somehow connecting the phone to one of the Sony Flash Tools.
Thanks again for your patience and assistance so far and I look forward any more ideas now I have provided a bit more detail.
My sanity hangs in the balance!
BTW, I imagine you are both quite right about what went went wrong in the first instance - I did not appreciate you couldn't flash any ROM once the Xperia T had been rooted. Again, when I resolve this issue, I will describe my exact plans before proceeding. Thanks for clearing that up. I'm learning all the time.
pfhastie said:
BTW, I imagine you are both quite right about what went went wrong in the first instance - I did not appreciate you couldn't flash any ROM once the Xperia T had been rooted. Again, when I resolve this issue, I will describe my exact plans before proceeding. Thanks for clearing that up. I'm learning all the time.
Click to expand...
Click to collapse
Try unlocking bootloader, fastboot flashing boot.img of the rom you want. (before hand get the rom you want on sd or something) And then you should flash without error.
First of all thank you so much for replying. These forums are quite daunting at times and it is good to know someone with some clout is listening. Apologies again for going into yet more detail, but it should help me reach a resolution sooner rather than later.
Click to expand...
Click to collapse
Detail is always good - much better than a "i rooted my phone and now it doesn't work" post. I agree, information is in many different places - very easy for that to happen.
As re the bootloader, I was under the impression that DooMLoRD's Easy Rooting Toolkit 17 would root my stock Xperia T while leaving the bootloader untouched - that is to say locked (as far as I am aware)
Click to expand...
Click to collapse
Yes - that is, if your bootloader was Locked when you started this whole adventure.
Now, I obviously lost root somewhere along the line
Click to expand...
Click to collapse
- Maybe but maybe not!,
but has the bootloader also been changed to unlocked? I don't know, but I wouldn't imagine so, so I can only assume it is still locked.
Click to expand...
Click to collapse
No - the bootloader unlock is a whole process in itself. DoomLord's (fantastic) root kit will root your phone - meaning, it will root your phone's current system, to allow read/write access to the system's files. When you unlock the bootloader, that allows you to write to partitions (kernel aka boot, radio/baseband? etc.)
I have recharged my phone ready to make some fresh attempts at this, but to confirm the current state of my Windows 7 connection, I can only connect to the PC in fastboot (with the blue light turned on after connecting to the machine while pressing volume down). There is definitely an issue with some aspect of the drivers since the Sony ADB Device is recognised as working in Device Manager as soon as I connect the phone, however the bothersome Sony Ericsson Seehcri Control Device is also present with a yellow exclamation mark indicating a problem.
Click to expand...
Click to collapse
Since right now, what you need to be able to do is flash a stock FTF (to get your phone working again), make sure your phone is disconnected from the PC. Drivers --- all you should need is Sony PC Companion installed (which installs base drivers for the phone), and Flashtool (http://forum.xda-developers.com/showthread.php?t=1943886). After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** i dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again. You will need them!!
Now, whether this is actually affecting my use of the Android Flash Tool 0.9.13.0 and the other flash tools, I can't actually say. When I open the Android Flash Tool with the phone connected, the two options available to me are flashmode or fast boot mode.
Click to expand...
Click to collapse
Stop here for a second - For the purpose of flashing an FTF (i.e. getting your phone back to working state), do not connect the phone yet.
When I try to use the flashmode with the (as far as I am aware) Xperia T stock firmware LT30P_9.1.A.1.141_PL.ftf, I simply cannot connect in flashmode when prompted. I am asked to remove the phone then reattach it, but no green light ever shows indicating flashmode, only the blue light indicating fast boot mode.
Click to expand...
Click to collapse
When using Flashmode, don't connect the phone at all - Choose flashmode, then choose the FTF, then wait for it to process the files, then it will pop up to tell you when to connect the phone. And this is very important - make sure the phone is fully OFF, then, hold the VOLDOWN button, then plug the usb cable in - when you see Flashmode start moving along, you can let go of the VOLDOWN button... and put the phone down gently .. you dont want to distrub this delicate process .
When I try to use fast boot mode on the other hand, firstly I am not sure which of the various methods to use - I have of course tried them all, and also I should say both the 32-bit and 64-bit versions of the Flash Tool - but when I do, I am always told that the device needs to be rooted first.
Click to expand...
Click to collapse
This may all depend on your bootloader - if your bootloader is locked, you likely cannot get the phone into Fastboot mode.
Now, this may have something to do with the kernels/firmware/ROMs that I am using (there's no question all the variations confuse me a little) as I assumed it simply wasn't possible to flash via fastboot yet further reading suggests that it should be possible to flash a stock kernel without root access.
Click to expand...
Click to collapse
Right - flashing via fastboot may not be possible right now if your bootloader is locked.
The kernels/firmware I have tried are: stock-7.0.A.3.223-twrp-2.3.3.0.elf; 15102012.img; Sony Xperia T Kernel (Stock) With CWM602; Sony Xperia T Kernel (Stock) With TWRP2500. So perhaps I am not using the correct firmware or kernel (I would like to try the LT30P_9.1.A.1.141_PL.ftf, but cannot see an option to do so via fast boot mode). If this is the case and I am able to identify the correct kernel, then perhaps this "device must be rooted first" notification would no longer happen and the state of the ADB drivers would be largely irrelevant.
Click to expand...
Click to collapse
Yes - let's skip the kernels for now - and get you flashing a fresh FTF so you can start over. I suggest that once the FTF is flashed, and the phone can boot normally, you dial the Service Menu number and look to see if your phone has "Bootloader Unlock Allowed: Yes" or "Bootloader Unlock Allowed: No". -If it says NO, it means NO! There is currently (as of Feb3/2014) no way to get around this. This means your bootloader cannot be unlocked, which means no custom kernels, and no fastboot! Custom ROMS can still be flashed - just those that are Locked Bootloader-friendly (meaning, the custom rom operates just fine/is based on the Stock kernel - whatever version is preferred will be mentioned in the dev's first post of the thread). There are a few.. like XperimenT and T-Hybrid. I like those.
I'm going to be safe and assume yours says No (like mine, because everyone should suffer with me!! ) You can then ROOT the system like you did, then install CWM Recovery for locked bootloaders (v8!! dont use v9 for now), then you can flash a rom or do whatever. If the custom rom you're installing is based on a stock kernel whose version number is different from your phone's base, then you may be able to find kernel zips that are flashable via CWM - since they are stock kernels, the flash will be allowed because they are signed or whatever. Example: Since you're going for LT30p .141 FTF, you're on the 141 kernel. If the rom you're installing says it recommends the .145 kernel, find the LT30P .145 kernel zip. You can flash that right after flashing the ROM. I think that the 141/145 kernels are similar to each other so in this case, you may not even have to flash from 141 to 145. But you will - because you will become addicted to flashing like the rest of us and you will want to observe/compare how the ROM behaves on each.
On the other hand if the flash tool in fast boot mode is always going to ask me to root first, wouldn't it make more sense to focus my attention on being able to connect to DooMLoRD's Easy Rooting Toolkit 17 in order to root the device so I can then use the Flash Tool in fast boot mode without any further issues.
Click to expand...
Click to collapse
I think what it's really asking you is to Unlock Your Bootloader. Unlocking the bootloader is kind of considered a global root (because it allows writing to any partition on the phone.
But that being the case, perhaps I should focus on working out what is happening with the problem Sony Ericsson Seehcri Control Device in Device Manager. Perhaps when that is resolved I will be able to connect to any of the available flash tools.
Click to expand...
Click to collapse
Yes - hopefully above we have tackled that.
As far as ROMs and Recovery Environments are concerned, I truly appreciate your advice - and believe me when I resolve this problem I will be sure to run through my rooting plans BEFORE executing them on these very forums - but for now I need to focus on flashing the phone back to stock or somehow connecting the phone to one of the Sony Flash Tools.
Thanks again for your patience and assistance so far and I look forward any more ideas now I have provided a bit more detail.
My sanity hangs in the balance!
Click to expand...
Click to collapse
Agreed!! Good luck!
Thanks for the considered responses. hhamzah49, I have tried to use the bootloader unlock in the flash tool, but it simply waits for me to connect in flash mode, which is what I am unable to do. There is not even an opportunity of using a SD card since I cannot start the phone either normally or in a recovery environment.
LaZiODROID, you're the man for going into so much detail, and yes I am looking forward to trying out loads of ROMs if possible, however I can't consider such luxuries until I've flashed the phone back to stock! It seems the bootloader probably has a lot to do with it, and I wish I could confirm one way or another if it is locked or not, but I don't see a way to do that in the phone's current state. I bought it from Amazon UK in October or thereabouts, so perhaps that might give you a clue - I would assume it is locked for now, but happy to try the process working on the assumption that it is unlocked if that is likely to help.
I am already using the Flash Tool you suggested and have OKed the drivers signature on Windows 7. I understand about not connecting the phone prior to preparing the flash tool (in flashmode) - and making sure it is fully off by pressing power and volume down until I feel the three vibrations indicating the phone is fully off - but all this seems to be immaterial as I am never able to connect in flash mode. Only the blue light ever appears, never the green one.
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked, however I am ONLY able to connect in fast boot mode so if I am not able to flash via fast boot, I am not sure what other course of action to take.
I think I understand now about the unlocked bootloader and having to source suitable ROMs when the time comes, but not quite there yet.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Anyway, my comatose phone and I remain on standby ready to try whatever it takes.
LaZiODROID said:
Detail is always good - much better than a "i rooted my phone and now it doesn't work" post. I agree, information is in many different places - very easy for that to happen.
Yes - that is, if your bootloader was Locked when you started this whole adventure. - Maybe but maybe not!, No - the bootloader unlock is a whole process in itself. DoomLord's (fantastic) root kit will root your phone - meaning, it will root your phone's current system, to allow read/write access to the system's files. When you unlock the bootloader, that allows you to write to partitions (kernel aka boot, radio/baseband? etc.)
Since right now, what you need to be able to do is flash a stock FTF (to get your phone working again), make sure your phone is disconnected from the PC. Drivers --- all you should need is Sony PC Companion installed (which installs base drivers for the phone), and Flashtool (http://forum.xda-developers.com/showthread.php?t=1943886). After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** i dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again. You will need them!!
Stop here for a second - For the purpose of flashing an FTF (i.e. getting your phone back to working state), do not connect the phone yet.
When using Flashmode, don't connect the phone at all - Choose flashmode, then choose the FTF, then wait for it to process the files, then it will pop up to tell you when to connect the phone. And this is very important - make sure the phone is fully OFF, then, hold the VOLDOWN button, then plug the usb cable in - when you see Flashmode start moving along, you can let go of the VOLDOWN button... and put the phone down gently .. you dont want to distrub this delicate process .
This may all depend on your bootloader - if your bootloader is locked, you likely cannot get the phone into Fastboot mode.
Right - flashing via fastboot may not be possible right now if your bootloader is locked.
Yes - let's skip the kernels for now - and get you flashing a fresh FTF so you can start over. I suggest that once the FTF is flashed, and the phone can boot normally, you dial the Service Menu number and look to see if your phone has "Bootloader Unlock Allowed: Yes" or "Bootloader Unlock Allowed: No". -If it says NO, it means NO! There is currently (as of Feb3/2014) no way to get around this. This means your bootloader cannot be unlocked, which means no custom kernels, and no fastboot! Custom ROMS can still be flashed - just those that are Locked Bootloader-friendly (meaning, the custom rom operates just fine/is based on the Stock kernel - whatever version is preferred will be mentioned in the dev's first post of the thread). There are a few.. like XperimenT and T-Hybrid. I like those.
I'm going to be safe and assume yours says No (like mine, because everyone should suffer with me!! ) You can then ROOT the system like you did, then install CWM Recovery for locked bootloaders (v8!! dont use v9 for now), then you can flash a rom or do whatever. If the custom rom you're installing is based on a stock kernel whose version number is different from your phone's base, then you may be able to find kernel zips that are flashable via CWM - since they are stock kernels, the flash will be allowed because they are signed or whatever. Example: Since you're going for LT30p .141 FTF, you're on the 141 kernel. If the rom you're installing says it recommends the .145 kernel, find the LT30P .145 kernel zip. You can flash that right after flashing the ROM. I think that the 141/145 kernels are similar to each other so in this case, you may not even have to flash from 141 to 145. But you will - because you will become addicted to flashing like the rest of us and you will want to observe/compare how the ROM behaves on each.
I think what it's really asking you is to Unlock Your Bootloader. Unlocking the bootloader is kind of considered a global root (because it allows writing to any partition on the phone.
Yes - hopefully above we have tackled that.
Agreed!! Good luck!
Click to expand...
Click to collapse
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------
pfhastie said:
Thanks for the considered responses. hhamzah49, I have tried to use the bootloader unlock in the flash tool, but it simply waits for me to connect in flash mode, which is what I am unable to do. There is not even an opportunity of using a SD card since I cannot start the phone either normally or in a recovery environment.
LaZiODROID, you're the man for going into so much detail, and yes I am looking forward to trying out loads of ROMs if possible, however I can't consider such luxuries until I've flashed the phone back to stock! It seems the bootloader probably has a lot to do with it, and I wish I could confirm one way or another if it is locked or not, but I don't see a way to do that in the phone's current state. I bought it from Amazon UK in October or thereabouts, so perhaps that might give you a clue - I would assume it is locked for now, but happy to try the process working on the assumption that it is unlocked if that is likely to help.
I am already using the Flash Tool you suggested and have OKed the drivers signature on Windows 7. I understand about not connecting the phone prior to preparing the flash tool (in flashmode) - and making sure it is fully off by pressing power and volume down until I feel the three vibrations indicating the phone is fully off - but all this seems to be immaterial as I am never able to connect in flash mode. Only the blue light ever appears, never the green one.
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked, however I am ONLY able to connect in fast boot mode so if I am not able to flash via fast boot, I am not sure what other course of action to take.
I think I understand now about the unlocked bootloader and having to source suitable ROMs when the time comes, but not quite there yet.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Anyway, my comatose phone and I remain on standby ready to try whatever it takes.
Click to expand...
Click to collapse
bro we got two buttons vol up and vol down. while connecting to flashtool ,holding the vol up key enters fastboot mode, and holding vol down key enters flashmode. if even holding vol down key makes u enter fastboot mode!!! try vol up key. i m just not sure about it. just give it a shot
rough map
romeoofair said:
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
Click to expand...
Click to collapse
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
pfhastie said:
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
Click to expand...
Click to collapse
anyway flashtool is the best sol for your issue bro. hope your device gets back on track soon. sorry i was too lazy to write a long post. so i gave it roughly
pfhastie said:
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
Click to expand...
Click to collapse
try to do a hard reset; (while NOT connected via usb or something) hold power+vol up, it will vibrate 1 time, and then 3 times quick. After that try to connect the usb (NOT while pressing any buttons) and press vol down+power
That should connect it into flashmode.
romeoofair said:
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------
bro we got two buttons vol up and vol down. while connecting to flashtool ,holding the vol up key enters fastboot mode, and holding vol down key enters flashmode. if even holding vol down key makes u enter fastboot mode!!! try vol up key. i m just not sure about it. just give it a shot
Click to expand...
Click to collapse
OK, I'm totally aware that this seems to be the main clincher, if I can somehow get it into flash mode (with green light), but I have tried connecting it pressing every combination of button I can think of, but it only ever connects in fast boot (with blue light). I'm just gonna grab a bite just now, but will try this some more right after and let you know (turning the phone off with one vibration, then three, up and down buttons etc). Thanks again for now.
romeoofair said:
man . you got some real patience to write all those.
Click to expand...
Click to collapse
Thank you. A patient attitude and thorough reply from others is what has kept me coming back to this forum.
its just what i wrote in twoo lines :silly:
Click to expand...
Click to collapse
I disagree.
pfhastie said:
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked,
Click to expand...
Click to collapse
I believe I said "if", not "because". The status was unknown to me. I couldn't say anything certain about your device.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Click to expand...
Click to collapse
Since your phone doesn't boot into a system, I'm not sure if DoomLord's rooting kit will help you. What is there to root? There's no Android system running yet for it to root (right?).
Great news
You beautiful, beautiful people!
I managed to get the phone into flash mode by following your exact instructions to turn the phone fully off when disconnected from the PC (by pressing power & volume up until I felt three vibrations following a single vibration), then connected the phone again WITHOUT pressing the volume down button (as I had always been doing before), then, after the red light came on and the Sony logo appeared, pressing power & volume up again until suddenly the beautiful green light lit up and I was able to flash the phone back to stock firmware (LT30P_9.1.A.1.141_PL.ftf). I lost flashmode the first time because I was so shocked, and there doesn't seem to be time to hang around, but the second time I connected it again the firmware flashed immediately, fairly quickly and without any issues and I am now looking at my freshly started phone and the virgin Sony Android screen.
I have to say this process is unquestionably difficult to explain over the internet, probably because there is no universal implementation of the buttons, but at least once you know how, you are sorted for future problems (of this type at least).
I swear to god, I feel about a stone lighter as this was really hanging over me - not only am I too skint to be worrying about dead phones and warranty issues, but now I feel more secure testing things out, and might even be able to help others in the same predicament in future. I'm not sure if all the excessive detail was warranted, but better to err on the side of caution as a general principle I believe.
My sincere thanks to everyone for helping me out! You have given me a great introduction to the site and I look forward to any and all future communications.
Sadly, I have a pile of crap to attend to, now I know the phone is working, so I will regather my strength for a fresh attempt at rooting the phone (with DooMLoRD Easy Rooting Toolkit 18 For Sony Xperia Devices), installing a recovery environment (CWM v8 as opposed to v9), then flashing a suitable ROM tomorrow evening. I checked my service menu and it states, "Rooting status: Bootloader unlock allowed: Yes," which I trust opens my options a bit more. The two ROMs I am initially wishing to try are CyanogenMod and KitKat, but would be nice to know I could try others without more problems. I am now also aware to backup the TA Partition via the Android Flash Tool 0.9.13.0 before rooting the phone and assume I should hold off reinstalling my Titanium Backups until I am happy with a particular ROM.
I expect this isn't the place to go over these things (although I am quite happy to do so), so I will start a new thread tomorrow to go over my best plan of action.
Thanks again, and I hope this helps out someone else in the same position!
Wicked! Happy flashing. I'm jealous of your unlockable bootloader!
LaZiODROID said:
Wicked! Happy flashing. I'm jealous of your unlockable bootloader!
Click to expand...
Click to collapse
Thank you, LaZiODROID. You've been more than helpful so I trust you don't mind my quickly confirming what I now understand about the bootloader now you have so succinctly brought it to my attention.
I previously hadn't taken into account the state of the bootloader when I tried to flash a ROM, so my failure (Status 7 Error) probably suggests that the bootloader must currently be locked, although it is possible to unlock it on my particular handset (but not yours), is that correct?
All I knew when I used Doomlord's Rooting Kit was that the bootloader would not be affected thus preserving my warranty status, however it would be advisable for me to unlock the bootloader using the Android Flash Tool 0.9.13.0 so I can install custom ROMs without having to worry about special packages like XperimenT & T-Hybrid, is that also correct?
The only final query I have is, if I do unlock the bootloader (using the Android Flash Tool) in order to flash custom ROMs, can I then lock it again for the purposes of my warranty?
I shall assume the bootloader should be unlocked AFTER rooting the device, but BEFORE installing the CWM Recovery Environment.
Thanks again! I will rest easier tonight.
I think hhamzah49 is the hero who got you going with that nice trick (to get you into flashmode)! I guess it turned out that you didn't have driver issues after all.
pfhastie said:
I previously hadn't taken into account the state of the bootloader when I tried to flash a ROM, so my failure (Status 7 Error) probably suggests that the bootloader must currently be locked, although it is possible to unlock it on my particular handset (but not yours), is that correct?
Click to expand...
Click to collapse
Yes. If you're gonna do it, read up (re: backing up your TA, etc.) I have read with bootloader unlocking, you also lose DRM apps like TrackID and the Bravia engine? If you dont use those then you probably won't mind.
All I knew when I used Doomlord's Rooting Kit was that the bootloader would not be affected thus preserving my warranty status
Click to expand...
Click to collapse
Right.
however it would be advisable for me to unlock the bootloader using the Android Flash Tool 0.9.13.0 so I can install custom ROMs without having to worry about special packages like XperimenT & T-Hybrid, is that also correct?
Click to expand...
Click to collapse
There is also the official Sony method of unlocking your bootloader (see the all-in-one thread). Re: ROMS... I guess it's not so much "worrying" about roms like XperimenT/T-Hybrid - they are good roms and they install via CWM recovery just like any other custom ROM, and they will run on an unlocked bootloader. You just have more ROM selection with an unlocked bootloader because you can use the kernels that ROMS like Cyaongen needs.
The only final query I have is, if I do unlock the bootloader (using the Android Flash Tool) in order to flash custom ROMs, can I then lock it again for the purposes of my warranty?
Click to expand...
Click to collapse
Read up to be sure - but I see in Flashtool that there is an FTF for bootloader re-locking (but more importantly it is linked in the all-in-one thread also)... so it sounds like it won't be too hard to re-lock if you need to.
I shall assume the bootloader should be unlocked AFTER rooting the device,
Click to expand...
Click to collapse
Yes so you can back up your TA after rooting?
but BEFORE installing the CWM Recovery Environment.
Click to expand...
Click to collapse
That I'm not certain of. I think that recovery can be installed whether your bootloader is locked or unlocked. For unlocked bootloaders, there are kernels that have recovery built in so you can just fastboot flash one of them.
pfhastie said:
You beautiful, beautiful people!
I managed to get the phone into flash mode by following your exact instructions to turn the phone fully off when disconnected from the PC (by pressing power & volume up until I felt three vibrations following a single vibration), then connected the phone again WITHOUT pressing the volume down button (as I had always been doing before), then, after the red light came on and the Sony logo appeared, pressing power & volume up again until suddenly the beautiful green light lit up and I was able to flash the phone back to stock firmware (LT30P_9.1.A.1.141_PL.ftf). I lost flashmode the first time because I was so shocked, and there doesn't seem to be time to hang around, but the second time I connected it again the firmware flashed immediately, fairly quickly and without any issues and I am now looking at my freshly started phone and the virgin Sony Android screen.
I have to say this process is unquestionably difficult to explain over the internet, probably because there is no universal implementation of the buttons, but at least once you know how, you are sorted for future problems (of this type at least).
I swear to god, I feel about a stone lighter as this was really hanging over me - not only am I too skint to be worrying about dead phones and warranty issues, but now I feel more secure testing things out, and might even be able to help others in the same predicament in future. I'm not sure if all the excessive detail was warranted, but better to err on the side of caution as a general principle I believe.
My sincere thanks to everyone for helping me out! You have given me a great introduction to the site and I look forward to any and all future communications.
Sadly, I have a pile of crap to attend to, now I know the phone is working, so I will regather my strength for a fresh attempt at rooting the phone (with DooMLoRD Easy Rooting Toolkit 18 For Sony Xperia Devices), installing a recovery environment (CWM v8 as opposed to v9), then flashing a suitable ROM tomorrow evening. I checked my service menu and it states, "Rooting status: Bootloader unlock allowed: Yes," which I trust opens my options a bit more. The two ROMs I am initially wishing to try are CyanogenMod and KitKat, but would be nice to know I could try others without more problems. I am now also aware to backup the TA Partition via the Android Flash Tool 0.9.13.0 before rooting the phone and assume I should hold off reinstalling my Titanium Backups until I am happy with a particular ROM.
I expect this isn't the place to go over these things (although I am quite happy to do so), so I will start a new thread tomorrow to go over my best plan of action.
Thanks again, and I hope this helps out someone else in the same position!
Click to expand...
Click to collapse
so my idea about vol up button instead of vol down button worked !!!!!!!! . its usually for entering fastboot mode. i just gave a try :silly:
LaZiODROID said:
I think hhamzah49 is the hero who got you going with that nice trick (to get you into flashmode)! I guess it turned out that you didn't have driver issues after all.
Yes. If you're gonna do it, read up (re: backing up your TA, etc.) I have read with bootloader unlocking, you also lose DRM apps like TrackID and the Bravia engine? If you dont use those then you probably won't mind.
Right. There is also the official Sony method of unlocking your bootloader (see the all-in-one thread). Re: ROMS... I guess it's not so much "worrying" about roms like XperimenT/T-Hybrid - they are good roms and they install via CWM recovery just like any other custom ROM, and they will run on an unlocked bootloader. You just have more ROM selection with an unlocked bootloader because you can use the kernels that ROMS like Cyaongen needs.
Read up to be sure - but I see in Flashtool that there is an FTF for bootloader re-locking (but more importantly it is linked in the all-in-one thread also)... so it sounds like it won't be too hard to re-lock if you need to.
Yes so you can back up your TA after rooting? That I'm not certain of. I think that recovery can be installed whether your bootloader is locked or unlocked. For unlocked bootloaders, there are kernels that have recovery built in so you can just fastboot flash one of them.
Click to expand...
Click to collapse
i feel awesome! Good luck trying roms and stuff!

[Q] Extremely Slow Xperia SP

Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.
bravept said:
Im really sorry for posting this question, but im really really noob at this.
I Have a Xperia SP C5303 with stock Android 4.3 and 12.1.A.1.205 and bootloader locked.
My phone is getting extremely slow at everthing, all applications take huge time to load, sometimes even crash, i cleared all cache on applications, even deleted all my messages (1.5years) and nothing worked. Started in safe mode and its pretty fast.
Im tempted to update my SP to a custom rom 4.4.x or even 5.xx .....but i really dont know nothing about it. Dont know how should i proceed and what steps should i take to backup and prevent any problem in case of something goes wrong.
I already used the "towelroot" and installed SuperSU from google playstore and it says its rooted, but already read somewhere that towelroot doesnt actually really root.
I really really appreciate a huge help on this if possible.
Thank you very much.
Click to expand...
Click to collapse
first of all (search for doing this !! )
take a TA partition backup and then unlock your bootloader .....then install the recoveries on the stock ROM>>then replay to me after that
Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....
bravept said:
Ok. Thank you.
Already did the TA Backup with Backup-TA-9.11, now moving on to search "unlocking bootloader"....
Click to expand...
Click to collapse
I think unlocking your bootloader resets everything so backup your apps for re installation once your are done.
I unlocked my bootloader the good old fashioned way via fastboot :
1 - Check if unlocking possible by typing *#*#7378423#*#* in the dialer and going into Service info > Configuration.
2 - If it says something like Bootloader unlock allowed - Yes then its unlockable. If its already unlocked, it will say something along those line as well.
If neither option appears then it isn't unlockable.
3 - Get the unlock code from Sony after filling the necessary details along with the IMEI no. of the phone.
3 - Open command prompt in the adb & flashboot folder by holding Shift + right click and selecting the "open command window here" option.
4 - Type fastboot.exe -i 0x0fce getvar version to check if device is connected properly.
5 - Type fastboot.exe -i 0x0fce oem unlock 0xKEY. Repalce KEY with the code that was received from Sony and hit Enter.
Alternatively the BLU option in FlashTool can be used to simplify things as it automates most of the above procedure. It can also be used to relock your bootloader.
There's also a new app called Kingo SONY Bootloader Unlock that apparently unlocks your bootloader with one click. Check it out.
I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...
bravept said:
I was doing that at the moment. Im using Fastboot also ....since i didnt find other ways
Already made a copy of everthing i can remember and used Titan backup also.
My phone says "Bootloader unlock allowed : no" , but im still trying doing all the thing....i read somewhere that sometimes works.
At the moment im stuck in connecting the phone in the computer with volume up ...and testing the fastboot getvar version to check if the phone is connected....but stays there....waiting for device...and nothing ...
Click to expand...
Click to collapse
If it says no then dunno what the chances of success are.
Came across this Youtube tutorial : https://www.youtube.com/watch?v=Li8Eim6gugw
Don't know how legit it is since its been posted a few months back and there are no comments at all so please proceed with caution and of course don't blame me if you brick your device
Also did you try the Kingo unlock app I mentioned?
Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...
Just install some 4.4.4 lbl build, for example cm11 by mateo337 is really good and even up-to-date.
You will not be able to unlock the boot loader i had XSP that said no and i was not able to do anything about it.
Dont use 5.x.x builds, they are really outdated and have a lot of bugs.
So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?
bravept said:
Nothing works...cant really connect in Fastboot mode...i tried everthing...even in 3 diferent computers...nothing works.
Dont know if "bootloader unlock allowed : no" means that i cannot enter in fastboot mode....or if im doing something wrong...
Click to expand...
Click to collapse
No you should still be able to enter fastboot mode. Are you using the latest version of FlashTool and have you installed all 3 required drivers? Does your phone show up in device manager when you connect it in fast boot mode?
I am not sure abt the last 2 procedures I posted but the first 2 require your phone to boot into fastboot and stay there till the job's done.
bravept said:
So, then i suppose the next step its to install a LBL Recovery? So i can boot in recovery to flash the custom rom....right?
Click to expand...
Click to collapse
Yeah. Since your phone's rooted now, you can follow a LBL procedure for flashing a custom recovery to allow you to install custom ROMs.
Sent from my Xperia SP using XDA Free mobile app

Categories

Resources