Related
If I have an unlocked G1, can anyone tell me if I root my phone and update to some of the firmwares posted hete (RC33), is it possibel that my phone becomes locked again? I now have RC19 and the phone is fully unlocked, but I'm afraid it can become locked again if I root it or flash it with another firmware. I have enough technical background to do the rooting and flashing as I have expoerience with windows mobile, but this is something new for me. Btw - i totally love the G1 and regret not leaving windows mobile.
The Sim-Lock is in an area of the phone that can not be "flashed' by the user. You are good to go!
Thanks a lot for that !
daveid said:
The Sim-Lock is in an area of the phone that can not be "flashed' by the user. You are good to go!
Click to expand...
Click to collapse
I have been looking for this answer, as well. I have a brand new g1 that I traded my 3g iphone for. It's unlocked and on my AT&T account with no problems. But I had my iphone modded to the hilt and so of course I want to do the with the g1. That was the answer i was looking for!
Anyone else?
Yes. Please, anyone who has rooted and upgraded their UNLOCKED g1 , share experience. It may seem like a stupid question to some of the "advanced" users
bt remember - you weren't born with knowledge, so share it!
For example - an ulocked Iphone can be locked when upgrading so are you sure that the G1 won't lock as well!
What do you mean unlocked? As in sim unlocked, if so it can not be locked by upgrading software.
If you mean unlocked as in you have access to root. Then yes, but that is why you use JF's firmware.
alright ive got a rooted rc33 and im on at&t, ive upgraded from rc30..
so even when you upgrade you're good to go
I mean sim unlocked
I mean what unlocked means - SIM unlocked. My device is rc19 and came unlocked for any sim cards. I haven't done anything with it yet - root or upgrade and I wanted to ask if it's safe root and upgrade a sim unlocked device.
I was concerned it may become locked again because I don't know anything about the unlocking process on the G1 - I know there is a code that's generated according to the IMEI and tahat's about it but I wanted to know if this code can be erased by flashing newer firmware. I have read the steps described on this site for root and upgrade and I plan to do those with my device but I wanted to gather some opinions first. I hope this topic will be useful to others who have bought the G1 unlocked and are concerned.
axlastro said:
I mean what unlocked means - SIM unlocked. My device is rc19 and came unlocked for any sim cards. I haven't done anything with it yet - root or upgrade and I wanted to ask if it's safe root and upgrade a sim unlocked device.
I was concerned it may become locked again because I don't know anything about the unlocking process on the G1 - I know there is a code that's generated according to the IMEI and tahat's about it but I wanted to know if this code can be erased by flashing newer firmware. I have read the steps described on this site for root and upgrade and I plan to do those with my device but I wanted to gather some opinions first. I hope this topic will be useful to others who have bought the G1 unlocked and are concerned.
Click to expand...
Click to collapse
youre safe to upgrade and root, ive done both and mine has stayed unlocked..
Ok. That sounds encouraging. I recall that there were more than one ways to unlock the Iphone. Is it the same with the G1 - I know the main way to unlock
it is by entering a code but I also know there are HARDWARE unlocked devices (as the developer edition of the G1) - Is yours only simUnlocked or is it hardware unlocked too? I'm sorry if I'm asking too much, but I don't want to pay 30$ to get an unlock code again.
It's not like the iphone. The iphone is has to be 'unlocked' by hacking the firmware, since apple have never released any legitimate way of unlocking it, and seem to take great delight in re-locking 'unlocked' iphones every couple of months (this is one of the reasons why my iphone sits at home gathering dust).
The G1 has a standard unlock code, just like just about every phone on the market. Once that code has been entered the phone is unlocked permanently. There's no such thing as a hardware unlocked device - it's merely never been locked to a provider. In the same way if I buy a 5800 from Nokia it's unlocked but it's no different to one got on contract, it's just never been locked.
Google don't care much if you run JF firmware or something you cooked up yourself... they give away the source code so you can do just that.
Thanks.
So entering the simunlock code is irreversible process, having nothing to do with the firmware. That's what I wanted to hear. Thanks guys.
Successfully rooted, upgraded to Jf RC33 with multitouch, put apps on SD and very happy now
Hi all,
I am new to Android device. So sorry in advance if this question appeared to be too stupid...
I understand that I need to unlock the bootloader if I want to install custom ROM.
My questions, do I need to unlock bootloader if I want to flash my device from one official ROM to another region's ROM? Say my device has UK Stock ROM, do I need to unlock the bootloader if I want to install HK stock ROM instead?
Also, I believe there is no hardware difference among different area releases (e.g. UK vs HK). So can I assume it is safe to flash the ROM to another area release?
Thanks!
I'd NOT recommend you to unlock bootloader on your Arc as there are no custom ROMs made for it yet, and maybe developers here could make ROMs that'd not require you to have unlocked bootloader. So you should really wait because if you unlock bootloader -- there's no going back -- you can't re-lock 'em. And you void your warranty too.
You don't have to unlock bootloader for flashing another region's ROM. You can flash other firmwares using "flashtool" (a program originally developed for Xperia X10 by Bin4ry for flashing original firmwares, but updated to work on Xperia Arc also) You can get it here.
And as you're new you should first read this thread.
Also for newbie step-by-step guides [with videos] for flashing ROMs, unlocking bootloader, etc. visit the link below:
http://www.theandroidsoul.com/tag/xperia-arc-hacks/
Brilliant,
Thanks for he information.
Can anyone confirm that there's no hardware difference between different region's release? (LT15i, LT15a are only different model numbers due to region?)
itskapil said:
And you void your warranty too.
Click to expand...
Click to collapse
That's simply not true.
There mere act of unlocking your bootloader does not void your warranty.
There is potential for you to void you warranty if you then were to flash a custom ROM but simply unlocking the bootloader won't void it.
Wrong section
It is possible to relock bootloader - if you have taken TA backup before unlocking, if you restore it bootloader will be relocked. I'm investigating TA Misc area to find out how to relock bootloader on already unlocked devices without TA backup.
Step666 said:
That's simply not true.
There mere act of unlocking your bootloader does not void your warranty.
There is potential for you to void you warranty if you then were to flash a custom ROM but simply unlocking the bootloader won't void it.
Click to expand...
Click to collapse
Actually SE asks you to insert your IMEI No. to get the secret key for unlocking the bootloader, and since unlocking bootloader is obviously meant for flashing custom ROMs, SE will put fingers on you only if you damage your phone -- as they have your IMEI registered under their systems as bootloader unlocked. Below are the warnings they've stated on their blog:
Please note that you may void the warranty of your phone if you unlock the boot loader. Sony Ericsson can then no longer guarantee the full functionality of your phone, and will not be responsible for any unsigned custom software being flashed to the phone after the boot loader is unlocked. Certain functions in your phone might cease to work, and performance might not be ideal. You might also damage your phone permanently. In the worst case, unlocking the boot loader will cause physical injuries or material damage, for example, due to the phone overheating.
Click to expand...
Click to collapse
and
Please note that there is no turning back when unlocking the boot loader. You will not be able to revert the phone to a locked or original state if you unlock it. Also, if you brick the phone, it is your own responsibility.
Click to expand...
Click to collapse
And @blagus man that'd really cool
itskapil said:
Actually SE asks you to insert your IMEI No. to get the secret key for unlocking the bootloader, and since unlocking bootloader is obviously meant for flashing custom ROMs, SE will put fingers on you only if you damage your phone -- as they have your IMEI registered under their systems as bootloader unlocked.
Click to expand...
Click to collapse
Just because someone has retrieved their unlocking key, that does not mean they have unlocked their bootloader, so there's no way SE will refuse to honour a warranties purely on that basis.
This is further evidenced by the fact that it is possible to retrieve unlocking keys for network-locked handsets which, as things stand, cannot have their bootloaders unlocked.
Also, you may want to re-read what SE have actually said:
Please note that you may void the warranty of your phone if you unlock the boot loader.
Click to expand...
Click to collapse
To further support Step666 - unlocking the bootloader in itself does NOT void the warranty.. LEGALLY SE cannot waive their obligations to warranty because someone unlocked the BL... it's the installation of custom ROM/ Kernals/ bootloader changes that gives them the right to refuse support...
no it's not possible see here:
http://forum.xda-developers.com/showpost.php?p=14019729&postcount=16
Step666 said:
Just because someone has retrieved their unlocking key, that does not mean they have unlocked their bootloader, so there's no way SE will refuse to honour a warranties purely on that basis.
This is further evidenced by the fact that it is possible to retrieve unlocking keys for network-locked handsets which, as things stand, cannot have their bootloaders unlocked.
Click to expand...
Click to collapse
Buddy my point was NOT just "retrieving unlocking key" -- this is very obvious that SE won't blame a customer just for retrieving an unlocking key, but if you unlock bootloader too -- that explains your interest in using a custom ROM on your phone.
Now if you're thinking that someone would just unlock his phone's bootloader, and never use a custom ROM over it, then simply that kind of effort is not worth it as there won't be any fun in that. Right?
See I understand your point, and you're right, but it just doesn't looks practical to me.
[Tried posting this in Q&A forum but received no answers]
I am coming from Droid Incredible running CM 7.1 on PagePlus for 3 years (Verizon MVNO for those who don't know). So I am familiar with Android ecosystem and rooting.
I am looking to buy Moto X to be used in USA on H2O (AT&T MVNO) because on Pageplus the speed are limited to 3G and most new phones cannot be activated without flashing which I don't want to do.
1) Is there any reason NOT to buy Developer Edition (GSM Networks)? Current price is now the same as AT&T branded version and I am OK with just one color being available.
2) Am I correct in understanding that this version of the phone supports all LTE and HSPA frequencies both for AT&T and TMobile? Quote from the spec:
Networks
GSM/GPRS/EDGE - UMTS/HSPA + up to 42 Mbps - 4G LTE
2G/2.5G GSM/GPRS/EDGE bands
850/900/1800/1900 MHz
3G UMTS bands
850/900/ AWS/1900/2100 MHz with HSPA+ up to 42 Mbps (B5/B8/B4/B2/B1)
4G LTE bands
700/AWS/1900MHz (B17/B4/B2)
3) Are there any known issues with Moto X that has not been fixed with software updates yet? I am also considering Moto G which would be good enough for me but it has battery issues ("instant" drops from full charge to 1%) that are now investigated by Motorola but no solution yet. For Moto X so far I only found that some people have small cracks on their cases that are fixed by mailing it for warranty work.
1) I too considered the GSM Dev Edition of the Moto X but decided not to get it based on looks. I don't like white phones. The Dev Moto X has a woven white back and I didn't like that. I also have not use for 32GB of internal storage. I didn't even fill the 8GB that was on my RAZR M (previous phone). This was my reasoning, so I went with the MotoMaker GSM unlocked retail Moto X (also referred to as the T-Mobile version).
2)I don't know about the Dev version but if I had to guess I'd say it's like my phone, so yes. I have an AT&T SIM in my Moto X and I get 4G LTE when I'm in town.
3)The only issues I know of are the cracks as you mentioned and the some of the wood backs having a poor finish applied. There may be another that I've yet to read here but I've not had any problem with the phone.
Hikikomori-Otaku said:
1) I too considered the GSM Dev Edition of the Moto X but decided not to get it based on looks. I don't like white phones. The Dev Moto X has a woven white back and I didn't like that. I also have not use for 32GB of internal storage. I didn't even fill the 8GB that was on my RAZR M (previous phone). This was my reasoning, so I went with the MotoMaker GSM unlocked retail Moto X (also referred to as the T-Mobile version).
2)I don't know about the Dev version but if I had to guess I'd say it's like my phone, so yes. I have an AT&T SIM in my Moto X and I get 4G LTE when I'm in town.
3)The only issues I know of are the cracks as you mentioned and the some of the wood backs having a poor finish applied. There may be another that I've yet to read here but I've not had any problem with the phone.
Click to expand...
Click to collapse
I don't like white phones either but I want to be able to root. Is what you went with (MotoMaker GSM unlocked retail Moto X) essentially the same as Dev Edition other than color? Or is it only carrier unlocked but not bootloader unlocked?
JoeSchmoe007 said:
I don't like white phones either but I want to be able to root. Is what you went with (MotoMaker GSM unlocked retail Moto X) essentially the same as Dev Edition other than color? Or is it only carrier unlocked but not bootloader unlocked?
Click to expand...
Click to collapse
The main differences between the two would be the retail version can be customs made in MotoMaker and when the bootloader is unlocked you loose your warranty. The Dev version only comes in one style but your warranty will still be intact after unlocking the bootloader.
Hikikomori-Otaku said:
The main differences between the two would be the retail version can be customs made in MotoMaker and when the bootloader is unlocked you loose your warranty. The Dev version only comes in one style but your warranty will still be intact after unlocking the bootloader.
Click to expand...
Click to collapse
Thank you for responding. So the warranty will be void completely, even for the hardware issues completely unrelated to unlocking bootloader?
Can bootloader on retail version be re-locked to send it in for warranty?
I think I read that each time OS updates are released for Moto X new exploit may need to be found to root/unlock bootloader. Did I get it right or am I confusing something?
Can root be achieved without unlocking bootloader? If I understand correctly unlocking bootloader is really only needed if one wants to try different ROM-s and root can sometimes be achieved without unlocking bootloader. But Moto X is almost stock Android, so I see no point in trying other ROM-s but I do want to have root.
JoeSchmoe007 said:
Thank you for responding. So the warranty will be void completely, even for the hardware issues completely unrelated to unlocking bootloader?
Can bootloader on retail version be re-locked to send it in for warranty?
I think I read that each time OS updates are released for Moto X new exploit may need to be found to root/unlock bootloader. Did I get it right or am I confusing something?
Can root be achieved without unlocking bootloader? If I understand correctly unlocking bootloader is really only needed if one wants to try different ROM-s and root can sometimes be achieved without unlocking bootloader. But Moto X is almost stock Android, so I see no point in trying other ROM-s but I do want to have root.
Click to expand...
Click to collapse
Yes, your warranty will be completly void if you unlock the bootloader on any Moto X except the Dev version.
You can relock (and reunlock) the bootloader but because you have to get the unlock key from Motorola, they will know even if you relock it. I believe there is also a line in fastboot that will will indicate if the warrently is void (as a result of the first unlock).
This is true. With any update there is the potential for an exploit being 'removed'. The same is true for most bootloaders but not necessarily for this phone. Even if the bootloader is updated, the unlock code for your phone will still work.
Yes, root can be achieved without unlocking the bootloader but it's a complex method for this phone. It's much easier to unlock the bootloader, flash a custom recovery, and flash the SU binary. This is also the preferred method if it's avalible for your Moto X.
Unlocking your bootloader let's you do a few things. The most common it to flash another recovery image and thus a new ROM. You can also flash kernals, binaries, apps, and a few other things with the bootloader unlocked.
Hikikomori-Otaku said:
....
This is true. With any update there is the potential for an exploit being 'removed'. The same is true for most bootloaders but not necessarily for this phone. Even if the bootloader is updated, the unlock code for your phone will still work.
Yes, root can be achieved without unlocking the bootloader but it's a complex method for this phone. It's much easier to unlock the bootloader, flash a custom recovery, and flash the SU binary. This is also the preferred method if it's avalible for your Moto X.
Unlocking your bootloader let's you do a few things. The most common it to flash another recovery image and thus a new ROM. You can also flash kernals, binaries, apps, and a few other things with the bootloader unlocked.
Click to expand...
Click to collapse
So what specific exploit can be removed? For rooting? Or for unlocking bootloader? The way I understand one can always unlock bootloader using code from Motorola no matter if your phone is retail or Dev. Edition, however then root may or may not work? But this contradicts with what you said about if bootloader is unlocked then you can flash custom recovery and SU, so you can still always achieve root. Is there an FAQ or thread on this forum where this is described in details?
JoeSchmoe007 said:
So what specific exploit can be removed? For rooting? Or for unlocking bootloader? The way I understand one can always unlock bootloader using code from Motorola no matter if your phone is retail or Dev. Edition, however then root may or may not work? But this contradicts with what you said about if bootloader is unlocked then you can flash custom recovery and SU, so you can still always achieve root. Is there an FAQ or thread on this forum where this is described in details?
Click to expand...
Click to collapse
Any exploit can be removed, so long as they're found and will not inhibit the use of the device. I guess I should clarify a bit. Your bootloader and root access have different ways to get them. The bootloader basically protects the partitions of the phone. The only way to unlock the bootloader of the Moto X is to go to Motorola and get the unique unlock code for your Moto X. The Verizon retail and AT&T retail versions are the only two models of my knowledge that can't be unlocked by Motorola and no exploit has been found for them. How root is achieved by having an unlocked bootloader is as followed; The bootloader is unlocked giving the user access to the partitions of the phone > a custom recovery is flashed > using the new recovery SU binary is added (flashed) to the dormant Android OS. Without an unlocked bootloader, this method is impossible as you can't complete the first step. This is when an exploit in the Android OS is needed. The current SlapMyMoto exploit takes advantage that Motorola lets Moto X users downgrade. Once on a lower version of Android, we can root that and basically 'tunnel' up a path to give ourselves root in they newer version of Android. The unlocked bootloader method is preferred because it's easier and will almost always work (unless Android is given a huge remake). While in recovery, the Android OS is not loaded and thus can't protect itself. This makes adding stuff to it much simpler. When the Android OS is booted though, there are security measures in place that we unrooted can't get past without an exploit.
http://forum.xda-developers.com/showthread.php?t=2603358
This thread has a lot of good info from rooting on both locked and unlocked bootloaders, downgrading, and much more.
Honestly I think you answered your own question. If rooting is your number one priority and you don't mind the white back (which I like actually), then I think the Developer Edition is a no brainer for you.
If you want a custom phone and rooting isn't that important, or you don't care about the warranty, then I'd say get the MotoMaker version.
As far as bugs, the only bug I know of is an exchange bug (which I don't use exchange so I don't even know what the bug is/was), but it was fixed in 4.4.2.
You can root the carrier version ie motomaker. That's all you really need is root along with greenify, xposed, gravity box, and viper4android.
MOTO X Slapped
[email protected] said:
You can root the carrier version ie motomaker. That's all you really need is root along with greenify, xposed, gravity box, and viper4android.
MOTO X Slapped
Click to expand...
Click to collapse
Currently there is NO root method for 4.4.2 without unlocking the bootloader.
I have recently been told that unlocked bootloader is not required for ROOT.
If I get N4, I'll want to root, but don't care about ROMS. So, I had been thinking I would likely need to got with TMO phone on AT&T, rather than AT&T, due to unlocked boot loader (although I planned to wait to be sure it is unlocked).
But, given that unlocked bootloader is not required for ROOT, I'm wondering if I still need to look at TMO. I suspect should just wait and see what shakes out.
Interested in hearing anyone's thoughts on Rooting possibility for the N4,
(my browser spazzed and I lost my last post if it shows up as a double ignore the other one!)
I'm new to Android and finding it confusing so thanks for the help so far!
I have a 910F Note 4 on Lollipop and want to root it to get rid of bloatware and possibly stop ads (if I can convince myself it's ethical) btu I *may* want to custom ROM it later.
So far your help and my reading have taught me this:
-- I can root using chainfire in order to get rid of bloat and block ads
-- If after rooting I later want a custom ROM or Xposed I'll need to get custom recovery in which case I'll be able to add CWM or TWRP later to my rooted phone
Assuming the above are true (if not please tell me!!) my question is this:
What on earth is oem unlock/bootloader unlock? In my reading I've come across people talking about this and it wiping the phone. I can't find an easy answer online. If I root +/- do CWM/TWRP will that automatically do OEM unlock or are they different things? Is bootloader unlock a different thing too? I'm confused! Will I need to root AND custom recovery AND oem unlock AND unlock bootloader?
Thanks in advance!!!
Some devices come with a locked bootloader, where you may be able to root the device via an exploit, but you can't change lower level software (ie kernel and/or recovery)... unless there is an unlock method for the bootloader.
The devices that do have a locked bootloader can be locked by the manufacturer, or by the carrier. That's the difference between the two. Either way the bootloader is still locked, only difference is who called for the locking.
For example, note 4 on tmobile does not have a locked bootloader, however, note 4 on at&t does. That decision was made by at&t, not Samsung. As far as I know, the at&t variant does not have a method for unlocking the bootloader yet so there's not much development for the device.
Compare to nexus devices, where Google automatically has the manufacturer lock the bootloader, but it being a development device, it's the easiest bootloader to unlock. It's literally a one line command in adb. HTC devices are locked but you can get an HTC dev code to unlock it from HTC.
I hope that makes sense. The best way to determine if your device has a locked bootloader is to visit the development forum or the general/Q&A forums for your device. If you have a locked bootloader and there is an unlock method, you only have to do it once (until you update or relock your bootloader). Some locked devices never get an unlock method. It designed to maintain the security and integrity of the device, but it also prevents user tampering.
Thank you for your thorough reply absinthesummer, very helpful.
However I'm still a little confused. My reading suggests to me that T-Mobile (910T) is *rootable* and the AT&T version (910S?) is not *rootable* but I'm in the UK and don't use these providers I use EE. And so I have the international variant of the Note 4 which is the 910F. I don't see a subforum or help for the UK EE version of the note 4 but as it's the 910F I assume that's the one I need to search for and not worry that EE will have put their own lock onto the 910F??
Now, because this happens to coincide with what you are saying has a locked bootloader or not, am I to assume that whether or not something is rootable is the same as whether or not it has an unlockable bootloader? i.e. is something only rootable or not because its bootloader is unlockable or not? If so therefore am I correct to assume that as the 910F which I have is rootable that it is also bootloadunlockable? And furthermore am I correct to assume that the very process of rooting itself unlocks the bootloader? Or perhaps in the case of the 910F it doesn't need to be so is even easier than Nexus devices? i.e. I just simply root and that in itself mean bootloader is already unlocked (and I am assuming that oem unlock is the same thing?)
I'm getting myself in a muddle I think!
Hehe it's totally cool, and yes your carrier could put a lock on it but that's incredibly rare in Europe due to frequent traveling between countries and the need to change Sims and carriers often... or at least that's what I've been told. The US carriers who lock their bootloaders are typically GSM carriers who do not expect you to need to root/carrier unlock/whatever. It's a control thing imo.
Anyway, your note 4 does not have a locked bootloader. If you check the development forum for your device you will see plenty of roms and guides and directions for rooting. That's usually a good indication that a device is unlocked (and those anticipating the release of new devices tend to get lock information prior to release, so they know which device they intend to buy).
Anyway, since you don't have a locked bootloader I wouldn't worry about it... that reminds me of a device I had for about a week, the LG L9. It had an oem bootloader lock but the international variant did not. We could root it & use a specially designed recovery with the bootloader locked but we couldn't flash a custom kernel (with a custom rom). They figured out that we could flash the international firmware and unlock that way, but it would make our display backwards (mirrored) and while that could be fixed, we would never be able to revert the boot screen. Now that's way too much trouble to go through just to unlock a bootloader and I did end up returning it and getting an s3 instead.
Bootloader locks are no fun, but they are not often placed on international devices for various reasons, so really I wouldn't worry about it too much.
If you get a device like a Google nexus, or an HTC that has a known locked bootloader, the bootloader and unlock method will be specifically mentioned in the routing guide. I hope that helps.
One more thing: rootability and locked bootloaders are not mutually exclusive, sometimes you can root devices with locked bootloaders and sometimes people will come up with ways around them (ie note 3 has safe strap recovery that runs parallel to stock recovery) to be able to use custom roms. However, if no exploit is found and there is no workaround, development will stall until one or both of those things is found. You may be able to root a device with a locked BL, but you may not be able to flash custom roms/kernels without a workaround. What I meant though is if you see a popular device with very little development, that's probably due to a locked bootloader and not having found a way around it yet. Most guides will explicitly mention the BL though if it's something you need to do
Yet another thoroughly helpful and detailed reply. Thank you very much indeed. You're a star!