Related
For unlocked bootloaders only!
Please use the recovery now to root any firmware!
http://forum.xda-developers.com/showthread.php?t=1596285
Just flash the SuperSU cwm zip with recovery and your phone will be rooted. To download SuperSU visit this thread:
http://forum.xda-developers.com/showthread.php?t=1538053
Regards
Bin4ry said:
For unlocked bootloaders only!
Download:
http://eddy.uni-duisburg.de/bin4ry/system_xps_prerooted_63fw.img
Connect device in fastboot mode (blue LED).
Open Command prompt and type:
fastboot flash system system_xps_prerooted_63fw.img
This will give you root immediatly after reboot!
A nicer way will come soon. But this should solve first problems
Regards
Click to expand...
Click to collapse
ERRRR u beat me to it
Cholek3 said:
Guys, you're asolutely f***ing amazing. Congrats.
Do you mean Command prompt in ADB or windows?
Click to expand...
Click to collapse
In Windows command prompt. But ou need fastboot installed.
This is only fist shot. If you dont know really what im talking about, then please wait for another image with good instructions
Jozinek said:
I can confirm, that it work, many thanks.
Edit - it work, but i cant downloads anything from Market, so back to stock version without root. Will wait on new kernel
Click to expand...
Click to collapse
If you get market problems go ot Settings -> Apps -> ... -> Search for the market in the list and then delete Data of the App. After that all will work fine.
Regards
Bin4ry said:
In Windows command prompt. But ou need fastboot installed.
This is only fist shot. If you dont know really what im talking about, then please wait for another image with good instructions
Click to expand...
Click to collapse
I know roughly what you are talking about. I know command prompt, although I never used fastboot, as I only owned X10 (until I dropped it and USB port snapped ), so never had to/wanted to unlock bootloader this way. But I want to learn, that's why I am reading all this now, and I need to ask about something I am not sure of.
Just go through the unlock bootloader process and then you will know what fastboot is
After that just type my comamnd with my file in the same directory and you will be done.
Regards
If I were you I would wait till I get ICS on the phone then unlock the bootloader and root the phone.
Quick question. It just wonders me. Sony "supports" unlocking bootloader, which is more dangerous than root. Why rooting is not supported then? Is it because we could unistall third party aplications and Sony has some sort of agreements with them and are obligated by law?
Cholek3 said:
Quick question. It just wonders me. Sony "supports" unlocking bootloader, which is more dangerous than root. Why rooting is not supported then? Is it because we could unistall third party aplications and Sony has some sort of agreements with them and are obligated by law?
Click to expand...
Click to collapse
No you are getting the idea wrong
Long ago we discussed alot with SonyEricsson and together decided this is the best way of doing it.
The reason is simple:
Rooting alone does not give you access to all partitions etc. pp See X10 Forums for that. Sony is very good in hiding partitions
With a bootloader unlock we get fully workable fastboot. We are able to write all partitions and change what we want. (Root too)
Also Sony(Ericsson) is able to track who unlocks and who not AND is able to provide a check mechanism to forbid unlocking of phones which are not owned by the user (for example provider branded phones in contract, the phone is usually property of the provider).
So this is the reason. Unlocked bootloader gives us nearly full access, so no need to worry I am in this game since X10 times (like you or not ?)and we always got the phones working like we wanted.
Our work for CM9 on XPS has started now too.
Regards
Bin4ry said:
No you are getting the idea wrong
Long ago we discussed alot with SonyEricsson and together decided this is the best way of doing it.
The reason is simple:
Rooting alone does not give you access to all partitions etc. pp See X10 Forums for that. Sony is very good in hiding partitions
With a bootloader unlock we get fully workable fastboot. We are able to write all partitions and change what we want. (Root too)
Also Sony(Ericsson) is able to track who unlocks and who not AND is able to provide a check mechanism to forbid unlocking of phones which are not owned by the user (for example provider branded phones in contract, the phone is usually property of the provider).
So this is the reason. Unlocked bootloader gives us nearly full access, so no need to worry I am in this game since X10 times (like you or not ?)and we always got the phones working like we wanted.
Our work for CM9 on XPS has started now too.
Regards
Click to expand...
Click to collapse
See, I was not aware of that "agreement". Now everything seems to make sense. I am android user since I bought X10 back in August 2010. I was more or less following XDA since then as well, but this forum is worldwide community and is almost imposible to keep a track on everything. I would consider myself somewhere between rookie and advanced users. I know how to do certain things (root, how to use ADB, I was changing framwork_res.apk for my own purposes, etc.). My point also is, I am more hardware sort of guy, rather than software. That's why I am glad you guys are here with us.
Will this wipe the phone data or only the system partition ?
Cholek3 said:
My point also is, I am more hardware sort of guy, rather than software. That's why I am glad you guys are here with us.
Click to expand...
Click to collapse
Hehe no problem. I'm hardware and software guy
gbil said:
Will this wipe the phone data or only the system partition ?
Click to expand...
Click to collapse
Well no. But the first step is that you need to unlock bootloader and THIS WILL wipe your data. To flash the systempartition itself will not wipe userdata.
Cholek3 said:
Yes, I agree. But myself, I will wait for root for phones with locked bootloader as well. I assume I will be happy with phone speed, but when CM9 comes out, then I will consider unlockin bootloader.
Click to expand...
Click to collapse
Your choice, i hope too that we will get a nice exploit again soon. But i personally have to time to work on an exploit.
Regards
3Shirts said:
Screw that! There are too many useful reasons for root. My motto:
Got android? Get root!
Click to expand...
Click to collapse
True that, after I heard that you can lock back the bootloader and update it via SEUS or PCC, I'm so gonna root it and true again.
thanks sir at all
every thing is ok bootloader is unlocked now and root is ok
just i face a problem when i restored 340 (programs+games) through titanium backup pro ...... and when opening just only setting application my phone force close setting menu .......i dont know why although i still have 330 mb free in app
thanks in advanced
hasan_abeer said:
thanks sir at all
every thing is ok bootloader is unlocked now and root is ok
just i face a problem when i restored 340 (programs+games) through titanium backup pro ...... and when opening just only setting application my phone force close setting menu .......i dont know why although i still have 330 mb free in app
thanks in advanced
Click to expand...
Click to collapse
So you restored with Titanium. Since Titanium is a Root app and you don't had Root before i think you are trying to restore a backup from another phone.
If you do that you have to assure that you ONLY RESTORE APPS and NOT SETTINGS! Settings from another phone will be most likely incompatible.
So this wil be your problem!
Regards
Bin4ry said:
So you restored with Titanium. Since Titanium is a Root app and you don't had Root before i think you are trying to restore a backup from another phone.
If you do that you have to assure that you ONLY RESTORE APPS and NOT SETTINGS! Settings from another phone will be most likely incompatible.
So this wil be your problem!
Regards
Click to expand...
Click to collapse
thanks sir i do so restore app+data from samsung galaxy note ........what is the best way to restore :
could i reset my phone through setting+pivacy+factory data reset without affecting root or i must reflash this rom in order to save root
thanks again for your hard job
rgrds
hasan_abeer said:
thanks sir i do so restore app+data from samsung galaxy note ........what is the best way to restore :
could i reset my phone through setting+pivacy+factory data reset without affecting root or i must reflash this rom in order to save root
thanks again for your hard job
rgrds
Click to expand...
Click to collapse
Restore only Apps in Titanium not Data! If you factory reset the phone root is still there
Regards
does the super one click work after bootloader unlocked?
unic0de said:
does the super one click work after bootloader unlocked?
Click to expand...
Click to collapse
I don't think it will, otherwise somebody would already confirmed that I think. At the moment the only way is to flash appropriate firmware (only with unlocked bootloader).
Thread cleaned guys.
Constructive posts only, if you want to say thanks then hit the thanks button.
to whom it concern for call recorder over this rom works like a charm both sides very clear and great loud
just use callrecorder by SKVALEX(green color) from market with choosing recording calls from kernel with 2 way recording patch(root required) option
+wav format
enjoy my friends
great thanks to mr Bin4ry for rooting rom
rgrds
I got a new Arc S phone and was told by the seller the OS cannot be changed? Does it mean that you can't upgrade android version to 3 or 4? I never heard this before. Anyway with knowledge on this pls let me know! Perhaps the seller does not know the phone can be rooted! I found out that not all updates are avaliable for the Arc S if they come from different countries.
I found out you need to flash it! Oh dear. Can anyone let me know if this is the right way of doing it? Flashing your phone to install android 4.0 on the phone? Will it just erase your phone so there are not icons etc? Thanks!
ArcSnewbie said:
I got a new Arc S phone and was told by the seller the OS cannot be changed? Does it mean that you can't upgrade android version to 3 or 4? I never heard this before. Anyway with knowledge on this pls let me know! Perhaps the seller does not know the phone can be rooted! I found out that not all updates are avaliable for the Arc S if they come from different countries.
I found out you need to flash it! Oh dear. Can anyone let me know if this is the right way of doing it? Flashing your phone to install android 4.0 on the phone? Will it just erase your phone so there are not icons etc? Thanks!
Click to expand...
Click to collapse
You can upgrade Android to ICS but you can't run another OS such as Windows Mobile on Arc S. The seller may not have made himself clear about this issue.
If you are new to this, just use Sony Update Service and follow the instructions on screen. If you have some knowledge about flashing then you can use Emma or flashtool to flash a ftf file. Note that both methods will wipe you personal data so don't forget to backup your data before flashing.
僕のLT18iから送られてきた
Thanks for replying..I spoke to a representative and they told me too not all countries release updates for the phone! That is very strange! It also told me on my phone that I got the latest software android 2. Won't update anymore.
I have not got an SD card but i will and will try out the sony site to see if it work and then flash if I can't get update from sony site..
So I think I figure it out and I know how to flash too. Thanks!
Yes thanks for telling me I can run windows on it.
Sony releases updates, however operators can limit it. If phone does have branded firmware (firmware, which includes operator side stuff), then you will only receive updates, that operator allows and not Sony global ones.
Also, do not believe everything the sellers say. I have heard all kinds of crap from them, most of it being false.
Hi,
I want to root my xperia z1 compact.
As i read, there are few steps that i need to take before rooting my device - backup TA partition, installing CWM, rooting the device.
Both of the CWM/TA backup require that the device will be rooted but if i will root my device without backing up the TA partition i cant go
back and reinstall the stock rom.
What is the correct order of the rooting process?
If the rooting process will get done correctly can i reinstall my stock rom back(for warranty issues)?
What are the downside for rooting - i want it mainly for Titanium backup and the Lba apps?
Thanks for any help!
http://forum.xda-developers.com/showthread.php?t=2642081
http://forum.xda-developers.com/showthread.php?t=2634196
If you follow the guide, you should be able to root without Unlocking Bootloader (Which will cause you loosing TA if you Unlock bootloader first)
So, the best way is to Root (Without unlock bootloader) which is in the guidance, then Backup TA, then you can unlock bootloader if you like (to install ROM or other tweaks).
For myself i just need root so i kept the Bootloader lock and have a backup TA just in case.
thermalboyz said:
http://forum.xda-developers.com/showthread.php?t=2642081
http://forum.xda-developers.com/showthread.php?t=2634196
If you follow the guide, you should be able to root without Unlocking Bootloader (Which will cause you loosing TA if you Unlock bootloader first)
Click to expand...
Click to collapse
If i understood correctly, i will be flashing other rom(previous version in which the root witout unlooking bootloader exploit exsist), to my device.
what will be the effects on my device? will i lose my current device configurations - apps/settings/localization/...? where this change wil be noted?
The process is very complicated and with a lot of "Brick" possibilities, will a more noob friendly version should be expected soon?
Yes you will lose your data as stated in the guides. There isn't really any brick potential, if you screw something up you should always be able to start over again.
As long as there is no other exploit, there won't be an easier method.
cohena said:
If i understood correctly, i will be flashing other rom(previous version in which the root witout unlooking bootloader exploit exsist), to my device.
what will be the effects on my device? will i lose my current device configurations - apps/settings/localization/...? where this change wil be noted?
The process is very complicated and with a lot of "Brick" possibilities, will a more noob friendly version should be expected soon?
Click to expand...
Click to collapse
Hi,
I've rooted my Z1C successfully 2 weeks ago with this guide: http://forum.xda-developers.com/showthread.php?t=2642081
At step 18 you had to do a factory reset... You should always create a backup. But you're are right, this guide could be more noob friendly
I wish there were some screenshots or more detailed explanations, because after I flashed the first file, I only could see a black screen, a white symbol photo of the Z1C with some japanese (?) characters and the phone doesn't do anything... Can't turn off, can't exit this screen... I was shocked until I see a home screen
D_R_Z_87 said:
[..] But you're are right, this guide could be more noob friendly
I wish there were some screenshots or more detailed explanations, because after I flashed the first file, I only could see a black screen, a white symbol photo of the Z1C with some japanese (?) characters and the phone doesn't do anything... Can't turn off, can't exit this screen... I was shocked until I see a home screen
Click to expand...
Click to collapse
If you have some concrete tips I'll be happy to edit the guide
zxz0O0 said:
If you have some concrete tips I'll be happy to edit the guide
Click to expand...
Click to collapse
Hi,
in my situation it would have been helpful to know following things:
- is it ok to rename the downloaded .ftf files from .zip to .ftf ? --> in my case it was ok, because the windows explorer automatically saves the .ftf file as .zip (also .apk files). --> in your guide, post #8, you wrote that this is not ok.
- as i already wrote in my last post, i thougt my phone got bricked after flashing the first file...
- i got stuck at step 13, installing dualrecovery and got the message "Waiting for device to connect" - in my case everything was configured right on my computer, already checked your tips, but it doesn't work until the fifth restart of my phone... maybe you should also suggest a few restarts when the phone would not be recognized
i've rooted several samsung and google nexus devices, but this phone...
but in general, your guide is really good and helped me!
zxz0O0 said:
If you have some concrete tips I'll be happy to edit the guide
Click to expand...
Click to collapse
I will take few days to better understand the process and then i will follow the guide's suggestions, i will post my experience
using the guide after the hopefully successful ending....
Two questions:
how do i do a "factory reset"?
I have no data to lose, so data loss is not an issue for me....
At the hopefully successful ending of the guide which rom do i have?
I want to get back the same device experience i begen the rooting process with....
cohena said:
I will take few days to better understand the process and then i will follow the guide's suggestions, i will post my experience
using the guide after the hopefully successful ending....
Two questions:
how do i do a "factory reset"?
I have no data to lose, so data loss is not an issue for me....
At the hopefully successful ending of the guide which rom do i have?
I want to get back the same device experience i begen the rooting process with....
Click to expand...
Click to collapse
Great :good:
I rooted and unlocked the bootloader right after I bought the phone so data loss was also not a problem for me.
Factory reset is located in Recovery Menu under 'Wipe data/factory reset'.
In the end you will have an unbranded UK firmware with root access. There isn't really any difference.
zxz0O0 said:
In the end you will have an unbranded UK firmware with root access. There isn't really any difference.
Click to expand...
Click to collapse
What do you mean there is no difference?
What are the diffrences between firmwares? what does firmware means- kernal maybe?
I need to understand if having the uk firmware will cahnge my current "device expereince" - gui, localization. preinstalled apps, or it is
just a change to the os itself without any imapct on the current user interface.
cohena said:
What do you mean there is no difference?
What are the diffrences between firmwares? what does firmware means- kernal maybe?
I need to understand if having the uk firmware will cahnge my current "device expereince" - gui, localization. preinstalled apps, or it is
just a change to the os itself without any imapct on the current user interface.
Click to expand...
Click to collapse
Pretty sure there is no difference in the kernel. There might be a difference in the pre-installed apps or modem, I don't know your current rom so I can't answer that. In the end you won't notice any difference.
cohena said:
Hi,
but if i will root my device without backing up the TA partition i cant go back and reinstall the stock rom.
Click to expand...
Click to collapse
Yes you can!
cohena said:
If the rooting process will get done correctly can i reinstall my stock rom back(for warranty issues)?
Click to expand...
Click to collapse
Yes.
cohena said:
What are the downside for rooting
Click to expand...
Click to collapse
NON!
cohena said:
what does firmware means- kernal maybe?
Click to expand...
Click to collapse
Firmware is basically the OS, Gingerbread, Icecream Sandwich, Jellybean, Kitkat, and the main difference between a UK ROM and a Global ROM for example might only be one or two apps at the most.
cohena said:
I need to understand if having the uk firmware will cahnge my current "device expereince" - gui, localization. preinstalled apps, or it is
just a change to the os itself without any imapct on the current user interface.
Click to expand...
Click to collapse
Sony's UI looks the same on an ROM (that is the same Firmware), and if you need to flash a new ROM to root then chances are you will loose whatever you haven't backed up.
zxz0O0 said:
Pretty sure there is no difference in the kernel. There might be a difference in the pre-installed apps or modem, I don't know your current rom so I can't answer that. In the end you won't notice any difference.
Click to expand...
Click to collapse
Thanks for your help so far...
The preinstall apps does not concern me - most of them i will remove anyway...
The modem part sounds problematic....
My build is 14.2.A.1.114, where can i found the rom/modem version data?
cohena said:
Thanks for your help so far...
The preinstall apps does not concern me - most of them i will remove anyway...
The modem part sounds problematic....
My build is 14.2.A.1.114, where can i found the rom/modem version data?
Click to expand...
Click to collapse
You don't need to care about that... Just follow the guide you won't notice anything different.
If you are scared so much you could create a ftf of your stock rom (there are guides on the forum).
zxz0O0 said:
You don't need to care about that... Just follow the guide you won't notice anything different.
If you are scared so much you could create a ftf of your stock rom (there are guides on the forum).
Click to expand...
Click to collapse
Let summerize the procedure so far :
1. I will create a ftf image of my stock rom using the guide that i found, here :
http://forum.xda-developers.com/showthread.php?p=35910775
in the "How to backup your Sony Ericsson Xperia firmware using Update Service and the FlashTool" video.
In that guide the end result is a ftf file and the root guide asks for zip file, how can i get the zip file from the ftf one?
2. I will root my xz1c as the guide suggests here :
http://forum.xda-developers.com/showthread.php?t=2642081
3.ABOUT THAT I AM NOT TOO SURE : on step 19 on sub step 1, i will instal my device ftf instead of the uk one and continue
with the rest of the other 2 sub steps.
Am i correct?
If i am flashing back my device rom or the uk rom at the end of the procedure and both roms are unrooted, how come the device is rooted?
After rooting the device how can i unroot or reroot if needed - i will have to go all the way again?
No.. I meant that you can create a ftf of your stock rom if something would be wrong with the UK one you could flash your old one.
But this won't even happen because the ROMs are almost the same! I don't understand what you are scared about.
There are people from many countries using this UK firmware and no one complained yet.
zxz0O0 said:
No.. I meant that you can create a ftf of your stock rom if something would be wrong with the UK one you could flash your old one.
But this won't even happen because the ROMs are almost the same! I don't understand what you are scared about.
There are people from many countries using this UK firmware and no one complained yet.
Click to expand...
Click to collapse
Ok, so no going back....
After having my device rooted with the uk rom, how cam i localize(keyboard, lang, cell operators, etc....),
the device to my country?
And again with the logical question - if at the end of the process i am flashing an unrooted rom that i flashed at
the beginning of the guide, how can the device be rooted?
I have just been notified that my device is going to get updated to Android ver 4.4.2(KitKat) today/tomrrow, does it changes anything regarding the root procedure?
cohena said:
Ok, so no going back....
After having my device rooted with the uk rom, how cam i localize(keyboard, lang, cell operators, etc....),
the device to my country?
And again with the logical question - if at the end of the process i am flashing an unrooted rom that i flashed at
the beginning of the guide, how can the device be rooted?
Click to expand...
Click to collapse
You just select your language in android, like you normally do
UK firmware does not mean there is only english. There are still all languages available.
In the end you are flashing a zip file (step 19.1), that zip file has root installed.
I am working on updating the guide for KitKat.
zxz0O0 said:
You just select your language in android, like you normally do
UK firmware does not mean there is only english. There are still all languages available.
In the end you are flashing a zip file (step 19.1), that zip file has root installed.
I am working on updating the guide for KitKat.
Click to expand...
Click to collapse
You right!
We need root our lovely Z1c device...
zxz0O0 said:
I am working on updating the guide for KitKat.
Click to expand...
Click to collapse
Ok, so Should i upgrade to kit kat or wait for the root guide?
Recently, Xperia Acro S was been removed from the Unlocking Bootloader list on the Official Sony site.
As maintaining a thread on Acro S section, some of my friends were unable to unlock their bootloader due to missing device in the list.
So, I Emailed Sony few weeks ago requesting them to re-list Acro S, and they said, they'll look at this. Now its been Re-listed.
I have even attached three screenshots for your conformation. So see it, Just check out below three links,
SS-01 || SS-02 || SS-03
For those who were waiting to unlock their phone, here's a good news for you all. Go ahead and get the unlock code from official Sony site providing them your IMEI.
1. To Get Unlock Code just click HERE!
2. Unlocking Bootloader step-by-step Guide, just click HERE!
Regards,
hitman-xda
As I said, I'll notify you after Acro S is re-listed, I'll mention you here; @bluvn || @sky202_how89 || @els_sand
Wow, Thanks for the surprise! U make my days!
sky202_how89 said:
Wow, Thanks for the surprise! U make my days!
Click to expand...
Click to collapse
That sounds good
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
sky202_how89 said:
Hey but too bad is I totally brick my phone. Almost all of the solution found by google seems no used.
Out of surprise, it happened for most of the Xperia Phones who are heavy flashing with custom ROM.
Check out the thread here: http://forum.xda-developers.com/xperia-s/help/xperia-acro-s-sim-card-service-detect-t3200650
Now my XAS is becoming a powerful MP4 Player. What a desperate. ;( ;(
Click to expand...
Click to collapse
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
hitman-xda said:
Did you checked weather your Bootloader is unlocked? If not then check it.
Also try to repair your phone through PC companion.
Its a strange problem. Hearing it first time.
Did you followed exact procedure of the Guide that I linked?
I don't think it occurs due to heavy flashing of ROMs, because I have used every ROM available for the phone for almost 100 times. I usually change my ROM after a month.
Click to expand...
Click to collapse
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
sky202_how89 said:
The problem occurred when the user try to flash back to stock ROM from Custom ROM.
The Bootloader is unlocked.
Now the BL appear to be like this: Bootloader Unlock Allowed = No (*#*#7378423#*#*)
Enter fastboot fail (No fastboot detected), Only Flash is allowed.
To install CWM or TWRP required fastboot, so I can't do anything besides keep trying to flash wiith different version of stock FTF.
Solution I tried but failed:
- Fix using Sony PC Companion (PCC)
- Flash any version of stock ROM, inclusive of just flashed the "Baseband" only.
- Flash Acro-HD S0-03D ROM then flash back to stock ROM.
- *#*#4636#*#* -> Phone information -> Set preferred network type (any of the option & reboot)
- Settings -> More -> Mobile Networks -> Network Mode(any option & reboot)
- Settings -> More -> Mobile Networks -> Select providers (automatic or manual), it manage to detects the service providers but registered on the network failed.
- Insert other active SIM Card
I try to locate the Antenna Board but it seems like it was attached with the mainboard. Unlike Xperia Z, the Antenna Board is seperated.
I assume this problem occurred when the partition accidentally bricked by Flashtool? I did try to flash different version of Baseband, nothing seems work.
I need someone favors. Create a Pre-rooted Stock ROM(.ftf) with Recovery Accessed (CWM or TWRP).
I found somewhere from this forum stated that tried to install back any of the Custom ROM to fix the No Signal Issue which it appeared to be my last hope. Without Recovery(Required Fastboot to install), I couldn't install any custom ROM.
Click to expand...
Click to collapse
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
hitman-xda said:
First of all let me clear that 'Unlocking Bootloader Allowed = No'
That means you cannot unlock it unless your coming to stock from other ROM.
Also Bootloader can be unlocked only once. So if your coming back to stock from custom, why did you tried to unlock your BL again?
Even if you flash stock ftf, you no need to unlock your BL again.
Click to expand...
Click to collapse
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
Secondly, don't try to flash other ROMs into your phone, you could mess up everything, even hard brick.
Your Fastboot mode isn't working, right? If so, then try to install fastboot drivers from flashtool driver pack. Maybe it could work.
Click to expand...
Click to collapse
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
sky202_how89 said:
I did not lock my BL, it just lock back by themselves. I still remember I unlock my BL with Sony Official way in 2013. After that, I did not touch that BL again. It's just after the recent flash which I did the same way like before(Custom to stock ROM), everything mess up.
I even format my pc which I thought it was my pc issue earlier. But ends up I realize it was something regarding to my BL. With BL Unlock Allowed: No, you cannot enter to your bootloader or fastboot.
This video is showing exactly my problem now:
Other thread that I discovered with same issue as I am:
http://forum.xda-developers.com/showthread.php?t=2432566
http://forum.xda-developers.com/xperia-z/help/xperia-z-signal-drops-unable-to-connect-t2183045
My very last but not recommended solution is to change the motherboard. However, looking at the posting not only me having the issue and it mostly happened when users are flashing back from Custom ROMS to Stock ROMS.
Changing motherboard is like changing another phone, your feeling towards the phone changed.
Click to expand...
Click to collapse
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
hitman-xda said:
After flashing stock ftf, the BL status always shows 'Bootloader Unlock Allowed = No' but it is actually unlocked. So it does not get relock after flashing stock ftf.
It seems like a serious problem.
Maybe, flashing other ROM will help you a bit. For that Obviously your phone must enter into fastboot mode (which is not happening). In this case did you use 'dd' command for installing recovery? If not then you could try it. And I think you'll be succeeded to install recovery and further you can flash ROM.zip through recovery.
You just need to copy recovery.img into your internal memory and enter some command's using adb shell.
Click to expand...
Click to collapse
I will try & let you know soonest. Kinda busy this few days.
---------- Post added at 05:35 PM ---------- Previous post was at 05:32 PM ----------
Mirhawk said:
You must have used a newer version of flashtool. This is causing similar issues for many people. The only solution for now seems going to Sony service center. There is another method too, flashing the TA backup, but I don''t know if it works or not.
Click to expand...
Click to collapse
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
---------- Post added at 05:41 PM ---------- Previous post was at 05:35 PM ----------
Latest UPDATE about the issue, PLEASE TAKE NOTE BECAUSE YOU'RE ABOUT TO BRICK YOUR PHONE JUST LIKE ME. THIS IS IMPORTANT!
@hitman-xda , Please pass this message around. Btw, How to quote the name?
If everyone here in this post flashed their phones with Flashtool 0.9.19.x version, then congrats my friends, we're all become owners of bricked phones with no network signal. Flashtool 0.9.19.x versions have sript error which replaces original Ta partition leading to unlocked bootloader to become locked and loss of network signal. If you're guys haven't backuped your Ta partition prior to bootloader unlocking then that's all.
Check here http://forum.xda-developers.com/show...68&postcount=4 and here http://forum.xda-developers.com/show...postcount=2758
Click to expand...
Click to collapse
http://forum.xda-developers.com/xpe...ice-detect-t3200650/post62904161#post62904161
sky202_how89 said:
YES, I am flashing with NEWEST VERSION of Flashtool. After that, the result turned nagative.
Do you mean TA Partition? Do you have a backup copy of it?
Click to expand...
Click to collapse
Flashing with latest flashtool flashes a partition which renders modem of the phone useless. Yes, I mean the TA partition. Each phone's TA partition is unique, so if You flash mine or other person's TA partition, Your phone would not even boot.
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
sky202_how89 said:
This is toooooooooooooooooooooooooooo OVER! It means my phone is bricked forever.
It's their mistake but we have to bear it on our owns.
Click to expand...
Click to collapse
Did nothing worked?
hitman-xda said:
Did nothing worked?
Click to expand...
Click to collapse
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Androxyde said:
On 0.9.18.X, even if simlock is included, it is excluded from flashing
On 0.9.19.5 I did this way :
- simlock is excluded by default with a warning when including it (unticking button)
- When simlock is included, when flashing, a YES/NO box appears asking if you are absolutely sure you want to flash this unit.
- When creating bundles, simlock can be included (no risk with 0.9.18 as it is always ignored)
So if you have a TA backup, with 0.9.19.5 you can restore the 07DA unit (then reactivating the phone). Thing you cannot do with any previous release as 07DA unit is hardcoded_excluded.
I will publish another patch that will backup any TA unit that is about to be flashed. That way there will always be a solution to come back to the previous state.
simlock, if present, is always ignored in 0.9.18 release
simlock, if present is excluded by default with the ability to include it with a warning and a user query before flashing the unit
people who had issues are ones using ftf bundles created prior to 0.9.18 with simlock included. Never had issues on 0.9.18 as it is excluded by default, I forget to keep this exclusion on 0.9.19.[1234] and added a defautl exclusion on .5 with the ability to include it anyway.
But maybe it is not the right way ... I was asking myself when I did it. I want to give the ability to restore 07DA unit if ever a backup exists
The only way to recover from locked phones is to reactivate them in a service center or to restore the 07DA unit.
Click to expand...
Click to collapse
sky202_how89 said:
Yes, nothing worked because Flashtool just accidentally bricked our Sony in the whole world. A careless mistake destroy the phone.
In 0.9.18.X, simlock.ta is always excluded by default but a careless mistake on the version 0.9.19.(1234) (at that time), The Simlock.ta is included while flashing. Each phone TA has their own unique number. Besides changing the mianboard (the only solution right now), no ones manage to solve this issue.
I wonder how many Sony phone in the world has already been bricked by this Flashtool update.
Click to expand...
Click to collapse
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
hitman-xda said:
Well, that is disappointing
Hard to believe, that Sony really did that serious change in its software.
Click to expand...
Click to collapse
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
sky202_how89 said:
At least you're out of trouble. I suggest you need to backup your TA Partition just in case.
Each TA is unique and cannot be transferred.
If your TA is used by 3rd party, they may face a Hard Brick & cannot be recovered anymore.
Well, this is an added Security by Sony. They are not stupid to "share" openly for free.
Now I'm realize.
Click to expand...
Click to collapse
I can't do that. Coz I have already unlocked my bootloader months ago
hitman-xda said:
I can't do that. Coz I have already unlocked my bootloader months ago
Click to expand...
Click to collapse
That's bad but still not too late. Your next Sony in future will be secured
I'm already ordered the replacement mainboard.
What kind of mainboard-Lock BL or Unlock BL, I do not know because it's not a new one.
Waiting for shipment.
How to unlock bootloader on Sony Xperia M5.
How to unlock bootloader
1.In http://developer.sonymobile.com/unlockbootloader/ choose Sony Xperia M2.
2.Submit Email
3.Submit IMEI
4.And unlock bootloader with intruction.
You get the code? Then we continue.
Download the latest version here or Flashtool http://www.flashtool.net/downloads.php
After installation, go the path C: \ Users \ username \ .flashTool \ registeredDevices here and create a folder with the code-name of your machine (you can find out if flashtool click on BLU and see where in the log are in line «Current device» for example, in line 09/045/2015 23:45:08 - INFO - Current device: C2104 - AB100C2DE3 - 1272-4136_R5B - 1269-5420_15.3.A.1.17 - WORLD-a_15.3.A.1.17 code machine will AB100C2DE3. Code which will write your name and location).
Later in this folder, create a text file and name it «ulcode» (without the quotes). Open, and in it write your unlock code, that you have on the site Sony. Save. Write code very carefully.
Now open flashtool and press the BLU. If everything is correct, in line you should write your code, pressing unlock. All should be ready to unlock.
Working on:E5633
I am not responsible for the broken device. Whatever you do, you do at your own risk
After unlocking bootloader will void the warranty
I forgot write. I get unlock code with my IMEI.
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
ykphuah said:
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
Click to expand...
Click to collapse
I think, in service centre check bootloader. If bootloader not unlocked, warranty is valid.
This method is working also on M5 dual, 6533
But the next step should be how to gain the root =)
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
ykphuah said:
Interesting, I checked my Rooting Info as per the guide and it does say allowed.
I think giving Sony my IMEI will potentially void my warranty claims? Let me think about it.
Click to expand...
Click to collapse
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
vsm778 said:
This method is working also on M5 dual, 6533
But the next step should be how to gain the root =)
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
Click to expand...
Click to collapse
Maybe 5633 ?
DukeMcWood said:
Maybe 5633 ?
Click to expand...
Click to collapse
yep, you're right, thanks
hello guys. when you unlock bootloader, can you than record 4k video in H.264 not H.265 and upload it to youtube?
vsm778 said:
This method is working also on M5 dual, 6533
Probably no.
You could reLock your device from flashtool simply, before visiting the service center.
Click to expand...
Click to collapse
Yes, you can relock your bootloader with Flash Tool but your DRM keys are gone forever, proprietary Sony features won't work even after relocking...
Also, it's veeeeeery unlikely, but they may check if your DRM keys still exist in Sony Service Center, in case they don't find them they'll know you've unlocked your bootloader...
How about port TWRP or CWM on Xperia M5 ? If we port recovery, we can get root.
mbc07 said:
Yes, you can relock your bootloader with Flash Tool but your DRM keys are gone forever, proprietary Sony features won't work even after relocking...
Also, it's veeeeeery unlikely, but they may check if your DRM keys still exist in Sony Service Center, in case they don't find them they'll know you've unlocked your bootloader...
Click to expand...
Click to collapse
I think there's a way to do it by backing up the TA partition. That's how Sony Xperia Z1 started. We root, unlock bootloader, backup TA and when we relock, we can actually restore the TA and DRM key
firdyRAY said:
I think there's a way to do it by backing up the TA partition. That's how Sony Xperia Z1 started. We root, unlock bootloader, backup TA and when we relock, we can actually restore the TA and DRM key
Click to expand...
Click to collapse
Err, no. To preserve your DRM keys you need a way to root without unlocking the bootloader (e.g. using an exploit), then you make a backup of your TA partition which will contain your DRM keys. If you unlocked your bootloader without a taking a TA backup first, your DRM keys are gone forever, even if you root your device afterwards and make a backup of your TA partition you won't have any keys at all because they already were wiped when you unlocked the bootloader, this applies to any Sony device.
In other words, currently there's no way of unlocking M5 bootloader and keeping your DRM keys, the hope is Xperia Z5 series or other flagship devices, they draw attention of many developers and like what happened with Z2 and Z3, for example, locked bootloader users probably gonna start a bounty or some kind of incentive for a way to root the locked variant of those flagships, eventually they'll find an exploit that probably can be ported to other devices with less development activity, like Xperia M4/M5.
It's the cat-and-mouse game, new flagships are released, devs will research possible exploits to those new flagship devices and when one is found it's very likely to work with most devices released at the same time (and that probably are unpatched too). Also, in Sony devices, if you have root in one firmware version, you'll automatically have root in any new firmware too (using tools like PRFCreator or dd Flasher)...
(as record, towelroot, developed originally for Galaxy S5, could be used in a lot of Xperia devices from that time, and the Xperia Z3 exploit was successfully ported to Xperia E3 as well and could probably be used in similar devices released around the same time like Xperia C3 and others)
Thank you! What's the chance of the M5 properly supported by custom rom, like FreeXperia and CyanogenMod?
optionalmgrr.la said:
Thank you! What's the chance of the M5 properly supported by custom rom, like FreeXperia and CyanogenMod?
Click to expand...
Click to collapse
I dont know. But, I want port flyme os from meizu devices.
camping here to get notified of root asap..
DukeMcWood said:
How to unlock bootloader on Sony Xperia M5.
How to unlock bootloader
Click to expand...
Click to collapse
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Ketansa said:
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
I dont know about 6.0, because i dont have 6.0. In the near future i maybe port recovery. But i dont have original recovery.img from Xperia M5 for port.
mbc07 said:
Err, no. To preserve your DRM keys you need a way to root without unlocking the bootloader (e.g. using an exploit), then you make a backup of your TA partition which will contain your DRM keys. If you unlocked your bootloader without a taking a TA backup first, your DRM keys are gone forever, even if you root your device afterwards and make a backup of your TA partition you won't have any keys at all because they already were wiped when you unlocked the bootloader, this applies to any Sony device.
In other words, currently there's no way of unlocking M5 bootloader and keeping your DRM keys, the hope is Xperia Z5 series or other flagship devices, they draw attention of many developers and like what happened with Z2 and Z3, for example, locked bootloader users probably gonna start a bounty or some kind of incentive for a way to root the locked variant of those flagships, eventually they'll find an exploit that probably can be ported to other devices with less development activity, like Xperia M4/M5.
It's the cat-and-mouse game, new flagships are released, devs will research possible exploits to those new flagship devices and when one is found it's very likely to work with most devices released at the same time (and that probably are unpatched too). Also, in Sony devices, if you have root in one firmware version, you'll automatically have root in any new firmware too (using tools like PRFCreator or dd Flasher)...
(as record, towelroot, developed originally for Galaxy S5, could be used in a lot of Xperia devices from that time, and the Xperia Z3 exploit was successfully ported to Xperia E3 as well and could probably be used in similar devices released around the same time like Xperia C3 and others)
Click to expand...
Click to collapse
That's very lengthy but good to know. Thank you!
Ketansa said:
Hello Duke,
On Sonymobile page for M5 it is showing that it is due to update to Android 6.0 Marshmellow which is coming soon.
So what do you think? I heard root isnt possible on Android 6.0 , and if rooted they will make it hard for the users.
Is it going to be well? or Rooting is history?
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
Well i personally don't trust any advice from any other source except for XDA just to be safe because we the internet have too many smart alecks who know nothing and try to act smart by being sarcastic. So i guess the safest thing to do is to check on XDA for root methods and go through the forum to see if it works for others
Ketansa said:
p.s - When I asked a youtube user for the bootloader for M5, he said " root method has been out for months, it would be great if you can put Google to use. no offense". Is this true? whats going on?
thank you.
Click to expand...
Click to collapse
I don't think he have a rooted M5. Before we get root, we must unlock the bootloader first, and this is the part that is not done yet.
firdyRAY said:
That's very lengthy but good to know. Thank you!
Well i personally don't trust any advice from any other source except for XDA just to be safe because we the internet have too many smart alecks who know nothing and try to act smart by being sarcastic. So i guess the safest thing to do is to check on XDA for root methods and go through the forum to see if it works for others
Click to expand...
Click to collapse
Hello Thank you,
Yes you are right, may be he is being Sarcastic or some kind of adware developer for corporates.
Looking in XDA forums.