This thread has been moved to http://forum.xda-developers.com/xperia-e1/general/xperia-e1-rooting-flashing-recovery-t3051225
Xperia E1 has his own Subforum now, Thank you XDA!
If any moderator sees this, please close this thread!
Hello there!
First of all really thank you for making this topic, it will really help people who wants to customize their Xperia E1.
I really appreciate your action.
Secondly, I wanted to ask more help with the bootloader unlock.
I do exactly what you do but it always comes the following result;
First, when I click on unlock it gives me Failed error.
When I click on unlock for second time, it gives me Okay, meaning that successfully unlocked.
After, I'm booting into system but it stack at the boot animation.
Some people called this bootloop but I don't know what to do to fix it.
Flashing again a stock firmware fixes this but no unlocked bootloader at all.
Repeating this will give the same results.
I would like some help on it, I remember somehow I had successfully unlock the bootloader without stack at boot animation.
At service menu was saying boot loader unlock: Yes
Instead of bootloader unlock allowed: Yes
I'm able to give any information about my phone so we can fix the problems, I'm not going to buy another phone anyways
Sent from my D2005 using XDA Free mobile app
Kizoky said:
Now hold the following buttons on the phone: POWER+VOLUME DOWN
Do this until the LED turns GREEN.
Great, the phone is now in Flashmode!
Click to expand...
Click to collapse
You are supposed to VOLUME DOWN + CONNECT USING USB and you should NOT hold the power button.
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
GiorgosGRN said:
Hello there!
First of all really thank you for making this topic, it will really help people who wants to customize their Xperia E1.
I really appreciate your action.
Secondly, I wanted to ask more help with the bootloader unlock.
I do exactly what you do but it always comes the following result;
First, when I click on unlock it gives me Failed error.
When I click on unlock for second time, it gives me Okay, meaning that successfully unlocked.
After, I'm booting into system but it stack at the boot animation.
Some people called this bootloop but I don't know what to do to fix it.
Flashing again a stock firmware fixes this but no unlocked bootloader at all.
Repeating this will give the same results.
I would like some help on it, I remember somehow I had successfully unlock the bootloader without stack at boot animation.
At service menu was saying boot loader unlock: Yes
Instead of bootloader unlock allowed: Yes
I'm able to give any information about my phone so we can fix the problems, I'm not going to buy another phone anyways
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
I have the same problem. Your career force-locked the phone, meaning that you cannot unlock it normally, only temporarily (that means when you do it the second time it says OKAY but when you reboot the device its gonna be locked again)
I got an email from my career, and they say the reason why I cannot unlock it is because of the firmware. I'm starting to think they don't know a thing about bootloaders.
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
GiorgosGRN said:
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
Some careers (like mine, Orange) trick the user, they say Unlock Allowed: Yes. It's actually kinda true, because you can temporarily unlock it, but thinking about it our situation is the same as if that message would say No. If there would be test points on the E1 maybe we could unlock it like the older devices, but I'm not sure as it's quite old. Maybe if someone can make a hack to set the flag of locking to unlocked or make a 2ndinit ability to load a second kernel on the bootup process.
I think it would be possible, but it would require a lot of work and a large knowledge of our device (in a deeper meaning)
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
mire777 said:
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
Click to expand...
Click to collapse
You need to reflash the firmware. Kizoky will sure add that later on.
mire777 said:
My phone says:
Bootloader unlock allowed: No.
So i can't unlock?
What should i do if i stuck on bootloop with unlocked bootloader, for some reason?
Need tutorial for this..
Thanks.
Click to expand...
Click to collapse
If you brick your phone, you can always reflash the Firmware, or use the backup method which is found in PhilZ recovery.
I'll do a tutorial on this too soon
So..uhm.. Any chance I can root my phone without bricking it with this bootloader stuff ?
Was rooted using Kingo, latest update (20.A.1.2.14) removed root, prevents kingo and all other apps from rooting again.
GiorgosGRN said:
God..So we will never unlock the bootloader of force locked E1 devices?
Edit: I read that force locked bootloaders come with the message at service menu:
Bootloader Unlock Allowed: No
My phone says:
Bootloader Unlock Allowed: Yes
Any ideas? Am I wrong?
Sent from my D2005 using XDA Free mobile app
Click to expand...
Click to collapse
As far as I know if it's says Allowed: Yes, as long as you obtain to code to unlock, along with using xperia flasher or fastboot tools to correctly unlock then it's should stay unlocked. An unlock allowed: No should not allow a request for unlock code via sony developer world site.
---------- Post added at 08:09 PM ---------- Previous post was at 07:55 PM ----------
Kizoky said:
If you brick your phone, you can always reflash the Firmware, or use the backup method which is found in PhilZ recovery.
I'll do a tutorial on this too soon
Click to expand...
Click to collapse
I made a backup zip, that way if you use fastboot tools to flash the boot.img, then the kernel has the philz recovery 6 that can install the clone rom.zip file.
image45 said:
As far as I know if it's says Allowed: Yes, as long as you obtain to code to unlock, along with using xperia flasher or fastboot tools to correctly unlock then it's should stay unlocked. An unlock allowed: No should not allow a request for unlock code via sony developer world site
Click to expand...
Click to collapse
Some careers like Orange in Slovakia trick the user(or use a different force method) that the bootloader can be unlocked by saying Yes in the service menu, but cannot unlock with the Sony Bootloader Unlock code, due to Command did not succeed error. I think they either have a custom code, or as they said in the email I sent to them: we have something Orange(or other career-related) firmware on our device that blocks unlocking. Or maybe it's just a 0-1 flag. (like ForceLockUnlock=1)
How unhelpful of them, that's why I started obtaining off network handsets from 2010 on wards. SIM UNLOCKED ? and fully bootloader unlockable.
image45 said:
How unhelpful of them, that's why I started obtaining off network handsets from 2010 on wards. SIM UNLOCKED and fully bootloader unlockable.
Click to expand...
Click to collapse
I hate companies who force-lock their phones. I can understand why they block other SIM cards, but come on, let the bootloader unlocked for geeks/devs
Kizoky said:
I hate companies who force-lock their phones. I can understand why they block other SIM cards, but come on, let the bootloader unlocked for geeks/devs
Click to expand...
Click to collapse
I think there's some kind of a 'flag' or something in the TA that blocks us. Or maybe it's something /dev related. If the test point unlocking would work, I would be very happy. Though I don't think it would work with newer phones and it's old.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also @Kizoky how are you planning to add more tutorials? Are you going to edit the first post or add a new post each time?
xezrunner said:
I think there's some kind of a 'flag' or something in the TA that blocks us. Or maybe it's something /dev related. If the test point unlocking would work, I would be very happy. Though I don't think it would work with newer phones and it's old.
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
Also @Kizoky how are you planning to add more tutorials? Are you going to edit the first post or add a new post each time?
Click to expand...
Click to collapse
I'm gonna do It tomorrow
Kizoky said:
I hate companies who force-lock their phones. I can understand why they block other SIM cards, but come on, let the bootloader unlocked for geeks/devs
Click to expand...
Click to collapse
Well I have three xperia E1's that I obtained off network along with this E3 that are all sim unlocked and fully bootloader unlockable. All the E1's are rooted with jelly bean or kit kat flashed via xperia flasher, with bootloader unlock: Yes. I find the 4.3 jb build to be the most responsive for D2005 handsets.
image45 said:
Well I have three xperia E1's that I obtained off network along with this E3 that are all sim unlocked and fully bootloader unlockable. All the E1's are rooted with jelly bean or kit kat flashed via xperia flasher, with bootloader unlock: Yes. I find the 4.3 jb build to be the most responsive for D2005 handsets.
Click to expand...
Click to collapse
Jelly Bean for the Xperia E1 (the official Sony one) is way too much unstable. KitKat is more stable. I've had random reboot issues and freezing issues (especially when playing games) on JB, while everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
xezrunner said:
Jelly Bean for the Xperia E1 (the official Sony one) is way too much unstable. KitKat is more stable. I've had random reboot issues and freezing issues (especially when playing games) on JB, while everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
Click to expand...
Click to collapse
You can decrease the boot time, If you delete the unnecessary apps (Google+, Google Books, etc..) And the apps you can't delete, or you are afraid, you can just disable them.
xezrunner said:
Jelly Bean for the Xperia E1 (the official Sony one) is way too much unstable. KitKat is more stable. I've had random reboot issues and freezing issues (especially when playing games) on JB
Click to expand...
Click to collapse
Well I rarely play games on any of my devices, however you are correct in that Jb does reboot more than kitkat does. When trying to control the kernel better for jelly bean, I did encounter freezing, however once I got the correct configuration it was fine.
xezrunner said:
everything is much better on KitKat (there are still some lags and it takes some time to boot up but everything else is fine.)
The only thing I loved about the JB build was the Notification Shade and the fast bootup time.
Click to expand...
Click to collapse
I would love to say everything is better, however rooting is more of a challenge for some of the kitkat builds and installation of supersu was more tricky/ time consuming. Have to delete apks to speed up kitkat too.
Hope we do get a stable lollipop ROM for the E1.
image45 said:
Well I rarely play games on any of my devices, however you are correct in that Jb does reboot more than kitkat does. When trying to control the kernel better for jelly bean, I did encounter freezing, however once I got the correct configuration it was fine.
I would love to say everything is better, however rooting is more of a challenge for some of the kitkat builds and installation of supersu was more tricky/ time consuming. Have to delete apks to speed up kitkat too.
Hope we do get a stable lollipop ROM for the E1.
Click to expand...
Click to collapse
I hope too. But we'll not get an Official Lollipop provided by Sony
We'll have to wait for experienced Devs.
Related
Hello,
I'm quite noob [totally newbie] in android installation and all, but I have been experiencing some problem on my atrix :
- after each reboot, all that have been erased reappeared, and all that have been installed/created disappeared... like a reset at a given date, or if nothing was really persisted in memory..
=> I tried a factory reset (via menu or hard reset) : after reboot, everything is like before
=> I tried to root the phone (found tuto with 4 differents tools) ; the tools don't fail, but after reboot, rootcheck tells me 'im not rooted
So last thing to do : change rom. I've found that link
http://forum.xda-developers.com/showthread.php?t=1336232
It seems fit my needs, just wondering :
- as the tuto talks about cyanogen 7, can follow the steps and install a 7.2 instead ?
- the cyanogemod 7.2 seems to be the latest very stable rom for atrix, no ?
- the atrix 4G is called olympus on cyanognemod site right ? i'm always wondering if I pick the good stuff
- for all that tuto i won't need any root permissions ? cause as I explained above, i can't manage to get them :/
- last question, do you think I have good weapons to initiate fire ?
Thanx a lot,
any advice/help is welcome,
quentasil said:
Hello,
I'm quite noob [totally newbie] in android installation and all, but I have been experiencing some problem on my atrix :
- after each reboot, all that have been erased reappeared, and all that have been installed/created disappeared... like a reset at a given date, or if nothing was really persisted in memory..
=> I tried a factory reset (via menu or hard reset) : after reboot, everything is like before
=> I tried to root the phone (found tuto with 4 differents tools) ; the tools don't fail, but after reboot, rootcheck tells me 'im not rooted
So last thing to do : change rom. I've found that link
http://forum.xda-developers.com/showthread.php?t=1336232
It seems fit my needs, just wondering :
- as the tuto talks about cyanogen 7, can follow the steps and install a 7.2 instead ?
- the cyanogemod 7.2 seems to be the latest very stable rom for atrix, no ?
- the atrix 4G is called olympus on cyanognemod site right ? i'm always wondering if I pick the good stuff
- for all that tuto i won't need any root permissions ? cause as I explained above, i can't manage to get them :/
- last question, do you think I have good weapons to initiate fire ?
Thanx a lot,
any advice/help is welcome,
Click to expand...
Click to collapse
yeah CM 7.2 is the stablest build the Artix got (Yes the codename for the Atrix is olympus) download the file at the bottom of this http://download.cyanogenmod.org/?device=olympus and flash it normally in your custom recovery without wiping the data.
Trozzul said:
yeah CM 7.2 is the stablest build the Artix got (Yes the codename for the Atrix is olympus) download the file at the bottom of this http://download.cyanogenmod.org/?device=olympus and flash it normally in your custom recovery without wiping the data.
Click to expand...
Click to collapse
Thanx Let's try, i'll give here my feedback ... well if i'm in trouble, i'll come here to scream and cry
Okay, so I'm back, and I need help :/
I well execute the steps until RSD Lite : i've seen the work on progress, the status was PASS (I assume it's good, even if my english sometimes sucks )
So i've done the next step : at the "starting fastboot protocol support" state, i tried to run the command moto-fastboot.exe oem unlock, and got the message
INFOOEM unlock is not implemented
Click to expand...
Click to collapse
So i googled the problem, and found the topic
http://forum.xda-developers.com/showthread.php?t=1185939&page=2
Click to expand...
Click to collapse
BUT the problem, the solution seems to be exactly what i previously did, i.e use http://diamantephoto.com/IHOP_Bell.rar with RSD Lite ...
So I tried a second time, just to check, but still same... Tell me PASS, but next step remains "INFOOEM unlock is not implemented" ...
I don't know what I am missing ?
quentasil said:
Okay, so I'm back, and I need help :/
I well execute the steps until RSD Lite : i've seen the work on progress, the status was PASS (I assume it's good, even if my english sometimes sucks )
So i've done the next step : at the "starting fastboot protocol support" state, i tried to run the command moto-fastboot.exe oem unlock, and got the
message "INFOOEM unlock is not implemented"
So i googled the problem, and found the topic
BUT the problem, the solution seems to be exactly what i previously did, i.e use http://diamantephoto.com/IHOP_Bell.rar with RSD Lite ...
So I tried a second time, just to check, but still same... Tell me PASS, but next step remains "INFOOEM unlock is not implemented" ...
I don't know what I am missing ?
Click to expand...
Click to collapse
i wanna say the bootloaders still locked, you should only have to open up ADB and type (be sure to go into fasboot mode first)" fastboot oem unlock " if your problem still persists, what guide are you using? i would recommend cyanogenmods if you want to flash their rom http://wiki.cyanogenmod.org/w/Install_CM_for_olympus
Is it because it's a tutorial for a locked phone AT&T, whereas mine isn't locked ?
quentasil said:
Is it because it's a tutorial for a locked phone AT&T, whereas mine isn't locked ?
Click to expand...
Click to collapse
carrier locked? or the bootloader
Trozzul said:
carrier locked? or the bootloader
Click to expand...
Click to collapse
carrier locked ... cause I guess you are right, the RSD Lite step I did doesn't seem to unlock my bootloader
Maybe it's the same cause why I didn't manage to root the mobile, as I explained in first posrt :/
I'm gonna try your link, but the one I had seemed very well
HTML:
http://forum.xda-developers.com/showthread.php?t=1336232
quentasil said:
carrier locked ... cause I guess you are right, the RSD Lite step I did doesn't seem to unlock my bootloader
Maybe it's the same cause why I didn't manage to root the mobile, as I explained in first posrt :/
I'm gonna try your link, but the one I had seemed very well
HTML:
http://forum.xda-developers.com/showthread.php?t=1336232
Click to expand...
Click to collapse
yup cant Root your devices with a locked bootloader carrier lock does not matter towards all this nerd entities
Trozzul said:
yup cant Root your devices with a locked bootloader carrier lock does not matter towards all this nerd entities
Click to expand...
Click to collapse
yes, but that is weird cause I'm NOT locked carrier ... So i should have been able to root without problem :/
quentasil said:
yes, but that is weird cause I'm NOT locked carrier ... So i should have been able to root without problem :/
Click to expand...
Click to collapse
well if you unlocked the boot-loader before you wouldn't have had a problem.
Ok i begin to understand a little Well, i'm slow, but it's late
So the tuto I had was for locked carrier so I guess this is why they expected to get a number when calling moto-fastboot.exe oem unlock...
Since mine is not, INFOOEM unlock is not implemented is the expected result Means my bootloader is unlocked, i'm right ?
The link you gave me is more clear to me
So i tried the next step, to flashClockworkMod Recovery
fastboot flash recovery your_recovery_image.img
Click to expand...
Click to collapse
but i have a beautiful
Failed to process command flash:recovery error (0x180002)
Click to expand...
Click to collapse
Googled a little, tried to change the name and path of the recovery, but didn't work :/
Ok, i just get a little confused now ...
On the tutorial of cyanogenmod, they say
On the computer, open terminal and run the following command:
fastboot oem unlock
If a message appears claiming that "INFOOEM lock is not implemented", you are done.
Click to expand...
Click to collapse
So I assumed that my bootloader was unlocked
But when i search on google the error Failed to process command flash:recovery error (0x180002), i often find that it means that the bootloader isn't unlocked ...
More crazy, sometimes I read that on Motorola Atrix 4G soemtimes bootloader isn't unlockable, and the solution is to flash a sbf with RSD Lite .... What I also did when i followed the first tutorial http://forum.xda-developers.com/showthread.php?t=1336232
So now, i'm totally confused
quentasil said:
Ok, i just get a little confused now ...
On the tutorial of cyanogenmod, they say
So I assumed that my bootloader was unlocked
But when i search on google the error Failed to process command flash:recovery error (0x180002), i often find that it means that the bootloader isn't unlocked ...
More crazy, sometimes I read that on Motorola Atrix 4G soemtimes bootloader isn't unlockable, and the solution is to flash a sbf with RSD Lite .... What I also did when i followed the first tutorial http://forum.xda-developers.com/showthread.php?t=1336232
So now, i'm totally confused
Click to expand...
Click to collapse
the bootloader should be unlockable as for the "[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX" its from 2011 so its a little old, i would stay with the cyanogenmod guide. about all of the time they are very clear with their guides.
if you get INFOOEM lock is not implemented that should mean your bootloader is unlocked,
INFOOEM unlock is not implemented would be a locked bootloader.
Trozzul said:
the bootloader should be unlockable as for the "[GUIDE] A detailed step-by-step "Dummies Guide" to installing CM7 on your ATRIX" its from 2011 so its a little old, i would stay with the cyanogenmod guide. about all of the time they are very clear with their guides.
if you get INFOOEM lock is not implemented that should mean your bootloader is unlocked,
INFOOEM unlock is not implemented would be a locked bootloader.
Click to expand...
Click to collapse
oh yes of course, makes so much sense now but i didn't notice INFOOEM lock/unlock variant
so I have INFOOEM unlock, so my bootloader is still locked, so the message I get when trying to flash the recovery is logical.
Thanx for making it obvious
Now I need to find why my bootloader is still locked, since I used RSD Lite with a sbf, which told me "PASS" after procedure :/
quentasil said:
oh yes of course, makes so much sense now but i didn't notice INFOOEM lock/unlock variant
so I have INFOOEM unlock, so my bootloader is still locked, so the message I get when trying to flash the recovery is logical.
Thanx for making it obvious
Now I need to find why my bootloader is still locked, since I used RSD Lite with a sbf, which told me "PASS" after procedure :/
Click to expand...
Click to collapse
Ok, seems RSDlite doesn't achieve to install new unlockable bootloader ... The process is very quick compare to a tuto i've seen, and at the end i have always the INFOOEM unlock ....
Is there any way to check the bootloader version once boot up ? But I suspect that, as the factory reset didn't work, the same thing happen when I try to put a new boatloader....
quentasil said:
Ok, seems RSDlite doesn't achieve to install new unlockable bootloader ... The process is very quick compare to a tuto i've seen, and at the end i have always the INFOOEM unlock ....
Is there any way to check the bootloader version once boot up ? But I suspect that, as the factory reset didn't work, the same thing happen when I try to put a new boatloader....
Click to expand...
Click to collapse
theres a mode like Hboot for htc devices on motorola phones, i dont know how to get into it though, mess witth the combinations.
---------- Post added at 01:57 PM ---------- Previous post was at 01:45 PM ----------
if we run out of ideas you can try this method i found http://www.atrixforums.com/forum/mo...ocking-bootloader-installing-custom-roms.html
Trozzul said:
theres a mode like Hboot for htc devices on motorola phones, i dont know how to get into it though, mess witth the combinations.
---------- Post added at 01:57 PM ---------- Previous post was at 01:45 PM ----------
if we run out of ideas you can try this method i found http://www.atrixforums.com/forum/mo...ocking-bootloader-installing-custom-roms.html
Click to expand...
Click to collapse
Ok, i'll check this tomorrow ... but at first look the flash of sbf seems the same, except maybe for the sbf file itself...
i have a droid razr max hd XT926 (verizon) is has 4.2.1 android installed ..but it is so buggy and i want uo upgrade it to kitkat which is available in system updates ..i want to ask if i update to kitkat will my phone be locked to verizone sim cards only or i can use other providers sim cards as well i live in pakistan .
desperately waiting for answer .sorry for bad English or if i double the post
thanks.
mshayan27 said:
i have a droid razr max hd XT926 (verizon) is has 4.2.1 android installed ..but it is so buggy and i want uo upgrade it to kitkat which is available in system updates ..i want to ask if i update to kitkat will my phone be locked to verizone sim cards only or i can use other providers sim cards as well i live in pakistan .
desperately waiting for answer .sorry for bad English or if i double the post
thanks.
Click to expand...
Click to collapse
If your are on GSM networks outside U.S., it won't be carrier locked to Verizon, whatever ROM you're using. SIM lock on GSM networks is only valid in U.S. by default (though could be worked around).
So you can upgrade to KitKat, your phone won't be SIM locked.
nagim said:
If your are on GSM networks outside U.S., it won't be carrier locked to Verizon, whatever ROM you're using. SIM lock on GSM networks is only valid in U.S. by default (though could be worked around).
So you can upgrade to KitKat, your phone won't be SIM locked.
Click to expand...
Click to collapse
thanks nagim your reply gave me hope but on inserting other sim it wil give me a message that sim is from other provider if i am not wrong and i just need to ignore it? ,furthermore i want to ask if this kitkat update is buggy or not? like on my current jellybean there are lots of bugs and wifi sometime dont connect fone to internet,some random errors etc..
mshayan27 said:
thanks nagim your reply gave me hope but on inserting other sim it wil give me a message that sim is from other provider if i am not wrong and i just need to ignore it? ,furthermore i want to ask if this kitkat update is buggy or not? like on my current jellybean there are lots of bugs and wifi sometime dont connect fone to internet,some random errors etc..
Click to expand...
Click to collapse
It will probably say that SIM is from unknown source, but you can ignore this, it won't affect your usage.
I cannot comment on the KitKat update, as I have not received my XT926 yet. You could check out the topics in the forum like this one:
http://forum.xda-developers.com/showthread.php?t=2771542
nagim said:
It will probably say that SIM is from unknown source, but you can ignore this, it won't affect your usage.
I cannot comment on the KitKat update, as I have not received my XT926 yet. You could check out the topics in the forum like this one:
http://forum.xda-developers.com/showthread.php?t=2771542
Click to expand...
Click to collapse
thanks a lot ..
mshayan27 said:
thanks a lot ..
Click to expand...
Click to collapse
You're welcome!
Of course, if your experience with the KitKat update will not be good, you can go back to JB, as the bootloader of these phones can be unlocked.
nagim said:
You're welcome!
Of course, if your experience with the KitKat update will not be good, you can go back to JB, as the bootloader of these phones can be unlocked.
Click to expand...
Click to collapse
lol i am newb to this phone lets see what happen
nagim said:
You're welcome!
Of course, if your experience with the KitKat update will not be good, you can go back to JB, as the bootloader of these phones can be unlocked.
Click to expand...
Click to collapse
I would suggest possibly NOT taking the update that is being sent to the phone as it MIGHT be the newest OTA which fixes the bootloader unlock and Towelroot exploits. People have reported getting this update that are not part of the soak.
Instead, ignore it and go and get the FXZ for the Kit Kat and flash that via RSDLite or House of Moto. That way, you can then go and root with Towelroot and then unlock the bootloader.
After that, THEN take any OTAs after that. If the current OTA that is getting pushed to his phone is from the latest soak, then if he takes it, he will NOT be able to unlock the bootloader NOR root his phone.
iBolski said:
I would suggest possibly NOT taking the update that is being sent to the phone as it MIGHT be the newest OTA which fixes the bootloader unlock and Towelroot exploits. People have reported getting this update that are not part of the soak.
Instead, ignore it and go and get the FXZ for the Kit Kat and flash that via RSDLite or House of Moto. That way, you can then go and root with Towelroot and then unlock the bootloader.
After that, THEN take any OTAs after that. If the current OTA that is getting pushed to his phone is from the latest soak, then if he takes it, he will NOT be able to unlock the bootloader NOR root his phone.
Click to expand...
Click to collapse
Thank you for this info, I wasn't aware of that. Surely saved us from some troubles! :good:
nagim said:
Thank you for this info, I wasn't aware of that. Surely saved us from some troubles! :good:
Click to expand...
Click to collapse
No biggie. The latest soak I believe just started getting pushed out in the last couple of days. I was part of the soak test, but I've since gone back to CM11 which is better IMHO, especially with the WiFi.
mshayan27 said:
lol i am newb to this phone lets see what happen
Click to expand...
Click to collapse
After what iBolski wrote, I would suggest that you look around the forum, see how you can flash the firmware. Remember, always read twice if you're not sure what you're doing!
iBolski said:
I would suggest possibly NOT taking the update that is being sent to the phone as it MIGHT be the newest OTA which fixes the bootloader unlock and Towelroot exploits. People have reported getting this update that are not part of the soak.
Instead, ignore it and go and get the FXZ for the Kit Kat and flash that via RSDLite or House of Moto. That way, you can then go and root with Towelroot and then unlock the bootloader.
After that, THEN take any OTAs after that. If the current OTA that is getting pushed to his phone is from the latest soak, then if he takes it, he will NOT be able to unlock the bootloader NOR root his phone.
Click to expand...
Click to collapse
i think my phone is still a verizon because on inserting my sim it still gives me error that simcard is from other user but my simcard does works normally well now the question is is my phone still lock with verizon or how can i unlock it i have no information i just brought fone yesterday from a local market and give me some links to get the best kitkat on my fone ultimatly i just want it to wirk perfectly fine like a free phone with no errors and bugs
thanks
iBolski said:
No biggie. The latest soak I believe just started getting pushed out in the last couple of days. I was part of the soak test, but I've since gone back to CM11 which is better IMHO, especially with the WiFi.
Click to expand...
Click to collapse
Well, it's strange to me that they won't allow us unlock the bootloader anymore (considering that we could before that). Which version is this?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
mshayan27 said:
i think my phone is still a verizon because on inserting my sim it still gives me error that simcard is from other user but my simcard does works normally well now the question is is my phone still lock with verizon or how can i unlock it i have no information i just brought fone yesterday from a local market and give me some links to get the best kitkat on my fone ultimatly i just want it to wirk perfectly fine like a free phone with no errors and bugs
thanks
Click to expand...
Click to collapse
You're confusing the SIM lock and the bootloader lock. The phone is not SIM locked outside the U.S., so don't worry about that.
The bootloader unlock is what allows you to install custom ROMs via a custom recovery.
nagim said:
Well, it's strange to me that they won't allow us unlock the bootloader anymore (considering that we could before that). Which version is this?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
You're confusing the SIM lock and the bootloader lock. The phone is not SIM locked outside the U.S., so don't worry about that.
The bootloader unlock is what allows you to install custom ROMs via a custom recovery.
Click to expand...
Click to collapse
i have no idea about boot loader lock ...i am talkin about simlock and i was asking if i update it to official kitkat will it then work in my country (pakistan)
nagim said:
Well, it's strange to me that they won't allow us unlock the bootloader anymore (considering that we could before that). Which version is this?
---------- Post added at 01:53 PM ---------- Previous post was at 01:50 PM ----------
You're confusing the SIM lock and the bootloader lock. The phone is not SIM locked outside the U.S., so don't worry about that.
The bootloader unlock is what allows you to install custom ROMs via a custom recovery.
Click to expand...
Click to collapse
You're surprised? Why? They don't want unlocking the bootloaders on the XT926s in the first place. The whole bootloader unlocking of the XT926 was due to a security exploit, not because Moto allowed it.
On JB, there was a version that allowed the bootloader to be unlocked until they patched it.
Then, when the initial Kit Kat OTA came out back in May/June, they accidentally re-introduced the bootloader unlock exploit. After the initial OTA, another soak test started and with that, they fixed the exploit again, so nothing surprising there.
This is the FXZ you want to flash to your phone (do NOT take the OTA just in case it's the latest soak which patches the exploit that was re-introduced with the first KK OTA) -> http://sbf.droid-developers.org/download.php?device=5&file=902
Go here to learn how to flash it and then unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
iBolski said:
You're surprised? Why? They don't want unlocking the bootloaders on the XT926s in the first place. The whole bootloader unlocking of the XT926 was due to a security exploit, not because Moto allowed it.
On JB, there was a version that allowed the bootloader to be unlocked until they patched it.
Then, when the initial Kit Kat OTA came out back in May/June, they accidentally re-introduced the bootloader unlock exploit. After the initial OTA, another soak test started and with that, they fixed the exploit again, so nothing surprising there.
This is the FXZ you want to flash to your phone (do NOT take the OTA just in case it's the latest soak which patches the exploit that was re-introduced with the first KK OTA) -> http://sbf.droid-developers.org/download.php?device=5&file=902
Go here to learn how to flash it and then unlock your bootloader -> http://www.droidrzr.com/index.php/topic/46155-rootunlock-442-182183-razr-hdm-only/
Click to expand...
Click to collapse
OK, my bad then again. When I first heard about this, it sounded like and official thing. But maybe I confused it with the Developers Edition.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
mshayan27 said:
i have no idea about boot loader lock ...i am talkin about simlock and i was asking if i update it to official kitkat will it then work in my country (pakistan)
Click to expand...
Click to collapse
It will work.
nagim said:
OK, my bad then again. When I first heard about this, it sounded like and official thing. But maybe I confused it with the Developers Edition.
---------- Post added at 02:28 PM ---------- Previous post was at 02:25 PM ----------
It will work.
Click to expand...
Click to collapse
Correct, the developers edition can always be unlocked, no matter what. But, not many have the developers edition as it was a limited release.
Most XT926 devices are the non-developer's edition and can only be unlocked via an exploit.
Does anyone know if Xperia Z3's supplied directly through EE or Orange have unlockable bootloaders?
I'm due an upgrade but don't want to be stung with a locked bootloader like I was with the Z1.
fl4r3 said:
Does anyone know if Xperia Z3's supplied directly through EE or Orange have unlockable bootloaders?
I'm due an upgrade but don't want to be stung with a locked bootloader like I was with the Z1.
Click to expand...
Click to collapse
Not sure if you can but still even if you could would you want to? Sony has put up a disclaimer on its website stating that unlocking the bootloader on its high-end models, namely the Xperia Z3, will lead to issues in the performance of its camera. After unlocking the bootloader of the device, taking photos in low-light conditions is going to be worse than before...
Yeah that's true but further into the Z3 life cycle things will eventually start to 'feel' boring as I like to tinker with my phones and from experience I tend to get bored if I stay on the same ROM - I may be considered a flashaholic :silly:. It's what makes my Z1 feel boring even though it is a good phone.
So being able to switch between ROMs and custom kernels is something I cannot do without again! Loosing the camera performance is something I can live with (plus a TA backup, once possible before unlocking, will mean I can revert back).
Anyone with an Xperia Z3 from EE want to do a quick check to see if bootloader is unlockable please?
If it's of any help, I know that the xperia z2 from ee had a unlockable bootloader.
Sent from my D6603 using Tapatalk
fl4r3 said:
Does anyone know if Xperia Z3's supplied directly through EE or Orange have unlockable bootloaders?
I'm due an upgrade but don't want to be stung with a locked bootloader like I was with the Z1.
Click to expand...
Click to collapse
http://developer.sonymobile.com/unlockbootloader/
Says:
Please note! It will only be possible to unlock the boot loader for certain releases. You can check if it is possible to unlock the boot loader of your device in the service menu by following the steps below:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
There's a link to a page where you provide an email address where they email you a code.
---------- Post added at 01:31 AM ---------- Previous post was at 01:30 AM ----------
theonecallednick said:
Not sure if you can but still even if you could would you want to?
Click to expand...
Click to collapse
Because as a developer you might be more interested in developing apps for the phone than taking photographs using DRM-restricted software?
Sorry to bump an old thread like this, but is there a definitive answer on this from someone that has a Z3 supplied by EE? I'm looking at a Z3 for an upgrade, but would really like an unlockable bootloader if possible.
Thanks for any input.
One last bump to see if anyone from the UK knows. I suppose I'll go and ask on EE's "support" forum if nobody knows.
I just received my Sony D6603 Xperia Z3 from my carrier which is Rogers. Is there a way to fully unlock the device as if it was purchased as an unlocked version? I've tried searching for answers, but only came up with how to unlock the bootloader and rooting instructions. Unless, if by doing those methods, will fully unlock my device including SIM lock. Any help and insight would be greatly appreciated.
Depending on Roger's terms you should be able to have them unlock it. Appears you have to wait 90 days though.
http://www.rogers.com/web/support/wireless/unlock/733?setLanguage=en
Loving this one:
Why do I have to wait 90 days before I can unlock my device?
Your device has been optimized for use on the Rogers network. You may find that some settings or features do not function properly once the device is unlocked and in use with another carrier's SIM card. We want to ensure that you've had the chance to experience the full capabilities of your device on the Rogers network before making the decision to unlock.
Rooting and bootloader unlock will make no difference to SIM unlock.
The two issues are separate.
gregbradley said:
Rooting and bootloader unlock will make no difference to SIM unlock.
The two issues are separate.
Click to expand...
Click to collapse
If I unlock the SIM on my device via a code, will it still be unlocked even after re-flashing my device's firmware?
Because I just checked to see if I can unlock my device's bootloader, but I'm not able to at all. Maybe I will be after getting it unlocked by Rogers themselves after the 90 days.
Flava0ne said:
If I unlock the SIM on my device via a code, will it still be unlocked even after re-flashing my device's firmware?
Because I just checked to see if I can unlock my device's bootloader, but I'm not able to at all. Maybe I will be after getting it unlocked by Rogers themselves after the 90 days.
Click to expand...
Click to collapse
Once your device is sim free (using code) it will remain unlocked no matter what you do
Flava0ne said:
If I unlock the SIM on my device via a code, will it still be unlocked even after re-flashing my device's firmware?
Because I just checked to see if I can unlock my device's bootloader, but I'm not able to at all. Maybe I will be after getting it unlocked by Rogers themselves after the 90 days.
Click to expand...
Click to collapse
Please re-read what I said. Bootloader unlock and SIM unlock are two separate things. One does not affect the other. It does not matter what you do to one it will not change the status of the other.
gregbradley said:
Please re-read what I said. Bootloader unlock and SIM unlock are two separate things. One does not affect the other. It does not matter what you do to one it will not change the status of the other.
Click to expand...
Click to collapse
Yes, I understood what you said. What I meant was, when or if I get Rogers to unlock my device, unless they're only unlocking the SIM on it, hopefully I'll be able to unlock the bootloader as if I originally purchased it unlocked to begin with. Because when I checked my device's service menu, the status on the bootloader is that it cannot be unlocked using Sony's official method. If I had purchased an unlocked device instead of getting it through Rogers, the bootloader unlockable status would be different, correct?
When I get home, I'll try and see if I can still unlock the bootloader un-officially using Flashtool, unless for some reason that method won't work at all and my bootloader will not be able to be unlocked at all currently.
Edit: All I basically want to accomplish in my new device is to have root access to it. My previous device was an Xperia PLAY which was also purchased originally locked from Rogers. But after fully unlocking it using the Omnius client, I was able to unlock it's bootloader, flash DooMLorD's kernel and get root access to it. Because all the tutorials I've found on how to access root on the Xperia Z3 involves having the bootloader unlocked.
Flava0ne said:
Yes, I understood what you said. What I meant was, when or if I get Rogers to unlock my device, unless they're only unlocking the SIM on it, hopefully I'll be able to unlock the bootloader as if I originally purchased it unlocked to begin with. Because when I checked my device's service menu, the status on the bootloader is that it cannot be unlocked using Sony's official method. If I had purchased an unlocked device instead of getting it through Rogers, the bootloader unlockable status would be different, correct?
Click to expand...
Click to collapse
Probably, but some carrier free devices come with a boot that cannot be unlocked and some devices that are from a carrier can be unlocked. SIM free or SIM locked does not imply the bootloader can or cannot be unlocked.
When I get home, I'll try and see if I can still unlock the bootloader un-officially using Flashtool, unless for some reason that method won't work at all and my bootloader will not be able to be unlocked at all currently.
Edit: All I basically want to accomplish in my new device is to have root access to it. My previous device was an Xperia PLAY which was also purchased originally locked from Rogers. But after fully unlocking it using the Omnius client, I was able to unlock it's bootloader, flash DooMLorD's kernel and get root access to it. Because all the tutorials I've found on how to access root on the Xperia Z3 involves having the bootloader unlocked.
Click to expand...
Click to collapse
There is no unofficial bootloader unlock for this device. Its done through sony's official method or not at all.
If Rodgers unlocks the sim for you it will not affect the status of the bootloader at all, unless you ask them to do it and they agree.
To get root access you do not need to be SIM unlocked. The only way to gain root acces on the Z3 currently is to unlock the bootloader, which you cannot do even if Rodgers SIM unlock it
The xperia play is a legacy device and there were unofficial ways to unlock the bootloader. That has not been the case with all new phones for a couple of years now. I believe (Correct me if I am wrong) that the xperia NEO was one of the last to come with an unofficial unlock (The test point method). My old Xperia T was one of the first to come that had no unofficial unlock and the only way to do it was via Sonys unlock site.
gregbradley said:
Probably, but some carrier free devices come with a boot that cannot be unlocked and some devices that are from a carrier can be unlocked. SIM free or SIM locked does not imply the bootloader can or cannot be unlocked.
Click to expand...
Click to collapse
That's something I didn't know, I've always thought that when you purchase an unlocked Android device that the bootloader would be unlockable, good to know!
gregbradley said:
If Rodgers unlocks the sim for you it will not affect the status of the bootloader at all, unless you ask them to do it and they agree.
Click to expand...
Click to collapse
So they can apparently change the unlock-able status of the bootloader themselves?
gregbradley said:
The xperia play is a legacy device and there were unofficial ways to unlock the bootloader. That has not been the case with all new phones for a couple of years now. I believe (Correct me if I am wrong) that the xperia NEO was one of the last to come with an unofficial unlock (The test point method). My old Xperia T was one of the first to come that had no unofficial unlock and the only way to do it was via Sonys unlock site.
Click to expand...
Click to collapse
So basically, unlocking Sony devices unofficially, stopped around the same time Sony Ericsson became only Sony?
Flava0ne said:
That's something I didn't know, I've always thought that when you purchase an unlocked Android device that the bootloader would be unlockable, good to know!
Click to expand...
Click to collapse
So they can apparently change the unlock-able status of the bootloader themselves?
Click to expand...
Click to collapse
Yes, there have been some posts that some people have managed to do this with some carriers, but I am very sceptical as to this actually happening.
So basically, unlocking Sony devices unofficially, stopped around the same time Sony Ericsson became only Sony?
Click to expand...
Click to collapse
That may be coincidence, I believe that Sony made a tactical decision to stop unofficial methods by allowing some devices to be unlocked officially. This saw an almost immediate stop in devs working on unofficial unlocks as you could always get hold of a device that could be unlocked officially and for free. They basically took the need of an unofficial unlock out of the equation.
If Rogers could do that, it really makes me wonder what kind of tool/program that they use to accomplish this.
Probably something similar to Emma or just fastboot and adb. I really do not know that. The problem is they know the keys, without them it needs a good dev to find a vulnerability and write an exploit. That takes time and skill. And since there is an official method there seems no need to spend that time, as people with that skill just get themselves devices which can be unlocked
My 3rd day now with my new Z3 and I'm really missing having root access.
11901
Will SIM unlocking allow you to delete the Rogers apps?
Also, I noticed my phone doesn't let me hide apps, though most people seem to have that option... is that a Rogers thing or is there something wrong with my device?
Sim unlock has nothing to do with root, so sim unlocking will not give you the ability to remove system apps.
msxghost said:
Will SIM unlocking allow you to delete the Rogers apps?
Also, I noticed my phone doesn't let me hide apps, though most people seem to have that option... is that a Rogers thing or is there something wrong with my device?
Click to expand...
Click to collapse
What i have done already to my device as soon as i got it, before even turning it on for the first time, was use Flashtool and flashed it with the Global Generic Firmware to get rid of the Rogers branding on it. I was able to disable most of the built in bloatware that originally comes with it.
57147468 said:
What i have done already to my device as soon as i got it, before even turning it on for the first time, was use Flashtool and flashed it with the Global Generic Firmware to get rid of the Rogers branding on it. I was able to disable most of the built in bloatware that originally comes with it.
Click to expand...
Click to collapse
Will doing so essentially wipe my phone? Unfortunately I've already downloaded all my apps/customized it how I want otherwise, so I'd like to avoid that if possible. Sorry if this seems like a stupid question, I'm new to Android.
msxghost said:
Will doing so essentially wipe my phone? Unfortunately I've already downloaded all my apps/customized it how I want otherwise, so I'd like to avoid that if possible. Sorry if this seems like a stupid question, I'm new to Android.
Click to expand...
Click to collapse
Not if you tick the box to exclude data on flashtool when you flash it
gregbradley said:
Not if you tick the box to exclude data on flashtool when you flash it
Click to expand...
Click to collapse
Is there some sort of beginners guide/explanation/walkthrough you can point me towards? I've never had an Android before, so I have no idea what I'm doing and I don't want to screw anything up.
Well, hello to everyone. I bought Sony Xperia Z3 and bought code to unlock it for all sim cards and it works. When i visited Sony's site for unlocking bootloader i came across this post:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Well, my device cannot be unlocked because it says No..
so what can i do to unlock it?
Info
mi-smozadrani said:
Well, hello to everyone. I bought Sony Xperia Z3 and bought code to unlock it for all sim cards and it works. When i visited Sony's site for unlocking bootloader i came across this post:
In your device, open the dialler and enter *#*#7378423#*#* to access the service menu.
Tap Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, then you can continue with the next step. If it says No, or if the status is missing, your device cannot be unlocked.
Well, my device cannot be unlocked because it says No..
so what can i do to unlock it?
Click to expand...
Click to collapse
it s better not to try it
it can hard-brick ur device if attempt to unlock bootloader
:good:
Geeks Empire said:
it s better not to try it
it can hard-brick ur device if attempt to unlock bootloader
:good:
Click to expand...
Click to collapse
What? Do you know what you are taking about..
Anyway, if the service menu says you cannot do it then it is impossible to unlock it.
Info
gregbradley said:
What? Do you know what you are taking about..
Anyway, if the service menu says you cannot do it then it is impossible to unlock it.
Click to expand...
Click to collapse
yeah i knew it but if user want to use some tools or something like this it can destroy the phone
:good:
i just need to know what to do to unlock it?
Why unlock it? You will lose your DRM keys if you do..
mi-smozadrani said:
i just need to know what to do to unlock it?
Click to expand...
Click to collapse
For your device it is not allowed, so you can't unlock the bootloader.
/I've read some threads about trying to unlock the bl although service says "no" on other Devices like z Ultra:
It's not impossible to unlock the bl with official method if you know your device earlier had status allowed "yes".
Sindroid said:
Why unlock it? You will lose your DRM keys if you do..
Click to expand...
Click to collapse
I dont care about drm keys. I want to install new custom roms on my phone. So.can.you point me to a link where i can unlock bootloader?
You cannot unlock it if it says bootloader unlock allowed: no
Sindroid said:
Why unlock it? You will lose your DRM keys if you do..
Click to expand...
Click to collapse
its necessity if you want an aosp rom .....
Stock basted Roms on most Sony devices are pretty fast and solid in my opinion no need to really unlock unless your desperate for cm
So that's it? If the bootloader can't be unlocked officially, I'm stuck on Sony roms forever?
Wouldn't bother me so much but my Z3 has a horrible bug where it doesn't work with the bluetooth in my car without rebooting first every time. Was hoping to install CM12.
Could be a hardware fault the Bluetooth
srw985 said:
I'm stuck on Sony roms forever?
Click to expand...
Click to collapse
Why did you get a Sony phone then
mickyw1980 said:
Why did you get a Sony phone then
Click to expand...
Click to collapse
It's not that I have any major issues with Sony roms, I'd just like to be able to flash other stuff in the future, should I want to.
I'm still going to keep the Z3, such a nice phone, nothing else really comes close to it for me yet. Maybe the M9, but I just got the Z3 for £260 from o2 and had it network unlocked, probably have been looking at least double that for the HTC.
You can still root the device and customize it. Tools like the XPosed framework are great at modifying specific parts of the ROM.
But to confirm: you're stuck. You can't unlock Sony's unlockable bootloader. I've heard of people trying to unlock it, I've never heard of a successful case.
Enjoy the phone, it's among the best available right now (imho).