Related
How do I tell if my bootloader is unlocked?
I just got the pone and haven't done anything to it yet but I'm seeing options I wasn't expecting in a locked phone like the ability to enable USB debugging and the ability to instanll non-market apps. So could that mean my phone already has an unlocked bootloader? How do I check?
No - the phones all have that. These have nothing to do with unlocked B/L. The ADB connectivity doesn't function as root though.
Standard Android settings...
Thanks. Guess that means I still have root the phone sometime. At least I'm on 2.3.3 and not 2.3.4 so I should be able to avoid the battery issue.
No battery issue here...
There is no battery issue with 2.3.4 it only happens when you try downgrading to 2.3.2 I believe (which I am not going to test myself, there is already enough people who have fallen into this trap), you can still root 2.3.4 too with rootxperia, the only thing that's not possible (yet) is doomlords kernel for overclocking and that's it, everything else is good, and 2.3.4 is so much better over 2.3.3. quicker, panorama pictures, and lots more including swipe inbuilt into the firmware
I can only root with rootXperia if I have an unlocked bootloader. And to me the process for unlocking the bootloader looks trickier than the process for rooting. So yeah I meant the issue when downgrading to 2.3.2.
It's not too tricky, get alejandrissimo to help you out or you can try the offical sony way. but yeah, I forgot that you couldn't use rootxperia without a unlocked bootloader, my bad. it's worth doing though to be honest.
I don't think I can keep a stable enough connection to Mexico for Alejandrissimo to help me out. Also as far as I know SE hasn't made that site yet that they wanted to allow bootloader unlocking (and even if they did it was gonna be region based so my region most likely won't be supported till 2020 or something like that).
At this point however I'm not noticing much I'd like to have and don't that a root would provide me with. I don't want to try custom roms, I'm perfectly happy with stock and my need for a better battery icon is taken care of by a widget so that just leaves better backups (since to full back everything up these apps needs root access)...but the thing is I probably would only need a backup if I wanted to root or flash something in the first place.
Okay fair enough then, yeah I didn't think about the stable connection. well you don't need a real stable connection to get the IMEI code to sony to get the unlock code, the bootloader unlock is here for the neo -> http://unlockbootloader.sonyericsson.com/instructions I don't think it is based on regions, however if the phone is locked to a provider, (from experience) I don't think it will work, (is why I couldn't use this method) up to you if you want to give it a shot though. good luck.
Oh wow thanks. I didn't know about that all. Does the bootloader get relocked upon doing a PC Companion update just like the root is lost? Because I notice that says not to do an OTA update after the bootloader has been unlocked that way.
The BL will remain unlocked whatever you do. Only deliberately relocking using a specific flash regime (available on XDA) will work.
The OTA warning is because once the BL is unlocked, OTA updates may/can fail badly. PC C is fine.
BTW, all this information is already on this forum...
Yeah sorry. I admit I haven't looked around enough. But I thought it was slightly different for every phone.
Search is your friend mate, do a bit of research and enjoy using your phone.
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
el_ochito said:
I'm 99.9% sold on the Amaze, I will probably be ordering this weekend.
One niggling doubt is the s-off issue. I see that it hasn't been achieved yet, though you can unlock the bootloader via the HTC.com dev code, and that allows perma-rooting and Custom Roms to be installed.
My questions are:
What would S-off achieve? Would there be more impressive roms that use the space and/or resources from /system or somewhere else that can't be touched without S-off? Is a CM 9 possible for the Amaze without S-off? In the CM forums, the "last" word so far is that it hasn't been included on the official list because "it doesn't even have S-off yet".
Is there a difference warranty-wise? I understand the _possible_ implication of asking HTC for the code, they have you in some database that says you unlocked the bootloader. But as for the device itself, is one undoable and the other not?
I understand that flashing kernels would be harder without s-off because it would have to be done via adb, I think I understood. This is no big deal in itself.
Finally: if you unlock the bootloader via the HTC code, and weeks or months down the road an exploit is found to gain S-Off, are you hosed because you used the code and didn't wait?
I'd like to know so I can make my decision before getting the phone. If it's very disadvantageous to use the code rather than wait for S-off, for one reason or another, then I'd have to decide if I can live with only temp-rooting the device.
I am not going to use it on T-Mobile, I'm in Venezuela and will use it with my carrier here, so the unnecessary bloat will be even more of an annoyance, because on top of it sucking, it won't even work; so it would be important for me to at least root to get rid of it.
I'm sorry if my questions are too expansive, I picked up bits and pieces of information in other posts, but none of them answered these questions clearly. Thank you very much to all those who can help me answer them.
Click to expand...
Click to collapse
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
el_ochito said:
Thanks a lot for your response, Binary. I see you have an Amaze and have indeed unlocked its bootloader, so I guess the real question would be: when and if s-off is achieved, will you be able to do it even though you've already unlocked the bootloader with the .bin file?
Warranty would be terribly hard for me to take advantage of anyways after the initial check. If I don't RMA the unit, then I'm pretty much gambling on the fact that it will work well no matter what, since sending it back to the US from Venezuela would be a major PITA, so I don't really care much about voiding it.
Click to expand...
Click to collapse
There is no reason that having an unlocked bootloader will interfere with being able to obtain s-off in the future because we can always relock the bootloader when (or if) it comes down to it.
Binary100100 said:
I don't know where to start with all of your questions but I will do my best.
The difference between S-OFF and Unlocked bootloader is that with S-OFF you can flash anything including a radio and supposedly it would give us the ability to update the kernel by recovery. With an unlocked bootloader we cannot update the radio or kernel but can pretty much change everything else. An unlocked bootloader is required to root your device and remove all the bloat that you don't like. You can temp root the device to remove that bloatware however they will re-appear after a reboot. It has been under some debate if in fact using the unlock_code.bin file provided by htcdev is going to void your warranty if your device would require servicing. If it's vital to know that information then call HTC to inquire before unlocking.
Regarding CM9, it is possible but slightly inconvenient since CM9 would almost certainly require a different kernel and since we cannot flash kernels by recovery it would have to be done in a very certain order. Is it currently in the works? To my understanding, yes! Any idea when you can see it as a download here in the forums? Not at this time. Check back daily because things change frequently!
Click to expand...
Click to collapse
Your words helped me a lot. I was thinking about the diff between s-on/off and lock.unlock bootloader for long. Thanks so much
OK, here's a thought process, help me out if the devs have already tried this. When it comes to unlocking a bootloader you have to find some exploit to unlock it correct? Here are some thoughts I had then:
- Downgrade - I have heard of downgrading Android versions to a previous version, is this possible? If not, why?
- Previous phones - previous phones by Motorola were able to have their bootloaders unlocked, could we try their processes? If not, why?
I really dont know too terribly much about how one goes to find the exploit to unlock the bootloader, so i'm wondering if a dev can help me out by explaining what it takes and how they do it. I would like to take a stab at it. If I can't, I know I have a wealth of knowledge on security where I work....i mean, look at my username, think that says it all. I love the specs of my phone, but I detest the Moto software.
ps - this is for an electrify,
Given up on unlock app doesn't work at all, I have serial cant get ota or unlock bootloader any alternatives coming out
at this point: No.
Its not that we dont want it, its just that the bootloader is both locked down and encrypted, its VERY hard to gain access.
There is some rumors going around that ASUS may unlock full NV flash, if they do that then PERHAPS we might have alternate methods of unlocking, but for now your stuck with what Asus gives you. sorry mate.
Yea saw that post, hope ppl figure it out , love the Modding community been havin a blast with Samsung sgs2 was hoping to be the same for the prime. Been trying to explain about the bootloader problem to rma ppl but they always don't get it.
I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
AzzaMan said:
I have an x10a, and I have for a while. But, its getting old, and boring. I wanted to spice it up with a custom ROM, namely Cyanogenmod. But going through the steps, xflashtool doesn't seem to want to play ball, informing me that "Your phone bootloader cannot be officially unlocked".
I've flashed it before, but only back to stock. This time I want something new.
Now, I've googled around and I've found a few pieces of information about this, but nothing concrete, and certainly nothing very in-depth.
I need to know;
- Does this mean that my attempts at a custom ROM are just at a halt completely? Too bad for me, try a different phone?
- If not, can I force the bootloader to be unlocked, and will it remove my ability to use the radio capability in the phone? (as I have read in a few places now), because my phone isn't a lot of good without the ability to do phone things.
- If I can force it, how, and are there any downsides?
and bonus round;
- Why are there certain phones that just can't have the bootloader unlocked.
Cheers in advance guys, I'd really like to hear some good news about this, but anything is better than what I have at this point.
Click to expand...
Click to collapse
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
1st: you still can flash custom rom, look for the one that have stated (for locked bootloader)
2nd: yes you can, there is testpoint method (correct me If I'm wrong)
3rd: no afaik
Bonus: because there are carrier locked, or just plain damn unlucky
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
AzzaMan said:
Champion. Cheers for the lightning fast reply, didn't expect to hear back for a day or two. I'm gonna begin my search for a copy of cyanogenmod for x10's that are for locked bootloaders. This should be fun
Click to expand...
Click to collapse
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
TakuyaZ said:
Cyanogen mod cant be installed in locked bootloader, due to cm require an custom kernel
Sent from my GT-P3110 using xda app-developers app
Click to expand...
Click to collapse
Damn it... Any suggestions for a good alternative? I'd like something either really fancy, or really low RAM and Battery usage.
TakuyaZ said:
...
Bonus: because there are carrier locked, or just plain damn unlucky
Click to expand...
Click to collapse
My X10i is carrirer locked, and I could unlock the boot loader without any problems.
The problem with those who lose their radio capability, is, as I suspect it to be, because they tried SIM-unlock their devices with third party methods in a way that are not supposed to be done. (A "bad" hack method of some kind). Once they unlock the boot loader, they lose that poor third party hack, and the device reverts back to a SIM-locked state. Since most of the people who do SIM-unlock their devices, uses a different carrier, will also lose the radio because of the carrier/SIM lock.
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
SysGhost said:
One can safely unlock the boot loader if:
* The device remains SIM-locked and haven't been touched by poor, unknown SIM-lock hacks.
* The device isn't SIM-locked in the first place. (Device was delivered in an unlocked state)
* The device is SIM-unlocked with the proper method, where one get proper unlock codes from their original carrier matched with the IMEI code.
Click to expand...
Click to collapse
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
AzzaMan said:
My phone was delivered locked to... Vodaphone? I think. I unlocked it a long time ago. But, I unlocked it by given them my IMEI, and getting the unlock code from them. So, as legit as it gets really. I am still not allowed to just unlock my bootloader. Based on what I've seen in this thread, and a couple of other places, if I force the bootloader to unlock by "less sturdy" means, I should be fine with my sim-unlock, or be able to just contact them again and get a new unlock code.
So, this Testpoint method that TakuyaZ mentioned, anyone able to point me in the right direction for that or an alternative? I can't seem to find a decent tutorial anywhere.
Click to expand...
Click to collapse
What method did you try to unlock the bootloader with? As far as I know your SIM-unlocked status shouldn't be affected at all, as it is properly unlocked, with the radio accepting all carriers. (Radio part of the device is semi-isolated from the rest of the system)
Try this method, and you should be fine: (But I cannot promise anything. If you do try it, you're on your own.)
http://forum.xda-developers.com/showthread.php?t=1253277
It's the method I used on a few X10i devices. Works on SIM-locked devices (They'll remain SIM-locked after, as it should be), as well as unlocked devices that previosly has been SIM-locked, but unlocked with the proper codes from the carrier. They remained SIM-unlocked after unlocking the boot loader. Good news that is.
So if you really know that your device has been properly SIM-unlocked with codes delivered from the carrier that locked the device in the first place, you should be fine. A.f.a.i.k, the only ones that lost their radio on their devices, are the ones who used improper third party hacking methods to SIM-unlock their devices.
Warning: If you are not 100% sure about what method that has been used to SIM-unlock your device. Stop. And turn back.
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
AzzaMan said:
Alright, attempting the method posted above, I have hit a snag. I then proceeded to hit the same snag over and over again, trying minutely different methods.
My problem is with the qsd8250_semc tool.
The most I can get out of it is;
"
Process requires standard 2.x android firmware.
Press any key to continue...
Getting ROOT rights.
error: protocol fault (no status)
error: device not found
error: device not found.
Waiting...
"
Any suggestions? At this point I've tried the methods listed on the sites below, but nothing is working.
http://forum.xda-developers.com/showthread.php?t=1253277
http://www.modaco.com/topic/346145-how-toguideunlock-x10-bootloader-permanently/
Click to expand...
Click to collapse
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
doodownunda said:
Did you try with Flashtool? Don't use the newest version, you need 0.9.10 release. From http://androxyde.github.io/ There is a thread on here some where ill inbox you the link if I find it.
But it is easy as to do. By memory I think you click the padlock in flashtool to root phone then click on the plugins and you have the option to unlock boot loader with a click. Not sure if you have to add recovery first? Get the older version of flashtool though.
I'm sure someone will remember and help :good:
Found this http://forum.xda-developers.com/showthread.php?t=1254087
Hey mate this is the thread I used http://forum.xda-developers.com/showthread.php?t=1821750
Click to expand...
Click to collapse
The only things needed on the X10 part is it to have original (Stock) firmware with Android 2.1 or 2.2, with the original 2.6.29 kernel.
Also one need to enable debugging over USB (Debug Bridge) in the developer settings. And lastly need the drivers installed if using Windows. (Which I assume is the case here)
Once that's done, it should all work.
I've written a Linux script if anyone needs it. Still need the other files from the original qsd8250.7z toolset from the_laser's thread. See attached files.
Place qsd8250_semc.bash in the same director as qsd8250_semc.cmd, then execute it.
One also need Linux-version of the adb command, and in the system PATH variable.